GSM TECHNICAL SPECIFICATION

Source: ETSI TC-SMG ICS: 33.060.50

GSM 04.80
August 1996 Version 5.0.0

Reference: TS/SMG-030480Q

Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)

Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 Supplementary services specification Formats and coding (GSM 04.80)

ETSI
European Telecommunications Standards Institute ETSI Secretariat Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr Tel.: +33 92 94 42 66 - Fax: +33 93 65 28 17
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © European Telecommunications Standards Institute 1996. All rights reserved.

Page 2 GSM 04.80 version 5.0.0: August 1996

Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to "ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3 GSM 04.80 version 5.0.0: August 1996

Contents

Foreword .......................................................................................................................................................7 1 Scope ..................................................................................................................................................9 1.1 Normative references ..........................................................................................................9 1.2 Abbreviations .....................................................................................................................10 Message functional definitions and contents ....................................................................................11 2.1 General ..............................................................................................................................11 2.2 Messages for supplementary services control...................................................................12 2.3 Facility ................................................................................................................................12 2.4 Register..............................................................................................................................13 2.4.1 Register (network to mobile station direction) ...............................................13 2.4.2 Register (mobile station to network direction) ...............................................13 2.4.2.1 SS version ...........................................................................14 2.5 Release complete ..............................................................................................................14 2.5.1 Cause ............................................................................................................14 2.5.2 Facility ...........................................................................................................14 General message format and information elements coding .............................................................15 3.1 Overview ............................................................................................................................15 3.2 Protocol discriminator ........................................................................................................15 3.3 Transaction identifier .........................................................................................................15 3.4 Message type.....................................................................................................................15 3.5 Other information elements ...............................................................................................16 3.6 Facility information element ...............................................................................................16 3.6.1 Component (octet 3 etc.)...............................................................................17 3.6.2 Component type tag ......................................................................................19 3.6.3 Component ID tag .........................................................................................19 3.6.4 Operation Code .............................................................................................20 3.6.5 Sequence and Set tags .................................................................................20 3.6.6 Error Code.....................................................................................................20 3.6.7 Problem Code ...............................................................................................20 3.7 Version handling for supplementary services ....................................................................22 3.7.1 Supplementary service screening indicator...................................................22 3.7.2 Supplementary service version indicator.......................................................22 Supplementary services operation specifications .............................................................................23 4.1 General ..............................................................................................................................23 4.2 Operation types..................................................................................................................24 4.2.1 [spare] ...........................................................................................................26 4.2.2 Operation types description...........................................................................27 4.2.2.1 RegisterSS (MS --> network)...............................................27 4.2.2.2 EraseSS (MS --> network)...................................................27 4.2.2.3 ActivateSS (MS --> network) ...............................................27 4.2.2.4 DeactivateSS (MS --> network) ...........................................27 4.2.2.5 InterrogateSS (MS --> network)...........................................27 4.2.2.6 NotifySS (network --> MS)...................................................27 4.2.2.7 RegisterPassword (MS --> network)....................................27 4.2.2.8 GetPassword (network --> MS) ...........................................27 4.2.2.9 ProcessUnstructuredSS-Data (MS --> network) .................27 4.2.2.10 ProcessUnstructuredSS-Request (MS --> network)............28 4.2.2.11 UnstructuredSS-Request (network --> MS).........................28 4.2.2.12 UnstructuredSS-Notify (network --> MS) .............................28 4.2.2.13 ForwardCheckSSIndication (network --> MS) .....................28 4.2.2.14 ForwardChargeAdvice (network --> MS) .............................28 4.2.2.15 BuildMPTY (MS --> network)...............................................28 4.2.2.16 HoldMPTY (MS --> network) ...............................................28

2

3

4

Page 4 GSM 04.80 version 5.0.0: August 1996 4.2.2.17 RetrieveMPTY (MS --> network)......................................... 28 4.2.2.18 SplitMPTY (MS --> network) ............................................... 28 4.2.2.19 ForwardCUG-Info (MS --> network).................................... 28 4.2.2.20 ExplicitCT (MS --> Network) ............................................... 28 Error types......................................................................................................................... 29 4.3.1 Error types ASN.1 specification .................................................................... 29 4.3.2 Error types description.................................................................................. 29 4.3.2.1 UnknownSubscriber............................................................ 29 4.3.2.2 BearerServiceNotProvisioned ............................................. 29 4.3.2.3 TeleServiceNotProvisioned................................................. 30 4.3.2.4 IllegalSS-Operation ............................................................. 30 4.3.2.5 SS-ErrorStatus .................................................................... 30 4.3.2.6 SS-NotAvailable .................................................................. 30 4.3.2.7 SS-SubscriptionViolation..................................................... 30 4.3.2.8 SS-Incompatibility ............................................................... 30 4.3.2.9 SystemFailure ..................................................................... 30 4.3.2.10 DataMissing ........................................................................ 30 4.3.2.11 UnexpectedDataValue ........................................................ 30 4.3.2.12 PasswordRegistrationFailure .............................................. 31 4.3.2.13 NegativePasswordCheck.................................................... 31 4.3.2.14 FacilityNotSupported........................................................... 31 4.3.2.15 ResourcesNotAvailable....................................................... 31 4.3.2.16 MaxNumberOfMPTY-ParticipantsExceeded ...................... 31 4.3.2.17 CallBarred ........................................................................... 31 4.3.2.18 NumberOfPW-AttemptsViolation ........................................ 31 4.3.2.19 AbsentSubscriber................................................................ 31 4.3.2.20 IllegalSubscriber.................................................................. 31 4.3.2.21 IllegalEquipment.................................................................. 32 4.3.2.22 USSD-Busy ......................................................................... 32 4.3.2.23 UnknownAlphabet ............................................................... 32 Data types and identifiers.................................................................................................. 33 4.4.1 General ......................................................................................................... 33 4.4.2 ASN.1 data types .......................................................................................... 33 4.4.3 Identifiers definition....................................................................................... 35 4.4.3.1 chargingInformation ............................................................ 35 4.4.3.2 e1 ........................................................................................ 35 4.4.3.3 e2 ........................................................................................ 35 4.4.3.4 e3 ........................................................................................ 36 4.4.3.5 e4 ........................................................................................ 36 4.4.3.6 e5 ........................................................................................ 36 4.4.3.7 e6 ........................................................................................ 36 4.4.3.8 e7 ........................................................................................ 36 4.4.3.9 ss-Code............................................................................... 36 4.4.3.10 ss-Notification ..................................................................... 36 4.4.3.11 ss-Status ............................................................................. 36 4.4.3.12 callsWaiting-Indicator.......................................................... 36 4.4.3.13 callOnhold-Indicator ............................................................ 36 4.4.3.14 mpty-Indicator ..................................................................... 36 4.4.3.15 forwardCUG-InfoArg ........................................................... 36 4.4.3.16 cug-Index ............................................................................ 37 4.4.3.17 suppressPrefCUG............................................................... 37 4.4.3.18 suppressOA ........................................................................ 37 4.4.3.19 clirSuppressionRejected ..................................................... 37 4.4.3.20 ect-Indicator ........................................................................ 37 4.4.3.21 ect-CallState........................................................................ 37 4.4.3.22 rdn ....................................................................................... 37 4.4.3.23 presentationAllowedAddress............................................... 37 4.4.3.24 presentationRestricted ........................................................ 37 4.4.3.25 numberNotAvailableDueToInterworking ............................. 37 4.4.3.26 presentationRestrictedAddress........................................... 37 4.4.3.27 partyNumber ....................................................................... 37 4.4.3.28 partyNumberSubaddress .................................................... 37 Operations and errors implementation.............................................................................. 38

4.3

4.4

4.5

Page 5 GSM 04.80 version 5.0.0: August 1996 Annex A (informative): Expanded ASN.1 Module "SS-Protocol" ............................................................40

History..........................................................................................................................................................52

80 version 5.0: August 1996 blank page .0.Page 6 GSM 04.

i.Page 7 GSM 04.y where: y the third digit is incremented when editorial only changes have been incorporated in the specification.0. the second digit is incremented for all other types of changes. updates. etc. These TSs may have subsequently become I-ETSs (Phase 1).0: August 1996 Foreword This Global System for Mobile communications Technical Specification (GTS) has been produced by the Special Mobile Group (SMG) Technical Committee (TC) of the European Telecommunications Standards Institute (ETSI). TC-SMG has also produced ETSI GSM TSs which give the technical specifications for the implementation of Phase 2+ enhancements of the digital cellular telecommunications system. This ensures the earliest possible access to GSM Phase 2+ specifications for all Manufacturers. These version 5. NOTE: TC-SMG has produced documents which give the technical specifications for the implementation of the digital cellular telecommunications system. or ETSs/ETSI Technical Reports (ETRs) (Phase 2). technical enhancements.x GSM Technical Specifications may be referred to as GTSs. Network operators and implementors of the Global System for Mobile communications. This ETSI GSM Technical Specification has been produced by the TC SMG Technical Committee of the European Telecommunications Standards Institute (ETSI). these documents have been identified as GSM Technical Specifications (GSM-TSs). prior to submission for the formal ETSI standards approval procedure to become European Telecommunications Standards (ETS). corrections.x.80 version 5. GSM technical specifications are produced by TC-SMG to enable the GSM Phase 2+ specifications to become publicly available.e. The contents of this GTS are subject to continuing work within TC-SMG and may change following formal TC-SMG approval. . Historically. x Reference is made within this GTS to GSM-TSs (note). Should TC-SMG modify the contents of this GTS it will then be republished by ETSI with an identifying change of release date and an increase in version number as follows: Version 5. This specification defines the coding of information necessary for support of supplementary service operation on the mobile radio interface layer 3 within the digital cellular telecommunications system (Phase 2/Phase 2+).x.

0: August 1996 Blank page .Page 8 GSM 04.80 version 5.0.

GSM 04. 1. GSM 04. GSM 04. Mobile Station .80 (ETS 300 564): "Digital cellular telecommunications system (Phase 2). subsequent amendments to or revisions of any of these publications apply to this specification only when incorporated in it by amendment or revision. For undated references the latest edition of the publication referred to applies.07 (ETS 300 556): "Digital cellular telecommunications (Phase 2). GSM 02. Mobile radio interface signalling layer 3 General aspects". system [7] [8] [9] system . Mobile radio interface layer 3 specification".Base Station system (MS . Abbreviations and acronyms". Mobile radio interface layer 3 Supplementary services specification General aspects".1 Normative references This specification incorporates by dated and undated references. Call Forwarding (CF) supplementary services . Clause 2 gives the functional definitions and contents of messages for call independent supplementary service operations. system [4] [5] system [6] GSM 04.80 version 5. provisions from other publications. GSM 04.08 (ETS 300 557): "Digital cellular telecommunications (Phase 2). Description of Charge Advice Information (CAI)".BSS) interface Data Link (DL) layer specification".0. For dated references. GSM 04.08. Messages necessary for support of call related supplementary service operations are defined in TS GSM 04.Stage 3". These normative references are cited at the appropriate places in the text and the publications are listed hereafter. Clause 4 gives the specification of the call related and call independent supplementary service operations. Mobile radio interface layer 3 supplementary services specification Formats and coding".Page 9 GSM 04. Line identification supplementary services .10 (ETS 300 558): "Digital cellular telecommunications system (Phase 2).04 (ETR 100): "Digital cellular telecommunications system (Phase 2).0: August 1996 1 Scope This specification contains the coding of information necessary for support of supplementary service operation on the mobile radio interface layer 3.81 (ETS 300 565): "Digital cellular telecommunications (Phase 2). system [2] [3] GSM 04. Clause 3 gives the general format and coding for messages used for call independent supplementary service and the format and coding of information elements used for both call related and call independent supplementary service operations.82 (ETS 300 566): "Digital cellular telecommunications (Phase 2).Stage 3". [1] GSM 01.06 (ETS 300 555): "Digital cellular telecommunications system (Phase 2).24 (ETS 300 510): "Digital cellular telecommunications (Phase 2).

system [13] [14] system [15] system [16] system [17] system [18] CCITT Recommendation X. system [11] [12] GSM 04.0.11 (ETS 300 606): "Digital cellular telecommunications (Phase 2).Stage 3".Stage 3". CCITT Recommendation X.1)". CCITT Recommendation Q.Stage 3".80 version 5.Stage 3". Multi Party (MPTY) supplementary services . GSM 04. Call Barring (CB) supplementary services .209: "Specification of Abstract Syntax Notation One (ASN.02 (ETS 300 599): "Digital cellular telecommunications (Phase 2).208: "Specification of basic encoding rules for Abstract Syntax Notation One (ASN. Advice of Charge (AoC) supplementary services .86 (ETS 300 570): "Digital cellular telecommunications (Phase 2).0: August 1996 [10] GSM 04. GSM 04.84 (ETS 300 568): "Digital cellular telecommunications (Phase 2). Closed User Group (CUG) supplementary services . Abbreviations "Transaction capabilities formats and [19] [20] 1.2 Abbreviations used in this specification are listed in GSM 01. . GSM 04.85 (ETS 300 569): "Digital cellular telecommunications system (Phase 2).90 (ETS 300 572): "Digital cellular telecommunications (Phase 2). GSM 04.88 (ETS 300 571): "Digital cellular telecommunications (Phase 2). Unstructured supplementary services operation . Signalling interworking for supplementary services".83 (ETS 300 567): "Digital cellular telecommunications system (Phase 2).Stage 3". Call Waiting (CW) and Call Hold (HOLD) supplementary services Stage 3". GSM 09. GSM 09.773: encoding". Mobile Application Part (MAP) specification".1)".04.Page 10 GSM 04.

9x-series this defines when the IE shall be included or not.Page 11 GSM 04. In a sequence of consecutive IEs with half octet length. TV or TLV. where "?" means that the maximum length of the IE is only constrained by the link layer protocol. This indication is non-normative. Each definition includes: a) b) a brief description of the message.07.80.10 or GSM 04. and a reference to a description of the value part of the IE. which is used in this and other specifications as a reference to the IE within the message. the second bits 5 to 8 of octet N. If the IEI has half octet length.8x and 04. if the IE has format T. the length of the IE (or permissible range of lengths). TV.1 Message functional definitions and contents General This clause defines the structure of the messages of the layer 3 protocol defined in TS GSM 04.0. as defined in TS GSM 04. what non-presence of such IEs means. and (for IEs with presence requirement C) the static conditions for presence and/or non-presence of the IEs (see TS GSM 04. Together with other conditions specified in TS GSM 04.80 version 5.07. the name of the type of the IE (which indicates the coding of the value part of the IE). it is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-). TLV) as defined in TS GSM 04. 2) 3) 4) 5) 6) c) Subclauses specifying conditions for IEs with presence requirement C or O in the relevant message.0: August 1996 2 2. LV. the third bits 1 to 4 of octet N+1 etc. V. the first IE occupies bits 1 to 4 of octet N. the format of the IE (T. in the message. in octets. These messages are standard L3 messages as defined in TS GSM 04.. the name of the IE (which gives an idea of the semantics of the element). in hexadecimal notation. a table listing the information elements in the order of their appearance in the message.07). the presence requirement indication (M.80.07.10. For each IE the table indicates: 1) the information element identifier. C or O) for the IE. . GSM 04. and in the case of the facility IE by possible further considerations specified in TS GSM 04.

See table 2.80 version 5.3 2.1 summarizes the messages for call independent supplementary services control.3 Message type 3. See TS GSM 04.Page 12 GSM 04. are specified in the Facility information element.0.4 Facility 3.2: FACILITY message content IEI Information element Supplementary service protocol discriminator Transaction identifier Facility message type Facility Type / Reference Protocol discriminator 3.5 This message is sent by the mobile station or the network to request or acknowledge a supplementary service. but is not to be released.1: Messages for call independent supplementary service control Messages for supplementary service control FACILITY REGISTER RELEASE COMPLETE 2.5 Presence M M M M Format V V V LV Length 1/2 1/2 1 2-? . The supplementary service to be invoked. Table 2.3 Facility Reference 2. It is used when information is to be conveyed and the transaction already exists.2 Messages for supplementary services control Table 2.4 2.0: August 1996 2. and its associated parameters. Table 2.10 for a detailed description of call independent supplementary service messages.2 Transaction identifier 3.2.

5 SS version indicator 3.4 2.80 version 5.4 Facility 3.0.2 Transaction identifier 3.4 Facility 3.3 Message type 3.2 O TLV 3 Presence M M M M Format V V V TLV Length 1/2 1/2 1 2-? .2 Transaction identifier 3.4.3: REGISTER message content (network to mobile station direction) IEI Information element Supplementary service protocol discriminator Transaction identifier Register message type 1C Facility Type / Reference Protocol discriminator 3. See table 2.5 2.0: August 1996 2.2 Register (mobile station to network direction) Presence M M M M Format V V V TLV Length 1/2 1/2 1 2-? This message is sent by the mobile station to the network to assign a new transaction identifier for call independent supplementary service control and to request or acknowledge a supplementary service.4.4: REGISTER message content (mobile station to network direction) IEI Information element Supplementary service protocol discriminator Transaction identifier Register message type 1C 7F Facility SS version Type / Reference Protocol discriminator 3. Table 2. See table 2.1 Register Register (network to mobile station direction) This message is sent by the network to the mobile station to assign a new transaction identifier for call independent supplementary service control and to request or acknowledge a supplementary service.Page 13 GSM 04.3 Message type 3.8.3. Table 2.4.

11. .5 2.2 Transaction identifier 3.2.80 version 5.0: August 1996 2.1 Cause Presence M M M O O Format V V V TLV TLV Length 1/2 1/2 1 4-32 2-? This information element shall be included when the functional handling of the Cause IE is specified in the service description or TS GSM 09. Table 2. If the functional handling of the Cause IE is not specified. 2.1 SS version This information element shall be included if the supplementary service operation being invoked is implemented according to the phase 2 GSM standards.5.10. 2.3 Message type 3.08 Facility 3.5.2 Facility This information element shall be included as required by the service description and the procedures defined in TS GSM 04. It may also request or acknowledge a supplementary service. See table 2.4 Cause TS GSM 04. the receiving entity may ignore the IE.0.5.Page 14 GSM 04.4.5: RELEASE COMPLETE message content IEI Information element Supplementary service protocol discriminator Transaction identifier Release Complete message type 08 1C Cause Facility Type / Reference Protocol discriminator 3.5 Release complete This message is sent by the mobile station or the network to release a transaction used for call independent supplementary service control.

bit 7 is coded with a "0". other information elements.07. In messages sent from the network. format and coding of transaction identifier values. .2 Protocol discriminator The Protocol Discriminator (PD) and its use are defined in TS GSM 04. 3. the bit designated "bit 1" is transmitted first. Similarly.0: August 1996 3 General message format and information elements coding The figures and text in this clause describe message contents.80 version 5. 3. 1 0 1 0 1 0 1 1 NOTE 1: NOTE 2: Message types Clearing messages: .3 supplementary services (call independent).1 defines the value part of the message type IE used in the supplementary service protocol. TS GSM 04. When a field extends over more than one octet. every message is a standard L3 message as defined in TS GSM 04. a particular information element may be present only once in a given message. This means that the message consists of the following parts: a) b) c) d) protocol discriminator.07.80 defines the protocols relating to the PD values: 1011 3.5: RELEASE COMPLETE message content 8 7 6 5 4 3 2 1 0 x 1 0 .07. transaction identifier. the order of bit values progressively decreases as the octet number increases. . Unless specified otherwise. etc.08. message type. .FACILITY . see TS GSM 04.1 Overview Within the layer 3 protocol defined in TS GSM 04. . see TS GSM 04. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. . . Table 3. Bit 7 is reserved for the send sequence number in messages sent from the mobile station. Within each octet. as required.REGISTER Bit 8 is reserved for possible future use as an extension bit.Page 15 GSM 04. followed by bits 2. Table 2. . Transaction identifier For general rules.80. 4. 3.RELEASE COMPLETE Miscellaneous message group: . 3. see TS GSM 04.07.07.4 Message type The message type IE and its use are defined in TS GSM 04. the octet shown at the top of each figure is sent first.0. 1 0 1 0 0 x 1 1 .

6 3.2 Reference (IE content) Facility information element The purpose of the Facility information element is to indicate the invocation and operation of supplementary services. The Facility information element is coded as shown in figure 3. Table 3.3 to 3. Figure 3. . The Facility is a type 4 information element with no upper length limit except that given by the maximum number of octets in a L3 message. 8 0 7 0 6 0 5 1 Facility IEI 4 1 3 1 2 0 1 0 octet 1 octet 2 octet 3 etc. .Page 16 GSM 04.5 Other information elements These information elements are coded according to the general coding rules as defined in TS GSM 04.0: August 1996 3.1: Facility information element .80 version 5. . see TS GSM 04.08 3. but the content of the Facility and SS version indicator IEs are defined within this specification. . 0 0 0 1 0 0 0 0 0 1 1 1 0 0 1 1 1 1 1 1 1 3.2 contains the code-points allocated to the information elements used in messages defined in this specification. Table 3.6 Type 3 and 4 information elements Cause Facility SS version indicator TS GSM 04.1 and tables 3.08.17.06.0. All IEs are defined in TS GSM 04.08.2: Information elements specific to call independent supplementary service control 8 7 6 5 4 3 2 1 0 . Length of Facility contents Component(s) (note) NOTE: One or more components may be included depending on specific service requirements. . identified by the corresponding operation code within the Facility information element.8. .

3 3. The parameters in tables 3.4 X.1 Component (octet 3 etc.6 may be one of the following: a Sequence of Parameters.3 to 3.Page 17 GSM 04.209 3. absent).3 X.6.6.6.3 to 3. This subclause is further based on: CCITT Recommendation X.208 and X.0: August 1996 3.4 4 Mandatory indication M M O M O . CCITT Recommendation X. NOTE: Concerning the general rules for encoding (structure of encoding.) This subclause provides the formats and encoding of components in the Facility information element.773 respectively T/S 43/BB is almost the same as the Component Portion of TC messages.209.02.209 (Specification of basic encoding rules for Abstract Syntax Notation One).1)). etc.e. Formats and encoding methods make use of and is a subset of CCITT Recommendation Q.6.209 3.209 3. a specific Parameter with its own tag (i.) see CCITT Recommendations X. a Set of Parameters. Table 3.3 3.208 and X.6.6. not part of a Sequence or Set). For these general rules the same exceptions apply as stated in TS GSM 09.6.6.80 version 5. length octets. nothing at all (i.208 (Specification of Abstract Syntax Notation One (ASN.0.209 formal description language is not used. This holds also for tables 3.e.6.3 X.3: Invoke component Invoke component Component type tag Component length Invoke ID tag Invoke ID length Invoke ID Linked ID tag Linked ID length Linked ID Operation Code tag Operation Code length Operation Code Parameters Reference 3. The only difference is that returnResultNotLast is not used.773 (Transaction Capabilities formats and Encoding) and T/S 43/BB.209 3. identifier octets. and is consistent with these CCITT Recommendations. The used part of CCITT Recommendation Q.2 X. The CCITT Recommendations X.

6.209 3.6.5 X.3 X.6.80 version 5.7 Mandatory indication M M M If the Invoke ID is not available.6.209 3.6: Reject component Mandatory indication M M M O Reject component Component type tag Component length Invoke ID tag (note) Invoke ID length Invoke ID Problem Code tag Problem Code length Problem Code NOTE: Reference 3.209 3.6.209 3.0.5: Return Error component Return Error component Component type tag Component length Invoke ID tag Invoke ID length Invoke ID Error Code tag Error Code length Error Code Parameters Reference 3.6. Table 3.4 4 Mandatory indication M M O (note) O (note) O (note) Omitted if the Return Result component does not include any parameters.6.6.209 3.6.6.4 X.6.Page 18 GSM 04.6.9) with length = 0 shall be used.7 X.2 X.209 3.3 X.209 3. .209 3.6.6 X.209 3.6.6 4 Table 3.3 3.6.2 X.2 X.209 3.3 X.0: August 1996 Table 3. Universal Null (table 3.3 3.4: Return Result component Return Result component Component type tag Component length Invoke ID tag Invoke ID length Invoke ID Sequence tag Sequence length Operation Code tag Operation Code length Operation Code Parameters NOTE: Reference 3.6.3 3.

Table 3. called an Invoke ID which is the reflection of the Invoke ID of the Invoke Component to which they are responding.0. The length of a Component ID is 1 octet.6.7: Coding of Component type tag Component type tag Invoke Return Result Return Error Reject 3. An Invoke Component has one or two Component IDs: an Invoke ID. may be rejected.6.3 Component ID tag 8 7 6 5 4 3 2 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 0 1 0 1 0 The term Component ID refers to the Invoke ID or the Linked ID. which is coded as a Universal INTEGER. Table 3.2 Component type tag The Component type tag is coded context-specific.8. . then the Linked ID is provided in addition to the Invoke ID. constructor as indicated in table 3. Universal NULL has always length = 0 Any kind of component. only the Invoke ID is used in the Reject Component. If this ID is unavailable (e. Table 3. and if it is desired to associate the Invoke with a previous Invoke.9.0: August 1996 3. The Reject Component uses as its Invoke ID.g. in order to distinguish it from the following tag (Operation Code) which is also coded as a Universal INTEGER. except a reject component. due to mutilation of the message not detected by lower layers).Page 19 GSM 04.80 version 5.8: Coding of Component ID tag Component ID tag Invoke ID Linked ID (note) NOTE: 8 7 6 5 4 3 2 1 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 This tag differs from the Invoke ID tag. the Invoke ID in the Component being rejected. then the Invoke ID tag is replaced with a universal NULL tag as shown in table 3. Return Result and Return Error Components have one Component ID. The Component ID tag is coded as shown in table 3.7.9: Coding of NULL tag 8 7 6 5 4 3 2 1 NULL tag 0 0 0 0 0 1 0 1 If an Invoke containing both Invoke and Linked IDs is being rejected.

6.11: Coding of Sequence and set tags Sequence and set tags Sequence tag Set tag 3. The tags for these elements are coded as shown in table 3.11. The Error Code tag is coded as shown in table 3.12: Coding of Error Code tag 8 7 6 5 4 3 2 1 Error Code tag The Error Codes for the different Errors are defined in subclause 4. An Operation Code follows an Operation Code tag and Operation Code length. which are coded universal.0.13: Coding of Problem tags Problem tags General Problem tag Invoke Problem tag Return Result Problem tag Return Error Problem tag 8 7 6 5 4 3 2 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 0 1 .7 Problem Code 0 0 0 0 0 0 1 0 The Problem Code consists of one of the four elements: General Problem. An Error Code follows an Error Code tag and Error Code length. they follow the Sequence or Set tag.6 Error Code 8 7 6 5 4 3 2 1 0 0 1 1 0 0 0 0 0 0 1 1 0 0 0 1 Each Error is assigned a value (Error Code) to identify it. Table 3. Return Result Problem or Return Error Problem.12.10: Coding of Operation Code tag 8 7 6 5 4 3 2 1 Operation Code tag 0 0 0 0 0 0 1 0 The Operation Codes for the different Operations are defined in subclause 4.Page 20 GSM 04.0: August 1996 3.4 Operation Code Each Operation is assigned an Operation Code to identify it. The Operation Code tag is coded as shown in table 3.13.6. constructor as shown in table 3.6. 3. Table 3. Table 3.10.5. Invoke Problem. Table 3.5 Sequence and Set tags When there is more than one parameter in a Component (applicable to all Component types).80 version 5.6. 3.5.

14: Coding of General Problem Codes General Problem Codes Unrecognized Component Mistyped Component Badly Structured Component 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 Table 3.0: August 1996 The Problem Codes for the different Problems are shown in tables 3.16: Coding of Return Result Problem Codes Return Result Problem Codes Unrecognized Invoke ID Return Result Unexpected Mistyped Parameter 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 Table 3.14 to 3.17. Table 3.Page 21 GSM 04.80 version 5.0.15: Coding of Invoke Problem Codes Invoke Problem Codes Duplicate Invoke ID Unrecognized Operation Mistyped Parameter Resource Limitation Initiating Release Unrecognized Linked ID Linked Response Unexpected Unexpected Linked Operation 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Table 3.17: Coding of Return Error Problem Codes Return Error Problem Codes Unrecognized Invoke ID Return Error Unexpected Unrecognized Error Unexpected Error Mistyped Parameter 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 0 0 1 0 1 0 .

The network shall interpret these values the same as "01".02. The network shall interpret all possible values of the SS version indicator the same as "00000000". The SS version indicator is included in messages as defined in TS GSM 04.Page 22 GSM 04.02.80 version 5.0.10.08 and GSM 04. The SS screening indicator is sent in the mobile station classmark 2 as defined in TS GSM 04.10 and GSM 09. The coding described in table 3.80. SS Error handling is described in TS GSM 04. 8 (note) NOTE: 7 (note) 6 5 4 3 (note) 2 1 SS screening indicator Values not relevant to supplementary services.10 and GSM 09. Any other octets received shall be ignored. and phase 2 error handling is supported (note 1) all other values are for future use (note 2) NOTE 1: Ellipsis notation is described in TS GSM 04. SS Error handling is described in TS GSM 04. The handling of the SS version indicator is described in TS GSM 04.7.0: August 1996 3.2 Supplementary service version indicator The purpose of the supplementary service version indicator is to allow the network to select the correct version of a protocol for a specific supplementary service.7. Table 3.2: Coding of SS screening indicator in mobile station classmark 2 Table 3.7 3.10.10. 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 NOTE 2: . Figure 3.1 Version handling for supplementary services Supplementary service screening indicator The purpose of the supplementary service screening indicator is to allow the network to asses the capabilities of the MS in advance of a network initiated SS activity. ellipsis notation.19: Coding of SS version indicator SS version indicator phase 2 service. NOTE 2: 3. The handling of the SS screening indicator is described in TS GSM 04.18: Coding of SS screening indicator in mobile station classmark 2 SS screening indicator in mobile station classmark 2 default value of phase 1 capability of handling of ellipsis notation and phase 2 error handling (note 1) for future use (note 2) for future use (note 2) NOTE 1: 6 0 0 1 1 5 0 1 0 1 Ellipsis notation is described in TS GSM 04.10.08.19 refers to the first octet received in the SS version indicator.

1 protocol description takes precedence over the diagrams in the GSM 04. When possible operations and errors are imported from TS GSM 09.8x and 04.1 comments.Page 23 GSM 04. it has to be considered as mandatory from a semantic point of view.80 including imports from TS GSM 09.209 (1998) with the same exceptions as stated in TS GSM 09.g. The encoding rules which are applicable to the defined abstract syntax are the Basic Encoding Rules for Abstract Syntax Notation One. closed user group. The ASN.208 (1998).1 Supplementary services operation specifications General This clause specifies the abstract syntax for the Supplementary Service protocol using the Abstract Syntax Notation One (ASN. except specific mention. defined in CCITT Recommendation X. defined in CCITT Recommendation X.0: August 1996 4 4.1 identifier has the same name as the corresponding parameter. but is not present according to the service description (stage 1 to stage 3). When an optional element is missing in an invoke component or in an inner data structure while it is required by the context. Ellipsis Notation shall be used in the same way as described in TS GSM 09.1). In case an element is defined as mandatory in the protocol description (TS GSM 04.02.80 version 5.9x-series of technical specifications. there is a PDU field (an ASN.1 data type which follows the keywords ARGUMENT "PARAMETER" or "RESULT" (for OPERATION and ERROR) is always optional from a syntactic point of view. the ASN. the first letter of the first word is lower-case and the first letter of the following words are capitalized (e. When in an invoke component. a mandatory element is missing in any component or inner data structure. supplementary services.02.1 notation (blanks between words are removed.02). a reject component is returned with the problem code "Mistyped Parameter".02 and shall be supported on the radio interface by the MS and the network for all operations defined in this specification including those imported from TS GSM 09. The mapping of OPERATION and ERROR to components is defined in clause 3 of this specification.02 thereby making the MSC transparent to most of the messages sent to or from the MS. the associated type of error is "DataMissing". "bearer service" is mapped to "bearerService"). Timer values for operations which require timers are shown as ASN. .0. except for the differences required by the ASN. an error component is returned. For each Supplementary Service parameter which has to be transferred by a Supplementary Service message.1 NamedType) whose ASN. In addition some words may be abbreviated as follows: ms ss cug mobile subscriber. However.

Page 24 GSM 04. ForwardChargeAdvice.exports operation types -.1: Relevance of supplementary service operations Operation name RegisterSS EraseSS ActivateSS DeactivateSS InterrogateSS RegisterPassword GetPassword ProcessUnstructuredSS-Data ForwardCheckSS-Indication ProcessUnstructuredSS-Request UnstructuredSS-Request UnstructuredSS-Notify ForwardChargeAdvice NotifySS ForwardCUG-Info BuildMPTY HoldMPTY RetrieveMPTY SplitMPTY ExplicitCT NOTE: Call related SS + + + + + + + + + Call independent SS + + + + + + + + + + + + - The ProcessUnstructuredSS-Data operation may be used call related by a phase 1 MS.10.80 version 5. ForwardCUG-Info.0: August 1996 4. IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} . BuildMPTY.2 Operation types Table 4. SplitMPTY. RetrieveMPTY.operations defined in this specification NotifySS.0. SS-Operations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Access (2) modules (3) ss-Operations (0) version2 (2)} DEFINITIONS ::= BEGIN EXPORTS -.1 summarizes the operations defined for supplementary services in this specification and shows which of these operations are call related and call independent. ExplicitCT. Table 4. HoldMPTY. The terms "call related" and "call independent" are defined in TS GSM 04.

SS-NotAvailable.80 version 5. -.ProcessUnstructuredSS-Request. ActivateSS.Page 25 GSM 04.are imported from MAP-Operations in SS-Protocol module. -.CallBarred FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version2 (2)} -. EraseSS. UnstructuredSS-Request.imports SS-Errors ResourcesNotAvailable. -. SS-ErrorStatus.0. -. SS-Incompatibility.imports MAP-errors IllegalSS-Operation.Timer T(BuildMPTY)= 5s to 30s RESULT ERRORS{ IllegalSS-Operation. InterrogateSS.RegisterPassword.The MAP operations -. MaxNumberOfMPTY-ParticipantsExceeded FROM SS-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Access (2) modules (3) ss-Errors (1) version2 (2)} .0: August 1996 -. SS-Incompatibility. UnstructuredSS-Notify -. ProcessUnstructuredSS-Data.Timer T(AoC)= 1s to 40s ForwardChargeAdviceArg OPERATION ForwardCUG-InfoArg BuildMPTY ::= OPERATION -. SS-ErrorStatus.RegisterSS. FacilityNotSupported. ForwardCUG-InfoArg FROM SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Access (2) modules (3) ss-Datatypes (2) version2 (2)} -. ResourcesNotAvailable.ForwardCheckSS-Indication -. DeactivateSS. SS-NotAvailable. SystemFailure.operation types definition NotifySS ::= ARGUMENT notifySS-Arg ForwardChargeAdvice ::= ARGUMENT forwardChargeAdviceArg RESULT ForwardCUG-Info ::= ARGUMENT forwardCUG-InfoArg OPERATION NotifySS-Arg OPERATION -. SystemFailure. GetPassword. ForwardChargeAdviceArg. MaxNumberOfMPTY-ParticipantsExceeded} .imports SS-data types NotifySS-Arg.

2. SystemFailure. SS-Incompatibility. SS-Incompatibility.Timer T(RetrieveMPTY)= 5s to 30s OPERATION -.Timer T(SplitMPTY)= 5s to 30s OPERATION -. FacilityNotSupported. ResourcesNotAvailable. SystemFailure} SplitMPTY ::= RESULT ERRORS{ IllegalSS-Operation. SystemFailure} RetrieveMPTY ::= RESULT ERRORS{ IllegalSS-Operation. SS-Incompatibility.Timer T(HoldMPTY)= 5s to 30s OPERATION -. FacilityNotSupported.Page 26 GSM 04.Timer T(ECT)= 5s to 15s 4. FacilityNotSupported. SS-NotAvailable. SS-ErrorStatus. SS-ErrorStatus. SS-ErrorStatus. FacilityNotSupported.0. SystemFailure} ExplicitCT ::= RESULT ERRORS{ IllegalSS-Operation.0: August 1996 HoldMPTY ::= RESULT ERRORS{ IllegalSS-Operation.80 version 5. CallBarred} END OPERATION -. SS-Incompatibility. SS-ErrorStatus.1 [spare] .

When no BasicService parameter is provided. . the activation applies to all provisioned and applicable basic services.2.80 version 5.2.1 RegisterSS (MS --> network) This operation type is invoked by an MS to register data related to a supplementary service in the network. 4. the erasure applies to all provisioned and applicable basic services. The operation "Register password" will be successful if the subscriber can provide the old password. the new password and the new password again as results of 3 subsequent operations "Get password". When no BasicService parameter is provided.9 ProcessUnstructuredSS-Data (MS --> network) This operation type is invoked by an MS to relay unstructured information in order to allow end to end SS operation between the MS and the network following specific rules (e. It may be used to allow the registration of a new password or the management of subscription data by the subscriber himself (e. 4. 4.2.2 Operation types description For each operation type this subclause provides a brief prose description. the registration applies to all provisioned and applicable basic services. 4. the deactivation applies to all provisioned and applicable basic services.6 NotifySS (network --> MS) This operation type is invoked by the network to forward a supplementary service notification towards a mobile subscriber.2.7 RegisterPassword (MS --> network) This operation type is invoked by an MS to register a new password related to the management by the subscriber himself of subscription data in the HLR.2.2.0.2.2. 4. embedding of keypad commands).0: August 1996 4. modification of call barring activation status).2.2.2.2. When no BasicService parameter is provided.2.2. 4. When no BasicService parameter is provided.90).g.2 EraseSS (MS --> network) This operation type is invoked by an MS to erase data related to a supplementary service in the network.g.2. 4.5 InterrogateSS (MS --> network) This operation type is invoked by an MS to request the network for a supplementary service interrogation. the interrogation applies to all provisioned and applicable basic services. The operation is used in order to provide backward compatibility (see TS GSM 04.2.3 ActivateSS (MS --> network) This operation type is invoked by an MS to request the network for a supplementary service activation.2.2.Page 27 GSM 04.2. 4. 4. When no BasicService parameter is provided.8 GetPassword (network --> MS) This operation type is invoked by the network to request a password from the mobile subscriber.4 DeactivateSS (MS --> network) This operation type is invoked by an MS to request the network for a supplementary service deactivation.

2.12 UnstructuredSS-Notify (network --> MS) This operation type is invoked by the network to give an unstructured supplementary service notification to the mobile user. The procedures for initiating ForwardCheckSSIndication are specified in TS GSM 09. 4.2. 4.80 version 5.13 ForwardCheckSSIndication (network --> MS) This operation type is invoked by the network to indicate to the mobile subscriber that the status of supplementary services may not be correct in the network.19 ForwardCUG-Info (MS --> network) This operation type is used by an MS to explicitly invoke a CUG call.17 RetrieveMPTY (MS --> network) This operation type is invoked by an MS to request retrieval of a multi party call held by that MS. 4. 4.2.2.2.2.14 ForwardChargeAdvice (network --> MS) This operation type is invoked by the network to forward Advice of Charge information to the mobile subscriber.15 BuildMPTY (MS --> network) This operation type is invoked by an MS to request the network to connect calls in a multi party call.11 UnstructuredSS-Request (network --> MS) This operation type is invoked by the network to request unstructured information from the MS in order to perform an unstructured supplementary service data application.0.2.20 ExplicitCT (MS --> Network) This operation type is invoked by an MS to request the network to connect the two calls of the subscriber.2.2.0: August 1996 4.2.2.2.2. 4.2.2.18 SplitMPTY (MS --> network) This operation type is invoked by an MS to request a private communication with one of the remote parties in a multi party call invoked by that MS.02. 4.2. 4.10 ProcessUnstructuredSS-Request (MS --> network) This operation type is invoked by an MS to start an unstructured supplementary service data application in the network.16 HoldMPTY (MS --> network) This operation type is invoked by an MS to put the MS-connection to a multi party call (invoked by that MS) on hold.2.2. 4.2. 4.2.2.Page 28 GSM 04. 4. .2.

3. -. SystemFailure.UnknownSubscriber.3.3 4.5. TeleserviceNotProvisioned. Errors from MAP are imported in the SS-Protocol module in subclause 4. IllegalSubscriber.0: August 1996 4.The MAP errors -.80 version 5. -.1 module provides an ASN.2 Error types description For each error type this subclause provides a brief prose description.3. SS-SubscriptionViolation. NegativePW-Check. BearerServiceNotProvisioned. .Page 29 GSM 04.error types definition ResourcesNotAvailable ::= ERROR MaxNumberOfMPTY-ParticipantsExceeded ::= ERROR END 4. SS-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Access (2) modules (3) ss-Errors (1) version2 (2)} DEFINITIONS ::= BEGIN IMPORTS ERROR FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)}. CallBarred.PW-RegistrationFailure.2 BearerServiceNotProvisioned This error is returned by the network when it is requested to perform an operation on a supplementary service and not even a subset of the requested bearer service group has been subscribed to. 4. IllegalEquipment. NumberOfPW-AttemptsViolation.1 Error types Error types ASN. SS-ErrorStatus. -.2. DataMissing.IllegalSS-Operation.1 specification The following ASN. UnknownAlphabet -.3. -. USSD-Busy.AbsentSubscriber. FacilityNotSupported. -.SS-Incompatibility.0. SS-NotAvailable.are imported from MAP-Errors in SS-Protocol module. 4. -.2.1 UnknownSubscriber This error is returned by the network when it is requested to perform an operation concerning an unknown subscriber. UnexpectedDataValue.1 specification of errors.

3. when it cannot perform an operation because of a failure in the network. The nature of the restriction or the transgressed options may be sent as parameters.0: August 1996 4.3. The identity and status of the conflicting service may also be indicated. 4. 4.2. 4. 4. The current status may be given as additional information by use of the SS-parameter. 4.2. 4.3. without type violation.11 UnexpectedDataValue This error is returned by the network when it receives a parameter with an unexpected value.2.2. the Basic Service Group parameter and the SS-status parameter.0. 4.3.80 version 5.9x-series of technical specifications. 4.3.2.8x and 04. The additional information may contain the SS-code parameter.2.6 SS-NotAvailable This error is returned by the network when it is requested to perform an operation on a supplementary service which is not available in the current location area.3. . registration request for a service which must be registered by the administration).3.4 IllegalSS-Operation This error is returned by the network when it is requested to perform an illegal operation which is defined as not applicable for the relevant supplementary service(s) (e.3. while it is required by the context of the request.9 SystemFailure This error is returned by the network.3 TeleServiceNotProvisioned This error is returned by the network when it is requested to perform an operation on a supplementary service and not even a subset of the requested teleservice group has been subscribed to.8 SS-Incompatibility This error is returned by the network when it is requested for a supplementary service operation incompatible with the status of an other supplementary service or with the teleservice or bearer service for which the operation is requested. see GSM 04.10 DataMissing This error is returned by the network when an optional parameter is missing in an invoke component or an inner data structure. This error shall only be used if the operation is not compatible for even a subset of the teleservice group or bearer service group specified in the request.2.5 SS-ErrorStatus This error is returned by the network when it is requested to perform an operation which is not compatible with the current status of the relevant supplementary service.Page 30 GSM 04.3. For the definition of the allowed operations for the individual supplementary services.g.2.7 SS-SubscriptionViolation This error is returned by the network when it is requested to perform an operation on a supplementary service. transgressing the subscription restrictions.2.

The parameter "operator barring" shall be included.3.2. new passwords mismatch. 4.2.g.3. 4.2. A more specific diagnostic may be passed as error parameter and indicates situations such as: invalid password format.2. This error is not used on the radio interface but only between network entities.80 version 5.13 This error is returned to indicate the negative result of a password check because the subscriber has not provided the required password or has provided a password which does not match the valid one.19 AbsentSubscriber This error is returned when the subscriber has activated the detach service or the system detects the absence condition. 4. This error is not used on the radio interface but only between network entities.3.18 NumberOfPW-AttemptsViolation This error is returned by the network to the MS when the maximum number of wrong password attempts is exceeded.2.2. a multi-party call available in the network.3. 4.3.12 PasswordRegistrationFailure This error is returned when a password registration procedure fails because of abnormal subscriber inputs.3.2. . 4.0.2.3. NegativePasswordCheck 4. 4.16 MaxNumberOfMPTY-ParticipantsExceeded This error is returned by the network to the MS if the request must be rejected because the number of subscribers to join a multi party call would exceed the maximum value.3.20 IllegalSubscriber This error is returned when illegality of the access has been established by use of authentication procedure.17 CallBarred This error is returned by the network to the MS when call independent subscriber control procedures are barred by the operator.3.15 ResourcesNotAvailable This error is returned by the network to the MS if temporarily there are no resources to support e.Page 31 GSM 04. 4.0: August 1996 4.14 FacilityNotSupported This error is returned by the network receiving a request about a facility which is not supported in the PLMN.2.

80 version 5.23 UnknownAlphabet This error is returned by the MS or the network when the alphabet/language used for the unstructured supplementary service data operation is not known by the network or the MS. This error is not used on the radio interface but only between network entities.Page 32 GSM 04.2. 4.3.22 USSD-Busy This error is returned by the MS to the network when the MS is not able to process the unstructured supplementary service data operation due to an on-going MMI input of the user or an already existing call independent supplementary service transaction. . 4.0.3.2.2.0: August 1996 4.3.21 IllegalEquipment This error is returned when the IMEI check procedure has shown that the IMEI is blacklisted or not white-listed.

1 data types This subclause provides an ASN.4 4.exports all data types defined in this module IMPORTS SS-Code FROM MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version2 (2)} -.4.0: August 1996 4.3 provides an overview of the identifiers used in SS ASN.0.1 module provided in subclause 4. Only data types which are specific for this specification are defined. All other data types are imported from MAP together with the import of operations and errors.4.1 module defining the abstract data types in operations and errors specification.4.80 version 5.Page 33 GSM 04. SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Access (2) modules (3) ss-DataTypes (2) version2 (2)} DEFINITIONS IMPLICIT TAGS ::= BEGIN -.2 ASN. ISDN-SubaddressString FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version2 (2)} .4. CUG-Index FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version2 (2)} ISDN-AddressString.2. .1 Data types and identifiers General The data types used in the SS protocol specifications are described in the ASN.1 specifications. 4. Since size constraints are subject to modifications named values have been defined in the following module for the upper boundaries of the value ranges associated to several sub-type specifications. while subclause 4.imports MAP-SS-DataTypes SS-Status.

ect-Indicator [1] [4] [5] [14] [15] [16] [17] [18] [19] SS-Code OPTIONAL.80 version 5. NULL OPTIONAL..0: August 1996 -. .. [7] E7 OPTIONAL...Page 34 GSM 04. ChargingInformation.0..max10TimesIncrement) max10TimesIncrement INTEGER ::= 8191 ..max10TimesTimeInterval) max10TimesTimeInterval INTEGER ::= 8191 E3 ::= INTEGER (0.. CUG-Index OPTIONAL. [4] E4 OPTIONAL. NULL OPTIONAL..} E1 ::= INTEGER (0. ECT-Indicator OPTIONAL } ForwardChargeAdviceArg ::= SEQUENCE{ ss-Code [0] chargingInformation [1] . SS-Notification OPTIONAL. ChargingInformation ::= SEQUENCE{ e1 e2 e3 e4 e5 e6 e7 .data types definition NotifySS-Arg ::= SEQUENCE{ ss-Code ss-Status ss-Notification callsWaiting-Indicator callOnHold-Indicator mpty-Indicator cug-Index clirSuppressionRejected . SS-Status OPTIONAL... CallOnHold-Indicator OPTIONAL. [3] E3 OPTIONAL.max10TimesUnitsPerTime) max10TimesUnitsPerTime INTEGER ::= 8191 E2 ::= INTEGER (0.} SS-Notification ::= OCTET STRING (SIZE (1)) SS-Code. [6] E6 OPTIONAL. -------------- Bit 8 7 6 5 4 Bit 3 0 1 Bit 2 0 1 Bit 1 0 1 00000 (Unused) Call is forwarded indication to A-subscriber (calling subscriber) No information content Outgoing call has been forwarded to C Call is forwarded indication to B-subscriber (forwarding subscriber) No information content Incoming call has been forwarded to C Call is forwarded indication to C-subscriber (forwarded-to subscriber) No information content Incoming call is a forwarded call [1] E1 OPTIONAL. NULL OPTIONAL.max100TimesScalingFactor) max100TimesScalingFactor INTEGER ::= 8191 E4 ::= INTEGER (0. [5] E5 OPTIONAL. [2] E2 OPTIONAL.

.maxNumberOfSegmentsPerDataInterval) maxNumberOfSegmentsPerDataInterval INTEGER ::= 8191 E7 ::= INTEGER (0.4. RemotePartyNumber} RemotePartyNumber partyNumber partyNumberSubaddress .24..1 chargingInformation The chargingInformation identifier refers to the necessary information for the Advice of Charge supplementary service.3. active (1)} RDN ::= CHOICE { presentationAllowedAddress [0] presentationRestricted [1] numberNotAvailableDueToInterworking [2] presentationRestrictedAddress [3] RemotePartyNumber. 4.. see TS GSM 02. NULL OPTIONAL.} ECT-CallState CUG-Index OPTIONAL..} ECT-Indicator ect-CallState rdn .4.80 version 5. 4.24.0: August 1996 E5 ::= INTEGER (0.max10TimesInitialTime) max10TimesInitialTime INTEGER ::= 8191 CallOnHold-Indicator ::= ENUMERATED { callRetrieved (0). See TS GSM 02.4.24. . ::= SEQUENCE { [0] ECT-CallState.3. ::= ENUMERATED { alerting (0).3 Identifiers definition The parameters which are described in the following subclauses correspond to the identifiers used in operation and error types description.0.4.3 e2 The e2 identifier refers to 10 times the length of the time interval in seconds in connection with the Advice of Charge supplementary service. 4. see TS GSM 02.max10TimesIncrementPerDataInterval) max10TimesIncrementPerDataInterval INTEGER ::= 8191 E6 ::= INTEGER (0. [1] ISDN-SubaddressString OPTIONAL. NULL.Page 35 GSM 04. callOnHold (1)} ForwardCUG-InfoArg ::= SEQUENCE { cug-Index [0] suppressPrefCUG [1] suppressOA [2] . NULL OPTIONAL. 4.. [1] RDN OPTIONAL. NULL..} END ::= SEQUENCE { [0] ISDN-AddressString.2 e1 The e1 identifier refers to 10 times the number of LPLMN units per time interval in connection with the Advice of Charge supplementary service.3....

4.12 callsWaiting-Indicator The callsWaiting-Indicator identifier refers to the indication given to the mobile station that the call is waiting.3. see TS GSM 02.4.9 ss-Code The ss-Code identifier refers to the code which identify a supplementary service or a group of supplementary services.4. 4.80 version 5.3.3.3.24. see TS GSM 02.24.14 mpty-Indicator The mpty-Indicator identifier refers to the indication given to the mobile station that the multi party call has been invoked. 4. .0: August 1996 4. see TS GSM 02.5 e4 The e4 identifier refers to 10 times the LPLMN increment in connection with the Advice of Charge supplementary service.0.15 forwardCUG-InfoArg The forwardCUG-InfoArg identifier refers to the indication given from the mobile subscriber to the network in connection with explicit invocation of a CUG call.10 ss-Notification The ss-Notification identifier refers to one or several supplementary service notifications which have to be forwarded to a mobile subscriber.3.4.6 e5 The e5 identifier refers to 10 times the number of LPLMN units incremented per data interval in connection with the Advice of Charge supplementary service. 4. see TS GSM 02. see TS GSM 02.24.4.3. 4.4.11 ss-Status The ss-Status identifier refers to the status of a supplementary service.4.4.4.3.3.3. 4.4.3.13 callOnhold-Indicator The callOnHold-Indicator identifier refers to the indication given to the mobile station that the call has been put on hold or has been retrieved. 4.7 e6 The e6 identifier refers to the number of segments per data interval in connection with the Advice of Charge supplementary service. 4.24.24. 4. 4.Page 36 GSM 04.4 e3 The e3 identifier refers to 100 times the scaling factor to convert from LPLMN units to HPLMN units in connection with the Advice of Charge supplementary service.3.4. 4.4.4.8 e7 The e7 identifier refers to 10 times the length of the initial time interval in seconds in connection with the Advice of Charge supplementary service.3.

4.3.4.0: August 1996 4.3. 4.27 partyNumber The partyNumber identifier refers to the remote party number. 4.4.4.4.4.0.4.22 rdn The Rdn identifier refers to the line identity information of the other remote party. . 4.3.3.Page 37 GSM 04.3. 4.3.3.23 presentationAllowedAddress The presentationAllowedAddress identifier refers to the line identity of the other remote party that is allowed to be presented. 4.3.26 presentationRestrictedAddress The presentationRestrictedAddress identifier refers to the line identity of the other remote party which presentation restriction is overridden.3.18 suppressOA The suppressOA identifier refers to the mobile subscribers request to the network to prohibit the use of the subscriber option "OA allowed". 4.80 version 5. 4.3. 4.21 ect-CallState The ect-CallState identifier refers to the state of the call to the other remote party in which Explicit Call Transfer was invoked. 4. 4. 4.20 ect-Indicator The ect-Indicator identifier refers to the indication given to the mobile station that the call was transferred.3.4.16 cug-Index The cug-Index identifier refers to the index of a CUG given in an explicit invocation of a CUG call.4.4.24 presentationRestricted The presentationRestricted identifier refers to the restriction of presentation of the line identity of the other remote party .4.3.3.17 suppressPrefCUG The suppressPrefCUG identifier refers to the mobile subscribers request to the network to prohibit the use of the preferential CUG.4.19 clirSuppressionRejected The clirSuppressionRejected identifier refers to the indication given to the mobile station that the CLIR suppression request has been rejected.28 partyNumberSubaddress The partyNumberSubaddress identifier refers to remote party number subaddress.25 numberNotAvailableDueToInterworking The numberNotAvailableDueToInterworking identifier refers to the unavailability of the line identity of the other remote party. 4.4.

imports operation types from the ASN. HoldMPTY. UnstructuredSS-Notify FROM MAP-SupplementaryServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) version2 (2)} -. TeleserviceNotProvisioned. NegativePW-Check. ActivateSS. IllegalSS-Operation. operations and errors have to be defined by value. ProcessUnstructuredSS-Data. SS-Incompatibility. SS-Protocol { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Access (2) modules (3) ss-Protocol (3) version2 (2)} DEFINITIONS ::= BEGIN IMPORTS -. ExplicitCT. CallBarred. USSD-Busy.imports operation types from MAP-SupplementaryServiceOperations RegisterSS. UnknownAlphabet FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version2 (2)} . SS-SubscriptionViolation. SystemFailure. For the involved operations and errors the same local values as in MAP are allocated. NumberOfPW-AttemptsViolation.2 and operation and error types from MAP. SS-NotAvailable. BuildMPTY. InterrogateSS. UnstructuredSS-Request.1 module described in subclause 4.imports operation types from SS-Operations NotifySS. DeactivateSS.imports operation types -. FacilityNotSupported.0.0: August 1996 4. GetPassword. DataMissing. It defines operations by allocating operations and errors a local value. RegisterPassword. IllegalSubscriber. ForwardChargeAdvice. RetrieveMPTY.imports error types -. BearerServiceNotProvisioned.80 version 5.imports error types from MAP-Errors UnknownSubscriber. SS-ErrorStatus. The following ASN. ProcessUnstructuredSS-Request. EraseSS. AbsentSubscriber.1 module. SplitMPTY. ForwardCUG-Info FROM SS-Operations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Access (2) modules (3) ss-Operations (0) version2 (2)} -. IllegalEquipment. UnexpectedDataValue. PW-RegistrationFailure.imports operation type from MAP-MobileServiceOperations ForwardCheckSS-Indication FROM MAP-MobileServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MobileServiceOperations (5) version2 (2)} -.Page 38 GSM 04.5 Operations and errors implementation For the actual implementation of supplementary services.

0. -.allocation of local values to errors unknownSubscriber UnknownSubscriber ::= localValue 1 illegalSubscriber IllegalSubscriber ::= localValue 9 bearerServiceNotProvisioned BearerServiceNotProvisioned ::= localValue 10 teleserviceNotProvisioned TeleserviceNotProvisioned ::= localValue 11 illegalEquipment IllegalEquipment ::= localValue 12 callBarred CallBarred ::= localValue 13 illegalSS-Operation IllegalSS-Operation ::= localValue 16 ss-ErrorStatus SS-ErrorStatus ::= localValue 17 ss-NotAvailable SS-NotAvailable ::= localValue 18 ss-SubscriptionViolation SS-SubscriptionViolation ::= localValue 19 ss-Incompatibility SS-Incompatibility ::= localValue 20 facilityNotSupported FacilityNotSupported ::= localValue 21 absentSubscriber AbsentSubscriber ::= localValue 27 systemFailure SystemFailure ::= localValue 34 dataMissing DataMissing ::= localValue 35 unexpectedDataValue UnexpectedDataValue ::= localValue 36 pw-RegistrationFailure PW-RegistrationFailure ::= localValue 37 negativePW-Check NegativePW-Check ::= localValue 38 numberOfPW-AttemptsViolation NumberOfPW-AttemptsViolation ::= localValue 43 unknownAlphabet UnknownAlphabet ::= localValue 71 ussd-Busy USSD-Busy ::= localValue 72 maxNumberOfMPTY-ParticipantsExceeded MaxNumberOfMPTY-ParticipantsExceeded ::= localValue 126 resourcesNotAvailable ResourcesNotAvailable ::= localValue 127 END .imports error types from SS-Errors ResourcesNotAvailable.allocation of local values to operations registerSS eraseSS activateSS deactivateSS interrogateSS notifySS registerPassword getPassword processUnstructuredSS-Data forwardCheckSS-Indication processUnstructuredSS-Request unstructuredSS-Request unstructuredSS-Notify forwardCUG-Info splitMPTY retrieveMPTY holdMPTY buildMPTY forwardChargeAdvice explicitCT RegisterSS ::= localValue 10 EraseSS ::= localValue 11 ActivateSS ::= localValue 12 DeactivateSS ::= localValue 13 InterrogateSS ::= localValue 14 NotifySS ::= localValue 16 RegisterPassword ::= localValue 17 GetPassword ::= localValue 18 ProcessUnstructuredSS-Data ::= localValue 19 ForwardCheckSS-Indication ::= localValue 38 ProcessUnstructuredSS-Request ::= localValue 59 UnstructuredSS-Request ::= localValue 60 UnstructuredSS-Notify ::= localValue 61 ForwardCUG-Info ::= localValue 120 SplitMPTY ::= localValue 121 RetrieveMPTY ::= localValue 122 HoldMPTY ::= localValue 123 BuildMPTY ::= localValue 124 ForwardChargeAdvice ::= localValue 125 ExplicitCT ::= localValue 126 -. MaxNumberOfMPTY-ParticipantsExceeded FROM SS-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Access (2) modules (3) ss-Errors (1) version2 (2)} .0: August 1996 -.80 version 5.Page 39 GSM 04.

noReplyConditionTime [5] IMPLICIT INTEGER (5 . basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). 20 ) ) OPTIONAL.. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). cug-Info [2] IMPLICIT SEQUENCE { cug-SubscriptionList SEQUENCE SIZE (1 . cugOG-CallBarred (2 )}. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).80 version 5. }. 20 ) ) OPTIONAL. 21 ) ) OPTIONAL. 21 ) ) OPTIONAL..... 30 ) OPTIONAL.. forwardedToSubaddress [8] IMPLICIT OCTET STRING (SIZE (1 .. 30 ) OPTIONAL.1 Module "SS-Protocol" -Expanded ASN... . } RESULT ss-Info CHOICE { forwardingInfo [0] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. }. forwardedToNumber [4] IMPLICIT OCTET STRING (SIZE (1 .. cugIC-CallBarred (1 ). noReplyConditionTime [7] IMPLICIT INTEGER (5 .1 Compiler P3. }.1 Module "SS-Protocol" --SIEMENS ASN. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.. forwardedToSubaddress [6] IMPLICIT OCTET STRING (SIZE (1 .0: August 1996 Annex A (informative): Expanded ASN. 10 ) OF SEQUENCE { cug-Index INTEGER (0 . .. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. basicServiceGroupList SEQUENCE SIZE (1 ...50 (96-05-31 07:42:56) -Date: 96-08-05 Time: 19:25:18 SS-Protocol { 0 identified-organization (4) etsi (0) mobileDomain (0) gsm-Access (2) modules (3) ss-Protocol (3) version2 (2) } DEFINITIONS ::= BEGIN registerSS OPERATION ARGUMENT registerSS-Arg SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ). forwardingFeatureList SEQUENCE SIZE (1 .. forwardingOptions [6] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. cug-Interlock OCTET STRING (SIZE (4 ) ). callBarringFeatureList SEQUENCE SIZE (1 .. . teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. ..Page 40 GSM 04. }. 32767 ).. intraCUG-Options ENUMERATED { noCUG-Restrictions (0 ).. . callBarringInfo [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL. forwardedToNumber [5] IMPLICIT OCTET STRING (SIZE (1 . 13 ) OF CHOICE { ...0.

21 ) ) OPTIONAL. forwardingFeatureList SEQUENCE SIZE (1 .systemFailure -.localValue : 17.. }.localValue : 10.. ss-SubscriptionOption CHOICE { cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent (0 ). -. -. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) )..teleserviceNotProvisioned -. basicServiceGroupList SEQUENCE SIZE (1 .localValue : 20} ::= localValue : 10 eraseSS OPERATION ARGUMENT ss-ForBS SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ).unexpectedDataValue -. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL..bearerServiceNotProvisioned -. cug-FeatureList SEQUENCE SIZE (1 . teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. 13 ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).. forwardingOptions [6] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL.. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) )... -. ..dataMissing -. . forwardedToSubaddress [8] IMPLICIT OCTET STRING (SIZE (1 .unknownSubscriber -. 32767 ) OPTIONAL.illegalSS-Operation -...ss-SubscriptionViolation -. 20 ) ) OPTIONAL. -. .. -.. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. -. }} ERRORS { -.ss-Incompatibility -.0. basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).localValue : 34.. -. temporaryDefaultRestricted (1 ). } OPTIONAL.0: August 1996 bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).. overrideDisabled (1 )}} OPTIONAL. ss-Data [3] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL.localValue : 35..localValue : 19. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.localValue : 16. -. temporaryDefaultAllowed (2 )}.Page 41 GSM 04. }. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL.localValue : 1. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. } RESULT ss-Info CHOICE { forwardingInfo [0] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL. .callBarred -. . teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. .localValue : 11. interCUG-Restrictions OCTET STRING (SIZE (1 ) ).ss-ErrorStatus -. -. -.80 version 5. forwardedToNumber [5] IMPLICIT OCTET STRING (SIZE (1 . preferentialCUG-Indicator INTEGER (0 .localValue : 36. overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled (0 ).localValue : 13.

32767 ) OPTIONAL.. cugIC-CallBarred (1 ). -.. -.Page 42 GSM 04..localValue : 16. }..ss-SubscriptionViolation -. ss-SubscriptionOption CHOICE { cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent (0 ). callBarringInfo [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL. -. } OPTIONAL. -. interCUG-Restrictions OCTET STRING (SIZE (1 ) ). 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).. }.unknownSubscriber -.localValue : 1. }. -. .dataMissing -.localValue : 17. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.. . -. }. 13 ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). callBarringFeatureList SEQUENCE SIZE (1 . 32767 ).. -.illegalSS-Operation -. preferentialCUG-Indicator INTEGER (0 ..0. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.systemFailure -. 30 ) OPTIONAL. cugOG-CallBarred (2 )}. ss-Data [3] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL.80 version 5..localValue : 36. . }. }.teleserviceNotProvisioned -. ..localValue : 34.unexpectedDataValue -. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. intraCUG-Options ENUMERATED { noCUG-Restrictions (0 ).. cug-FeatureList SEQUENCE SIZE (1 . temporaryDefaultRestricted (1 ). basicServiceGroupList SEQUENCE SIZE (1 .. overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled (0 ).. 10 ) OF SEQUENCE { cug-Index INTEGER (0 .. . teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. . ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. }} ERRORS { -. -.localValue : 13. .localValue : 35.. overrideDisabled (1 )}} OPTIONAL. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) )......localValue : 19} . ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL..bearerServiceNotProvisioned -.. basicServiceGroupList SEQUENCE SIZE (1 .ss-ErrorStatus -.. -. cug-Info [2] IMPLICIT SEQUENCE { cug-SubscriptionList SEQUENCE SIZE (1 . .0: August 1996 noReplyConditionTime [7] IMPLICIT INTEGER (5 .. temporaryDefaultAllowed (2 )}.localValue : 11. cug-Interlock OCTET STRING (SIZE (4 ) ).localValue : 10. 13 ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).callBarred -.

32767 ). }.. . noReplyConditionTime [7] IMPLICIT INTEGER (5 . ss-SubscriptionOption CHOICE { . 13 ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. . teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.... teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. 30 ) OPTIONAL. cugOG-CallBarred (2 )}.. cug-Interlock OCTET STRING (SIZE (4 ) )... ss-Data [3] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL. } OPTIONAL. intraCUG-Options ENUMERATED { noCUG-Restrictions (0 ). }......... . }. 32767 ) OPTIONAL. 21 ) ) OPTIONAL. cug-FeatureList SEQUENCE SIZE (1 . teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.. }. .. forwardedToSubaddress [8] IMPLICIT OCTET STRING (SIZE (1 . preferentialCUG-Indicator INTEGER (0 .. cug-Info [2] IMPLICIT SEQUENCE { cug-SubscriptionList SEQUENCE SIZE (1 . forwardedToNumber [5] IMPLICIT OCTET STRING (SIZE (1 .0. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). }. 20 ) ) OPTIONAL. cugIC-CallBarred (1 ). .. callBarringInfo [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL. interCUG-Restrictions OCTET STRING (SIZE (1 ) ). . ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). basicServiceGroupList SEQUENCE SIZE (1 .80 version 5.. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. forwardingOptions [6] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. }.... forwardingFeatureList SEQUENCE SIZE (1 . 10 ) OF SEQUENCE { cug-Index INTEGER (0 . } RESULT ss-Info CHOICE { forwardingInfo [0] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.Page 43 GSM 04...0: August 1996 ::= localValue : 11 activateSS OPERATION ARGUMENT ss-ForBS SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ). callBarringFeatureList SEQUENCE SIZE (1 . 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).. . .

cug-Info [2] IMPLICIT SEQUENCE { . overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled (0 ). . basicServiceGroupList SEQUENCE SIZE (1 .localValue : 43} ::= localValue : 12 deactivateSS OPERATION ARGUMENT ss-ForBS SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ).dataMissing -.. }} ERRORS { -. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. }. -...ss-ErrorStatus -. -.localValue : 16.systemFailure -. . basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). -. callBarringFeatureList SEQUENCE SIZE (1 . teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.illegalSS-Operation -. -.ss-SubscriptionViolation -.. .unknownSubscriber -.80 version 5. noReplyConditionTime [7] IMPLICIT INTEGER (5 . callBarringInfo [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL. .localValue : 19.localValue : 38.localValue : 36. -.....localValue : 1. } RESULT ss-Info CHOICE { forwardingInfo [0] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL.teleserviceNotProvisioned -. -. -. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. -.localValue : 17. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).. overrideDisabled (1 )}} OPTIONAL. forwardingOptions [6] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL.numberOfPW-AttemptsViolation -. .Page 44 GSM 04.localValue : 20. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). forwardedToNumber [5] IMPLICIT OCTET STRING (SIZE (1 .0: August 1996 cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent (0 ).. }. temporaryDefaultAllowed (2 )}.localValue : 10.callBarred -.localValue : 13.localValue : 11. 13 ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).. 30 ) OPTIONAL..bearerServiceNotProvisioned -.. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. forwardedToSubaddress [8] IMPLICIT OCTET STRING (SIZE (1 .localValue : 35. 21 ) ) OPTIONAL.negativePW-Check -. . forwardingFeatureList SEQUENCE SIZE (1 .0.unexpectedDataValue -.localValue : 34. 20 ) ) OPTIONAL.. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. -.... -. }. temporaryDefaultRestricted (1 ).. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. }.ss-Incompatibility -. -. -.

unexpectedDataValue -. -.Page 45 GSM 04. cugIC-CallBarred (1 ).numberOfPW-AttemptsViolation -.teleserviceNotProvisioned -. cug-FeatureList SEQUENCE SIZE (1 . cug-Interlock OCTET STRING (SIZE (4 ) ). . -. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. }.0: August 1996 cug-SubscriptionList SEQUENCE SIZE (1 .localValue : 13.. .. 13 ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).localValue : 38. 32767 )....ss-SubscriptionViolation -. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. -.illegalSS-Operation -.. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.0. ss-Data [3] IMPLICIT SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ) OPTIONAL. temporaryDefaultRestricted (1 ).. ss-SubscriptionOption CHOICE { cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent (0 ).. preferentialCUG-Indicator INTEGER (0 .bearerServiceNotProvisioned -. . overrideDisabled (1 )}} OPTIONAL.negativePW-Check -. -. }.localValue : 35. -.callBarred -. -. cugOG-CallBarred (2 )}.. .localValue : 43} ::= localValue : 13 interrogateSS OPERATION ARGUMENT ss-ForBS SEQUENCE { ss-Code OCTET STRING (SIZE (1 ) ).localValue : 16. -. } OPTIONAL. 13 ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).ss-ErrorStatus -..localValue : 19. overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled (0 ).localValue : 36. basicServiceGroupList SEQUENCE SIZE (1 ...localValue : 1. -. -. basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). basicServiceGroupList SEQUENCE SIZE (1 .systemFailure -. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).localValue : 34. . 32767 ) OPTIONAL.unknownSubscriber -.. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL..localValue : 11. intraCUG-Options ENUMERATED { noCUG-Restrictions (0 ). interCUG-Restrictions OCTET STRING (SIZE (1 ) ).. temporaryDefaultAllowed (2 )}. }} ERRORS { -. -.localValue : 10.dataMissing -. } RESULT interrogateSS-Res CHOICE { .80 version 5.localValue : 17.. -. 10 ) OF SEQUENCE { cug-Index INTEGER (0 .

dataMissing -.. presentationRestricted [1] IMPLICIT NULL. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.Page 46 GSM 04.systemFailure -. forwardedToSubaddress [8] IMPLICIT OCTET STRING (SIZE (1 .localValue : 13. ..localValue : 1. 30 ) OPTIONAL. . mpty-Indicator [16] IMPLICIT NULL OPTIONAL. callOnHold-Indicator [15] IMPLICIT ENUMERATED { callRetrieved (0 ).. }} ERRORS { -.. -.unknownSubscriber -. 20 ) ). temporaryDefaultRestricted (1 ). forwardingOptions [6] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. cli-RestrictionInfo [4] IMPLICIT SEQUENCE { ss-Status OCTET STRING (SIZE (1 ) ).. .localValue : 36. -.0: August 1996 ss-Status [0] IMPLICIT OCTET STRING (SIZE (1 ) ). }. 20 ) ).localValue : 18} ::= localValue : 14 notifySS OPERATION ARGUMENT notifySS-Arg SEQUENCE { ss-Code [1] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. }. callsWaiting-Indicator [14] IMPLICIT NULL OPTIONAL. ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. 32767 ) OPTIONAL.0. . ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL. partyNumberSubaddress [1] IMPLICIT OCTET STRING (SIZE (1 ..localValue : 16. rdn [1] CHOICE { presentationAllowedAddress [0] IMPLICIT SEQUENCE { partyNumber [0] IMPLICIT OCTET STRING (SIZE (1 . teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )}. forwardedToNumber [1] IMPLICIT OCTET STRING (SIZE (1 . cliRestrictionOption ENUMERATED { permanent (0 )..unexpectedDataValue -. numberNotAvailableDueToInterworking [2] IMPLICIT NULL. -.80 version 5. ss-Notification [5] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL... 21 ) ) OPTIONAL. -.localValue : 11. 21 ) ) OPTIONAL..localValue : 10. 13 ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ).... noReplyConditionTime [7] IMPLICIT INTEGER (5 .. clirSuppressionRejected [18] IMPLICIT NULL OPTIONAL. -. presentationRestrictedAddress [3] IMPLICIT SEQUENCE { partyNumber [0] IMPLICIT OCTET STRING (SIZE (1 . forwardedToNumber [5] IMPLICIT OCTET STRING (SIZE (1 . active (1 )}. -. -.teleserviceNotProvisioned -.callBarred -.bearerServiceNotProvisioned -.ss-NotAvailable -. forwardingFeatureList [3] IMPLICIT SEQUENCE SIZE (1 . 20 ) ). basicServiceGroupList [2] IMPLICIT SEQUENCE SIZE (1 . .. callOnHold (1 )} OPTIONAL.illegalSS-Operation -. -. temporaryDefaultAllowed (2 )} OPTIONAL. ect-Indicator [19] IMPLICIT SEQUENCE { ect-CallState [0] IMPLICIT ENUMERATED { alerting (0 ). cug-Index [17] IMPLICIT INTEGER (0 ..localValue : 34. 13 ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) )..localValue : 35. . 20 ) ) OPTIONAL..

localValue : 36.numberOfPW-AttemptsViolation -. . ussd-String OCTET STRING (SIZE (1 . -.localValue : 34. -.ss-SubscriptionViolation -.unexpectedDataValue -.. enterNewPW-Again (2 )... . } OPTIONAL} ::= localValue : 16 registerPassword OPERATION ARGUMENT ss-Code OCTET STRING (SIZE (1 ) ) RESULT newPassword NumericString (FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9" )|SIZE (4 ) ) ERRORS { -. .localValue : 34.localValue : 36. .0.unexpectedDataValue -.localValue : 35. -.unexpectedDataValue -.negativePW-Check -....Page 47 GSM 04. -.systemFailure -..localValue : 34..localValue : 37. }} OPTIONAL.localValue : 43} LINKED { -. } ERRORS { -.80 version 5.localValue : 13. 200 ) ) ERRORS { -. 21 ) ) OPTIONAL.localValue : 38. enterNewPW (1 ). ussd-String OCTET STRING (SIZE (1 .0: August 1996 partyNumberSubaddress [1] IMPLICIT OCTET STRING (SIZE (1 . -..dataMissing -. -. -.. 160 ) ).pw-RegistrationFailure -.. -. . 160 ) ).dataMissing -.. -.. 200 ) ) RESULT ss-UserData IA5String (SIZE (1 .localValue : 35. } RESULT ussd-Res SEQUENCE { ussd-DataCodingScheme OCTET STRING (SIZE (1 ) ).callBarred -.localValue : 18} ::= localValue : 17 getPassword OPERATION ARGUMENT guidanceInfo ENUMERATED { enterPW (0 ).systemFailure -. badPW-TryAgain (3 ).getPassword -.localValue : 19.localValue : 36} ::= localValue : 19 forwardCheckSS-Indication OPERATION ::= localValue : 38 processUnstructuredSS-Request OPERATION ARGUMENT ussd-Arg SEQUENCE { ussd-DataCodingScheme OCTET STRING (SIZE (1 ) ).systemFailure -. badPW-FormatTryAgain (4 )} RESULT currentPassword NumericString (FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9" )|SIZE (4 ) ) ::= localValue : 18 processUnstructuredSS-Data OPERATION ARGUMENT ss-UserData IA5String (SIZE (1 . -.

0: August 1996 -. ussd-String OCTET STRING (SIZE (1 . } RESULT ussd-Res SEQUENCE { ussd-DataCodingScheme OCTET STRING (SIZE (1 ) ). .localValue : 35.localValue : 34} ::= localValue : 121 . suppressOA [2] IMPLICIT NULL OPTIONAL.unknownAlphabet -.localValue : 9. -.illegalSubscriber -. } ::= localValue : 120 splitMPTY OPERATION RESULT zzzz-empty NULL ERRORS { -. -...absentSubscriber -. 32767 ) OPTIONAL.localValue : 34.. -.illegalEquipment -.localValue : 71. -.localValue : 9.localValue : 35. -.unknownAlphabet -..callBarred -.localValue : 36.unknownAlphabet -.Page 48 GSM 04. 160 ) ). -. -. ..ss-Incompatibility -.dataMissing -. -.localValue : 16. -. -.localValue : 21.systemFailure -.localValue : 71.localValue : 34.systemFailure -.localValue : 13} ::= localValue : 59 unstructuredSS-Request OPERATION ARGUMENT ussd-Arg SEQUENCE { ussd-DataCodingScheme OCTET STRING (SIZE (1 ) ).80 version 5.. .localValue : 72} ::= localValue : 61 forwardCUG-Info OPERATION ARGUMENT forwardCUG-InfoArg SEQUENCE { cug-Index [0] IMPLICIT INTEGER (0 .0. -. ussd-String OCTET STRING (SIZE (1 .absentSubscriber -. suppressPrefCUG [1] IMPLICIT NULL OPTIONAL.localValue : 12. -..ussd-Busy -. -.localValue : 12..illegalEquipment -.facilityNotSupported -.unexpectedDataValue -.dataMissing -.illegalSS-Operation -. -.. } ERRORS { -.... 160 ) ).ussd-Busy -.localValue : 17.ss-ErrorStatus -. -.localValue : 20.localValue : 71.localValue : 27. -. } ERRORS { -.illegalSubscriber -.localValue : 36. 160 ) ). -. -. ussd-String OCTET STRING (SIZE (1 .localValue : 72} ::= localValue : 60 unstructuredSS-Notify OPERATION ARGUMENT ussd-Arg SEQUENCE { ussd-DataCodingScheme OCTET STRING (SIZE (1 ) ). .localValue : 27.systemFailure -. -.unexpectedDataValue -.

ss-ErrorStatus -. ..facilityNotSupported -..localValue : 20.localValue : 13} . -.resourcesNotAvailable -.localValue : 21..localValue : 17. -. 8191 ) OPTIONAL.ss-NotAvailable -. -. -.ss-ErrorStatus -.localValue : 18.localValue : 18. } RESULT zzzz-empty NULL ::= localValue : 125 explicitCT OPERATION ERRORS { -. -.illegalSS-Operation -.. -. e2 [2] IMPLICIT INTEGER (0 .localValue : 20. -. -.systemFailure -. 8191 ) OPTIONAL.ss-Incompatibility -.Page 49 GSM 04. -..localValue : 34} ::= localValue : 122 holdMPTY OPERATION RESULT zzzz-empty NULL ERRORS { -. e7 [7] IMPLICIT INTEGER (0 .localValue : 17.localValue : 21. -..localValue : 16.systemFailure -.maxNumberOfMPTY-ParticipantsExceeded -.localValue : 16. -. -.. .ss-Incompatibility -. -.illegalSS-Operation -.ss-Incompatibility -. 8191 ) OPTIONAL.80 version 5..localValue : 34} ::= localValue : 123 buildMPTY OPERATION RESULT zzzz-empty NULL ERRORS { -. e5 [5] IMPLICIT INTEGER (0 .callBarred -. -..localValue : 20.localValue : 16. 8191 ) OPTIONAL.localValue : 16.localValue : 17.illegalSS-Operation -.systemFailure -. -.illegalSS-Operation -.localValue : 21. e3 [3] IMPLICIT INTEGER (0 . 8191 ) OPTIONAL. e6 [6] IMPLICIT INTEGER (0 .facilityNotSupported -.localValue : 34. -.localValue : 127. 8191 ) OPTIONAL.. -.ss-ErrorStatus -. -.localValue : 127.localValue : 17.. e4 [4] IMPLICIT INTEGER (0 . }. chargingInformation [1] IMPLICIT SEQUENCE { e1 [1] IMPLICIT INTEGER (0 .0: August 1996 retrieveMPTY OPERATION RESULT zzzz-empty NULL ERRORS { -.0.ss-Incompatibility -.ss-NotAvailable -.systemFailure -. 8191 ) OPTIONAL.localValue : 20. -. -. -.facilityNotSupported -.ss-ErrorStatus -.localValue : 126} ::= localValue : 124 forwardChargeAdvice OPERATION ARGUMENT forwardChargeAdviceArg SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING (SIZE (1 ) ).resourcesNotAvailable -.localValue : 34.

temporaryDefaultAllowed (2 )}.. overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled (0 ).0: August 1996 ::= localValue : 126 unknownSubscriber ERROR ::= localValue : 1 illegalSubscriber ERROR ::= localValue : 9 bearerServiceNotProvisioned ERROR ::= localValue : 10 teleserviceNotProvisioned ERROR ::= localValue : 11 illegalEquipment ERROR ::= localValue : 12 callBarred ERROR PARAMETER callBarringCause ENUMERATED { barringServiceActive (0 ).. . ss-Status [4] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL.Page 50 GSM 04. operatorBarring (1 )} ::= localValue : 13 illegalSS-Operation ERROR ::= localValue : 16 ss-ErrorStatus ERROR PARAMETER ss-Status OCTET STRING (SIZE (1 ) ) ::= localValue : 17 ss-NotAvailable ERROR ::= localValue : 18 ss-SubscriptionViolation ERROR PARAMETER ss-SubscriptionOption CHOICE { cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent (0 ). overrideDisabled (1 )}} ::= localValue : 19 ss-Incompatibility ERROR PARAMETER ss-IncompatibilityCause SEQUENCE { ss-Code [1] IMPLICIT OCTET STRING (SIZE (1 ) ) OPTIONAL.0. basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING (SIZE (1 ) ). } ::= localValue : 20 facilityNotSupported ERROR ::= localValue : 21 absentSubscriber ERROR PARAMETER . temporaryDefaultRestricted (1 ).80 version 5. teleservice [3] IMPLICIT OCTET STRING (SIZE (1 ) )} OPTIONAL.

pvlr (3 ). newPasswordsMismatch (2 )} ::= localValue : 37 negativePW-Check ERROR ::= localValue : 38 numberOfPW-AttemptsViolation ERROR ::= localValue : 43 unknownAlphabet ERROR ::= localValue : 71 ussd-Busy ERROR ::= localValue : 72 maxNumberOfMPTY-ParticipantsExceeded ERROR ::= localValue : 126 resourcesNotAvailable ERROR ::= localValue : 127 END . vmsc (5 ). eir (6 ). invalidFormat (1 ). hlr (1 ).80 version 5. vlr (2 ). controllingMSC (4 ).0. rss (7 )} ::= localValue : 34 dataMissing ERROR ::= localValue : 35 unexpectedDataValue ERROR ::= localValue : 36 pw-RegistrationFailure ERROR PARAMETER pw-RegistrationFailureCause ENUMERATED { undetermined (0 ).Page 51 GSM 04.0: August 1996 mwd-Set BOOLEAN ::= localValue : 27 systemFailure ERROR PARAMETER networkResource ENUMERATED { plmn (0 ).

80-39 rev 1 (category D) CR 04.80-50 (category D) approved by SMG#08 TS changed to draft prETS 300 564 CR 04.80-26 rev 2 (category D) CR 04.80-25 rev 2 (category D) CR 04.1.80-43 rev 1 (category D) CR 04.80-42 rev 1 (category D) CR 04.0 Release 92 Oct 90 Jan 91 March 91 June 91 version 3.7.80-05 rev 3 (category B) approved by GSM#30 CR 04.1) CR 04.0 Remarks Last common phase 1/phase 2 version (I-ETS 300 027 = version 3.80-10 rev 3 (category D) approved by GSM#30 CR 04.80-28 rev 1 (category D) CR 04.1.0.80-18 rev 1 (category B) CR 04.80-16 (category D) CR 04.80-35 (category C) approved by SMG#04 CR 04.80-46 rev 6 (category F) approved by SMG#09 CR 04.80-29 (category D) CR 04.0 version 4.80-30 rev 1 (category C) CR 04.7.80-10 rev 3 (category A) approved by GSM#29 CR 04.80-56 (category F) TS frozen by SMG#09 April 92 version 4.Page 52 GSM 04.0.80-44 (category D) CR 04.0 version 4.80-53 (category F) CR 04.0 Oct 93 Jan 94 version 4.4.80-33 (category D) approved by SMG#04 CR 04.0.80-49 (category C) TS conditionally frozen by SMG#07 (except USSD) CR 04.0 June 93 version 4.80-54 (category F) CR 04.80 Date Version version 3.80-04 rev 1 (category B) approved by GSM#28 CR 04.80-36 rev 2 (category D) approved by SMG#06 CR 04.2.80-19 rev 2 (category B) CR 04.0: August 1996 History Status of Technical Specification GSM 04.0 version 4.80-40 rev 1 (category C) CR 04.0 version 4.80-52 (category F) CR 04.0 .0 version 4.5.80-27 (category D) CR 04.80-22 rev 2 (category C) CR 04.80-12 rev 3 (category D) CR 04.80-20 (category B) CR 04.6.80-55 rev 1 (category F) CR 04.1 version 4.80-23 rev 2 (category C) CR 04.3.0 Sept 92 Jan 93 April 93 version 4.2.80-47 rev 1 (category C) CR 04.8.80-45 rev 2 (category D) CR 04.80-21 rev 3 (category D) approved by SMG#02 CR 04.80 version 5.1 version 4.80-37 rev 1 (category D) CR 04.80-38 (category C) approved by SMG#07 CR 04.4.

Page 53 GSM 04.0 ISBN 2-7437-0836-0 Dépôt légal : Août 1996 .1 Remarks CR 04.80-A004 (category F) approved by SMG#17 CR 04.80 version 5.11.9.dot Document history August 1996 Publication of version 5.9.80 (continuation) Date April 94 Oct 94 Version version 4.80-A003 (category D) approved by SMG#16 AR 04.80-55 rev 2 (category F) approved by SMG#10 CR 04.0.9.2 version 4.80-58 (category D) approved by SMG#12 CR 04.0 Text and figures: WORD 6.0 ASN.0 version 4.0 version 5.80-A005 (category B) (ECT) approved by SMG#18 Jan 95 Oct 95 Febr 96 April 1996 version 4.80-59 rev 1 (category D) TS changed to final draft prETS 300 564 TS changed to ETS 300 564 First edition AR 04.0.10.0: August 1996 Status of Technical Specification GSM 04.0 version 4.1: Siemens ASN.0.1 compiler Stylesheet: C:\msoffice\winword\template\etsiw_60.

Sign up to vote on this title
UsefulNot useful