FreeCalypso > hg > freecalypso-sw
view gsm-fw/cdg/sap/ll.sap @ 652:a39ec5bb5549
gsm-fw/cdg: imported MDF and PDF files from LoCosto, along with XML sources
| author | Michael Spacefalcon <msokolov@ivan.Harhan.ORG> |
|---|---|
| date | Thu, 25 Sep 2014 08:46:13 +0000 |
| parents | |
| 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">ll</DocName> <DocNum Number="104" 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 GPRS consists of several entities. Each entity has one ore more service access points, over which the entity provides a service for the upper entity.</Section> <Section>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="7" Month="4" Year="1999"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Initial</Comment> </DocHistory> <DocHistory> <DocVersion Number="002" Year="99"/> <Date Day="7" Month="6" Year="1999"/> <Author>ANS</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>ANS, LL_RESET_IND, QoS, Radio Priority, and TLLI inserted, Protection mode removed</Comment> </DocHistory> <DocHistory> <DocVersion Number="003" Year="99"/> <Date Day="22" Month="6" Year="1999"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Replaced List of Generic Data Descriptors with Service Data Unit, removed Reference in certain primitives and removed LL_UNITDATA_CNF</Comment> </DocHistory> <DocHistory> <DocVersion Number="004" Year="99"/> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Inserted LL_GETUNITDATA_REQ</Comment> </DocHistory> <DocHistory> <DocVersion Number="005" Year="99"/> <Date Day="14" Month="10" Year="1999"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Corrected opcodes of primitives</Comment> </DocHistory> <DocHistory> <DocVersion Number="006" Year="99"/> <Date Day="16" Month="12" Year="1999"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>N202 changed due to 04.64 version 6.5.1</Comment> </DocHistory> <DocHistory> <DocVersion Number="007" Year="99"/> <Date Day="20" Month="1" Year="2000"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Inserted LL_SAPI_INVALID</Comment> </DocHistory> <DocHistory> <DocVersion Number="008" Year="99"/> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Inserted parameters reserved and xid_valid</Comment> </DocHistory> <DocHistory> <DocVersion Number="009" Year="99"/> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Inserted reserved arrays to align LL_DATA_REQ/LL_UNITDATA_REQ with CCI_CIPHER_REQ, and CCI_DECIPHER_CNF with LL_DATA_IND/LL_UNITDATA_IND</Comment> </DocHistory> <DocHistory> <DocVersion Number="010" Year="99"/> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Inserted reserved octets to exactly align primitives</Comment> </DocHistory> <DocHistory> <DocVersion Number="011" Year="99"/> <Date Day="28" Month="7" Year="2000"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Inserted constants LLC_SDU_OFFSET and LLC_SDU_OFFSET_BITS</Comment> </DocHistory> <DocHistory> <DocVersion Number="012" Year="99"/> <Date Day="17" Month="8" Year="2000"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Inserted some comments</Comment> </DocHistory> <DocHistory> <DocVersion Number="013" Year="99"/> <Date Day="6" Month="9" Year="2000"/> <Author>DB</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Inserted LL_STATUS_IND primitive</Comment> </DocHistory> <DocHistory> <DocVersion Number="014" Year="99"/> <Date Day="4" Month="12" Year="2000"/> <Author>GS</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>LL_DATA_CNF changed to confirm up to LLC_MAX_CNF L3-PDUs</Comment> </DocHistory> <DocHistory> <DocVersion Number="015" Year="99"/> <Date Day="26" Month="6" Year="2001"/> <Author>GS</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>Reference renamed to reference1. Constant LLC_MAX_L3_XID_LEN added.</Comment> </DocHistory> <DocHistory> <DocVersion Number="016" Year="99"/> <Date Day="5" Month="12" Year="2001"/> <Author>GS</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>xid_valid added to LL_ESTABLISH_RSP</Comment> </DocHistory> <DocHistory> <DocVersion Number="017" Year="99"/> <Date Day="4" Month="2" Year="2003"/> <Author>UT</Author> <DocStatus State="BEING_PROCESSED"/> <Comment>LL_UNITDESC_REQ and LL_DESC_REQ added to support support descriptor in uplink direction. LL_UNITDATA_REQ and LL_DATA_REQ are used for test puposes.</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 LL SAP</Section> </Description> <Constant> <Alias>N202</Alias> <Value ValueType="DEC">4</Value> <Comment>maximum number of octets in the layer-3 header, Requirements: <R.LLC.LLC_PAR.A.008>, <R.LLC.TXUI_ADM.A.003>, <R.LLC.RXUI_ADM.A.003></Comment> </Constant> <Constant> <Alias>LLC_SDU_OFFSET</Alias> <Value ValueType="DEC">37</Value> <Comment>number of octets that have to be reserved at the beginning of an SDU when an upper layer allocates an SDU for uplink data transfer; these octets are the maximum number of octets that the LLC header can occupy, they have to be skipped when upper layers write / read the contents of the SDU</Comment> </Constant> <Constant> <Alias>LLC_SDU_OFFSET_BITS</Alias> <Value ValueType="DEC">296</Value> <Comment>LLC_SDU_OFFSET in bits. NOTE: When this definition is changed, upper layer SAPs may also need to be changed!</Comment> </Constant> <Constant> <Alias>LLC_MAX_L3_XID_LEN</Alias> <Value ValueType="DEC">255</Value> <Comment>Maximum byte length of the L3 XID parameter.</Comment> </Constant> <Constant> <Alias>LLC_MAX_L3_XID_LEN</Alias> <Value ValueType="DEC">255</Value> <Comment>Maximum byte length of the L3 XID parameter.</Comment> </Constant> <Constant> <Alias>LLC_MAX_CNF</Alias> <Value ValueType="DEC">32</Value> <Comment>Maximum number of L3-PDU confirmations included in one LL_DATA_CNF</Comment> </Constant> <Constant> <Alias>LLC_ORIGINATING_ENTITY</Alias> <ItemLink> <DocName DocType="SAP">gsmcom</DocName> <Name>LLC_ORIGINATING_ENTITY</Name> </ItemLink> <Comment>mask for indicating the originating entity of a cause is LLC</Comment> </Constant> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="16" Month="12" Year="1999"/> <Author>DB</Author> <Comment>Changed from 5 to 4 due to version 6.5.1</Comment> </History> <History> <Date Day="28" Month="7" Year="2000"/> <Author>DB</Author> <Comment>Inserted LLC_SDU_OFFSET and LLC_SDU_OFFSET_BITS</Comment> </History> <History> <Date Day="4" Month="12" Year="2000"/> <Author>GS</Author> <Comment>LLC_MAX_CNF added</Comment> </History> <History> <Date Day="26" Month="6" Year="2001"/> <Author>GS</Author> <Comment>LLC_MAX_L3_XID_LEN added.</Comment> </History> <History> <Date Day="10" Month="9" Year="2001"/> <Author>UT</Author> <Comment>LLC_ORIGINATING_ENTITY added.</Comment> </History> </ConstantsSection> <PrimitivesSection PrimIDType="BIT16" SAPid="34"> <Description> <Section>This section contains all primitives that are defined for the LL SAP</Section> </Description> <Primitive> <Description> <Section>LL-RESET-IND is used in the MS to indicate to SNDCP that the Reset XID parameter has been received from the SGSN. All LLEs in state ABM enter state ADM and all LLC parameters are set to their default values.</Section> <Section>Parameter tlli is valid, but needs not to be evaluated by layer 3.</Section> <Section>Requirements:</Section> <Section><R.LLC.L_RESET.M.002></Section> </Description> <PrimDef> <Name>LL_RESET_IND</Name> <PrimID Direction="DOWNLINK" Number="0"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <History> <Date Day="3" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_ESTABLISH_REQ is used to request establishment of ABM operation by layer 3. Therefore LLC sends the command SABM to its peer.</Section> <Section>Parameter tlli is evaluated by LLC. It has to be a valid TLLI.</Section> <Section>Parameter sdu is used to negotiate layer-3 XID parameters (up to LLC_MAX_L3_XID_LEN bytes) between the layer-3 peers. If this parameter is valid then an XID information field shall be included within the SABM command containing the requested layer-3 parameters. If no layer-3 parameters shall be negotiated then the parameter sdu contains no data (member l_buf is 0).</Section> <Section>NOTE: It is currently an error to send LL_RELEASE_REQ or LL_XID_REQ before the corresponding LL_ESTABLISH_CNF or LL_RELEASE_IND have been received as a response to LL_ESTABLISH_REQ.</Section> <Section>Requirements:</Section> <Section><R.LLC.REESTCRI.A.002></Section> </Description> <PrimDef> <Name>LL_ESTABLISH_REQ</Name> <PrimID Direction="UPLINK" Number="0"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>layer-3 XID parameters to be negotiated</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_ESTABLISH_CNF is used to acknowledge the successful establishment of ABM operation to layer 3 (i.e. an UA response has been received from the peer LLC).</Section> <Section>Parameter tlli is valid, but needs not to be evaluated by layer 3.</Section> <Section>Parameters n201_u and n201_i contain the values of the maximum number of octets in an information field for U/UI frames (N201-U) and I frames (N201-I).</Section> <Section>Parameter xid_valid indicates if layer-3 XID parameters are included in this primitve.</Section> <Section>Parameter sdu contains the received layer-3 XID parameters (up to LLC_MAX_L3_XID_LEN bytes) from the peer. If an empty layer-3 XID parameter was received from the peer, the member l_buf will be set to 0, and xid_valid will indicate that layer-3 XID parameters are included.</Section> <Section>Requirements:</Section> <Section><R.LLC.ABMEST_R.A.020>, <R.LLC.REESTPRO.A.006></Section> </Description> <PrimDef> <Name>LL_ESTABLISH_CNF</Name> <PrimID Direction="DOWNLINK" Number="1"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>n201_u</Name> </ItemLink> <Comment>unacknowledged information field length</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>n201_i</Name> </ItemLink> <Comment>acknowledged information field length</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>xid_valid</Name> </ItemLink> <Comment>layer-3 XID parameters valid</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>negotiated layer-3 XID parameters</Comment> </PrimItem> <History> <Date Day="7" Month="4" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Inserted xid_valid</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_ESTABLISH_IND is used to indicate the request to establish ABM operation of the peer LLC to layer 3.</Section> <Section>Parameter tlli is valid, but needs not to be evaluated by layer 3.</Section> <Section>Parameters n201_u and n201_i contain the values of the maximum number of octets in an information field for U/UI frames (N201-U) and I frames (N201-I).</Section> <Section>Parameter xid_valid indicates if layer-3 XID parameters are included in this primitve.</Section> <Section>Parameter sdu is used to negotiate layer-3 XID parameters (up to LLC_MAX_L3_XID_LEN bytes) between the layer-3 peers which have been received in the XID information field of the SABM command from the peer LLC. If an empty layer-3 XID parameter was received from the peer, the member l_buf will be set to 0, and xid_valid will indicate that layer-3 XID parameters are included.</Section> <Section>Requirements:</Section> <Section><R.LLC.ABMEST_R.A.015>, <R.LLC.ABMEST_I.A.005>, <R.LLC.REESTPRO.A.005></Section> </Description> <PrimDef> <Name>LL_ESTABLISH_IND</Name> <PrimID Direction="DOWNLINK" Number="2"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>n201_u</Name> </ItemLink> <Comment>unacknowledged information field length</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>n201_i</Name> </ItemLink> <Comment>acknowledged information field length</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>xid_valid</Name> </ItemLink> <Comment>layer-3 XID parameters valid</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>layer-3 XID parameters to be negotiated</Comment> </PrimItem> <History> <Date Day="7" Month="4" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Inserted xid_valid</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_ESTABLISH_RES is used to acknowledge establishment of ABM operation.</Section> <Section>Parameter tlli is evaluated by LLC. It has to be a valid TLLI.</Section> <Section>Parameter xid_valid indicates if layer-3 XID parameters are included in this primitve.</Section> <Section>Parameter sdu contains the negotiated layer-3 XID parameters (up to LLC_MAX_L3_XID_LEN bytes), if any. If no negotiated layer-3 parameters are included this parameter contains no data (member l_buf is 0).</Section> <Section>Requirements:</Section> <Section><R.LLC.ABMEST_I.A.006></Section> </Description> <PrimDef> <Name>LL_ESTABLISH_RES</Name> <PrimID Direction="UPLINK" Number="1"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>xid_valid</Name> </ItemLink> <Comment>layer-3 XID parameters valid</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>negotiated layer-3 XID parameters</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="5" Month="12" Year="2001"/> <Author>GS</Author> <Comment>Parameter xid_valid added.</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_RELEASE_REQ is used to request termination of previously established ABM operation.</Section> <Section>Parameter tlli is evaluated by LLC. It has to be a valid TLLI.</Section> <Section>The parameter local indicates whether the termination is local (i.e. no DISC command is transmitted to the peer LLC) or not local (i.e. a DISC command is transmitted to the peer LLC, and a UA or DM response is expected from the peer LLC).</Section> <Section>NOTE: It is currently an error to send LL_ESTABLISH_REQ or LL_XID_REQ before the corresponding LL_RELEASE_CNF has been received as a response to LL_RELEASE_REQ.</Section> </Description> <PrimDef> <Name>LL_RELEASE_REQ</Name> <PrimID Direction="UPLINK" Number="2"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>local</Name> </ItemLink> <Comment>local release</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_RELEASE_CNF is used to acknowledge the requested termination of ABM mode of operation. If local release was requested then the primitive LL_RELEASE_CNF is sent immediately to layer 3 without notification of the peer LLC. Otherwise the primitive is sent after the UA or DM response is received from the peer LLC.</Section> <Section>Parameter tlli is valid. It is set to the value which was received from GRR.</Section> <Section>NOTE: Parameter 'reserved' is used to align this primitive with LL_RELEASE_REQ.</Section> <Section>Requirements:</Section> <Section><R.LLC.ABMEST_R.A.020>, <R.LLC.ABMTER_R.A.002>, <R.LLC.ABMTER_R.A.008>, <R.LLC.ABMTER_R.A.016>, <R.LLC.ABMTER_R.A.022>, <R.LLC.COLITXRX.A.013>, <R.LLC.COLDTXRX.A.006></Section> </Description> <PrimDef> <Name>LL_RELEASE_CNF</Name> <PrimID Direction="DOWNLINK" Number="3"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_release_cnf</Name> </ItemLink> <Comment>reserved octets for release confirm</Comment> </PrimItem> <History> <Date Day="31" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Inserted parameter 'reserved'</Comment> </History> <History> <Date Day="5" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Renamed reserved to reserved_release_cnf</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_RELEASE_IND is used to inform layer 3 that ABM operation has been terminated by the peer LLC, or that the requested establishment of ABM operation has failed.</Section> <Section>Parameter tlli is valid. It is set to the value which was received from GRR.</Section> <Section>The parameter cause indicates the reason for the termination of ABM operation.</Section> <Section>Requirements:</Section> <Section><R.LLC.ABMEST_R.A.015>, <R.LLC.ABMEST_R.A.022>, <R.LLC.ABMEST_R.A.030>, <R.LLC.ABMTER_R.A.003>, <R.LLC.ABMTER_I.A.004>, <R.LLC.XIDNEG_O.A.016>, <R.LLC.XIDNEG_O.A.022>, <R.LLC.COLDTXRX.A.005></Section> </Description> <PrimDef> <Name>LL_RELEASE_IND</Name> <PrimID Direction="DOWNLINK" Number="4"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>cause</Name> </ItemLink> <Comment>cause of ABM termination</Comment> </PrimItem> <History> <Date Day="31" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="10" Month="9" Year="1999"/> <Author>UT</Author> <Comment>Type of cause changed from UBYTE to USHORT</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_XID_REQ is used to request negotiation of layer-3 XID parameters.</Section> <Section>Parameter tlli is evaluated by LLC. It has to be a valid TLLI.</Section> <Section>The parameter sdu contains the layer-3 XID parameters (up to LLC_MAX_L3_XID_LEN bytes) that are to be negotiated. The XID command including an XID information field with the layer-3 parameters is sent to the peer LLC.</Section> <Section>NOTE: It is currently an error to send LL_ESTABLISH_REQ or LL_RELEASE_REQ before the corresponding LL_XID_CNF has been received as a response to LL_XID_REQ.</Section> </Description> <PrimDef> <Name>LL_XID_REQ</Name> <PrimID Direction="UPLINK" Number="3"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>service data unit</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_XID_CNF is used to transport the negotiated layer-3 XID parameters to layer 3 that are received from the peer layer 3.</Section> <Section>Parameter tlli is valid. It is set to the value which was received from GRR.</Section> <Section>The parameters n201_u and n201_i contain the values of the maximum number of octets in an information field for U/UI frames (N201-U) and I frames (N201-I).</Section> <Section>The parameter sdu contains the negotiated layer-3 XID parameters (up to LLC_MAX_L3_XID_LEN bytes) that have been received with the XID response from the peer LLC. If no layer-3 parameters have been included within the XID response then the parameter sdu contains no data (member l_buf is 0).</Section> <Section>Requirements:</Section> <Section><R.LLC.XIDNEG_O.A.009></Section> </Description> <PrimDef> <Name>LL_XID_CNF</Name> <PrimID Direction="DOWNLINK" Number="5"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>n201_u</Name> </ItemLink> <Comment>unacknowledged information field length</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>n201_i</Name> </ItemLink> <Comment>acknowledged information field length</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>service data unit</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_XID_IND is used to indicate to layer 3 that the peer layer 3 wants to negotiate the included layer-3 XID parameters.</Section> <Section>Parameter tlli is valid. It is set to the value which was received from GRR.</Section> <Section>The parameters n201_u and n201_i contain the values of the maximum number of octets in an information field for U/UI frames (N201-U) and I frames (N201-I).</Section> <Section>The parameter xid_valid indicates if layer-3 XID parameters are included in this primitve.</Section> <Section>The parameter sdu contains the layer-3 XID parameters to be negotiated that have been received with the XID command from the peer LLC. If an empty layer-3 XID parameter was received from the peer, the member l_buf will be set to 0, and xid_valid will indicate that layer-3 XID parameters are included.</Section> <Section>Requirements:</Section> <Section><R.LLC.XIDNEG_O.A.010>, <R.LLC.XIDNEG_R.A.004>, <R.LLC.XIDNEG_R.A.011></Section> </Description> <PrimDef> <Name>LL_XID_IND</Name> <PrimID Direction="DOWNLINK" Number="6"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>n201_u</Name> </ItemLink> <Comment>unacknowledged information field length</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>n201_i</Name> </ItemLink> <Comment>acknowledged information field length</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>xid_valid</Name> </ItemLink> <Comment>layer-3 XID parameters valid</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>layer-3 XID parameters to be negotiated</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Inserted xid_valid</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_XID_RES is used for negotiation of layer-3 XID parameters, started by the peer layer 3.</Section> <Section>Parameter tlli is evaluated by LLC. It has to be a valid TLLI.</Section> <Section>Parameter sdu contains the negotiated layer-3 XID parameters, if any. If no negotiated layer-3 parameters are included then this parameter contains no data (member l_buf is 0).</Section> <Section>Requirements:</Section> <Section><R.LLC.XIDNEG_R.A.005></Section> </Description> <PrimDef> <Name>LL_XID_RES</Name> <PrimID Direction="UPLINK" Number="4"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>service data unit</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_READY_IND is used to inform layer 3 that one LL_DATA_REQ primitive can be sent to LLC. The primitive LL_READY_IND is only used in state 'ABM'. It is always sent to layer 3 if one of the following three circumstances are met:</Section> <Section>1) LLC has established a logical link to its peer (LLC has just entered state 'ABM', LL_ESTABLISH_CNF / LL_ESTABLISH_IND has been sent to layer 3). This also includes the re-establishment of an LLC connection.</Section> <Section>2) LLC receives the primitive LL_DATA_REQ from layer 3, and enough space is available for another I frame in the local LLC frame buffer.</Section> <Section>3) A transmitted I frame is acknowledged from the peer LLC (this frame is therefore removed from the local LLC frame buffer) and no LL_READY_IND has been sent to layer 3 in response to an LL_DATA_REQ primitive (see above).</Section> <Section>Parameter tlli is not valid, needs not to be evaluated by layer 3. This parameter will be set to LL_TLLI_INVALID.</Section> <Section>This primitive is an addition to [GSM 04.64], where the implementation of the flow control is not specified.</Section> </Description> <PrimDef> <Name>LL_READY_IND</Name> <PrimID Direction="DOWNLINK" Number="7"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_UNITREADY_IND is used to inform layer 3 that one LL_UNITDATA_REQ primitive can be sent to LLC. The primitive LL_UNITREADY_IND is used in all states except 'TIIL Unassigned'. It is always sent to layer 3 if one of the following three circumstances are met:</Section> <Section>1) LLC has entered state 'ADM'.</Section> <Section>2) LLC receives the primitive LL_UNITDATA_REQ from layer 3, and enough space is available for another UI frame in the local LLC unacknowledged frame buffer.</Section> <Section>3) A UI frame is transmitted to the peer LLC (this frame is therefore removed from the local LLC unacknowledged frame buffer) and no LL_UNITREADY_IND has been sent to layer 3 in response to an LL_UNITDATA_REQ primitive (see above).</Section> <Section>Parameter tlli is not valid, needs not to be evaluated by layer 3. This parameter will be set to LL_TLLI_INVALID.</Section> <Section>This primitive is an addition to [GSM 04.64], where the implementation of the flow control is not specified.</Section> </Description> <PrimDef> <Name>LL_UNITREADY_IND</Name> <PrimID Direction="DOWNLINK" Number="8"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_GETDATA_REQ is used by layer 3 to inform LLC that one LL_DATA_IND primitive can be sent to layer 3. The primitive LL_GETDATA_REQ is only used in state 'ABM'. LLC is permitted to send only one received L3-PDU to layer 3 after the receipt of this primitive. If no L3-PDU is available for sending to layer 3 (i.e. no data has been received from the peer), LLC sends the L3-PDU as soon as it is available.</Section> <Section>Parameter tlli is not evaluated by LLC.</Section> <Section>This primitive is an addition to [GSM 04.64], where the implementation of the flow control is not specified.</Section> </Description> <PrimDef> <Name>LL_GETDATA_REQ</Name> <PrimID Direction="UPLINK" Number="5"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_GETUNITDATA_REQ is used by layer 3 to inform LLC that one LL_UNITDATA_IND primitive can be sent to layer 3. The primitive LL_GETUNITDATA_REQ is used in all states except 'TLLI Unassigned'. LLC is permitted to send only one received L3-PDU to layer 3 after the receipt of this primitive. If no L3-PDU is available for sending to layer 3 (i.e. no data has been received from the peer), LLC sends the L3-PDU as soon as it is available.</Section> <Section>Parameter tlli is not evaluated by LLC.</Section> <Section>This primitive is an addition to [GSM 04.64], where the implementation of the flow control is not specified.</Section> </Description> <PrimDef> <Name>LL_GETUNITDATA_REQ</Name> <PrimID Direction="UPLINK" Number="6"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>tlli</Name> </ItemLink> <Comment>temporary logical link entity</Comment> </PrimItem> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_DATA_REQ is used for test purposes. The primitive is send for acknowledged data transfer. It is handled in LL_DESC_REQ.</Section> </Description> <PrimDef> <Name>LL_DATA_REQ</Name> <PrimID Direction="UPLINK" Number="7"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>tlli</Name> </ItemLink> <Comment>temporary logical link entity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>ll_qos</Name> </ItemLink> <Comment>quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>radio_prio</Name> </ItemLink> <Comment>radio priority</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_req1</Name> </ItemLink> <Comment>reserved octet</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reference1</Name> </ItemLink> <Comment>reference to the PDU</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>seg_pos</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>attached_counter</Name> </ItemLink> <Comment>attached to primitive counter</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_req4</Name> </ItemLink> <Comment>reserved octets for data request</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>pkt_flow_id</Name> </ItemLink> <Version>REL99</Version> <Comment>packet flow identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_req5</Name> </ItemLink> <Version>!REL99</Version> <Comment>reserved octets for data request</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>service data unit</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="3" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>QoS and Radio Priority included</Comment> </History> <History> <Date Day="18" Month="6" Year="1999"/> <Author>DB</Author> <Comment>Replaced desc_list with sdu</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Changed qos to ll_qos</Comment> </History> <History> <Date Day="5" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Moved reference, included reserved_data_req</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_data_req1-3, renamed old one to _req4</Comment> </History> <History> <Date Day="12" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> <History> <Date Day="7" Month="3" Year="2001"/> <Author>HK</Author> <Comment>Replace reserved_data_req3 by attached_counter.</Comment> </History> <History> <Date Day="26" Month="6" Year="2001"/> <Author>GS</Author> <Comment>Reference renamed to reference1</Comment> </History> <History> <Date Day="4" Month="2" Year="2003"/> <Author>UT</Author> <Comment>The primitive is used for test puposes. Comments updated</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_DATA_CNF is used to acknowledge the successful transmission of an L3-PDU to layer 3. This primitive is only used in state 'ABM'.</Section> <Section>Parameter tlli is valid, but needs not to be evaluated by layer 3. (Parameter reference identifies the sent layer-3 PDU.)</Section> <Section>The parameter reference is set to the same value as the parameter reference in the corresponding LL_DATA_REQ primitive. One LL_DATA_CNF can be uses to confirm up to LLC_MAX_CNF data requests.</Section> <Section>Requirements:</Section> <Section><R.LLC.L_DATA.A.001>, <R.LLC.RX_ACK.A.011></Section> </Description> <PrimDef> <Name>LL_DATA_CNF</Name> <PrimID Direction="DOWNLINK" Number="9"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reference1</Name> </ItemLink> <Control>[1..LLC_MAX_CNF]</Control> <Comment>reference to the PDU</Comment> </PrimItem> <History> <Date Day="31" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="4" Month="12" Year="2000"/> <Author>GS</Author> <Comment>Reference changed to array of 1 to LLC_MAX_CNF elements</Comment> </History> <History> <Date Day="26" Month="6" Year="2001"/> <Author>GS</Author> <Comment>Reference renamed to reference1</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_DATA_IND is used to deliver a correctly received L3-PDU to layer 3. This primitive is only used in state 'ABM' for acknowledged frames.</Section> <Section>Parameter tlli is valid, needs not to be evaluated by layer 3.</Section> <Section>The parameter sdu contains the L3-PDU which has been received from the peer LLC.</Section> <Section>NOTE: Parameter reserved_data_ind is used to align the position of the sdu with the primitives LL_UNITDATA_IND and CCI_DECIPHER_CNF. If anything is changed which affects the position of the sdu in this primitive, reserved_data_ind must be adapted.</Section> <Section>Requirements:</Section> <Section><R.LLC.L_DATA.A.001>, <R.LLC.RX_IFRM.A.003>, <R.LLC.RX_IFRM.A.011></Section> </Description> <PrimDef> <Name>LL_DATA_IND</Name> <PrimID Direction="DOWNLINK" Number="10"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>tlli</Name> </ItemLink> <Comment>temporary logical link entity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_ind1</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_ind2</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_ind3</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_ind4</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_ind5</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_ind6</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>service data unit</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="18" Month="6" Year="1999"/> <Author>DB</Author> <Comment>Replaced desc_list with sdu, removed reference</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_data_ind</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_UNITDATA_REQ is used for test purposes. The primitive is send for unacknowledged data transfer. It is handled in LL_UNITDESC_REQ.</Section> </Description> <PrimDef> <Name>LL_UNITDATA_REQ</Name> <PrimID Direction="UPLINK" Number="8"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>tlli</Name> </ItemLink> <Comment>temporary logical link entity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>ll_qos</Name> </ItemLink> <Comment>quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>radio_prio</Name> </ItemLink> <Comment>radio priority</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>cipher</Name> </ItemLink> <Comment>ciphering indicator</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_req1</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>seg_pos</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>attached_counter</Name> </ItemLink> <Comment>attached to primitive counter</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_req4</Name> </ItemLink> <Comment>reserved octets for unitdata request</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>pkt_flow_id</Name> </ItemLink> <Version>REL99</Version> <Comment>packet flow identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_req5</Name> </ItemLink> <Version>!REL99</Version> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>service data unit</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="3" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>QoS included</Comment> </History> <History> <Date Day="18" Month="6" Year="1999"/> <Author>DB</Author> <Comment>Replaced desc_list with sdu, removed reference</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Changed qos to ll_qos</Comment> </History> <History> <Date Day="5" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_unitdata_req</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_unitdata_req1-3, renamed old one to _req4</Comment> </History> <History> <Date Day="4" Month="2" Year="2003"/> <Author>UT</Author> <Comment>The primitive is used for test puposes. Comments updated</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_UNITDATA_IND is used to deliver an L3-PDU received in an UI frame to layer 3 (LLC unacknowledged mode). This primitive is permitted in state 'ADM' and in state 'ABM'.</Section> <Section>Parameter tlli is valid, but needs not to be evaluated by layer 3.</Section> <Section>The parameter cipher indicates if the received UI frame was ciphered or not.</Section> <Section>The parameter sdu contains the L3-PDU which has been received from the peer LLC.</Section> <Section>NOTE: Parameter reserved_unitdata_ind is used to align the position of the sdu with the primitives LL_DATA_IND and CCI_DECIPHER_CNF. If anything is changed which affects the position of the sdu in this primitive, reserved_unitdata_ind must be adapted.</Section> <Section>Requirements:</Section> <Section><R.LLC.L_UNTDTA.A.001>, <R.LLC.RXUI_ADM.A.006></Section> </Description> <PrimDef> <Name>LL_UNITDATA_IND</Name> <PrimID Direction="DOWNLINK" Number="11"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>tlli</Name> </ItemLink> <Comment>temporary logical link entity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_ind1</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_ind2</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_ind3</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_ind4</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_ind5</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>cipher</Name> </ItemLink> <Comment>ciphering indicator</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sdu</Name> </ItemLink> <Comment>service data unit</Comment> </PrimItem> <History> <Date Day="24" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="18" Month="6" Year="1999"/> <Author>DB</Author> <Comment>Replaced desc_list with sdu</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_unitdata_ind</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_STATUS_IND is used to inform layer 3 when an LLC error occurs that cannot be corrected by LLC.</Section> <Section>Parameter tlli is valid, but needs not to be evaluated by layer 3.</Section> <Section>Parameter cause contains the cause of the error that has occurred.</Section> <Section>Requirements:</Section> <Section><R.LLC.L_STATUS.A.001>, <R.LLC.XIDNEG_O.A.026>, <R.LLC.XIDNEG_O.A.027></Section> </Description> <PrimDef> <Name>LL_STATUS_IND</Name> <PrimID Direction="DOWNLINK" Number="12"/> <PrimUsage> <Sender>LLC</Sender> <Receiver>L3</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>error_cause</Name> </ItemLink> <Comment>error cause</Comment> </PrimItem> <History> <Date Day="6" Month="9" Year="2000"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="10" Month="9" Year="1999"/> <Author>UT</Author> <Comment>Type of error_cause changed from UBYTE to USHORT</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_DESC_REQ is used to request the confirmed transmission of an L3-PDU to the peer (LLC acknowledged mode). This primitive is therefore only permitted in state 'ABM'.</Section> <Section>Parameter ll_qos contains the requested Quality of Service for the L3-PDU. LLC observes only the member peak (Peak Throughput). All other members of ll_qos are not necessary for LLC.</Section> <Section>Parameter radio_prio defines the radio priority level that is to be used by RLC/MAC for the transmission of the L3-PDU.</Section> <Section>Parameter reference is used by layer 3 as an identifier for the L3-PDU (see also LL_DATA_CNF).</Section> <Section>Parameter desc_list3 contains a list of data descriptors.</Section> <Section>NOTE: Parameter reserved_data_req is used to align the position of the sdu with the primitives LL_UNITDATA_REQ and CCI_CIPHER_REQ. If anything is changed which affects the position of the sdu in this primitive, reserved_data_req must be adapted.</Section> <Section>Requirements:</Section> <Section><R.LLC.L_DATA.A.001>, <R.LLC.L_DATA.M.005>, <R.LLC.L_DATA.A.006>, , <R.LLC.L_DATA.A.007></Section> </Description> <PrimDef> <Name>LL_DESC_REQ</Name> <PrimID Direction="UPLINK" Number="9"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>tlli</Name> </ItemLink> <Comment>temporary logical link entity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>ll_qos</Name> </ItemLink> <Comment>quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>radio_prio</Name> </ItemLink> <Comment>radio priority</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_req1</Name> </ItemLink> <Comment>reserved octet</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reference1</Name> </ItemLink> <Comment>reference to the PDU</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>seg_pos</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>attached_counter</Name> </ItemLink> <Comment>attached to primitive counter</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_req4</Name> </ItemLink> <Comment>reserved octets for data request</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>pkt_flow_id</Name> </ItemLink> <Version>REL99</Version> <Comment>packet flow identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_data_req5</Name> </ItemLink> <Version>!REL99</Version> <Comment>reserved octets for data request</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>desc_list3</Name> </ItemLink> <Comment>List of generic data descriptors</Comment> </PrimItem> <History> <Date Day="26" Month="11" Year="2002"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LL_UNITDESC_REQ is used to request the unconfirmed transmission of an L3-PDU to the peer (LLC unacknowledged mode). This primitive is permitted in state 'ADM' and in state 'ABM'.</Section> <Section>Parameter ll_qos contains the requested Quality of Service for the L3-PDU. LLC observes only the members peak (Peak Throughput) and relclass (Reliability Class). All other members of ll_qos are not necessary for LLC. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected LLC mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>Parameter radio_prio defines the radio priority level that is to be used by RLC/MAC for the transmission of the L3-PDU.</Section> <Section>Parameter cipher indicates if the UI frame is ciphered before the transmission or not.</Section> <Section>Parameter desc_list3 contains a list of data descriptors.</Section> <Section>NOTE: Parameter reserved_unitdata_req is used to align the position of the sdu with the primitives LL_DATA_REQ and CCI_CIPHER_REQ. If anything is changed which affects the position of the sdu in this primitive, reserved_unitdata_req must be adapted. ???????</Section> <Section>Requirements:</Section> <Section><R.LLC.L_UNTDTA.A.001>, <R.LLC.L_UNTDTA.M.004></Section> </Description> <PrimDef> <Name>LL_UNITDESC_REQ</Name> <PrimID Direction="UPLINK" Number="10"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>sapi</Name> </ItemLink> <Comment>service access point identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>tlli</Name> </ItemLink> <Comment>temporary logical link entity</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>ll_qos</Name> </ItemLink> <Comment>quality of service</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>radio_prio</Name> </ItemLink> <Comment>radio priority</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>cipher</Name> </ItemLink> <Comment>ciphering indicator</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_req1</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>seg_pos</Name> </ItemLink> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>attached_counter</Name> </ItemLink> <Comment>attached to primitive counter</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_req4</Name> </ItemLink> <Comment>reserved octets for unitdata request</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>pkt_flow_id</Name> </ItemLink> <Version>REL99</Version> <Comment>packet flow identifier</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_unitdata_req5</Name> </ItemLink> <Version>!REL99</Version> <Comment>reserved octets</Comment> </PrimItem> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>desc_list3</Name> </ItemLink> <Comment>List of generic data descriptors</Comment> </PrimItem> <History> <Date Day="26" Month="11" Year="2002"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </Primitive> <Primitive> <Description> <Section>LLC_DUMMY_REQ is defined to avoid a warning during compilation. It creates a reference on the parameter desc3. Otherwise the compiler gives a warning, that the parameter desc3 is defined but not used.</Section> </Description> <PrimDef> <Name>LLC_DUMMY_REQ</Name> <PrimID Direction="UPLINK" Number="11"/> <PrimUsage> <Sender>L3</Sender> <Receiver>LLC</Receiver> </PrimUsage> </PrimDef> <PrimItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>desc3</Name> </ItemLink> <Comment>generic data descriptor</Comment> </PrimItem> <History> <Date Day="26" Month="11" Year="2002"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </Primitive> </PrimitivesSection> <PrimStructElementsSection> <Description> <Section>Parameters shall be part of the primitives described above and if applied the parameters shall contain the values specified here. These values are selected to correspond to element values used in the air interface protocol.</Section> </Description> <PrimStructElem> <Description> <Section>This parameter contains either a L3-PDU or layer-3 parameters that are negotiated between the peer entities.</Section> <Section>Requirements:</Section> <Section><R.LLC.M_SUSPND.A.002>, <R.LLC.M_RESUME.A.001>, <R.LLC.L_UNTDTA.A.001>, <R.LLC.TXUI_ADM.A.001>, <R.LLC.RXUI_ADM.A.006>, <R.LLC.TX_IFRM.A.002>, <R.LLC.RX_IFRM.A.003>, <R.LLC.ABMEST_R.A.004>, <R.LLC.ABMEST_R.A.020>, <R.LLC.ABMEST_I.A.005>, <R.LLC.ABMEST_I.A.006>, <R.LLC.XIDNEG_O.A.002>, <R.LLC.XIDNEG_O.A.004>, <R.LLC.XIDNEG_O.A.009>, <R.LLC.XIDNEG_R.A.004>, <R.LLC.XIDNEG_R.A.005></Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>sdu</Name> <Comment>service data unit</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>l_buf</Name> </ItemLink> <Comment>length of content in bit</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>o_buf</Name> </ItemLink> <Comment>offset of content in bit</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>buf</Name> </ItemLink> <Control>[1]</Control> <Comment>buffer content</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 include L3-PDU</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This parameter is used by layer 3 to identify a transmitted L3-PDU in acknowledged mode of operation. Reference is stored by LLC for the identification of the frame after it has been acknowledged from the peer LLC after transmission.</Section> <Section>NOTE: reserved_unitdata_req1 is used to align the position of the SDU between LL_DATA_REQ, LL_UNITDATA_REQ, and CCI_CIPHER_REQ. If the size of this structure is modified, the structure in CCI_CIPHER_REQ must also be modified.</Section> <Section>Requirements:</Section> <Section><R.LLC.RX_ACK.A.011></Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>reference1</Name> <Comment>to the segment to be confirmed</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>reserved_unitdata_req1</Name> <Comment>reserved octets</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>reserved_data_ind2</Name> <Comment>reserved octets</Comment> </PrimStructElemDef> <PrimStructElemDef Type="STRUCT"> <Name>reserved_unitdata_ind2</Name> <Comment>reserved octets</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>ref_nsapi</Name> </ItemLink> <Comment>ref_nsapi</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>ref_npdu_num</Name> </ItemLink> <Comment>ref_npdu_num</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</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="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> <History> <Date Day="26" Month="6" Year="2001"/> <Author>GS</Author> <Comment>Reference renamed to reference1</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. QoS Parameters in the MS in primitive LL_DATA_REQ include only peak throughput, and in primitive LL_UNITDATA_REQ include only peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>NOTE: The reserved elements at the end are necessary to align this structure with a KC structure in CCI_CIPHER_REQ.</Section> <Section>Requirements:</Section> <Section><R.LLC.L_DATA.M.005>, <R.LLC.L_DATA.A.006></Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>ll_qos</Name> <Comment>quality of service</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>delay</Name> </ItemLink> <Comment>delay class</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>relclass</Name> </ItemLink> <Comment>reliability class</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>peak</Name> </ItemLink> <Comment>peak throughput</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>preced</Name> </ItemLink> <Comment>precedence class</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>mean</Name> </ItemLink> <Comment>main throughput</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_1</Name> </ItemLink> <Comment>reserved</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_2</Name> </ItemLink> <Comment>reserved</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>reserved_3</Name> </ItemLink> <Comment>reserved</Comment> </PrimStructElemItem> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="4" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Included from SNSM</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*"), type qos renamed to ll_qos</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_1-3 to match exactly CCI primitives</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This parameter defines a list of data descriptors.</Section> <Section>It is implemented as a linked list where the element 'first' is a pointer to the first generic data descriptor (see 4.18).</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>desc_list3</Name> <Comment>List of generic data descriptors</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>list_len</Name> </ItemLink> <Comment>length in octets of whole data</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>first</Name> </ItemLink> <Comment>pointer to first generic data descriptor</Comment> </PrimStructElemItem> <History> <Date Day="13" Month="1" Year="2003"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </PrimStructElem> <PrimStructElem> <Description> <Section>This is one element of the linked list of generic data descriptors.</Section> <Section>The member 'next' contains a pointer to the next descriptor or NULL if this is the last descriptor. The member 'offset' contains the number of octets before the first valid octet within the data buffer (which is referenced with the pointer 'buffer' ). The member 'len' contains the number of valid octets within the data buffer.</Section> </Description> <PrimStructElemDef Type="STRUCT"> <Name>desc3</Name> <Comment>generic data descriptor</Comment> </PrimStructElemDef> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>next</Name> </ItemLink> <Comment>next generic data descriptor</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>offset</Name> </ItemLink> <Comment>offset in octets</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>len</Name> </ItemLink> <Comment>length of content in octets</Comment> </PrimStructElemItem> <PrimStructElemItem Presentation="MANDATORY"> <ItemLink> <DocName DocType="SAP">ll</DocName> <Name>buffer</Name> </ItemLink> <Comment>pointer to buffer</Comment> </PrimStructElemItem> <History> <Date Day="2" Month="1" Year="2003"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </PrimStructElem> </PrimStructElementsSection> <PrimBasicElementsSection> <Description> <Section>Parameters shall be part of the primitives described above and if applied the parameters shall contain the values specified here. These values are selected to correspond to element values used in the air interface protocol.</Section> </Description> <PrimBasicElem> <Description> <Section>This parameter identifies a point at which LLC services are provided by an LLE to a layer-3 entity. Consequently, SAPI identifies an LLE that processes an LLC frame and also a layer-3 entity that is to receive information carried by the LLC frame.</Section> <Section>SAPI allows 16 service access points to be specified but only six of them are currently defined. The rest is reserved for future use.</Section> </Description> <PrimBasicElemDef> <Name>sapi</Name> <Type>U8</Type> <Comment>service access point identifier</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_sapi</Name> </ValuesLink> <History> <Date Day="6" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*")</Comment> </History> <History> <Date Day="28" Month="1" Year="2000"/> <Author>DB</Author> <Comment>Inserted LL_SAPI_INVALID</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter identifies the MS. Within the SGSN it is used to distinguish between the different LLC entities. On the side of the MS this parameter is required for the support of anonymous access. An anonymous PDP context has always a different TLLI than the normal PDP context of the MS.</Section> </Description> <PrimBasicElemDef> <Name>tlli</Name> <Type>U32</Type> <Comment>temporary logical link identifier</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_tlli</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Added LL_TLLI_INVALID</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter indicates if layer-3 XID parameters are valid. This indication is needed when an empty layer-3 XID parameter block is received by LLC. This may result in an LL_XID_IND with an empty (but valid!) layer-3 XID parameter.</Section> </Description> <PrimBasicElemDef> <Name>xid_valid</Name> <Type>U8</Type> <Comment>layer-3 XID parameters valid or not</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_xid_valid</Name> </ValuesLink> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</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> <Section>Requirements:</Section> <Section>&lt;R.LLC.M_SUSPND.A.002&gt;, &lt;R.LLC.M_RESUME.A.001&gt;, &lt;R.LLC.L_UNTDTA.A.001&gt;, &lt;R.LLC.TXUI_ADM.A.001&gt;, &lt;R.LLC.RXUI_ADM.A.006&gt;, &lt;R.LLC.TX_IFRM.A.002&gt;, &lt;R.LLC.RX_IFRM.A.003&gt;, &lt;R.LLC.ABMEST_R.A.004&gt;, &lt;R.LLC.ABMEST_R.A.020&gt;, &lt;R.LLC.ABMEST_I.A.005&gt;, &lt;R.LLC.ABMEST_I.A.006&gt;, &lt;R.LLC.XIDNEG_O.A.002&gt;, &lt;R.LLC.XIDNEG_O.A.004&gt;, &lt;R.LLC.XIDNEG_O.A.009&gt;, &lt;R.LLC.XIDNEG_R.A.004&gt;, &lt;R.LLC.XIDNEG_R.A.005&gt;</Section> </Description> <PrimBasicElemDef> <Name>l_buf</Name> <Type>U16</Type> <Comment>length of content in bit</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 include L3-PDU</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> <Section>Requirements:</Section> <Section>&lt;R.LLC.M_SUSPND.A.002&gt;, &lt;R.LLC.M_RESUME.A.001&gt;, &lt;R.LLC.L_UNTDTA.A.001&gt;, &lt;R.LLC.TXUI_ADM.A.001&gt;, &lt;R.LLC.RXUI_ADM.A.006&gt;, &lt;R.LLC.TX_IFRM.A.002&gt;, &lt;R.LLC.RX_IFRM.A.003&gt;, &lt;R.LLC.ABMEST_R.A.004&gt;, &lt;R.LLC.ABMEST_R.A.020&gt;, &lt;R.LLC.ABMEST_I.A.005&gt;, &lt;R.LLC.ABMEST_I.A.006&gt;, &lt;R.LLC.XIDNEG_O.A.002&gt;, &lt;R.LLC.XIDNEG_O.A.004&gt;, &lt;R.LLC.XIDNEG_O.A.009&gt;, &lt;R.LLC.XIDNEG_R.A.004&gt;, &lt;R.LLC.XIDNEG_R.A.005&gt;</Section> </Description> <PrimBasicElemDef> <Name>o_buf</Name> <Type>U16</Type> <Comment>offset of content in bit</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 include L3-PDU</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> <Section>Requirements:</Section> <Section>&lt;R.LLC.M_SUSPND.A.002&gt;, &lt;R.LLC.M_RESUME.A.001&gt;, &lt;R.LLC.L_UNTDTA.A.001&gt;, &lt;R.LLC.TXUI_ADM.A.001&gt;, &lt;R.LLC.RXUI_ADM.A.006&gt;, &lt;R.LLC.TX_IFRM.A.002&gt;, &lt;R.LLC.RX_IFRM.A.003&gt;, &lt;R.LLC.ABMEST_R.A.004&gt;, &lt;R.LLC.ABMEST_R.A.020&gt;, &lt;R.LLC.ABMEST_I.A.005&gt;, &lt;R.LLC.ABMEST_I.A.006&gt;, &lt;R.LLC.XIDNEG_O.A.002&gt;, &lt;R.LLC.XIDNEG_O.A.004&gt;, &lt;R.LLC.XIDNEG_O.A.009&gt;, &lt;R.LLC.XIDNEG_R.A.004&gt;, &lt;R.LLC.XIDNEG_R.A.005&gt;</Section> </Description> <PrimBasicElemDef> <Name>buf</Name> <Type>U8</Type> <Comment>buffer content</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 include L3-PDU</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter defines the maximum number of octets in an information field for U and UI frames. The maximum value for this parameter is 1520 octets. The minimum value is 400 octets for SAPI 1, 270 octets for SAPI 7, and 140 octets otherwise. The default value is 400 octets for SAPI 1, 270 octets for SAPI 7, and 500 octets otherwise.</Section> <Section>Requirements:</Section> <Section><R.LLC.ABMEST_R.A.020>, <R.LLC.ABMEST_I.A.005>, <R.LLC.XIDNEG_O.A.009>, <R.LLC.XIDNEG_O.A.010>, <R.LLC.XIDNEG_R.A.004>, <R.LLC.XIDNEG_R.A.011></Section> </Description> <PrimBasicElemDef> <Name>n201_u</Name> <Type>U16</Type> <Comment>maximum number of octets in an U or UI frame information field</Comment> </PrimBasicElemDef> <History> <Date Day="17" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter defines the maximum number of octets in an information field for I frames. The maximum value for this parameter is 1520 octets, and the minimum value is 140 octets. This parameter is not valid for SAPIs 1 and 7, which support no ABM mode of operation. Therefore it shall be ignored by the layer-3 entity.</Section> <Section>Requirements:</Section> <Section><R.LLC.ABMEST_R.A.020>, <R.LLC.ABMEST_I.A.005>, <R.LLC.XIDNEG_O.A.009>, <R.LLC.XIDNEG_O.A.010>, <R.LLC.XIDNEG_R.A.004>, <R.LLC.XIDNEG_R.A.011></Section> </Description> <PrimBasicElemDef> <Name>n201_i</Name> <Type>U16</Type> <Comment>maximum number of octets in an I frame information field</Comment> </PrimBasicElemDef> <History> <Date Day="17" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter indicates whether the termination of ABM operation is local (i.e. no DISC command is transmitted to the peer LLC) or not local (i.e. a DISC command is transmitted to the peer LLC, and a UA or DM response is expected from the peer LLC).</Section> <Section>Requirements:</Section> <Section><R.LLC.ABMTER_R.A.006>, <R.LLC.ABMTER_R.A.007>, <R.LLC.ABMTER_R.A.008></Section> </Description> <PrimBasicElemDef> <Name>local</Name> <Type>U8</Type> <Comment>local release or release both sides</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_local</Name> </ValuesLink> <History> <Date Day="4" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*")</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter indicates the reason of the termination of ABM operation to layer 3.</Section> <Section>Requirements:</Section> <Section><R.LLC.ABMEST_R.A.015>, <R.LLC.ABMEST_R.A.022>, <R.LLC.ABMEST_R.A.030>, <R.LLC.ABMTER_R.A.003>, <R.LLC.ABMTER_I.A.004>, <R.LLC.XIDNEG_O.A.016>, <R.LLC.XIDNEG_O.A.022>, <R.LLC.COLDTXRX.A.005></Section> </Description> <PrimBasicElemDef> <Name>cause</Name> <Type>U16</Type> <Comment>cause of ABM termination</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_cause</Name> </ValuesLink> <History> <Date Day="31" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*")</Comment> </History> <History> <Date Day="10" Month="9" Year="1999"/> <Author>UT</Author> <Comment>Values of c-macro changed according to cause concept</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used by layer 3 to identify a transmitted L3-PDU in acknowledged mode of operation. Reference is stored by LLC for the identification of the frame after it has been acknowledged from the peer LLC after transmission.</Section> <Section>NOTE: reserved_unitdata_req1 is used to align the position of the SDU between LL_DATA_REQ, LL_UNITDATA_REQ, and CCI_CIPHER_REQ. If the size of this structure is modified, the structure in CCI_CIPHER_REQ must also be modified.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.RX_ACK.A.011&gt;</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="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> <History> <Date Day="26" Month="6" Year="2001"/> <Author>GS</Author> <Comment>Reference renamed to reference1</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used by layer 3 to identify a transmitted L3-PDU in acknowledged mode of operation. Reference is stored by LLC for the identification of the frame after it has been acknowledged from the peer LLC after transmission.</Section> <Section>NOTE: reserved_unitdata_req1 is used to align the position of the SDU between LL_DATA_REQ, LL_UNITDATA_REQ, and CCI_CIPHER_REQ. If the size of this structure is modified, the structure in CCI_CIPHER_REQ must also be modified.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.RX_ACK.A.011&gt;</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="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> <History> <Date Day="26" Month="6" Year="2001"/> <Author>GS</Author> <Comment>Reference renamed to reference1</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter is used by layer 3 to identify a transmitted L3-PDU in acknowledged mode of operation. Reference is stored by LLC for the identification of the frame after it has been acknowledged from the peer LLC after transmission.</Section> <Section>NOTE: reserved_unitdata_req1 is used to align the position of the SDU between LL_DATA_REQ, LL_UNITDATA_REQ, and CCI_CIPHER_REQ. If the size of this structure is modified, the structure in CCI_CIPHER_REQ must also be modified.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.RX_ACK.A.011&gt;</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="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> <History> <Date Day="26" Month="6" Year="2001"/> <Author>GS</Author> <Comment>Reference renamed to reference1</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>In the primitive LL_UNITDATA_REQ this primitive defines if the corresponding UI frame is to be ciphered or not before transmission.</Section> <Section>In the primitive LL_UNITDATA_IND this primitive indicates if the corresponding received UI frame has been ciphered or not.</Section> </Description> <PrimBasicElemDef> <Name>cipher</Name> <Type>U8</Type> <Comment>ciphering indicator</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_cipher</Name> </ValuesLink> <History> <Date Day="15" Month="3" Year="1999"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*")</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of the radio priority information element is to specify the priority level that the MS shall use at the lower layers (RLC/MAC) for transmission of data related to a PDP context or for mobile originated SMS transmission.</Section> <Section>Requirements:</Section> <Section><R.LLC.L_DATA.A.007></Section> </Description> <PrimBasicElemDef> <Name>radio_prio</Name> <Type>U8</Type> <Comment>Radio Priority</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_radio_prio</Name> </ValuesLink> <History> <Date Day="3" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Initial</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*")</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. QoS Parameters in the MS in primitive LL_DATA_REQ include only peak throughput, and in primitive LL_UNITDATA_REQ include only peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>NOTE: The reserved elements at the end are necessary to align this structure with a KC structure in CCI_CIPHER_REQ.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.L_DATA.M.005&gt;, &lt;R.LLC.L_DATA.A.006&gt;</Section> </Description> <PrimBasicElemDef> <Name>delay</Name> <Type>U8</Type> <Comment>delay class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_delay</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="4" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Included from SNSM</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*"), type qos renamed to ll_qos</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_1-3 to match exactly CCI primitives</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. QoS Parameters in the MS in primitive LL_DATA_REQ include only peak throughput, and in primitive LL_UNITDATA_REQ include only peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>NOTE: The reserved elements at the end are necessary to align this structure with a KC structure in CCI_CIPHER_REQ.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.L_DATA.M.005&gt;, &lt;R.LLC.L_DATA.A.006&gt;</Section> </Description> <PrimBasicElemDef> <Name>relclass</Name> <Type>U8</Type> <Comment>reliability class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_relclass</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="4" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Included from SNSM</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*"), type qos renamed to ll_qos</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_1-3 to match exactly CCI primitives</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. QoS Parameters in the MS in primitive LL_DATA_REQ include only peak throughput, and in primitive LL_UNITDATA_REQ include only peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>NOTE: The reserved elements at the end are necessary to align this structure with a KC structure in CCI_CIPHER_REQ.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.L_DATA.M.005&gt;, &lt;R.LLC.L_DATA.A.006&gt;</Section> </Description> <PrimBasicElemDef> <Name>peak</Name> <Type>U8</Type> <Comment>peak throughput</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_peak</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="4" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Included from SNSM</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*"), type qos renamed to ll_qos</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_1-3 to match exactly CCI primitives</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. QoS Parameters in the MS in primitive LL_DATA_REQ include only peak throughput, and in primitive LL_UNITDATA_REQ include only peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>NOTE: The reserved elements at the end are necessary to align this structure with a KC structure in CCI_CIPHER_REQ.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.L_DATA.M.005&gt;, &lt;R.LLC.L_DATA.A.006&gt;</Section> </Description> <PrimBasicElemDef> <Name>preced</Name> <Type>U8</Type> <Comment>precedence class</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_preced</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="4" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Included from SNSM</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*"), type qos renamed to ll_qos</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_1-3 to match exactly CCI primitives</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. QoS Parameters in the MS in primitive LL_DATA_REQ include only peak throughput, and in primitive LL_UNITDATA_REQ include only peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>NOTE: The reserved elements at the end are necessary to align this structure with a KC structure in CCI_CIPHER_REQ.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.L_DATA.M.005&gt;, &lt;R.LLC.L_DATA.A.006&gt;</Section> </Description> <PrimBasicElemDef> <Name>mean</Name> <Type>U8</Type> <Comment>main throughput</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_mean</Name> </ValuesLink> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="4" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Included from SNSM</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*"), type qos renamed to ll_qos</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_1-3 to match exactly CCI primitives</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. QoS Parameters in the MS in primitive LL_DATA_REQ include only peak throughput, and in primitive LL_UNITDATA_REQ include only peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>NOTE: The reserved elements at the end are necessary to align this structure with a KC structure in CCI_CIPHER_REQ.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.L_DATA.M.005&gt;, &lt;R.LLC.L_DATA.A.006&gt;</Section> </Description> <PrimBasicElemDef> <Name>reserved_1</Name> <Type>U8</Type> <Comment>reserved</Comment> </PrimBasicElemDef> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="4" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Included from SNSM</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*"), type qos renamed to ll_qos</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_1-3 to match exactly CCI primitives</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. QoS Parameters in the MS in primitive LL_DATA_REQ include only peak throughput, and in primitive LL_UNITDATA_REQ include only peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>NOTE: The reserved elements at the end are necessary to align this structure with a KC structure in CCI_CIPHER_REQ.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.L_DATA.M.005&gt;, &lt;R.LLC.L_DATA.A.006&gt;</Section> </Description> <PrimBasicElemDef> <Name>reserved_2</Name> <Type>U8</Type> <Comment>reserved</Comment> </PrimBasicElemDef> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="4" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Included from SNSM</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*"), type qos renamed to ll_qos</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_1-3 to match exactly CCI primitives</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>The purpose of this parameter is to specify the QoS parameters for a PDP context. QoS Parameters in the MS in primitive LL_DATA_REQ include only peak throughput, and in primitive LL_UNITDATA_REQ include only peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used.</Section> <Section>NOTE: The reserved elements at the end are necessary to align this structure with a KC structure in CCI_CIPHER_REQ.</Section> <Section>Requirements:</Section> <Section>&lt;R.LLC.L_DATA.M.005&gt;, &lt;R.LLC.L_DATA.A.006&gt;</Section> </Description> <PrimBasicElemDef> <Name>reserved_3</Name> <Type>U8</Type> <Comment>reserved</Comment> </PrimBasicElemDef> <History> <Date Day="16" Month="4" Year="1999"/> <Author>HK</Author> <Comment>Added</Comment> </History> <History> <Date Day="4" Month="6" Year="1999"/> <Author>ANS</Author> <Comment>Included from SNSM</Comment> </History> <History> <Date Day="1" Month="7" Year="1999"/> <Author>DB</Author> <Comment>Macro names changed ("LL_*"), type qos renamed to ll_qos</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included reserved_1-3 to match exactly CCI primitives</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_release_cnf</Name> <Type>U8</Type> <Comment>reserved octets for release confirm</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_data_req1</Name> <Type>U8</Type> <Comment>reserved octets</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_data_req4</Name> <Type>U32</Type> <Comment>reserved octets for data request</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_data_req5</Name> <Type>U16</Type> <Version>!REL99</Version> <Comment>reserved octets</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_unitdata_req4</Name> <Type>U32</Type> <Comment>reserved octets for unitdata request</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_unitdata_req5</Name> <Type>U16</Type> <Version>!REL99</Version> <Comment>reserved octets</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_data_ind1</Name> <Type>U32</Type> <Comment>reserved octets for data indication</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_data_ind3</Name> <Type>U8</Type> <Comment>reserved octets for data indication</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_data_ind4</Name> <Type>U8</Type> <Comment>reserved octets for data indication</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_data_ind5</Name> <Type>U8</Type> <Comment>reserved octets for data indication</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_data_ind6</Name> <Type>U8</Type> <Comment>reserved octets for data indication</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_unitdata_ind1</Name> <Type>U32</Type> <Comment>reserved octets</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_unitdata_ind3</Name> <Type>U8</Type> <Comment>reserved octets</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_unitdata_ind4</Name> <Type>U8</Type> <Comment>reserved octets</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>These parameters are used to insert reserved octets into the data structures of LL_DATA_REQ, LL_UNITDATA_REQ, LL_DATA_IND, LL_UNITDATA_IND, and LL_RELEASE_CNF, in order to align these primitives with each other, and with CCI primitives (see the specific primitive description for further details).</Section> </Description> <PrimBasicElemDef> <Name>reserved_unitdata_ind5</Name> <Type>U8</Type> <Comment>reserved octets</Comment> </PrimBasicElemDef> <History> <Date Day="8" Month="2" Year="2000"/> <Author>DB</Author> <Comment>Initial (copied from GRR-SAP)</Comment> </History> <History> <Date Day="6" Month="4" Year="2000"/> <Author>DB</Author> <Comment>Added arrays for LL_xDATA_REQ/LL_xDATA_IND</Comment> </History> <History> <Date Day="21" Month="6" Year="2000"/> <Author>DB</Author> <Comment>Included several reserved elements, renamed some old ones</Comment> </History> <History> <Date Day="13" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Alignment</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter defines the cause of the error that has occurred.</Section> <Section>Requirements:</Section> <Section><R.LLC.XIDNEG_O.A.026>, <R.LLC.XIDNEG_O.A.027></Section> </Description> <PrimBasicElemDef> <Name>error_cause</Name> <Type>U16</Type> <Comment>error cause</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_error_cause</Name> </ValuesLink> <History> <Date Day="6" Month="9" Year="2000"/> <Author>DB</Author> <Comment>Initial</Comment> </History> <History> <Date Day="20" Month="2" Year="2001"/> <Author>ZL</Author> <Comment>Added LL_ERRCS_NO_PEER_RES</Comment> </History> <History> <Date Day="10" Month="9" Year="1999"/> <Author>UT</Author> <Comment>Values of c-macro changed according to cause concept</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>Indicates the number of attached entities/services to the primitive data. Each user of this primitive must increase the counter at beginning of use and decrease the counter after use. If the counter decreases to zero the primitive data must be freed.</Section> </Description> <PrimBasicElemDef> <Name>attached_counter</Name> <Type>U8</Type> <Comment>attached to primitive data counter</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_attached_counter</Name> </ValuesLink> <History> <Date Day="2" Month="2" Year="2001"/> <Author>GS</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter indicates whether a CCI_COMP_IND is the first and/or last segment of an N-PDU.</Section> </Description> <PrimBasicElemDef> <Name>seg_pos</Name> <Type>U8</Type> <Comment>First and/or last segment of N-PDU?</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_seg_pos</Name> </ValuesLink> <History> <Date Day="7" Month="6" Year="2000"/> <Author>HK</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter defines a list of data descriptors.</Section> <Section>It is implemented as a linked list where the element 'first' is a pointer to the first generic data descriptor (see 4.18).</Section> </Description> <PrimBasicElemDef> <Name>list_len</Name> <Type>U16</Type> <Comment>length in octets of whole data</Comment> </PrimBasicElemDef> <History> <Date Day="13" Month="1" Year="2003"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This parameter defines a list of data descriptors.</Section> <Section>It is implemented as a linked list where the element 'first' is a pointer to the first generic data descriptor (see 4.18).</Section> </Description> <PrimBasicElemDef> <Name>first</Name> <Type>U32</Type> <Comment>pointer to first generic data descriptor</Comment> </PrimBasicElemDef> <History> <Date Day="13" Month="1" Year="2003"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is one element of the linked list of generic data descriptors.</Section> <Section>The member 'next' contains a pointer to the next descriptor or NULL if this is the last descriptor. The member 'offset' contains the number of octets before the first valid octet within the data buffer (which is referenced with the pointer 'buffer' ). The member 'len' contains the number of valid octets within the data buffer.</Section> </Description> <PrimBasicElemDef> <Name>next</Name> <Type>U32</Type> <Comment>next generic data descriptor</Comment> </PrimBasicElemDef> <History> <Date Day="2" Month="1" Year="2003"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is one element of the linked list of generic data descriptors.</Section> <Section>The member 'next' contains a pointer to the next descriptor or NULL if this is the last descriptor. The member 'offset' contains the number of octets before the first valid octet within the data buffer (which is referenced with the pointer 'buffer' ). The member 'len' contains the number of valid octets within the data buffer.</Section> </Description> <PrimBasicElemDef> <Name>offset</Name> <Type>U16</Type> <Comment>offset in octets</Comment> </PrimBasicElemDef> <History> <Date Day="2" Month="1" Year="2003"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is one element of the linked list of generic data descriptors.</Section> <Section>The member 'next' contains a pointer to the next descriptor or NULL if this is the last descriptor. The member 'offset' contains the number of octets before the first valid octet within the data buffer (which is referenced with the pointer 'buffer' ). The member 'len' contains the number of valid octets within the data buffer.</Section> </Description> <PrimBasicElemDef> <Name>len</Name> <Type>U16</Type> <Comment>length of content in octets</Comment> </PrimBasicElemDef> <History> <Date Day="2" Month="1" Year="2003"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section>This is one element of the linked list of generic data descriptors.</Section> <Section>The member 'next' contains a pointer to the next descriptor or NULL if this is the last descriptor. The member 'offset' contains the number of octets before the first valid octet within the data buffer (which is referenced with the pointer 'buffer' ). The member 'len' contains the number of valid octets within the data buffer.</Section> </Description> <PrimBasicElemDef> <Name>buffer</Name> <Type>U32</Type> <Comment>pointer to buffer</Comment> </PrimBasicElemDef> <History> <Date Day="2" Month="1" Year="2003"/> <Author>UT</Author> <Comment>Initial</Comment> </History> </PrimBasicElem> <PrimBasicElem> <Description> <Section/> </Description> <PrimBasicElemDef> <Name>pkt_flow_id</Name> <Type>U16</Type> <Version>REL99</Version> <Comment>packet flow identifier</Comment> </PrimBasicElemDef> <ValuesLink> <DocName DocType="SAP">ll</DocName> <Name>VAL_pkt_flow_id</Name> </ValuesLink> <History> <Date Day="12" Month="07" Year="2006"/> <Author/> <Comment>Initial</Comment> </History> </PrimBasicElem> </PrimBasicElementsSection> <ValuesSection> <Description> <Section>This section contains all sets of values that are defined for the LL 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_sapi</Name> <Comment>values for sapi</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_SAPI_1</Alias> <Comment>SAP for GMM</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>LL_SAPI_3</Alias> <Comment>SAP 1 for SNDCP</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>LL_SAPI_5</Alias> <Comment>SAP 2 for SNDCP</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">7</Value> <Alias>LL_SAPI_7</Alias> <Comment>SAP for SMS</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">9</Value> <Alias>LL_SAPI_9</Alias> <Comment>SAP 3 for SNDCP</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">11</Value> <Alias>LL_SAPI_11</Alias> <Comment>SAP 4 for SNDCP</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">255</Value> <Alias>LL_SAPI_INVALID</Alias> <Comment>invalid SAPI identifier</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_tlli</Name> <Comment>values for tlli</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">FFFFFFFF</Value> <Alias>LL_TLLI_INVALID</Alias> <Comment>invalid TLLI 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_xid_valid</Name> <Comment>values for xid_valid</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>LL_XID_INVALID</Alias> <Comment>layer-3 XID parameters are not valid</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_XID_VALID</Alias> <Comment>layer-3 XID parameters are valid</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_local</Name> <Comment>values for local</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>LL_REL_NOTLOCAL</Alias> <Comment>release both sides of the connection</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_REL_LOCAL</Alias> <Comment>local release only (no notification of the peer LLC)</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_cause</Name> <Comment>values for cause</Comment> </ValuesDef> <ValuesItem> <Value ValueType="BIN">0101000000000000</Value> <Alias>LL_RELCS_INVALID_XID</Alias> <Comment>invalid XID response</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0101000000000001</Value> <Alias>LL_RELCS_DM_RECEIVED</Alias> <Comment>DM received</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0101000000000010</Value> <Alias>LL_RELCS_NO_PEER_RES</Alias> <Comment>no peer response</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0101000000000100</Value> <Alias>LL_RELCS_NORMAL</Alias> <Comment>normal release</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_cipher</Name> <Comment>values for cipher</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>LL_CIPHER_OFF</Alias> <Comment>UI frame not ciphered</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_CIPHER_ON</Alias> <Comment>UI frame ciphered</Comment> </ValuesItem> <History> <Date Day="4" Month="11" Year="2003"/> <Author>doc2XML</Author> <Comment>Initial</Comment> </History> </Values> <Values> <Description> <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section> </Description> <ValuesDef> <Name>VAL_radio_prio</Name> <Comment>values for radio_prio</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>LL_RADIO_PRIO_1</Alias> <Comment>Radio Priority Level 1 (higest)</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_RADIO_PRIO_2</Alias> <Comment>Radio Priority Level 2</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>LL_RADIO_PRIO_3</Alias> <Comment>Radio Priority Level 3</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>LL_RADIO_PRIO_4</Alias> <Comment>Radio Priority Level 4 (lowest)</Comment> </ValuesItem> <History> <Date Day="4" Month="11" Year="2003"/> <Author>doc2XML</Author> <Comment>Initial</Comment> </History> </Values> <Values> <Description> <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section> </Description> <ValuesDef> <Name>VAL_peak</Name> <Comment>values for peak</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>LL_PEAK_SUB</Alias> <Comment>Subscribed peak throughput</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_PEAK_1K</Alias> <Comment>Up to 1 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>LL_PEAK_2K</Alias> <Comment>Up to 2 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>LL_PEAK_4K</Alias> <Comment>Up to 4 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>LL_PEAK_8K</Alias> <Comment>Up to 8 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>LL_PEAK_16K</Alias> <Comment>Up to 16 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">6</Value> <Alias>LL_PEAK_32K</Alias> <Comment>Up to 32 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">7</Value> <Alias>LL_PEAK_64K</Alias> <Comment>Up to 64 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">8</Value> <Alias>LL_PEAK_128K</Alias> <Comment>Up to 128 000 octet/s</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">9</Value> <Alias>LL_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>LL_RELCLASS_SUB</Alias> <Comment>Subscribed reliability class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_GTP_LLC_RLC_PROT</Alias> <Comment>Acknowledged GTP, LLC, and RLC; Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>LL_LLC_RLC_PROT</Alias> <Comment>Unacknowledged GTP; Acknowledged LLC and RLC, Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>LL_RLC_PROT</Alias> <Comment>Unacknowledged GTP and LLC; Acknowledged RLC, Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>LL_PROT</Alias> <Comment>Unacknowledged GTP, LLC, and RLC, Protected data</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>LL_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>LL_DELAY_SUB</Alias> <Comment>Subscribed delay class</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_DELAY_1</Alias> <Comment>Delay class 1</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>LL_DELAY_2</Alias> <Comment>Delay class 2</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>LL_DELAY_3</Alias> <Comment>Delay class 3</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>LL_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>LL_MEAN_SUB</Alias> <Comment>Subscribed mean throughput</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_MEAN_100</Alias> <Comment>100 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>LL_MEAN_200</Alias> <Comment>200 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>LL_MEAN_500</Alias> <Comment>500 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">4</Value> <Alias>LL_MEAN_1K</Alias> <Comment>1 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">5</Value> <Alias>LL_MEAN_2K</Alias> <Comment>2 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">6</Value> <Alias>LL_MEAN_5K</Alias> <Comment>5 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">7</Value> <Alias>LL_MEAN_10K</Alias> <Comment>10 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">8</Value> <Alias>LL_MEAN_20K</Alias> <Comment>20 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">9</Value> <Alias>LL_MEAN_50K</Alias> <Comment>50 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">10</Value> <Alias>LL_MEAN_100K</Alias> <Comment>100 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">11</Value> <Alias>LL_MEAN_200K</Alias> <Comment>200 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">12</Value> <Alias>LL_MEAN_500K</Alias> <Comment>500 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">13</Value> <Alias>LL_MEAN_1M</Alias> <Comment>1 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">14</Value> <Alias>LL_MEAN_2M</Alias> <Comment>2 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">15</Value> <Alias>LL_MEAN_5M</Alias> <Comment>5 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">16</Value> <Alias>LL_MEAN_10M</Alias> <Comment>10 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">17</Value> <Alias>LL_MEAN_20M</Alias> <Comment>20 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">18</Value> <Alias>LL_MEAN_50M</Alias> <Comment>50 000 000 octet/h</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">31</Value> <Alias>LL_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>LL_PRECED_SUB</Alias> <Comment>Subscribed precedence</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_PRIO_HIGH</Alias> <Comment>High priority</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>LL_PRIO_NORM</Alias> <Comment>Normal priority</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>LL_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_error_cause</Name> <Comment>values for error_cause</Comment> </ValuesDef> <ValuesItem> <Value ValueType="BIN">0101000000000000</Value> <Alias>LL_ERRCS_INVALID_XID</Alias> <Comment>invalid XID response</Comment> </ValuesItem> <ValuesItem> <Value ValueType="BIN">0101000000000010</Value> <Alias>LL_ERRCS_NO_PEER_RES</Alias> <Comment>no peer response</Comment> </ValuesItem> <History> <Date Day="4" Month="11" Year="2003"/> <Author>doc2XML</Author> <Comment>Initial</Comment> </History> </Values> <Values> <Description> <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section> </Description> <ValuesDef> <Name>VAL_attached_counter</Name> <Comment>values for attached_counter</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>LLC_NO_ATTACHE</Alias> <Comment>no entity/service is attached to the primitive</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_seg_pos</Name> <Comment>values for seg_pos</Comment> </ValuesDef> <ValuesItem> <Value ValueType="DEC">0</Value> <Alias>LL_SEG_POS_NONE</Alias> <Comment>In between</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">1</Value> <Alias>LL_SEG_POS_FIRST</Alias> <Comment>first</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">2</Value> <Alias>LL_SEG_POS_LAST</Alias> <Comment>last</Comment> </ValuesItem> <ValuesItem> <Value ValueType="DEC">3</Value> <Alias>LL_SEG_POS_FIRST_LAST</Alias> <Comment>both</Comment> </ValuesItem> <History> <Date Day="4" Month="11" Year="2003"/> <Author>doc2XML</Author> <Comment>Initial</Comment> </History> </Values> <Values> <Description> <Section/> </Description> <ValuesDef> <Name>VAL_pkt_flow_id</Name> <Version>REL99</Version> <Comment>values for pkt_flow_id</Comment> </ValuesDef> <ValuesItem> <Value ValueType="HEX">00</Value> <Alias>LL_PFI_BEST_EFFORT</Alias> <Version>REL99</Version> <Comment>best effort</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">01</Value> <Alias>LL_PFI_SIGNALING</Alias> <Version>REL99</Version> <Comment>signalling</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">02</Value> <Alias>LL_PFI_SMS</Alias> <Version>REL99</Version> <Comment>SMS</Comment> </ValuesItem> <ValuesItem> <Value ValueType="HEX">FF</Value> <Alias>LL_PKT_FLOW_ID_NOT_PRES</Alias> <Version>REL99</Version> <Comment>value FF is used to indicate when packet flwo identifier is not present</Comment> </ValuesItem> <History> <Date Day="12" Month="07" Year="2006"/> <Author/> <Comment>Initial</Comment> </History> </Values> </ValuesSection> </SAP>