1、3404583 0337978 616 Released: 14 July 1994 GSM 03.11 Version: 4.7.0 Date: I July I994 Source: ETSI TC-SMG UDC: 621.396.21 Reference: GSM 03.1 1 Key words: European digital cellular telecommunications system, Global System for Mobile communications (GSM) European digital cellular telecommunications s
2、ystem (Phase 2); Technical realization of supplementary services (GSM 03.11) ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: 06921 Sophia Antipolis Cedex - FRANCE Office address: Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE Tel.: + 33 92 94 42 O0 -
3、Fax: + 33 93 65 47 16 European Telecommunications Standards Institute 1994. All rights reserved. No part may be reproduced except as authorised by written permission. The copyright and the foregoing restriction on reproduction extend to all media in which the information may be embodied. Page 2 GSM
4、03.1 1 version 4.7.0 3404583 0117979 552 H 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 “ETCI Editing and Standards Approval Dept.“ at the
5、address shown on the title page. 9 3404583 OLL7980 274 9 Page 3 GSM 03.1 1 version 4.7.0 Contents Foreword . 5 1 General . 7 Scope . 7 1 . 1 1.3 1.2 Normative references 7 Definitions and abbreviations . 8 2 Activation. deactivation. registration. erasure. interrogation and invocation . 9 General .
6、9 2.1 2.1.1 2.1.2 Definition of “state vectors” . 9 Handling of service states at the HLR . 10 2.1.2.1 Encoding of SS-Status 11 2.1.2.2 Invocation of services at the HLR . 11 2.1.3.1 2.1.3.2 Interrogation of the service at the VLR and notifications from VLR 12 Handling of SS-Status at the MS . 12 2.
7、1.3 Handling of SS-Status at the VLR 11 Invocation of services at the VLR . 12 2.1.4 Handling of call independent SS procedures with respect to basic service 2.2 2.3 groups 12 Exceptional handling of basic service codes . 13 3 Password handling 18 Registration of password . 23 Use of password 23 3.1
8、 General . 18 3.4 Deactivation 26 3.2 3.3 4 5 History 28 Supplementary service data management . 27 Format of description 27 W 3404583 0337983 LOO W Page 5 . GSM 03.1 1 version 4.7.0 Foreword This section will be provided later. Previous page is blank H 3404583 0117982 047 Page 7 GSM 03.1 1 version
9、4.7.0 1 General 1.1 Scope This technical specification describes the general aspects on how supplementary services in the GSM system are realized from a technical point of view. Description of technical realization for specific supplementary services can be found in GSM 03.8 and 03.9-series technica
10、l specifications. All supplementary services may require signalling on the radio path. Signalling procedures and messages used are defined in the GSM 04.8 and 04.9x-series of technical specifications. For some supplementary services information needs to be transferred between the home location regis
11、ter (HLR), the visitor location register (VLR) and the mobile services switching centre (MSC). Signalling procedures for such information transfer are defined in technical specification GSM 09.02. Definitions and descriptions of supplementary services are given in the GSM 02.8 and 02.9-series of tec
12、hnical specifications. Definitions are given in technical specification GSM 02.04. NOTE 1 : The technical specifications on the technical realization of supplementary services do not distinguish between subscriber, user and customer, since all three do not fully cover the textual needs. Generally th
13、e term “subscriber“ is used, even if this person is not having the subscription. NOTE 2: The terms “he“, “his“ and “him“ are used as abbreviation of “he/she“, “hidher“ and “him/her“ respectively. 1.2 Normative references This ETS incorporates by dated and undated reference, provisions from other pub
14、lications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this ETC only when incorporated in it by amendment or revision. For undat
15、ed references, the latest edition of the publication referred to applies. 121 i41 i71 GSM 01.04: “European digital cellular telecommunications system (Phase 2); “Abbreviations and acronyms“. GSM 02.04: “European digital celiular telecommunications system (Phase 2); General on supplementary services“
16、. GSM 02.30: “European digital cellular telecommunications system (Phase 2); Man-Machine Interface (MMI) of the Mobile Station (MS)“. GSM 03.81 : “European digital cellular telecommunications system (Phase 2); Line identification supplementary services - Stage 2“. GSM 03.82: “European digital cellul
17、ar telecommunications system (Phase 2); Call Forwarding (CF) supplementary services - Stage 2“. GSM 03.83: “European digital cellular telecommunications system (Phase 2); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2“. GSM 03.84: “European digital cellular telecommunication
18、s system (Phase 2); Multi Party (MPTY) supplementary services - Stage 2“. Previous page is blank 3404583 OLL7983 T83 Page 8 GSM 03.1 1 version 4.7.0 i81 i91 i101 il 11 i1 21 i1 31 i141 i1 51 t161 11 71 I 81 191 1201 121 1 1.3 GSM 03.85: “European digital cellular telecommunications system (Phase 2);
19、 Closed User Group (CUG) supplementary services - Stage 2“. GSM 03.86: “European digital cellular telecommunications system (Phase 2); Advice of Charge (AOC) supplementary services - Stage 2“. GSM 03.88: “European digital cellular telecommunications system (Phase 2); Call Barring (CB) Supplementary
20、services - Stage 2“. GSM 03.90: “European digital cellular telecommunications system (Phase 2); Unstructured supplementary services operation - Stage 2“. GSM 04.80: “European digital cellular telecommunications system (Phase 2); Mobile radio interface layer 3 supplementary services specification For
21、mats and coding“. GSM 04.81 : “European digital cellular telecommunications system (Phase 2); Line identification supplementary services - Stage 3“. GSM 04.82: “European digital cellular telecommunications system (Phase 2); Call Forwarding (CF) supplementary services - Stage 3“. GSM 04.83: “ Europea
22、n digital cellular telecommunications system (Phase 2); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3“. GSM 04.84: “European digital cellular telecommunications system (Phase 2); Multi Party (MPTY) supplementary services - Stage 3“. GSM 04.85: “European digital cellular tel
23、ecommunications system (Phase 2); Closed User Group (CUG) supplementary services - Stage 3“. GSM 04.86: “European digital cellular telecommunications system (Phase 2); Advice of Charge (AOC) supplementary services - Stage 3“. GCM 04.88: “European digital cellular telecommunications system (Phase 2);
24、 Call Barring (CB) supplementary services - Stage 3“. GSM 04.90: “European digital cellular telecommunications system (Phase 2); Unstructured supplementary services operation - Stage 3“. GSM 09.02: “European digital cellular telecommunications system (Phase 2); Mobile Application Part (MAP) specific
25、ation“. Definitions and abbreviations Abbreviations used in this specification are listed in GSM 01.04. 3404583 OlLidLi 91T Page 9 GSM 03.1 1 version 4.7.0 2 Activation, deactivation, registration, erasure, interrogation and invocation 2.1 General Activation, deactivation, registration, erasure, int
26、errogation and invocation are defined independently from a particular supplementary service. Whether they are applicable to a particular supplementary service or not is defined in the corresponding TS GSM 03.8 and 03.9-series. The invocation of a supplementary service is executed as described in the
27、 corresponding stage 2 description and always includes a MSC and a location register. When a MSC receives a request for either activation/deactivation or registration/erasure or an interrogation, it invokes one of the following procedures. The MSC then can: - contact only the current VLR (e.g. inter
28、rogation of a call forwarding conditional supplementary service); - contact only the HLR (e.g. interrogation of the supplementary service call forwarding unconditional); - contact the HLR, after which the HLR updates the VLR (e.g. registration of a forwarding number for a conditional call forwarding
29、 supplementary service). Which of the above listed procedures is applied for a call independent supplementary service operation is described in the corresponding TS GSM 03.8 and 03.9-series. Successful activation, deactivation, registration and erasure change the service state at the HLR. These tran
30、sitions (if applicable to a particular service) are defined in the GSM 03.8 and 03.9- series, Note that the HLR may also change the service state due to “HLR Induction“ (see section 2.1 .I I. In connection with supplementary service operations the served subscriber or remote subscribers may get noti
31、fications from the network. 2.1 .I Definition of “state vectors“ In order to provide a tool to define service states the concept of a “state vector“ is introduced. The state vector is used to represent the state of the service in terms of four variables: 1) Provisioning State, possible values are “P
32、rovisioned“ or “Not Provisioned“; 2) Registration State, possible values are “Registered“, “Erased“, or “Not Applicable“; 3) Activation State, possible values are “Not Active“, “Active and Operative“ or “Active and Quiescent“; 4) HLR Induction State, possible values are “Induced“ or “Not Induced“. T
33、he state vector represents the state of the service by using all four variables together. The state vector is represented using the notation: IProvisioning State, Registration Stete, Activation State, HLR Induction State) e.g.: (Provisioned, Registered, Not Active, Not Induced). W 3404583 OLL7985 85
34、6 Page 10 GSM 03.1 1 version 4.7.0 Note that the state vector is a logical (not a physical) representation of the service state. Note also that though some parts of the state vector are similar to elements of SS-Status the mapping between the state vector and SS-Status is not one to one. The use of
35、state vectors is not intended to specify any particular implementation internally in a node. There is a relationship specified between the state vector and parts of the transfer syntax. This relationship is not a direct one-to- one mapping. The following text specifies the semantics of each variable
36、 in the state vector. The three variables “Provisioning State“, “Registration State“ and “Activation State“ are used to represent the state of the service according to the normal behaviour based on service provider and user actions. The “HLR Induction State“ records whether or not the HLR has tempor
37、arily induced the service (e.g. if the VLR does not support CUG, the HLR may induce an outgoing barring service). The Provisioning State, Registration State and Activation State are not affected by HLR induction of a service. Provisioning State - - has value “provisioned“, if the subscriber has a su
38、bscription to the service; has value “Not Provisioned“ otherwise. Registration State - - - has value “Erased“ otherwise. has value “Not Applicable“, if registration is not applicable to the service; has value “Registered“, if registration is applicable, and there is registration data available; Acti
39、vation State - - has value “Active and Operative“, if the service is in a state where it can be invoked (and this is not due to HLR induction); has value “Active and Quiescent“, if the service is in a state where it cannot be invoked, but where it will automatically move to the “Active and Operative
40、“ state when conflicting conditions are removed; has value “Not Active“ otherwise. - HLR Induction State - - has the value “Induced“ if the HLR has induced the service (e.g. if the VLR does not support CUG, the HLR may induce an outgoing barring service). has the value “Not Induced“ otherwise. For f
41、urther information about how HLR induction applies to particular services refer to the GSM 03.8 and 03.9-series. 2.1.2 Handling of service states at the HLR Valid states (represented by state vectors) are defined on a service-by-service basis in the GSM 03.8 and 03.9-series. For each service the set
42、 of valid states represents the logical states that can exist in the HLR. The HLR contains the master copy of service state information. = 3404583 O117786 772 Page 11 GSM 03.1 1 version 4.7.0 HLR Induction State “Not Induced“ P bit R bit A bit Provision State “Provisioned“ 1 “Not Provisioned“ O Regi
43、stration State “Registered“ 1 “Not Registered“ O “Not Applicable“ o11 Activation State “Active and Operative“ 1 “Active and Quiescent“ 1 “Not Active“ O 2.1.2.1 Encoding of SS-Status 0 bit O 1 O1 1 To send service state information to the VLR or the MS, the HLR often uses the SS-Status parameter, Thi
44、s parameter contains four bits (referred to here as the “P bit“, “R Bit“, “A bit“ and “Q bit“). In a phase 2 context the HLR shall encode the SS-Status using the mapping defined in this section from the service states to SS-Status. HLR Induction State “Induced“ If the HLR Induction State is “Not Ind
45、uced“ then: - If the Provisioning State is “Provisioned“, then the P bit shall be 1, otherwise the P bit shall be O. If the Registration State is “Registered“, the R bit shall be 1. If the Registration State is “Not Registered“ the R bit shall be O. If the Registration State is “Not Applicable“ the
46、R bit shall be either O or 1. If the Activation State is “Active and Operative“ the A bit shall be 1 and the O bit shall be O. If the Activation State is “Active and Quiescent“ the A bit shall be 1 and the Q bit shall be 1. If the Activation State is “Not Active“ the A bit shall be O and the Q bit s
47、hall be either O or 1. if the HLR Induction State is “Induced“ then the P bit shall be 1, the R bit shall be O or 1, the A bit shall be 1 and the Q bit shall be O. - - P bit R bit A bit Q bit 1 o1 1 O O11 Table 2.1 : Encoding of the P, R, A and Q bits in the SS-Status parameter 2.1.2.2 Invocation of
48、 services at the HLR If the service can be invoked at the HLR (e.g. to bar an incoming call) then invocation is possible only if the Activation State is “Active and Operative“. Note that the concept of HLR induction does not apply to services invoked at the HLR as the HLR can invoke the effect of th
49、ese services without needing to induce them first. 2.1.3 Handling of SS-Status at the VLR The VLR shall store sufficient information to support VLR based invocation, interrogation and notifications from the VLR to the MS. The VLR shall not check the internal consistency of SS-Status values received from the HLR (.e. it shall not impose any rules relating values of some bits in SS-Status to other bits). The VLR shall not check that the SS-Status received from the HLR is valid according to the VLRs definition of the relevant service. 3404583 O117987 629 Page 12 GSM 03
