<?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">snsm</DocName>
        <DocNum Number="109" Project="8441"/>
        <Description>
            <Section>The Protocol Stacks are used to define the functionality of the GSM protocols for interfaces. The GSM specifications are normative when used to describe the functionality of interfaces, but the stacks and the subdivision of protocol layers does not imply or restrict any implementation.</Section>
            <Section>The protocol stack for fax and data transmission consists of several entities. Each entity has one ore more service access points, over which the entity provides a service for the upper entity. The entity, which is described in this document, is coloured grey in the following figure :</Section>
            <Section>Figure 1-1: Architecture of the GSM/GPRS protocol stack</Section>
            <Section>The information units passed via the SAPs are called primitives and consists of an operation code and several parameters. See the Users Guide for details.</Section>
            <Section>The entities of the GPRS protocol stack are:</Section>
            <Section>1.1 GRR (RLC/MAC) - Radio Link Control/Medium Access Control</Section>
            <Section>This layer contains two functions: The Radio Link Control function provides a radio-solution-dependent reliable link. The Medium Access Control function controls the access signalling (request and grant) procedures for the radio channel, and the mapping of LLC frames onto the GSM physical channel.</Section>
            <Section>1.2 LLC - Logical Link Control</Section>
            <Section>The LLC entity provides multiple highly reliable logical links for asynchronous data transfer between the MS and the network. It supports variable-length information frames, acknowledged and unacknowledged data transfer, flow and sequence control, error detection and recovery, notification of unrecoverable errors, user identity confidentiality, and ciphering of user and signaling data.</Section>
            <Section>1.3 GMM - GPRS Mobility Management</Section>
            <Section>The GMM entity provides procedures for the mobility of the MS, such as informing the network of its present location, and user identity confidentiality. It manages the GMM context (attach, detach, routing area updating), supports security functions such as authentication of user and MS, controls ciphering of data, and initiates the response to paging messages.</Section>
            <Section>1.4 SM - Session Management</Section>
            <Section>The main function of the session management (SM) is to support PDP context handling of the user terminal. Session Management activates, modifies and deletes the contexts for packet data protocols (PDP). Session Management services are provided at the SMREG-SAP and the SNSM-SAP for anonymous and non-anonymous access. The non-anonymous and anonymous access procedures for PDP context activation and PDP context deactivation are available at the SMREG-SAP. In addition there exists a PDP context modification for non-anonymous PDP contexts.</Section>
            <Section>1.5 SNDCP - Subnetwork Dependant Convergence Protocol</Section>
            <Section>SNDCP carries out all functions related to transfer of Network layer Protocol Data Units (N-PDUs) over GPRS in a transparent way. SNDCP helps to improve channel efficiency by means of compression techniques. The set of protocol entities above SNDCP consists of commonly used network protocols. They all use the same SNDCP entity, which then performs multiplexing of data coming from different sources to be sent using the service provided by the LLC layer.</Section>
            <Section>1.6 GACI - GPRS Application Control Interface</Section>
            <Section>The GACI is the GPRS extension of the ACI. It is specified in GSM 07.07 and 07.60. It is responsible for processing of the GPRS related AT Commands to setup, activate and deactivate the PDP context parameter. It also provides functionality for the interworking between GMM/SM/SNDCP and a packet oriented protocol like PPP.</Section>
            <Section>1.7 USART - Universal Synchronous Asynchronous Receiver Transmitter Driver</Section>
            <Section>The USART is a hardware component that facilitates a connection between the mobile station and terminal equipment (e.g. a PC). This interface uses some of the circuits described in V.24.</Section>
            <Section>The data exchange provided by this unit is serial and asynchronous (synchronous communication is not in the scope of this document). A driver that uses interrupts to manage a circular buffer for the sending and receiving direction is necessary in order to use this component in the GPRS. The driver has to be able to perform flow control.</Section>
            <Section>1.8 TOM - Tunnelling of Messages</Section>
            <Section>The TOM entity is present if and only if HS136 is supported (the feature flag FF_HS136 is enabled).</Section>
            <Section>The main function of TOM is to tunnel non-GSM signalling messages between the MS and the SGSN. The only non-GSM signalling which is currently supported by TOM is for the EGPRS-136 system (according to TIA/EIA-136-376). Data transfer in both uplink and downlink direction is possible. Two different priorities (high, low) of signalling data transfer are supported. TOM uses the unacknowledged mode of LLC and the acknowledged mode of GRR (RLC/MAC).</Section>
        </Description>
        <DocHistory>
            <DocVersion Number="001" Year="99"/>
            <Date Day="1" Month="6" Year="1999"/>
            <Author>Harald</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Krug Initial</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="002" Year="99"/>
            <Date Day="19" Month="4" Year="2000"/>
            <Author>Harald</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Krug Changed hcomp/dcomp values</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="003" Year="99"/>
            <Date Day="20" Month="4" Year="2000"/>
            <Author>Harald</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Krug Renamed values for ppp_hc</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="004" Year="99"/>
            <Date Day="27" Month="4" Year="2000"/>
            <Author>Harald</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Krug Added parameter to SNSM_SEQUENCE_RES</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="005" Year="99"/>
            <Date Day="2" Month="6" Year="2000"/>
            <Author>Harald</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Krug S3</Comment>
        </DocHistory>
        <DocRef>
            <RefId>[1]</RefId>
            <RefTitle>GSM 05.02 version 8.0.0 Release 1999Digital cellular telecommunications system (Phase 2+);Multiplexing and multiple access on the radio path</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[2]</RefId>
            <RefTitle>GSM 04.60 version 6.3.0 Release 1997Digital cellular telecommunications system (Phase 2+);General Packet Radio Service (GPRS);Mobile Station (MS) - Base Station System (BSS) interface;Radio Link Control/ Medium Access Control (RLC/MAC) protocol</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[3]</RefId>
            <RefTitle>GSM 04.08 version 6.3.0 Release 1997Digital cellular telecommunications system (Phase 2+);Mobile radio interface layer 3 specification</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[4]</RefId>
            <RefTitle>GSM 03.64 version 6.1.0 Release 1997Digital cellular telecommunications system (Phase 2+);General Packet Radio Service (GPRS);Overall description of the GPRS radio interface; Stage 2</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[5]</RefId>
            <RefTitle>GSM 03.60 version 6.3.1 Release 1997Digital cellular telecommunications system (Phase 2+);General Packet Radio Service (GPRS);Service description; Stage 2</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[6]</RefId>
            <RefTitle>GSM 04.07 version 6.3.0 Release 1997Digital cellular telecommunications system (Phase 2+);Mobile radio interface signalling layer 3; General aspects</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[7]</RefId>
            <RefTitle>GSM 04.64 version 6.3.0 Release 1997Digital cellular telecommunications system (Phase 2+);General Packet Radio Service (GPRS);Mobile Station - Serving GPRS Support Node (MS-SGSN)Logical Link Control (LLC) layer specification</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[8]</RefId>
            <RefTitle>GSM 05.08 version 6.4.0 Release 1997Digital cellular telecommunications system (Phase 2+);Radio subsystem link control</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[9]</RefId>
            <RefTitle>GSM 05.10 version 6.3.0 Release 1997Digital cellular telecommunications system (Phase 2+);Radio subsystem synchronization</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[10]</RefId>
            <RefTitle>GSM 03.20 TS 100 929: July 1998 (GSM 03.20 version 6.0.1)Security related network functions, ETSI</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[11]</RefId>
            <RefTitle>Draft GSM 03.22: August 1998 (GSM 03.22 version 6.1.0)Functions related to Mobile Station (MS) in idle mode and group receive mode, ETSI</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[12]</RefId>
            <RefTitle>GSM 04.65 V6.3.0: Subnetwork Dependant Convergence Protocol ETSI, March 1999</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[13]</RefId>
            <RefTitle>ITU-T V42bis ITU-T, Recommendation V.42 bis 1990</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[14]</RefId>
            <RefTitle>GSM 09.60 GPRS Tunneling Protocol (GTP) across the Gn and Gp Interface</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[15]</RefId>
            <RefTitle>RFC 1661 IETF STD 51 July 1994The Point-to-Point Protocol (PPP)</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[16]</RefId>
            <RefTitle>RFC 1662 IETF STD 51 July 1994PPP in HDLC-like Framing</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[17]</RefId>
            <RefTitle>RFC 1570 January 1994PPP LCP Extensions</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[18]</RefId>
            <RefTitle>RFC 1989 August 1996PPP Link Quality Monitoring</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[19]</RefId>
            <RefTitle>RFC 1332 May 1992The PPP Internet Protocol Control Protocol (IPCP)</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[20]</RefId>
            <RefTitle>RFC 1877 December 1995PPP IPCP Extensions for Name Server Addresses</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[21]</RefId>
            <RefTitle>RFC 2153 May 1997PPP Vendor Extensions</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[22]</RefId>
            <RefTitle>RFC 1334 October 1992PPP Authentication Protocols (for Password Authentication Protocol only)</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[23]</RefId>
            <RefTitle>RFC 1994 August 1996PPP Challenge Handshake Authentication Protocol (CHAP)</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[24]</RefId>
            <RefTitle>TIA/EIA-136-370Packet-Data Services - Enhanced General Packet Radio for TIA/EIA-136 (EGPRS-136) - Overview, Telecommunications Industry Association</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[25]</RefId>
            <RefTitle>TIA/EIA-136-376Packet-Data Services - EGPRS-136 Mobility Management, Telecommunications Industry Association</RefTitle>
        </DocRef>
        <DocRef>
            <RefId>[26]</RefId>
            <RefTitle>TIA/EIA-136-972Packet-Data Services - Stage 2 Description, Telecommunications Industry Association</RefTitle>
        </DocRef>
    </DocInfoSection>
    <ConstantsSection>
        <Description>
            <Section>This section contains all constants that are defined for the SNSM SAP</Section>
        </Description>
        <Constant>
            <Alias>SNSM_COMP_NEITHER_DIRECT</Alias>
            <Value ValueType="BIN">00</Value>
            <Comment>compress neither direction</Comment>
        </Constant>
        <Constant>
            <Alias>SNSM_COMP_MS_SGSN_DIRECT</Alias>
            <Value ValueType="BIN">01</Value>
            <Comment>compress MS to SGSN direction only</Comment>
        </Constant>
        <Constant>
            <Alias>SNSM_COMP_SGSN_MS_DIRECT</Alias>
            <Value ValueType="BIN">10</Value>
            <Comment>compress SGSN to MS direction only</Comment>
        </Constant>
        <Constant>
            <Alias>SNSM_COMP_BOTH_DIRECT</Alias>
            <Value ValueType="BIN">11</Value>
            <Comment>compress both directions</Comment>
        </Constant>
        <History>
            <Date Day="3" Month="3" Year="1999"/>
            <Author>HK</Author>
            <Comment>Initial</Comment>
        </History>
        <History>
            <Date Day="20" Month="4" Year="2000"/>
            <Author>HK</Author>
            <Comment>Added constants for hcomp/dcomp</Comment>
        </History>
    </ConstantsSection>
    <PrimitivesSection PrimIDType="BIT16" SAPid="39">
        <Description>
            <Section>This section contains all primitives that are defined for the SNSM SAP</Section>
        </Description>
        <Primitive>
            <Description>
                <Section>Indication used by the SM entity to inform the SNDCP entity that an NSAPI has been actiated for data transfer. It also informs the SNDCP entity about the negotiated QoS profile (see [GSM 04.08], the SAPI assigned for this NSAPI, and, in the MS, the radio priority level to be uesd by RLC/MAC. If the NSAPI activated uses the acknowledged peer-to-peer LLC operation, the NSAPI shall enter the recovery state. Upon reception of the SNSM_ACTIVATE_IND from the SM sublayer, the SNDCP entity shall, if necessary, establish the acknowledged peer-to-peer LLC operation for the indicated SAPI.</Section>
                <Section>Parameter tlli is needed. Note: the parameters ppp_hc, msid, hcomp, dcomp are just passed from the SMREG user. They are used to determine the values for the compression enitities used in SNDCP.</Section>
            </Description>
            <PrimDef>
                <Name>SNSM_ACTIVATE_IND</Name>
                <PrimID Direction="DOWNLINK" Number="0"/>
                <PrimUsage>
                    <Sender>SM</Sender>
                    <Receiver>SNDCP</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>snsm_qos</Name>
                </ItemLink>
                <Comment>quality of service</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>sapi</Name>
                </ItemLink>
                <Comment>service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>radio_prio</Name>
                </ItemLink>
                <Comment>radio priority</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>ppp_hc</Name>
                </ItemLink>
                <Comment>header compression of PPP connection</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>msid</Name>
                </ItemLink>
                <Comment>max slot identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>dcomp</Name>
                </ItemLink>
                <Comment>Data compression used/direction</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>hcomp</Name>
                </ItemLink>
                <Comment>Header compression used/direction</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>dti_linkid</Name>
                </ItemLink>
                <Comment>DTI link-id</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>dti_neighbor</Name>
                </ItemLink>
                <Comment>DTI neighbor entity</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>dti_direction</Name>
                </ItemLink>
                <Comment>DTI direction</Comment>
            </PrimItem>
            <History>
                <Date Day="14" Month="4" Year="2000"/>
                <Author>HK</Author>
                <Comment>Initial .</Comment>
            </History>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added extra compression parameters.</Comment>
            </History>
            <History>
                <Date Day="7" Month="6" Year="2001"/>
                <Author>HK</Author>
                <Comment>Added dti_linkid, dti_neighbor.</Comment>
            </History>
            <History>
                <Date Day="13" Month="6" Year="2001"/>
                <Author>HK</Author>
                <Comment>Added dti_direction.</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>Response used by the SNDCP layer to inform SM entity that the indicated NSAPI is now in use and the acknowledged peer-to-peer LLC operation for the indicated SAPI is established, if necessary.</Section>
                <Section>Parameter tlli is not needed.</Section>
            </Description>
            <PrimDef>
                <Name>SNSM_ACTIVATE_RES</Name>
                <PrimID Direction="UPLINK" Number="0"/>
                <PrimUsage>
                    <Sender>SNDCP</Sender>
                    <Receiver>SM</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>ppp_hc</Name>
                </ItemLink>
                <Comment>header compression of PPP connection</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>msid</Name>
                </ItemLink>
                <Comment>max slot identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>dcomp</Name>
                </ItemLink>
                <Comment>Data compression used</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>hcomp</Name>
                </ItemLink>
                <Comment>Header compression used</Comment>
            </PrimItem>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="20" Month="4" Year="2000"/>
                <Author>HK</Author>
                <Comment>Dcomp and hcomp were switched</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>Indication used by the SM to inform the SNDCP entity that an NSAPI has been deallocated and cannot be used by the SNDCP entity anymore. All buffered N-PDUs corresponding to this NSAPI are deleted. Upon reception of the SNSMA_DEACTIVATE_IND the SNDCP entity shall, if necessary, release the acknowledged peer-to-peer LLC operation for the associated SAPI.</Section>
                <Section>Parameter tlli is not needed.</Section>
            </Description>
            <PrimDef>
                <Name>SNSM_DEACTIVATE_IND</Name>
                <PrimID Direction="DOWNLINK" Number="1"/>
                <PrimUsage>
                    <Sender>SM</Sender>
                    <Receiver>SNDCP</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>nsapi_set</Name>
                </ItemLink>
                <Comment>set of network layer service access point identifiers</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>rel_ind</Name>
                </ItemLink>
                <Comment>LLC Release indicator</Comment>
            </PrimItem>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>Response used by the SNDCP layer to inform SM entity that the NSAPI indicated is no longer in use and that the acknowledged peer-to-peer LLC operation for the associated SAPI is released, if necessary.</Section>
                <Section>Parameter tlli is not needed.</Section>
            </Description>
            <PrimDef>
                <Name>SNSM_DEACTIVATE_RES</Name>
                <PrimID Direction="UPLINK" Number="1"/>
                <PrimUsage>
                    <Sender>SNDCP</Sender>
                    <Receiver>SM</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>Indication used by the SM entity to trigger change of the QoS profile (see [GSM 04.08]) for an NSAPI and indication of the SAPI to be used. It is also used in the MS to signal a change of the radio priority level to used by RLC/MAC ([GSM 04.65, 5.1.2.23] with focus only on MS side).</Section>
                <Section>Parameter tlli is not needed.</Section>
            </Description>
            <PrimDef>
                <Name>SNSM_MODIFY_IND</Name>
                <PrimID Direction="DOWNLINK" Number="2"/>
                <PrimUsage>
                    <Sender>SM</Sender>
                    <Receiver>SNDCP</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>snsm_qos</Name>
                </ItemLink>
                <Comment>quality of service</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>sapi</Name>
                </ItemLink>
                <Comment>service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>radio_prio</Name>
                </ItemLink>
                <Comment>radio priority</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>send_no</Name>
                </ItemLink>
                <Comment>send n-pdu number</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>rec_no</Name>
                </ItemLink>
                <Comment>receive n-pdu number</Comment>
            </PrimItem>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="3" Month="8" Year="1999"/>
                <Author>HK</Author>
                <Comment>added n-dpu number parameters</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>Response used by the SNDCP entity to inform the SM entity that the indicated NSAPI and QoS profile are now in use and the acknowledged peer-to-peer LLC operations for the appropriate SAPIs are established and/or released, if necessary.</Section>
                <Section>Parameter tlli is not needed.</Section>
            </Description>
            <PrimDef>
                <Name>SNSM_MODIFY_RES</Name>
                <PrimID Direction="UPLINK" Number="2"/>
                <PrimUsage>
                    <Sender>SNDCP</Sender>
                    <Receiver>SM</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>This primitive is used by the SNDCP layer to inform the SM sub-layer that SNDCP cannot continue ist operation due to errors at the LLC layer (as indicated with LL_RELEASE_IND) or at the SNDCP layer. The Cause parameter indicates the cause of the error..</Section>
                <Section>Parameter tlli is not needed.</Section>
            </Description>
            <PrimDef>
                <Name>SNSM_STATUS_REQ</Name>
                <PrimID Direction="UPLINK" Number="3"/>
                <PrimUsage>
                    <Sender>SNDCP</Sender>
                    <Receiver>SM</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>sapi</Name>
                </ItemLink>
                <Comment>service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>status_cause</Name>
                </ItemLink>
                <Comment>cause of the error</Comment>
            </PrimItem>
            <History>
                <Date Day="3" Month="3" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>This primitive is used during an inter-SGSN routeing area update and applies only to NSAPIs using acknowledged peer-to-peer LLC operation. When the primitive is used in the MS, the Receive N-PDU number parameter indicates the Receive N-PDU number in the SGSN. When the primitive is used in the SGSN, the Receive N-PDU number parameter indicates the Receive N-PDU number in the MS. If a buffered N-PDU is confirmed by the Receive N-PDU number parameter to have been received by the peer SNDCP entity, the N-PDU shall be deleted from the buffer. In addition, the receipt of this primitive by the SNDCP entity resumes the transmission of SN-PDUs for the NSAPI, and all buffered N-PDUs (i.e., the ones whose complete reception has not been acknowledged and the ones that have not been transmitted yet) shall be transmitted starting from the oldest N-PDU. If acknowledged peer-to-peer LLC operation has not yet been established for the SAPI used by this NSAPI, the transmission of the buffered N-PDUs shall begin only after the receipt of the LL-ESTABLISH.indication or LL-ESTABLISH.confirm primitive.</Section>
                <Section>[GSM 04.65, 5.1.2.26]]</Section>
                <Section>Parameter tlli is not needed.</Section>
            </Description>
            <PrimDef>
                <Name>SNSM_SEQUENCE_IND</Name>
                <PrimID Direction="DOWNLINK" Number="3"/>
                <PrimUsage>
                    <Sender>SM</Sender>
                    <Receiver>SNDCP</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>rec_no</Name>
                </ItemLink>
                <Comment>receive n-pdu number</Comment>
            </PrimItem>
            <History>
                <Date Day="3" Month="8" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>This primitive is used during an inter-SGSN routeing area update and applies only to NSAPIs using acknowledged peer-to-peer LLC operation. The primitive is used by the SNDCP layer in the MS following receipt of an SNSM-SEQUENCE.indcation, in order to return the Receive N-PDU number to the SGSN during an ongoing inter-SGSN routeing area update.</Section>
                <Section>Parameter tlliis not needed.</Section>
            </Description>
            <PrimDef>
                <Name>SNSM_SEQUENCE_RES</Name>
                <PrimID Direction="UPLINK" Number="4"/>
                <PrimUsage>
                    <Sender>SNDCP</Sender>
                    <Receiver>SM</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>rec_no</Name>
                </ItemLink>
                <Comment>receive n-pdu number</Comment>
            </PrimItem>
            <History>
                <Date Day="3" Month="8" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="27" Month="4" Year="2000"/>
                <Author>HK</Author>
                <Comment>Added parameter rec_no</Comment>
            </History>
        </Primitive>
    </PrimitivesSection>
    <PrimStructElementsSection>
        <Description>
            <Section>Parameters shall be part of the primitives described below and if applied the parameters shall contain the values specified here. These values are selected to correspond element values used in the air interface protocol.</Section>
        </Description>
        <PrimStructElem>
            <Description>
                <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. The "snsm_" preffix is for distinguishing constants of same denominator.</Section>
            </Description>
            <PrimStructElemDef Type="STRUCT">
                <Name>snsm_qos</Name>
                <Comment>quality of service</Comment>
            </PrimStructElemDef>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>delay</Name>
                </ItemLink>
                <Comment>delay class</Comment>
            </PrimStructElemItem>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>relclass</Name>
                </ItemLink>
                <Comment>reliablility class</Comment>
            </PrimStructElemItem>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>peak</Name>
                </ItemLink>
                <Comment>peak throughput</Comment>
            </PrimStructElemItem>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>preced</Name>
                </ItemLink>
                <Comment>precedence class</Comment>
            </PrimStructElemItem>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">snsm</DocName>
                    <Name>mean</Name>
                </ItemLink>
                <Comment>main throughput</Comment>
            </PrimStructElemItem>
            <History>
                <Date Day="16" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
        </PrimStructElem>
    </PrimStructElementsSection>
    <PrimBasicElementsSection>
        <Description>
            <Section>Parameters shall be part of the primitives described below and if applied the parameters shall contain the values specified here. These values are selected to correspond element values used in the air interface protocol.</Section>
        </Description>
        <PrimBasicElem>
            <Description>
                <Section>This parameter defines the affected network layer service access point identifier. For each SN-PDU the NSAPI is an index to the PDP context of the PDP that is using the service provided by the SNDCP layer.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>nsapi</Name>
                <Type>U8</Type>
                <Comment>network layer service access point identifier</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_nsapi</Name>
            </ValuesLink>
            <History>
                <Date Day="3" Month="3" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. The "snsm_" preffix is for distinguishing constants of same denominator.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>delay</Name>
                <Type>U8</Type>
                <Comment>delay class</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_delay</Name>
            </ValuesLink>
            <History>
                <Date Day="16" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. The "snsm_" preffix is for distinguishing constants of same denominator.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>relclass</Name>
                <Type>U8</Type>
                <Comment>reliablility class</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_relclass</Name>
            </ValuesLink>
            <History>
                <Date Day="16" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. The "snsm_" preffix is for distinguishing constants of same denominator.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>peak</Name>
                <Type>U8</Type>
                <Comment>peak throughput</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_peak</Name>
            </ValuesLink>
            <History>
                <Date Day="16" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. The "snsm_" preffix is for distinguishing constants of same denominator.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>preced</Name>
                <Type>U8</Type>
                <Comment>precedence class</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_preced</Name>
            </ValuesLink>
            <History>
                <Date Day="16" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. The "snsm_" preffix is for distinguishing constants of same denominator.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>mean</Name>
                <Type>U8</Type>
                <Comment>main throughput</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_mean</Name>
            </ValuesLink>
            <History>
                <Date Day="16" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter defines an arbitrary set of applicable network layer service access point identifiers. For each SN-PDU the NSAPI is an index to the PDP context of the PDP that is using the service provided by the SNDCP layer. Field mapping (according to [GSM 04.08, 7.1.3]): Two octets are used for encoding: the first octet is used for NSAPIs 15 to 8, the second octet is used for NSAPIs 7 to 0, in decreasingly order. A bit set to 0 means that the correspnding NSAPI is not to be applied, a bit set to 1 means that the correspnding NSAPI is to be applied.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>nsapi_set</Name>
                <Type>U16</Type>
                <Comment>set of network layer service access point identifiers</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter identifies a point at which LLC services are provided by an LLE to a layer-3 entity. Consequently, SAPI identifies an LLE that processes an LLC frame and also a layer-3 entity that is to receive information carried by the LLC frame.</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">snsm</DocName>
                <Name>VAL_sapi</Name>
            </ValuesLink>
            <History>
                <Date Day="6" Month="3" Year="1999"/>
                <Author>DB</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter identifies the radio priority level to be used by RLC/MAC. The purpose of the radio priority information element is to specify the priority level that the MS shall use at the lower</Section>
                <Section>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. [GSM 04.08, 10.5.7.2]</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>radio_prio</Name>
                <Type>U8</Type>
                <Comment>radio priority</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_radio_prio</Name>
            </ValuesLink>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>The parameter is used to indicate whether a deactivation shall be done locally or not. In case of local deactivation (REL_IND_YES) no LL_XID_REQ will be sent.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>rel_ind</Name>
                <Type>U8</Type>
                <Comment>Release indicator</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_rel_ind</Name>
            </ValuesLink>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
            <History>
                <Date Day="12" Month="10" Year="1999"/>
                <Author>HK</Author>
                <Comment>Changed meaning (assumption)</Comment>
            </History>
            <History>
                <Date Day="26" Month="11" Year="2001"/>
                <Author>HK</Author>
                <Comment>parameter is now used to indicate local/non local</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter is used to indicate the cause for an SNSM_STATUS_REQ, i.e. the error that ocurred in LLC or SNDCP. The pssible values are derived from the SAP specicification for LL, parameter cause.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>status_cause</Name>
                <Type>U16</Type>
                <Comment>Cause of the error</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_status_cause</Name>
            </ValuesLink>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
            <History>
                <Date Day="13" Month="9" Year="2002"/>
                <Author>HK</Author>
                <Comment>Adopt cause concept: remove all but 2 val, switch to U16</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter is used to indicate Receive N-PDU number and/or Send N-PDU number to be set after an SNSM_MODIFY_IND in some cases.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>send_no</Name>
                <Type>U8</Type>
                <Comment>send n-pdu number</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter is used to indicate Receive N-PDU number and/or Send N-PDU number to be set after an SNSM_MODIFY_IND in some cases.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>rec_no</Name>
                <Type>U8</Type>
                <Comment>receive n-pdu number</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="20" Month="4" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter specifies a header compression algorithm that is communicated with the TE, by now only Van Jacobson (see also [GSM 4.65]) is specified. There are two possibilities: "Decompression supported by TE" and "Compression in TE requested".</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>ppp_hc</Name>
                <Type>U8</Type>
                <Comment>header compression of PPP connection</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_ppp_hc</Name>
            </ValuesLink>
            <History>
                <Date Day="6" Month="10" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
            <History>
                <Date Day="8" Month="12" Year="1999"/>
                <Author>STW</Author>
                <Comment>Renamed</Comment>
            </History>
            <History>
                <Date Day="20" Month="4" Year="2000"/>
                <Author>HK</Author>
                <Comment>Renamed values</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter specifies the number of state slots used by Van Jacobson (de-)compression algorithm.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>msid</Name>
                <Type>U8</Type>
                <Comment>max slot identifier</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="6" Month="10" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
            <History>
                <Date Day="8" Month="12" Year="1999"/>
                <Author>STW</Author>
                <Comment>Renamed</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter specifies if data or header compression is requested by GACI (when used in a REQ prim) or will be used (when used in an IND prim). Values are derived from [GSM 4.65, 6.6.2.1.2]. Same parameter is used in SMREG SAP.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>hcomp</Name>
                <Type>U8</Type>
                <Comment>Header compression used/requested</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="6" Month="10" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
            <History>
                <Date Day="19" Month="4" Year="2000"/>
                <Author>HK</Author>
                <Comment>changed _V42_ to _COMP_</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter specifies if data or header compression is requested by GACI (when used in a REQ prim) or will be used (when used in an IND prim). Values are derived from [GSM 4.65, 6.6.2.1.2]. Same parameter is used in SMREG SAP.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>dcomp</Name>
                <Type>U8</Type>
                <Comment>Data compression used/requested</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="6" Month="10" Year="1999"/>
                <Author>HK</Author>
                <Comment>Added</Comment>
            </History>
            <History>
                <Date Day="19" Month="4" Year="2000"/>
                <Author>HK</Author>
                <Comment>changed _V42_ to _COMP_</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter is Condat-specific. It is a unique identifier used by the DTI library.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>dti_linkid</Name>
                <Type>U32</Type>
                <Comment>DTI link identifier</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="12" Month="12" Year="2000"/>
                <Author>MVJ</Author>
                <Comment>Added</Comment>
            </History>
            <History>
                <Date Day="6" Month="6" Year="2001"/>
                <Author>HK</Author>
                <Comment>Copied from MVJ branch</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter is Condat-specific. It is used by the DTI library to find an entity by name.</Section>
                <Section>NOTE: This value is a pointer - U8 * - but due to type limitations it is not passed as such.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>dti_neighbor</Name>
                <Type>U32</Type>
                <Comment>DTI neighbor entity name</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="12" Month="12" Year="2000"/>
                <Author>MVJ</Author>
                <Comment>Added</Comment>
            </History>
            <History>
                <Date Day="6" Month="6" Year="2001"/>
                <Author>HK</Author>
                <Comment>Copied from MVJ branch.</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter is Condat-specific. It is used by the DTI library to find out about the direction of the DTI connection.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>dti_direction</Name>
                <Type>U8</Type>
                <Comment>direction of DTI connection</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">snsm</DocName>
                <Name>VAL_dti_direction</Name>
            </ValuesLink>
            <History>
                <Date Day="13" Month="6" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
    </PrimBasicElementsSection>
    <ValuesSection>
        <Description>
            <Section>This section contains all sets of values that are defined for the SNSM SAP</Section>
        </Description>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_nsapi</Name>
                <Comment>values for nsapi</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SNSM_NSAPI_0</Alias>
                <Comment>escape mechanism for future extensions</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_NSAPI_1</Alias>
                <Comment>Point-To-Multipoint Multicast information</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SNSM_NSAPI_2</Alias>
                <Comment>reserved for future use</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SNSM_NSAPI_3</Alias>
                <Comment>reserved for future use</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>SNSM_NSAPI_4</Alias>
                <Comment>reserved for future use</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>SNSM_NSAPI_5</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias>SNSM_NSAPI_6</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias>SNSM_NSAPI_7</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">8</Value>
                <Alias>SNSM_NSAPI_8</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">9</Value>
                <Alias>SNSM_NSAPI_9</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">10</Value>
                <Alias>SNSM_NSAPI_10</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">11</Value>
                <Alias>SNSM_NSAPI_11</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">12</Value>
                <Alias>SNSM_NSAPI_12</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">13</Value>
                <Alias>SNSM_NSAPI_13</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">14</Value>
                <Alias>SNSM_NSAPI_14</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">15</Value>
                <Alias>SNSM_NSAPI_15</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_peak</Name>
                <Comment>values for peak</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SNSM_PEAK_SUB</Alias>
                <Comment>Subscribed peak throughput</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_PEAK_1K</Alias>
                <Comment>Up to 1 000 octet/s</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SNSM_PEAK_2K</Alias>
                <Comment>Up to 2 000 octet/s</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SNSM_PEAK_4K</Alias>
                <Comment>Up to 4 000 octet/s</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>SNSM_PEAK_8K</Alias>
                <Comment>Up to 8 000 octet/s</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>SNSM_PEAK_16K</Alias>
                <Comment>Up to 16 000 octet/s</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias>SNSM_PEAK_32K</Alias>
                <Comment>Up to 32 000 octet/s</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias>SNSM_PEAK_64K</Alias>
                <Comment>Up to 64 000 octet/s</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">8</Value>
                <Alias>SNSM_PEAK_128K</Alias>
                <Comment>Up to 128 000 octet/s</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">9</Value>
                <Alias>SNSM_PEAK_256K</Alias>
                <Comment>Up to 256 000 octet/s</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_relclass</Name>
                <Comment>values for relclass</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SNSM_RELCLASS_SUB</Alias>
                <Comment>Subscribed reliability class</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_GTP_LLC_RLC_PROT</Alias>
                <Comment>Acknowledged GTP, LLC, and RLC; Protected data</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SNSM_LLC_RLC_PROT</Alias>
                <Comment>Unacknowledged GTP; Acknowledged LLC and RLC, Protected data</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SNSM_RLC_PROT</Alias>
                <Comment>Unacknowledged GTP and LLC; Acknowledged RLC, Protected data</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>SNSM_PROT</Alias>
                <Comment>Unacknowledged GTP, LLC, and RLC, Protected data</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>SNSM_NO_REL</Alias>
                <Comment>Unacknowledged GTP, LLC, and RLC, Unprotected data</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_delay</Name>
                <Comment>values for delay</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SNSM_DELAY_SUB</Alias>
                <Comment>Subscribed delay class</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_DELAY_1</Alias>
                <Comment>Delay class 1</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SNSM_DELAY_2</Alias>
                <Comment>Delay class 2</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SNSM_DELAY_3</Alias>
                <Comment>Delay class 3</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>SNSM_DELAY_4</Alias>
                <Comment>Delay class 4 (best effort)</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_mean</Name>
                <Comment>values for mean</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SNSM_MEAN_SUB</Alias>
                <Comment>Subscribed mean throughput</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_MEAN_100</Alias>
                <Comment>100 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SNSM_MEAN_200</Alias>
                <Comment>200 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SNSM_MEAN_500</Alias>
                <Comment>500 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>SNSM_MEAN_1K</Alias>
                <Comment>1 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>SNSM_MEAN_2K</Alias>
                <Comment>2 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias>SNSM_MEAN_5K</Alias>
                <Comment>5 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias>SNSM_MEAN_10K</Alias>
                <Comment>10 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">8</Value>
                <Alias>SNSM_MEAN_20K</Alias>
                <Comment>20 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">9</Value>
                <Alias>SNSM_MEAN_50K</Alias>
                <Comment>50 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">10</Value>
                <Alias>SNSM_MEAN_100K</Alias>
                <Comment>100 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">11</Value>
                <Alias>SNSM_MEAN_200K</Alias>
                <Comment>200 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">12</Value>
                <Alias>SNSM_MEAN_500K</Alias>
                <Comment>500 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">13</Value>
                <Alias>SNSM_MEAN_1M</Alias>
                <Comment>1 000 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">14</Value>
                <Alias>SNSM_MEAN_2M</Alias>
                <Comment>2 000 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">15</Value>
                <Alias>SNSM_MEAN_5M</Alias>
                <Comment>5 000 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">16</Value>
                <Alias>SNSM_MEAN_10M</Alias>
                <Comment>10 000 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">17</Value>
                <Alias>SNSM_MEAN_20M</Alias>
                <Comment>20 000 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">18</Value>
                <Alias>SNSM_MEAN_50M</Alias>
                <Comment>50 000 000 octet/h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">31</Value>
                <Alias>SNSM_MEAN_BEST</Alias>
                <Comment>Best effort</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_preced</Name>
                <Comment>values for preced</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SNSM_PRECED_SUB</Alias>
                <Comment>Subscribed precedence</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_PRIO_HIGH</Alias>
                <Comment>High priority</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SNSM_PRIO_NORM</Alias>
                <Comment>Normal priority</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SNSM_PRIO_LOW</Alias>
                <Comment>Low priority</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_sapi</Name>
                <Comment>values for sapi</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_LLC_SAPI_1</Alias>
                <Comment>SAP for GMM</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SNSM_LLC_SAPI_3</Alias>
                <Comment>SAP 1 for SNDCP</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>SNSM_LLC_SAPI_5</Alias>
                <Comment>SAP 2 for SNDCP</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias>SNSM_LLC_SAPI_7</Alias>
                <Comment>SAP for SMS</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">9</Value>
                <Alias>SNSM_LLC_SAPI_9</Alias>
                <Comment>SAP 3 for SNDCP</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">11</Value>
                <Alias>SNSM_LLC_SAPI_11</Alias>
                <Comment>SAP 4 for SNDCP</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_radio_prio</Name>
                <Comment>values for radio_prio</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_RADIO_PRIO_1</Alias>
                <Comment>radio priority 1 (highest)</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>SNSM_RADIO_PRIO_2</Alias>
                <Comment>radio priority 2</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>SNSM_RADIO_PRIO_3</Alias>
                <Comment>radio priority 3</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>SNSM_RADIO_PRIO_4</Alias>
                <Comment>radio priority 4 (lowest)</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_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="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_status_cause</Name>
                <Comment>values for status_cause</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="HEX">5100</Value>
                <Alias>SNSM_RELCS_INVALID_XID</Alias>
                <Comment>invalid XID response</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">5101</Value>
                <Alias>SNSM_RELCS_NO_PEER_RES</Alias>
                <Comment>no peer response</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_ppp_hc</Name>
                <Comment>values for ppp_hc</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SNSM_VAN_NOT_USED</Alias>
                <Comment>Van Jacobson is not supported</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_VAN_USED</Alias>
                <Comment>Van Jacobson is supported</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
        <Values>
            <Description>
                <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section>
            </Description>
            <ValuesDef>
                <Name>VAL_dti_direction</Name>
                <Comment>values for dti_direction</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SNSM_HOME</Alias>
                <Comment>mapped to HOME from dti.h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SNSM_NEIGHBOR</Alias>
                <Comment>mapped to NEIGHBOR from dti.h</Comment>
            </ValuesItem>
            <History>
                <Date Day="4" Month="11" Year="2003"/>
                <Author>doc2XML</Author>
                <Comment>Initial</Comment>
            </History>
        </Values>
    </ValuesSection>
</SAP>