FreeCalypso > hg > tcs211-l1-reconst
diff g23m/condat/com/doc/msg/sms.aim @ 0:509db1a7b7b8
initial import: leo2moko-r1
| author | Space Falcon <falcon@ivan.Harhan.ORG> |
|---|---|
| date | Mon, 01 Jun 2015 03:24:05 +0000 |
| parents | |
| children |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/g23m/condat/com/doc/msg/sms.aim Mon Jun 01 03:24:05 2015 +0000 @@ -0,0 +1,5280 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!-- edited with SAPE SAP Editor --> +<AIM xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="aim.xsd"> + <DocInfoSection> + <DocName DocType="AIM">sms</DocName> + <DocNum Number="607" Project="6147"/> + <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 base of the Protocol Stack rests on the physical layer.</Section> + <Section>The Data Link Layer (DL) is used to handle an acknowledged connection between mobile and base station. The LAPDm protocol is used.</Section> + <Section>Radio Resource (RR) manages the resources of the air-interface. That means configuration of physical layer, cell selection and cell reselection, data transfer, RR-Connection handling.</Section> + <Section>Mobility Management (MM) handles registration aspects for the mobile station. It detects changes of location areas and updates a mobile station in the new location area.</Section> + <Section>Call Control (CC) provides the call functionality. This includes call establishment, call maintenance procedures like Hold, Retrieve or Modify, and call disconnection.</Section> + <Section>Supplementary Services (SS) handles all call independent supplementary services like call forwarding or call barring.</Section> + <Section>Short Message Services (SMS) is used for sending and receiving point-to-point short messages. Additionally the reception of cell broadcast short messages is included.</Section> + <Section>The man machine interface (MMI) is the interface to the user. Normally it is connected with a keypad as input device and a display as output device.</Section> + <Section>Between the several entities data interfaces are defined. These data interfaces are called Service Access Points (SAPs), indicating that an upper layer uses the services of a lower layer.</Section> + <Section>The GSM specification do not set out any implementation of the Protocol Stack. The following diagrams show the implementation described in all these documents for the mobile station. All entities except the Man Machine Interface and Physical Layer are implemented as part of the Protocol Stack.</Section> + <Section>Figure 1: Mobile-station protocol architecture</Section> + <Section>This document describes the messages processed by the Short Message Service.</Section> + </Description> + <DocHistory> + <DocVersion Number="100" Year="97"/> + <Date Day="15" Month="1" Year="1998"/> + <Author>Stefan</Author> + <DocStatus State="BEING_PROCESSED"/> + <Comment>Lemke et al Initial</Comment> + </DocHistory> + <DocHistory> + <DocVersion Number="101" Year="97"/> + <Date Day="4" Month="2" Year="2000"/> + <Author>UB</Author> + <DocStatus State="BEING_PROCESSED"/> + <Comment>et al Condat AG change</Comment> + </DocHistory> + <DocHistory> + <DocVersion Number="102" Year="97"/> + <Date Day="11" Month="9" Year="2001"/> + <Author>FK</Author> + <DocStatus State="BEING_PROCESSED"/> + <Comment>Change for various SMS enhancements</Comment> + </DocHistory> + <DocRef> + <RefId>[1]</RefId> + <RefTitle>GSM 4.11, SMS support on the mobile radio interface ETS 300 559, ETSI, March 1996</RefTitle> + </DocRef> + <DocRef> + <RefId>[1a]</RefId> + <RefTitle>GSM 2.81, Line Identification Supplementary Services - Stage 1 ETS 300 514, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[2]</RefId> + <RefTitle>GSM 2.82, Call Forwarding Supplementary Services - Stage 1 ETS 300 515, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[3]</RefId> + <RefTitle>GSM 2.83, Call Waiting and Call Hold Supplementary Services - Stage 1 ETS 300 516, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[4]</RefId> + <RefTitle>GSM 2.84, Multi Party Supplementary Services - Stage 1 ETS 300 517, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[5]</RefId> + <RefTitle>GSM 2.85, Closed User Group Supplementary Services - Stage 1 ETS 300 518, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[6]</RefId> + <RefTitle>GSM 2.86, Advice of Charge Supplementary Services - Stage 1 ETS 300 519, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[7]</RefId> + <RefTitle>GSM 2.88, Call Barring Supplementary Services - Stage 1 ETS 300 520, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[8]</RefId> + <RefTitle>GSM 3.14, Support of Dual Tone Multi Frequency Signalling via the GSM System ETS 300 532, ETSI, April 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[9]</RefId> + <RefTitle>GSM 3.40, Technical Realization of the Short Message Service Point-to-Point ETS 300 536, ETSI, January 1996</RefTitle> + </DocRef> + <DocRef> + <RefId>[10]</RefId> + <RefTitle>GSM 3.41, Technical Realization of Short Message Service Cell Broadcast ETS 300 537, ETSI, June 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[11]</RefId> + <RefTitle>GSM 3.81, Line Identification Supplementary Services - Stage 2 ETS 300 542, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[12]</RefId> + <RefTitle>GSM 3.82, Call Forwarding Supplementary Services - Stage 2 ETS 300 543, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[13]</RefId> + <RefTitle>GSM 3.83, Call Waiting and Call Hold Supplementary Services - Stage 2 ETS 300 544, ETSI, November 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[14]</RefId> + <RefTitle>GSM 3.84, Multi Party Supplementary Services - Stage 2 ETS 300 545, ETSI, November 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[15]</RefId> + <RefTitle>GSM 3.85, Closed User Group Supplementary Services - Stage 2 ETS 300 546, ETSI, January 1996</RefTitle> + </DocRef> + <DocRef> + <RefId>[16]</RefId> + <RefTitle>GSM 3.86, Advice of Charge Supplementary Services - Stage 2 ETS 300 547, ETSI, March 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[17]</RefId> + <RefTitle>GSM 3.88, Call Barring Supplementary Services - Stage 2 ETS 300 548, ETSI, November 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[18]</RefId> + <RefTitle>GSM 4.01, MS-BSS Interface General Aspects and Principles ETS 300 550, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[18a]</RefId> + <RefTitle>GSM 4.03, MS-BSS Interface Channel Structures and Access Capabilities ETS 300 552, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[19]</RefId> + <RefTitle>GSM 4.05, Data Link Layer General Aspects ETS 300 554, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[20]</RefId> + <RefTitle>GSM 4.06, MS-BSS Interface Data Link Layer Specification ETS 300 555, ETSI, September 1994</RefTitle> + </DocRef> + <DocRef> + <RefId>[21]</RefId> + <RefTitle>GSM 4.07, Mobile Radio Interface Signalling Layer 3 General Aspects ETS 300 556, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[22]</RefId> + <RefTitle>GSM 4.08, Mobile Radio Interface Layer 3 Specification ETS 300 557, ETSI, January 1996</RefTitle> + </DocRef> + <DocRef> + <RefId>[23]</RefId> + <RefTitle>GSM 4.10, Mobile Radio Interface Layer 3 Supplementary Services Specification General Aspects ETS 300 558, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[24]</RefId> + <RefTitle>GSM 4.11, Point-to-Point Short Message Service Support on Mobile Radio Interface ETS 300 559, ETSI, October 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[25]</RefId> + <RefTitle>GSM 4.12, Short Message Service Cell Broadcast Support on Mobile Radio Interface ETS 300 560, ETSI, January 1996</RefTitle> + </DocRef> + <DocRef> + <RefId>[26]</RefId> + <RefTitle>GSM 4.80, Mobile Radio Interface Supplementary Services Specification Formats and Coding ETS 300 564, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[27]</RefId> + <RefTitle>GSM 4.81, Line Identification Supplementary Services - Stage 3 ETS 300 565, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[28]</RefId> + <RefTitle>GSM 4.82, Call Forwarding Supplementary Services - Stage 3 ETS 300 566, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[29]</RefId> + <RefTitle>GSM 4.83, Call Waiting and Call Hold Supplementary Services - Stage 3 ETS 300 567, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[30]</RefId> + <RefTitle>GSM 4.84, Multi Party Supplementary Services - Stage 3 ETS 300 568, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[31]</RefId> + <RefTitle>GSM 4.85, Closed User Group Supplementary Services - Stage 3 ETS 300 569, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[32]</RefId> + <RefTitle>GSM 4.86, Advice of Charge Supplementary Services - Stage 3 ETS 300 570, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[33]</RefId> + <RefTitle>GSM 4.88, Call Barring Supplementary Services - Stage 3 ETS 300 571, ETSI, February 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[34]</RefId> + <RefTitle>GSM 5.01, Physical Layer on the Radio Path General Description ETS 300 573, ETSI, October 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[35]</RefId> + <RefTitle>GSM 5.02, Multiplexing and Multiple Access on the Radio Path ETS 300 574, ETSI, January 1996</RefTitle> + </DocRef> + <DocRef> + <RefId>[36]</RefId> + <RefTitle>GSM 5.08, Radio Sub-system Link Control ETS 300 578, ETSI, January 1996</RefTitle> + </DocRef> + <DocRef> + <RefId>[37]</RefId> + <RefTitle>GSM 5.10, Radio Sub-system Synchronization ETS 300 579, ETSI, October 1995</RefTitle> + </DocRef> + <DocRef> + <RefId>[38]</RefId> + <RefTitle>Service Access Point MMREG 6147.100.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[39]</RefId> + <RefTitle>Service Access Point MNCC 6147.101.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[40]</RefId> + <RefTitle>Service Access Point MNSS 6147.102.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[41]</RefId> + <RefTitle>Service Access Point MNSMS 6147.103.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[42]</RefId> + <RefTitle>Service Access Point MMCC 6147.104.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[43]</RefId> + <RefTitle>Service Access Point MMSS 6147.105.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[44]</RefId> + <RefTitle>Service Access Point MMSMS 6147.106.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[45]</RefId> + <RefTitle>Service Access Point RR 6147.107.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[46]</RefId> + <RefTitle>Service Access Point SIM 6147.108.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[47]</RefId> + <RefTitle>Service Access Point MPH 6147.109.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[48]</RefId> + <RefTitle>Service Access Point DL 6147.110.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[49]</RefId> + <RefTitle>Service Access Point MDL 6147.111.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[50]</RefId> + <RefTitle>Service Access Point PH 6147.112.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[51]</RefId> + <RefTitle>Service Access Point MMI 6147.113.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[52]</RefId> + <RefTitle>Message Sequence Charts CC 6147.200.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[53]</RefId> + <RefTitle>Message Sequence Charts SS 6147.201.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[54]</RefId> + <RefTitle>Message Sequence Charts SMS 6147.202.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[55]</RefId> + <RefTitle>Message Sequence Charts MM 6147.203.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[56]</RefId> + <RefTitle>Message Sequence Charts RR 6147.204.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[57]</RefId> + <RefTitle>Message Sequence Charts DL 6147.205.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[58]</RefId> + <RefTitle>Users Guide 6147.300.96.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[59]</RefId> + <RefTitle>Test Specification CC 6147.400.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[60]</RefId> + <RefTitle>Test Specification SS 6147.401.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[61]</RefId> + <RefTitle>Test Specification SMS 6147.402.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[62]</RefId> + <RefTitle>Test Specification MM 6147.403.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[63]</RefId> + <RefTitle>Test Specification RR 6147.404.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[64]</RefId> + <RefTitle>Test Specification DL 6147.405.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[65]</RefId> + <RefTitle>Test Specification CCD 6147.406.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[66]</RefId> + <RefTitle>SDL Specification CC 6147.500.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[67]</RefId> + <RefTitle>SDL Specification SS 6147.501.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[68]</RefId> + <RefTitle>SDL Specification SMS 6147.502.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[69]</RefId> + <RefTitle>SDL Specification MM 6147.503.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[70]</RefId> + <RefTitle>SDL Specification RR 6147.504.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[71]</RefId> + <RefTitle>SDL Specification DL 6147.505.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[72]</RefId> + <RefTitle>Message Specification CC 6147.600.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[73]</RefId> + <RefTitle>Message Specification SS 6147.601.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[74]</RefId> + <RefTitle>Message Specification SMS 6147.602.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[75]</RefId> + <RefTitle>Message Specification MM 6147.603.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[76]</RefId> + <RefTitle>Message Specification RR 6147.604.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[77]</RefId> + <RefTitle>Message Specification DL 6147.605.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[78]</RefId> + <RefTitle>Technical Documentation CC 6147.700.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[79]</RefId> + <RefTitle>Technical Documentation SS 6147.701.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[80]</RefId> + <RefTitle>Technical Documentation SMS 6147.702.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[81]</RefId> + <RefTitle>Technical Documentation MM 6147.703.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[82]</RefId> + <RefTitle>Technical Documentation RR 6147.704.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[83]</RefId> + <RefTitle>Technical Documentation DL 6147.705.97.100; Condat AG</RefTitle> + </DocRef> + <DocRef> + <RefId>[84]</RefId> + <RefTitle>Technical Documentation CCD 6147.706.97.100; Condat AG</RefTitle> + </DocRef> + </DocInfoSection> + <ConstantsSection> + <Description> + <Section>This section contains all constants that are defined for the SMS AIM</Section> + </Description> + <Constant> + <Alias>SIM_PDU_BIT_LEN</Alias> + <Value ValueType="DEC">1400</Value> + <Comment>Bit length of SIM-PDU (record length of EF(SMS) minus Status Byte)</Comment> + </Constant> + <Constant> + <Alias>TPDU_BIT_LEN</Alias> + <Value ValueType="DEC">1312</Value> + <Comment>Bit length of a SMS-TPDU (164 * 8)</Comment> + </Constant> + <Constant> + <Alias>MAX_SMS_ADDR_DIG</Alias> + <Value ValueType="DEC">20</Value> + <Comment>Maximum number of address digits</Comment> + </Constant> + <Constant> + <Alias>MAX_SMS_SGL_CHAR</Alias> + <Value ValueType="DEC">160</Value> + <Comment>Maximum number of characters (septets) in a single Short Message</Comment> + </Constant> + <Constant> + <Alias>MAX_SMS_DATA_LEN</Alias> + <Value ValueType="DEC">160</Value> + <Comment>Maximum length of a data field</Comment> + </Constant> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="27" Month="4" Year="2001"/> + <Author>FK</Author> + <Comment>Supports separate CCD use for TPDUs</Comment> + </History> + <History> + <Date Day="11" Month="9" Year="2001"/> + <Author>FK</Author> + <Comment>Limiting definitions added</Comment> + </History> + </ConstantsSection> + <MessagesSection> + <Description> + <Section>This section contains all messages that are defined for the SMS AIM</Section> + </Description> + <Message> + <Description> + <Section>This message is sent between the network to the mobile station, in both directions, and is used to acknowledge the reception of a CP-DATA message.</Section> + <Section>Reference : [1] section 7.2.2</Section> + </Description> + <MsgDef> + <Name>b_cp_ack</Name> + <MsgID Direction="BOTH" IDType="BIN">00000100</MsgID> + <Comment>CP Ack</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>msg_type</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>8.1.3</SpecRef> + <Comment>CP Message Type</Comment> + </MsgItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </Message> + <Message> + <Description> + <Section>This message is sent between an MSC and an MS, in downlink directions The message contains user data to be relayed between the CM-users, and associated parameters.</Section> + <Section>Reference : [1] section 7.2.1</Section> + </Description> + <MsgDef> + <Name>d_cp_data</Name> + <MsgID Direction="DOWNLINK" IDType="BIN">00000001</MsgID> + <Comment>CP Data Downlink</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>msg_type</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>8.1.3</SpecRef> + <Comment>CP Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>cp_user_data_dl</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>8.1.4.1</SpecRef> + <Comment>CP User Data downlink</Comment> + </MsgItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </Message> + <Message> + <Description> + <Section>This message is sent between an MSC and an MS, in uplink directions The message contains user data to be relayed between the CM-users, and associated parameters.</Section> + <Section>Reference : [1] section 7.2.1</Section> + </Description> + <MsgDef> + <Name>u_cp_data</Name> + <MsgID Direction="UPLINK" IDType="BIN">00000001</MsgID> + <Comment>CP Data Uplink</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>msg_type</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>8.1.3</SpecRef> + <Comment>CP Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>cp_user_data_ul</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>8.1.4.1</SpecRef> + <Comment>CP User Data uplink</Comment> + </MsgItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </Message> + <Message> + <Description> + <Section>This message is sent between an MSC and an MS, in both directions, and is used to convey error information.</Section> + <Section>Reference : [1] section 7.2.3</Section> + </Description> + <MsgDef> + <Name>b_cp_error</Name> + <MsgID Direction="BOTH" IDType="BIN">00010000</MsgID> + <Comment>CP Error</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>msg_type</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>8.1.3</SpecRef> + <Comment>CP Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>cp_cause</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>8.1.4.2</SpecRef> + <Comment>CP Cause</Comment> + </MsgItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </Message> + <Message> + <Description> + <Section>The TP SMS-DELIVER is the mobile terminated short message. The TP-MTI element has a fixed value of 0b00.</Section> + <Section>Reference : [9] section 9.2.2.1</Section> + </Description> + <MsgDef> + <Name>tp_deliver</Name> + <MsgID Direction="DOWNLINK" IDType="ALPHA">SMS_VT_DELIVER</MsgID> + <Comment>TP SMS-DELIVER</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vt_mti</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>Virtual Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_rp</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Reply Path</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udhi</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_sri</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Status Report Indication</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>00</Pattern> + <BitLen>2</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mms</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP More Message To Send</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_oa</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>TP Origination Address</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_scts</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>TP Service Center Time Stamp</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ud</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udhi = SMS_UDHI_NOT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udh_inc</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udhi = SMS_UDHI_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data with Header included</Comment> + </MsgItem> + <History> + <Date Day="27" Month="4" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </Message> + <Message> + <Description> + <Section>The TP SMS-DELIVER-REPORT is the response from the mobile station to a received mobile terminated short message. In cause of a failure response it is sent to the network in a RP-ERROR message. The TP-MTI element has a fixed value of 0b00.</Section> + <Section>Reference : [9] section 9.2.2.1a</Section> + </Description> + <MsgDef> + <Name>tp_dlvr_rep_err</Name> + <MsgID Direction="UPLINK" IDType="ALPHA">SMS_VT_DLVR_REP_ERR</MsgID> + <Comment>TP SMS-DELIVER-REPORT (RP-ERROR)</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vt_mti</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>Virtual Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udhi</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0000</Pattern> + <BitLen>4</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_fcs</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Failure Cause</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ext</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Extension Control Bit</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0000</Pattern> + <BitLen>4</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udl_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_rsrvd</Name> + </ItemLink> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>Extension Octet</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid</Name> + </ItemLink> + <Control> + <Condition>tp_pid_p = SMS_PID_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs</Name> + </ItemLink> + <Control> + <Condition>tp_dcs_p = SMS_DCS_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ud</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_NOT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udh_inc</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data with Header included</Comment> + </MsgItem> + <History> + <Date Day="27" Month="4" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="5" Month="2" Year="2002"/> + <Author>FK</Author> + <Comment>Explicit handling of extension octet</Comment> + </History> + </Message> + <Message> + <Description> + <Section>The TP SMS-DELIVER-REPORT is the response from the mobile station to a received mobile terminated short message. In cause of a successful reception it is sent to the network in a RP-ACK message. The TP-MTI element has a fixed value of 0b00.</Section> + <Section>Reference : [9] section 9.2.2.1a</Section> + </Description> + <MsgDef> + <Name>tp_dlvr_rep_ack</Name> + <MsgID Direction="UPLINK" IDType="ALPHA">SMS_VT_DLVR_REP_ACK</MsgID> + <Comment>TP SMS-DELIVER-REPORT (RP-ACK)</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vt_mti</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>Virtual Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udhi</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0000</Pattern> + <BitLen>4</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ext</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Extension Control Bit</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0000</Pattern> + <BitLen>4</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udl_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_rsrvd</Name> + </ItemLink> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>Extension Octet</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid</Name> + </ItemLink> + <Control> + <Condition>tp_pid_p = SMS_PID_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs</Name> + </ItemLink> + <Control> + <Condition>tp_dcs_p = SMS_DCS_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ud</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_NOT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udh_inc</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data with Header included</Comment> + </MsgItem> + <History> + <Date Day="27" Month="4" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="5" Month="2" Year="2002"/> + <Author>FK</Author> + <Comment>Explicit handling of extension octet</Comment> + </History> + </Message> + <Message> + <Description> + <Section>The TP SMS-SUBMIT is the mobile originated short message. It is send to the network in a RP-DATA message. The TP-MTI element has a fixed value of 0b01.</Section> + <Section>Reference : [9] section 9.2.2.2</Section> + </Description> + <MsgDef> + <Name>tp_submit</Name> + <MsgID Direction="UPLINK" IDType="ALPHA">SMS_VT_SUBMIT</MsgID> + <Comment>TP SMS-SUBMIT</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vt_mti</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>Virtual Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_rp</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Reply Path</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udhi</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_srr</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Status Report Request</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vpf</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Validity Period Format</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_rd</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Reject Duplicates</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mr</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Reference</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_da</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>TP Destination Address</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vp_enh</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_vpf = SMS_VPF_ENHANCED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Validity Period (enhanced format)</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vp_rel</Name> + </ItemLink> + <Control> + <Condition>tp_vpf = SMS_VPF_RELATIVE</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP relative Validity Period</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vp_abs</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_vpf = SMS_VPF_ABSOLUTE</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP absolute Validity Period</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ud</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udhi = SMS_UDHI_NOT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udh_inc</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udhi = SMS_UDHI_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data with Header included</Comment> + </MsgItem> + <History> + <Date Day="2" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </Message> + <Message> + <Description> + <Section>The TP SMS-DELIVER-REPORT is the response from the network to a sent mobile originated short message. In cause of a failure response it is sent by the network in a RP-ERROR message. The TP-MTI element has a fixed value of 0b01.</Section> + <Section>Reference : [9] section 9.2.2.2a</Section> + </Description> + <MsgDef> + <Name>tp_sbmt_rep_err</Name> + <MsgID Direction="DOWNLINK" IDType="ALPHA">SMS_VT_SBMT_REP_ERR</MsgID> + <Comment>TP SMS-SUBMIT-REPORT (RP-ERROR)</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vt_mti</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>Virtual Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udhi</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0000</Pattern> + <BitLen>4</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_fcs</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Failure Cause</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ext</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Extension Control Bit</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0000</Pattern> + <BitLen>4</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udl_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_rsrvd</Name> + </ItemLink> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>Extension Octet</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_scts</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>TP Service Centre Time Stamp</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid</Name> + </ItemLink> + <Control> + <Condition>tp_pid_p = SMS_PID_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs</Name> + </ItemLink> + <Control> + <Condition>tp_dcs_p = SMS_DCS_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ud</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_NOT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udh_inc</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data with Header included</Comment> + </MsgItem> + <History> + <Date Day="2" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="5" Month="2" Year="2002"/> + <Author>FK</Author> + <Comment>Explicit handling of extension octet</Comment> + </History> + </Message> + <Message> + <Description> + <Section>The TP SMS-SUBMIT-REPORT is the response from the network to a sent mobile originated short message. In cause of a successful reception it is sent by the network in a RP-ACK message. The TP-MTI element has a fixed value of 0b01.</Section> + <Section>Reference : [9] section 9.2.2.2a</Section> + </Description> + <MsgDef> + <Name>tp_sbmt_rep_ack</Name> + <MsgID Direction="DOWNLINK" IDType="ALPHA">SMS_VT_SBMT_REP_ACK</MsgID> + <Comment>TP SMS-SUBMIT-REPORT (RP-ACK)</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vt_mti</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>Virtual Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udhi</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0000</Pattern> + <BitLen>4</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ext</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Extension Control Bit</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0000</Pattern> + <BitLen>4</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udl_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_rsrvd</Name> + </ItemLink> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>Extension Octet</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_scts</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>TP Service Centre Time Stamp</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid</Name> + </ItemLink> + <Control> + <Condition>tp_pid_p = SMS_PID_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs</Name> + </ItemLink> + <Control> + <Condition>tp_dcs_p = SMS_DCS_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ud</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_NOT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udh_inc</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data with Header included</Comment> + </MsgItem> + <History> + <Date Day="2" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="5" Month="2" Year="2002"/> + <Author>FK</Author> + <Comment>Explicit handling of extension octet</Comment> + </History> + </Message> + <Message> + <Description> + <Section>The TP SMS-STATUS-REPORT is sent by the network to report the outcome of a previously sent mobile originated short message.</Section> + <Section>Reference : [1] section 9.2.2.4</Section> + </Description> + <MsgDef> + <Name>tp_status</Name> + <MsgID Direction="DOWNLINK" IDType="ALPHA">SMS_VT_STATUS</MsgID> + <Comment>TP SMS-STATUS-REPORT</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vt_mti</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>Virtual Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udhi</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_srq</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Status Report Qualifier</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>00</Pattern> + <BitLen>2</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mms</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP More Message To Send</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mr</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Reference</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ra</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>TP Recipient Address</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_scts</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>TP Service Centre Time Stamp</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dt</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>TP Discharge Time</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_st</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Status</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0000</Pattern> + <BitLen>4</BitLen> + </Spare> + <Control> + <BitGroupDef>+</BitGroupDef> + </Control> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udl_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs_p</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid_p</Name> + </ItemLink> + <Control> + <BitGroupDef>-</BitGroupDef> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier present</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_rsrvd</Name> + </ItemLink> + <Control> + <BitGroupDef>*</BitGroupDef> + </Control> + <SpecRef>-</SpecRef> + <Comment>Extension Octet</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid</Name> + </ItemLink> + <Control> + <Condition>tp_pid_p = SMS_PID_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_dcs</Name> + </ItemLink> + <Control> + <Condition>tp_dcs_p = SMS_DCS_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Data Coding Scheme</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ud</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_NOT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udh_inc</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>tp_udl_p = SMS_UD_INCLUDED AND tp_udhi = SMS_UDHI_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP User Data with Header included</Comment> + </MsgItem> + <History> + <Date Day="2" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </Message> + <Message> + <Description> + <Section>The TP SMS-COMMAND is sent to the network to request a status report for a previously sent mobile originated short message. The TP-MTI element has a fixed value of 0b10.</Section> + <Section>Reference : [9] section 9.2.2.4</Section> + </Description> + <MsgDef> + <Name>tp_command</Name> + <MsgID Direction="UPLINK" IDType="ALPHA">SMS_VT_COMMAND</MsgID> + <Comment>TP SMS-COMMAND</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vt_mti</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>Virtual Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udhi</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_srr</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Status Report Request</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <Spare> + <Pattern>000</Pattern> + <BitLen>3</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mr</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Reference</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_pid</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Protocol Identifier</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ct</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Command Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mn</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>TP Message Number</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_da</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>TP Destination Address</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_cd</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <Control> + <Condition>tp_udhi = SMS_UDHI_NOT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Command Data</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_cdh_inc</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <Control> + <Condition>tp_udhi = SMS_UDHI_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Command Data with Header included</Comment> + </MsgItem> + <History> + <Date Day="2" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </Message> + <Message> + <Description> + <Section>This is the coding of EF(SMS) starting with the second byte of the record. The first byte is the EF record's Status Byte, which is not part of this definition. This message format is also used to exchange data between the Entities SMS and ACI with the primitives defined in SAP MNSMS</Section> + <Section>Reference : [41]</Section> + </Description> + <MsgDef> + <Name>sim_pdu</Name> + <MsgID Direction="BOTH" IDType="ALPHA">SMS_VT_SIM_PDU</MsgID> + <Comment>SMS SIM-PDU</Comment> + </MsgDef> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vt_mti</Name> + </ItemLink> + <Type>GSM3_V</Type> + <SpecRef>-</SpecRef> + <Comment>Virtual Message Type</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_addr</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>-</SpecRef> + <Comment>RP Service Center Address</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <Control> + <CmdSequence>GETPOS,:,6,+,SETPOS</CmdSequence> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgItem> + <MsgItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tpdu</Name> + </ItemLink> + <Type>GSM5_V</Type> + <Control> + <CmdSequence>SETPOS</CmdSequence> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Data Unit</Comment> + </MsgItem> + <History> + <Date Day="2" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </Message> + </MessagesSection> + <MsgStructElementsSection> + <Description> + <Section>This section contains all structured elements that are defined for the SMS AIM</Section> + </Description> + <MsgStructElem> + <Description> + <Section>The CP-User data field is used to carry the RPDU in downlink direction. The maximum length of the data field is 248 octets.</Section> + <Section>Reference : [1] section 8.1.4.1</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>cp_user_data_dl</Name> + <Comment>CP User Data downlink</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>00000</Pattern> + <BitLen>5</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Message Type Indicator</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>reference</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Message Reference</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_data_dl</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>rp_mti = RP_DATA_DL</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>RP-DATA Downlink</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_error</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>rp_mti = RP_ERROR_DL</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>RP-ERROR Downlink</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_ack</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>rp_mti = RP_ACK_DL</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>RP-ACK-Downlink</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="18" Month="11" Year="1999"/> + <Author>FK</Author> + <Comment>RP-ACK added</Comment> + </History> + <History> + <Date Day="4" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>No distinction between downlink and uplink for RP ACK/ERROR</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>The CP-User data field is used to carry the RPDU in uplink direction. The maximum length of the data field is 248 octets.</Section> + <Section>Reference : [1] section 8.1.4.1</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>cp_user_data_ul</Name> + <Comment>CP User Data Uplink</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>00000</Pattern> + <BitLen>5</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_mti</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Message Type Indicator</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>reference</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Message Reference</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_data_ul</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>rp_mti = RP_DATA_UL</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>RP-DATA Uplink</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_error</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>rp_mti = RP_ERROR_UL</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>RP-ERROR Uplink</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_ack</Name> + </ItemLink> + <Type>GSM3_V</Type> + <Control> + <Condition>rp_mti = RP_ACK_UL</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>RP-ACK-Uplink</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="18" Month="11" Year="1999"/> + <Author>FK</Author> + <Comment>RP-ACK added</Comment> + </History> + <History> + <Date Day="4" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>No distinction between downlink and uplink for RP ACK/ERROR</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>This element is a variable length element always included in the RP-ERROR message, conveying a negative result of a RP-DATA message transfer attempt or RP-SMMA notication attempt. The element contains a cause value and optionally a diagnostic field giving further details of the error cause.</Section> + <Section>Reference : [1] section 8.2.5.4</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>rp_cause</Name> + <Comment>RP Cause</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_cause_value</Name> + </ItemLink> + <Control> + <BitGroupDef>+</BitGroupDef> + </Control> + <SpecRef>-</SpecRef> + <Comment>cause value</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>diag</Name> + </ItemLink> + <Control> + <TypeModifier>[0..5]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>diagnostic field</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>This message is sent in MSC -> MS direction. The message is used to relay the TPDUs.</Section> + <Section>Reference : [1] section 7.3.1</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>rp_data_dl</Name> + <Comment>RP Data downlink</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_addr</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>-</SpecRef> + <Comment>RP Originator Address</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>00000000</Pattern> + <BitLen>8</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>RP Destination Address</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_user_data</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>-</SpecRef> + <Comment>RP User Data Downlink</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>This message is sent in MS -> MSC direction. The message is used to relay the TPDUs.</Section> + <Section>Reference : [1] section 7.3.1</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>rp_data_ul</Name> + <Comment>RP Data uplink</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>00000000</Pattern> + <BitLen>8</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>RP Originator Address</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_addr</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>-</SpecRef> + <Comment>RP Destination Address</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_user_data</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>-</SpecRef> + <Comment>RP User Data Uplink</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="13" Month="2" Year="1998"/> + <Author>SZ</Author> + <Comment>ctrl added</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>In the case of MO transfer this element contains the destination Service Center address.</Section> + <Section>Reference : [1] section 8.2.5.2</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>rp_addr</Name> + <Comment>RP Service Center Address</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>ton</Name> + </ItemLink> + <Control> + <BitGroupDef>+</BitGroupDef> + </Control> + <SpecRef>-</SpecRef> + <Comment>Type of number</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>npi</Name> + </ItemLink> + <Control> + <BitGroupDef>*</BitGroupDef> + </Control> + <SpecRef>-</SpecRef> + <Comment>Numbering plan identification</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>num</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[0..MAX_SMS_ADDR_DIG]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Number digit</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="12" Month="2" Year="1998"/> + <Author>LE</Author> + <Comment>4 -> LV4</Comment> + </History> + <History> + <Date Day="11" Month="9" Year="2001"/> + <Author>FK</Author> + <Comment>Maximum digit number derived from constant</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>This message is sent from the MSC to the MS and is used to relay an error cause from an errorneous short message or notification transfer attempt. Comment: the optional RP user data downlink is not included.</Section> + <Section>Reference : [1] section 7.3.4</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>rp_error</Name> + <Comment>RP-ERROR downlink / uplink</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_cause</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>-</SpecRef> + <Comment>RP Cause</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_user_data</Name> + </ItemLink> + <Type>GSM4_TLV</Type> + <ItemTag TagType="HEX">41</ItemTag> + <SpecRef>-</SpecRef> + <Comment>RP Error Data Downlink</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="17" Month="11" Year="1999"/> + <Author>FK</Author> + <Comment>Optional element RP-User-Data added</Comment> + </History> + <History> + <Date Day="4" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>No distinction between downlink and uplink</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>This message is sent from the MSC to the MS and is used to relay an acknowledgement from the transmission of a short message or command. The element is optional.</Section> + <Section>Reference : [1] section 7.3.3</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>rp_ack</Name> + <Comment>RP-ACK downlink / uplink</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>rp_user_data</Name> + </ItemLink> + <Type>GSM4_TLV</Type> + <ItemTag TagType="HEX">41</ItemTag> + <SpecRef>-</SpecRef> + <Comment>RP Ack Data</Comment> + </MsgStructElemItem> + <History> + <Date Day="17" Month="11" Year="1999"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="4" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>No distinction between downlink and uplink</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>The RP-User data field contains the TPDU and is mandatory in a RP-DATA message. The element has a variable length, up to 239 octets, the first octet sent being is a length indicator.</Section> + <Section>Reference : [1] section 8.2.5.3</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>rp_user_data</Name> + <Comment>RP-User Data</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_mti</Name> + </ItemLink> + <Control> + <CmdSequence>GETPOS,:,6,+,SETPOS</CmdSequence> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Message Type Indicator</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tpdu</Name> + </ItemLink> + <Type>GSM5_V</Type> + <Control> + <CmdSequence>SETPOS</CmdSequence> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Data Unit</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="5" Month="3" Year="1998"/> + <Author>SZ</Author> + <Comment>tp_mti's corrected</Comment> + </History> + <History> + <Date Day="23" Month="11" Year="1999"/> + <Author>FK</Author> + <Comment>RP-ACK and RP-ERROR separated</Comment> + </History> + <History> + <Date Day="2" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Redeclared as SDU bitstream</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>The TP Command Data field contains data relating to the operation requested by the MS which is to be performed at the SC.</Section> + <Section>Reference : [?] section 9.2.3.21, 9.2.3.24</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_cd</Name> + <Comment>TP Command Data</Comment> + </MsgStructElemDef> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_udh</Name> + <Comment>TP User Data Header</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>data</Name> + </ItemLink> + <Control> + <TypeModifier>[0..MAX_SMS_DATA_LEN]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Data</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="3" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Range from 0 to 160, coverage of TP User Data Header</Comment> + </History> + <History> + <Date Day="11" Month="9" Year="2001"/> + <Author>FK</Author> + <Comment>Maximum field length derived from constant</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>The TP Destination address contains the address of the receiving side for a mobile originated short message transfer.</Section> + <Section>Reference : [9] section 9.2.3.8</Section> + <Section>The TP Originating address contains the address of the sending side for a mobile terminated short message transfer.</Section> + <Section>Reference : [9] section 9.2.3.7</Section> + <Section>The TP Recipient address contains the address of the SME that was the destination of the previously submitted mobile originated short message being subject to the status report.</Section> + <Section>Reference : [9] section 9.2.3.14</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_da</Name> + <Comment>TP Destination Address</Comment> + </MsgStructElemDef> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_oa</Name> + <Comment>TP Originating Address</Comment> + </MsgStructElemDef> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_ra</Name> + <Comment>TP Recipient Address</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>digits</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Number of digits</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>1</Pattern> + <BitLen>1</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>ton</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Type of number</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>npi</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Numbering plan identification</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>num</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[digits..MAX_SMS_ADDR_DIG]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Number digit</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="26" Month="8" Year="1998"/> + <Author>LE</Author> + <Comment>length depends on digits, not on bytes</Comment> + </History> + <History> + <Date Day="3" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>All TP-ADDRESS definitions in one clause, spare bit new</Comment> + </History> + <History> + <Date Day="11" Month="9" Year="2001"/> + <Author>FK</Author> + <Comment>Maximum digit number derived from constant</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>The TP Validity Period (Absolute Format) field is given in semi-octet representation and gives the absolute time to which the submitted message shall exist.</Section> + <Section>Reference : [9] section 9.2.3.12.2</Section> + <Section>The TP Service Centre Time Stamp field is given in semi-octet representation and is set by the Service Center.</Section> + <Section>Reference : [9] section 9.2.3.11</Section> + <Section>The TP Discharge Time field is given in semi-octet representation and gives the time at which the Service Center attempted to deliver the message to the recipient.</Section> + <Section>Reference : [9] section 9.2.3.13</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_vp_abs</Name> + <Comment>TP Validity Period (Absolute Format)</Comment> + </MsgStructElemDef> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_scts</Name> + <Comment>TP Service Centre Time Stamp</Comment> + </MsgStructElemDef> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_dt</Name> + <Comment>TP Discharge Time</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>year</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[2]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Year</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>month</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[2]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Month</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>day</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[2]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Day</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>hour</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[2]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Hour</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>minute</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[2]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Minute</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>second</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[2]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Second</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tz_lsb</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Time Zone, LSB</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tz_sign</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Time Zone, sign</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tz_msb</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Time Zone, MSB</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="31" Month="3" Year="2000"/> + <Author>FK</Author> + <Comment>Date/time digits have fixed length of 2 semi-octets</Comment> + </History> + <History> + <Date Day="3" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>TP-VP (abolute) added</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>The TP Validity Period (Enhanced Format) provides various options for coding a validity period.</Section> + <Section>Reference : [9] section 9.2.3.12.3</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_vp_enh</Name> + <Comment>TP Validity Period (Enhanced Format)</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ext</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Extension Control Bit</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_ss</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Single Shot Bit</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>000</Pattern> + <BitLen>3</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tvpf</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Type of Validity Period Format</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>0</Pattern> + <BitLen>1</BitLen> + </Spare> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_rsrvd</Name> + </ItemLink> + <Control> + <Condition>tp_ext = SMS_EXT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>Extension Octet</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vp_rel</Name> + </ItemLink> + <Control> + <Condition>tvpf = SMS_TVPF_RELATIVE</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>TP Validity Period Relative</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_vp_sec</Name> + </ItemLink> + <Control> + <Condition>tvpf = SMS_TVPF_SECONDS</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>Validity period in seconds</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>hour</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[2]</TypeModifier> + <Condition>tvpf = SMS_TVPF_HOURS</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>Hour</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>minute</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[2]</TypeModifier> + <Condition>tvpf = SMS_TVPF_HOURS</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>Minute</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>second</Name> + </ItemLink> + <Type>BCDEVEN</Type> + <Control> + <TypeModifier>[2]</TypeModifier> + <Condition>tvpf = SMS_TVPF_HOURS</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>Second</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>00000000</Pattern> + <BitLen>8</BitLen> + </Spare> + <Control> + <Condition>tp_ext = SMS_EXT_NOT_INCLUDED</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>00000000</Pattern> + <BitLen>8</BitLen> + </Spare> + <Control> + <Condition>tvpf = SMS_TVPF_RELATIVE OR tvpf = SMS_TVPF_SECONDS</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>00000000</Pattern> + <BitLen>8</BitLen> + </Spare> + <Control> + <Condition>tvpf = SMS_TVPF_RELATIVE OR tvpf = SMS_TVPF_SECONDS</Condition> + </Control> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>00000000</Pattern> + <BitLen>8</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <Spare> + <Pattern>00000000</Pattern> + <BitLen>8</BitLen> + </Spare> + <SpecRef>-</SpecRef> + <Comment>spare</Comment> + </MsgStructElemItem> + <History> + <Date Day="3" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="5" Month="2" Year="2002"/> + <Author>FK</Author> + <Comment>Explicit handling of extension octet</Comment> + </History> + <History> + <Date Day="21" Month="11" Year="2002"/> + <Author>TLU</Author> + <Comment>Spare octets added</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>The TP User Data field contains up to 140 octets of user data.</Section> + <Section>Reference : [?] section 9.2.3.34</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_ud</Name> + <Comment>TP User Data</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>length</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Length</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>data</Name> + </ItemLink> + <Control> + <TypeModifier>[0..MAX_SMS_DATA_LEN]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Data</Comment> + </MsgStructElemItem> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="31" Month="3" Year="2000"/> + <Author>FK</Author> + <Comment>The length can be up to 160 octets, dependent of TP-MTI</Comment> + </History> + <History> + <Date Day="11" Month="9" Year="2001"/> + <Author>FK</Author> + <Comment>Maximum field length derived from constant</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>The TP User Data field contains up to 140 octets of user data including the User Data Header.</Section> + <Section>Reference : [?] section 9.2.3.24</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_udh_inc</Name> + <Comment>TP User Data with Header</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>length</Name> + </ItemLink> + <SpecRef>-</SpecRef> + <Comment>Length</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udh</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>data</Name> + </ItemLink> + <Control> + <TypeModifier>[0..MAX_SMS_DATA_LEN]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Data</Comment> + </MsgStructElemItem> + <History> + <Date Day="3" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="11" Month="9" Year="2001"/> + <Author>FK</Author> + <Comment>Maximum field length derived from constant</Comment> + </History> + </MsgStructElem> + <MsgStructElem> + <Description> + <Section>The TP User Data field contains up to 140 octets of user data.</Section> + <Section>Reference : [?] section 9.2.3.34</Section> + </Description> + <MsgStructElemDef Type="STRUCT"> + <Name>tp_cdh_inc</Name> + <Comment>TP Command Data with Header</Comment> + </MsgStructElemDef> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>tp_udh</Name> + </ItemLink> + <Type>GSM4_LV</Type> + <SpecRef>-</SpecRef> + <Comment>TP User Data Header</Comment> + </MsgStructElemItem> + <MsgStructElemItem Presentation="MANDATORY"> + <ItemLink> + <DocName DocType="AIM">sms</DocName> + <Name>data</Name> + </ItemLink> + <Control> + <TypeModifier>[0..MAX_SMS_DATA_LEN]</TypeModifier> + </Control> + <SpecRef>-</SpecRef> + <Comment>Data</Comment> + </MsgStructElemItem> + <History> + <Date Day="4" Month="5" Year="2000"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="11" Month="9" Year="2001"/> + <Author>FK</Author> + <Comment>Maximum field length derived from constant</Comment> + </History> + </MsgStructElem> + </MsgStructElementsSection> + <MsgBasicElementsSection> + <Description> + <Section>This section contains all basic elements that are defined for the SMS AIM</Section> + </Description> + <MsgBasicElem> + <Description> + <Section>This element is included in the CP-ERROR message.</Section> + <Section>Reference : [1] section 8.1.4.2</Section> + </Description> + <MsgBasicElemDef> + <Name>cp_cause</Name> + <BitLen>8</BitLen> + <Comment>CP cause</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_cp_cause</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The purpose of the message type, together with the protocol discriminator, is to identify the function of the message being sent.</Section> + <Section>Reference : [1] section 8.1.3</Section> + </Description> + <MsgBasicElemDef> + <Name>msg_type</Name> + <BitLen>8</BitLen> + <Comment>CP Message Type</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>Data is the content of a short message or a command.</Section> + </Description> + <MsgBasicElemDef> + <Name>data</Name> + <BitLen>8</BitLen> + <Comment>Data</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>This element defines the optional diagnostic field of a RP cause element.</Section> + <Section>Reference : [1] section 8.2.5.4</Section> + </Description> + <MsgBasicElemDef> + <Name>diag</Name> + <BitLen>8</BitLen> + <Comment>Diagnostic field</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The message reference field contains a sequence number in the range 0 through 255, and is used to link an RP-ACK message or RP-ERROR message to the associated (preceding) RP-DATA or RP-SMMA message transfer attempt.</Section> + <Section>Reference : [1] section 8.2.3</Section> + </Description> + <MsgBasicElemDef> + <Name>reference</Name> + <BitLen>8</BitLen> + <Comment>Message Reference</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The message type indicator is a 3-bit field, located in the first octet of all RP-messages.</Section> + <Section>Reference : [1] section 8.2.2</Section> + </Description> + <MsgBasicElemDef> + <Name>rp_mti</Name> + <BitLen>3</BitLen> + <Comment>Message Type Indicator</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_rp_mti</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>num</Name> + <BitLen>4</BitLen> + <Comment>Number digit</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>year</Name> + <BitLen>4</BitLen> + <Comment/> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>month</Name> + <BitLen>4</BitLen> + <Comment/> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>day</Name> + <BitLen>4</BitLen> + <Comment/> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>hour</Name> + <BitLen>4</BitLen> + <Comment/> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>minute</Name> + <BitLen>4</BitLen> + <Comment/> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>second</Name> + <BitLen>4</BitLen> + <Comment/> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>npi</Name> + <BitLen>4</BitLen> + <Comment>Numbering plan identification</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_npi</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>ton</Name> + <BitLen>3</BitLen> + <Comment>Type of number</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_ton</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>This element defines the RP cause value of the RP cause element.</Section> + <Section>Reference : [1] section 8.2.5.4</Section> + </Description> + <MsgBasicElemDef> + <Name>rp_cause_value</Name> + <BitLen>7</BitLen> + <Comment>RP cause</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_rp_cause_value</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The Time Zone code enables the receiver to calculate the equivalent time in GMT from the other semi-octets in the Service Centre Time Stamp, or indicate the time zone (GMT, GMT+1H etc.), or perform other similar calculations as required by the implementation.</Section> + </Description> + <MsgBasicElemDef> + <Name>tz_lsb</Name> + <BitLen>4</BitLen> + <Comment>Time Zone, LSB</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Split in 3 items</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The Time Zone code enables the receiver to calculate the equivalent time in GMT from the other semi-octets in the Service Centre Time Stamp, or indicate the time zone (GMT, GMT+1H etc.), or perform other similar calculations as required by the implementation.</Section> + </Description> + <MsgBasicElemDef> + <Name>tz_sign</Name> + <BitLen>1</BitLen> + <Comment>Time Zone, sign</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Split in 3 items</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The Time Zone code enables the receiver to calculate the equivalent time in GMT from the other semi-octets in the Service Centre Time Stamp, or indicate the time zone (GMT, GMT+1H etc.), or perform other similar calculations as required by the implementation.</Section> + </Description> + <MsgBasicElemDef> + <Name>tz_msb</Name> + <BitLen>3</BitLen> + <Comment>Time Zone, MSB</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Split in 3 items</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP-Command type is an 8 bit field specifying the type of operation that the service centre is to perform.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_ct</Name> + <BitLen>8</BitLen> + <Comment>TP Command Type</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_ct</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP-Data-Coding-Scheme field indicates the data coding scheme of the TP-UD field, and may indicate a message class.</Section> + <Section>Reference: GSM 03.38.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_dcs</Name> + <BitLen>8</BitLen> + <Comment>TP Data Coding Scheme</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_dcs</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Definitions changed</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP-Failure Cause field is used to report the reason for failure to transfer or process a short message. (MO) means used for mobile originated transfer. (MT) means used for mobile terminated transfer</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_fcs</Name> + <BitLen>8</BitLen> + <Comment>TP Failure Cause</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_fcs</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + <History> + <Date Day="12" Month="11" Year="2001"/> + <Author>FK</Author> + <Comment>Missing definitions added</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP message number is an 8 bit field allowing a mobile station to refer uniquely to an short message in the service centre which that mobile station has previously submitted. The TP-message number value is the TP-message reference of a previously submitted short message.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_mn</Name> + <BitLen>8</BitLen> + <Comment>TP Message Number</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP message reference field gives an integer representation of a reference number of the SMS submit or SMS command submitted to the service centre by the mobile station.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_mr</Name> + <BitLen>8</BitLen> + <Comment>TP Message Reference</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The parameter defines the TP Message Type Indicator.</Section> + <Section>Reference : [9] section 9.2.3.1</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_mti</Name> + <BitLen>2</BitLen> + <Comment>TP Message Type Indicator</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_mti</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="13" Month="2" Year="1998"/> + <Author>SZ</Author> + <Comment>values corrected</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP More Messages To Send is a 1-bit field, located within bit no 2 of the first octet of SMS deliver and SMS status report.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_mms</Name> + <BitLen>1</BitLen> + <Comment>TP More Messages To Send</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_mms</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP Protocol Identifier defines the protocol for the short message.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_pid</Name> + <BitLen>8</BitLen> + <Comment>TP Protocol Identifier</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_pid</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP-Reject Duplicates is a 1 bit field located within bit 2 of the first octet of SMS submit.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_rd</Name> + <BitLen>1</BitLen> + <Comment>TP Reject Duplicates</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_rd</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP Reply Path is a 1-bit field, located within bit no 7 of the first octet of both SMS deliver and SMS submit.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_rp</Name> + <BitLen>1</BitLen> + <Comment>TP Reply Path</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_rp</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP-Status field indicates the status of a previously submitted SMS submit and certain SMS commands for which a status report is requested. (T) indicates temporary error and (P) indicates permanent error.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_st</Name> + <BitLen>8</BitLen> + <Comment>TP Status</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_st</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_', comments corrected</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP Status Report Indication is a 1-bit field, located within bit no 5 of the first octet of SMS deliver.</Section> + <Section>Reference : [9] section 9.2.3.4</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_sri</Name> + <BitLen>1</BitLen> + <Comment>TP Status Report Indication</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_sri</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP Status Report Request is a 1-bit field, located within bit no 5 of the first octet of SMS submit.</Section> + <Section>Reference : [9] section 9.2.3.5</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_srr</Name> + <BitLen>1</BitLen> + <Comment>TP Status Report Request</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_srr</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP Status Report Qualifier is a 1 bit field, located within bit no 5 of the first octet of SMS status report.</Section> + <Section>Reference : [9] section 9.2.3.26</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_srq</Name> + <BitLen>1</BitLen> + <Comment>TP Status Report Qualifier</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_srq</Name> + </ValuesLink> + <History> + <Date Day="3" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP User Data Header Indicator is a 1-bit field, located within bit no 6 of the first octet of SMS submit.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_udhi</Name> + <BitLen>1</BitLen> + <Comment>TP User Data Header Indicator</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_udhi</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP Validity Period Format is a 2-bit field, located within bit no 3 and 4 of the first octet of SMS submit.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_vpf</Name> + <BitLen>2</BitLen> + <Comment>TP Validity Period Format</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_vpf</Name> + </ValuesLink> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="31" Month="3" Year="2000"/> + <Author>FK</Author> + <Comment>Definition for TP-VP (enhanced format) added</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP-Validity Period Relative format is an integer representation defining the length of the validity period. It is calculated according the following table:</Section> + <Section>TP-VP value</Section> + <Section>Validity period value</Section> + <Section>0 to 143</Section> + <Section>(TP-VP + 1) x 5 minutes (i.e. 5 minutes intervals up to 12 hours)</Section> + <Section>144 to 167</Section> + <Section>12 hours + ((TP-VP -143) x 30 minutes)</Section> + <Section>168 to 196</Section> + <Section>(TP-VP - 166) x 1 day</Section> + <Section>197 to 255</Section> + <Section>(TP-VP - 192) x 1 week</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_vp_rel</Name> + <BitLen>8</BitLen> + <Comment>TP Validity Period Relative</Comment> + </MsgBasicElemDef> + <History> + <Date Day="15" Month="1" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP User Data Present Flag is a 1-bit field, located within bit no 2 of the TP Paramater Indicator of SMS Deliver Report.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_udl_p</Name> + <BitLen>1</BitLen> + <Comment>TP User Data present</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_udl_p</Name> + </ValuesLink> + <History> + <Date Day="18" Month="11" Year="1999"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP Data Coding Scheme Present Flag is a 1-bit field, located within bit no 1 of the TP Paramater Indicator of SMS Deliver Report.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_dcs_p</Name> + <BitLen>1</BitLen> + <Comment>TP User Data Header Indicator</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_dcs_p</Name> + </ValuesLink> + <History> + <Date Day="18" Month="11" Year="1999"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The TP Protocol Identifier Present Flag is a 1-bit field, located within bit no 0 of the TP Paramater Indicator of SMS Deliver Report.</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_pid_p</Name> + <BitLen>1</BitLen> + <Comment>TP User Data Header Indicator</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_pid_p</Name> + </ValuesLink> + <History> + <Date Day="18" Month="11" Year="1999"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + <History> + <Date Day="8" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Prefixed with 'SMS_'</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The length of TP user data contains the number of 7-bit characters of the TP User Data and not the number of following bytes.</Section> + </Description> + <MsgBasicElemDef> + <Name>length</Name> + <BitLen>8</BitLen> + <Comment>Length</Comment> + </MsgBasicElemDef> + <History> + <Date Day="26" Month="3" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The parameter defines the number of digits in TP destination address, TP originator address and TP recipient address.</Section> + </Description> + <MsgBasicElemDef> + <Name>digits</Name> + <BitLen>8</BitLen> + <Comment>Digits</Comment> + </MsgBasicElemDef> + <History> + <Date Day="26" Month="3" Year="1998"/> + <Author>LE</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>This virtual message type is used to enable the CCD to handle TPDUs in a separate (de)coding step. The values are derived from the TP-MTI values given in GSM 03.40, but further distinction is made to resolve ambiguities between UPLINK/DOWNLINK and RP-ACK/RP-ERROR codings.</Section> + <Section>Reference : [9] section 9.2.3.1</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_vt_mti</Name> + <BitLen>8</BitLen> + <Comment>Virtual TP Message Type</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_vt_mti</Name> + </ValuesLink> + <History> + <Date Day="27" Month="4" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>Reference : [9] section 9.2</Section> + </Description> + <MsgBasicElemDef> + <Name>tpdu</Name> + <BitLen>TPDU_BIT_LEN</BitLen> + <Comment>TP Data Unit</Comment> + </MsgBasicElemDef> + <History> + <Date Day="27" Month="4" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>*No description found in source document*</Section> + </Description> + <MsgBasicElemDef> + <Name>tvpf</Name> + <BitLen>3</BitLen> + <Comment>Type of Validity Period Format</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tvpf</Name> + </ValuesLink> + <History> + <Date Day="3" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The validity period given in seconds for the TP VP (Enhanced Format) element.</Section> + <Section>Reference : [9] section 9.2.3.12.3</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_vp_sec</Name> + <BitLen>8</BitLen> + <Comment>Validity period in seconds</Comment> + </MsgBasicElemDef> + <History> + <Date Day="4" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The element TP Validity Period (Enhanced Format) and the octet TP Parameter Indicator are provided with an extension mechanism. Subsequent octets are not yet defined but have to be recognized.</Section> + <Section>Reference : [9] section 9.2.3.12.3, 9.2.3.27</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_rsrvd</Name> + <BitLen>7</BitLen> + <Comment>Extension Octet</Comment> + </MsgBasicElemDef> + <History> + <Date Day="4" Month="5" Year="2001"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>The extension mechanism defined for TP Validity Period (Enhanced Format) and the octet TP Parameter Indicator operates with a meaning contrary to GSM 04.08: a '1' indicates the presence of a following octet, a '0' indicates its absence. For this reasons CCDGENs built in feature of handling extended octets cannot be used.</Section> + <Section>Reference : [9] section 9.2.3.12.3, 9.2.3.27</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_ext</Name> + <BitLen>1</BitLen> + <Comment>Extension Control Bit</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_ext</Name> + </ValuesLink> + <History> + <Date Day="5" Month="2" Year="2002"/> + <Author>FK</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + <MsgBasicElem> + <Description> + <Section>If the Single Shot Bit is set to 1 then the SC is required to make up to one delivery attempt.</Section> + <Section>Reference : [9] section 9.2.3.12.3</Section> + </Description> + <MsgBasicElemDef> + <Name>tp_ss</Name> + <BitLen>1</BitLen> + <Comment>Single Shot Bit</Comment> + </MsgBasicElemDef> + <ValuesLink> + <DocName DocType="AIM">sms</DocName> + <Name>VAL_tp_ss</Name> + </ValuesLink> + <History> + <Date Day="25" Month="11" Year="2002"/> + <Author>TLU</Author> + <Comment>Initial</Comment> + </History> + </MsgBasicElem> + </MsgBasicElementsSection> + <ValuesSection> + <Description> + <Section>This section contains all sets of values that are defined for the SMS AIM</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_cp_cause</Name> + <Comment>values for cp_cause</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">17</Value> + <Alias>SMS_CP_CS_NETWORK_FAILURE</Alias> + <Comment>Network Failure</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">22</Value> + <Alias>SMS_CP_CS_CONGESTION</Alias> + <Comment>Congestion</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">81</Value> + <Alias>SMS_CP_CS_INVALID_TI</Alias> + <Comment>Invalid Transaction Identifier</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">95</Value> + <Alias>SMS_CP_CS_SEM_INC_MSG</Alias> + <Comment>Semantically incorrect message</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">96</Value> + <Alias>SMS_CP_CS_INV_MAND_INFO</Alias> + <Comment>Invalid mandatory information</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">97</Value> + <Alias>SMS_CP_CS_MSG_TYPE_NON_EXIST</Alias> + <Comment>Message type non-existent or not implemented</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">98</Value> + <Alias>SMS_CP_CS_MSG_NOT_COMP</Alias> + <Comment>Message not compatible with the short message protocol state</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">99</Value> + <Alias>SMS_CP_CS_INFO_NON_EXIST</Alias> + <Comment>Information element non-existent or not implemented</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">111</Value> + <Alias>SMS_CP_CS_PROTOCOL_ERROR</Alias> + <Comment>Protocol error, unspecified</Comment> + </ValuesItem> + <History> + <Date Day="4" Month="11" Year="2003"/> + <Author>doc2XML</Author> + <Comment>Initial</Comment> + </History> + </Values> + <Values> + <Description> + <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section> + </Description> + <ValuesDef> + <Name>VAL_rp_mti</Name> + <Comment>values for rp_mti</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>RP_DATA_UL</Alias> + <Comment>RP_DATA message MS to network</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>RP_DATA_DL</Alias> + <Comment>RP_DATA message network to MS</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">2</Value> + <Alias>RP_ACK_UL</Alias> + <Comment>RP_ACK message MS to network</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">3</Value> + <Alias>RP_ACK_DL</Alias> + <Comment>RP_ACK message network to MS</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">4</Value> + <Alias>RP_ERROR_UL</Alias> + <Comment>RP_ERROR message MS to network</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">5</Value> + <Alias>RP_ERROR_DL</Alias> + <Comment>RP_ERROR message network to MS</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">6</Value> + <Alias>RP_SMMA_UL</Alias> + <Comment>RP_SMMA message MS to network</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_npi</Name> + <Comment>values for npi</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_NPI_UNKNOWN</Alias> + <Comment>unknown</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_NPI_ISDN</Alias> + <Comment>ISDN/telephony numbering plan (Rec. E.164/E.163)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">3</Value> + <Alias>SMS_NPI_X121</Alias> + <Comment>data numbering plan (Recommendation X.121)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">4</Value> + <Alias>SMS_NPI_F69</Alias> + <Comment>telex numbering plan (Recommendation F.69)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">8</Value> + <Alias>SMS_NPI_NATIONAL</Alias> + <Comment>national numbering plan</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">9</Value> + <Alias>SMS_NPI_PRIVATE</Alias> + <Comment>private numbering plan</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">10</Value> + <Alias>SMS_NPI_ERMES</Alias> + <Comment>ERMES numbering plan (ETSI DE/PS 3 01-3)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">15</Value> + <Alias>SMS_NPI_EXTENSTION</Alias> + <Comment>reserved for extension</Comment> + </ValuesItem> + <ValuesDefault> + <Comment>reserved</Comment> + </ValuesDefault> + <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_ton</Name> + <Comment>values for ton</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_TON_UNKNOWN</Alias> + <Comment>unknown</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_TON_INTERNATIONAL</Alias> + <Comment>international number</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">2</Value> + <Alias>SMS_TON_NATIONAL</Alias> + <Comment>national number</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">3</Value> + <Alias>SMS_TON_NETWORK_SPEC</Alias> + <Comment>network specific number</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">4</Value> + <Alias>SMS_TON_SUBSCRIBER</Alias> + <Comment>dedicated access, short code</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">5</Value> + <Alias>SMS_TON_ALPHANUMERIC</Alias> + <Comment>alphanumeric</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">6</Value> + <Alias>SMS_TON_ABBREVIATED</Alias> + <Comment>abbreviated</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">7</Value> + <Alias>SMS_TON_EXTENSION</Alias> + <Comment>reserved for extention</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_rp_cause_value</Name> + <Comment>values for rp_cause_value</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_RP_CS_UNASSIGNED_NUMBER</Alias> + <Comment>Unassigned (unallocated) number</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">8</Value> + <Alias>SMS_RP_CS_OPERATOR_DET_BARRED</Alias> + <Comment>Operator determined barring</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">10</Value> + <Alias>SMS_RP_CS_CALL_BARRED</Alias> + <Comment>Call barred</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">21</Value> + <Alias>SMS_RP_CS_SM_TRANSFER_REJECTED</Alias> + <Comment>Short message transfer rejected</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">22</Value> + <Alias>SMS_RP_CS_MEM_CAP_EXCEEDED</Alias> + <Comment>Memory Capacity exceeded</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">27</Value> + <Alias>SMS_RP_CS_DEST_OUT_OF_ORDER</Alias> + <Comment>Destination out of order</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">28</Value> + <Alias>SMS_RP_CS_UNIDENT_SUBSCRIBER</Alias> + <Comment>Unidentified subscriber</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">29</Value> + <Alias>SMS_RP_CS_FACILITY_REJECTED</Alias> + <Comment>Facility rejected</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">30</Value> + <Alias>SMS_RP_CS_UNKNOWN_SUBSCRIBER</Alias> + <Comment>Unknown subscriber</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">38</Value> + <Alias>SMS_RP_CS_NET_OUT_OF_ORDER</Alias> + <Comment>Network out of order</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">41</Value> + <Alias>SMS_RP_CS_TEMP_FAILURE</Alias> + <Comment>Temporary Failure</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">42</Value> + <Alias>SMS_RP_CS_CONGESTION</Alias> + <Comment>Congestion</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">47</Value> + <Alias>SMS_RP_CS_NO_RESOURCES</Alias> + <Comment>Resources unavailable, unspecified</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">50</Value> + <Alias>SMS_RP_CS_FAC_NOT_SUBSCRIBED</Alias> + <Comment>Requested facility not subscribed</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">69</Value> + <Alias>SMS_RP_CS_FAC_NOT_IMPL</Alias> + <Comment>Requested facility not implemented</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">81</Value> + <Alias>SMS_RP_CS_INV_SM_TR_REF_VAL</Alias> + <Comment>Invalid short message transfer reference value</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">95</Value> + <Alias>SMS_RP_CS_SEM_INC_MSG</Alias> + <Comment>Semantically incorrect message</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">96</Value> + <Alias>SMS_RP_CS_INV_MAND_INFO</Alias> + <Comment>Invalid mandatory information</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">97</Value> + <Alias>SMS_RP_CS_MSG_NON_EXIST</Alias> + <Comment>Message type non-existent or not implemented</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">98</Value> + <Alias>SMS_RP_CS_MSG_NOT_COMP</Alias> + <Comment>Message not compatible with the short message protocol state</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">99</Value> + <Alias>SMS_RP_CS_INFO_NON_EXIST</Alias> + <Comment>Information element non-existent or not implemented</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">111</Value> + <Alias>SMS_RP_CS_PROTOCOL_ERROR</Alias> + <Comment>Protocol error, unspecified</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">127</Value> + <Alias>SMS_RP_CS_INTERWORKING</Alias> + <Comment>Interworking, unspecified</Comment> + </ValuesItem> + <History> + <Date Day="4" Month="11" Year="2003"/> + <Author>doc2XML</Author> + <Comment>Initial</Comment> + </History> + </Values> + <Values> + <Description> + <Section>This former local values table was generated by the doc2XML converter tool. Please exchange this description by a more meaningful one !!!</Section> + </Description> + <ValuesDef> + <Name>VAL_tp_ct</Name> + <Comment>values for tp_ct</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="HEX">00</Value> + <Alias>SMS_CT_ENQUIRY</Alias> + <Comment>Enquiry to submitted short message</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">01</Value> + <Alias>SMS_CT_CANCEL_REP</Alias> + <Comment>Cancel status report request</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">02</Value> + <Alias>SMS_CT_DELETE</Alias> + <Comment>Delete short message</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">03</Value> + <Alias>SMS_CT_ENABLE</Alias> + <Comment>Enable status report request</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_tp_dcs</Name> + <Comment>values for tp_dcs</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="HEX">00</Value> + <Alias>SMS_DCS_GRP_DEF</Alias> + <Comment>Coding group: uncompressed, no message class</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">10</Value> + <Alias>SMS_DCS_GRP_CLASS</Alias> + <Comment>Coding group: uncompressed, with message class</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">20</Value> + <Alias>SMS_DCS_GRP_COMPR</Alias> + <Comment>Coding group: compressed, no message class</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">30</Value> + <Alias>SMS_DCS_GRP_CLASS_COMPR</Alias> + <Comment>Coding group: compressed, with message class</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">C0</Value> + <Alias>SMS_DCS_GRP_MW_DISCD</Alias> + <Comment>Coding group: message waiting, discard</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">D0</Value> + <Alias>SMS_DCS_GRP_MW_STORE</Alias> + <Comment>Coding group: message waiting, store</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">E0</Value> + <Alias>SMS_DCS_GRP_MW_STORE_UCS2</Alias> + <Comment>Coding group: message waiting, store, UCS2 coded</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">F0</Value> + <Alias>SMS_DCS_DATA_CLASS</Alias> + <Comment>Coding group: data coding, with message class</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_tp_fcs</Name> + <Comment>values for tp_fcs</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="HEX">80</Value> + <Alias>SMS_FCS_TM_IW_NOT_SUP</Alias> + <Comment>Telematic interworking not supported (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">81</Value> + <Alias>SMS_FCS_SM_0_NOT_SUP</Alias> + <Comment>Short Message Type 0 not supported (MO, MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">82</Value> + <Alias>SMS_FCS_CANT_REP_SM</Alias> + <Comment>Cannot replace short message (MO, MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">8F</Value> + <Alias>SMS_FCS_TP_PID_UNSPEC</Alias> + <Comment>Unspecified TP-PID error (MO, MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">90</Value> + <Alias>SMS_FCS_DCS_NOT_SUP</Alias> + <Comment>Data coding scheme (alphabet) not supported (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">91</Value> + <Alias>SMS_FCS_CLASS_NOT_SUP</Alias> + <Comment>Message class not supported (MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">9F</Value> + <Alias>SMS_FCS_TP_DCS_UNSPEC</Alias> + <Comment>Unspecified TP-DCS error (MO, MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">A0</Value> + <Alias>SMS_FCS_CMD_CANT_ACT</Alias> + <Comment>Command cannot be actioned (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">A1</Value> + <Alias>SMS_FCS_CMD_NOT_SUP</Alias> + <Comment>Command unsupported (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">AF</Value> + <Alias>SMS_FCS_TP_CMD_UNSPEC</Alias> + <Comment>Unspecified TP-Command error (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">B0</Value> + <Alias>SMS_FCS_TPDU_NOT_SUP</Alias> + <Comment>TPDU not supported (MO, MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">C0</Value> + <Alias>SMS_FCS_SC_BUSY</Alias> + <Comment>SC busy (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">C1</Value> + <Alias>SMS_FCS_NO_SC_SUBSCRIPT</Alias> + <Comment>No SC subscription (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">C2</Value> + <Alias>SMS_FCS_SC_SYS_FAIL</Alias> + <Comment>SC system failure (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">C3</Value> + <Alias>SMS_FCS_INV_SME_ADDR</Alias> + <Comment>Invalid SME address (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">C4</Value> + <Alias>SMS_FCS_DEST_SME_BARRED</Alias> + <Comment>Destination SME barred (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">C5</Value> + <Alias>SMS_FCS_REJ_DUPL_SM</Alias> + <Comment>SM rejected-duplicate SM (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">C6</Value> + <Alias>SMS_FCS_TPVPF_NOT_SUP</Alias> + <Comment>Validity Period Format not supported (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">C7</Value> + <Alias>SMS_FCS_TPVP_NOT_SUP</Alias> + <Comment>Validity Period not supported (MO)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">D0</Value> + <Alias>SMS_FCS_SIM_MEM_FULL</Alias> + <Comment>SIM SMS storage full (MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">D1</Value> + <Alias>SMS_FCS_NO_SMS_MEM_IN_MS</Alias> + <Comment>No SMS storage capability in SIM (MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">D2</Value> + <Alias>SMS_FCS_ERROR_IN_MS</Alias> + <Comment>Error in MS (MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">D3</Value> + <Alias>SMS_FCS_MEM_CAP_EXCEED</Alias> + <Comment>Memory Capacity exceeded (MO, MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">D4</Value> + <Alias>SMS_FCS_SAT_BUSY</Alias> + <Comment>SIM Application Toolkit busy (MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">D5</Value> + <Alias>SMS_FCS_SAT_DNL_ERROR</Alias> + <Comment>SIM Data Download error (MT)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">FF</Value> + <Alias>SMS_FCS_UNSPECIFIED</Alias> + <Comment>Unspecified error cause (MO, MT)</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_tp_mti</Name> + <Comment>values for tp_mti</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_DELIVER</Alias> + <Comment>SMS deliver (SC to MS)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_DELIVER_REPORT</Alias> + <Comment>SMS deliver report (MS to SC)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">2</Value> + <Alias>SMS_STATUS_REPORT</Alias> + <Comment>SMS status report (SC to MS)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">2</Value> + <Alias>SMS_COMMAND</Alias> + <Comment>SMS command (MS to SC)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_SUBMIT</Alias> + <Comment>SMS submit (MS to SC)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_SUBMIT_REPORT</Alias> + <Comment>SMS submit report (SC to MS)</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_tp_mms</Name> + <Comment>values for tp_mms</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_MMS_MORE_MESSAGES</Alias> + <Comment>More messages are waiting for the MS in this SC</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_MMS_NO_MORE_MESSAGES</Alias> + <Comment>No more messages are waiting for the MS in this SC</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_tp_pid</Name> + <Comment>values for tp_pid</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="HEX">00</Value> + <Alias>SMS_PID_DEFAULT</Alias> + <Comment/> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">40</Value> + <Alias>SMS_PID_SM_TYPE_0</Alias> + <Comment>Short Message Type 0</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">41</Value> + <Alias>SMS_PID_REP_SM_TYPE_1</Alias> + <Comment>Replace Short Message Type 1</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">42</Value> + <Alias>SMS_PID_REP_SM_TYPE_2</Alias> + <Comment>Replace Short Message Type 2</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">43</Value> + <Alias>SMS_PID_REP_SM_TYPE_3</Alias> + <Comment>Replace Short Message Type 3</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">44</Value> + <Alias>SMS_PID_REP_SM_TYPE_4</Alias> + <Comment>Replace Short Message Type 4</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">45</Value> + <Alias>SMS_PID_REP_SM_TYPE_5</Alias> + <Comment>Replace Short Message Type 5</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">46</Value> + <Alias>SMS_PID_REP_SM_TYPE_6</Alias> + <Comment>Replace Short Message Type 6</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">47</Value> + <Alias>SMS_PID_REP_SM_TYPE_7</Alias> + <Comment>Replace Short Message Type 7</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">5F</Value> + <Alias>SMS_PID_RET_CALL_MSG</Alias> + <Comment>Return Call Message</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">7D</Value> + <Alias>SMS_PID_ME_DOWNLOAD</Alias> + <Comment>ME Data Download</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">7E</Value> + <Alias>SMS_PID_ME_DEPERSON</Alias> + <Comment>ME Depersonalization SM</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">7F</Value> + <Alias>SMS_PID_SIM_DOWNLOAD</Alias> + <Comment>SIM Data Download</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_tp_rd</Name> + <Comment>values for tp_rd</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_RD_ACCEPT</Alias> + <Comment>Accept duplicated SMS submit</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_RD_REJECT</Alias> + <Comment>Reject duplicated SMS submit</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_tp_rp</Name> + <Comment>values for tp_rp</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_RP_NOT_SET</Alias> + <Comment>TP Reply Path parameter is not set</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_RP_SET</Alias> + <Comment>TP Reply Path parameter is set</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_tp_st</Name> + <Comment>values for tp_st</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="HEX">00</Value> + <Alias>SMS_ST_SM_REC_BY_SME</Alias> + <Comment>Short message received by the SME</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">01</Value> + <Alias>SMS_ST_SM_FORW_SC</Alias> + <Comment>Short message forwarded by the SC, not confirmed</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">02</Value> + <Alias>SMS_ST_SM_REP_BY_SC</Alias> + <Comment>Short message replaced by the SC</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">20</Value> + <Alias>SMS_ST_CONGESTION</Alias> + <Comment>Congestion (T)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">21</Value> + <Alias>SMS_ST_SMS_BUSY</Alias> + <Comment>SME is busy (T)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">22</Value> + <Alias>SMS_ST_NO_RESPONSE</Alias> + <Comment>No response from the SME (T)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">23</Value> + <Alias>SMS_ST_SERV_REJ</Alias> + <Comment>Service rejected (T)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">24</Value> + <Alias>SMS_ST_QUAL_NOT_AVAIL</Alias> + <Comment>Quality of service not available (T)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">25</Value> + <Alias>SMS_ST_ERR_IN_SME</Alias> + <Comment>Error in SME (T)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">40</Value> + <Alias>SMS_ST_REM_PROC_ERR</Alias> + <Comment>Remote procedure error (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">41</Value> + <Alias>SMS_ST_INCOMP_DEST</Alias> + <Comment>Incompatible destination (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">42</Value> + <Alias>SMS_ST_CON_REJ_BY_SME</Alias> + <Comment>Connection rejected by SME (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">43</Value> + <Alias>SMS_ST_NOT_OBTAINABLE</Alias> + <Comment>Not obtainable (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">44</Value> + <Alias>SMS_ST_QUAL_NOT_AVAIL_P</Alias> + <Comment>Quality of service not available (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">45</Value> + <Alias>SMS_ST_NO_INTERWORK</Alias> + <Comment>No interworking available (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">46</Value> + <Alias>SMS_ST_SM_VP_EXP</Alias> + <Comment>Short message validity period expired (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">47</Value> + <Alias>SMS_ST_SM_DEL_BY_SME</Alias> + <Comment>Short message deleted by originating SME (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">48</Value> + <Alias>SMS_ST_SM_DEL_BY_SC</Alias> + <Comment>Short message deleted by SC administration (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">49</Value> + <Alias>SMS_ST_SM_NOT_EXIST</Alias> + <Comment>Short message not exists (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">60</Value> + <Alias>SMS_ST_CONGESTION2</Alias> + <Comment>Congestion (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">61</Value> + <Alias>SMS_ST_SMS_BUSY2</Alias> + <Comment>SME is busy (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">62</Value> + <Alias>SMS_ST_NO_RESPONSE2</Alias> + <Comment>No response from the SME (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">63</Value> + <Alias>SMS_ST_SERV_REJ2</Alias> + <Comment>Service rejected (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">64</Value> + <Alias>SMS_ST_QUAL_NOT_AVAIL2</Alias> + <Comment>Quality of service not available (P)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">65</Value> + <Alias>SMS_ST_ERR_IN_SME2</Alias> + <Comment>Error in SME (P)</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_tp_sri</Name> + <Comment>values for tp_sri</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_SRI_NO_RETURN</Alias> + <Comment>A status report will not be returned to the SME</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_SRI_RETURN</Alias> + <Comment>A status report will be returned to the SME</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_tp_srr</Name> + <Comment>values for tp_srr</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_SRR_NOT_REQUESTED</Alias> + <Comment>A status report is not requested</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_SRR_REQUESTED</Alias> + <Comment>A status report is requested</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_tp_srq</Name> + <Comment>values for tp_srq</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_SRQ_SUBMIT</Alias> + <Comment>The SMS status report is the result of a SMS submit</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_SRQ_COMMAND</Alias> + <Comment>The SMS status report is the result of a SMS command or enquiry</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_tp_udhi</Name> + <Comment>values for tp_udhi</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_UDHI_NOT_INCLUDED</Alias> + <Comment>No user data header included</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_UDHI_INCLUDED</Alias> + <Comment>User data header included</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_tp_vpf</Name> + <Comment>values for tp_vpf</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_VPF_NOT_PRESENT</Alias> + <Comment>TP-VP field not present</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_VPF_ENHANCED</Alias> + <Comment>TP-VP field present in enhanced format</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">2</Value> + <Alias>SMS_VPF_RELATIVE</Alias> + <Comment>TP-VP field present and integer represented (relative)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">3</Value> + <Alias>SMS_VPF_ABSOLUTE</Alias> + <Comment>TP-VP field present and semi-octet represented (absolute)</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_tp_udl_p</Name> + <Comment>values for tp_udl_p</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_UD_NOT_INCLUDED</Alias> + <Comment>No user data included</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_UD_INCLUDED</Alias> + <Comment>User data included</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_tp_dcs_p</Name> + <Comment>values for tp_dcs_p</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_DCS_NOT_INCLUDED</Alias> + <Comment>No data coding scheme included</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_DCS_INCLUDED</Alias> + <Comment>Data coding scheme included</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_tp_pid_p</Name> + <Comment>values for tp_pid_p</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_PID_NOT_INCLUDED</Alias> + <Comment>No protocol identifier included</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_PID_INCLUDED</Alias> + <Comment>Protocol identifier included</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_tp_vt_mti</Name> + <Comment>values for tp_vt_mti</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="HEX">20</Value> + <Alias>SMS_VT_DLVR_REP_ACK</Alias> + <Comment>TP SMS-DELIVER-REPORT in RP_ACK message, MS to network</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">21</Value> + <Alias>SMS_VT_SUBMIT</Alias> + <Comment>TP SMS-SUBMIT in RP_DATA message, MS to network</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">22</Value> + <Alias>SMS_VT_COMMAND</Alias> + <Comment>TP SMS-COMMAND in RP_DATA message, MS to network</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">24</Value> + <Alias>SMS_VT_DLVR_REP_ERR</Alias> + <Comment>TP SMS-DELIVER-REPORT in RP_ERROR message, MS to network</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">28</Value> + <Alias>SMS_VT_DELIVER</Alias> + <Comment>TP SMS-DELIVER in RP_DATA message, network to MS</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">29</Value> + <Alias>SMS_VT_SBMT_REP_ACK</Alias> + <Comment>TP SMS-SUBMIT-REPORT in RP_ACK message, network to MS</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">2A</Value> + <Alias>SMS_VT_STATUS</Alias> + <Comment>TP SMS-STATUS-REPORT in RP-DATA or RP_ACK message, network to MS</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">2B</Value> + <Alias>SMS_VT_SBMT_REP_ERR</Alias> + <Comment>TP SMS-SUBMIT-REPORT in RP_ERROR message, network to MS</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="HEX">30</Value> + <Alias>SMS_VT_SIM_PDU</Alias> + <Comment>Virtual message type for SIM-PDU used in SAP MNSMS</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_tvpf</Name> + <Comment>values for tvpf</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_TVPF_NOT_PRESENT</Alias> + <Comment>Enhanced validity period not present</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_TVPF_RELATIVE</Alias> + <Comment>Enhanced validity period relative as TP-VP (relative)</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">2</Value> + <Alias>SMS_TVPF_SECONDS</Alias> + <Comment>Enhanced validity period given in seconds 1 .. 255</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">3</Value> + <Alias>SMS_TVPF_HOURS</Alias> + <Comment>Enhanced validity period given in hours, minutes, seconds</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_tp_ext</Name> + <Comment>values for tp_ext</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_EXT_NOT_INCLUDED</Alias> + <Comment>No extension octet following</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_EXT_INCLUDED</Alias> + <Comment>Extension octet following</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_tp_ss</Name> + <Comment>values for tp_ss</Comment> + </ValuesDef> + <ValuesItem> + <Value ValueType="DEC">0</Value> + <Alias>SMS_SS_NOT_SET</Alias> + <Comment>Single Shot bit not set</Comment> + </ValuesItem> + <ValuesItem> + <Value ValueType="DEC">1</Value> + <Alias>SMS_SS_SET</Alias> + <Comment>Single Shot bit set</Comment> + </ValuesItem> + <History> + <Date Day="4" Month="11" Year="2003"/> + <Author>doc2XML</Author> + <Comment>Initial</Comment> + </History> + </Values> + </ValuesSection> +</AIM>