FreeCalypso > hg > tcs211-l1-reconst
view g23m/condat/ms/doc/sap/smreg.sap @ 7:706e64623330
pdt_2091.mak patched for successful build
author | Space Falcon <falcon@ivan.Harhan.ORG> |
---|---|
date | Mon, 01 Jun 2015 07:16:43 +0000 |
parents | 509db1a7b7b8 |
children |
line wrap: on
line source
<?xml version="1.0" encoding="UTF-8"?> <!-- edited with SAPE SAP Editor --> <SAP xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="sap.xsd"> <DocInfoSection> <DocName DocType="SAP">smreg</DocName> <DocNum Number="108" 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="7" 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 dcomp/hcomp 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 ppp_hc values</Comment> </DocHistory> <DocHistory> <DocVersion Number="004" Year="99"/> <Date Day="2" Month="6" Year="2000"/> <Author>Harald</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Krug S3, changed order of hcomp, dcomp in SMREG_ACTIVATE_CNF</Comment> </DocHistory> <DocHistory> <DocVersion Number="005" Year="99"/> <Date Day="2" Month="8" Year="2000"/> <Author>Harald</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Krug Added QoS constants.</Comment> </DocHistory> <DocHistory> <DocVersion Number="006" Year="99"/> <Date Day="8" Month="2" Year="2001"/> <Author>Harald</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Krug Modify MT activation.</Comment> </DocHistory> <DocHistory> <DocVersion Number="007" Year="99"/> <Date Day="26" Month="4" Year="2002"/> <Author>Harald</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Krug Skip anonymous access.</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 SMREG SAP</Section> </Description> <Constant> <Alias>COMP_USED</Alias> <Value ValueType="DEC">0</Value> <Comment>Compression requested/used for Requested Compression</Comment> </Constant> <Constant> <Alias>COMP_NOT_USED</Alias> <Value ValueType="DEC">1</Value> <Comment>Compression not requested/used for Requested Compression</Comment> </Constant> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </ConstantsSection> <PrimitivesSection PrimIDType="BIT16" SAPid="38"> <Description> <Section>This section contains all primitives that are defined for the SMREG SAP</Section> </Description> <Primitive> <Description> <Section>The MS initiates a PDP context activation. SM is requested to send the ACTIVATE PDP CONTEXT REQUEST message to the network. The PDP context is pending activation. [HK: the parameters mentioned in [GSM 4.07] don't seem to be complete, the address is missing, and the purpose of the "Data Mode" parameter in the same document is not mentioned. So a different set of parameters is assumed that hopefully fits the requirements of the activation procedure.]. [HK: the parameters 1."te_decomp", 2."slots", 3."dcomp" and 4."hcomp" are implementation dependant and are used for 1. The capability and will of the TE to apply the Van Jacobson header compression/decompression algorithm, 2. The number of state slots proposed by the TE for that purpose, 3. The AT command based information that the user wishes to use data compression, 4. The same for header compression.]</Section> </Description> <PrimDef> <Name>SMREG_PDP_ACTIVATE_REQ</Name> <PrimID Direction="UPLINK" Number="0"/> <PrimUsage> <Sender>ACI</Sender> <Receiver>SM</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>direc</Name> </ItemLink> <Comment>initiator</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>ppp_hc</Name> </ItemLink> <Comment>header compression of PPP connection</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>msid</Name> </ItemLink> <Comment>max slot identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>dcomp</Name> </ItemLink> <Comment>Data compression used/direction</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>hcomp</Name> </ItemLink> <Comment>Header compression used/direction</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>pdp_type</Name> </ItemLink> <Comment>Pdp type</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_qos</Name> </ItemLink> <Comment>Requested quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_min_qos</Name> </ItemLink> <Comment>Minimum requested QoS</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_nsapi</Name> </ItemLink> <Comment>network layer service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_ti</Name> </ItemLink> <Comment>transaction identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>pdp_address</Name> </ItemLink> <Comment>PDP address</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_apn</Name> </ItemLink> <Comment>Access point name</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>dti_linkid</Name> </ItemLink> <Comment>DTI link-id</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>dti_neighbor</Name> </ItemLink> <Comment>DTI neighbor entity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>dti_direction</Name> </ItemLink> <Comment>DTI direction</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>sdu</Name> </ItemLink> <Comment>PDP config options</Comment> </PrimItem> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> <History> <Date Day="21" Month="9" Year="1999"/> <Author>HK</Author> <Comment>Changed al parameters, params in ETSI doc seem to be rubbish</Comment> </History> <History> <Date Day="8" Month="12" Year="1999"/> <Author>STW</Author> <Comment>Compression done in TE and state slots parameter renamed</Comment> </History> <History> <Date Day="9" Month="2" Year="2001"/> <Author>HK</Author> <Comment>Add smreg_ti</Comment> </History> <History> <Date Day="7" Month="6" Year="2001"/> <Author>HK</Author> <Comment>Add 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>The MS initiated PDP context activation succeeded. The network confirmd the PDP context activation, i.e. the ACTIVATE_PDPCONTEXT_ACCEPT message was received from the network. Then SM has ordered SNDCP to establish the needed LLC links. The PDP context is active.</Section> </Description> <PrimDef> <Name>SMREG_PDP_ACTIVATE_CNF</Name> <PrimID Direction="DOWNLINK" Number="0"/> <PrimUsage> <Sender>SM</Sender> <Receiver>ACI</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>ppp_hc</Name> </ItemLink> <Comment>header compression of PPP connection</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>msid</Name> </ItemLink> <Comment>max slot identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>dcomp</Name> </ItemLink> <Comment>Data compression requested</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>hcomp</Name> </ItemLink> <Comment>Header compression requested</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>pdp_type</Name> </ItemLink> <Comment>PDP type</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_qos</Name> </ItemLink> <Comment>quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_nsapi</Name> </ItemLink> <Comment>network layer service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>pdp_address</Name> </ItemLink> <Comment>PDP address</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>sdu</Name> </ItemLink> <Comment>PDP config options</Comment> </PrimItem> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>The PDP context activation failed, the PDP context is not activated. One reason for failure is that the network rejected the activation attempt, which means the ACTIVATE_PDP_CONTEXT_FAILURE message was received. Another reason is i.e. that ut was not possible to establish the needed LLC links.</Section> <Section>[HK: the parameter "smreg_nsapi" is not mentioned in [GSM 4.07] but seems to be useful to distinguish between the contexts IF the activation of only one context is affected.]</Section> </Description> <PrimDef> <Name>SMREG_PDP_ACTIVATE_REJ</Name> <PrimID Direction="DOWNLINK" Number="1"/> <PrimUsage> <Sender>SM</Sender> <Receiver>ACI</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_cause</Name> </ItemLink> <Comment>Cause of rejection</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_nsapi</Name> </ItemLink> <Comment>network layer service access point identifier</Comment> </PrimItem> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> <History> <Date Day="21" Month="9" Year="1999"/> <Author>HK</Author> <Comment>added type and address param to distinguish between contexts</Comment> </History> </Primitive> <Primitive> <Description> <Section>The network asked for a PDP context activation. The REQUEST_PDP_CONTEXT_ACTIVATION message was received from the network. The MS reacts either by initiating a new PDP context or by rejecting the network's request.</Section> </Description> <PrimDef> <Name>SMREG_PDP_ACTIVATE_IND</Name> <PrimID Direction="DOWNLINK" Number="2"/> <PrimUsage> <Sender>SM</Sender> <Receiver>ACI</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_qos</Name> </ItemLink> <Comment>quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_ti</Name> </ItemLink> <Comment>transaction identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_apn</Name> </ItemLink> <Comment>access point name</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>pdp_type</Name> </ItemLink> <Comment>Pdp type</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>pdp_address</Name> </ItemLink> <Comment>PDP address</Comment> </PrimItem> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> <History> <Date Day="9" Month="6" Year="2000"/> <Author>HK</Author> <Comment>Added parameters pdp_type, pdp_address</Comment> </History> <History> <Date Day="9" Month="2" Year="2001"/> <Author>HK</Author> <Comment>Add smreg_ti, remove smreg_nsapi</Comment> </History> </Primitive> <Primitive> <Description> <Section>The MS initiates a PDP context deactivation: SM is requested to send a DEACTIVATE_PDP_CONTEXT_REQUEST message to the network. The PDP context is pending deactivation.</Section> </Description> <PrimDef> <Name>SMREG_PDP_DEACTIVATE_REQ</Name> <PrimID Direction="UPLINK" Number="1"/> <PrimUsage> <Sender>ACI</Sender> <Receiver>SM</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>nsapi_set</Name> </ItemLink> <Comment>set of network layer service access point identifiers</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_local</Name> </ItemLink> <Comment>local deactivation?</Comment> </PrimItem> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>The MS initiated PDP context deactivation has been done. The network confirmed the PDP context deactivation, i.e. the DEACTIVATE_PDP_CONTEXT_ACCEPT message has been received from the network then SM has ordered SNDCP to locally release not further needed LLC links. The PDP context has been deactivated.</Section> </Description> <PrimDef> <Name>SMREG_PDP_DEACTIVATE_CNF</Name> <PrimID Direction="DOWNLINK" Number="3"/> <PrimUsage> <Sender>SM</Sender> <Receiver>ACI</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>nsapi_set</Name> </ItemLink> <Comment>set of network layer service access point identifiers</Comment> </PrimItem> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>A network initiated PDP context deactivation has been performed. The DEACTIVATE_PDP_CONTEXT_REQUEST message has been received from the network. The MS has acknowledged with the DEACTIVATE_PDP_CONTEXT_ACCEPT message. The PDP context has been deactivated, not further needed LLC links were locally released.</Section> </Description> <PrimDef> <Name>SMREG_PDP_DEACTIVATE_IND</Name> <PrimID Direction="DOWNLINK" Number="4"/> <PrimUsage> <Sender>SM</Sender> <Receiver>ACI</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>nsapi_set</Name> </ItemLink> <Comment>set of network layer service access point identifiers</Comment> </PrimItem> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>A network initiated PDP context modification has been performed. The MODIFY_PDP_CONTEXT_REQUEST message has been received from the network. The modification has been ac knowledged by sending the MODIFY_PDP_CONTEXT_ACCEPT message. One or several PDP contexts have been modified. LLC links are adjusted. [HK: [GSM 04.07, 6.5.1] says "QoS(s)", [GSM 04.08, 9.5.6] says that one MODIFY PDPD CONTEXT REQ includes only ONE QoS. It is assumed here that only ONE QoS will be regarded which will then be applied for all NSAPIs connected to the SAPI given in the MODIFY PDPD CONTEXT REQ.</Section> </Description> <PrimDef> <Name>SMREG_PDP_MODIFY_IND</Name> <PrimID Direction="DOWNLINK" Number="5"/> <PrimUsage> <Sender>SM</Sender> <Receiver>ACI</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_qos</Name> </ItemLink> <Comment>quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>nsapi_set</Name> </ItemLink> <Comment>set of network layer service access point identifier</Comment> </PrimItem> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>This is an extra primitive that is not mentioned in GSM 4.07. It will be used in the situation where an MT context activation occurs and GACI is not able to set up another context. In that situation there may be a) an extra prim like this or b) a timer waiting for the SMREG_PDP_ACTIVATE_REQ.</Section> </Description> <PrimDef> <Name>SMREG_PDP_ACTIVATE_RES</Name> <PrimID Direction="UPLINK" Number="2"/> <PrimUsage> <Sender>ACI</Sender> <Receiver>SM</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_ti</Name> </ItemLink> <Comment>transaction identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>smreg_cause</Name> </ItemLink> <Comment>Cause of rejection</Comment> </PrimItem> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> <History> <Date Day="9" Month="2" Year="2001"/> <Author>HK</Author> <Comment>Add smreg_ti</Comment> </History> <History> <Date Day="26" Month="4" Year="2002"/> <Author>HK</Author> <Comment>Change opcode after skip of AA</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 parameter defines a service data unit.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>sdu</Name> <Comment>Service Data Unit</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>l_buf</Name> </ItemLink> <Comment>length of content in bit</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>o_buf</Name> </ItemLink> <Comment>offset of content in bit</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>buf</Name> </ItemLink> <Control>[1]</Control> <Comment>buffer content</Comment> </PrimStructElemItem> <History> <Date Day="23" Month="2" Year="1998"/> <Author>MG</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>smreg_min_qos</Name> <Comment>quality of service</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>smreg_qos</Name> <Comment>quality of service</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>delay</Name> </ItemLink> <Comment>delay class</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>relclass</Name> </ItemLink> <Comment>reliablility class</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>peak</Name> </ItemLink> <Comment>peak throughput</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>preced</Name> </ItemLink> <Comment>precedence class</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>mean</Name> </ItemLink> <Comment>main throughput</Comment> </PrimStructElemItem> <History> <Date Day="16" Month="4" Year="2000"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="2" Month="8" Year="2000"/> <Author>HK</Author> <Comment>Added constants</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>Derived from IE in [GSM 04.08, 10.5.6.3]. Length is variable from 4 to 20 in message, but is set to the maximum here.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>pdp_address</Name> <Comment>PDP address</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>buff</Name> </ItemLink> <Control>[0..16]</Control> <Comment>buff</Comment> </PrimStructElemItem> <History> <Date Day="7" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Changed length</Comment> </History> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="7" Month="12" Year="1999"/> <Author>HK</Author> <Comment>deleted l_buf field, changed to variable array</Comment> </History> <History> <Date Day="8" Month="1" Year="2002"/> <Author>HK</Author> <Comment>Renamed from ambigous "buf".</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>The purpose of the access point name information element is to identify the packet data network to which the GPRS</Section> <Section>user wishes to connect.</Section> <Section>The Access Point Name is a label or a full qualified domain name according to DNS naming conventions (see GSM</Section> <Section>03.03 [10]).</Section> <Section>The access point name is a type 4 information element with a minimum length of 3 octets and a maximum length of</Section> <Section>102 octets.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>smreg_apn</Name> <Comment>access point name</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">smreg</DocName> <Name>buffer</Name> </ItemLink> <Control>[3..102]</Control> <Comment>Access point name value</Comment> </PrimStructElemItem> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="7" Month="12" Year="1999"/> <Author>HK</Author> <Comment>deleted l_buf field, changed to variable array</Comment> </History> <History> <Date Day="8" Month="1" Year="2002"/> <Author>HK</Author> <Comment>Renamed from ambigous "buf".</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>smreg_nsapi</Name> <Type>U8</Type> <Comment>network layer service access point identifier</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_smreg_nsapi</Name> </ValuesLink> <History> <Date Day="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The parameter defines a service data unit.</Section> </Description> <PrimBasicElemDef> <Name>l_buf</Name> <Type>U16</Type> <Comment>length of content in bit</Comment> </PrimBasicElemDef> <History> <Date Day="23" Month="2" Year="1998"/> <Author>MG</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The parameter defines a service data unit.</Section> </Description> <PrimBasicElemDef> <Name>o_buf</Name> <Type>U16</Type> <Comment>offset of content in bit</Comment> </PrimBasicElemDef> <History> <Date Day="23" Month="2" Year="1998"/> <Author>MG</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The parameter defines a service data unit.</Section> </Description> <PrimBasicElemDef> <Name>buf</Name> <Type>U8</Type> <Comment>buffer content</Comment> </PrimBasicElemDef> <History> <Date Day="23" Month="2" Year="1998"/> <Author>MG</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used to define the type of the Packet Data Protocol.</Section> </Description> <PrimBasicElemDef> <Name>pdp_type</Name> <Type>U8</Type> <Comment>PDP type</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_pdp_type</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.</Section> </Description> <PrimBasicElemDef> <Name>delay</Name> <Type>U8</Type> <Comment>delay class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_delay</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="2000"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="2" Month="8" Year="2000"/> <Author>HK</Author> <Comment>Added constants</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context.</Section> </Description> <PrimBasicElemDef> <Name>relclass</Name> <Type>U8</Type> <Comment>reliablility class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_relclass</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="2000"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="2" Month="8" Year="2000"/> <Author>HK</Author> <Comment>Added constants</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context.</Section> </Description> <PrimBasicElemDef> <Name>peak</Name> <Type>U8</Type> <Comment>peak throughput</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_peak</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="2000"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="2" Month="8" Year="2000"/> <Author>HK</Author> <Comment>Added constants</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context.</Section> </Description> <PrimBasicElemDef> <Name>preced</Name> <Type>U8</Type> <Comment>precedence class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_preced</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="2000"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="2" Month="8" Year="2000"/> <Author>HK</Author> <Comment>Added constants</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context.</Section> </Description> <PrimBasicElemDef> <Name>mean</Name> <Type>U8</Type> <Comment>main throughput</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_mean</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="2000"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="2" Month="8" Year="2000"/> <Author>HK</Author> <Comment>Added constants</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used to indicate the reason why a session management request is rejected. Values not mentioned in the list below shall be treated as follows: Any other value received by the mobile station shall be treated as 00100010, 'Service option temporarily out of order'. Any other value received by the network shall betreated as 01101111, 'Protocol error, unspecified'.</Section> </Description> <PrimBasicElemDef> <Name>smreg_cause</Name> <Type>U16</Type> <Comment>cause</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_smreg_cause</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="16" Month="9" Year="2002"/> <Author>HK</Author> <Comment>Adopted cause concept rules</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="3" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Derived from IE in [GSM 04.08, 10.5.6.3]. Length is variable from 4 to 20 in message, but is set to the maximum here.</Section> </Description> <PrimBasicElemDef> <Name>buff</Name> <Type>U8</Type> <Comment>buff</Comment> </PrimBasicElemDef> <History> <Date Day="7" Month="3" Year="1999"/> <Author>HK</Author> <Comment>Changed length</Comment> </History> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="7" Month="12" Year="1999"/> <Author>HK</Author> <Comment>deleted l_buf field, changed to variable array</Comment> </History> <History> <Date Day="8" Month="1" Year="2002"/> <Author>HK</Author> <Comment>Renamed from ambigous "buf".</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of the access point name information element is to identify the packet data network to which the GPRS</Section> <Section>user wishes to connect.</Section> <Section>The Access Point Name is a label or a full qualified domain name according to DNS naming conventions (see GSM</Section> <Section>03.03 [10]).</Section> <Section>The access point name is a type 4 information element with a minimum length of 3 octets and a maximum length of</Section> <Section>102 octets.</Section> </Description> <PrimBasicElemDef> <Name>buffer</Name> <Type>U8</Type> <Comment>Access point name value</Comment> </PrimBasicElemDef> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="7" Month="12" Year="1999"/> <Author>HK</Author> <Comment>deleted l_buf field, changed to variable array</Comment> </History> <History> <Date Day="8" Month="1" Year="2002"/> <Author>HK</Author> <Comment>Renamed from ambigous "buf".</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">smreg</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 SNSM SAP.</Section> </Description> <PrimBasicElemDef> <Name>hcomp</Name> <Type>U8</Type> <Comment>Header compression used/requested</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_hcomp</Name> </ValuesLink> <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 SNSM SAP.</Section> </Description> <PrimBasicElemDef> <Name>dcomp</Name> <Type>U8</Type> <Comment>Data compression used/requested</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_hcomp</Name> </ValuesLink> <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 additional to the ETSI specs and indicates the initiator of the activation.</Section> </Description> <PrimBasicElemDef> <Name>direc</Name> <Type>U8</Type> <Comment>Initiator of the activation</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_direc</Name> </ValuesLink> <History> <Date Day="6" Month="10" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Transaction identifier (see GSM 4.07, 11.2.3.1.3).</Section> </Description> <PrimBasicElemDef> <Name>smreg_ti</Name> <Type>U8</Type> <Comment>transaction identifier</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2001"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>A deactivation (activation also???) may be local or not. This means, a DEACT_PDP_REQ message may be sent or not.</Section> </Description> <PrimBasicElemDef> <Name>smreg_local</Name> <Type>U8</Type> <Comment>is (de)activation local</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">smreg</DocName> <Name>VAL_smreg_local</Name> </ValuesLink> <History> <Date Day="7" Month="5" 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> </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">smreg</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 SMREG 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_smreg_nsapi</Name> <Comment>values for smreg_nsapi</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>SMREG_NSAPI_0</Alias> <Comment>escape mechanism for future extensions</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SMREG_NSAPI_1</Alias> <Comment>Point-To-Multipoint Multicast information</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>SMREG_NSAPI_2</Alias> <Comment>reserved for future use</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>SMREG_NSAPI_3</Alias> <Comment>reserved for future use</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>SMREG_NSAPI_4</Alias> <Comment>reserved for future use</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>SMREG_NSAPI_5</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">6</Value> <Alias>SMREG_NSAPI_6</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">7</Value> <Alias>SMREG_NSAPI_7</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">8</Value> <Alias>SMREG_NSAPI_8</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">9</Value> <Alias>SMREG_NSAPI_9</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">10</Value> <Alias>SMREG_NSAPI_10</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">11</Value> <Alias>SMREG_NSAPI_11</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">12</Value> <Alias>SMREG_NSAPI_12</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">13</Value> <Alias>SMREG_NSAPI_13</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">14</Value> <Alias>SMREG_NSAPI_14</Alias> <Comment>dynamically allocated SMREG_NSAPI value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">15</Value> <Alias>SMREG_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_pdp_type</Name> <Comment>values for pdp_type</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>X_121</Alias> <Comment>X.121 address</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">33</Value> <Alias>IP_V_4</Alias> <Comment>IP version 4</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">87</Value> <Alias>IP_V_6</Alias> <Comment>IP version 6</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>SMREG_PEAK_SUB</Alias> <Comment>Subscribed peak throughput</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SMREG_PEAK_1K</Alias> <Comment>Up to 1 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>SMREG_PEAK_2K</Alias> <Comment>Up to 2 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>SMREG_PEAK_4K</Alias> <Comment>Up to 4 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>SMREG_PEAK_8K</Alias> <Comment>Up to 8 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>SMREG_PEAK_16K</Alias> <Comment>Up to 16 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">6</Value> <Alias>SMREG_PEAK_32K</Alias> <Comment>Up to 32 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">7</Value> <Alias>SMREG_PEAK_64K</Alias> <Comment>Up to 64 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">8</Value> <Alias>SMREG_PEAK_128K</Alias> <Comment>Up to 128 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">9</Value> <Alias>SMREG_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>SMREG_RELCLASS_SUB</Alias> <Comment>Subscribed reliability class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SMREG_GTP_LLC_RLC_PROT</Alias> <Comment>Acknowledged GTP, LLC, and RLC; Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>SMREG_LLC_RLC_PROT</Alias> <Comment>Unacknowledged GTP; Acknowledged LLC and RLC, Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>SMREG_RLC_PROT</Alias> <Comment>Unacknowledged GTP and LLC; Acknowledged RLC, Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>SMREG_PROT</Alias> <Comment>Unacknowledged GTP, LLC, and RLC, Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>SMREG_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>SMREG_DELAY_SUB</Alias> <Comment>Subscribed delay class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SMREG_DELAY_1</Alias> <Comment>Delay class 1</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>SMREG_DELAY_2</Alias> <Comment>Delay class 2</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>SMREG_DELAY_3</Alias> <Comment>Delay class 3</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>SMREG_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>SMREG_MEAN_SUB</Alias> <Comment>Subscribed mean throughput</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SMREG_MEAN_100</Alias> <Comment>100 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>SMREG_MEAN_200</Alias> <Comment>200 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>SMREG_MEAN_500</Alias> <Comment>500 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>SMREG_MEAN_1K</Alias> <Comment>1 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>SMREG_MEAN_2K</Alias> <Comment>2 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">6</Value> <Alias>SMREG_MEAN_5K</Alias> <Comment>5 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">7</Value> <Alias>SMREG_MEAN_10K</Alias> <Comment>10 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">8</Value> <Alias>SMREG_MEAN_20K</Alias> <Comment>20 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">9</Value> <Alias>SMREG_MEAN_50K</Alias> <Comment>50 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">10</Value> <Alias>SMREG_MEAN_100K</Alias> <Comment>100 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">11</Value> <Alias>SMREG_MEAN_200K</Alias> <Comment>200 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">12</Value> <Alias>SMREG_MEAN_500K</Alias> <Comment>500 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">13</Value> <Alias>SMREG_MEAN_1M</Alias> <Comment>1 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">14</Value> <Alias>SMREG_MEAN_2M</Alias> <Comment>2 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">15</Value> <Alias>SMREG_MEAN_5M</Alias> <Comment>5 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">16</Value> <Alias>SMREG_MEAN_10M</Alias> <Comment>10 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">17</Value> <Alias>SMREG_MEAN_20M</Alias> <Comment>20 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">18</Value> <Alias>SMREG_MEAN_50M</Alias> <Comment>50 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">31</Value> <Alias>SMREG_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>SMREG_PRECED_SUB</Alias> <Comment>Subscribed precedence</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SMREG_PRIO_HIGH</Alias> <Comment>High priority</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>SMREG_PRIO_NORM</Alias> <Comment>Normal priority</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>SMREG_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_smreg_cause</Name> <Comment>values for smreg_cause</Comment> </ValuesDef> <ValuesItem> <Value ValueType="BIN">0100101100011010</Value> <Alias>SMREG_RC_INSUF_RES</Alias> <Comment>Insufficicent resources</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100011010</Value> <Alias>SMREG_RC_INSUF_RES_NO</Alias> <Comment>Insufficicent resources network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100011011</Value> <Alias>SMREG_RC_MISS_UNKWN_APN</Alias> <Comment>Missing or unknown APN network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100011100</Value> <Alias>SMREG_RC_ADD_OR_TYPE_UNKNWN</Alias> <Comment>Unknown PDP address or PDP type network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100011101</Value> <Alias>SMREG_RC_USE_AUTHED_FAILED</Alias> <Comment>User authentication failed network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100011110</Value> <Alias>SMREG_RC_GGSN_ACT_REJ</Alias> <Comment>Activation rejected by GGSN network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100011111</Value> <Alias>SMREG_RC_ACT_REJ_UNSPEC</Alias> <Comment>Activation rejected, unspecified network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100100000</Value> <Alias>SMREG_RC_SERV_OPT_NOT_SUPP</Alias> <Comment>Service option not supported network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100100001</Value> <Alias>SMREG_RC_SERV_OPT_NOT_SUBS</Alias> <Comment>Requested service option not subscribed network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100100010</Value> <Alias>SMREG_RC_SERV_OPT_TEMP_OOO</Alias> <Comment>Service option temporarily out of order network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101100100011</Value> <Alias>SMREG_RC_NSAPI_ALREADY_USED</Alias> <Comment>NSAPI already used</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100100011</Value> <Alias>SMREG_RC_NSAPI_ALREADY_USED_NO</Alias> <Comment>NSAPI already used network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101100100100</Value> <Alias>SMREG_RC_REGULAR_DEACTIVATION</Alias> <Comment>Regular deactivation</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100100100</Value> <Alias>SMREG_RC_REGULAR_DEACTIVATION_NO</Alias> <Comment>Regular deactivation network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101100100101</Value> <Alias>SMREG_RC_QOS_NOT_ACCEPTED</Alias> <Comment>QoS not accepted mobile originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100100110</Value> <Alias>SMREG_RC_NETWORK_FAILURE_NO</Alias> <Comment>Network failure network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101100100110</Value> <Alias>SMREG_RC_NETWORK_FAILURE</Alias> <Comment>Network failure</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101100100111</Value> <Alias>SMREG_RC_REACTIVATION_REQD</Alias> <Comment>Reactivation required network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101101010001</Value> <Alias>SMREG_RC_TI_INVALID_NO</Alias> <Comment>Invalid transaction identifier value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101101010001</Value> <Alias>SMREG_RC_TI_INVALID</Alias> <Comment>Invalid transaction identifier value</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101101011111</Value> <Alias>SMREG_RC_SEMANTIC_INCORRECT_NO</Alias> <Comment>Semantically incorrect message network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101101011111</Value> <Alias>SMREG_RC_SEMANTIC_INCORRECT</Alias> <Comment>Semantically incorrect message</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101101100000</Value> <Alias>SMREG_RC_INVALID_MANDAT_NO</Alias> <Comment>Invalid mandatory information network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101101100000</Value> <Alias>SMREG_RC_INVALID_MANDAT</Alias> <Comment>Invalid mandatory information</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101101100001</Value> <Alias>SMREG_RC_TYPE_NONEXIST_NOTIMP_NO</Alias> <Comment>Message type non-existant or not implemented network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101101100001</Value> <Alias>SMREG_RC_TYPE_NONEXIST_NOTIMP</Alias> <Comment>Message type non-existant or not implemented</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101101100010</Value> <Alias>SMREG_RC_TYPE_NOT_STATE_COMP_NO</Alias> <Comment>Message type not compatible with the protocol state network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101101100010</Value> <Alias>SMREG_RC_TYPE_NOT_STATE_COMP</Alias> <Comment>Message type not compatible with the protocol state</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101101100011</Value> <Alias>SMREG_RC_IE_NONEXIST_NOTIMP_NO</Alias> <Comment>Information element non-existatnt or not implemented network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101101100011</Value> <Alias>SMREG_RC_IE_NONEXIST_NOTIMP</Alias> <Comment>Information element non-existatnt or not implemented</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101101100100</Value> <Alias>SMREG_RC_COND_IE_ERROR_NO</Alias> <Comment>Conditional IE error network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101101100100</Value> <Alias>SMREG_RC_COND_IE_ERROR</Alias> <Comment>Conditional IE error</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101101100101</Value> <Alias>SMREG_RC_MSG_NOT_STATE_COMP_NO</Alias> <Comment>Message not compatible with protocol state network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101101100101</Value> <Alias>SMREG_RC_MSG_NOT_STATE_COMP</Alias> <Comment>Message not compatible with protocol state</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0000101101101111</Value> <Alias>SMREG_RC_PROT_ERROR_UNSPEC_NO</Alias> <Comment>Protocol error, unspecified network originated</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0100101101101111</Value> <Alias>SMREG_RC_PROT_ERROR_UNSPEC</Alias> <Comment>Protocol error, unspecified</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>SMREG_VAN_NOT_USED</Alias> <Comment>Van Jacobson is not supported</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SMREG_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_hcomp</Name> <Comment>values for hcomp</Comment> </ValuesDef> <ValuesItem> <Value ValueType="BIN">00</Value> <Alias>SMREG_COMP_NEITHER_DIRECT</Alias> <Comment>compress neither direction</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">01</Value> <Alias>SMREG_COMP_MS_SGSN_DIRECT</Alias> <Comment>compress MS to SGSN direction only</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">10</Value> <Alias>SMREG_COMP_SGSN_MS_DIRECT</Alias> <Comment>compress SGSN to MS direction only</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">11</Value> <Alias>SMREG_COMP_BOTH_DIRECT</Alias> <Comment>compress both directions</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_direc</Name> <Comment>values for direc</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>DIREC_MO</Alias> <Comment>Mobile initiates</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>DIREC_MT</Alias> <Comment>Network initiates</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_smreg_local</Name> <Comment>values for smreg_local</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>SMREG_NONLOCAL</Alias> <Comment>not local, air msg will be sent</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SMREG_LOCAL</Alias> <Comment>local, no air msg will be sent</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">0</Value> <Alias>SMREG_HOME</Alias> <Comment>mapped to HOME from dti.h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>SMREG_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>