<?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">sn</DocName>
        <DocNum Number="110" 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="12" 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 Version number</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="003" Year="99"/>
            <Date Day="2" Month="6" Year="2000"/>
            <Author>Harald</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Krug Version number for S3</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="004" Year="99"/>
            <Date Day="6" Month="10" Year="2000"/>
            <Author>Harald</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Krug Matched data_inds to cci_decomp_ind</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="005" Year="99"/>
            <Date Day="26" Month="3" Year="2001"/>
            <Author>Harald</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Krug Add SN_MODIFICATION_IND</Comment>
        </DocHistory>
        <DocHistory>
            <DocVersion Number="006" Year="99"/>
            <Date Day="8" Month="10" Year="2001"/>
            <Author>Harald</Author>
            <DocStatus State="BEING_PROCESSED"/>
            <Comment>Krug Add SN_SWITCH_REQ, _CNF</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.7.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 SN SAP</Section>
        </Description>
        <Constant>
            <Alias>MAX_PARAM_NUMBER</Alias>
            <Value ValueType="DEC">4</Value>
            <Comment>Maximal number of parameters per compressor unit</Comment>
        </Constant>
        <Constant>
            <Alias>MAX_COMP_NUMBER</Alias>
            <Value ValueType="DEC">3</Value>
            <Comment>Currently there are 3 PCOMP values for V.42bis</Comment>
        </Constant>
        <Constant>
            <Alias>MAX_ENT_NUMBER</Alias>
            <Value ValueType="DEC">1</Value>
            <Comment>There is 1 data compression entity currently and 1 header compression entity.</Comment>
        </Constant>
        <History>
            <Date Day="3" Month="3" Year="1999"/>
            <Author>HK</Author>
            <Comment>Initial</Comment>
        </History>
        <History>
            <Date Day="11" Month="4" Year="2000"/>
            <Author>HK</Author>
            <Comment>Initial</Comment>
        </History>
    </ConstantsSection>
    <PrimitivesSection PrimIDType="BIT16" SAPid="40">
        <Description>
            <Section>This section contains all primitives that are defined for the SN SAP</Section>
        </Description>
        <Primitive>
            <Description>
                <Section>SN_MODIFICATION_IND is used to negotiate header compression again. If the VanJacobson header compression is done in the TE, and during a context modification the header compression is switched off or the numer of state slots is changed then this primitive is sent to GACI and from there to PPP (as PPP_MODIFICATION_REQ). No SN_MODIFICATION_RES is expected. If the TE does not agree to the given parameters then the context is deactivated.</Section>
                <Section>The parameter ppp_hc indicates the desired header compression. The parameter msid is only valid if the parameter ppp_hc indicates Van Jacobson header compression.</Section>
            </Description>
            <PrimDef>
                <Name>SN_MODIFICATION_IND</Name>
                <PrimID Direction="DOWNLINK" Number="8"/>
                <PrimUsage>
                    <Sender>SNDCP</Sender>
                    <Receiver>PDP</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>ppp_hc</Name>
                </ItemLink>
                <Comment>header compression of PPP connection</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>msid</Name>
                </ItemLink>
                <Comment>max slot identifier</Comment>
            </PrimItem>
            <History>
                <Date Day="26" Month="3" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>This primitive is not mentioned in the specifications. It can be used to get information about the amount of transferred data. Parameter 'nsapi' indicates the affected nsapi. If parameter 'reset'  is set to SN_RESET_YES, then the last values of all counters will be sent with the resulting SN_COUNT_CNF and all counters for the affected nsapi will be set to 0. If parameter 'reset' is set to SN_RESET_NO then then the last values of all counters will be sent with the resulting SN_COUNT_CNF.</Section>
            </Description>
            <PrimDef>
                <Name>SN_COUNT_REQ</Name>
                <PrimID Direction="UPLINK" Number="8"/>
                <PrimUsage>
                    <Sender>PDP</Sender>
                    <Receiver>Relay</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>reset</Name>
                </ItemLink>
                <Comment>shall counters be reset</Comment>
            </PrimItem>
            <History>
                <Date Day="2" Month="8" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>This primitive is not mentioned in the specifications. It can be used to get information about the amount of transferred data. Parameter 'nsapi' indicates the affected nsapi. Parameter 'octets_uplink' indicates the number of transferred octets uplink. Only payload without SN, LLC, RLC headers is computed. Parameter 'octets_downlink' indicates the number of transferred octets downlink. Parameter 'packets_uplink' indicates the number of transferred packets uplink. Parameter 'packets_downlink' indicates the number of transferred packets downlink.</Section>
            </Description>
            <PrimDef>
                <Name>SN_COUNT_CNF</Name>
                <PrimID Direction="DOWNLINK" Number="9"/>
                <PrimUsage>
                    <Sender>SNDCP</Sender>
                    <Receiver>PDP</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>octets_uplink</Name>
                </ItemLink>
                <Comment>octets uplink</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>octets_downlink</Name>
                </ItemLink>
                <Comment>octets  downlink</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>packets_uplink</Name>
                </ItemLink>
                <Comment>packets uplink</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>packets_downlink</Name>
                </ItemLink>
                <Comment>packets downlink</Comment>
            </PrimItem>
            <History>
                <Date Day="2" Month="8" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>To enable change of dti properties as linkid, neighbor or direction this primitive is sent to SNDCP. SNDCP will then close the existing dti connection for the given nsapi and open a new one with the given values..</Section>
            </Description>
            <PrimDef>
                <Name>SN_SWITCH_REQ</Name>
                <PrimID Direction="UPLINK" Number="9"/>
                <PrimUsage>
                    <Sender>PDP</Sender>
                    <Receiver>Relay</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>dti_linkid</Name>
                </ItemLink>
                <Comment>dti linkid</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>dti_neighbor</Name>
                </ItemLink>
                <Comment>dti neighbor</Comment>
            </PrimItem>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>dti_direction</Name>
                </ItemLink>
                <Comment>dti direction</Comment>
            </PrimItem>
            <History>
                <Date Day="8" Month="10" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </Primitive>
        <Primitive>
            <Description>
                <Section>SNDCP confirms that it has closed the existing dti connection for the given nsai and the opened a new dti connection with the values given in the SN_SWITCH_REQ.</Section>
            </Description>
            <PrimDef>
                <Name>SN_SWITCH_CNF</Name>
                <PrimID Direction="DOWNLINK" Number="10"/>
                <PrimUsage>
                    <Sender>SNDCP</Sender>
                    <Receiver>PDP</Receiver>
                </PrimUsage>
            </PrimDef>
            <PrimItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>nsapi</Name>
                </ItemLink>
                <Comment>network layer service access point identifier</Comment>
            </PrimItem>
            <History>
                <Date Day="8" Month="10" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</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>This parameter defines a list of data descriptors. It is implemented as a pointer to the first generic data descriptor.</Section>
            </Description>
            <PrimStructElemDef Type="STRUCT">
                <Name>desc_list2</Name>
                <Comment>list of generic data descriptors</Comment>
            </PrimStructElemDef>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>list_len</Name>
                </ItemLink>
                <Comment>length in octets of whole data</Comment>
            </PrimStructElemItem>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>first</Name>
                </ItemLink>
                <Comment>pointer to  generic data descriptors</Comment>
            </PrimStructElemItem>
            <History>
                <Date Day="15" Month="3" Year="1999"/>
                <Author>DB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="22" Month="7" Year="1999"/>
                <Author>HK</Author>
                <Comment>Changed from array to pointer to first desc</Comment>
            </History>
        </PrimStructElem>
        <PrimStructElem>
            <Description>
                <Section>This parameter contains either a L3-PDU or layer-3 parameters that are negotiated between the peer entities.</Section>
            </Description>
            <PrimStructElemDef Type="STRUCT">
                <Name>sdu</Name>
                <Comment>service data unit</Comment>
            </PrimStructElemDef>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>l_buf</Name>
                </ItemLink>
                <Comment>length of content in bit</Comment>
            </PrimStructElemItem>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>o_buf</Name>
                </ItemLink>
                <Comment>offset of content in bit</Comment>
            </PrimStructElemItem>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>buf</Name>
                </ItemLink>
                <Control>[1]</Control>
                <Comment>buffer content</Comment>
            </PrimStructElemItem>
            <History>
                <Date Day="25" Month="6" Year="1999"/>
                <Author>ID</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimStructElem>
        <PrimStructElem>
            <Description>
                <Section>Used to identify a PDU going from SNDCP to CCI and back to SNDCP. In case of uplink transfer (CCI_DECOMP_IND) SNDCP provides 'ref_nsapi' and 'ref_npdu_num'. The segment number 'ref_seg_num' has to be set by CCI. The reference shall then copied to the CCI_COMP_IND going back to SNDCP.</Section>
                <Section>In case of downlink transfer CCI just passes the pdu_ref from the incoming CCI_DECOMP_REQs to the one outgoing CCI_DECOMP_IND, ignoring the 'ref_seg_num' field.</Section>
                <Section>Since the DATA primitives are N-PDUs, the 'ref_seg_num' field is not valid for them. It will only be evaluated or set for the TRANSFER primitives (because they represent segments).</Section>
            </Description>
            <PrimStructElemDef Type="STRUCT">
                <Name>reserved_data_ind1</Name>
                <Comment>to the segment to be confirmed</Comment>
            </PrimStructElemDef>
            <PrimStructElemDef Type="STRUCT">
                <Name>reserved_unitdata_ind1</Name>
                <Comment>to the segment to be confirmed</Comment>
            </PrimStructElemDef>
            <PrimStructElemDef Type="STRUCT">
                <Name>reserved_data_req2</Name>
                <Comment>to the segment to be confirmed</Comment>
            </PrimStructElemDef>
            <PrimStructElemDef Type="STRUCT">
                <Name>reserved_unitdata_req2</Name>
                <Comment>to the segment to be confirmed</Comment>
            </PrimStructElemDef>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>ref_nsapi</Name>
                </ItemLink>
                <Comment>ref_nsapi</Comment>
            </PrimStructElemItem>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>ref_npdu_num</Name>
                </ItemLink>
                <Comment>ref_npdu_num</Comment>
            </PrimStructElemItem>
            <PrimStructElemItem Presentation="MANDATORY">
                <ItemLink>
                    <DocName DocType="SAP">sn</DocName>
                    <Name>ref_seg_num</Name>
                </ItemLink>
                <Comment>ref_seg_num</Comment>
            </PrimStructElemItem>
            <History>
                <Date Day="17" Month="3" Year="1999"/>
                <Author>DB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="18" Month="6" Year="1999"/>
                <Author>DB</Author>
                <Comment>Modified description to reflect new memory management</Comment>
            </History>
            <History>
                <Date Day="1" Month="3" Year="2000"/>
                <Author>HK</Author>
                <Comment>Changed to struct</Comment>
            </History>
            <History>
                <Date Day="21" Month="6" Year="2000"/>
                <Author>DB</Author>
                <Comment>Included reserved_unitdata_req1</Comment>
            </History>
            <History>
                <Date Day="29" Month="6" Year="2000"/>
                <Author>HK</Author>
                <Comment>Imported from LL SAP.</Comment>
            </History>
            <History>
                <Date Day="7" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Changed ref_npdu_num from UBYTE to USHORT.</Comment>
            </History>
            <History>
                <Date Day="1" Month="8" Year="2000"/>
                <Author>HK</Author>
                <Comment>Modified comment.</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">sn</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>This parameter defines a list of data descriptors. It is implemented as a pointer to the first generic data descriptor.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>list_len</Name>
                <Type>U16</Type>
                <Comment>length in octets of whole data</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="15" Month="3" Year="1999"/>
                <Author>DB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="22" Month="7" Year="1999"/>
                <Author>HK</Author>
                <Comment>Changed from array to pointer to first desc</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter defines a list of data descriptors. It is implemented as a pointer to the first generic data descriptor.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>first</Name>
                <Type>U32</Type>
                <Comment>pointer to  generic data descriptors</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="15" Month="3" Year="1999"/>
                <Author>DB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="22" Month="7" Year="1999"/>
                <Author>HK</Author>
                <Comment>Changed from array to pointer to first desc</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter indicates the type of PDP packet.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>p_id</Name>
                <Type>U8</Type>
                <Comment>protocol identifier</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">sn</DocName>
                <Name>VAL_p_id</Name>
            </ValuesLink>
            <History>
                <Date Day="20" Month="9" Year="1999"/>
                <Author>STW</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter contains either a L3-PDU or layer-3 parameters that are negotiated between the peer entities.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>l_buf</Name>
                <Type>U16</Type>
                <Comment>length of content in bit</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="25" Month="6" Year="1999"/>
                <Author>ID</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter contains either a L3-PDU or layer-3 parameters that are negotiated between the peer entities.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>o_buf</Name>
                <Type>U16</Type>
                <Comment>offset of content in bit</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="25" Month="6" Year="1999"/>
                <Author>ID</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter contains either a L3-PDU or layer-3 parameters that are negotiated between the peer entities.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>buf</Name>
                <Type>U8</Type>
                <Comment>buffer content</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="25" Month="6" Year="1999"/>
                <Author>ID</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Parameter reserved contains reserved octets for CCI_UNITDATA_IND. This is necessary to align this primitive with CCI_DATA_CNF.</Section>
                <Section>Used in: CCI_UNITDATA_IND.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>reserved_data_ind2</Name>
                <Type>U8</Type>
                <Comment>reserved octets</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="23" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Parameter reserved contains reserved octets for CCI_UNITDATA_IND. This is necessary to align this primitive with CCI_DATA_CNF.</Section>
                <Section>Used in: CCI_UNITDATA_IND.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>reserved_unitdata_ind2</Name>
                <Type>U8</Type>
                <Comment>reserved octets</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="23" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Parameter reserved contains reserved octets for CCI_UNITDATA_IND. This is necessary to align this primitive with CCI_DATA_CNF.</Section>
                <Section>Used in: CCI_UNITDATA_IND.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>reserved_data_req1</Name>
                <Type>U8</Type>
                <Comment>reserved octets</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="23" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Parameter reserved contains reserved octets for CCI_UNITDATA_IND. This is necessary to align this primitive with CCI_DATA_CNF.</Section>
                <Section>Used in: CCI_UNITDATA_IND.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>reserved_data_req3</Name>
                <Type>U8</Type>
                <Comment>reserved octets</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="23" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Parameter reserved contains reserved octets for CCI_UNITDATA_IND. This is necessary to align this primitive with CCI_DATA_CNF.</Section>
                <Section>Used in: CCI_UNITDATA_IND.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>reserved_unitdata_req1</Name>
                <Type>U8</Type>
                <Comment>reserved octets</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="23" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Parameter reserved contains reserved octets for CCI_UNITDATA_IND. This is necessary to align this primitive with CCI_DATA_CNF.</Section>
                <Section>Used in: CCI_UNITDATA_IND.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>reserved_unitdata_req3</Name>
                <Type>U8</Type>
                <Comment>reserved octets</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="23" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Used to identify a PDU going from SNDCP to CCI and back to SNDCP. In case of uplink transfer (CCI_DECOMP_IND) SNDCP provides 'ref_nsapi' and 'ref_npdu_num'. The segment number 'ref_seg_num' has to be set by CCI. The reference shall then copied to the CCI_COMP_IND going back to SNDCP.</Section>
                <Section>In case of downlink transfer CCI just passes the pdu_ref from the incoming CCI_DECOMP_REQs to the one outgoing CCI_DECOMP_IND, ignoring the 'ref_seg_num' field.</Section>
                <Section>Since the DATA primitives are N-PDUs, the 'ref_seg_num' field is not valid for them. It will only be evaluated or set for the TRANSFER primitives (because they represent segments).</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>ref_nsapi</Name>
                <Type>U8</Type>
                <Comment>ref_nsapi</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="17" Month="3" Year="1999"/>
                <Author>DB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="18" Month="6" Year="1999"/>
                <Author>DB</Author>
                <Comment>Modified description to reflect new memory management</Comment>
            </History>
            <History>
                <Date Day="1" Month="3" Year="2000"/>
                <Author>HK</Author>
                <Comment>Changed to struct</Comment>
            </History>
            <History>
                <Date Day="21" Month="6" Year="2000"/>
                <Author>DB</Author>
                <Comment>Included reserved_unitdata_req1</Comment>
            </History>
            <History>
                <Date Day="29" Month="6" Year="2000"/>
                <Author>HK</Author>
                <Comment>Imported from LL SAP.</Comment>
            </History>
            <History>
                <Date Day="7" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Changed ref_npdu_num from UBYTE to USHORT.</Comment>
            </History>
            <History>
                <Date Day="1" Month="8" Year="2000"/>
                <Author>HK</Author>
                <Comment>Modified comment.</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Used to identify a PDU going from SNDCP to CCI and back to SNDCP. In case of uplink transfer (CCI_DECOMP_IND) SNDCP provides 'ref_nsapi' and 'ref_npdu_num'. The segment number 'ref_seg_num' has to be set by CCI. The reference shall then copied to the CCI_COMP_IND going back to SNDCP.</Section>
                <Section>In case of downlink transfer CCI just passes the pdu_ref from the incoming CCI_DECOMP_REQs to the one outgoing CCI_DECOMP_IND, ignoring the 'ref_seg_num' field.</Section>
                <Section>Since the DATA primitives are N-PDUs, the 'ref_seg_num' field is not valid for them. It will only be evaluated or set for the TRANSFER primitives (because they represent segments).</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>ref_npdu_num</Name>
                <Type>U16</Type>
                <Comment>ref_npdu_num</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="17" Month="3" Year="1999"/>
                <Author>DB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="18" Month="6" Year="1999"/>
                <Author>DB</Author>
                <Comment>Modified description to reflect new memory management</Comment>
            </History>
            <History>
                <Date Day="1" Month="3" Year="2000"/>
                <Author>HK</Author>
                <Comment>Changed to struct</Comment>
            </History>
            <History>
                <Date Day="21" Month="6" Year="2000"/>
                <Author>DB</Author>
                <Comment>Included reserved_unitdata_req1</Comment>
            </History>
            <History>
                <Date Day="29" Month="6" Year="2000"/>
                <Author>HK</Author>
                <Comment>Imported from LL SAP.</Comment>
            </History>
            <History>
                <Date Day="7" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Changed ref_npdu_num from UBYTE to USHORT.</Comment>
            </History>
            <History>
                <Date Day="1" Month="8" Year="2000"/>
                <Author>HK</Author>
                <Comment>Modified comment.</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Used to identify a PDU going from SNDCP to CCI and back to SNDCP. In case of uplink transfer (CCI_DECOMP_IND) SNDCP provides 'ref_nsapi' and 'ref_npdu_num'. The segment number 'ref_seg_num' has to be set by CCI. The reference shall then copied to the CCI_COMP_IND going back to SNDCP.</Section>
                <Section>In case of downlink transfer CCI just passes the pdu_ref from the incoming CCI_DECOMP_REQs to the one outgoing CCI_DECOMP_IND, ignoring the 'ref_seg_num' field.</Section>
                <Section>Since the DATA primitives are N-PDUs, the 'ref_seg_num' field is not valid for them. It will only be evaluated or set for the TRANSFER primitives (because they represent segments).</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>ref_seg_num</Name>
                <Type>U8</Type>
                <Comment>ref_seg_num</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="17" Month="3" Year="1999"/>
                <Author>DB</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="18" Month="6" Year="1999"/>
                <Author>DB</Author>
                <Comment>Modified description to reflect new memory management</Comment>
            </History>
            <History>
                <Date Day="1" Month="3" Year="2000"/>
                <Author>HK</Author>
                <Comment>Changed to struct</Comment>
            </History>
            <History>
                <Date Day="21" Month="6" Year="2000"/>
                <Author>DB</Author>
                <Comment>Included reserved_unitdata_req1</Comment>
            </History>
            <History>
                <Date Day="29" Month="6" Year="2000"/>
                <Author>HK</Author>
                <Comment>Imported from LL SAP.</Comment>
            </History>
            <History>
                <Date Day="7" Month="7" Year="2000"/>
                <Author>HK</Author>
                <Comment>Changed ref_npdu_num from UBYTE to USHORT.</Comment>
            </History>
            <History>
                <Date Day="1" Month="8" Year="2000"/>
                <Author>HK</Author>
                <Comment>Modified comment.</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>This parameter indicates which header compression algorithm is used by the TE or should used by the TE.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>ppp_hc</Name>
                <Type>U8</Type>
                <Comment>header compression of PPP connection</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">sn</DocName>
                <Name>VAL_ppp_hc</Name>
            </ValuesLink>
            <History>
                <Date Day="26" Month="3" Year="2001"/>
                <Author>HK</Author>
                <Comment>Copied from PPP</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>The Max-Slot-Identifier indicates the number of slots used by the Van Jacobson header compression algorithm. This parameter is only valid, if the ppp_hc parameter indicates that Van Jacobson header compression is used.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>msid</Name>
                <Type>U8</Type>
                <Comment>max slot identifier</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="26" Month="3" Year="2001"/>
                <Author>HK</Author>
                <Comment>Copied from PPP</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>If parameter 'reset'  is set to SN_RESET_YES, then the last values of all counters will be sent with the resulting SN_COUNT_CNF and all counters for the affected nsapi will be set to 0. If parameter 'reset' is set to SN_RESET_NO then then the last values of all counters will be sent with the resulting SN_COUNT_CNF..</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>reset</Name>
                <Type>U8</Type>
                <Comment>reset flag</Comment>
            </PrimBasicElemDef>
            <ValuesLink>
                <DocName DocType="SAP">sn</DocName>
                <Name>VAL_reset</Name>
            </ValuesLink>
            <History>
                <Date Day="4" Month="8" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Number of transferred octets uplink.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>octets_uplink</Name>
                <Type>U32</Type>
                <Comment>octets uplink</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="4" Month="8" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Number of transferred octets downlink.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>octets_downlink</Name>
                <Type>U32</Type>
                <Comment>octets downlink</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="4" Month="8" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Number of transferred packets uplink.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>packets_uplink</Name>
                <Type>U32</Type>
                <Comment>packets uplink</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="4" Month="8" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
        </PrimBasicElem>
        <PrimBasicElem>
            <Description>
                <Section>Number of transferred packets downlink.</Section>
            </Description>
            <PrimBasicElemDef>
                <Name>packets_downlink</Name>
                <Type>U32</Type>
                <Comment>packets downlink</Comment>
            </PrimBasicElemDef>
            <History>
                <Date Day="4" Month="8" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</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>
            <History>
                <Date Day="8" Month="10" Year="2001"/>
                <Author>HK</Author>
                <Comment>Copied from SMREG doc</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>
            <History>
                <Date Day="8" Month="10" Year="2001"/>
                <Author>HK</Author>
                <Comment>Copied from SMREG doc</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">sn</DocName>
                <Name>VAL_dti_direction</Name>
            </ValuesLink>
            <History>
                <Date Day="13" Month="6" Year="2001"/>
                <Author>HK</Author>
                <Comment>Initial</Comment>
            </History>
            <History>
                <Date Day="8" Month="10" Year="2001"/>
                <Author>HK</Author>
                <Comment>Copied from SMREG doc</Comment>
            </History>
            <History>
                <Date Day="27" Month="11" Year="2001"/>
                <Author>HK</Author>
                <Comment>Changed names and values</Comment>
            </History>
        </PrimBasicElem>
    </PrimBasicElementsSection>
    <ValuesSection>
        <Description>
            <Section>This section contains all sets of values that are defined for the SN 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>NSAPI_0</Alias>
                <Comment>escape mechanism for future extensions</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>NSAPI_1</Alias>
                <Comment>Point-To-Multipoint Multicast information</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">2</Value>
                <Alias>NSAPI_2</Alias>
                <Comment>reserved for future use</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">3</Value>
                <Alias>NSAPI_3</Alias>
                <Comment>reserved for future use</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">4</Value>
                <Alias>NSAPI_4</Alias>
                <Comment>reserved for future use</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">5</Value>
                <Alias>NSAPI_5</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">6</Value>
                <Alias>NSAPI_6</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">7</Value>
                <Alias>NSAPI_7</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">8</Value>
                <Alias>NSAPI_8</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">9</Value>
                <Alias>NSAPI_9</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">10</Value>
                <Alias>NSAPI_10</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">11</Value>
                <Alias>NSAPI_11</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">12</Value>
                <Alias>NSAPI_12</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">13</Value>
                <Alias>NSAPI_13</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">14</Value>
                <Alias>NSAPI_14</Alias>
                <Comment>dynamically allocated NSAPI value</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">15</Value>
                <Alias>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_p_id</Name>
                <Comment>values for p_id</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="HEX">21</Value>
                <Alias>PPP_PID_IP</Alias>
                <Comment>simple ip packet</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">2D</Value>
                <Alias>PPP_PID_CTCP</Alias>
                <Comment>Van Jacobson compressed TCP/IP header</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="HEX">2F</Value>
                <Alias>PPP_PID_UTCP</Alias>
                <Comment>Van Jacobson uncompressed TCP/IP header</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>SN_HC_OFF</Alias>
                <Comment>no header compression</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SN_HC_VJ</Alias>
                <Comment>Van Jacobson header compression</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_reset</Name>
                <Comment>values for reset</Comment>
            </ValuesDef>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SN_RESET_NO</Alias>
                <Comment>no reset</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">1</Value>
                <Alias>SN_RESET_YES</Alias>
                <Comment>reset</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>SN_HOME</Alias>
                <Comment>mapped to HOME from dti.h</Comment>
            </ValuesItem>
            <ValuesItem>
                <Value ValueType="DEC">0</Value>
                <Alias>SN_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>
