FreeCalypso > hg > fc-magnetite
view cdg3/sap/8010_152_ps_include.sap @ 365:f8ad9dcadde0
RV timing: better RVF_MS_TO_TICKS() formula
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Sun, 31 Dec 2017 06:32:33 +0000 |
| parents | c15047b3d00d |
| children |
line wrap: on
line source
<?xml version="1.0" encoding="UTF-8"?> <!-- edited with SAPE SAP Editor --> <SAP xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="sap.xsd"> <DocInfoSection> <DocName DocType="SAP">8010_152_ps_include</DocName> <DocNum Number="152" Project="8010"/> <Description> <Section>This document contains type and constant declarations used in more than one Service Access Point (SAP) specification for the Protocol Stack (PS). The types and constants declared within this document are common for the entire protocol stack, are only declared here and are imported into SAP documents specifying the interfaces for entities throughout the protocol stack using the include mechanisms of the SAP tool-chain.</Section> <Section>As a document specifying common types and constants, this document is a part of the set of include-documents existing for the protocol stack. The relationship between these documents can be seen in Figure 1.</Section> <Section>Figure 1 - Hierarchical inclusion of type and constant definitions</Section> </Description> <DocHistory> <DocVersion Number="001" Year="02"/> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Initial version.</Comment> </DocHistory> <DocHistory> <DocVersion Number="002" Year="02"/> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Document based on 7010_152_PS_Include.doc</Comment> </DocHistory> <DocHistory> <DocVersion Number="003" Year="02"/> <Date Day="2" Month="12" Year="2002"/> <Author>HEM</Author> <DocStatus State="APPROVED"/> <Comment>Changed status to Accepted.</Comment> </DocHistory> <DocHistory> <DocVersion Number="004" Year="02"/> <Date Day="3" Month="12" Year="2002"/> <Author>NIA</Author> <DocStatus State="APPROVED"/> <Comment>Peak throughput parameter inserted</Comment> </DocHistory> <DocHistory> <DocVersion Number="005" Year="02"/> <Date Day="3" Month="12" Year="2002"/> <Author>NIA</Author> <DocStatus State="APPROVED"/> <Comment>Minor update in Service Access Point Identifier definition</Comment> </DocHistory> <DocHistory> <DocVersion Number="006" Year="02"/> <Date Day="20" Month="12" Year="2002"/> <Author>ALE</Author> <DocStatus State="APPROVED"/> <Comment>"List of unacknowledged SDUs " and "Memory Handle" types have been added.</Comment> </DocHistory> <DocHistory> <DocVersion Number="007" Year="02"/> <Date Day="20" Month="12" Year="2002"/> <Author>AGR</Author> <DocStatus State="APPROVED"/> <Comment>The sdu variable must be the last element in PS_EXPORT.</Comment> </DocHistory> <DocHistory> <DocVersion Number="008" Year="02"/> <Date Day="16" Month="1" Year="2003"/> <Author>LOE</Author> <DocStatus State="SUBMITTED"/> <Comment>Size of SDU buffer array changed to one (1) byte.</Comment> </DocHistory> <DocHistory> <DocVersion Number="009" Year="02"/> <Date Day="29" Month="1" Year="2003"/> <Author>JMA</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Added cell identity and Network operation mode</Comment> </DocHistory> <DocHistory> <DocVersion Number="010" Year="02"/> <Date Day="3" Month="2" Year="2003"/> <Author>KBS</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Inserted est_service definition</Comment> </DocHistory> <DocHistory> <DocVersion Number="011" Year="02"/> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <DocStatus State="SUBMITTED"/> <Comment>Reworked after review</Comment> </DocHistory> <DocHistory> <DocVersion Number="012" Year="02"/> <Date Day="11" Month="2" Year="2003"/> <Author>AGR</Author> <DocStatus State="SUBMITTED"/> <Comment>The SAPI is now common for LLC and DLL SAPs. The enumeration for radio priority now starts from zero.</Comment> </DocHistory> <DocHistory> <DocVersion Number="013" Year="02"/> <Date Day="26" Month="2" Year="2003"/> <Author>JMA</Author> <DocStatus State="SUBMITTED"/> <Comment>Removed cell id and NOM from GSM cell description</Comment> </DocHistory> <DocHistory> <DocVersion Number="014" Year="02"/> <Date Day="7" Month="3" Year="2003"/> <Author>BRY</Author> <DocStatus State="SUBMITTED"/> <Comment>Updating according to review report 8010_152_02_009_review_repost. Only the issues not already implemented since version 009.</Comment> </DocHistory> <DocHistory> <DocVersion Number="015" Year="02"/> <Date Day="24" Month="3" Year="2003"/> <Author>CSH</Author> <DocStatus State="APPROVED"/> <Comment>Regarding section 4.11 U16 (ARFCN) Multiple ranges out commented due to error in generated val files. Needs bugfix of CCDgen.</Comment> </DocHistory> <DocHistory> <DocVersion Number="016" Year="02"/> <Date Day="31" Month="3" Year="2003"/> <Author>JMA</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Corrections to Mode of Operation</Comment> </DocHistory> <DocHistory> <DocVersion Number="017" Year="02"/> <Date Day="4" Month="4" Year="2003"/> <Author>HCH</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Added: Core Network Common GSM-MAP NAS System Information</Comment> </DocHistory> <DocHistory> <DocVersion Number="018" Year="02"/> <Date Day="4" Month="4" Year="2003"/> <Author>KKS</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Core Network Common GSM-MAP NAS System Information removed again .-)</Comment> </DocHistory> <DocHistory> <DocVersion Number="019" Year="02"/> <Date Day="12" Month="6" Year="2003"/> <Author>BRY</Author> <DocStatus State="APPROVED"/> <Comment>Added LLC mode.</Comment> </DocHistory> <DocHistory> <DocVersion Number="020" Year="02"/> <Date Day="27" Month="6" Year="2003"/> <Author>BRY</Author> <DocStatus State="APPROVED"/> <Comment>Updated bookmarks to correct caption in constant section.</Comment> </DocHistory> <DocHistory> <DocVersion Number="021" Year="02"/> <Date Day="21" Month="7" Year="2003"/> <Author>BRY</Author> <DocStatus State="APPROVED"/> <Comment>Changed prim ID to 0x0000 as this is the only allowed multiple defined prim ID value.</Comment> </DocHistory> <DocHistory> <DocVersion Number="022" Year="02"/> <Date Day="13" Month="8" Year="2003"/> <Author>JMA</Author> <DocStatus State="APPROVED"/> <Comment>GSM frequency band values corrected.</Comment> </DocHistory> <DocHistory> <DocVersion Number="023" Year="02"/> <Date Day="15" Month="10" Year="2003"/> <Author>LOE</Author> <DocStatus State="APPROVED"/> <Comment>Added a "not set" value to GSM Frequency Band</Comment> </DocHistory> </DocInfoSection> <PragmasSection> <Description> <Section>Each of these constant values will be used to control the size of an element in a structure. The size parameter will usually denote the number of elements in an array of a specified type. Normally the use of one of these constants will result in a fixed size array declaration, where all elements are used to contain the specified information.</Section> <Section>In case of variable size arrays, a parameter will accompany the declared array, specifying the number of elements actually included/allocated. This parameter is automatically generated when "compiling" this document. This approach is used where it is desirable to allow a dynamic number of elements in a primitive (e.g. when passing lists of information where the worst case number of elements is large or where each element may have considerable size).</Section> <Section>All size constant values will have the prefix SIZE_, which will uniquely link them to this part of the document.</Section> <Section>In general, a size constant determines the number of elements of a given type used to contain data. For strings of digits, this will normally be a number of bytes, with one digit (0-9) contained in each byte. If this encoding is not used, the alternative type of encoding will be explicitly stated at the declaration of the size definition or at the declaration of the parameter using the size definition.</Section> </Description> <Pragma> <Name>PREFIX</Name> <Value ValueType="ALPHA">PS</Value> <Comment>Prefix for this document</Comment> </Pragma> <Pragma> <Name>ALLWAYS_ENUM_IN_VAL_FILE</Name> <Value ValueType="ALPHA">YES</Value> <Comment>Enumeration values in value file</Comment> </Pragma> <Pragma> <Name>ENABLE_GROUP</Name> <Value ValueType="ALPHA">NO</Value> <Comment>Enable h-file grouping</Comment> </Pragma> <Pragma> <Name>COMPATIBILITY_DEFINES</Name> <Value ValueType="ALPHA">NO</Value> <Comment>Compatible to the old #defines</Comment> </Pragma> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="26" Month="12" Year="2002"/> <Author>ALE</Author> <Comment>MAX_UL_SDU item has been added.</Comment> </History> <History> <Date Day="16" Month="1" Year="2003"/> <Author>LOE</Author> <Comment>Maximum size of SDU removed.</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added KC_CONTENT, SIZE_IK, PSC_MIN, PSC_MAX, NCC_MAX, BCC_MAX, CPICH_RSCP_MAX, CPICH_RSCP_MIN, CONTENT_P_TMSI, CONTENT_TMSI</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Added ENABLE_GROUP and COMPATIBILITY_DEFINES to pragmas. Updated some constant descriptions according to review report. Added MIN_BCD_VALUE, MAX_BCD_VALUE, MIN_KEY_SEQ_NUM, MAX_KEY_SEQ_NUM, MIN_ARFCN_XXX, MAX_ARFCN_XXX, MIN_RSSI_GSM, MAX_RSSI_GSM, MIN_RSSI_UMTS, MAX_RSSI_UMTS, MIN_UARFCN, MAX_UARFCN. Renamed KC_CONTENT to SIZE_KC. Renamed CONTENT_TMSI to SIZE_TMSI. Renamed CONTENT_P_TMSI to SIZE_P_TMSI. Renamed SIZE_START_MAX to MAX_START_VALUE.</Comment> </History> <History> <Date Day="27" Month="6" Year="2003"/> <Author>BRY</Author> <Comment>Bookmarks MUST have the exact same name as the constant/parameter, including the caption.</Comment> </History> </PragmasSection> <ConstantsSection> <Description> <Section>Each of these constant values will be used to control the size of an element in a structure. The size parameter will usually denote the number of elements in an array of a specified type. Normally the use of one of these constants will result in a fixed size array declaration, where all elements are used to contain the specified information.</Section> <Section>In case of variable size arrays, a parameter will accompany the declared array, specifying the number of elements actually included/allocated. This parameter is automatically generated when "compiling" this document. This approach is used where it is desirable to allow a dynamic number of elements in a primitive (e.g. when passing lists of information where the worst case number of elements is large or where each element may have considerable size).</Section> <Section>All size constant values will have the prefix SIZE_, which will uniquely link them to this part of the document.</Section> <Section>In general, a size constant determines the number of elements of a given type used to contain data. For strings of digits, this will normally be a number of bytes, with one digit (0-9) contained in each byte. If this encoding is not used, the alternative type of encoding will be explicitly stated at the declaration of the size definition or at the declaration of the parameter using the size definition.</Section> </Description> <Constant> <Alias>BCC_MAX</Alias> <Value ValueType="DEC">7</Value> <Comment>Maximum value of BCC</Comment> </Constant> <Constant> <Alias>SIZE_TMSI</Alias> <Value ValueType="DEC">4</Value> <Comment>Size in bytes of Temporary Mobile Subscriber Identity (TMSI)</Comment> </Constant> <Constant> <Alias>SIZE_P_TMSI</Alias> <Value ValueType="DEC">4</Value> <Comment>Size in bytes of Packet Temporary Mobile Subscriber Identity (P-TMSI)</Comment> </Constant> <Constant> <Alias>CPICH_RSCP_MAX</Alias> <Value ValueType="DEC">-25</Value> <Comment>Maximum value of CPICH RSCPs for a UMTS cell is -25 dBm</Comment> </Constant> <Constant> <Alias>CPICH_RSCP_MIN</Alias> <Value ValueType="DEC">-115</Value> <Comment>Minimum value of CPICH RSCPs for a UMTS cell is -115 dBm</Comment> </Constant> <Constant> <Alias>SIZE_KC</Alias> <Value ValueType="DEC">8</Value> <Comment>Size in bytes of Ciphering Key</Comment> </Constant> <Constant> <Alias>MAX_EQUIVALENT_PLMNS</Alias> <Value ValueType="DEC">5</Value> <Comment>Maximum number of equivalent PLMNs</Comment> </Constant> <Constant> <Alias>MAX_FORBIDDEN_LAI</Alias> <Value ValueType="DEC">10</Value> <Comment>Maximum number of forbidden location areas in a forbidden location area list.</Comment> </Constant> <Constant> <Alias>MAX_GSM_NCELLS</Alias> <Value ValueType="DEC">32</Value> <Comment>Maximum number if GSM neighbour cells when camped on a UMTS cell for dual mode operations (see [3G 25.331]).</Comment> </Constant> <Constant> <Alias>MAX_GSM_NCELL_INDEX</Alias> <Value ValueType="DEC">31</Value> <Comment>Maximum value of a GSM neighbour cell index for indexing a cell in a GSM neighbour cell list when camped on a UMTS cell for dual mode operations.</Comment> </Constant> <Constant> <Alias>MAX_UMTS_NCELLS</Alias> <Value ValueType="DEC">64</Value> <Comment>Maximum number of UMTS FDD neighbour cells on one UARFCN when camped on a GSM cell for dual mode operations (see [3G 05.08]).</Comment> </Constant> <Constant> <Alias>MAX_UMTS_NCELLS_PER_UARFCN</Alias> <Value ValueType="DEC">32</Value> <Comment>Maximum number of UMTS FDD neighbour cells one frequency when camped on a GSM cell for dual mode operations (see [3G 05.08]).</Comment> </Constant> <Constant> <Alias>MAX_UMTS_NCELL_UARFCNS</Alias> <Value ValueType="DEC">3</Value> <Comment>Maximum number of UMTS FDD channels on which neighbour cells can exist</Comment> </Constant> <Constant> <Alias>MAX_UMTS_PRECONFIGURATIONS</Alias> <Value ValueType="DEC">16</Value> <Comment>Maximum number of UMTS pre-configurations</Comment> </Constant> <Constant> <Alias>NCC_MAX</Alias> <Value ValueType="DEC">7</Value> <Comment>Maximum value of NCC cell</Comment> </Constant> <Constant> <Alias>PSC_MAX</Alias> <Value ValueType="HEX">01FF</Value> <Comment>Maximum value of Primary Scrambling Code</Comment> </Constant> <Constant> <Alias>PSC_MIN</Alias> <Value ValueType="HEX">0000</Value> <Comment>Minimum value of Primary Scrambling Code</Comment> </Constant> <Constant> <Alias>SIZE_ACC</Alias> <Value ValueType="DEC">2</Value> <Comment>Number of bytes used to contain the EFACC of the (U)SIM, see [3G 11.11] and [3G 31.102].</Comment> </Constant> <Constant> <Alias>SIZE_AI</Alias> <Value ValueType="DEC">2</Value> <Comment>Number of bytes used to contain Additional Information from EFAD of the (U)SIM, see [3G 11.11] and [3G 31.102].</Comment> </Constant> <Constant> <Alias>SIZE_IMSI_MAX</Alias> <Value ValueType="DEC">15</Value> <Comment>Maximum number of digits in an IMSI</Comment> </Constant> <Constant> <Alias>SIZE_IMSI_MIN</Alias> <Value ValueType="DEC">6</Value> <Comment>Minimum number of digits in an IMSI</Comment> </Constant> <Constant> <Alias>SIZE_LAC</Alias> <Value ValueType="DEC">2</Value> <Comment>Minimum size of location area information</Comment> </Constant> <Constant> <Alias>SIZE_MCC</Alias> <Value ValueType="DEC">3</Value> <Comment>Size in bytes of mobile country code.</Comment> </Constant> <Constant> <Alias>SIZE_MNC_MAX</Alias> <Value ValueType="DEC">3</Value> <Comment>Three digit (byte) mobile network code</Comment> </Constant> <Constant> <Alias>SIZE_MNC_MIN</Alias> <Value ValueType="DEC">2</Value> <Comment>Two digit (byte) mobile network code</Comment> </Constant> <Constant> <Alias>MAX_START_VALUE</Alias> <Value ValueType="HEX">FFFFF</Value> <Comment>Maximum value of START parameter</Comment> </Constant> <Constant> <Alias>SIZE_CK</Alias> <Value ValueType="HEX">0010</Value> <Comment>Number of bytes used to contain the Ciphering Key from EFKEYS of the (U)SIM, see [3G 11.11] and [3G 31.102].</Comment> </Constant> <Constant> <Alias>SIZE_IK</Alias> <Value ValueType="HEX">0010</Value> <Comment>Number of bytes used to contain the Integrity Key from EFKEYS of the (U)SIM, see [3G 11.11] and [3G 31.102].</Comment> </Constant> <Constant> <Alias>SIZE_CN_COMMON_GSM_NAS_SI</Alias> <Value ValueType="HEX">0008</Value> <Comment>Number of bytes used to contain a CN Common GSM NAS System Information IE from a network cell [3G 25.331]</Comment> </Constant> <Constant> <Alias>MAX_UL_SDU</Alias> <Value ValueType="DEC">255</Value> <Comment>Max number of unacknowledged SDUs transferred between RATs.</Comment> </Constant> <Constant> <Alias>MIN_BCD_VALUE</Alias> <Value ValueType="DEC">0</Value> <Comment>Minimum value of a BCD digit according to [3G 24.008].</Comment> </Constant> <Constant> <Alias>MAX_BCD_VALUE</Alias> <Value ValueType="DEC">9</Value> <Comment>Maximum value of a BCD digit according to [3G 24.008].</Comment> </Constant> <Constant> <Alias>MIN_KEY_SEQ_NUM</Alias> <Value ValueType="HEX">00</Value> <Comment>Minimum value of ciphering key sequence number.</Comment> </Constant> <Constant> <Alias>MAX_KEY_SEQ_NUM</Alias> <Value ValueType="HEX">06</Value> <Comment>Maximum value of ciphering key sequence number.</Comment> </Constant> <Constant> <Alias>KEY_SEQ_INVALID</Alias> <Value ValueType="HEX">07</Value> <Comment>Corresponds to ciphering key not available, see [3G 24.008] [3G 11.11] and [3G 31.102].</Comment> </Constant> <Constant> <Alias>MIN_ARFCN_VALUE</Alias> <Value ValueType="DEC">0</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MAX_ARFCN_VALUE</Alias> <Value ValueType="DEC">1023</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MIN_ARFCN_GSM900E_LOW</Alias> <Value ValueType="DEC">0</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MAX_ARFCN_GSM900E_LOW</Alias> <Value ValueType="DEC">124</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MIN_ARFCN_GSM900E_HIGH</Alias> <Value ValueType="DEC">975</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MAX_ARFCN_GSM900E_HIGH</Alias> <Value ValueType="DEC">1023</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MIN_ARFCN_GSM900P</Alias> <Value ValueType="DEC">1</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MAX_ARFCN_GSM900P</Alias> <Value ValueType="DEC">124</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MIN_ARFCN_GSM850</Alias> <Value ValueType="DEC">128</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MAX_ARFCN_GSM850</Alias> <Value ValueType="DEC">251</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MIN_ARFCN_GSM450</Alias> <Value ValueType="DEC">259</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MAX_ARFCN_GSM450</Alias> <Value ValueType="DEC">293</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MIN_ARFCN_GSM480</Alias> <Value ValueType="DEC">306</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MAX_ARFCN_GSM480</Alias> <Value ValueType="DEC">340</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MIN_ARFCN_GSM1800</Alias> <Value ValueType="DEC">512</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MAX_ARFCN_GSM1800</Alias> <Value ValueType="DEC">885</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MIN_ARFCN_GSM1900</Alias> <Value ValueType="DEC">512</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MAX_ARFCN_GSM1900</Alias> <Value ValueType="DEC">810</Value> <Comment>ARFCN range, see [3G 05.05]</Comment> </Constant> <Constant> <Alias>MIN_RSSI_GSM</Alias> <Value ValueType="DEC">-110</Value> <Comment>Minimum GSM RSSI in dBm.</Comment> </Constant> <Constant> <Alias>MAX_RSSI_GSM</Alias> <Value ValueType="DEC">-20</Value> <Comment>Maximum GSM RSSI in dBm.</Comment> </Constant> <Constant> <Alias>MIN_RSSI_UMTS</Alias> <Value ValueType="DEC">-48</Value> <Comment>Minimum UMTS RSSI in 0.5 dBm units.</Comment> </Constant> <Constant> <Alias>MAX_RSSI_UMTS</Alias> <Value ValueType="DEC">0</Value> <Comment>Maximum UMTS RSSI in 0.5 dBm units.</Comment> </Constant> <Constant> <Alias>MIN_UARFCN</Alias> <Value ValueType="HEX">0000</Value> <Comment>UARFCN range, see [3G 25.101]</Comment> </Constant> <Constant> <Alias>MAX_UARFCN</Alias> <Value ValueType="HEX">3FFF</Value> <Comment>UARFCN range, see [3G 25.101]</Comment> </Constant> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="26" Month="12" Year="2002"/> <Author>ALE</Author> <Comment>MAX_UL_SDU item has been added.</Comment> </History> <History> <Date Day="16" Month="1" Year="2003"/> <Author>LOE</Author> <Comment>Maximum size of SDU removed.</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added KC_CONTENT, SIZE_IK, PSC_MIN, PSC_MAX, NCC_MAX, BCC_MAX, CPICH_RSCP_MAX, CPICH_RSCP_MIN, CONTENT_P_TMSI, CONTENT_TMSI</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Added ENABLE_GROUP and COMPATIBILITY_DEFINES to pragmas. Updated some constant descriptions according to review report. Added MIN_BCD_VALUE, MAX_BCD_VALUE, MIN_KEY_SEQ_NUM, MAX_KEY_SEQ_NUM, MIN_ARFCN_XXX, MAX_ARFCN_XXX, MIN_RSSI_GSM, MAX_RSSI_GSM, MIN_RSSI_UMTS, MAX_RSSI_UMTS, MIN_UARFCN, MAX_UARFCN. Renamed KC_CONTENT to SIZE_KC. Renamed CONTENT_TMSI to SIZE_TMSI. Renamed CONTENT_P_TMSI to SIZE_P_TMSI. Renamed SIZE_START_MAX to MAX_START_VALUE.</Comment> </History> <History> <Date Day="27" Month="6" Year="2003"/> <Author>BRY</Author> <Comment>Bookmarks MUST have the exact same name as the constant/parameter, including the caption.</Comment> </History> </ConstantsSection> <PrimitivesSection PrimIDType="BIT16" SAPid="0"> <Description> <Section>This section contains all primitives that are defined for the 8010_152_PS_INCLUDE SAP</Section> </Description> <Primitive> <Description> <Section>This message is here to export to other SAPs using the parameters defined in this document.</Section> </Description> <PrimDef> <Name>PS_EXPORT</Name> <PrimID Direction="UPLINK" Number="0"/> <PrimUsage> <Sender>XX</Sender> <Receiver>PS</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>acc</Name> </ItemLink> <Comment>Access control class</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ad</Name> </ItemLink> <Comment>Administrative data</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>arfcn</Name> </ItemLink> <Comment>GSM channel number</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>arfcn_rssi</Name> </ItemLink> <Comment>GSM channel RSSI measurement</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>bsic</Name> </ItemLink> <Comment>GSM BSIC</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>cn_domain</Name> </ItemLink> <Comment>Core network domain identity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>cpich_ec_n0</Name> </ItemLink> <Comment>UMTS cell measurement value of CPICH Ec/N0</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>cpich_rscp</Name> </ItemLink> <Comment>UMTS cell measurement value of CPICH RSCP</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>est_service</Name> </ItemLink> <Comment>Establisment service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>cs_security_parms</Name> </ItemLink> <Comment>UMTS security parameters</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>equivalent_plmn</Name> </ItemLink> <Comment>Equivalent network identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>equivalent_plmn_list</Name> </ItemLink> <Comment>Container for equivalent PLMN list</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>forbidden_lai</Name> </ItemLink> <Comment>Container for forbidden location area list</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_cell_description</Name> </ItemLink> <Comment>GSM channel number and band specification</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_frequency_band</Name> </ItemLink> <Comment>Frequency band specification</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_ncell_index</Name> </ItemLink> <Comment>GSM neighbour cell index</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_ncell_list</Name> </ItemLink> <Comment>GSM neighbour cell list</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_ncell_measurement</Name> </ItemLink> <Comment>GSM neighbour cell measurement result</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_ncell_results</Name> </ItemLink> <Comment>GSM neighbour cell results</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_key_set</Name> </ItemLink> <Comment>GSM Key Set for Ciphering</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>home_plmn</Name> </ItemLink> <Comment>Home network identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>imsi</Name> </ItemLink> <Comment>Container for a subscriber id</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>k_c</Name> </ItemLink> <Comment>KC</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>k_c_gprs</Name> </ItemLink> <Comment>KC-GPRS</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>key_set</Name> </ItemLink> <Comment>UMTS key set for ciphering and integrity handling</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ksi</Name> </ItemLink> <Comment>UMTS key set identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>lac</Name> </ItemLink> <Comment>Container for location area code</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>lai</Name> </ItemLink> <Comment>Container for location area information</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>loci</Name> </ItemLink> <Comment>Location information</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>llc_mode</Name> </ItemLink> <Comment>LLC mode</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>meas_mode</Name> </ItemLink> <Comment>Measurement mode</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>mem_handle</Name> </ItemLink> <Comment>Memory Handle</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>nas_system_info</Name> </ItemLink> <Comment>NAS system information</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>operation_mode</Name> </ItemLink> <Comment>Supported radio access technologies.</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>p_tmsi</Name> </ItemLink> <Comment>Packet temporary mobile subscriber identity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>peak_throughput</Name> </ItemLink> <Comment>Peak Trhoughput QoS Parameter</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>plmn_id</Name> </ItemLink> <Comment>Container for a GSM MAP network identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ps_loci</Name> </ItemLink> <Comment>Packet switched location information</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ps_security_parms</Name> </ItemLink> <Comment>UMTS security parameters</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>psc</Name> </ItemLink> <Comment>FDD primary scrambling code</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>radio_prio</Name> </ItemLink> <Comment>Radio Priority</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>rac</Name> </ItemLink> <Comment>Routing Area Code</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>rai</Name> </ItemLink> <Comment>Routing Area Identification</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>rat</Name> </ItemLink> <Comment>Radio Access Technology Identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>rel_ind</Name> </ItemLink> <Comment>Local Release Indicator</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>sapi</Name> </ItemLink> <Comment>Service Access Point Identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>search_mode</Name> </ItemLink> <Comment>Search mode for network scan</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>security_info</Name> </ItemLink> <Comment>Security Information</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>selected_plmn</Name> </ItemLink> <Comment>Selected network identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>start_val</Name> </ItemLink> <Comment>UMTS START value</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>sim_type</Name> </ItemLink> <Comment>Subscriber card type</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>tmsi</Name> </ItemLink> <Comment>Temporary mobile subscriber identity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>tx_diversity</Name> </ItemLink> <Comment>UMTS FDD TX diversity indicator</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>uarfcn</Name> </ItemLink> <Comment>UMTS channel number</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>uarfcn_rssi</Name> </ItemLink> <Comment>UMTS channel RSSI measurement</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ul_sdus</Name> </ItemLink> <Comment>List of Unacknowledged SDUs</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>umts_cell_description</Name> </ItemLink> <Comment>Container for cell description information for a UMTS cell</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>umts_ncell_list</Name> </ItemLink> <Comment>UMTS neighbour cell list</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>umts_ncell_measurement</Name> </ItemLink> <Comment>UMTS neighbour cell measurement result</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>umts_ncell_results</Name> </ItemLink> <Comment>UMTS neighbour cell results</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>umts_security_info</Name> </ItemLink> <Comment>UMTS security information</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>service_level</Name> </ItemLink> <Comment>Service Level</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>qos</Name> </ItemLink> <Comment>quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>qos_r97</Name> </ItemLink> <Comment>R97 quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>qos_r99</Name> </ItemLink> <Comment>R99 quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>min_qos</Name> </ItemLink> <Comment>minimum quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>pkt_flow_id</Name> </ItemLink> <Comment>Packet Flow Identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>sdu</Name> </ItemLink> <Comment>Container for a message</Comment> </PrimItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="20" Month="12" Year="2002"/> <Author>ALE</Author> <Comment>"Memory Handle" and "List of Unacknowledged SDUs" have been added.</Comment> </History> <History> <Date Day="20" Month="12" Year="2002"/> <Author>AGR</Author> <Comment>The sdu variable must be the last element in PS_EXPORT.</Comment> </History> <History> <Date Day="11" Month="2" Year="2003"/> <Author>AGR</Author> <Comment>The llc_sapi is renamed to sapi.</Comment> </History> <History> <Date Day="12" Month="2" Year="2003"/> <Author>TBAI</Author> <Comment>Added cell status</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text.</Comment> </History> <History> <Date Day="12" Month="6" Year="2003"/> <Author>BRY</Author> <Comment>Added LLC mode.</Comment> </History> <History> <Date Day="21" Month="7" Year="2003"/> <Author>BRY</Author> <Comment>Changed prim ID to 0x0000 as this is the only allowed multiple defined prim ID value.</Comment> </History> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Added qos, qos_r97, qos_r99, min_qos and pkt_flow_id.</Comment> </History> </Primitive> </PrimitivesSection> <PrimStructElementsSection> <Description> <Section>This section contains all structured elements that are defined for the 8010_152_PS_INCLUDE SAP</Section> </Description> <PrimStructElem> <Description> <Section>This is a container for the contents of the Access Control Class field from the (U)SIM, see [3G 11.11] and [3G 31.102]. The content is a bit-field, and the value definitions must be used with caution. Each value definition identifies one bit in the bit field when applied to the correct element of the acc array, using the defined indexes.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>acc</Name> <Comment>Container for the access control class field from (U)SIM, see [3G 11.11] and [3G 31.102]</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>content</Name> </ItemLink> <Control>[SIZE_ACC]</Control> <Comment>Content of access control class</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Description text updated</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for the contents of the Administrative Data field from the (U)SIM, see [3G 11.11] and [3G 31.102]. It is a complete copy of the contents from the (U)SIM.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>ad</Name> <Comment>Container for the administrative data field from (U)SIM, see [3G 11.11] and [3G 31.102]</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>op</Name> </ItemLink> <Comment>UE operation mode</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ai</Name> </ItemLink> <Control>[SIZE_AI]</Control> <Comment>Additional information</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Description text updated</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for an equivalent PLMN list. Each element in the list specifies a PLMN equivalent to the selected PLMN.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>equivalent_plmn_list</Name> <Comment>Container for equivalent PLMN list</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>equivalent_plmn</Name> </ItemLink> <Control>[0..MAX_EQUIVALENT_PLMNS]</Control> <Comment>Equivalent PLMN</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container holding a list of location areas in which the selection and reselection of cells is known to be forbidden.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>forbidden_lai</Name> <Comment>Container for forbidden location area list</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>lai</Name> </ItemLink> <Control>[1.. MAX_FORBIDDEN_LAI]</Control> <Comment>location area information</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>The mode of operation is a parameter, which can be used to indicate or store information regarding active mode of operation for the protocol stack with regard to radio access technologies.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>gsm_bands</Name> <Comment>GSM bands</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_frequency_band</Name> </ItemLink> <Comment>Frequency band specification</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_band_priority</Name> </ItemLink> <Comment>GSM band priority</Comment> </PrimStructElemItem> <History> <Date Day="31" Month="3" Year="2003"/> <Author>JMA</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This structure holds the BSIC of a GSM cell. The BSIC consists of two 3-bit fields containing the NCC and BCC of a cell.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>bsic</Name> <Comment>GSM BSIC</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ncc</Name> </ItemLink> <Comment>NCC</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>bcc</Name> </ItemLink> <Comment>BCC</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constants NCC_MAX & MIN</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This parameter is used to hold the specification of a GSM channel including its channel number and a frequency band indicator. Since the channel number is not necessarily uniquely mapped to a frequency, it must be interpreted using the frequency band specification given with it. BSIC is included for the cell.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>gsm_cell_description</Name> <Comment>GSM channel number and band specification</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_frequency_band</Name> </ItemLink> <Comment>Band specification</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>arfcn</Name> </ItemLink> <Comment>Channel number</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>bsic</Name> </ItemLink> <Comment>BSIC</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>Contains information related to ciphering for GSM and GPRS.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>gsm_key_set</Name> <Comment>Contains information related to ciphering</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>k_c</Name> </ItemLink> <Comment>KC</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>k_c_gprs</Name> </ItemLink> <Comment>KC-GPRS</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for a list of GSM cells that are neighbours to a cell currently or previously selected.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>gsm_ncell_list</Name> <Comment>GSM neighbour cell list</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_cell_description</Name> </ItemLink> <Control>[1.. MAX_GSM_NCELLS]</Control> <Comment>GSM neighbour cell descriptions</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This parameter contains a measurement result for a single GSM neighbour cell. The cell is identified through the cell description. A status parameter indicates whether the BSIC of the cell has been decoded and found to be a match with the BSIC for the specified cell or not. If a measurement result is available, RSSI is included in the measurement result. An existing measurement is indicated as invalid through the inclusion of a measurement result with the RSSI value absent.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>gsm_ncell_measurement</Name> <Comment>GSM neighbour cell measurement result</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_cell_description</Name> </ItemLink> <Comment>GSM neighbour cell description</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>bsic_valid</Name> </ItemLink> <Comment>BSIC validated</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>arfcn_rssi</Name> </ItemLink> <Comment>Average received signal level</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for a list of measurement results for GSM neighbour cells when camped on a UMTS cell for dual mode purposes.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>gsm_ncell_results</Name> <Comment>GSM neighbour cell results</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_ncell_measurement</Name> </ItemLink> <Control>[1.. MAX_GSM_NCELLS]</Control> <Comment>GSM neighbour cell descriptions</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for a GSM international mobile subscriber identity, also known as the IMSI. It is encoded as a sequence of digits (0-9)</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>imsi</Name> <Comment>Container for a subscriber id</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>identity</Name> </ItemLink> <Control>[SIZE_IMSI_MIN..SIZE_IMSI_MAX]</Control> <Comment>Content of IMSI</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for the GSM ciphering parameters KC and KC-GPRS (see [3G 11.11] and [3G 31.102]). The ksi parameter is named according to UMTS ([3G 31.102]) but is equal to the cksn parameter defined in GSM ([3G 11.11]).</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>k_c</Name> <Comment>Container for GSM ciphering parameter</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>k_c_gprs</Name> <Comment>Container for GPRS ciphering parameter</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>key</Name> </ItemLink> <Control>[SIZE_KC]</Control> <Comment>Ciphering key</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ksi</Name> </ItemLink> <Comment>Ciphering key sequence number</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constant KC_CONTENT</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Renamed KC_CONTENT to SIZE_KC. Changed to use constants for the range definition. Changed to use the ksi parameter.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This parameter is used to return buffered, unacknowledged SDUs from SNDCP/PDCP to UPM. Only NSAPIs that use acknowledged mode LLC transfer and only RBs that use acknowledged mode RLC shall have their SDUs transferred to the new RAT.</Section> <Section>The SDUs are returned as an array of MEM handles.</Section> <Section>In addition to SDUs, the sequence number of the last acknowledged uplink and the sequence number of the next expected downlink SDU SDU is included</Section> <Section>The maximum number of unacknowledged SDUs possible is 255. [3G 23.060, 6.13.1.2] says that the UE must discard all SDUs with sequence numbers older than the eight least significant bits of the PDCP-SNU.</Section> <Section>The sequence numbers below have the full range of an 8-bit integer. It must be noted that the sequence numbers are given as SNDCP N-PDU numbers (see [3G 04.65]), not PDCP N-PDU numbers (see [3G 25.323]). The mapping between the two types is defined in [3G 23.060] as: SNDCP N-PDU sequence number is the lower 8 bit of a PDCP N-PDU sequence number.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>ul_sdus</Name> <Comment>Sequence numbers and mem handles pr. NSAPI</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ul_sequence_number</Name> </ItemLink> <Comment>Sequence number of last unacknowledged uplink SDU</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>dl_sequence_number</Name> </ItemLink> <Comment>Sequence number of last unacknowledged downlink SDU (used by the network)</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>mem_handle</Name> </ItemLink> <Control>PTR [0 .. MAX_UL_SDU]</Control> <Comment>List of unacknowledged uplink SDUs</Comment> </PrimStructElemItem> <History> <Date Day="20" Month="12" Year="2002"/> <Author>ALE</Author> <Comment>Initial.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for location area code. For further information, see [3G 24.008].</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>lac</Name> <Comment>Container for location area code</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>lac_elements</Name> </ItemLink> <Control>[SIZE_LAC]</Control> <Comment>Location area code element</Comment> </PrimStructElemItem> <History> <Date Day="19" Month="2" Year="2003"/> <Author>JMA</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for location area information. For further information, see [3G 24.008], [3G 11.11] and [3G 31.102].</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>lai</Name> <Comment>Container for location area information</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>plmn_id</Name> </ItemLink> <Comment>Network ID</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>lac</Name> </ItemLink> <Comment>Location area code</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for the location information from the (U)SIM. The information is contained in a field as described in [3G11.11] and [3G 31.102].</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>loci</Name> <Comment>Container for location information</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>lai</Name> </ItemLink> <Comment>Location area information</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>tmsi</Name> </ItemLink> <Comment>TMSI</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>The mode of operation is a struct used to inform AS about the radio access technology used. If RAT is GSM then additional info is given.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>operation_mode</Name> <Comment>Supported radio access technologies</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>access_modes</Name> </ItemLink> <Comment>Supported access modes</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_bands</Name> </ItemLink> <Comment>GSM bands</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This message informs NAS of the System Information needed by NAS.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>nas_system_info</Name> <Comment>NAS system information</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>lac</Name> </ItemLink> <Comment>Location area code</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>rac</Name> </ItemLink> <Comment>Routing area code</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>nmo</Name> </ItemLink> <Comment>Network mode of operation</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>attach_detach_allowed</Name> </ItemLink> <Comment>Attach / detach allowed</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>t3212</Name> </ItemLink> <Comment>Periodic updating timer</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="1" Year="2003"/> <Author>JMA</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for the location information for the packet switched domain from the (U)SIM. The information is contained in a field as described in [3G 11.11] and [3G 31.102].</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>ps_loci</Name> <Comment>Container for packet switched location information</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>rai</Name> </ItemLink> <Comment>Routing area identification</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>p_tmsi</Name> </ItemLink> <Comment>P-TMSI</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>Used to contain a 32-bit Packet Temporary Mobile Subscriber Identity (P-TMSI). The formatting of this parameter is like the air interface transmission order, see [3G 24.008], and the (U)SIM format, see [3G 11.11] and [3G 31.102].</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>p_tmsi</Name> <Comment>Container for P-TMSI</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>content_p_tmsi</Name> </ItemLink> <Control>[SIZE_P_TMSI]</Control> <Comment>Content of P-TMSI</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constant CONTENT_P_TMSI</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text. Renamed CONTENT_P_TMSI to SIZE_P_TMSI.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for a GSM MAP network identifier. The network identifier consists of a Mobile Country Code and Mobile Network Code. Encoding of the country and network codes is as sequences of digits (0-9).</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>plmn_id</Name> <Comment>Container for a GSM MAP network identifier</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>selected_plmn</Name> <Comment>Selected network identifier</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>home_plmn</Name> <Comment>Home network identifier</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>equivalent_plmn</Name> <Comment>Equivalent network identifier</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>mcc</Name> </ItemLink> <Control>[SIZE_MCC]</Control> <Comment>Mobile country code</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>mnc</Name> </ItemLink> <Control>[SIZE_MNC_MIN..SIZE_MNC_MAX]</Control> <Comment>Mobile network code</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text and added values section.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for Routing Area Identification (RAI). For further information, see [3G 24.008], [3G 11.11] and [3G 31.102].</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>rai</Name> <Comment>Container for packet switched routing area identification</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>lai</Name> </ItemLink> <Comment>Location area information</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>rac</Name> </ItemLink> <Comment>Routing area code</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>Contains information related to ciphering and integrity protection. The structure may contain information for use in both GSM/GPRS and UMTS, as well as for both CN domains. In case (U)SIM is present the security information is loaded from USIM.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>security_info</Name> <Comment>Contains information related to ciphering and integrity protection.</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>sim_type</Name> </ItemLink> <Comment>SIM type</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>gsm_key_set</Name> </ItemLink> <Comment>GSM specific security information</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>umts_security_info</Name> </ItemLink> <Comment>UMTS specific security information</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Made sim_type a separate type.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for a service data unit. It consists of a length field specifying the size of the message in the container, an offset specifying where inside the included data array the message starts and a data array holding the message. The array has a default size of one byte, but in reality this is a variable length structure. Only use as the last element in a primitive, and allocate memory using SDU allocation routine.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>sdu</Name> <Comment>Container for a message</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>l_buf</Name> </ItemLink> <Comment>Length in bits</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>o_buf</Name> </ItemLink> <Comment>Offset in bits</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>buf</Name> </ItemLink> <Control>[1]</Control> <Comment>Message content</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="16" Month="1" Year="2003"/> <Author>LOE</Author> <Comment>Default length set to one byte</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>Used to contain a 32-bit Temporary Mobile Subscriber Identity (TMSI). The formatting of this parameter is like the air interface transmission order, see [3G 24.008], and the (U)SIM format, see [3G 11.11] and [3G 31.102].</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>tmsi</Name> <Comment>Container for TMSI</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>content_tmsi</Name> </ItemLink> <Control>[SIZE_TMSI]</Control> <Comment>Content of TMSI</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constant CONTENT_TMSI</Comment> </History> <History> <Date Day="3" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for information describing the attributes of a cell in a UMTS network. The included attributes are the cell frequency (frequency channel number), the primary scrambling code and diversity information.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>umts_cell_description</Name> <Comment>Container for cell description information for a UMTS cell</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>uarfcn</Name> </ItemLink> <Comment>UMTS Channel number</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>psc</Name> </ItemLink> <Comment>UMTS Primary scrambling code</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>tx_diversity</Name> </ItemLink> <Comment>UMTS TX diversity indicator</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>Contains ciphering and integrity keys for a CN domain. The order of bits is specified in [3G 31.102]: the MSB is the MSB of the first byte in the byte array and the LSB is the LSB of the last byte in the byte array.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>key_set</Name> <Comment>Ciphering and integrity keys for a CN domain</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ksi</Name> </ItemLink> <Comment>Key set identifier</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ciphering_key</Name> </ItemLink> <Control>[SIZE_CK]</Control> <Comment>Ciphering key</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>integrity_key</Name> </ItemLink> <Control>[SIZE_IK]</Control> <Comment>Integrity protection key</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for a list of UMTS cells that are neighbours to a cell currently or previously selected.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>umts_ncell_list</Name> <Comment>UMTS neighbour cell list</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>umts_cell_description</Name> </ItemLink> <Control>[1.. MAX_UMTS_NCELLS]</Control> <Comment>UMTS neighbour cell descriptions</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This parameter contains a measurement result for a single UMTS neighbour cell. The cell is identified through the cell description. If no measurements are available for the cell (e.g. it was not found), measurements will be absent from the structure.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>umts_ncell_measurement</Name> <Comment>UMTS neighbour cell measurement result</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>psc</Name> </ItemLink> <Comment>Primary scrambling code</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>cell_status</Name> </ItemLink> <Comment>Cell suitability status</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>cpich_rscp</Name> </ItemLink> <Comment>CPICH RSCP</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>cpich_ec_n0</Name> </ItemLink> <Comment>CPICH Ec/N0</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is a container for a list of measurement results for UMTS neighbour cells when camped on a GSM cell for dual mode purposes.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>umts_ncell_results</Name> <Comment>UMTS neighbour cell results</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>uarfcn</Name> </ItemLink> <Comment>Channel</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>uarfcn_rssi</Name> </ItemLink> <Comment>Channel RSSI</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>umts_ncell_measurement</Name> </ItemLink> <Control>[1..MAX_UMTS_NCELLS_PER_UARFCN]</Control> <Comment>Cell measurements</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>Contains information related to ciphering and integrity protection for both CN domains. In case USIM is present the security information is loaded from USIM.</Section> <Section>In case only a SIM card is a present, UMTS cipher key and integrity key are derived using conversion functions c4 and c5 [[3G 33.102, 6.8.2.4]. The conversion functions c4 and c5 are implemented in NAS. In this case THRESHOLD value shall be set to default value (all ones) while START values are marked as "not present". If present the START values will be ignored by RRC. The START values are maintained solely by the RRC entity.</Section> <Section>In case neither USIM nor SIM is present the cipher keys and integrity keys are marked as "not present". START values are initialised to zero and THRESHOLD value is set to default value (all ones). This is according to [3G 25.331, 8.1.3.6].</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>umts_security_info</Name> <Comment>Contains information related to UMTS ciphering and integrity protection.</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>threshold</Name> </ItemLink> <Comment>THRESHOLD value</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>cs_security_parms</Name> </ItemLink> <Comment>UMTS circuit switched security parameters</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ps_security_parms</Name> </ItemLink> <Comment>UMTS packet switched security parameters</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated and minor typing error</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Renamed SIZE_START_MAX to MAX_START_VALUE.</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>Contains parameters related to ciphering and integrity protection for CS/PS domain.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>cs_security_parms</Name> <Comment>Contains parameters related to ciphering and integrity protection for CS domain.</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>ps_security_parms</Name> <Comment>Contains parameters related to ciphering and integrity protection for PS domain.</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>key_set</Name> </ItemLink> <Comment>Ciphering and integrity keys</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="OPTIONAL"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>start_val</Name> </ItemLink> <Comment>Start value (PS)</Comment> </PrimStructElemItem> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>The purpose of this parameter is to specify the requested QoS parameters for a PDP context. QoS parameters may be either R97 or R99 compatible but not both, so this data type is represented as a union.</Section> </Description> <PrimStructElemDef Type="UNION"> <Name>qos</Name> <Comment>quality of service</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>qos_not_present</Name> </ItemLink> <UnionTag> <Name>is_qos_not_present</Name> </UnionTag> <Comment>QoS parameters absent</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>qos_r97</Name> </ItemLink> <UnionTag> <Name>is_R97</Name> </UnionTag> <Comment>R97 QoS parameters</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>qos_r99</Name> </ItemLink> <UnionTag> <Name>is_R99</Name> </UnionTag> <Comment>R99 QoS parameters</Comment> </PrimStructElemItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>The purpose of this parameter is to specify the minimum QoS parameters for a PDP context. QoS parameters may be either R97 or R99 compatible but not both, so this data type is represented as a union.</Section> </Description> <PrimStructElemDef Type="UNION"> <Name>min_qos</Name> <Comment>quality of service</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>min_qos_not_present</Name> </ItemLink> <UnionTag> <Name>is_min_qos_not_present</Name> </UnionTag> <Comment>QoS parameters absent</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>qos_r97</Name> </ItemLink> <UnionTag> <Name>is_min_R97</Name> </UnionTag> <Comment>R97 QoS parameters</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>qos_r99</Name> </ItemLink> <UnionTag> <Name>is_min_R99</Name> </UnionTag> <Comment>R99 QoS parameters</Comment> </PrimStructElemItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the ETSI release 97 version of the QoS parameters.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>qos_r97</Name> <Comment>quality of service R97</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>delay</Name> </ItemLink> <Comment>delay class</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>relclass</Name> </ItemLink> <Comment>reliability class</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>peak</Name> </ItemLink> <Comment>peak throughput</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>preced</Name> </ItemLink> <Comment>precedence class</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>mean</Name> </ItemLink> <Comment>mean throughput</Comment> </PrimStructElemItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>qos_r99</Name> <Comment>quality of service R99</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>tc</Name> </ItemLink> <Comment>traffic class; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>order</Name> </ItemLink> <Comment>delivery order; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>del_err_sdu</Name> </ItemLink> <Comment>delivery of erroneous SDU; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>max_sdu</Name> </ItemLink> <Comment>max SDU size; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>max_rate_ul</Name> </ItemLink> <Comment>max bit-rate uplink; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>max_rate_dl</Name> </ItemLink> <Comment>max bit-rate downlink; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ber</Name> </ItemLink> <Comment>residual BER; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>sdu_err_ratio</Name> </ItemLink> <Comment>SDU error ratio; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>xfer_delay</Name> </ItemLink> <Comment>transfer delay; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>handling_pri</Name> </ItemLink> <Comment>traffic handling priority; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>guar_br_ul</Name> </ItemLink> <Comment>guaranteed bit-rate uplink; R99 / UMTS</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>guar_br_dl</Name> </ItemLink> <Comment>guaranteed bit-rate downlink; R99 / UMTS</Comment> </PrimStructElemItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This parameter is used for specifying error ratios in pseudo-human-readable format (derived from [3G 27.007, 10.1.6]. It is used by applications for specifying bit error rates etc. through ACI.</Section> <Section>The format is MANT * 10-EXP. Note that the exponent is sign-inverted.</Section> <Section>Example: To get 5 * 10-3 (from application input value 5E3), the values must be ratio_mant=5 and ratio_exp=3.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>sdu_err_ratio</Name> <Comment>SDU error ratio</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>ber</Name> <Comment>Residual bit error ratio</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ratio_mant</Name> </ItemLink> <Comment>mantissa</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>ratio_exp</Name> </ItemLink> <Comment>exponent</Comment> </PrimStructElemItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimStructElem> </PrimStructElementsSection> <PrimBasicElementsSection> <Description> <Section>This section contains all basic elements that are defined for the 8010_152_PS_INCLUDE SAP</Section> </Description> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the requested QoS parameters for a PDP context. QoS parameters may be either R97 or R99 compatible but not both, so this data type is represented as a union.</Section> </Description> <PrimBasicElemDef> <Name>qos_not_present</Name> <Type>U32</Type> <Comment>QoS parameters absent. From nas_include sap</Comment> </PrimBasicElemDef> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Added not_present controller value. From nas_include sap</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This information element indicates the Packet Flow Identifier for a Packet Flow Context.</Section> </Description> <PrimBasicElemDef> <Name>pkt_flow_id</Name> <Type>U16</Type> <Comment>packet flow identifier</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_pkt_flow_id</Name> </ValuesLink> <History> <Date Day="8" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Moving pkt_flow_id from nas_include to ps_include sap.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the minimum QoS parameters for a PDP context. QoS parameters may be either R97 or R99 compatible but not both, so this data type is represented as a union.</Section> </Description> <PrimBasicElemDef> <Name>min_qos_not_present</Name> <Type>U32</Type> <Comment>QoS parameters absent</Comment> </PrimBasicElemDef> <History> <Date Day="7" Month="4" Year="2003"/> <Author>MVJ</Author> <Comment>Initial</Comment> </History> <History> <Date Day="21" Month="7" Year="2003"/> <Author>MVJ</Author> <Comment>Added not_present controller value.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the ETSI release 97 version of the QoS parameters.</Section> </Description> <PrimBasicElemDef> <Name>delay</Name> <Type>U8</Type> <Comment>delay class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_delay</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the ETSI release 97 version of the QoS parameters.</Section> </Description> <PrimBasicElemDef> <Name>relclass</Name> <Type>U8</Type> <Comment>reliability class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_relclass</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the ETSI release 97 version of the QoS parameters.</Section> </Description> <PrimBasicElemDef> <Name>peak</Name> <Type>U8</Type> <Comment>peak throughput</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_peak</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the ETSI release 97 version of the QoS parameters.</Section> </Description> <PrimBasicElemDef> <Name>preced</Name> <Type>U8</Type> <Comment>precedence class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_preced</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the ETSI release 97 version of the QoS parameters.</Section> </Description> <PrimBasicElemDef> <Name>mean</Name> <Type>U8</Type> <Comment>mean throughput</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_mean</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>tc</Name> <Type>U8</Type> <Comment>traffic class; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_tc</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>order</Name> <Type>U8</Type> <Comment>delivery order; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_order</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>del_err_sdu</Name> <Type>U8</Type> <Comment>delivery of erroneous SDU; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_del_err_sdu</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>max_sdu</Name> <Type>U16</Type> <Comment>max SDU size; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_max_sdu</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>max_rate_ul</Name> <Type>U16</Type> <Comment>max bit-rate uplink; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_max_rate_ul</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>max_rate_dl</Name> <Type>U16</Type> <Comment>max bit-rate downlink; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_max_rate_dl</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>xfer_delay</Name> <Type>U16</Type> <Comment>transfer delay; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_xfer_delay</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>handling_pri</Name> <Type>U8</Type> <Comment>traffic handling priority; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_handling_pri</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>guar_br_ul</Name> <Type>U16</Type> <Comment>guaranteed bit-rate uplink; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_guar_br_ul</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. This structure contains the 3GPP release 99 version of the QoS parameters.</Section> <Section>The parameter "max SDU size" is passed on this SAP as an ordinary number of octets [0; 1520], which is then converted to the equivalent air message octet value by SM. The "max SDU size" parameter is encoded as follows:</Section> <Section>0 is subscribed</Section> <Section>10 - 1500 octets map to the values 1 - 150 (effectively divide by 10 and round: ((size / 10)()</Section> <Section>1502, 1510, 1520 octets are coded as 151, 152, and 153, respectively.</Section> <Section>Similarly, the 4 bit-rate parameters "max_rate_ul", "max_rate_dl", "guar_br_ul", and "guar_br_dl" are passed as ordinary numbers [0; 8640] (kbps); they are then converted by SM using the following rule:</Section> <Section>0 is subscribed</Section> <Section>1-63 kbps map to 1-63, 1 kbps granularity;</Section> <Section>64-568 kbps are coded as 64-127 (((bit-rate / 8)( + (64 - 8)), granularity 8kbps;</Section> <Section>576-8640 kbps are coded as 128-254 (((bit-rate / 64)( + (128 - 9)), granularity 64kbps;</Section> <Section>0 kbps maps to the value 255 in [3G 24.008], but is not possible to specify on this interface.</Section> <Section>The guaranteed bit-rate parameters "guar_br_ul" and "guar_br_dl" are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>The "transfer delay" parameter is coded according to the following rule:</Section> <Section>0 is subscribed;</Section> <Section>10-150ms map to 1-15, (((value / 10)( );</Section> <Section>200-950ms are coded as 16-31, (((value / 50)( + (16 - 4));</Section> <Section>1000-4000ms are coded as 32-62, (((value / 100)( + (32 - 10));</Section> <Section>63 is reserved.</Section> <Section>The transfer delay parameter and guaranteed bit-rate parameters are ignored if traffic class (tc) is Interactive or Background class.</Section> <Section>Similarly, the transfer handling priority parameter is ignored if the traffic class (tc) is Conversation, Streaming, or Background class.</Section> <Section>NOTE: The parameter values for traffic class (tc), delivery order (order) and delivery of erroneous SDU (del_err_sdu) are not equal for 24.008 and 27.007 3GPP specs. The parameter values are taken from 27.007 and SM converts to the equivalent air interface values.</Section> </Description> <PrimBasicElemDef> <Name>guar_br_dl</Name> <Type>U16</Type> <Comment>guaranteed bit-rate downlink; R99 / UMTS</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_guar_br_dl</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used for specifying error ratios in pseudo-human-readable format (derived from [3G 27.007, 10.1.6]. It is used by applications for specifying bit error rates etc. through ACI.</Section> <Section>The format is MANT * 10-EXP. Note that the exponent is sign-inverted.</Section> <Section>Example: To get 5 * 10-3 (from application input value 5E3), the values must be ratio_mant=5 and ratio_exp=3.</Section> </Description> <PrimBasicElemDef> <Name>ratio_mant</Name> <Type>U8</Type> <Comment>mantissa</Comment> </PrimBasicElemDef> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used for specifying error ratios in pseudo-human-readable format (derived from [3G 27.007, 10.1.6]. It is used by applications for specifying bit error rates etc. through ACI.</Section> <Section>The format is MANT * 10-EXP. Note that the exponent is sign-inverted.</Section> <Section>Example: To get 5 * 10-3 (from application input value 5E3), the values must be ratio_mant=5 and ratio_exp=3.</Section> </Description> <PrimBasicElemDef> <Name>ratio_exp</Name> <Type>U8</Type> <Comment>exponent</Comment> </PrimBasicElemDef> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section/> </Description> <PrimBasicElemDef> <Name>sgsn_rel</Name> <Type>U8</Type> <Comment>sgsn release version</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_sgsn_rel</Name> </ValuesLink> <History> <Date Day="28" Month="04" Year="2004"/> <Author/> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for the contents of the Access Control Class field from the (U)SIM, see [3G 11.11] and [3G 31.102]. The content is a bit-field, and the value definitions must be used with caution. Each value definition identifies one bit in the bit field when applied to the correct element of the acc array, using the defined indexes.</Section> </Description> <PrimBasicElemDef> <Name>content</Name> <Type>U8</Type> <Comment>Content of access control class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_content</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Description text updated</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The access modes is a parameter, which can be used to indicate or store information regarding active mode of operation for the protocol stack with regard to radio access technologies.</Section> </Description> <PrimBasicElemDef> <Name>access_modes</Name> <Type>U8</Type> <Comment>Supported access modes.</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_access_modes</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for the contents of the Administrative Data field from the (U)SIM, see [3G 11.11] and [3G 31.102]. It is a complete copy of the contents from the (U)SIM.</Section> </Description> <PrimBasicElemDef> <Name>op</Name> <Type>U8</Type> <Comment>UE operation mode</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Description text updated</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for the contents of the Administrative Data field from the (U)SIM, see [3G 11.11] and [3G 31.102]. It is a complete copy of the contents from the (U)SIM.</Section> </Description> <PrimBasicElemDef> <Name>ai</Name> <Type>U8</Type> <Comment>Additional information</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Description text updated</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter contains a measured value of RSSI for a GSM channel.</Section> </Description> <PrimBasicElemDef> <Name>arfcn_rssi</Name> <Type>S8</Type> <Comment>GSM channel RSSI measurement</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_arfcn_rssi</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Changed to use constants for the range</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter indicated whether or not attach and detach is allowed.</Section> </Description> <PrimBasicElemDef> <Name>attach_detach_allowed</Name> <Type>U8</Type> <Comment>Attach/detach allowed</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_attach_detach_allowed</Name> </ValuesLink> <History> <Date Day="1" Month="4" Year="2003"/> <Author>JMA</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter type may be used in order to indicate the camped status of a network cell. The cell is either suitable or acceptable (see [3G 25.304])</Section> </Description> <PrimBasicElemDef> <Name>service_level</Name> <Type>U8</Type> <Comment>Cell service level</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_service_level</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="12" Month="1" Year="2003"/> <Author>TBAI</Author> <Comment>Moved from UMTS include to this document and values are renamed</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used to indicate the core network domain identity for an element or a message. The domain identity either indicates that an element belongs to the Circuit Switched (CS) domain, Packet Switched (PS) domain, or that the domain is not important for the element [3G 25.331].</Section> </Description> <PrimBasicElemDef> <Name>cn_domain</Name> <Type>U8</Type> <Comment>Core network domain identity</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_cn_domain</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used in order to pass a measurement of CPICH Ec/N0 for a UMTS cell.</Section> </Description> <PrimBasicElemDef> <Name>cpich_ec_n0</Name> <Type>S8</Type> <Comment>UMTS cell measurement value of CPICH Ec/N0</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_cpich_ec_n0</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Changed to use constants for the range</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used in order to pass a measurement of CPICH RSCP for a UMTS cell.</Section> </Description> <PrimBasicElemDef> <Name>cpich_rscp</Name> <Type>S8</Type> <Comment>UMTS cell measurement value of CPICH RSCP</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_cpich_rscp</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added CPICH_RSCP_MIN & MAX to constants</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a service used by NAS in order to indicate to AS which type of call is requested. In a MO call, it is always send in a MMCM_ESTABLISH_REQ, or in a MMCM_SYNC_REQ. In the MT case, the establishment service is always sent in the MMCM_SYNC_REQ to indicate the service type.</Section> <Section>For an MT call, or if the establishment service has to be changed during the MO call (i.e. if the requested service cannot be obtained from the network), it is sent in an RRC_SYNC_REQ.</Section> </Description> <PrimBasicElemDef> <Name>est_service</Name> <Type>U8</Type> <Comment>Establishment service requested</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_est_service</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>initial</Comment> </History> <History> <Date Day="31" Month="1" Year="2002"/> <Author>KBS</Author> <Comment>SERVICE EMERG defines (call_prio removed)</Comment> </History> <History> <Date Day="3" Month="2" Year="2003"/> <Author>KBS</Author> <Comment>Fetched from MMCM and RRC SAP</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a specification of a GSM absolute radio frequency channel number. The channel number can be translated into a frequency using rules set up in [3G 05.05]. Note that the channel numbers for GSM1800 and GSM1900 overlap, which means that it is necessary to know which band the channel number belongs to in the overlapping range (see 4.18).</Section> </Description> <PrimBasicElemDef> <Name>arfcn</Name> <Type>U16</Type> <Comment>GSM channel number</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_arfcn</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="3" Month="1" Year="2003"/> <Author>ALE</Author> <Comment>ARFCN_GSM850_MIN->ARFCN_GSM850_MAX</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Changed values section to use constants and ranges</Comment> </History> <History> <Date Day="24" Month="3" Year="2003"/> <Author>CSH</Author> <Comment>Multiple ranges out commented due to error in generated val files.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The band priority is a parameter, which hold the band priority, i.e. which band the UE should regarding active mode of operation for the protocol stack with regard to radio access technologies.</Section> </Description> <PrimBasicElemDef> <Name>gsm_band_priority</Name> <Type>U16</Type> <Comment>GSM band priority</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_gsm_band_priority</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This structure holds the BSIC of a GSM cell. The BSIC consists of two 3-bit fields containing the NCC and BCC of a cell.</Section> </Description> <PrimBasicElemDef> <Name>ncc</Name> <Type>U8</Type> <Comment>NCC</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_ncc</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constants NCC_MAX & MIN</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This structure holds the BSIC of a GSM cell. The BSIC consists of two 3-bit fields containing the NCC and BCC of a cell.</Section> </Description> <PrimBasicElemDef> <Name>bcc</Name> <Type>U8</Type> <Comment>BCC</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_bcc</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constants NCC_MAX & MIN</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used to specify which frequency band a channel number belongs to or which frequency bands are supported.</Section> </Description> <PrimBasicElemDef> <Name>gsm_frequency_band</Name> <Type>U16</Type> <Comment>Frequency band specification</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_gsm_frequency_band</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="13" Month="8" Year="2003"/> <Author>JMA</Author> <Comment>GSM1800/1900 value corrected.</Comment> </History> <History> <Date Day="15" Month="10" Year="2003"/> <Author>LOE</Author> <Comment>Added a "band not set" value</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is an index number referring to an element in a GSM neighbour cell list (see 4.21). It identifies a single entry in the list for an operation in the context in which the index is used.</Section> </Description> <PrimBasicElemDef> <Name>gsm_ncell_index</Name> <Type>U8</Type> <Comment>GSM neighbour cell index</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_gsm_ncell_index</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter contains a measurement result for a single GSM neighbour cell. The cell is identified through the cell description. A status parameter indicates whether the BSIC of the cell has been decoded and found to be a match with the BSIC for the specified cell or not. If a measurement result is available, RSSI is included in the measurement result. An existing measurement is indicated as invalid through the inclusion of a measurement result with the RSSI value absent.</Section> </Description> <PrimBasicElemDef> <Name>bsic_valid</Name> <Type>U8</Type> <Comment>BSIC validated</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_bsic_valid</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for a GSM international mobile subscriber identity, also known as the IMSI. It is encoded as a sequence of digits (0-9)</Section> </Description> <PrimBasicElemDef> <Name>identity</Name> <Type>U8</Type> <Comment>Content of IMSI</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for the GSM ciphering parameters KC and KC-GPRS (see [3G 11.11] and [3G 31.102]). The ksi parameter is named according to UMTS ([3G 31.102]) but is equal to the cksn parameter defined in GSM ([3G 11.11]).</Section> </Description> <PrimBasicElemDef> <Name>key</Name> <Type>U8</Type> <Comment>Ciphering key</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constant KC_CONTENT</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Renamed KC_CONTENT to SIZE_KC. Changed to use constants for the range definition. Changed to use the ksi parameter.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used to return buffered, unacknowledged SDUs from SNDCP/PDCP to UPM. Only NSAPIs that use acknowledged mode LLC transfer and only RBs that use acknowledged mode RLC shall have their SDUs transferred to the new RAT.</Section> <Section>The SDUs are returned as an array of MEM handles.</Section> <Section>In addition to SDUs, the sequence number of the last acknowledged uplink and the sequence number of the next expected downlink SDU SDU is included</Section> <Section>The maximum number of unacknowledged SDUs possible is 255. [3G 23.060, 6.13.1.2] says that the UE must discard all SDUs with sequence numbers older than the eight least significant bits of the PDCP-SNU.</Section> <Section>The sequence numbers below have the full range of an 8-bit integer. It must be noted that the sequence numbers are given as SNDCP N-PDU numbers (see [3G 04.65]), not PDCP N-PDU numbers (see [3G 25.323]). The mapping between the two types is defined in [3G 23.060] as: SNDCP N-PDU sequence number is the lower 8 bit of a PDCP N-PDU sequence number.</Section> </Description> <PrimBasicElemDef> <Name>ul_sequence_number</Name> <Type>U8</Type> <Comment>Sequence number of last unacknowledged uplink SDU</Comment> </PrimBasicElemDef> <History> <Date Day="20" Month="12" Year="2002"/> <Author>ALE</Author> <Comment>Initial.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used to return buffered, unacknowledged SDUs from SNDCP/PDCP to UPM. Only NSAPIs that use acknowledged mode LLC transfer and only RBs that use acknowledged mode RLC shall have their SDUs transferred to the new RAT.</Section> <Section>The SDUs are returned as an array of MEM handles.</Section> <Section>In addition to SDUs, the sequence number of the last acknowledged uplink and the sequence number of the next expected downlink SDU SDU is included</Section> <Section>The maximum number of unacknowledged SDUs possible is 255. [3G 23.060, 6.13.1.2] says that the UE must discard all SDUs with sequence numbers older than the eight least significant bits of the PDCP-SNU.</Section> <Section>The sequence numbers below have the full range of an 8-bit integer. It must be noted that the sequence numbers are given as SNDCP N-PDU numbers (see [3G 04.65]), not PDCP N-PDU numbers (see [3G 25.323]). The mapping between the two types is defined in [3G 23.060] as: SNDCP N-PDU sequence number is the lower 8 bit of a PDCP N-PDU sequence number.</Section> </Description> <PrimBasicElemDef> <Name>dl_sequence_number</Name> <Type>U8</Type> <Comment>Sequence number of last unacknowledged downlink SDU (used by the network)</Comment> </PrimBasicElemDef> <History> <Date Day="20" Month="12" Year="2002"/> <Author>ALE</Author> <Comment>Initial.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The parameter gives the LLC mode for a SAPI.</Section> </Description> <PrimBasicElemDef> <Name>llc_mode</Name> <Type>U8</Type> <Comment>LLC mode</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_llc_mode</Name> </ValuesLink> <History> <Date Day="12" Month="6" Year="2003"/> <Author>BRY</Author> <Comment>Initial version</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for location area code. For further information, see [3G 24.008].</Section> </Description> <PrimBasicElemDef> <Name>lac_elements</Name> <Type>U8</Type> <Comment>Location area code element</Comment> </PrimBasicElemDef> <History> <Date Day="19" Month="2" Year="2003"/> <Author>JMA</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used to indicate the mode in which measurements are to be made for neighbour cells.</Section> </Description> <PrimBasicElemDef> <Name>meas_mode</Name> <Type>U8</Type> <Comment>Measurement mode</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_meas_mode</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>LOE</Author> <Comment>Initial</Comment> </History> <History> <Date Day="25" Month="2" Year="2003"/> <Author>TBAI</Author> <Comment>Moved from DRRC SAP to this document</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This handle is returned by the mem_alloc function, see [TI 8010.112 MEM SAP]. The handle is used to refer to a memory allocation in the interlayer communication.</Section> </Description> <PrimBasicElemDef> <Name>mem_handle</Name> <Type>U32</Type> <Comment>Memory handle</Comment> </PrimBasicElemDef> <History> <Date Day="20" Month="12" Year="2002"/> <Author>ALE</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>A GPRS MS operating in mode A or B a in network that operates in mode I, uses the combined GMM specific procedures in place of the MM specific procedures, so all conditions describing when to trigger a MM specific procedure (see [GSM 04.08, sections 4.3 and 4.4]) shall not apply.</Section> <Section>A GPRS MS operating in mode A or B in a network that operates in mode I should not use any MM timers relating to MM specific procedures, (e.g. T3210, T3211, T3212, T3213) expect in some error and abnormal cases.</Section> <Section>If the network operates in mode II or III, GPRS MSs that operate in mode A or B and wish to be or are simultaneously IMSI attached for GPRS and non-GPRS services, shall use the MM specific procedures listed in [GSM 04.08, sections 4.3 and 4.4] and the GMM specific procedures listed in [GSM 04.08, sections 4.7.3, 4.7.4 and 4.7.5].</Section> </Description> <PrimBasicElemDef> <Name>nmo</Name> <Type>U8</Type> <Comment>Network mode of operation</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_nmo</Name> </ValuesLink> <History> <Date Day="28" Month="1" Year="2003"/> <Author>JMA</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Processed minor review comments</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a parameter used in RR, RCM and RRC network scan request. The parameter defines if it is an automatic or manual network scan. During automatic scan, cell suitability criteria are checked (with the exception of network specific parameters (network id and location area information), and only suitable cells indicated. In manual mode, only core network type is validated.</Section> </Description> <PrimBasicElemDef> <Name>search_mode</Name> <Type>U8</Type> <Comment>Search mode for network scan</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_search_mode</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Used to contain a 32-bit Packet Temporary Mobile Subscriber Identity (P-TMSI). The formatting of this parameter is like the air interface transmission order, see [3G 24.008], and the (U)SIM format, see [3G 11.11] and [3G 31.102].</Section> </Description> <PrimBasicElemDef> <Name>content_p_tmsi</Name> <Type>U8</Type> <Comment>Content of P-TMSI</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constant CONTENT_P_TMSI</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text. Renamed CONTENT_P_TMSI to SIZE_P_TMSI.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Used to contain Peak Throughput.</Section> </Description> <PrimBasicElemDef> <Name>peak_throughput</Name> <Type>U16</Type> <Comment>Peak throughput QoS parameter</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_peak</Name> </ValuesLink> <History> <Date Day="3" Month="12" Year="2002"/> <Author>NIA</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter informs NAS of the periodic updating timer.</Section> </Description> <PrimBasicElemDef> <Name>t3212</Name> <Type>U8</Type> <Comment>Periodic updating timer</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_t3212</Name> </ValuesLink> <History> <Date Day="1" Month="4" Year="2003"/> <Author>JMA</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for a GSM MAP network identifier. The network identifier consists of a Mobile Country Code and Mobile Network Code. Encoding of the country and network codes is as sequences of digits (0-9).</Section> </Description> <PrimBasicElemDef> <Name>mcc</Name> <Type>U8</Type> <Comment>Mobile country code</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_mcc</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text and added values section.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for a GSM MAP network identifier. The network identifier consists of a Mobile Country Code and Mobile Network Code. Encoding of the country and network codes is as sequences of digits (0-9).</Section> </Description> <PrimBasicElemDef> <Name>mnc</Name> <Type>U8</Type> <Comment>Mobile network code</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_mnc</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text and added values section.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter can be used to identify a radio access technology within a given context.</Section> </Description> <PrimBasicElemDef> <Name>rat</Name> <Type>U8</Type> <Comment>Radio access technology</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_rat</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of the radio priority information element is to specify the priority level that the MS shall use at the lower layers for transmission of data related to a PDP context or for mobile originated SMS transmission. All other values are interpreted as priority level 4 by this version of the protocol. See [3G 24.008, 10.5.7.2].</Section> <Section>NOTE. Due to the lower layers, the enumeration starts from zero. This gives an offset by one compared to the values in [3G 24.008, 10.5.7.2].</Section> </Description> <PrimBasicElemDef> <Name>radio_prio</Name> <Type>U8</Type> <Comment>Radio priority</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_radio_prio</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial.</Comment> </History> <History> <Date Day="11" Month="2" Year="2003"/> <Author>AGR</Author> <Comment>The enumeration now starts from 0.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used in GSM/GPRS only. This parameter is used to indicate whether a deactivation shall be performed locally or not. In case of local deactivation (REL_IND_YES), no LL_XID_REQ is sent.</Section> </Description> <PrimBasicElemDef> <Name>rel_ind</Name> <Type>U8</Type> <Comment>Local Release Indicator</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_rel_ind</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for Routing Area Code (RAC). The RAC is an 8 bit field encoded as specified in [3G 23.003] and [3G 24.008] and have values over the entire 8 bit integer range.</Section> </Description> <PrimBasicElemDef> <Name>rac</Name> <Type>U8</Type> <Comment>Container for packet switched routing area code</Comment> </PrimBasicElemDef> <History> <Date Day="19" Month="2" Year="2003"/> <Author>JMA</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Key set identifier (KSI) is used to identify a key set consisting of the ciphering key CK and integrity key IK, please refer to [3G 33.102].</Section> <Section>The KSI is encoded in the same way as Ciphering Key Sequence Number (CKSN), please refer to [3G 24.008, 10.5.1.2].</Section> </Description> <PrimBasicElemDef> <Name>ksi</Name> <Type>U8</Type> <Comment>Key set identifier</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_ksi</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="10" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Renamed section and made the parameter reusable between UMTS and GSM</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>It identifies a point at which LLC or DLL services are provided to a layer-3 entity, see [3G 04.06] and [04.64].</Section> <Section>SAPI allows 16 service access points to be specified but only six of them are currently defined. The rest is reserved for future use.</Section> </Description> <PrimBasicElemDef> <Name>sapi</Name> <Type>U8</Type> <Comment>Service Access Point Identifier</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_sapi</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial.</Comment> </History> <History> <Date Day="11" Month="2" Year="2003"/> <Author>AGR</Author> <Comment>The SAPI is now common for LLC and DLL SAP's.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for a service data unit. It consists of a length field specifying the size of the message in the container, an offset specifying where inside the included data array the message starts and a data array holding the message. The array has a default size of one byte, but in reality this is a variable length structure. Only use as the last element in a primitive, and allocate memory using SDU allocation routine.</Section> </Description> <PrimBasicElemDef> <Name>l_buf</Name> <Type>U16</Type> <Comment>Length in bits</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="16" Month="1" Year="2003"/> <Author>LOE</Author> <Comment>Default length set to one byte</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for a service data unit. It consists of a length field specifying the size of the message in the container, an offset specifying where inside the included data array the message starts and a data array holding the message. The array has a default size of one byte, but in reality this is a variable length structure. Only use as the last element in a primitive, and allocate memory using SDU allocation routine.</Section> </Description> <PrimBasicElemDef> <Name>o_buf</Name> <Type>U16</Type> <Comment>Offset in bits</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="16" Month="1" Year="2003"/> <Author>LOE</Author> <Comment>Default length set to one byte</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is a container for a service data unit. It consists of a length field specifying the size of the message in the container, an offset specifying where inside the included data array the message starts and a data array holding the message. The array has a default size of one byte, but in reality this is a variable length structure. Only use as the last element in a primitive, and allocate memory using SDU allocation routine.</Section> </Description> <PrimBasicElemDef> <Name>buf</Name> <Type>U8</Type> <Comment>Message content</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="16" Month="1" Year="2003"/> <Author>LOE</Author> <Comment>Default length set to one byte</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter defines the type of subscriber card present.</Section> </Description> <PrimBasicElemDef> <Name>sim_type</Name> <Type>U8</Type> <Comment>Type of subscriber card present.</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_sim_type</Name> </ValuesLink> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Used to contain a 32-bit Temporary Mobile Subscriber Identity (TMSI). The formatting of this parameter is like the air interface transmission order, see [3G 24.008], and the (U)SIM format, see [3G 11.11] and [3G 31.102].</Section> </Description> <PrimBasicElemDef> <Name>content_tmsi</Name> <Type>U8</Type> <Comment>Content of TMSI</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constant CONTENT_TMSI</Comment> </History> <History> <Date Day="3" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Updated description text.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter contains a measured value of RSSI for a UMTS channel.</Section> </Description> <PrimBasicElemDef> <Name>uarfcn_rssi</Name> <Type>S8</Type> <Comment>UMTS channel RSSI measurement</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_uarfcn_rssi</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used in order to specify a UMTS channel number (UARFCN). The channel number can be used for either an uplink channel or a downlink channel, as the channel number ranges are the same.</Section> </Description> <PrimBasicElemDef> <Name>uarfcn</Name> <Type>U16</Type> <Comment>UMTS channel number</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_uarfcn</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Changed to use constants in range.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Contains ciphering and integrity keys for a CN domain. The order of bits is specified in [3G 31.102]: the MSB is the MSB of the first byte in the byte array and the LSB is the LSB of the last byte in the byte array.</Section> </Description> <PrimBasicElemDef> <Name>ciphering_key</Name> <Type>U8</Type> <Comment>Ciphering key</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Contains ciphering and integrity keys for a CN domain. The order of bits is specified in [3G 31.102]: the MSB is the MSB of the first byte in the byte array and the LSB is the LSB of the last byte in the byte array.</Section> </Description> <PrimBasicElemDef> <Name>integrity_key</Name> <Type>U8</Type> <Comment>Integrity protection key</Comment> </PrimBasicElemDef> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter contains a measurement result for a single UMTS neighbour cell. The cell is identified through the cell description. If no measurements are available for the cell (e.g. it was not found), measurements will be absent from the structure.</Section> </Description> <PrimBasicElemDef> <Name>cell_status</Name> <Type>U8</Type> <Comment>Cell suitability status</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_cell_status</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter specifies the primary scrambling code for a UMTS FDD cell (that of the PCCPCH). The contents are as specified in [3G 31.102].</Section> </Description> <PrimBasicElemDef> <Name>psc</Name> <Type>U16</Type> <Comment>FDD primary scrambling code</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_psc</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Added constants PSC_MIN & MAX</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Contains information related to ciphering and integrity protection for both CN domains. In case USIM is present the security information is loaded from USIM.</Section> <Section>In case only a SIM card is a present, UMTS cipher key and integrity key are derived using conversion functions c4 and c5 [[3G 33.102, 6.8.2.4]. The conversion functions c4 and c5 are implemented in NAS. In this case THRESHOLD value shall be set to default value (all ones) while START values are marked as "not present". If present the START values will be ignored by RRC. The START values are maintained solely by the RRC entity.</Section> <Section>In case neither USIM nor SIM is present the cipher keys and integrity keys are marked as "not present". START values are initialised to zero and THRESHOLD value is set to default value (all ones). This is according to [3G 25.331, 8.1.3.6].</Section> </Description> <PrimBasicElemDef> <Name>threshold</Name> <Type>U32</Type> <Comment>THRESHOLD value</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_threshold</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated and minor typing error</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Renamed SIZE_START_MAX to MAX_START_VALUE.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is container for a START value used in connection with UMTS ciphering</Section> </Description> <PrimBasicElemDef> <Name>start_val</Name> <Type>U32</Type> <Comment>START value (20 bits)</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_start_val</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="6" Month="2" Year="2003"/> <Author>GSO</Author> <Comment>Link updated</Comment> </History> <History> <Date Day="9" Month="3" Year="2003"/> <Author>BRY</Author> <Comment>Renamed SIZE_START_MAX to MAX_START_VALUE.</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter determines whether transmit diversity is used for a UMTS FDD cell.</Section> </Description> <PrimBasicElemDef> <Name>tx_diversity</Name> <Type>U8</Type> <Comment>UMTS FDD TX diversity indicator</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">8010_152_ps_include</DocName> <Name>VAL_tx_diversity</Name> </ValuesLink> <History> <Date Day="28" Month="11" Year="2002"/> <Author>KBS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> </PrimBasicElementsSection> <ValuesSection> <Description> <Section>This section contains all sets of values that are defined for the 8010_152_PS_INCLUDE SAP</Section> </Description> <Values> <Description> <Section>Values for pkt_flow_id</Section> </Description> <ValuesDef> <Name>VAL_pkt_flow_id</Name> <Comment>values for pkt_flow_id</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>PFI_BEST_EFFORT</Alias> <Comment>Best Effort</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>PFI_SIGNALING</Alias> <Comment>Signalling</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">02</Value> <Alias>PFI_SMS</Alias> <Comment>SMS</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">FF</Value> <Alias>PKT_FLOW_ID_NOT_PRES</Alias> <Comment>Value FF is used to indicate when Packet Flow Identifier is not present.</Comment> </ValuesItem> <History> <Date Day="8" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Moving values from nas_include to ps_include</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_content</Name> <Comment>values for content</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>ACC_INDEX_CLASSES_8_TO_15</Alias> <Comment>Index to use in content array for classes 8 to 15</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>ACC_INDEX_CLASSES_0_TO_7</Alias> <Comment>Index to use in content array for classes 0 to 7</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>ACC_MASK_CLASS_00</Alias> <Comment>Mask for accessing access class 0</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">02</Value> <Alias>ACC_MASK_CLASS_01</Alias> <Comment>Mask for accessing access class 1</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">04</Value> <Alias>ACC_MASK_CLASS_02</Alias> <Comment>Mask for accessing access class 2</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">08</Value> <Alias>ACC_MASK_CLASS_03</Alias> <Comment>Mask for accessing access class 3</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">10</Value> <Alias>ACC_MASK_CLASS_04</Alias> <Comment>Mask for accessing access class 4</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">20</Value> <Alias>ACC_MASK_CLASS_05</Alias> <Comment>Mask for accessing access class 5</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">40</Value> <Alias>ACC_MASK_CLASS_06</Alias> <Comment>Mask for accessing access class 6</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">80</Value> <Alias>ACC_MASK_CLASS_07</Alias> <Comment>Mask for accessing access class 7</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>ACC_MASK_CLASS_08</Alias> <Comment>Mask for accessing access class 8</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">02</Value> <Alias>ACC_MASK_CLASS_09</Alias> <Comment>Mask for accessing access class 9</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">04</Value> <Alias>ACC_MASK_CLASS_10</Alias> <Comment>Mask for accessing access class 10</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">08</Value> <Alias>ACC_MASK_CLASS_11</Alias> <Comment>Mask for accessing access class 11</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">10</Value> <Alias>ACC_MASK_CLASS_12</Alias> <Comment>Mask for accessing access class 12</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">20</Value> <Alias>ACC_MASK_CLASS_13</Alias> <Comment>Mask for accessing access class 13</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">40</Value> <Alias>ACC_MASK_CLASS_14</Alias> <Comment>Mask for accessing access class 14</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">80</Value> <Alias>ACC_MASK_CLASS_15</Alias> <Comment>Mask for accessing access class 15</Comment> </ValuesItem> <History> <Date Day="26" 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_access_modes</Name> <Comment>values for access_modes</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>GSM_VOICE_ONLY</Alias> <Comment>GSM voice only mode</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>GSM</Alias> <Comment>GSM voice and data mode</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>GSM_GPRS</Alias> <Comment>GSM voice and data with GPRS mode</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>UMTS_FDD</Alias> <Comment>UMTS FDD only mode</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>GSM_GPRS_UMTS_FDD</Alias> <Comment>GSM voice and data, GPRS and UMTS mode</Comment> </ValuesItem> <History> <Date Day="26" 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_arfcn_rssi</Name> <Comment>values for arfcn_rssi</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>MIN_RSSI_GSM</MinValue> <MaxValue>MAX_RSSI_GSM</MaxValue> <Comment>Range of averaged received signal strength</Comment> </ValuesRange> <History> <Date Day="26" 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_attach_detach_allowed</Name> <Comment>values for attach_detach_allowed</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>ATTACH_DETACH_NOT_ALLOWED</Alias> <Comment>Attach/detach not allowed</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>ATTACH_DETACH_ALLOWED</Alias> <Comment>Attach/detach allowed</Comment> </ValuesItem> <History> <Date Day="26" 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_service_level</Name> <Comment>values for service_level</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>LIMITED_SERVICE</Alias> <Comment>Camped on acceptable cell. This indicates that the cell is selected for limited service.</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>NORMAL_SERVICE</Alias> <Comment>Camped on suitable cell. This indicates that the cell is selected for normal service.</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">02</Value> <Alias>NORMAL_SERVICE_OPERATOR_CELL</Alias> <Comment>Camped on a suitable operator cell. This indicates that the cell is selected for normal service, and is reserved for operator use.</Comment> </ValuesItem> <History> <Date Day="26" 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_cn_domain</Name> <Comment>values for cn_domain</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>CN_DOMAIN_CS</Alias> <Comment>Circuit switched core network domain</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>CN_DOMAIN_PS</Alias> <Comment>Packet switched core network domain</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">02</Value> <Alias>CN_DOMAIN_NOT_IMPORTANT</Alias> <Comment>Core network domain not important</Comment> </ValuesItem> <History> <Date Day="26" 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_cpich_ec_n0</Name> <Comment>values for cpich_ec_n0</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>MIN_RSSI_UMTS</MinValue> <MaxValue>MAX_RSSI_UMTS</MaxValue> <Comment>The CPICH Ec/N0 parameter has a range from -24 to 0 dB in steps of 0.5. The value is multiplied with 2 to avoid using floating-point numbers.</Comment> </ValuesRange> <History> <Date Day="26" 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_cpich_rscp</Name> <Comment>values for cpich_rscp</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>CPICH_RSCP_MIN</MinValue> <MaxValue>CPICH_RSCP_MAX</MaxValue> <Comment>The range of CPICH RSCP is -115 to -25 dBm in steps of 1.</Comment> </ValuesRange> <History> <Date Day="26" 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_est_service</Name> <Comment>values for est_service</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>SERVICE_SPEECH</Alias> <Comment>CS Speech call</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>SERVICE_MULTIMEDIA</Alias> <Comment>CS Multimedia call</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">02</Value> <Alias>SERVICE_FAX</Alias> <Comment>CS Fax call</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">03</Value> <Alias>SERVICE_NT_CSD</Alias> <Comment>Non transparent CS data call</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">04</Value> <Alias>SERVICE_T_CSD</Alias> <Comment>Transparent CS data call</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">05</Value> <Alias>SERVICE_EMERGE</Alias> <Comment>CS emergency speech call</Comment> </ValuesItem> <History> <Date Day="26" 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_arfcn</Name> <Comment>values for arfcn</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>MIN_ARFCN_VALUE</MinValue> <MaxValue>MAX_ARFCN_VALUE</MaxValue> <Comment>Range of ARFCN, see [3G 05.05]</Comment> </ValuesRange> <History> <Date Day="26" 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_gsm_band_priority</Name> <Comment>values for gsm_band_priority</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>EU_BAND</Alias> <Comment>EU band has priority</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>US_BAND</Alias> <Comment>US band has priority</Comment> </ValuesItem> <History> <Date Day="26" 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_bcc</Name> <Comment>values for bcc</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>0</MinValue> <MaxValue>BCC_MAX</MaxValue> <Comment>Range of BCC</Comment> </ValuesRange> <History> <Date Day="26" 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_ncc</Name> <Comment>values for ncc</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>0</MinValue> <MaxValue>NCC_MAX</MaxValue> <Comment>Range of NCC</Comment> </ValuesRange> <History> <Date Day="26" 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_gsm_frequency_band</Name> <Comment>values for gsm_frequency_band</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">0000</Value> <Alias>GSM_BAND_NOT_SET</Alias> <Comment>No channel numbers.</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">0001</Value> <Alias>GSM450</Alias> <Comment>Channel numbers from 259 to 293 for GSM450</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">0002</Value> <Alias>GSM480</Alias> <Comment>Channel numbers from 306 to 340 for GSM480</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">0004</Value> <Alias>GSM850</Alias> <Comment>Channel numbers from 128 to 251 for GSM850</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">0008</Value> <Alias>GSM900P</Alias> <Comment>Channel numbers from 1 to 124 for P-GSM900</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">0010</Value> <Alias>GSM900E</Alias> <Comment>Channel numbers from 0 to 124, and 975 to 1023 for E-GSM900</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">0020</Value> <Alias>GSM1800</Alias> <Comment>Channel numbers from 512 to 885 for GSM1800</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">0040</Value> <Alias>GSM1900</Alias> <Comment>Channel numbers from 512 to 810 for GSM1900</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">0039</Value> <Alias>GSM1800_BAND_INDICATOR</Alias> <Comment>All channel numbers. Channel numbers from 512 to 810 are to be interpreted as GSM1800 channel numbers.</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">0046</Value> <Alias>GSM1900_BAND_INDICATOR</Alias> <Comment>All channel numbers. Channel numbers from 512 to 810 are to be interpreted as GSM1900 channel numbers.</Comment> </ValuesItem> <History> <Date Day="26" 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_gsm_ncell_index</Name> <Comment>values for gsm_ncell_index</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>0</MinValue> <MaxValue>MAX_GSM_NCELL_INDEX</MaxValue> <Comment>Range of index</Comment> </ValuesRange> <History> <Date Day="26" 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_bsic_valid</Name> <Comment>values for bsic_valid</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>BSIC_NOT_VALIDATED</Alias> <Comment>BSIC for the cell on this channel is not validated or not matched to that of the specified cell.</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>BSIC_VALIDATED</Alias> <Comment>BSIC for the cell on this channel is validated and matches that of the specified cell.</Comment> </ValuesItem> <History> <Date Day="26" 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_llc_mode</Name> <Comment>values for llc_mode</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>LLC_UNACKNOWLEDGED</Alias> <Comment>Unacknowledged SAPI</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LLC_ACKNOWLEDGED</Alias> <Comment>Acknowledged SAPI</Comment> </ValuesItem> <History> <Date Day="26" 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_meas_mode</Name> <Comment>values for meas_mode</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>MEASURE_IDLE</Alias> <Comment>Measurements without a configured DCH</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>MEASURE_DEDICATED</Alias> <Comment>Measurements with a configured DCH</Comment> </ValuesItem> <History> <Date Day="26" 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_nmo</Name> <Comment>values for nmo</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>RR_NMO_I</Alias> <Comment>Network mode of operation I, only one Paging channel for both: PCCCH or CCCH</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>RR_NMO_II</Alias> <Comment>Network mode of operation II, Paging only on CCCH</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>RR_NMO_III</Alias> <Comment>Network mode of operation III, Paging on CCCH for CS and either on CCCH or on PCCCH for GPRS, if PCCH allocated in the cell</Comment> </ValuesItem> <History> <Date Day="26" 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_search_mode</Name> <Comment>values for search_mode</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>SEARCH_MODE_AUTO</Alias> <Comment>Automatic network scan</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SEARCH_MODE_MAN</Alias> <Comment>Manual network scan</Comment> </ValuesItem> <History> <Date Day="26" 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_t3212</Name> <Comment>values for t3212</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>NO_PERIODIC_UPDATE</Alias> <Comment>No periodic updating</Comment> </ValuesItem> <ValuesRange ValueType="DEC"> <MinValue>1</MinValue> <MaxValue>255</MaxValue> <Comment>(6 * value) minutes</Comment> </ValuesRange> <History> <Date Day="26" 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_mnc</Name> <Comment>values for mnc</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>MIN_BCD_VALUE</MinValue> <MaxValue>MAX_BCD_VALUE</MaxValue> <Comment>Range of a MNC digit.</Comment> </ValuesRange> <History> <Date Day="26" 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_mcc</Name> <Comment>values for mcc</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>MIN_BCD_VALUE</MinValue> <MaxValue>MAX_BCD_VALUE</MaxValue> <Comment>Range of a MCC digit.</Comment> </ValuesRange> <History> <Date Day="26" 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_rat</Name> <Comment>values for rat</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>RAT_GSM</Alias> <Comment>GSM</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>RAT_UMTS_FDD</Alias> <Comment>UMTS FDD</Comment> </ValuesItem> <History> <Date Day="26" 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_radio_prio</Name> <Comment>values for radio_prio</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>RADIO_PRIO_1</Alias> <Comment>radio priority 1 (highest)</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>RADIO_PRIO_2</Alias> <Comment>radio priority 2</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>RADIO_PRIO_3</Alias> <Comment>radio priority 3</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>RADIO_PRIO_4</Alias> <Comment>radio priority 4 (lowest)</Comment> </ValuesItem> <History> <Date Day="26" 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_rel_ind</Name> <Comment>values for rel_ind</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>REL_IND_NO</Alias> <Comment>Non-local deactivation</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>REL_IND_YES</Alias> <Comment>Local deactivation</Comment> </ValuesItem> <History> <Date Day="26" 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_ksi</Name> <Comment>values for ksi</Comment> </ValuesDef> <ValuesItem> <Value ValueType="ALPHA">KEY_SEQ_INVALID</Value> <Alias/> <Comment>Sequence number value indicating that the key is not present (initial value on (U)SIM)</Comment> </ValuesItem> <ValuesRange ValueType="ALPHA"> <MinValue>MIN_KEY_SEQ_NUM</MinValue> <MaxValue>MAX_KEY_SEQ_NUM</MaxValue> <Comment>Range of sequence number</Comment> </ValuesRange> <History> <Date Day="26" 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_sapi</Name> <Comment>values for sapi</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>SAPI_0</Alias> <Comment>SAPI 0 (GSM only)</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SAPI_1</Alias> <Comment>SAP for MM</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>SAPI_3</Alias> <Comment>SAP 1 for SNDCP or SAPI 3 (GSM only)</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>SAPI_5</Alias> <Comment>SAP 2 for SNDCP</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">7</Value> <Alias>SAPI_7</Alias> <Comment>SAP for SMS</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">9</Value> <Alias>SAPI_9</Alias> <Comment>SAP 3 for SNDCP</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">11</Value> <Alias>SAPI_11</Alias> <Comment>SAP 4 for SNDCP</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">255</Value> <Alias>SAPI_INVALID</Alias> <Comment>Invalid SAPI identifier</Comment> </ValuesItem> <History> <Date Day="26" 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_sim_type</Name> <Comment>values for sim_type</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>SIM_PRESENT</Alias> <Comment>SIM present</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>USIM_PRESENT</Alias> <Comment>USIM present</Comment> </ValuesItem> <History> <Date Day="26" 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_uarfcn_rssi</Name> <Comment>values for uarfcn_rssi</Comment> </ValuesDef> <ValuesRange ValueType="DEC"> <MinValue>-100</MinValue> <MaxValue>-25</MaxValue> <Comment>Range of averaged received signal strength in dBm.</Comment> </ValuesRange> <History> <Date Day="26" 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_uarfcn</Name> <Comment>values for uarfcn</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>MIN_UARFCN</MinValue> <MaxValue>MAX_UARFCN</MaxValue> <Comment>UARFCN range, see [3G 25.101].</Comment> </ValuesRange> <History> <Date Day="26" 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_cell_status</Name> <Comment>values for cell_status</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>CELL_STATUS_UNKNOWN</Alias> <Comment>It is not known whether this cell is suitable or acceptable at this time.</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>CELL_STATUS_UNACCEPTABLE</Alias> <Comment>The cell is not acceptable or suitable as defined by the criteria in [3G 25.304]</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">02</Value> <Alias>CELL_STATUS_ACCEPTABLE</Alias> <Comment>The cell is acceptable as defined by the criteria in [3G 25.304].</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">03</Value> <Alias>CELL_STATUS_SUITABLE</Alias> <Comment>The cell is suitable as defined by the criteria in [3G 25.304]</Comment> </ValuesItem> <History> <Date Day="26" 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_psc</Name> <Comment>values for psc</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>PSC_MIN</MinValue> <MaxValue>PSC_MAX</MaxValue> <Comment>Range og Primary Scrambling Code</Comment> </ValuesRange> <History> <Date Day="26" 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_threshold</Name> <Comment>values for threshold</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>0</MinValue> <MaxValue>MAX_START_VALUE</MaxValue> <Comment>The THRESHOLD value is 20 bits long</Comment> </ValuesRange> <History> <Date Day="26" 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_start_val</Name> <Comment>values for start_val</Comment> </ValuesDef> <ValuesRange ValueType="ALPHA"> <MinValue>0</MinValue> <MaxValue>MAX_START_VALUE</MaxValue> <Comment>The START value is max 20 bits</Comment> </ValuesRange> <History> <Date Day="26" 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_tx_diversity</Name> <Comment>values for tx_diversity</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>TX_DIVERSITY_USED</Alias> <Comment>TX diversity used for a cell</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>TX_DIVERSITY_NOT_USED</Alias> <Comment>TX diversity not used for a cell</Comment> </ValuesItem> <History> <Date Day="26" Month="11" Year="2003"/> <Author>doc2XML</Author> <Comment>Initial</Comment> </History> </Values> <Values> <Description> <Section/> </Description> <ValuesDef> <Name>VAL_sgsn_rel</Name> <Comment>Values for SGSN release</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>SGSN_UNKNOWN</Alias> <Comment>SGSN release unknown/uninitialized</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>SGSN_98_OLDER</Alias> <Comment>SGSN is release 98 or older</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">02</Value> <Alias>SGSN_99_ONWARDS</Alias> <Comment>SGSN is relesase 99 or onwards</Comment> </ValuesItem> <History> <Date Day="28" Month="04" Year="2004"/> <Author/> <Comment>Initial</Comment> </History> <History> <Date Day="3" Month="6" Year="2004"/> <Author>HB</Author> <Comment>Invalid SGSN release deleted due to its redundancy</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_peak</Name> <Comment>values for peak</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>PEAK_SUB</Alias> <Comment>Subscribed peak throughput</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>PEAK_1K</Alias> <Comment>Up to 1 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>PEAK_2K</Alias> <Comment>Up to 2 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>PEAK_4K</Alias> <Comment>Up to 4 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>PEAK_8K</Alias> <Comment>Up to 8 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>PEAK_16K</Alias> <Comment>Up to 16 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">6</Value> <Alias>PEAK_32K</Alias> <Comment>Up to 32 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">7</Value> <Alias>PEAK_64K</Alias> <Comment>Up to 64 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">8</Value> <Alias>PEAK_128K</Alias> <Comment>Up to 128 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">9</Value> <Alias>PEAK_256K</Alias> <Comment>Up to 256 000 octet/s</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_relclass</Name> <Comment>values for relclass</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>RELCLASS_SUB</Alias> <Comment>Subscribed reliability class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>GTP_LLC_RLC_PROT</Alias> <Comment>Acknowledged GTP, LLC, and RLC; Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>LLC_RLC_PROT</Alias> <Comment>Unacknowledged GTP; Acknowledged LLC and RLC, Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>RLC_PROT</Alias> <Comment>Unacknowledged GTP and LLC; Acknowledged RLC, Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>PROT</Alias> <Comment>Unacknowledged GTP, LLC, and RLC, Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>NO_REL</Alias> <Comment>Unacknowledged GTP, LLC, and RLC, Unprotected data</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_delay</Name> <Comment>values for delay</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>DELAY_SUB</Alias> <Comment>Subscribed delay class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>DELAY_1</Alias> <Comment>Delay class 1</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>DELAY_2</Alias> <Comment>Delay class 2</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>DELAY_3</Alias> <Comment>Delay class 3</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>DELAY_4</Alias> <Comment>Delay class 4 (best effort)</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_mean</Name> <Comment>values for mean</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>MEAN_SUB</Alias> <Comment>Subscribed mean throughput</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>MEAN_100</Alias> <Comment>100 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>MEAN_200</Alias> <Comment>200 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>MEAN_500</Alias> <Comment>500 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>MEAN_1K</Alias> <Comment>1 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>MEAN_2K</Alias> <Comment>2 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">6</Value> <Alias>MEAN_5K</Alias> <Comment>5 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">7</Value> <Alias>MEAN_10K</Alias> <Comment>10 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">8</Value> <Alias>MEAN_20K</Alias> <Comment>20 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">9</Value> <Alias>MEAN_50K</Alias> <Comment>50 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">10</Value> <Alias>MEAN_100K</Alias> <Comment>100 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">11</Value> <Alias>MEAN_200K</Alias> <Comment>200 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">12</Value> <Alias>MEAN_500K</Alias> <Comment>500 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">13</Value> <Alias>MEAN_1M</Alias> <Comment>1 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">14</Value> <Alias>MEAN_2M</Alias> <Comment>2 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">15</Value> <Alias>MEAN_5M</Alias> <Comment>5 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">16</Value> <Alias>MEAN_10M</Alias> <Comment>10 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">17</Value> <Alias>MEAN_20M</Alias> <Comment>20 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">18</Value> <Alias>MEAN_50M</Alias> <Comment>50 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">31</Value> <Alias>MEAN_BEST</Alias> <Comment>Best effort</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_preced</Name> <Comment>values for preced</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>PRECED_SUB</Alias> <Comment>Subscribed precedence</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>PRIO_HIGH</Alias> <Comment>High priority</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>PRIO_NORM</Alias> <Comment>Normal priority</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>PRIO_LOW</Alias> <Comment>Low priority</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_guar_br_dl</Name> <Comment>values for guar_br_dl</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>GUAR_BR_DL_SUB</Alias> <Comment>Subscribed guaranteed uplink data rate</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_max_rate_dl</Name> <Comment>values for max_rate_dl</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>MAX_BR_DL_SUB</Alias> <Comment>Subscribed maximum downlink data rate</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">255</Value> <Alias>MAX_BR_DL_0</Alias> <Comment>0 kbps downlink data rate</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_max_sdu</Name> <Comment>values for max_sdu</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>MAX_SDU_SUB</Alias> <Comment>Subscribed maximum SDU size</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">151</Value> <Alias>MAX_SDU_1502</Alias> <Comment>Value not corresponding to binary coding of SDU size declared constant</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">152</Value> <Alias>MAX_SDU_1510</Alias> <Comment>do.</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">153</Value> <Alias>MAX_SDU_1520</Alias> <Comment>do.</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_order</Name> <Comment>values for order</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>ORDER_NO</Alias> <Comment>Without delivery order ('no')</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>ORDER_YES</Alias> <Comment>With delivery order ('yes')</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>ORDER_SUB</Alias> <Comment>Subscribed delivery order</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_del_err_sdu</Name> <Comment>values for del_err_sdu</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>DEL_ERR_NO</Alias> <Comment>Erroneous SDUs are not delivered ('no')</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>DEL_ERR_YES</Alias> <Comment>Erroneous SDUs are delivered ('yes')</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>DEL_ERR_NODETECT</Alias> <Comment>No detect ('-')</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>DEL_ERR_SUB</Alias> <Comment>Subscribed delivery of erroneous SDUs</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_tc</Name> <Comment>values for tc</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>TC_CONV</Alias> <Comment>Conversational class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>TC_STREAM</Alias> <Comment>Streaming class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>TC_INTER</Alias> <Comment>Interactive class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>TC_BG</Alias> <Comment>Background class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>TC_SUB</Alias> <Comment>Subscribed traffic class</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_max_rate_ul</Name> <Comment>values for max_rate_ul</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>MAX_BR_UL_SUB</Alias> <Comment>Subscribed maximum uplink data rate</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">255</Value> <Alias>MAX_BR_UL_0</Alias> <Comment>0 kbps uplink data rate</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_guar_br_ul</Name> <Comment>values for guar_br_ul</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>GUAR_BR_UL_SUB</Alias> <Comment>Subscribed guaranteed uplink data rate</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_handling_pri</Name> <Comment>values for handling_pri</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>HANDLING_PRI_SUB</Alias> <Comment>Subscribed traffic handling priority</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>HANDLING_PRI_1</Alias> <Comment>Priority level 1</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>HANDLING_PRI_2</Alias> <Comment>Priority level 2</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>HANDLING_PRI_3</Alias> <Comment>Priority level 3</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</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_xfer_delay</Name> <Comment>values for xfer_delay</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>XFER_DELAY_SUB</Alias> <Comment>Subscribed transfer delay</Comment> </ValuesItem> <History> <Date Day="7" Month="6" Year="2004"/> <Author>rpk</Author> <Comment>Initial</Comment> </History> </Values> </ValuesSection> </SAP>