ETSI GSM 04 80-1993 See PRI-ETS 300 027《参见PRI-ETS 300 027》.pdf

1、 3404583 0079973 469 9 Released: I July 1993 GSM 04.80 Version: 4.7.0 Date: 25 June 1993 Work Item No: Key words: European digital cellular telecommunication system (phase 2); Mobile radio interface layer 3 Supplementary services specification Formats and Coding ETSI European Telecommunications Stan

2、dards Institute ETSI Secretariat: Route des Lucioles, F-O6921 Sophia Antipolis Cedex . France TP. + 33 92 94 42 O0 TF. + 33 93 65 47 16 Tx. 47 O0 40 F _ *his is an unpublished work the copyright in which vests in the European Telecommunications Standards Institute. All rights reserved. The informati

3、on contained herein is the property of ETSI and no part may be reproduced or used except as authorised by contract or other written permission. The copyright and the foregoing restriction on reproduction and use extend to all media in which the information may be embodied. 3404583 0077774 3T5 Page 3

4、 GSM 04.80 . version 4.7.0 : June 1993 CONTENTS 1 . SCOPE 5 2 . 3 . MESSAGE FUNCTIONAL DEFINITIONS AND CONTENTS . 6 2.1 General . 6 2.2 Messages for supplementary services control . 7 2.3 Facility 7 2.4 Register 8 2.4.1 Register (network to mobile station direction) . 8 2.4.2 Register (mobile statio

5、n to network direction) . 8 2.4.2.1 SS version . 9 2.5 Release complete . 9 2.5.1 Cause . 9 2.5.2 Facility 9 GENERAL MESSAGE FORMAT AND INFORMATION ELEMENTS CODING . 10 3.1 Overview 10 3.2 Protocol discriminator . 10 3.3 Transaction identifier 10 3.4 Message type 11 3.5 Other information elements 12

6、 3.6 Facility information element . 12 3.6.1 Component (octet 3 etc) 13 3.6.2 Component type tag 16 3.6.3 Component ID tag . 16 3.6.4 Operation Code 17 3.6.5 Sequence and Set tags 17 3.6.6 Error Code . 18 3.6.7 Problem Code . 18 3.7 Version handling for supplementary services 20 3.7.1 Supplementary

7、service screening indicator 20 3.7.2 Supplementary service version indicator . 21 4 . SUPPLEMENTARY SERVICES OPERATION SPECIFICATIONS 22 4.1 General . 22 4.2 Operation types . 23 4.2.2 Operation types description 25 4.2.2.1 RegisterSS (MS -. Network) . 25 4.2.2.2 EraseSS (MS -. Network) . 25 4.2.2.3

8、 ActivateSS (MS Network) . 26 4.2.2.4 DeactivateSS (MS Network) . 26 4.2.2.5 InterrogateSS (MS Network) . 26 4.2.2.6 NotifySS (Network MS) 26 4.2.2.7 Registerpassword (MS Network) . 26 4.2.2.8 Getpassword (Network MS) 26 4.2.2.9 ProcessUnstructuredSsData (MS Network) . 26 4.2.2.1 O ForwardCheckSslnd

9、ication (Network MS) . 26 4.2.2.1 1 ForwardChargeAdvice (Network MS) . 27 4.2.2.12 BuildMPTY (MS Network) . 27 4.2.2.13 HoldMPTY (MS Network) . 27 4.2.2.14 RetrieveMPTY (MS Network) 27 4.2.2.15 SplitMPTY (MS Network) . 27 Previous page is blank m 3404583 0079975 23L m Page 4 GSM 04.80 . version 4.7.

10、0 : June 1993 4.2.2.1 6 ForwardCUG-info (MS Network) 27 4.3 Error types 28 4.3.1 Error types ASN . 1 specification 28 4.3.2 Error types description . 28 4.3.2.1 UnknownSubscriber 28 4.3.2.2 BearerServiceNotProvisioned . 28 4.3.2.3 TeleServiceNotProvisioned 29 4.3.2.5 SS-ErrorStatus 29 4.3.2.6 SS-Not

11、Available 29 4.3.2.8 SS-Incompatibility . 29 4.3.2.9 SystemFailure 29 4.3.2.7 SS-SubscriptionViolation 29 DataMissing . 30 UnexpectedDataValue 30 PasswordRegistrationFailure . 30 NegativePasswordCheck 30 FacilityNotSupported . 30 ResourcesNotAvailable . 30 MaxNumberOfMPTY-ParticipantsExceeded 30 Cal

12、lBarred 30 Number0fPW.AttemptsVioiation 30 CI . 4.3.2.1 O 4.3.2.1 1 4.3.2.12 4.3.2.13 4.3.2.14 4.3.2.1 5 4.3.2.16 4.3.2.17 4.3.2.18 4.4 Data types and identifiers J 1 4.4.1 General . 31 4.4.2 ASN.l data types . 31 4.4.3 Identifiers definition . 33 4.4.3.1 charginglnformation . 33 4.4.3.2 el . 33 4.4

13、.3.3 e2 . 34 4.4.3.4 e3 . 34 4.4.3.5 e4 . 34 4.4.3.6 e5 . 34 4.4.3.7 e6 . 34 4.4.3.8 e7 . 34 4.4.3.9 ss-Code . 34 4.4.3.10 ss-Notification 34 4.4.3.1 1 ss-Status . 35 4.4.3.1 2 calIIsWaiting-Indicator 35 4.4.3.1 3 call0nhold-indicator . 35 4.4.3.14 mpty-Indicator 35 4.4.3.1 5 forwardCUG-InfoArg 35 4

14、.4.3.16 cug-Index . 35 4.4.3.1 7 suppressPrefCUG 35 4.4.3.18 suppress0A . 35 4.5 Operations and errors implementation . 36 Annex A Expanded ASN . 1 Module SS.Protocol. 38 3404583 007997b 178 Page 5 GSM 04.80 - version 4.7.0 : June 1993 SECTION 1 1. SCOPE This technical specification contains the cod

15、ing of information necessary for support of Supplementary service operation on the mobile radio interface layer 3. Section 2 gives the functional definitions and contents of messages for call independent supplementary service operations. Messages necessary for support of call related supplementary s

16、ervice operations are defined in TS GSM 04.08. Section 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. Section 4 give

17、s the specification of the call related and call independent supplementary service operations. 3404583 0079977 004 Page 6 GSM 04.80 - version 4.7.0 : June 1993 SECTION 2 2. MESSAGE FUNCTIONAL DEFINITIONS AND CONTENTS 2.1 General This section defines the structure of the messages of the layer 3 proto

18、col defined in TS GSM 04.80. These messages are standard L3 messages as defined in TS GSM 04.07. Each definition includes: a) a brief description of the message. b) a table listing the information elements in the order of their appearance in the message. In a sequence of consecutive IEs with half oc

19、tet length, the first IE occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N + 1 etc. For each IE the table indicates: 1. the information element identifier, in hexadecimal notation, if the IE has format T, TV or TLV. If the IEl has half octet length,

20、 it is specified by a notation representing the IEl as a hexadecimal digit followed by a “-“ (example: E). 2. the name of the IE (which gives an idea of the semantics of the element), which is used in this and other specifications as a reference to the IE within the message. 3. the name of the type

21、of the IE (which indicates the coding of the value part of the IE, and a reference to a description of the value part of the IE. 4. The presence requirement indication (Ml C or O) for the IE, as defined in TS GSM 04.07. 5. the format of the IE (T, V, TV, LV, TLV) as defined in TS GSM 04.07. 6. the l

22、ength of the IE (or permissible range of lengths), in octets, in the message, where “7“ means that the maximum length of the IE is only constrained by the link layer protocol, and in the case of the feciliry IE by possible further considerations specified in TS GSM 04.1 O. This indication is non-nor

23、mative. cl subsections specifying conditions for IEs with presence requirement C or O in the relevant message. Together with other conditions specified in TS GSM 04.80, GSM 04.10 or GSM 04.8 and 04.9-series this defines when the IE shall be included or not, what non-presence of such IEs means, and (

24、for IEs with presence requirement C) the static conditions for presence and/or non-presence of the IEs (see TS GSM 04.07). 3404583 0079978 T40 Messages for supplementary service control Page 7 GSM 04.80 - version 4.7.0 : June 1993 Reference 2.2 Messages for supplementary services control Facility Ta

25、ble 2.1 /GSM 04.80 summarizes the messages for call independent supplementary services control. See TS GSM 04.10 for a detailed description of call independent supplementary service messages. Information element Supplementary service protocol discriminator Transaction identifier Type I Reference Pro

26、tocol discriminator 3.2 Transaction identifier 3.3 FACILITY REGISTER RELEASE COMPLETE 2.3 2.4 2.5 Table 2.1 IGSM 04.80 Messages for call independent supplementary service control 2.3 Facility This message is sent by the mobile station or the network to request or acknowledge a supplementary service.

27、 It is used when information is to be conveyed and the transaction already exists, but is not to be released. The supplementary service to be invoked, and its associated parameters, are specified in the Facility information element. See table 2.2/GCM 04.80. Facility message type Message type 3.4 Fac

28、ility 3.5 Presence Format -I- -+ Length 112 112 1 2-? Table 2.2/GSM 04.80 FACILITY message content 3YOY583 0079979 787 Information element Type / Reference Supplementary service Protocol discriminator protocol discriminator 3.2 Transaction identifier Transaction identifier 3.3 Register Message type

29、message type 3.4 Facility Facility 3.5 Page 8 GSM 04.80 - version 4.7.0 : June 1993 2.4 Register 2.4.1 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 an

30、d to request or acknowledge a Supplementary service. See table 2.3IGSM 04.80. Presence Format Length M V 112 M V 1 /2 M V 1 M TLV 2-? - IEl IEl Information element Type / Reference Supplementary service Protocol discriminator protocol discriminator 3.2 Table 2.3/GSM 04.80 REGISTER message content (n

31、etwork to mobile station direction) Transaction identifier Register message type 2.4.2 Register (mobile station to network direction) Transaction identifier 3.3 Message type 3.4 This message is sent by the mobile station to the network to assign a new transaction identifier for call independent supp

32、lementary service control and to request or acknowledge a supplementary service. See table 2.4/GSM 04.80. 12 Facility 7F SS version Facility 3.5 SS version indicator I 3.8.2 MIV MIV I TLV Length 112 1 12 1 2-? 3 Table 2.4/GSM 04.80 REGISTER message content (mobile station to network direction) = 340

33、4583 0077780 bT IEl Information element Page 9 GSM 04.80 - version 4.7.0 : June 1993 Type / Reference Presence 2.4.2.1 SS version Supplementary service protocol discriminator Transaction identifier Release Complete message type This information element shall be included if the supplementary service

34、operation being invoked is implemented according to the phase 2 GSM standards. Protocol discriminator M 3.2 Transaction identifier M 3.3 Message type M 3.4 2.5 Release complete 08 12 This message is sent by the mobile station or the network to release a transaction used for call independent suppleme

35、ntary service control. It may also request or acknowledge a supplementary service. See table 2.5/GSM 04.80. Cause Cause O TS GSM 04.08 Facility Facility O 3.5 I lf2 1 t2 I Table 2.5/GSM 04.80 RELEASE COMPLETE message content 2.5.1 Cause This information element shall be included when the functional

36、handling of the Cause I is specified in the service description or TS GSM 09.1 1, If the functional handling of the Cause IE is not specified, the receiving entity may ignore the IE. 2.5.2 Facility This information element shall be included as required by the service description and the procedures d

37、efined in TS GSM 04.10. Page 10 GSM 04.80 - version 4.7.0 : June 1993 SECTION 3 3. GENERAL MESSAGE FORMAT AND INFORMATION ELEMENTS CODING The figures and text in this section describe message contents. Within each octet, the bit designated “bit 1“ is transmitted first, followed by bits 2, 3, 4, etc.

38、 Similarly, the octet shown at the top of each figure is sent first. 3.1 Overview Within the layer 3 protocol defined in TS GSM 04.80, every message is a standard i3 message as defined in TS GSM 04.07. This means that the message consists of the following parts: a) protocol discriminator; b) transac

39、tion identifier; ci message type; d) other information elements, as required. Unless specified otherwise, a particular information element may be present only once in a given message. When a field extends over more than one octet, the order of bit values progressively decreases as the octet number i

40、ncreases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. 3.2 Protocol discriminator The Protocol Discriminator (PD) and its use are defined in TS GSM 04.07. TS GSM 04.80 defines the protocols relating to the PD values: 101

41、1 supplementary services (call independent). 3.3 Transaction identifier For general rules, format and coding of transact#; , identifier values, see TS GSM 04.08. W 3404583 0079982 471 D 87654321 0x10 . . 1010 0x11 . . 1010 1011 Page 11 GSM 04.80 - version 4.7.0 : June 1993 Message types Clearing mes

42、sages: i - RELEASE COMPLETE Miscellaneous message group: - FACILITY - REGISTER 3.4 Message type The message type IE and its use are defined in TS GSM 04.07, Table 3.1/04.80 defines the value part of the message type IE used in the supplementary service protocol. Note 2: Bit 7 is reserved for the sen

43、d sequence number in messages sent from the mobile station. In messages sent from the network, bit 7 is coded with a “O“, see TS GSM 04.07. Table 3.1 /GSM 04.80 Message types m 3404583 0039983 308 m Page 12 GSM 04.80 - version 4.7.0 : June 1993 3.5 Other information elements These information elemen

44、ts are coded according to the general coding rules as defined in TS GSM 04.08. Table 3.2/GSM 04.80 contains the codepoints allocated to the information elements used in messages defined in this technical specification. All IEs are defined in TS GSM 04.08, but the content of the Facility and SS versi

45、on indicator IEs are defined within this specification. 187654321 r Reference I I (IE content) o . . . . . . . Type 3 and 4 information elements I l 0001000 Cause 0011100 Facility 1111111 SS version indicator TS GSM 04.08 3.6 3.8.2 Table 3.2/GSM 04.80 Information elements specific to call independen

46、t supplementary service control 3.6 Facility information element The purpose of the Facility information element is to indicate the invocation and operation of supplementary services, identified by the corresponding operation code within the Facility information ebement. The Facility information ele

47、ment is coded as shown in figure 3.1IGSM 04.80 and tables 3.3/GSM 04.80 to 3.1 7IGSM 04.80. 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, see TS GSM 04.06. I 8 7 6 5 4 3 2 1 octet 1 OI O O 1 1 1 O Io Facilit

48、y IEl Length of Facility contents 1 octet 2 I Note: One or more components may be included depending on specific service requirements. Figure 3.1 /GSM 04.80 Facility information element D 3404583 0079984 244 m Pago 13 GSM 04.80 - version 4.7.0 : June 1993 3.6.1 Component (octet 3 etc) This section p

49、rovides the formats and encoding of components in the Facility information element. Formats and encoding methods make use of and is a subset of recommendation CCIlT Q.773 (Transaction Capabilities formats and Encoding) and T/S 43/88. The used part of Q.773 respectively T/S 43/88 is almost the same as the Component Portion of TCAP messages. The only difference is that returnResuitNotLast is not used. This section is further based on - - and is consistent with these CCITT recommendations. The CCIl7 X.208 and X.209 formal d