<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with SAPE SAP Editor -->
<AIM xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="aim.xsd">
    <DocInfoSection>
        <DocName DocType="AIM">rr_com</DocName>
        <DocNum Number="250" Project="8443"/>
        <Description>
            <Section>The Protocol Stacks are used to define the functionality of the GSM protocols for interfaces. The GSM specifications are normative when used to describe the functionality of interfaces, but the stacks and the subdivision of protocol layers does not imply or restrict any implementation.</Section>
            <Section>The protocol stack for GPRS consists of several entities. Each entity has one ore more service access points, over which the entity provides a service for the upper entity.</Section>
            <Section>The information units passed via the SAPs are called primitives and consists of an operation code and several parameters. See the Users Guide for details.</Section>
            <Section>The Air-interface document (MSG) defines the radio interface between Mobile Station (MS) and network. It gives the general description of messages format of layer 3.</Section>
            <Section>The present document makes definitions for Radio Resource (RR) management common to several MSGs (RR, GRR and GMM).</Section>
            <Section>Figure 1-1: Architecture of the GSM/GPRS protocol stack</Section>
            <Section>The entities of the GSM/GPRS protocol stack are:</Section>
            <Section>1.1 GRR (RLC/MAC) - Radio Link Control/Medium Access Control</Section>
            <Section>This layer contains two functions: The Radio Link Control function provides a radio-solution-dependent reliable link. The Medium Access Control function controls the access signalling (request and grant) procedures for the radio channel, and the mapping of LLC frames onto the GSM physical channel.</Section>
            <Section>1.2 LLC - Logical Link Control</Section>
            <Section>The LLC entity provides multiple highly reliable logical links for asynchronous data transfer between the MS and the network. It supports variable-length information frames, acknowledged and unacknowledged data transfer, flow and sequence control, error detection and recovery, notification of unrecoverable errors, user identity confidentiality, and ciphering of user and signaling data.</Section>
            <Section>1.3 GMM - GPRS Mobility Management</Section>
            <Section>The GMM entity provides procedures for the mobility of the MS, such as informing the network of its present location, and user identity confidentiality. It manages the GMM context (attach, detach, routing area updating), supports security functions such as authentication of user and MS, controls ciphering of data, and initiates the response to paging messages.</Section>
            <Section>1.4 SM - Session Management</Section>
            <Section>The main function of the session management (SM) is to support PDP context handling of the user terminal. Session Management activates, modifies and deletes the contexts for packet data protocols (PDP). Session Management services are provided at the SMREG-SAP and the SNSM-SAP for anonymous and non-anonymous access. The non-anonymous and anonymous access procedures for PDP context activation and PDP context deactivation are available at the SMREG-SAP. In addition there exists a PDP context modification for non-anonymous PDP contexts.</Section>
            <Section>1.5 SNDCP - Subnetwork Dependant Convergence Protocol</Section>
            <Section>SNDCP carries out all functions related to transfer of Network layer Protocol Data Units (N-PDUs) over GPRS in a transparent way. SNDCP helps to improve channel efficiency by means of compression techniques. The set of protocol entities above SNDCP consists of commonly used network protocols. They all use the same SNDCP entity, which then performs multiplexing of data coming from different sources to be sent using the service provided by the LLC layer.</Section>
            <Section>1.6 GACI - GPRS Application Control Interface</Section>
            <Section>The GACI is the GPRS extension of the ACI. It is specified in GSM 07.07 and 07.60. It is responsible for processing of the GPRS related AT Commands to setup, activate and deactivate the PDP context parameter. It also provides functionality for the interworking between GMM/SM/SNDCP and a packet oriented protocol like PPP.</Section>
            <Section>1.7 USART - Universal Synchronous Asynchronous Receiver Transmitter Driver</Section>
            <Section>The USART is a hardware component that facilitates a connection between the mobile station and terminal equipment (e.g. a PC). This interface uses some of the circuits described in V.24.</Section>
            <Section>The data exchange provided by this unit is serial and asynchronous (synchronous communication is not in the scope of this document). A driver that uses interrupts to manage a circular buffer for the sending and receiving direction is necessary in order to use this component in the GPRS. The driver has to be able to perform flow control.</Section>
            <Section>1.8 TOM - Tunnelling of Messages</Section>
            <Section>The TOM entity is present if and only if HS136 is supported (the feature flag FF_HS136 is enabled).</Section>
            <Section>The main function of TOM is to tunnel non-GSM signalling messages between the MS and the SGSN. The only non-GSM signalling which is currently supported by TOM is for the EGPRS-136 system (according to TIA/EIA-136-376). Data transfer in both uplink and downlink direction is possible. Two different priorities (high, low) of signalling data transfer are supported. TOM uses the unacknowledged mode of LLC and the acknowledged mode of GRR (RLC/MAC).</Section>
        </Description>
        <DocHistory>
            <DocVersion Number="001" Year="02"/>
            <Date Day="22" Month="3" Year="2002"/>
            <Author>MSB</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Initial version.</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="002" Year="02"/>
            <Date Day="3" Month="5" Year="2002"/>
            <Author>MSB</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>move spare bit at rf_power4 in rf_cap (Mobile Station Power Class Structure (4 bit))</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="003" Year="02"/>
            <Date Day="16" Month="5" Year="2002"/>
            <Author>MSB</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED at basic element 6.1</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="004" Year="02"/>
            <Date Day="22" Month="5" Year="2002"/>
            <Author>MSB</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Define some members in own structs (gprs_struct, egprs_struct, dtm_struct), remove S_PADDING at the end of a CSN1_S1 element</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="005" Year="02"/>
            <Date Day="5" Month="6" Year="2002"/>
            <Author>LG</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>revised CSN1_S1 IEs</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="006" Year="02"/>
            <Date Day="13" Month="6" Year="2002"/>
            <Author>MSB</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>fix comments for logic of the Encryption algorithms A5/n</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="007" Year="02"/>
            <Date Day="18" Month="6" Year="2002"/>
            <Author>MSB</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Fit Radio Access Capabilities to R97 (remove R99 elements), Link to R97 elements, Comment out the formerly R99 Radio Access Capability</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="008" Year="02"/>
            <Date Day="18" Month="11" Year="2002"/>
            <Author>MSB</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Corection of classmark 3: no spare after A5 bits in case of mb_value == 0 (MB_NO_EUROPEAN_BAND)</Comment>
        </DocHistory>
        <DocRef>
            <RefId>[C_7010.801]</RefId>
            <RefTitle>7010.801, References and Vocabulary, Condat AG</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[3GPP_TS04.18]</RefId>
            <RefTitle>3GPP TS 04.18 V8.12.0 (2001-12)3rd Generation Partnership Project;Technical Specification Group GSM EDGE Radio Access Network;Mobile radio interface layer 3 specification, Radio Resource Control Protocol (Release 1999)</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[GSM_05.02]</RefId>
            <RefTitle>GSM 05.02 V8.5.0 (2000-07)Digital cellular telecommunications system (Phase 2+)Multiplexing and multiple access on the radio path (Release 1999)</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[3GPP_TS05.05]</RefId>
            <RefTitle>3GPP TS 05.05 V8.7.1 (2000-11) 3rd Generation Partnership Project;Technical Specification Group GERANDigital cellular telecommunications system (Phase 2+), Radio subsystem link control (Release 1999)</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[3GPP_TS24.008]</RefId>
            <RefTitle>3GPP TS 24.008 V3.10.0 (2001-12)3rd Generation Partnership Project;Technical Specification Group Core NetworkMobile radio interface layer 3 specification, Core Network Protocols - Stage 3 (Release 1999)</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[3GPP_TS24.007]</RefId>
            <RefTitle>3GPP TS 24.007 V3.6.0 (2000-12)3rd Generation Partnership Project;Technical Specification Group Core NetworkMobile radio interface layer 3 specification, General aspects (Release 1999)</RefTitle>
        </DocRef>
    </DocInfoSection>
    <ConstantsSection>
        <Description>
            <Section>This section contains all constants that are defined for the RR_COM AIM</Section>
        </Description>
        <Constant>
            <Alias>RR_COM_DUMMY_CONSTANT</Alias>
            <Value ValueType="DEC">0</Value>
            <Comment>Dummy to fulfil tool requirements to have section 2 of  an MSG</Comment>
        </Constant>
        <History>
            <Date Day="22" Month="3" Year="2002"/>
            <Author>MSB</Author>
            <Comment>Initial</Comment>
        </History>
    </ConstantsSection>
    <MessagesSection>
        <Description>
            <Section>This section contains all messages that are defined for the RR_COM AIM</Section>
        </Description>
        <Message>
            <Description>
                <Section>This structure defines the RF capability (available bands and radio power class?) of the MS. This structure must be filled by the customer and stored in the permanent configuration memory. From this structure the MS reads the available values on run time and use it to fill the classmark info elements 1 to 3 depend on the found frequency band.</Section>
            </Description>
            <MsgDef>
                <Name>ms_rf_capability</Name>
                <MsgID Direction="DOWNLINK" IDType="BIN">00000001</MsgID>
                <Comment>Mobile Station RF Capabilities</Comment>
            </MsgDef>
            <MsgItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>msg_type</Name>
                </ItemLink>
                <Type>GSM3_V</Type>
                <SpecRef>-</SpecRef>
                <Comment>Message Type</Comment>
            </MsgItem>
            <MsgItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>rf_cap</Name>
                </ItemLink>
                <Type>GSM3_V</Type>
                <SpecRef>-</SpecRef>
                <Comment>MS RF Capability</Comment>
            </MsgItem>
            <History>
                <Date Day="28" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </Message>
    </MessagesSection>
    <MsgStructElementsSection>
        <Description>
            <Section>This section contains all structured elements that are defined for the RR_COM AIM</Section>
        </Description>
        <MsgStructElem>
            <Description>
                <Section>The purpose of the Mobile Station Classmark 1 information element is to provide the network with information concerning aspects of high priority of the mobile station equipment. This affects the manner in which the network handles the operation of the mobile station.</Section>
                <Section>Note : not used in GSM RR.</Section>
                <Section>Reference : [1] section 10.5.1.5</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>mob_class_1</Name>
                <Comment>Mobile Station Classmark 1</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0</Pattern>
                    <BitLen>1</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>rev_lev</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Revision level</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>es_ind</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Early Classmark Sending</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_1</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/1; Encryption algorithm A5/1 available (0) or not (1).  Please note the invers logic!</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>rf_pow_cap</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>RF power capability</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="1" Month="1" Year="2000"/>
                <Author>VK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="19" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move to this document</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>The purpose of the Mobile Station Classmark 2 information element is to provide the network with information concerning aspects of both high and low priority of the mobile station equipment. This affects the manner in which the network handles the operation of the mobile station.</Section>
                <Section>Reference: [3GPP_TS24.008] section 10.5.1.6</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>mob_class_2</Name>
                <Comment>Mobile Station Classmark 2</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0</Pattern>
                    <BitLen>1</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>rev_lev</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Revision level; Indicates the revision level of the MS</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>es_ind</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Early Classmark Sending; &quot;Controlled Early Classmark Sending&quot; option is implementation (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_1</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/1; Encryption algorithm A5/1 available (0) or not (1). Please note the invers logic!</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>rf_pow_cap</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>RF power capability (CM2); Indication of the RF power capabilities corresponding to the supported band</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0</Pattern>
                    <BitLen>1</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ps</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Pseudo Synchronisation capability; PS capability present (1) or not present (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ss_screen</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>SS Screen. Indicator</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>mt_pp_sms</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Short Message capability; MS does supports (1) MT point to point SMS or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>vbs</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>VBS Notification Reception; VBS capability and notifications wanted (1) or vice versa (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>vgcs</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>VGCS Notification Reception; VGCS capability and notifications wanted (1) or vice versa (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>egsm</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Frequency capability; When the GSM 850 or DCS 1800 or PCS 1900 band is used, this bit shall be sent with the value '0'. When a GSM 900 band is used, this bit describes the support of the extension band</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>class3</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Classmark 3; The MS supports options that are indicated in classmark 3 (1) or it does not support any classmark 3 options (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0</Pattern>
                    <BitLen>1</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>lcsva</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>LCSVA capability; LCS value added location request notification supported (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ucs2_treat</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>UCS2 treatment; Indicates the likely treatment by the MS of UCS2 encoded</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>solsa</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>SoLSA Supported; MS supports SoLSA (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>cmsp</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>CMSP Supported; MS supports (1) CM service Prompt (network initiated MO CM connection request) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_3</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/3; Encryption algorithm A5/3 available (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_2</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/2; Encryption algorithm A5/2 available (1) or not (0)</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="7" Month="5" Year="1997"/>
                <Author>VK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="19" Month="4" Year="2000"/>
                <Author>LG</Author>
                <Comment>conform to V7.1.2</Comment>
            </History>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fit to R99</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>The purpose of the Mobile Station Classmark 3 information element is to provide the network with information concerning aspects of the mobile station. The contents might affect the manner in which the network handles the operation of the mobile station.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>mob_class_3</Name>
                <Comment>Mobile Station Classmark 3</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0</Pattern>
                    <BitLen>1</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>Spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>mb_value</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Multiband Support</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_7</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/7</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_6</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/6</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_5</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/5</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_4</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/4</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>radio_cap_2</Name>
                </ItemLink>
                <Control>
                    <Condition>mb_value=5 OR mb_value=6</Condition>
                </Control>
                <SpecRef>-</SpecRef>
                <Comment>Associated Radio Capability 2</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0000</Pattern>
                    <BitLen>4</BitLen>
                </Spare>
                <Control>
                    <Condition>mb_value=1 OR mb_value=2 OR mb_value=4</Condition>
                </Control>
                <SpecRef>-</SpecRef>
                <Comment>Spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>radio_cap_1</Name>
                </ItemLink>
                <Control>
                    <Condition>mb_value#0</Condition>
                </Control>
                <SpecRef>-</SpecRef>
                <Comment>Associated Radio Capability 1</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>rgsm_class</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>R Support (R-GSM Class)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ms_class</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>Multi Slot Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ucs2_treat</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>UCS2 Treatment</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ext_meas</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Extended Measurement Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>measurement</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>Measurement Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>pos_method</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>MS Positioning Method Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>edge_ms_class</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>EGDE Multi Slot Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>egde_struct</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>EGDE Structure</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gsm400_struct</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>GSM 400 Bands Supported Structure</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gsm850_cap</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>GSM 850 Associated Radio Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>pcs1900_cap</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>PCS 1900 Associated Radio Cap.</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>umts_fdd</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>UMTS FDD Radio Access Technology</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>umts_tdd</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>UMTS TDD Radio Access Technology</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>cdma2000</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>CDMA 2000 Radio Access Technology</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>dtm_ms</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>DTM Multislot Structure</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>single_band</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>Single Band Support</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>00000000</Pattern>
                    <BitLen>8</BitLen>
                </Spare>
                <Type>S_PADDING</Type>
                <Control>
                    <CmdSequence>0</CmdSequence>
                </Control>
                <SpecRef>-</SpecRef>
                <Comment>N Spare Padding</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="7" Month="5" Year="1997"/>
                <Author>VK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="20" Month="1" Year="1999"/>
                <Author>LE</Author>
                <Comment>structure changed</Comment>
            </History>
            <History>
                <Date Day="20" Month="4" Year="2000"/>
                <Author>LG</Author>
                <Comment>R Support until Spare Padding and ctrl column added, E bit replaced by spare</Comment>
            </History>
            <History>
                <Date Day="2" Month="11" Year="2001"/>
                <Author>VK</Author>
                <Comment>Remove &quot;{ m_s_class = 1 }&quot; at ucs2_treat and ext_meas_cap</Comment>
            </History>
            <History>
                <Date Day="7" Month="11" Year="2001"/>
                <Author>VK</Author>
                <Comment>Change type of ext_meas_cap and ucs2_treat</Comment>
            </History>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Fit to R99</Comment>
            </History>
            <History>
                <Date Day="4" Month="6" Year="2002"/>
                <Author>LG</Author>
                <Comment>Fit to CSN1_S1 coding type</Comment>
            </History>
            <History>
                <Date Day="18" Month="11" Year="2002"/>
                <Author>MSB</Author>
                <Comment>no spare after A5 bits in case of mb_value == 0 (MB_NO_EUROPEAN_BAND)</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This information field indicates which GSM 400 bands the MS supports and the associated Radio Access Capability for that/those band(s). It is contained in the classmark 3 IE only if the MS supports the GSM 450 and/or the GSM 480 band.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>gsm400_struct</Name>
                <Comment>GSM 400 Bands Supported Structure</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gsm400_supp</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>GSM 400 Bands Supported</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gsm400_cap</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>GSM 400 Associated Radio Capability</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="4" Month="6" Year="2002"/>
                <Author>LG</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>The information field contains values about the measurement capabilities. The SMS field indicates the time for the MS to switch from one radio channel to another, perform a neighbour cell power measurement, and the switch from that radio channel to another radio channel. The SM field indicates the time needed for the MS to switch from one radio channel to another and perform a neighbour cell power measurement.</Section>
                <Section>Reference: [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference: [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>measurement</Name>
                <Comment>Measurement Capability</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>sms_val</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Switch-Measure-Switch-Value</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>sm_val</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Switch-Measure-Value</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="12" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="4" Month="6" Year="2002"/>
                <Author>LG</Author>
                <Comment>removed component meas</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This information field indicates which positiong method(s) are supported by the mobil station. This shall be sent only if the MS supports positioning methods.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>pos_method</Name>
                <Comment>MS Positioning Method</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>assist_eotd</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS assisted E-OTD; bit 5</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>based_eotd</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS based E-OTD; bit 4</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>assist_gps</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS assisted GPS; bit 3</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>based_gps</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS based GPS; bit 2</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>conv_gps</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS conventional GPS; bit 1</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>The EDGE Struct contains the Modulation Capability field which indicates the supported modulation scheme by an EDGE MS in addition to GMSK. If 8-PSK modulation is supported for both uplink and downlink, the additional EDGE RF Power Capability fields indicate the radio capability for 8-PSK modulation in GSM400, GSM850, GSM900, DCS1800 or PCS1900.</Section>
                <Section>This field shall be sent only the MS support EDGE (edge_cap)</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>egde_struct</Name>
                <Comment>EGDE Structure</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>mod</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>EDGE Modulation Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>egde_pow1</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>EGDE RF Power Capability 1</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>egde_pow2</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>EGDE RF Power Capability 2</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="25" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Change short name of EDGE RF Power Capabilities</Comment>
            </History>
            <History>
                <Date Day="4" Month="6" Year="2002"/>
                <Author>LG</Author>
                <Comment>removed component edge</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>The DTM Multislot Struct contains GPRS related capabilities.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>dtm_ms</Name>
                <Comment>DTM Multislot Structure</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>dtm_g_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>DTM GPRS Multi Slot Sub-Class</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>mac_support</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MAC Mode support</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>dtm_e_ms_class</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>DTM EGPRS Multi Slot Sub-Class</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="4" Month="6" Year="2002"/>
                <Author>LG</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This element defines the MS Radio Access Capability. It provides the radio part of the network with information concerning radio aspect of the mobile station. The content might affect the mennaer in which the network handles the operation of the mobile station.</Section>
                <Section>This definition are used by links from the GRR and GMM message interface.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.5.12a</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>ra_cap</Name>
                <Comment>MS RA capability value part</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>acc_tech_typ</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Access Technology Type</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>acc_cap</Name>
                </ItemLink>
                <Type>GSM7_LV</Type>
                <SpecRef>-</SpecRef>
                <Comment>Access Capabilities</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>flag_ra_cap2</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Valid flag for MS RA capability value part II</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ra_cap2</Name>
                </ItemLink>
                <Control>
                    <Condition>flag_ra_cap2=1</Condition>
                </Control>
                <SpecRef>-</SpecRef>
                <Comment>MS RA capability value part II</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="31" Month="5" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="23" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Changes due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="29" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>&quot;Access capability Length&quot; removed and type BL7V included</Comment>
            </History>
            <History>
                <Date Day="15" Month="9" Year="2000"/>
                <Author>ANS</Author>
                <Comment>CSN1_S1</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element in order to correlate GMM and GRR definition</Comment>
            </History>
            <History>
                <Date Day="9" Month="1" Year="2002"/>
                <Author>SAB</Author>
                <Comment>Replace CSN1_S1 control by flag control</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move definition to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="22" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove S_PADDING at the end of a CSN1_S1 element</Comment>
            </History>
            <History>
                <Date Day="18" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Link to R97 elements</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This element defines the MS Radio Access Capability. It?s the same as MS RA capability value part 5.1. The Specification allows any number of access technologies by recursive use of this structure. The real implementation allows only two parts at the moment.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.5.12a</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>ra_cap2</Name>
                <Comment>MS RA capability value part</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>acc_tech_typ</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Access Technology Type</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>acc_cap</Name>
                </ItemLink>
                <Type>GSM7_LV</Type>
                <SpecRef>-</SpecRef>
                <Comment>Access Capabilities</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0</Pattern>
                    <BitLen>1</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="21" Month="9" Year="2001"/>
                <Author>ANS</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element in order to correlate GMM and GRR definition</Comment>
            </History>
            <History>
                <Date Day="9" Month="1" Year="2001"/>
                <Author>SAB</Author>
                <Comment>Add spare bit to finalize recursive MS RA Capability value part struct</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="21" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>replace remaining spare bits by one spare bit</Comment>
            </History>
            <History>
                <Date Day="18" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Link to R97 elements</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This element is a member from MS RA Capability value part</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.5.12a</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>acc_cap</Name>
                <Comment>Access capabilities</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>pow_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>RF Power Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_bits</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>A5 bits</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>es_ind</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Early Classmark Sending</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ps</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Pseudo Synchronisation capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>vgcs</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Voice Group Call Service</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>vbs</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Voice Broadcast Service</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ms_struct</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>Multi Slot Capability Struct</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="31" Month="5" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="23" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Changes due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="31" Month="8" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Spare Bits, *00000000 removed: &quot;may be used ...&quot;</Comment>
            </History>
            <History>
                <Date Day="13" Month="7" Year="2001"/>
                <Author>ID</Author>
                <Comment>rename msc to msc_gmm</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element in order to correlate GMM and GRR definition</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources. Fit to R99</Comment>
            </History>
            <History>
                <Date Day="18" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Fit to R97 (remove all R99 elements), Link to R97 elements</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>No definition of this field (zero as CSN1_S1) means that the same values for multislot parameters as given in an earlier Access capabilities field within this IE apply also here</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.5.12a</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>ms_struct</Name>
                <Comment>Multislot Capability Struct</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>hscsd_ms_class</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>HSCSD multislot class</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gprs_struct</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>GPRS multislot class and Extended Dynamic Allocation Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>sms_sm_value</Name>
                </ItemLink>
                <Type>CSN1_S1</Type>
                <SpecRef>-</SpecRef>
                <Comment>MS Measurement Capability</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="31" Month="5" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="23" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Changed due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="13" Month="7" Year="2001"/>
                <Author>ID</Author>
                <Comment>rename msc to msc_gmm</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element in order to correlate GMM and GRR definition</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources. Fit to R99</Comment>
            </History>
            <History>
                <Date Day="21" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Define some members in own structs (gprs_struct, egprs_struct, dtm_struct) as CSN1_S1 type</Comment>
            </History>
            <History>
                <Date Day="18" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Fit to R97 (remove all R99 elements)</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This field describes the availability of the encryption algorithm A5.</Section>
                <Section>No definition of this field (zero as CSN1_S1) means that the same values apply for parameters as in the immediately preceding Access capabilities field within this IE. The presence of the A5 bits is mandatory in the first access capability struct within this IE</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.5.12a</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>a5_bits</Name>
                <Comment>A5 bits</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_1</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/1; Encryption algorithm A5/1.  Note inverse logic for the A5/1 encryption algorithm between classmark 1 and 2 on the one hand  (available=0 or not=1) and radio access capability on the other hand (available=1 or not=0).</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_2</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/2; Encryption algorithm A5/2 available (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_3</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/3; Encryption algorithm A5/3 available (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_4</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/4; Encryption algorithm A5/4 available (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_5</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/5; Encryption algorithm A5/5 available (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_6</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/6; Encryption algorithm A5/6 available (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_7</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5/7; Encryption algorithm A5/7 available (1) or not (0)</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="23" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element in order to correlate GMM and GRR definition</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>The SMS field indicates the time needed for the mobile station to switch from one radio channel to another, perform a neighbor cell power measurement, and the switch from that radio channel to another radio channel.</Section>
                <Section>The SM field indicates the time needed for the mobile station to switch from one radio channel to another and perform a neighbour cell power measurement.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>sms_sm_value</Name>
                <Comment>MS Measurement Capability</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>sms_val</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Switch-Mesure-Switch Value</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>sm_val</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Switch-Measure-Value</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="31" Month="5" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="23" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Changed due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element in order to correlate GMM and GRR definition</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This field indicates the Multislot Class and the Extended Dynamic Allocation Capability for GPRS. The Multislot Class is coded as the binary representation defined in 3GPP TS GSM 05.02-</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.5.12a</Section>
                <Section>Reference : [GSM_05.02]</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>gprs_struct</Name>
                <Comment>GPRS Multislot Class and Extended Dynamic Allocation Capability</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gprs_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>GPRS multislot class</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gprs_eda</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>GPRS Extended Dynamic Allocation Capability</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="21" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This structure defines the RF capability (available bands and radio power class?) of the MS. This structure must be filled by the customer and store in the permanent configuration memory. From this structure the MS reads the available values on run time and use it to fill the classmark info elements 1 to 3 and the MS Radio Access Capability depend on the found frequency band.</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>rf_cap</Name>
                <Comment>MS RF Capability</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>setbands</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Set Frequency Bands; bitmask of set frequency bands</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>bands</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Supported Frequency Bands; bitmask of all available frequency bands</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>rf_power</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS RF Power Classes; MS RF Power Classes</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>rf_ms</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS RF Multi Slot Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>es_ind</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Early Classmark Sending; &quot;Controlled Early Classmark Sending&quot; option is implementation (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ps</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Pseudo Synchronisation capability; PS capability present (1) or not present (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>mt_pp_sms</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Short Message capability; MS does supports (1) MT point to point SMS or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>lcsva</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>LCSVA capability; LCS value added location request notification supported (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>solsa</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>SoLSA Supported; MS does supports SoLSA (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>cmsp</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>CMSP Supported; MS does supports (1) CM service Prompt (network initiated MO CM connection request) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>mod</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>EDGE Modulation Capability; The Modulation Capability field indicates the supported modulation scheme by MS in addition to GMSK. 8-PSK supported for downlink reception only (0) or for for uplink transmission and downlink reception (1)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>mac_support</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MAC Mode support; MS does supports Dynamic and Fixed Allocation (1) or only supports Exclusive Allocation (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>meas</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Measurement Capability; Indicates whether a IE shall contain any value about the measurement capabilities (1) or not (0).</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ext_meas</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Extended Measurement Capability; The MS does supports &quot;Extended Measurement&quot; (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>compact</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>COMPACT Interference Measurement Capability; The MS does support COMPACT Interference Measurement (1) or not (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>vbs</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>VBS Notification Reception; VBS capability and notifications wanted (1) or vice versa (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>vgcs</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>VGCS Notification Reception; VGCS capability and notifications wanted (1) or vice versa (0)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ucs2_treat</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>UCS2 treatment; Indicates the likely treatment by the MS of UCS2 encoded</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ss_screen</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>SS Screen. Indicator</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>sms_val</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Switch-Measure-Switch-Value</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>sm_val</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>Switch-Measure-Value</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>a5_bits</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>A5 bits; Encryption algorithm A5/n available (0) or not (1)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0</Pattern>
                    <BitLen>1</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>assist_eotd</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS assisted E-OTD; bit 5</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>based_eotd</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS based E-OTD; bit 4</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>assist_gps</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS assisted GPS; bit 3</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>based_gps</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS based GPS; bit 2</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>conv_gps</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>MS conventional GPS; bit 1</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gprs_eda</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>GPRS Extended Dynamic Allocation Capability; Extended Dynamic Allocation Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>egprs_eda</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>EGPRS Extended Dynamic Allocation Capability; Extended Dynamic Allocation Capability</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0</Pattern>
                    <BitLen>1</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="22" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Supplement of classmark 2 and 3 capabilities</Comment>
            </History>
            <History>
                <Date Day="25" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Supplement of Extended Dynamic Allocation Capabilities</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This structure defines the RF capability (available bands and radio power class?) of the MS. This structure must be filled by the customer and store in the permanent configuration memory. From this structure the MS reads the available values on run time and use it to fill the classmark info elements 1 to 3 depend on the found frequency band.</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>pow_class4</Name>
                <Comment>RF Power Capability (4 bits); Power Class of GSM 400, GSM 850, GSM 900, DCS 1800, PCS 1900</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>0</Pattern>
                    <BitLen>1</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>pow_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>RF Power Capability</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="3" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move spare bit to MSB of nibble  (power cap at the lower bits of nibble)</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This structure defines the RF power classes for all available bands of the MS. This is a sub-structure of the MS RF Capability structure.</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>rf_power</Name>
                <Comment>MS RF Power Classes</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>pow_class4</Name>
                </ItemLink>
                <Control>
                    <TypeModifier>[5]</TypeModifier>
                </Control>
                <SpecRef>-</SpecRef>
                <Comment>RF Power Capability (4 bits); Power Class of GSM 400, GSM 850, GSM 900, DCS 1800, PCS 1900</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>egde_pow1</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>EGDE RF Power Capability 1; 8-PSK Power Class of GSM 400, GSM 850, GSM 900</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>egde_pow2</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>EGDE RF Power Capability 2; 8-PSK Power Class of DCS 1800, PCS 1900</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="22" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="25" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Change short name of EDGE RF Power Capabilities</Comment>
            </History>
        </MsgStructElem>
        <MsgStructElem>
            <Description>
                <Section>This structure defines the RF multi slot capability and classes of the MS. This is a sub-structure of the MS RF Capability structure.</Section>
            </Description>
            <MsgStructElemDef Type="STRUCT">
                <Name>rf_ms</Name>
                <Comment>MS RF Multi Slot Capability</Comment>
            </MsgStructElemDef>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gsm_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>GSM Multi Slot Class; Zero indicates that MS doesn?t supports the use of multiple timeslots</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>000</Pattern>
                    <BitLen>3</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>edge_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>EDGE Multi Slot Class; Zero indicates that MS doesn?t supports the use of multiple timeslots</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>000</Pattern>
                    <BitLen>3</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>hscsd_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>HSCSD Multi Slot Class; Zero indicates that MS doesn?t supports the use of multiple timeslots</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>000</Pattern>
                    <BitLen>3</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>gprs_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>GPRS Multi Slot Class; Zero indicates that MS doesn?t supports the use of multiple timeslots</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>dtm_g</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>DTM GPRS Multi Slot Capability; GPRS MS does supports dual transfer mode (DTM)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>dtm_g_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>DTM GPRS Multi Slot Sub-Class; DTM GPRS Multi Slot Sub-Class (independent from the Multi Slot Capabilities field.)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>ecsd_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>ECSD Multi Slot Class; Zero indicates that MS doesn?t supports the use of multiple timeslots</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <Spare>
                    <Pattern>000</Pattern>
                    <BitLen>3</BitLen>
                </Spare>
                <SpecRef>-</SpecRef>
                <Comment>spare</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>egprs_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>EGPRS Multi Slot Class; Zero indicates that MS doesn?t supports the use of multiple timeslots</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>dtm_e</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>DTM EGPRS Multi Slot Capability; Enhanced GPRS MS does supports dual transfer mode (DTM)</Comment>
            </MsgStructElemItem>
            <MsgStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="AIM">rr_com</DocName>
                    <Name>dtm_e_ms_class</Name>
                </ItemLink>
                <SpecRef>-</SpecRef>
                <Comment>DTM EGPRS Multi Slot Sub-Class; DTM EGPRS Multi Slot Sub-Class (independent from the Multi Slot Capabilities field.)</Comment>
            </MsgStructElemItem>
            <History>
                <Date Day="22" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="24" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>gsm_ms_class name changed</Comment>
            </History>
        </MsgStructElem>
    </MsgStructElementsSection>
    <MsgBasicElementsSection>
        <Description>
            <Section>This section contains all basic elements that are defined for the RR_COM AIM</Section>
        </Description>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>bool</Name>
                <BitLen>1</BitLen>
                <Comment>Boolean; the value is set (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>support</Name>
                <BitLen>1</BitLen>
                <Comment>Feature Support; MS does supports a feature (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>flag_ra_cap2</Name>
                <BitLen>1</BitLen>
                <Comment>Valid flag for MS RA capability value part II; Second part of MS RA capability is available (1) or not (1)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>es_ind</Name>
                <BitLen>1</BitLen>
                <Comment>Early Classmark Sending; 'controlled early classmark sending' option is implemented (1) or not (0) in the MS</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>ps</Name>
                <BitLen>1</BitLen>
                <Comment>Pseudo Synchronisation capability; Pseudo synchronisation capabilty is present (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>mt_pp_sms</Name>
                <BitLen>1</BitLen>
                <Comment>Short Message capability; MS does supports (1) MT point to point SMS or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>vgcs</Name>
                <BitLen>1</BitLen>
                <Comment>Voice Group Call Service; VGCS capability and notification wanted (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>vbs</Name>
                <BitLen>1</BitLen>
                <Comment>Voice Broadcast Service; VBS capability and notification wanted (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>class3</Name>
                <BitLen>1</BitLen>
                <Comment>Classmark 3; The MS supports options that are indicated in classmark 3 (1) or it does not support any classmark 3 options (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>lcsva</Name>
                <BitLen>1</BitLen>
                <Comment>LCSVA capability; LCS value added location request notification supported (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>solsa</Name>
                <BitLen>1</BitLen>
                <Comment>SoLSA Supported; MS does supports SoLSA (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>cmsp</Name>
                <BitLen>1</BitLen>
                <Comment>CMSP Supported; MS does supports (1) CM service Prompt (network initiated MO CM connection request) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>ext_meas</Name>
                <BitLen>1</BitLen>
                <Comment>Extended Measurement Capability; MS does supports 'extended measurements`(1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>meas</Name>
                <BitLen>1</BitLen>
                <Comment>Measurement Capability; Indicates whether the IE contains any value about the measurement capabilities or not</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>pos</Name>
                <BitLen>1</BitLen>
                <Comment>MS Positioning Method Capability; Indicates whether MS does supports positioning method or not</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>edge</Name>
                <BitLen>1</BitLen>
                <Comment>EDGE Structure; Indicates whether MS does supports the EDGE or not</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>edge_ms</Name>
                <BitLen>1</BitLen>
                <Comment>Multi Slot Capability; Indicates whether MS does supports the use of multiple timeslots or not</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>ms</Name>
                <BitLen>1</BitLen>
                <Comment>Multi Slot Capability; indicates whether MS does supports the use of multiple timeslots or not</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>hscsd_ms</Name>
                <BitLen>1</BitLen>
                <Comment>HSCSD Multi Slot Capability; indicates whether MS supports the use of multiple timeslots or not</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>gprs_ms</Name>
                <BitLen>1</BitLen>
                <Comment>GPRS Multi Slot Capability; indicates whether MS supports the use of multiple timeslots or not</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>ecsd_ms</Name>
                <BitLen>1</BitLen>
                <Comment>ECSD Multi Slot Capability; indicates whether MS supports the use of multiple timeslots or not</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>egprs_ms</Name>
                <BitLen>1</BitLen>
                <Comment>EGPRS Multi Slot Capability; indicates whether MS supports the use of multiple timeslots or not</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>mod</Name>
                <BitLen>1</BitLen>
                <Comment>Modulation Capability; MS does supports 8-PSK modulation for uplink and downlink (1) or only for downlink (0) in addition to GSMK</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>assist_eotd</Name>
                <BitLen>1</BitLen>
                <Comment>MS assisted E-OTD; MS does supports assisted E-OTD (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>based_eotd</Name>
                <BitLen>1</BitLen>
                <Comment>MS based E-OTD; MS does supports based E-OTD (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>assist_gps</Name>
                <BitLen>1</BitLen>
                <Comment>MS assisted GPS; MS does supports assisted GPS (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>based_gps</Name>
                <BitLen>1</BitLen>
                <Comment>MS based GPS; MS does supports based GPS (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>conv_gps</Name>
                <BitLen>1</BitLen>
                <Comment>MS conventional GPS; MS does supports conventional GPS (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>umts_fdd</Name>
                <BitLen>1</BitLen>
                <Comment>UMTS FDD Radio Access Technology; MS does supports  UMTS FDD (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>umts_tdd</Name>
                <BitLen>1</BitLen>
                <Comment>UMTS TDD Radio Access Technology; MS does supports UMTS TDD (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>cdma2000</Name>
                <BitLen>1</BitLen>
                <Comment>CDMA 2000 Radio Access Technology; MS does supports CDMA 2000 (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>mac_support</Name>
                <BitLen>1</BitLen>
                <Comment>MAC Mode support; MS does supports dynamice and fixed allocation (1) or only exclusive allocation (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>compact</Name>
                <BitLen>1</BitLen>
                <Comment>COMPACT Interference Measurement Capability; COMPACT Interference Measurement Capability is implemented (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>gprs_eda</Name>
                <BitLen>1</BitLen>
                <Comment>GPRS Extended Dynamic Allocation Capability; MS does supports dynamice and fixed allocation (1) or only exclusive allocation (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>egprs_eda</Name>
                <BitLen>1</BitLen>
                <Comment>EGPRS Extended Dynamic Allocation Capability; MS does supports dynamice and fixed allocation (1) or only exclusive allocation (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>a5_1</Name>
                <BitLen>1</BitLen>
                <Comment>A5/1; Encryption algorithm A5/1.  Note inverse logic for the A5/1 encryption algorithm between classmark 1 and 2 on the one hand  (available=0 or not=1) and radio access capability on the other hand (available=1 or not=0).</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>a5_2</Name>
                <BitLen>1</BitLen>
                <Comment>A5/2; Encryption algorithm A5/2 available (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>a5_3</Name>
                <BitLen>1</BitLen>
                <Comment>A5/3; Encryption algorithm A5/3 available (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>a5_4</Name>
                <BitLen>1</BitLen>
                <Comment>A5/4; Encryption algorithm A5/4 available (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>a5_5</Name>
                <BitLen>1</BitLen>
                <Comment>A5/5; Encryption algorithm A5/5 available (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>a5_6</Name>
                <BitLen>1</BitLen>
                <Comment>A5/6; Encryption algorithm A5/6 available (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>a5_7</Name>
                <BitLen>1</BitLen>
                <Comment>A5/7; Encryption algorithm A5/7 available (1) or not (0)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>dtm_g</Name>
                <BitLen>1</BitLen>
                <Comment>DTM GPRS Multi Slot Capability; GPRS MS does supports dual transfer mode (DTM)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This indicates whether the MS supports a feature or not respectively whether the value is set or not.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>dtm_e</Name>
                <BitLen>1</BitLen>
                <Comment>DTM EGPRS Multi Slot Capability; EGPRS MS does supports dual transfer mode (DTM)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bool</Name>
            </ValuesLink>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="16" Month="5" Year="2002"/>
                <Author>MSB</Author>
                <Comment>remove c-macros IMPLEMENTED and NOT_IMPLEMENTED</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2002"/>
                <Author>MSB</Author>
                <Comment>fix logic of encryption algorithms A5/n</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>Discrimination between GSM phase 1 or 2 or support of R99 or later versions.</Section>
                <Section>Reference: [3GPP_TS04.18] section 10.5.1.6 (Mobile Station Classmark 2)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>rev_lev</Name>
                <BitLen>2</BitLen>
                <Comment>Revision Level</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_rev_lev</Name>
            </ValuesLink>
            <History>
                <Date Day="7" Month="5" Year="1997"/>
                <Author>VK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Add R99_SUPPORT</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>Coding of SS screening indicator in mobile station classmark 2</Section>
                <Section>Reference: [GSM_04.08] section 10.5.1.6 (Mobile Station Classmark 2)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>ss_screen</Name>
                <BitLen>2</BitLen>
                <Comment>SS Screening Indicator</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_ss_screen</Name>
            </ValuesLink>
            <History>
                <Date Day="7" Month="5" Year="1997"/>
                <Author>VK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="11" Month="8" Year="1998"/>
                <Author>VK</Author>
                <Comment>Add Values</Comment>
            </History>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Comment supplemented</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>When the GSM 850 or DCS 1800 or PCS 1900 band is used, this bit shall be sent with the value '0'. When a GSM 900 band is used, this bit describes the support of the extension band.</Section>
                <Section>Reference : [GSM_04.08] section 10.5.1.6 (Mobile Station Classmark 2)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>egsm</Name>
                <BitLen>1</BitLen>
                <Comment>Frequency capability</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_egsm</Name>
            </ValuesLink>
            <History>
                <Date Day="7" Month="5" Year="1997"/>
                <Author>VK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Description supplemented</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This information field indicates the likely treatment by the mobile station of UCS2 encoded</Section>
                <Section>character strings. For backward compatibility reasons, if this field is not included, the value 0 shall be assumed by the receiver.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.6 (Mobile Station Classmark 2)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>ucs2_treat</Name>
                <BitLen>1</BitLen>
                <Comment>UCS2 treatment</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_ucs2_treat</Name>
            </ValuesLink>
            <History>
                <Date Day="20" Month="4" Year="2000"/>
                <Author>LG</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>comments changed</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates the band which is supported together with UMTS.</Section>
                <Section>Note: This field shall be sent if the mobile station supports UMTS and one and only one GSM band with the exception of R-GSM; this field shall not be sent otherwise.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>single_band</Name>
                <BitLen>4</BitLen>
                <Comment>Single GSM Band Support</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_single_band</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The modulation capability field indicates the supported modulation scheme by MS in addition to GMSK</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>mod_cap</Name>
                <BitLen>1</BitLen>
                <Comment>Modulation Capability</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_mod_cap</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates the bands which is supported together</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>mb_value</Name>
                <BitLen>3</BitLen>
                <Comment>Multiband Support</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_mb_value</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates the support of the GSM 450 and GSM 480 bands.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>gsm400_supp</Name>
                <BitLen>2</BitLen>
                <Comment>GSM 400 Bands Supported</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_gsm400_supp</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="4" Month="6" Year="2002"/>
                <Author>LG</Author>
                <Comment>description of value 0 changed</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates the access technology type to be associated with the following access capabilities.</Section>
                <Section>Reference: [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>acc_tech_typ</Name>
                <BitLen>4</BitLen>
                <Comment>Access Technology Type</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_acc_tech_typ</Name>
            </ValuesLink>
            <History>
                <Date Day="23" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element in order to correlate GMM and GRR definition</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources. Fit to R99</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The SMS field indicates the time for the MS to switch from one radio channel to another, perform a neighbour cell power measurement, and the switch from that radio channel to another radio channel.</Section>
                <Section>The SM field indicates the time needed for the MS to switch from one radio channel to another and perform a neighbour cell power measurement.</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference: [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>sms_val</Name>
                <BitLen>4</BitLen>
                <Comment>Switch-Measure-Switch-Value</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_sms_val</Name>
            </ValuesLink>
            <History>
                <Date Day="31" Month="5" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element in order to correlate GMM and GRR definition</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources. Fit to R99</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The SMS field indicates the time for the MS to switch from one radio channel to another, perform a neighbour cell power measurement, and the switch from that radio channel to another radio channel.</Section>
                <Section>The SM field indicates the time needed for the MS to switch from one radio channel to another and perform a neighbour cell power measurement.</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference: [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>sm_val</Name>
                <BitLen>4</BitLen>
                <Comment>Switch-Measure-Value</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_sms_val</Name>
            </ValuesLink>
            <History>
                <Date Day="31" Month="5" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element in order to correlate GMM and GRR definition</Comment>
            </History>
            <History>
                <Date Day="8" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources. Fit to R99</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The MS shall indicate the RF power capability of the band for GSM 850, GSM 900 P or E, DCS 1800 or PCS 1900. Note: the coding of the power class in RF radio capability is different to that used in the MS classmark 3 or MS Radio Access Capability information elements (-> 6.13).</Section>
                <Section>Reference: [3GPP_TS24.008] section 10.5.1.5 (Mobile Station Classmark 1)</Section>
                <Section>[3GPP_TS24.008] section 10.5.1.6 (Mobile Station Classmark 2)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>rf_pow_cap</Name>
                <BitLen>3</BitLen>
                <Comment>RF power capability</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_rf_pow_cap</Name>
            </ValuesLink>
            <History>
                <Date Day="7" Month="5" Year="1997"/>
                <Author>VK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="25" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Description and 'RF_CLASS_IRRELEVANT' supplemented</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates wether the associated radio capability for a RF band. Note: the coding of the power class in associated radio capability is different to that used in the MS classmark 1 and 2 information elements (-> 6.12).</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station )</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>pow_class</Name>
                <BitLen>3</BitLen>
                <Comment>RF Power Capability</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_class</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="9" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="24" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>add indexes</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates wether the associated radio capability for a RF band. Note: the coding of the power class in associated radio capability is different to that used in the MS classmark 1 and 2 information elements (-&amp;gt; 6.12).</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station )</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>radio_cap_1</Name>
                <BitLen>4</BitLen>
                <Comment>Associated Radio Capability 1</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_class</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="9" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="24" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>add indexes</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates wether the associated radio capability for a RF band. Note: the coding of the power class in associated radio capability is different to that used in the MS classmark 1 and 2 information elements (-&amp;gt; 6.12).</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station )</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>radio_cap_2</Name>
                <BitLen>4</BitLen>
                <Comment>Associated Radio Capability 2</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_class</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="9" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="24" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>add indexes</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates wether the associated radio capability for a RF band. Note: the coding of the power class in associated radio capability is different to that used in the MS classmark 1 and 2 information elements (-&amp;gt; 6.12).</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station )</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>rgsm_class</Name>
                <BitLen>3</BitLen>
                <Comment>R Support (R-GSM Class)</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_class</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="9" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="24" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>add indexes</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates wether the associated radio capability for a RF band. Note: the coding of the power class in associated radio capability is different to that used in the MS classmark 1 and 2 information elements (-&amp;gt; 6.12).</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station )</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>gsm400_cap</Name>
                <BitLen>4</BitLen>
                <Comment>GSM 400 Associated Radio Capability</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_class</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="9" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="24" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>add indexes</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates wether the associated radio capability for a RF band. Note: the coding of the power class in associated radio capability is different to that used in the MS classmark 1 and 2 information elements (-&amp;gt; 6.12).</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station )</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>gsm850_cap</Name>
                <BitLen>4</BitLen>
                <Comment>GSM 850 Associated Radio Capability</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_class</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="9" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="24" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>add indexes</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates wether the associated radio capability for a RF band. Note: the coding of the power class in associated radio capability is different to that used in the MS classmark 1 and 2 information elements (-&amp;gt; 6.12).</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station )</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>pcs1900_cap</Name>
                <BitLen>4</BitLen>
                <Comment>PCS 1900 Associated Radio Cap.</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_class</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="9" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>move and merge definitions to this document and link it to the original sources.</Comment>
            </History>
            <History>
                <Date Day="24" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>add indexes</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The Multi Slot Class is coded as the binary representation of the multislot class defined in TS GSM 05.02. The range are 1 to 29, all other values are reserved.</Section>
                <Section>Note For HSCSD, only multislot classes 1 to 18 are recognised. An MS with a higher multislot class number shall indicate a suitable multislot class less than 19 for HSCSD applications.</Section>
                <Section>Reference [GSM_05.02] Annex B.1 (MS classes for multislot capability)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>ms_class</Name>
                <BitLen>5</BitLen>
                <Comment>Multi Slot Class</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_ms_class</Name>
            </ValuesLink>
            <History>
                <Date Day="24" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The Multi Slot Class is coded as the binary representation of the multislot class defined in TS GSM 05.02. The range are 1 to 29, all other values are reserved.</Section>
                <Section>Note For HSCSD, only multislot classes 1 to 18 are recognised. An MS with a higher multislot class number shall indicate a suitable multislot class less than 19 for HSCSD applications.</Section>
                <Section>Reference [GSM_05.02] Annex B.1 (MS classes for multislot capability)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>gsm_ms_class</Name>
                <BitLen>5</BitLen>
                <Comment>GSM Multi Slot Class</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_ms_class</Name>
            </ValuesLink>
            <History>
                <Date Day="24" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The Multi Slot Class is coded as the binary representation of the multislot class defined in TS GSM 05.02. The range are 1 to 29, all other values are reserved.</Section>
                <Section>Note For HSCSD, only multislot classes 1 to 18 are recognised. An MS with a higher multislot class number shall indicate a suitable multislot class less than 19 for HSCSD applications.</Section>
                <Section>Reference [GSM_05.02] Annex B.1 (MS classes for multislot capability)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>edge_ms_class</Name>
                <BitLen>5</BitLen>
                <Comment>EDGE Multi Slot Class</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_ms_class</Name>
            </ValuesLink>
            <History>
                <Date Day="24" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The Multi Slot Class is coded as the binary representation of the multislot class defined in TS GSM 05.02. The range are 1 to 29, all other values are reserved.</Section>
                <Section>Note For HSCSD, only multislot classes 1 to 18 are recognised. An MS with a higher multislot class number shall indicate a suitable multislot class less than 19 for HSCSD applications.</Section>
                <Section>Reference [GSM_05.02] Annex B.1 (MS classes for multislot capability)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>hscsd_ms_class</Name>
                <BitLen>5</BitLen>
                <Comment>HSCSD Multi Slot Class</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_ms_class</Name>
            </ValuesLink>
            <History>
                <Date Day="24" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The Multi Slot Class is coded as the binary representation of the multislot class defined in TS GSM 05.02. The range are 1 to 29, all other values are reserved.</Section>
                <Section>Note For HSCSD, only multislot classes 1 to 18 are recognised. An MS with a higher multislot class number shall indicate a suitable multislot class less than 19 for HSCSD applications.</Section>
                <Section>Reference [GSM_05.02] Annex B.1 (MS classes for multislot capability)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>gprs_ms_class</Name>
                <BitLen>5</BitLen>
                <Comment>GPRS Multi Slot Class</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_ms_class</Name>
            </ValuesLink>
            <History>
                <Date Day="24" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The Multi Slot Class is coded as the binary representation of the multislot class defined in TS GSM 05.02. The range are 1 to 29, all other values are reserved.</Section>
                <Section>Note For HSCSD, only multislot classes 1 to 18 are recognised. An MS with a higher multislot class number shall indicate a suitable multislot class less than 19 for HSCSD applications.</Section>
                <Section>Reference [GSM_05.02] Annex B.1 (MS classes for multislot capability)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>ecsd_ms_class</Name>
                <BitLen>5</BitLen>
                <Comment>ECSD Multi Slot Class</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_ms_class</Name>
            </ValuesLink>
            <History>
                <Date Day="24" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>The Multi Slot Class is coded as the binary representation of the multislot class defined in TS GSM 05.02. The range are 1 to 29, all other values are reserved.</Section>
                <Section>Note For HSCSD, only multislot classes 1 to 18 are recognised. An MS with a higher multislot class number shall indicate a suitable multislot class less than 19 for HSCSD applications.</Section>
                <Section>Reference [GSM_05.02] Annex B.1 (MS classes for multislot capability)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference [3GPP_TS24.008] section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>egprs_ms_class</Name>
                <BitLen>5</BitLen>
                <Comment>EGPRS Multi Slot Class</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_ms_class</Name>
            </ValuesLink>
            <History>
                <Date Day="24" Month="7" Year="1999"/>
                <Author>ANS</Author>
                <Comment>Initial due to GSM 04.08 V6.4.0</Comment>
            </History>
            <History>
                <Date Day="18" Month="12" Year="2001"/>
                <Author>SAB</Author>
                <Comment>update of MS radio access capability information element</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates the GPRS or EGPRS DTM capabilities of the MS. The GPRS or EGPRS DTM Multi Slot Sub-Class is independent from the Multi Slot Capabilities field. In case of EPGPRS this field shall be included only if the mobile station supports EGPRS DTM.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference : [3GPP_TS24.008] section section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>dtm_g_ms_class</Name>
                <BitLen>2</BitLen>
                <Comment>DTM GPRS Multi Slot Sub-Class</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_dtm_g_ms_class</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This field indicates the GPRS or EGPRS DTM capabilities of the MS. The GPRS or EGPRS DTM Multi Slot Sub-Class is independent from the Multi Slot Capabilities field. In case of EPGPRS this field shall be included only if the mobile station supports EGPRS DTM.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference : [3GPP_TS24.008] section section 10.5.5.12a (MS Radio Access Capability)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>dtm_e_ms_class</Name>
                <BitLen>2</BitLen>
                <Comment>DTM EGPRS Multi Slot Sub-Class; only if the MS supports EGPRS DTM</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_dtm_g_ms_class</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>If 8-PSK modulation is supported this field indicates the radio capability for 8-PSK.</Section>
                <Section>Note (Classmark 3): If 8-PSK modulation is supported for both uplink and downlink, the EDGE RF Power Capability 2 field indicates the radio capability for 8-PSK modulation in GSM400, GSM850, GSM900, DCS1800 or PCS1900 if supported, and is not included otherwise.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.12a (MS Radio Access Capability)</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station for 8-PSK modulation)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>pow_8psk_cap</Name>
                <BitLen>2</BitLen>
                <Comment>8-PSK Power Capability</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_8psk_cap</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>If 8-PSK modulation is supported this field indicates the radio capability for 8-PSK.</Section>
                <Section>Note (Classmark 3): If 8-PSK modulation is supported for both uplink and downlink, the EDGE RF Power Capability 2 field indicates the radio capability for 8-PSK modulation in GSM400, GSM850, GSM900, DCS1800 or PCS1900 if supported, and is not included otherwise.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.12a (MS Radio Access Capability)</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station for 8-PSK modulation)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>egde_pow1</Name>
                <BitLen>2</BitLen>
                <Comment>EGDE RF Power Capability 1</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_8psk_cap</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>If 8-PSK modulation is supported this field indicates the radio capability for 8-PSK.</Section>
                <Section>Note (Classmark 3): If 8-PSK modulation is supported for both uplink and downlink, the EDGE RF Power Capability 2 field indicates the radio capability for 8-PSK modulation in GSM400, GSM850, GSM900, DCS1800 or PCS1900 if supported, and is not included otherwise.</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.7 (Mobile Station Classmark 3)</Section>
                <Section>Reference : [3GPP_TS24.008] section 10.5.1.12a (MS Radio Access Capability)</Section>
                <Section>Reference : [3GPP_TS05.05] section 4.1.1 (Output power Mobile Station for 8-PSK modulation)</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>egde_pow2</Name>
                <BitLen>2</BitLen>
                <Comment>EGDE RF Power Capability 2</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_pow_8psk_cap</Name>
            </ValuesLink>
            <History>
                <Date Day="27" Month="3" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This parameter defines which frequency bands shall be measured. This parameter is not used in the current implementation but is introduced for future extensions. It is a bitmap indicating the frequency bands for which power measurements shall be carried out.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>bands</Name>
                <BitLen>8</BitLen>
                <Comment>Supported Frequency Bands; bitmask of all available frequency bands</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bands</Name>
            </ValuesLink>
            <History>
                <Date Day="9" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>This parameter defines which frequency bands shall be measured. This parameter is not used in the current implementation but is introduced for future extensions. It is a bitmap indicating the frequency bands for which power measurements shall be carried out.</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>setbands</Name>
                <BitLen>8</BitLen>
                <Comment>Set Frequency Bands; bitmask of set frequency bands</Comment>
            </MsgBasicElemDef>
            <ValuesLink>
                <DocName DocType="AIM">rr_com</DocName>
                <Name>VAL_bands</Name>
            </ValuesLink>
            <History>
                <Date Day="9" Month="4" Year="2002"/>
                <Author>MSB</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
        <MsgBasicElem>
            <Description>
                <Section>Reference: [GSM_04.08] section 10.4</Section>
            </Description>
            <MsgBasicElemDef>
                <Name>msg_type</Name>
                <BitLen>8</BitLen>
                <Comment>Message Type</Comment>
            </MsgBasicElemDef>
            <History>
                <Date Day="7" Month="5" Year="1997"/>
                <Author>VK</Author>
                <Comment>Initial</Comment>
            </History>
        </MsgBasicElem>
    </MsgBasicElementsSection>
    <ValuesSection>
        <Description>
            <Section>This section contains all sets of values that are defined for the RR_COM AIM</Section>
        </Description>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_bool</Name>
                <Comment>values for bool</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>NO</Alias>
                <Comment>value is not set</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>YES</Alias>
                <Comment>value is set</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>NOT_SUPPORTED</Alias>
                <Comment>feature not supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SUPPORTED</Alias>
                <Comment>feature supported</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_rev_lev</Name>
                <Comment>values for rev_lev</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>PHASE_1</Alias>
                <Comment>Reserved for GSM phase 1</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>PHASE_2</Alias>
                <Comment>Used by GSM phase 2 mobile stations</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>R99_SUPPORT</Alias>
                <Comment>Used by mobile stations supporting R99 or later versions</Comment>
            </ValuesItem>
            <ValuesDefault>
                <Comment>Reserved by future use</Comment>
            </ValuesDefault>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_ss_screen</Name>
                <Comment>values for ss_screen</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SS_SCREEN_DEFAULT</Alias>
                <Comment>default value of phase 1</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SS_SCREEN_PHASE_2</Alias>
                <Comment>capability of handling of ellipsis notation and phase 2 error handling</Comment>
            </ValuesItem>
            <ValuesDefault>
                <Comment>for future use (The network shall interpret these values the same as ?1?)</Comment>
            </ValuesDefault>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_egsm</Name>
                <Comment>values for egsm</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>EGSM_NOT_SUPPORTED</Alias>
                <Comment>The mobile station does not support the extension band.</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>EGSM_SUPPORTED</Alias>
                <Comment>The mobile station does support the extension band (E-GSM or R-GSM).</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_ucs2_treat</Name>
                <Comment>values for ucs2_treat</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>DEFAULT_PREF</Alias>
                <Comment>the ME has a preference for the default alphabet (defined in GSM 03.38) over UCS2.</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>NO_PREF</Alias>
                <Comment>the ME has no preference between the use of the default alphabet and the use of UCS2.</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_single_band</Name>
                <Comment>values for single_band</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SINGLE_EGSM</Alias>
                <Comment>Extended GSM is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SINGLE_GSM900</Alias>
                <Comment>GSM 900 is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SINGLE_DCS1800</Alias>
                <Comment>DCS 1800 is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SINGLE_GSM450</Alias>
                <Comment>GSM 450 is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>SINGLE_GSM480</Alias>
                <Comment>GSM 480 is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>SINGLE_GSM850</Alias>
                <Comment>GSM 850 is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias>SINGLE_PCS1900</Alias>
                <Comment>PCS 1900 is supported</Comment>
            </ValuesItem>
            <ValuesDefault>
                <Comment>Reserved</Comment>
            </ValuesDefault>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_mod_cap</Name>
                <Comment>values for mod_cap</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>DL_ONLY_8PSK</Alias>
                <Comment>8-PSK supported for downlink reception only</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>FULL_8PSK</Alias>
                <Comment>8-PSK supported for uplink transmission and downlink reception</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_mb_value</Name>
                <Comment>values for mb_value</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>MB_NO_EUROPEAN_BAND</Alias>
                <Comment>0b000: neither GSM 900, E-GSM or DCS 1800 supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>MB_GSM900</Alias>
                <Comment>0b001: GSM 900 is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>MB_EGSM</Alias>
                <Comment>0b010: E-GSM is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>MB_DCS1800</Alias>
                <Comment>0b100: DCS 1800 is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>MB_DUAL</Alias>
                <Comment>0b101: GSM 900 and DCS 1800 is supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias>MB_DUAL_EXT</Alias>
                <Comment>0b110: E-GSM and DCS 1800 is supported</Comment>
            </ValuesItem>
            <ValuesDefault>
                <Comment>Reserved</Comment>
            </ValuesDefault>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_gsm400_supp</Name>
                <Comment>values for gsm400_supp</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias/>
                <Comment>reserved (if neither GSM 480 nor GSM 450 is supported the whole gsm400_struct is omitted)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>GSM480</Alias>
                <Comment>GSM 480 supported but GSM 450 not supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>GSM450</Alias>
                <Comment>GSM 450 supported but GSM 480 not supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>GSM450_480</Alias>
                <Comment>GSM 450 supported and GSM 480 supported</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_acc_tech_typ</Name>
                <Comment>values for acc_tech_typ</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>ACC_GSM_P</Alias>
                <Comment>GSM P</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>ACC_GSM_E</Alias>
                <Comment>GSM E -note that GSM E covers GSM P</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>ACC_GSM_R</Alias>
                <Comment>GSM R - note that GSM R covers GSM E and GSM P</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>ACC_GSM_1800</Alias>
                <Comment>GSM 1800 (DCS)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>ACC_GSM_1900</Alias>
                <Comment>GSM 1900 (PCS)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>ACC_GSM_450</Alias>
                <Comment>GSM 450</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias>ACC_GSM_480</Alias>
                <Comment>GSM 480</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias>ACC_GSM_850</Alias>
                <Comment>GSM 850</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">15</Value>
                <Alias>ACC_INVALID</Alias>
                <Comment>no valid access technology type present (this value isn?t defined in the specification)</Comment>
            </ValuesItem>
            <ValuesDefault>
                <Comment>unknown</Comment>
            </ValuesDefault>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_sms_val</Name>
                <Comment>values for sms_val</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SM_1</Alias>
                <Comment>1/4  timeslot (~144 micro sec)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SM_2</Alias>
                <Comment>2/4 timeslot (~288 micro sec)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SM_3</Alias>
                <Comment>3/4 timeslot (~433 micro sec)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SM_4</Alias>
                <Comment>4/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>SM_5</Alias>
                <Comment>5/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>SM_6</Alias>
                <Comment>6/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias>SM_7</Alias>
                <Comment>7/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias>SM_8</Alias>
                <Comment>8/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">8</Value>
                <Alias>SM_9</Alias>
                <Comment>9/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">9</Value>
                <Alias>SM_10</Alias>
                <Comment>10/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">10</Value>
                <Alias>SM_11</Alias>
                <Comment>11/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">11</Value>
                <Alias>SM_12</Alias>
                <Comment>12/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">12</Value>
                <Alias>SM_13</Alias>
                <Comment>13/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">13</Value>
                <Alias>SM_14</Alias>
                <Comment>14/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">14</Value>
                <Alias>SM_15</Alias>
                <Comment>15/4 timeslot</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">15</Value>
                <Alias>SM_16</Alias>
                <Comment>16/4 timeslot (~2307 micro sec)</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_rf_pow_cap</Name>
                <Comment>values for rf_pow_cap</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>RF_CLASS_1</Alias>
                <Comment>class 1 for GSM 850, 900P+E, DCS 1800 and PCS 1900</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>RF_CLASS_2</Alias>
                <Comment>class 2 for GSM 850, 900P+E, DCS 1800 and PCS 1900</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>RF_CLASS_3</Alias>
                <Comment>class 3 for GSM 850, 900P+E, DCS 1800 and PCS 1900</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>RF_CLASS_4</Alias>
                <Comment>class 4 for GSM 850, 900P+E (reserved for DCS 1800 and PCS 1900)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>RF_CLASS_5</Alias>
                <Comment>class 5 for GSM 850, 900P+E (reserved for DCS 1800 and PCS 1900)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias/>
                <Comment>reserved</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias/>
                <Comment>reserved</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias>RF_CLASS_IRRELEVANT</Alias>
                <Comment>irrelevent for this IE (multiband GSM MS)</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_pow_class</Name>
                <Comment>values for pow_class</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>POWER_CLASS_1</Alias>
                <Comment>Power Class 1</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>POWER_CLASS_2</Alias>
                <Comment>Power Class 2</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>POWER_CLASS_3</Alias>
                <Comment>Power Class 3</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>POWER_CLASS_4</Alias>
                <Comment>Power Class 4</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>POWER_CLASS_5</Alias>
                <Comment>Power Class 5</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias/>
                <Comment>Reserved</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias/>
                <Comment>Reserved</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="ALPHA">POWER_CLASS_2</Value>
                <Alias>MIN_CLASS_GSM</Alias>
                <Comment>minimal GSM power class</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="ALPHA">POWER_CLASS_5</Value>
                <Alias>MAX_CLASS_GSM</Alias>
                <Comment>maximal GSM power class</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="ALPHA">POWER_CLASS_1</Value>
                <Alias>MIN_CLASS_DCS</Alias>
                <Comment>minimal DCS power class</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="ALPHA">POWER_CLASS_3</Value>
                <Alias>MAX_CLASS_DCS</Alias>
                <Comment>maximal DCS power class</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="ALPHA">POWER_CLASS_1</Value>
                <Alias>MIN_CLASS_PCS</Alias>
                <Comment>minimal PCS power class</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="ALPHA">POWER_CLASS_3</Value>
                <Alias>MAX_CLASS_PCS</Alias>
                <Comment>maximal PCS power class</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="ALPHA">POWER_CLASS_5</Value>
                <Alias>CLASS_MIN_POW_GSM</Alias>
                <Comment>GSM power class with the lowest output power</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="ALPHA">POWER_CLASS_2</Value>
                <Alias>CLASS_MIN_POW_DCS</Alias>
                <Comment>DCS power class with the lowest output power</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="ALPHA">POWER_CLASS_2</Value>
                <Alias>CLASS_MIN_POW_PCS</Alias>
                <Comment>PCS power class with the lowest output power</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>IDX_PWRCLASS_900</Alias>
                <Comment>Index for use with rf_cap.rf_power.pow_class4[] array</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>IDX_PWRCLASS_1800</Alias>
                <Comment>Index for use with rf_cap.rf_power.pow_class4[] array</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>IDX_PWRCLASS_1900</Alias>
                <Comment>Index for use with rf_cap.rf_power.pow_class4[] array</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>IDX_PWRCLASS_850</Alias>
                <Comment>Index for use with rf_cap.rf_power.pow_class4[] array</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>IDX_PWRCLASS_400</Alias>
                <Comment>Index for use with rf_cap.rf_power.pow_class4[] array</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_ms_class</Name>
                <Comment>values for ms_class</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>MSLOT_CLASS_1</Alias>
                <Comment>Multi Slot Class 1</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>MSLOT_CLASS_2</Alias>
                <Comment>Multi Slot Class 2</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>MSLOT_CLASS_3</Alias>
                <Comment>Multi Slot Class 3</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>MSLOT_CLASS_4</Alias>
                <Comment>Multi Slot Class 4</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>MSLOT_CLASS_5</Alias>
                <Comment>Multi Slot Class 5</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias>MSLOT_CLASS_6</Alias>
                <Comment>Multi Slot Class 6</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias>MSLOT_CLASS_7</Alias>
                <Comment>Multi Slot Class 7</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">8</Value>
                <Alias>MSLOT_CLASS_8</Alias>
                <Comment>Multi Slot Class 8</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">9</Value>
                <Alias>MSLOT_CLASS_9</Alias>
                <Comment>Multi Slot Class 9</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">10</Value>
                <Alias>MSLOT_CLASS_10</Alias>
                <Comment>Multi Slot Class 10</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">11</Value>
                <Alias>MSLOT_CLASS_11</Alias>
                <Comment>Multi Slot Class 11</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">12</Value>
                <Alias>MSLOT_CLASS_12</Alias>
                <Comment>Multi Slot Class 12</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">13</Value>
                <Alias>MSLOT_CLASS_13</Alias>
                <Comment>Multi Slot Class 13</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">14</Value>
                <Alias>MSLOT_CLASS_14</Alias>
                <Comment>Multi Slot Class 14</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">15</Value>
                <Alias>MSLOT_CLASS_15</Alias>
                <Comment>Multi Slot Class 15</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">16</Value>
                <Alias>MSLOT_CLASS_16</Alias>
                <Comment>Multi Slot Class 16</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">17</Value>
                <Alias>MSLOT_CLASS_17</Alias>
                <Comment>Multi Slot Class 17</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">18</Value>
                <Alias>MSLOT_CLASS_18</Alias>
                <Comment>Multi Slot Class 18</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">19</Value>
                <Alias>MSLOT_CLASS_19</Alias>
                <Comment>Multi Slot Class 19</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">20</Value>
                <Alias>MSLOT_CLASS_20</Alias>
                <Comment>Multi Slot Class 20 (not for HSCSD)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">21</Value>
                <Alias>MSLOT_CLASS_21</Alias>
                <Comment>Multi Slot Class 21 (not for HSCSD)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">22</Value>
                <Alias>MSLOT_CLASS_22</Alias>
                <Comment>Multi Slot Class 22 (not for HSCSD)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">23</Value>
                <Alias>MSLOT_CLASS_23</Alias>
                <Comment>Multi Slot Class 23 (not for HSCSD)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">24</Value>
                <Alias>MSLOT_CLASS_24</Alias>
                <Comment>Multi Slot Class 24 (not for HSCSD)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">25</Value>
                <Alias>MSLOT_CLASS_25</Alias>
                <Comment>Multi Slot Class 25 (not for HSCSD)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">26</Value>
                <Alias>MSLOT_CLASS_26</Alias>
                <Comment>Multi Slot Class 26 (not for HSCSD)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">27</Value>
                <Alias>MSLOT_CLASS_27</Alias>
                <Comment>Multi Slot Class 27 (not for HSCSD)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">28</Value>
                <Alias>MSLOT_CLASS_28</Alias>
                <Comment>Multi Slot Class 28 (not for HSCSD)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">29</Value>
                <Alias>MSLOT_CLASS_29</Alias>
                <Comment>Multi Slot Class 29 (not for HSCSD)</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_dtm_g_ms_class</Name>
                <Comment>values for dtm_g_ms_class</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SUB_CLASS_1</Alias>
                <Comment>Sub-Class 1 supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SUB_CLASS_5</Alias>
                <Comment>Sub-Class 5 supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SUP_CLASS_9</Alias>
                <Comment>Sub-Class 9 supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias/>
                <Comment>Reserved</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_pow_8psk_cap</Name>
                <Comment>values for pow_8psk_cap</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias/>
                <Comment>Reserved</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>POWER_CLASS_E1</Alias>
                <Comment/>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>POWER_CLASS_E2</Alias>
                <Comment/>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>POWER_CLASS_E3</Alias>
                <Comment/>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_bands</Name>
                <Comment>values for bands</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="HEX">00</Value>
                <Alias>BAND_AUTO</Alias>
                <Comment>0b00000000: All bands shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">01</Value>
                <Alias>BAND_GSM_900</Alias>
                <Comment>0b00000001: GSM 900 is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">02</Value>
                <Alias>BAND_DCS_1800</Alias>
                <Comment>0b00000010: DCS 1800 is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">04</Value>
                <Alias>BAND_PCS_1900</Alias>
                <Comment>0b00000100: PCS 1900 is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">08</Value>
                <Alias>BAND_E_GSM</Alias>
                <Comment>0b00001000: Extended GSM is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">10</Value>
                <Alias>BAND_GSM_850</Alias>
                <Comment>0b00010000: GSM 850 is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">20</Value>
                <Alias>BAND_GSM_450</Alias>
                <Comment>0b00100000: GSM 450 is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">40</Value>
                <Alias>BAND_GSM_480</Alias>
                <Comment>0b01000000: GSM 480 is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">80</Value>
                <Alias>BAND_R_GSM</Alias>
                <Comment>0b10000000: R-GSM is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">03</Value>
                <Alias>BAND_DUAL</Alias>
                <Comment>0b00000011: GSM 900 and DCS 1800 is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">0B</Value>
                <Alias>BAND_DUAL_EXT</Alias>
                <Comment>0b00001011: GSM 900, E-GSM and DCS 1800 is supported, shall be scanned</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">14</Value>
                <Alias>BAND_DUAL_US</Alias>
                <Comment>0b00010100: GSM 850 and PCS 1900 is supported, shall be scanned</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
    </ValuesSection>
</AIM>
