hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 3.1 Definitions | All definitions used in this specification are specified in GSM 03.20 Annex E. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 3.2 Abbreviations | In addition to those mentioned below, abbreviations used in this specification are listed in GSM 01.04.
CTS Cordless Telephony System
SAGE Security Algorithms Group of Experts
CTS-ME CTS Mobile Equipment
MS-SIM Mobile Station CTS Subscriber Identity Module
FP-SIM Fixed Part CTS Subscriber Identity Module
CTS-MS A CTS-ME combined with a CTS-SIM
CTS-FP CTS Fixed Part
CTS-SN CTS Service Node
FPAC code entered by the CTS user to initialise a CTS-MS/CTS-FP
Ka CTS authentication key for a CTS-MS/CTS-FP pair
Kc CTS ciphering key for a CTS-MS/CTS-FP pair
Kop CTS authentication key used for the authentication of the CTS-FP by the CTS-SN and the authentication by the CTS-FP of the signature issued by the CTS-SN
Data1 CTS data constant used for the CTS-FP authentication by the CTS-SN
Data2 CTS data sequence to be signed by the CTS-SN and sent to the CTS-FP for signature authentication
MAC1 CTS result of the computation of the CTS-FP authentication algorithm using Kop and Data1
MAC2 CTS signature of the data sequence Data2
RIFP CTS Random Initial value sent from the CTS-MS to the CTS-FP
RIMS CTS Random Initial value sent from the CTS-FP to the CTS-MS
SRES1 CTS Signed RESponse of the CTS-FP’s CH1 and the Ka of the CTS-MS
SRES2 CTS Signed RESponse of the CTS-MS’s CH2 and the Ka of the CTS-FP
XSRES1 CTS Signed RESponse of the CTS-FP’s CH1 and the Ka of the CTS-FP (to be compared with SRES1)
XSRES2 CTS Signed RESponse of the CTS-MS’s CH2 and the Ka of the CTS-MS (to be compared with SRES2) |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 4 Use of the CTS algorithm set | The purpose of this clause is to define those organisations for whom the algorithm set is intended, describe the type of information which the algorithm set is intended to protect, indicate possible geographical/geopolitical restrictions on the use of equipment which embodies the algorithm set, and describe the types of implementations of the algorithm set that are envisaged. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 4.1 Use of the algorithm set | The algorithm set shall only be used for providing the authentication and key management as described in GSM 03.20 Annex E. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 4.2 Places of Use | The algorithm set is installed in each CTS Mobile Equipment (CTS-ME) ,in each CTS Fixed Part (CTS-FP) and in each CTS Service Node (CTS-SN). The standard does not forbid future use in a CTS-SIM in later CTS phases.
Legal restrictions on the use or export of equipment containing cryptographic features that are enforced by various European Governments may prevent the use of equipment in certain countries. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 4.3 Types of Implementation | An algorithm with minimal restrictions on export when licensed and managed as described in clause 5, is desired because of the global use of GSM.
The design of the algorithm set should support software implementations for 8 bit processors. Those implementing the algorithm set shall be required through a licence and confidentiality agreement which they shall sign with ETSI, as described in subclause 5.3, to adopt suitable measures to ensure that their implementations are commensurate with the need to maintain confidentiality of the algorithm set. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 5 Use of the algorithm specification | This clause addresses ownership of the algorithm set specification, to define which types of organisations are entitled to obtain a copy of the algorithm set specification, and to outline how and under what conditions such organisations may obtain the specification. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 5.1 Ownership | The algorithm set and all copyright to the algorithm set and test data specifications shall be owned exclusively by ETSI.
The design authority for the algorithm set shall be ETSI SAGE. Amendments to the algorithm set specification may be made only by ETSI SAGE under instruction authorised by the ETSI Board.
The algorithm set specification shall not be published as an ETSI standard or otherwise made publicly available, but shall be provided to organisations that need and are entitled to receive it subject to a licence and confidentiality agreement.
The licence and confidentiality agreement shall require recipients of the specification not to attempt to patent the algorithm or otherwise register any and IPR relating to the algorithm set or its use. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 5.2 Users of the specification | The algorithm set specification may be made available to those who need the algorithm set specification in order to build equipment or components (including IC cards) which embody (parts of) the algorithm set, according to the GSM-CTS standard. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 5.3 Licensing | Users of the algorithm set specification shall be required to sign a restricted usage and confidentiality agreement with ETSI.
Appropriate restricted usage and confidentiality agreements shall be drawn up by ETSI.
Usage shall be royalty free. However, the algorithm set custodian may impose a small charge to cover administrative costs involved in issuing the licenses.
The license and confidentiality agreement signed by an organisation that needs the algorithm set specification in order to build equipment or components which embody (part of) the algorithm set, shall require that organisation to adopt measures to ensure that its implementations of the algorithm set are commensurate with the need to maintain confidentiality of the algorithm. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 5.4 Management of the specification | The distribution procedure for the algorithm set specification shall be specified by ETSI. SAGE is expected to design the appropriate procedure for the distribution of the algorithm set after consulting ETSI SMG and GSM Association Security Group. The outline procedure is as follows:
- ETSI shall appoint a custodian for administration of the algorithm set specification;
- an organisation which intends to build equipment or components that embody (or part of) the algorithm set may request copies of the algorithm set specification (and test data) and a licence to use the algorithm set from the custodian;
- if an organisation mentioned above is entitled to use the algorithm set, the custodian shall issue the requested algorithm specifications subject to the organisation signing a licence and confidentiality agreement;
- at least manufacturers of CTS equipment who are ETSI members are entitled to the algorithms set of specifications. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6 Functional requirements | ETSI SAGE are required to design an algorithm set which satisfies the functional requirements specified in this clause. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1 Composition of the Algorithm Set and Type and Parameters of Algorithms | As specified in GSM 03.20 annex E, the algorithm set contains the following algorithms:
B1: Shall be used to compute the Kc from Ka and CH1. The algorithm shall have the following properties:
Input 1: Bit string of length |Ka|;
Input 2: Bit string of length |CH1|;
Output: Bit string of length |Kc|.
The algorithm should be designed such that it is difficult to infer any information about Input 1 from the knowledge of Input 2 and the Output (even if the details of the algorithm are known). Similarly it shall be difficult to infer any information about the Output from only the knowledge of Input 2.
B2: Shall be used to compute Ka from RIMS, RIFP, and FPAC. The algorithm shall have the following properties:
Input 1: Bit string of length |FPAC|;
Input 2: Bit string of length |RIMS|;
Input 3: Bit string of length |RIFP|;
Output: Bit string of length Ka.
The algorithm should be designed such that it is difficult to infer any information about Input 1 from the knowledge of Input 2, Input 3 and Output 1 (even if the details of the algorithm are known). Similarly it shall be difficult to infer any information about the Output from only the knowledge of Input 2 and Input 3.
B3: Shall be used to compute (X)SRES1 from Ka and CH1. The algorithm shall have the following properties:
Input 1: Bit string of length |Ka|;
Input 2: Bit string of length |CH1|;
Output: Bit string of length |(X)SRES1|.
The algorithm should be designed such that it is difficult to infer any information about Input 1 from the knowledge of Input 2 and the Output (even if the details of the algorithm are known). Similarly it shall be difficult to infer any information about the Output from only the knowledge of Input 2.
B4: Shall be used to compute (X)SRES2 from Ka and CH2.The algorithm shall have the following properties:
Input 1: Bit string of length |Ka|;
Input 2: Bit string of length |CH2|;
Output: Bit string of length |(X)SRES2|.
The algorithm should be designed such that it is difficult to infer any information about Input 1 from the knowledge of Input 2 and the Output (even if the details of the algorithm are known). Similarly it shall be difficult to infer any information about the Output from only the knowledge of Input 2.
The mutual authentication offered by B3 and B4 shall be protected against a reflection attack (e.g. by using a key offset method).
B5: Shall be used to compute MAC1 from Kop and Data1. The algorithm shall have the following properties:
Input 1: Bit string of length |Kop|;
Input 2: Bit string of length |Data1|;
Output: Bit string of length |MAC1|.
The algorithm should be designed such that it is difficult to infer any information about Input 1 from the knowledge of Input 2 and the Output (even if the details of the algorithm are known). Similarly it shall be difficult to infer any information about the Output from only the knowledge of Input 2.
B6: Shall be used to compute MAC2 from Kop and Data2. The algorithm shall have the following properties:
Input 1: Bit string of length |Kop|;
Input 2: Bit string of length |Data2|;
Output: Bit string of length |MAC2|.
The algorithm should be designed such that it is difficult to infer any information about Input 1 from the knowledge of Input 2 and the Output (even if the details of the algorithm are known). Similarly it shall be difficult to infer any information about the Output from only the knowledge of Input 2.
As long as the resilience requirements on the algorithm set are not violated, all algorithms in the set do not need to be distinct and complete. Indeed large parts of algorithm specifications might be identical.
Figure 1 shows the use of B3 and B4 to obtain mutual authentication between a CTS-MS and a CTS-FP, and the use of B1 for generating the ciphering key Kcx.
Figure 1: Mutual authentication of CTS-MS and CTS-FP using B3 and B4 and ciphering key Kcx generation by B1
Figure 2 shows the use of B2 to generate the key Ka.
Figure 2: Generation of initial key Ka
Figure 3:Computation of the result of the authentication of the CTS-FP using Kop and B5 algorithm
Figure 4 : Generation of the signature of the data sequence Data2 using Kop and B6 |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.1 FPAC | The CTS-FP is equipped with a manufacturer installed FPAC code. The FPAC is unstructured data. The FPAC is used to facilitate initial mutual authentication of CTS-MS and CTS-FP and to facilitate encryption set-up.
The length of the FPAC is 128 bits. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.2 CH1 and CH2 | The challenge from CTS-FP to CTS-MS (CH1) and the challenge from CTS-MS to CTS-FP (CH2) are random 128 bit strings.
6.1.3 Ka
The authentication key is unstructured data. It is generated by algorithm B2 from FPAC and two random inputs RIMS (generated by CTS-FP and sent to CTS-MS) and RIFP (generated by CTS-MS and sent to CTS-FP). The length is 128 bits.
6.1.4 Kc
The ciphering key (Kc) is unstructured data. It is generated by algorithm B1 from the authentication key Ka and the random challenge CH1. The length is 64 bits. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.5 Kop | The authentication key (Kop) is unstructured data. This key is generated from an authentication key stored on the FP-SIM and a key generation algorithm A8’ as described in GSM03.20 Annex E. The length is 128 bits. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.6 Data1 | The data sequence (Data1) is unstructured data. It length is n bytes. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.7 Data2 | The data sequence (Data2) is unstructured data. It length is n bytes. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.8 MAC1 | The authentication result (MAC1) is unstructured data. (MAC1) is computed form Kop and Data1 using the B5 algorithm. MAC1=B5(Kop, Data1).The length is 128 bits. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.9 MAC2 | The signature (MAC2) is unstructured data. The signature (MAC2) is generated using Kop and a sequence Data2. MAC2=B6(Kop, Data2). The length is 128 bits. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.10 SRES1 and SRES2 | The response sent from CTS-MS to CTS-FP (SRES1) and the response sent from CTS-FP to CTS-MS (SRES2) are 32 bit values computed from the authentication key (Ka) and the challenges CH1 and CH2 respectively. SRES1=B3(Ka,CH1) and SRES2=B4(Ka,CH2). |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.11 RIMS and RIFP | The generation of Ka through algorithm B2 involves the use of two random values RIMS and RIFP. RIMS is sent from CTS-FP to CTS-MS and RIFP is sent from CTS-MS to CTS-FP. Both RIMS and RIFP are 64 bits long. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.12 SRES1 and SRES2 | The response expected by the CTS-FP (XSRES1) and the response expected by the CTS-MS (XSRES2) are 32 bit values computed from the authentication key (Ka) and the challenges CH1 and CH2 respectively. XSRES1=B3(Ka,CH1) and XSRES2=B3(Ka,CH2). |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.2 Interfaces to the Algorithm | The dimensioning and definition of the interface parameters to the algorithms described in subclause 6.1 are listed below. In this listing X[i] denoted the i-th bit of the variable X.
FPAC 128 bits: FPAC[0], FPAC[1], …, FPAC[127]
CH1 128 bits: CH1[0], CH1[1],…, CH1[127]
CH2 128 bits: CH2[0], CH2[1],…, CH2[127]
Ka 128 bits: Ka[0], Ka[1],…, Ka[127]
Kc 64 bits: Kc [0], Kc [1],…, Kc [63]
Kop 128 bits: Kop[0], Kop[1],…, Kop[127]
Data1 n bytes: Data1[0], Data1[1],…, Data1[8n-1]
Data2 n bytes: Data2[0], Data2[1],…, Data2[8n-1]
MAC1 128 bits: MAC1[0], MAC1[1],…, MAC1[127]
MAC2 128 bits: MAC2[0], MAC2[1],…, MAC2[127]
SRES1 32 bits SRES1[0], SRES1[1],…, SRES1[31]
SRES2 32 bits SRES2[0], SRES2[1],…, SRES2[31]
RIMS 64 bits: RIMS[0], RIMS[1],…, RIMS[63]
RIFP 64 bits: RIFP[0], RIFP[1],…, RIFP[63]
XSRES1 32 bits XSRES1[0], XSRES1[1],…, XSRES1[31]
XSRES2 32 bits XSRES2[0], XSRES2[1],…, XSRES2[31] |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.3 Implementation and Operational Considerations | The algorithm should be designed for software implementations
As a reference, the set of the algorithms should be implementable on a 6805-family of microprocessors, in particular the Motorola SC21 series and Philips 83C852 series, running at 4 MHz. However the performance of the implementation of the algorithms should favourably scale when implementation is carried out on a 16-bit or 32-bit processor which support similar logical and arithmetical operations as found on the 6805-family but with larger word size.
For the reference platform it should be possible to realise an efficient state of the art implementation such that
- for each of the algorithms B1, B3, B4, the time for one operation is less than 200 milliseconds;
- for the algorithm B2 the time for one operation is less than 250 milliseconds;
- the complete set of algorithms can be implemented using less than 3000 bytes ROM and 128 bytes RAM. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.4 Resilience of Algorithm set | The algorithm set should be designed with a view to its continued use for a period of at least 15 years.
The algorithm set should be designed such that:
- the strength of the individual algorithms should not be significantly less than indicated by its key parameter(s);
- the requirements on the individual algorithms listed in subclause 6.1 should be fulfilled.
ETSI SAGE are required to design the algorithm set to a strength which reflects the above requirements but imposes minimal restrictions on the exportability of equipment that is fitted with the algorithm. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7 Algorithm specification and test data requirements | ETSI SAGE are required to provide four separate deliverables: a specification of the algorithm, a set of design conformance test data, a set of algorithm input/output test data and a design and evaluation report. Requirements on the specification and test data deliverables are given in this clause, those on the design and evaluation report in subclause 8.3.
The design of the algorithm set will have a pre-evaluation phase. Equipment manufacturers/organisations that have contributed to the funding of the SAGE design work for this algorithm set are allowed to participate in this evaluation and can get access to the algorithm specifications as they stand.
The purpose of the pre-evaluation phase is to allow manufacturers/implementators early visibility of the structure of the algorithm(s) so that they can assess what is involved in its implementation, and confirm that there are no problems in realising the design in the target environment. They will be provided with an algorithm specification that accurately reflects structure and processing requirements of the algorithm set. Any changes between pre-evaluation specification and the final specification are not expected to have any significant impact on code size or algorithm timing.
The specification shall include an annex which provides simulation code written in ANSI C. Access requires a non-disclosure agreement between the manufacturer/organisation and ETSI SAGE.
Those equipment manufacturers/organisations that do not contribute will get access to algorithm set specification only after the SAGE work has been completed. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7.1 Specification of the algorithm set | An unambiguous specification of the algorithm set needs to be provided which is suitable for use by implementors of the algorithm set.
The specification shall include an annex which provides simulation code for the algorithm set written in ANSI C. The specification may also include an annex containing illustrations of functional elements of the algorithm set. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7.2 Design conformance test data | Design conformance test data is required to allow implementors of the algorithm set to test their implementations.
The test data needs to be designed to give a high degree of confidence in the correctness of implementations of the algorithm set.
The test data shall be designed so that significant points in the execution of the algorithm may be verified. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7.3 Algorithm set input/output test data | Algorithm set input/output test data is required to allow users of the algorithm set to test each member of the algorithm set as a "black box" function.
The input/output test data shall consist solely of data passed across the interfaces to the algorithm set members. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7.4 Format and handling of deliverables | The specification of the algorithm set shall be produced on paper, and provided only to the ETSI appointed custodian (see subclause 5.4). The document shall be marked "Strictly ETSI confidential" and carry the warning "This information is subject to a licence and confidentiality agreement".
The design conformance test data shall be produced on paper, and provided only to the ETSI appointed custodian. The document shall be marked "Strictly ETSI confidential" and carry the warning "This information is subject to a licence and confidentiality agreement".
The algorithm set input/output test data shall be produced on paper and on magnetic disc. The document and disc shall be provided to the ETSI appointed custodian. Special markings or warnings are not required.
The design and evaluation report should be published as an ETSI Technical Report. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 8 Quality assurance requirements | This clause advises ETSI SAGE on measures needed to provide users of the algorithm set with confidence that it is fit for purpose, and users of the algorithm set specification and test data assurance that appropriate quality control has been exercised in their production.
The measures shall be recorded by ETSI SAGE in a design and evaluation report which shall be published by ETSI as a Technical Report. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 8.1 Quality assurance for the algorithm set | Prior to its release to the ETSI custodian, the algorithm set needs to be approved as meeting the technical requirements specified in clause 6 by all members of ETSI SAGE. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 8.2 Quality assurance for the specification and test data | Prior to delivery of the algorithm set specification, two independent simulations of each algorithm in the set needs to be made using the specification, and confirmed against test data designed to allow verification of significant points in the execution of each algorithm in the set.
Design conformance and algorithm input/output test data needs to be generated using a simulation of each algorithm in the set produced from the specification and confirmed as above. The simulation used to produce this test data needs to be identified in the test data deliverables and retained by ETSI SAGE. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 8.3 Design and evaluation report | The design and evaluation report is intended to provide evidence to potential users of the algorithm set, specification and test data that appropriate and adequate quality control has been applied to their production. The report shall explain the following:
- the algorithm set and test data design criteria;
- the algorithm set evaluation criteria;
- the methodology used to design and evaluate algorithms in the set;
- the extent of the mathematical analysis and statistical testing applied to the algorithms in the set;
- the principal conclusions of the algorithm set evaluation;
- the quality control applied to the production of the algorithm set specification and test data.
The report shall confirm that all members of ETSI SAGE have approved the algorithm set, specification and test data.
The report shall not contain any information about the algorithm set, such as design techniques used, mathematical analysis or statistical testing of components of the algorithm set, which might reveal part or all of the structure or detail of the algorithm set. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 9 Summary of ETSI SAGE deliverables | - Specification of the algorithm set:
- a confidential document for delivery only to the ETSI custodian;
The specification shall include a simulation code of the algorithm set written in ANSI C.
- Design conformance test data:
- a confidential document for delivery only to the ETSI custodian;
- Algorithm set input/output test data:
- in a document and on disc for delivery to the ETSI custodian;
- Design and evaluation report;
- to be published as an ETSI Technical Report. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 9.1 Pre-evaluation phase deliverables | - Specification of the algorithm set at the pre-evaluation version of the algorithm set:
- a confidential document for delivery only to manufacturers that have contributed to funding of the algorithm design;
The specification shall include a simulation code of the algorithm set written in ANSI C.
Annex A (informative):
Status of GSM 01.56
Status
of
GSM 01.56
March 1998
version 0.0.1 prepared for SMG10 CTS Ad hoc meeting #2
March 26 1998
Version 0.0.2 prepared for SMG10 #2/98
April 9 1998
Version 0.0.3 reviewed by SMG10 #2/98
July 1998
Version 0.1.1 SMG10 #3/98
November 1998
Version 0.2.0 SMG10 #4/98
January 1999
Version 0.3.0 reviewed following SMG10 #4/98
February 1999
version 1.0.0 to SMG#28 for information and approval; approved by SMG#28 to become version 7.0.0
History
Document history
V7.0.0
May 1999
Unpublished |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 0 Scope | The present document describes and defines a recommended set of Teleservices to be supported by a GSM PLMN in connection with other networks as a basis for defining the network capabilities required.
Teleservices not included in the present document should not be introduced unilaterally by a mobile network operator, if the provision of this service requires that the GSM signalling specifications are modified. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 0.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunication services supported by a GSM Public Land Mobile Network (PLMN)".
[3] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)".
[4] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services".
[5] GSM 02.68: "Digital cellular telecommunications system (Phase 2+); Voice Group Call Service (VGCS) - Stage 1".
[6] GSM 02.69: "Digital cellular telecommunications system (Phase 2+); Voice Broadcast Service (VBS) - Stage 1".
[7] GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point‑to‑Point (PP)".
[8] GSM 03.41: "Digital cellular telecommunications system (Phase 2+); Technical realization of Short Message Service Cell Broadcast (SMSCB)".
[9] GSM 04.08: "Digital cellular telecommunication system (Phase 2+); Mobile radio interface layer 3 specification".
[10] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
[11] GSM 07.05: "Digital cellular telecommunications system (Phase 2+); Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)".
[12] CCITT Recommendation T.4: "Standardization of group 3 facsimile apparatus for document transmission".
[13] CCITT Recommendation T.30: "Procedures for document facsimile transmission in the general switched telephone network". |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 0.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04 [1]. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 1 Framework for describing teleservices supported by a GSM PLMN | Teleservices supported by a GSM PLMN are described by a number of attributes which are intended to be largely independent.
These attributes are described and defined in specification GSM 02.01 [2].
They are grouped into three categories:
- High layer attributes;
- Low layer attributes (describing the Bearer capabilities which support the Teleservice).
- information transfer attributes;
- access attributes.
- General attributes.
NOTE: Teleservices generally make use of underlying lower layer capabilities of Bearer Services as defined in specification GSM 02.02 [3]. However, where Teleservices are provided by a single Administration, RPOA or other services provider, the combination of values of lower layer attributes applicable to specific Teleservices may not necessarily be identical to any of those identified for the Bearer Services appearing in specification GSM 02.02 [3].
Figure 1 shows the relationship between the different categories of services attributes, and their scope within a Teleservice.
NOTE 1: A transit network may not exist.
NOTE 2: Communication may be established from both ends in principle.
Figure 1: Relationship between the categories of services attributes and their scope
within a Teleservice |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2 List of the teleservice attributes | Table 1 gives the list of the attributes. For the definitions and possible values of these attributes, see GSM 02.01 [2].
Table 1: List of Teleservice attributes
1. High layer capabilities
1.1 Type of user information
1.2 Layer 4 protocol functions
1.3 Layer 5 " "
1.4 Layer 6 " "
1.5 Layer 7 " "
Dominant Teleservice attribute category
Secondary attributes
" "
2. Low layer capabilities (describing the Bearer capability which supports the Teleservice) |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1 Information transfer | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.1 Information transfer capabilities | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.2 Information transfer mode | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.3 Information transfer rate | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.4 Structure | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.5 Establishment of communication | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.6 Communication configuration | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.7 Symmetry | " "
" "
" "
Individual services (in the category)
2.2 Access (GSM 02.01) |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.2.1 Signalling access | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.2.2 Information access | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.3 Interworking | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.3.1 Terminating network type | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.3.2 National/international interworking | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.3.3 Interface of terminal equipment | Qualifying attributes
" "
" "
" "
" "
Further specify the individual services
3. General
3.1 Supplementary services provided
3.2 Quality of service
3.3 Operational and commercial |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 3 List of teleservice categories and individual teleservices | Table 2 presents a list of all Teleservices categories and of individual Teleservices and the associated dominant and secondary attributes. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 4 Description of individual teleservices | The annex contains a data sheet per Teleservice with all attributes and comments. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 5 Bearer capabilities supporting teleservices | According to specification GSM 02.01 [2] the Bearer Capability defines the technical features of a Teleservice as they appear to the user at the customer access point or an appropriate interface of a fixed network. The Bearer Capability is characterized by information transfer, access and interworking attributes. The same set of attributes as for a Bearer Service is used. A Bearer Capability is associated with every Teleservice. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 6 Possible further evolution phases of teleservices in a GSM PLMN | Possible further evolution phases according to the definition in GSM 01.06 could become necessary. For instance, speech coding procedures (half rate speech codec) will provide for the reduction of the bit rate for speech transmission and thus increase the network capacity.
Table 2: Teleservice categories and Teleservices
Dominant attribute
Category of
teleservice
Individual Teleservice
Type of user in- formation
No
Name
No
Name
Speech
1
Speech trans-mission
11
12
Telephony
Emergency Calls
Short message
2
Short message service
21
22
23
Short message MT/PP
Short message MO/PP
Short message cell broadcast
Facsimile
6
Facsimile
trans -
61
Alternate speech and facsimile group 3
T
NT
mission
62
Automatic Facsimile group 3
T
NT
Speech
9
Voice Group service
91
92
Voice Group Call Service
Voice Broadcast Service
NOTE: Direct access to private networks is foreseen by recommended provision A.
Annex A (normative):
Description of individual Teleservices
NOTE 1: Interworking with Telex may be provided via teletex-telex- or other interworking functions.
NOTE 2: Within the GSM PLMN the "Information transfer rate" attribute is not indicated, this is because the user may access the PLMN at either an "S" or "R" reference point. In addition, the "Information transfer rate" at other reference points within the PLMN assumed or otherwise may be different.
A.1 Individual Teleservices
A.1.1 Telephony
Teleservice 11, Telephony
1.
1.1 Type or user information
speech
A
HLC
1.2 Layer 4 protocol functions
-
T
1.3 Layer 5 protocol functions
-
T
1.4 Layer 6 protocol functions
-
R
1.5 Layer 7 protocol functions
-
I
2.
2.1
2.1.1 Information transfer capability
speech (digital representation)
B
LLC
2.1.2 Information transfer mode
circuit
U
Inform
2.1.3 Information transfer rate
not applicable
T
transfer
2.1.4 Structure
not applicable
E
2.1.5 Establishment of connection
demand MO MT
S
2.1.6 Communication configuration
point-to-point
2.1.7 Symmetry
bidirectional symmetry
2.2
2.2.1 Signalling access
manual
Access
2.2.2 Information access
rate
full rate/half rate
at MS
(GSM 02.01)
interface
2.3
2.3.1 Visible network type
PSTN/ISDN/GSM-PLMN
Inter-
2.3.2 National/Internat. interworking
international/national
working
2.3.3 Interface of TE to terminating
2 wire, analogue
4 wire
S (B+B+D)
GSM/ME
3.
3.1 Supplementary service provided
GSM 02.04
Gen
3.2 Quality of service
Comments:
This service provides the transmission of speech information and audible signalling tones of the PSTN/ISDN. In the GSM PLMN and the fixed network processing technique appropriate for speech such as analogue transmission, echo cancellation and low bit rate voice encoding may be used. Hence, bit integrity is not assured.
1) Transparency for telephone signalling tones is provided.
2) Transparency for voice band facsimile signals is not mandatory. (Appropriate bearer services see GSM 02.02 [3].)
3) Transparency for end to end speech encryption is not mandatory. If a user needs to apply this technique an appropriate bearer service (GSM 02.02 [3]) can be used.
4) Transmission of DTMF is provided in the mobile to fixed direction (e.g. for controlling voice mail boxes) during any time of an established call.
A.1.2 Emergency calls
Teleservice 12, Emergency calls
1.
1.1 Type or user information
speech
A
HLC
1.2 Layer 4 protocol functions
-
T
1.3 Layer 5 protocol functions
-
T
1.4 Layer 6 protocol functions
-
R
1.5 Layer 7 protocol functions
-
I
2.
2.1
2.1.1 Information transfer capability
speech (digital representation)
B
LLC
2.1.2 Information transfer mode
circuit
U
Inform
2.1.3 Information transfer rate
not applicable
T
transfer
2.1.4 Structure
not applicable
E
2.1.5 Establishment of connection
demand MO MT
S
2.1.6 Communication configuration
point-to-point
2.1.7 Symmetry
bidirectional symmetry
2.2
2.2.1 Signalling access
manual
Access
2.2.2 Information access
rate
full rate/half rate
at MS
(GSM 02.01)
interface
2.3
2.3.1 Visible network type
PSTN
ISDN
Inter-
2.3.2 National/Internat. interworking
national
working
2.3.3 Interface of TE to terminating Ntwk.
2 wire
4 wire
3.
3.1 Supplementary service provided
GSM 02.04 (see note 3)
Gen
3.2 Quality of service
Comments:
1) A standardized access method throughout all GSM PLMNs is mandatory. In addition national emergency call numbers of PSTN/ISDN must be usable from MS.
2) It shall be an option of the network operator whether to accept emergency calls coming from mobile stations which do not transmit an IMSI or a TMSI.
3) Emergency calls supersede all constraints imposed by supplementary services or mobile station features used for other Tele or Bearer services. The lock state of the MS is overridden by the SOS‑procedure.
4) Emergency calls will be routed to the emergency services in accordance with national regulations.
5) In order to help identifying callers in cases of misuse databases in the GSM PLMN may be accessed to retrieve the identity of the calling MS.
A.1.3 Short Message Service (SMS)
A.1.3.1 Short message service MT/PP
Teleservice 21, Short Message MT point-to-point 1), 2)
1.
1.1 Type or user information
short message, 160 characters
A
1.2 Layer 4 protocol functions
T
1.3 Layer 5 protocol functions
see GSM 03.40
T
1.4 Layer 6 protocol functions
see GSM 03.40
R
1.5 Layer 7 protocol functions
see GSM 03.40
I
2.
2.1
2.1.1 Information transfer capability
not applicable
B
2.1.2 Information transfer mode
not applicable
U
Inform
2.1.3 Information transfer rate
not applicable
T
transfer
2.1.4 Structure
not applicable
E
2.1.5 Establishment of connection
not applicable
S
2.1.6 Communication configuration
not applicable
2.1.7 Symmetry
not applicable
2.2
2.2.1 Signalling access
see GSM 07.05
Access
2.2.2 Information access
rate
not applicable
at MS
(GSM 02.01)
interface
2.3
2.3.1 Visible network type
not applicable 3)
Inter-
2.3.2 National/Internat. interworking
not applicable 3)
working
2.3.3 Interface of TE to terminating Ntwk.
not applicable 3)
3.
3.1 Supplementary service provided
GSM 02.04
Gen
3.2 Quality of service
Comments:
1) This service provides the transmission of a short message from a message handling system (service centre) to a mobile station. The service centre is functionally separated from the GSM PLMN.
2) After reception an acknowledgement message should be sent back.
3) There is only an interworking between the PLMN and SMS Service Centre (SMS-SC). Connections from the fixed network to the SMS-SC are out of the scope of the GSM Standard.
4) The information transfer attributes refer to the connection-oriented services (ISDN, Bluebook Q.931). The Short Message Service is not a connection orientated service, hence the transfer attributes here are not applicable.
A.1.3.2 Short message service MO/PP
Teleservice 22, Short Message MO point-to-point 1), 2)
1.
1.1 Type or user information
short message, 160 characters
A
1.2 Layer 4 protocol functions
T
1.3 Layer 5 protocol functions
see GSM 03.40
T
1.4 Layer 6 protocol functions
see GSM 03.40
R
1.5 Layer 7 protocol functions
see GSM 03.40
I
2.
2.1
2.1.1 Information transfer capability
not applicable
B
2.1.2 Information transfer mode
not applicable
U
Inform
2.1.3 Information transfer rate
not applicable
T
transfer
2.1.4 Structure
not applicable
E
2.1.5 Establishment of connection
not applicable
S
2.1.6 Communication configuration
not applicable
2.1.7 Symmetry
not applicable
2.2
2.2.1 Signalling access
see GSM 07.05
Access
2.2.2 Information access
rate
not applicable
at MS
(GSM 02.01)
interface
2.3
2.3.1 Visible network type
not applicable 3)
Inter-
2.3.2 National/Internat. interworking
not applicable 3)
working
2.3.3 Interface of TE to terminating Ntwk.
not applicable 3)
3.
3.1 Supplementary service provided
GSM 02.04
Gen
3.2 Quality of service
Comments:
1) This service provides the transmission of a short message from a mobile station to a message handling system (service centre). The service centre is functionally separated from the GSM PLMN.
2) After reception an acknowledgement message is sent back.
3) There is only an interworking between the PLMN and SMS Service Centre (SMS-SC). Connections from the fixed network to the SMS-SC are out of the scope of the GSM Standard.
4) The information transfer attributes refer to the connection-oriented services (ISDN, Bluebook Q.931). The Short Message Service is not a connection orientated service, hence the transfer attributes here are not applicable.
5) Information from the following sources at the MS might be transmitted:
- a pre-recorded message in a store;
- a number from the dialling key pad;
- information from an external keyboard or terminal equipment connected to the ME.
A.1.3.3 Short message service Cell Broadcast (CB)
Teleservice 23, Short Message transmission cell broadcast
1.
1.1 Type or user information
short message, 93 characters 4)
A
1.2 Layer 4 protocol functions
T
1.3 Layer 5 protocol functions
see GSM 03.41
T
1.4 Layer 6 protocol functions
see GSM 03.41
R
1.5 Layer 7 protocol functions
see GSM 03.41
I
2.
2.1
2.1.1 Information transfer capability
not applicable
B
2.1.2 Information transfer mode
not applicable
U
Inform
2.1.3 Information transfer rate
not applicable
T
transfer
2.1.4 Structure
not applicable
E
2.1.5 Establishment of connection
not applicable
S
2.1.6 Communication configuration
not applicable
2.1.7 Symmetry
2.2
2.2.1 Signalling access
not applicable
Access
2.2.2 Information access
rate
not applicable
at MS
(GSM 02.01)
interface
not applicable
2.3
2.3.1 Visible network type
2)
Inter-
2.3.2 National/Internat. interworking
2)
working
2.3.3 Interface of TE to terminating Ntwk.
2)
3.
3.1 Supplementary service provided
GSM 02.04
Gen
3.2 Quality of service
Comments:
1) This service provides the transmission of a short message from a message handling system to all mobile stations in the area of a Base Station. The service centre is functionally separated from the GSM PLMN. There is no acknowledgement message after reception.
2) An interworking only with the Cell-Broadcast Service Centre is foreseen. Connections from the fixed network to the SC are out of the scope of the GSM Standard.
3) The information transfer attributes refer to the connection-oriented services (ISDN, Bluebook Q.931). The Short Message Service is not a connection orientated service, hence the transfer attributes here are not applicable.
4) GSM 03.41 provides up to 15 concatenated "pages" of up to 93 characters each.
A.1.3.4 Short message service description
Description of:
teleservice 21, "Short message MT/PP";
teleservice 22 "Short message MO/PP"; and
teleservice 23 "Cell broadcast short messages". |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 1 Introduction | The purpose of this annex is to describe the short message teleservice.
Three different types of short messages are defined, namely short message MT/PP (Mobile Terminated/Point-to-point), short message MO/PP (Mobile Originated/Point-to-point) and Cell Broadcast short messages. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2 Definition of the short message service MT/PP and MO/PP | For both mobile originated and mobile terminated services the Service Centre acts as store and forward centre. The Service Centre is functionally separate from the PLMN although this does not preclude an integrated implementation. More than one service centre may be connected to a PLMN. Messages may be input to the service centre from a fixed network customer by means of a suitable telecommunications service either from the fixed network, e.g. speech, telex, facsimile, etc. or from a mobile network customer. The list is not intended to be comprehensive and it is entirely open to the service centre provider what telecommunication services it supports. The service centre shall then reformat the message into that provided by the short message service, for delivery to the mobile station.
For mobile originated SMS messages the SMT formats the message into that used by the SMS service and sends to the service centre (to allow interworking with ERMES also ERMES-format addresses may be sent from the MS to the SC). In general the user may use alphanumeric addresses for more user convenience. In principle the message may be intended for a subscriber on the fixed network or for another mobile subscriber. For the message to another mobile subscriber the service centre should deliver as described in this section.
The message text is limited to a length of 160 characters.
The originator does not need to know the location of the mobile subscriber to whom he wants to send a message. The message is addressed to the recipient's Directory Number.
As a part of the basic service for both MT and MO, an acknowledgement will be provided on a message by message basis to the SC (MT) or MS (MO). This acknowledgement indicates that the PLMN has successfully transferred the message to the MS (MT) or SC (MO).
Optionally, the SC may offer final delivery notification to the originator. In this case, the originator may request to have a notification returned from the SC informing her about the delivery of the Short Message to the recipient. This delivery report indicates whether this particular message has been correctly received at the receiving station or not, to the extent that the SC is able to establish this. It does not indicate whether the message has been read. If the delivery report is negative, i.e. the message has not been successfully delivered to the recipient, it shall include the failure cause.
The delivery report is sent to the originator, if reachable, as soon as the information (positive or negative) is available.
In addition, the SC may use the delivery report capabilities for other purposes, such as intermediate status reports etc.
All GSM point-to-point short messages are either to or from the service centre. A message from one mobile station to another must pass through a service centre. This case is effectively an MO and MT message together. The two transactions are separate, though clearly related.
Point-to-point messages may be sent or received when the MS is engaged on a call (voice or data), or in idle mode. However, messages which overlap the boundary of such a call, or during a handover, may be lost, in which case they will be sent again.
The accounting between the SC and PLMN if applicable is for agreement between those parties.
The originator of a short message may notify the SC of an expiry time after which the message is no longer of value and may be deleted by the SC. During the validity period of the message, the SC shall try to deliver the message. After the expiry date the SC will take no further step to deliver the message, but its status may be kept by the SC to enable the originator to enquire the result. If the originator of the short message does not request any expiry time a standard value, e.g. 24 hours, is used.
The Service Centre may give a short message a priority status. This priority message will be attempted to be delivered irrespective of whether or not the MS has been identified as temporarily absent. Delivery of non-priority messages will not be attempted if the MS has been identified as temporarily absent.
If necessary, the originator may request the SC to perform specific operations on a previously submitted short message, such as provision/cancellation of a report or deletion of the short message.
The recipient of a short message will be informed by the message about the date and time it was submitted to the SC.
If the MS Message Store is full, the Message Store Overflow indicator is activated, and any further messages received will not be accepted. An appropriate specific non-acknowledgement message shall be returned. By help of an optional flow control mechanism further waiting short messages will be transmitted after the MS has memory available again. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 3 Reply path | The reply path facility is an enhancement to the point-to-point SMS. In the mobile originated case the mobile user will request his Service Centre to guarantee to forward a single reply to his message back to him (Reply Path).
In the mobile terminated case the recipient of the Short Message will get an indication by the service centre that a reply via this Service centre will be accepted on a subscriptionless basis. The recipient may then submit a reply to this SC (within a period of time defined by the SC operator), which is then forwarded to the submitter of the original message.
No subscription with the Service centre is needed by the replying user. The costs, if any, for the reply path are allocated to the originator. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 4 Definition of the cell broadcast short message | The cell broadcast is a Teleservice which enables an Information Provider to submit short messages for broadcasting to a specified area within the PLMN.
The cell broadcast service is characterized by the following aspects:
(i) No acknowledgement is sent from the MS.
(ii) The cell broadcast message is sent on control channels in a limited area, defined by the originator of the message, by agreement with the PLMN.
(iii) An identifier is associated with each message. This identifier is received by the MS and used by the short message function of the MS not to store broadcast messages which are not wanted or which have already been received.
(iv) Reception is only possible in idle mode.
(v) Generally, cell broadcast messages will be sent continuously, so that all such messages are sent in turn, and then repeated. The cycle time will need to be short enough for important messages to be received by travellers moving through a group of cells.
(vi) Cell broadcast messages are MT only. The origination of these messages is outside the scope of GSM.
(vii) The maximum length of each cell broadcast message will be 93 characters. GSM 03.41 describes a concatenation mechanism which allows up to 15 of these 93 character messages treated as segments of a longer message. These segments are then referred to as "pages".
(viii) Cell broadcast DRX mode is defined to improve the battery life for Mobile Stations. This feature is optional.
(ix) The cell broadcast channel allowing the transfer of broadcast messages to the MS is divided into the basic channel and the extended channel. The transfer and scheduling of the messages on both channels shall be done independently. The support of the extended cell broadcast channel by a MS is optional. The reading of the extended SMSCB broadcast channel by the MS shall have low priority, i.e. if necessary the reading of broadcast messages on the extended channel can be interrupted.
A.1.4 Alternate speech/facsimile G3
Teleservice 61, Alternate speech and facsimile group 3
1.
1.1 Type or user information
facsimile/speech
A
HLC
1.2 Layer 4 protocol functions
Procedures according to CCITT
T
1.3 Layer 5 protocol functions
recommendation T.30/T4.
T
1.4 Layer 6 protocol functions
R
1.5 Layer 7 protocol functions
I
2.
2.1
2.1.1 Information transfer capability
alternate speech/group 3 fax
B
LLC
2.1.2 Information transfer mode
circuit
U
Inform
2.1.3 Information transfer rate
up to 14400 bits/s
T
transfer
2.1.4 Structure
not applicable
E
2.1.5 Establishment of connection
demand (MO MT)
S
2.1.6 Communication configuration
point-to-point
2.1.7 Symmetry
bidirectional symmetry
2.2
2.2.1 Signalling access
I.440/450 (GSM 04.08)
Access
2.2.2 Information access
rate
fullrate
at MS
(GSM 02.01)
interface
2 wire analogue
2.3
2.3.1 Visible network type
PSTN
ISDN
GSM
Inter-
2.3.2 National/Internat. interworking
international/national
working
2.3.3 Interface of TE to terminating
2 wire, analogue/GSM MS
3.
3.1 Supplementary service provided
GSM 02.04
Gen
3.2 Quality of service
Comments:
1) This Teleservice allows the connection of CCITT group 3 fax apparatus (send and/or receive) to the mobile stations of a GSM PLMN. Facsimile connections may be established to/from group 3 apparatus in the PSTN, ISDN or GSM PLMN.
2) A high quality of service even under bad radio conditions and/or in connection to/from moving vehicles is required.
3) Both speech and fax portions of the call will use a full rate. The fax portion of the call may use multiple full rate channels.
4) Subscription for TS61 includes also subscription for TS62 (refer to TS GSM 02.01[2]). For this reason and in order to allow a user to change between ME supporting TS61 or TS62 both a network and a MS supporting TS61 shall also accept call set-ups for TS62. If a subscriber originates/receives a TS61 call but either the MS or the network do not support TS61 (but supports TS62), then TS61 shall be negotiated to TS62 in accordance to the rules specified in GSM 07.01 [10]. If the negotiation does not succeed, then the call shall be released.
A.1.5 Automatic facsimile G3
Teleservice 62, Alternate facsimile group 3
1.
1.1 Type or user information
facsimile
A
HLC
1.2 Layer 4 protocol functions
Procedures according to CCITT
T
1.3 Layer 5 protocol functions
recommendation T.30/T4.
T
1.4 Layer 6 protocol functions
R
1.5 Layer 7 protocol functions
I
2.
2.1
2.1.1 Information transfer capability
Facsimile group 3
B
LLC
2.1.2 Information transfer mode
circuit
U
Inform
2.1.3 Information transfer rate
up to 14400 bits/s
T
transfer
2.1.4 Structure
not applicable
E
2.1.5 Establishment of connection
demand (MO MT)
S
2.1.6 Communication configuration
point-to-point
2.1.7 Symmetry
bidirectional symmetry
2.2
2.2.1 Signalling access
I.440/450 (GSM 04.08)
Access
2.2.2 Information access
rate
fullrate
at MS
(GSM 02.01)
interface
2 wire, analogue
2.3
2.3.1 Visible network type
PSTN
ISDN
GSM PLMN
Inter-
2.3.2 National/Internat. interworking
international/national
working
2.3.3 Interface of TE to terminating
2 wire, analogue/GSM MS
3.
3.1 Supplementary service provided
GSM 02.04
Gen
3.2 Quality of service
Comments:
1) This teleservice supports a Facsimile Group 3 Autocalling/Autoanswering mode only.
2) This teleservice allows connection of CCITT group 3 fax apparatus to and from the mobile stations of a GSM PLMN. Facsimile connections may be established to and from group 3 apparatus in the PSTN, ISDN or GSM PLMN.
3) A high quality of service even under bad radio conditions and/or in connection to/from moving vehicles is required.
4) If a Network receives a call set-up for TS61 and if the subscriber in question has a subscription for TS62 only, then the network shall negotiate TS61 to TS62 in accordance to the rules specified in GSM 07.01 [10]. If the negotiation does not succeed, then the call shall be released. See also item 4) in the description of TS61.
5) This teleservice may use multiple full rate channels.
A.1.6 Voice Group Call Service
Teleservice 91, Voice Group Call Service
1.
1.1 Type or user Information
speech
A
HLC
1.2 Layer 4 protocol functions
-
T
1.3 Layer 5 protocol functions
-
T
1.4 Layer 6 protocol functions
-
R
1.5 Layer 7 protocol functions
-
I
2.
2.1
2.1.1 Information transfer capability
speech (digital representation)
B
LLC
2.1.2 Information transfer mode
circuit
U
Inform
2.1.3 Information transfer rate
not applicable
T
transfer
2.1.4 Structure
not applicable
E
2.1.5 Establishment of connection
demand MO MT
S
2.1.6 Communication configuration
multipoint
2.1.7 Symmetry
bidirectional symmetry
2.2
2.2.1 Signalling access
manual
Access
2.2.2 Information access
rate
full rate/half rate
at MS
(GSM 02.01)
interface
2.3
2.3.1 Visible network type
PSTN/ISDN/GSM-PLMN
Inter-
2.3.2 National/Internat. interworking
international/national
working
2.3.3 Interface of TE to terminating
2 wire, analogue
4 wire
S (B+B+D)
GSM/ME
3.
3.1 Supplementary service provided
GSM 02.68
Gen
3.2 Quality of service
Comments:
This service provides for speech conversation of a predefined group of service subscribers in half duplex mode on the radio link taking into account multiple mobile service subscribers involved in the VGCS call per cell. A detailed service description is given in GSM 02.68 [5].
A.1.7 Voice Broadcast Service
Teleservice 92, Voice Broadcast Service
1.
1.1 Type or user Information
speech
A
HLC
1.2 Layer 4 protocol functions
-
T
1.3 Layer 5 protocol functions
-
T
1.4 Layer 6 protocol functions
-
R
1.5 Layer 7 protocol functions
-
I
2.
2.1
2.1.1 Information transfer capability
speech (digital representation)
B
LLC
2.1.2 Information transfer mode
circuit
U
Inform
2.1.3 Information transfer rate
not applicable
T
transfer
2.1.4 Structure
not applicable
E
2.1.5 Establishment of connection
demand MO MT
S
2.1.6 Communication configuration
broadcast
2.1.7 Symmetry
unidirectional
2.2
2.2.1 Signalling access
manual
Access
2.2.2 Information access
rate
full rate/half rate
at MS
(GSM 02.01)
interface
2.3
2.3.1 Visible network type
PSTN/ISDN/GSM-PLMN
Inter-
2.3.2 National/Internat. interworking
international/national
working
2.3.3 Interface of TE to terminating
2 wire, analogue
4 wire
S (B+B+D)
GSM/ME
3.
3.1 Supplementary service provided
GSM 02.69
Gen
3.2 Quality of service
Comments:
This service provides for the distribution of speech, generated by a service subscriber, to all or a predefined group service subscribers located in this area. A detailed service description is given in GSM 02.69 [6].
Annex B (informative):
Change history
Change history
SMG No.
TDoc. No.
CR. No.
Section affected
New version
Subject/Comments
SMG#17
052/96
A001r1
6, AnnA
5.0.0
Addition of VGCS and VBS
SMG#19
395/96
A002
4.0
5.1.0
Introduction of second SMS-CB channel
5.1.1
UAP 58: 1996‑11‑18 to 1997‑03‑14
SMG#21
232/97
A003
A.1.4,
A.1.5
5.2.0
Changes needed to implement 14.4 kbps
SMG#22
305/97
A004
Comments in A.1.4 and A.1.5
5.3.0
HSCSD use of multiple TS for Fax & Data
SMG#27>
6.0.0
Specification upgrade to Release 1997 version 6.0.0
SMG#29
7.0.0
Specification upgrade to Release 1998 version 7.0.0
History
Document history
V7.0.0
August 1999
Publication |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 1 Scope | This TS defines Mobile Station (MS) features and to classifies them according to their type and whether they are mandatory or optional. The MS features detailed in this TS do not represent an exhaustive list. Those MS features which are subject to Type Approval are described in GSM 11.10 [13]. |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 1.1 Normative references | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies.
- A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
- For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y).
[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)".
[3] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services".
[4] GSM 02.11: "Digital cellular telecommunications system (Phase 2+); Service accessibility".
[5] GSM 02.16: "Digital cellular telecommunications system (Phase 2+); International Mobile station Equipment Identities (IMEI)".
[6] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber identity modules; Functional characteristics".
[7] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man-Machine Interface (MMI) of the Mobile Station (MS)".
[8] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress indications".
[9] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Stage 1 description of Unstructured Supplementary Service Data (USSD)".
[10] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification".
[11] GSM 03.14: "Digital cellular telecommunications system (Phase 2+); Support of Dual Tone Multi-Frequency signalling (DTMF) via the GSM system".
[12] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
[13] GSM 11.10: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) conformity specification".
[14] GSM 11.11: "Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface".
[15] GSM 02.43: "Digital cellular telecommunications system (Phase 2+); Support of Localised Service Area (SoLSA). Stage 1".
[16] GSM 02.34: "Digital cellular telecommunications system (Phase 2+); High Speed Circuit Switched Data (HSCSD). Stage 1".
[17] GSM 02.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS). Stage 1". |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 1.2 Definitions and abbreviations | For the purposes of this TS, the following definitions apply:
An MS feature is defined as a piece of equipment of function which directly relates to the operation of the MS. On the basis of this, three categories of features can be distinguished: basic, supplementary and additional features.
Basic MS features: A basic MS feature is directly related to the operation of basic telecommunication services (e.g. key-pad function).
Supplementary MS features: A supplementary MS feature is directly related to the operation of supplementary services (e.g. display of calling line number).
Additional MS features: An additional MS feature is a feature which is neither a basic nor a supplementary feature (e.g. abbreviated dialling).
Additional MS features and supplementary services may be used independently according to the choice of subscribers/users (e.g. barring of outgoing calls). Features not directly relevant to the use as a Mobile Station are permitted, provided they do not interfere with the performance of the MS (e.g. a clock).
Abbreviations used in this TS are listed in GSM 01.04 [1]. |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 2 Requirements for implementing MS features | MS features are qualified as mandatory or optional. Mandatory features have to be implemented as long as they are relevant to the MS type, and will be subject to Type Approval when applied according to GSM 11.10 [13]. Whether or not an optional feature is implemented is left to the manufacturers' discretion. The method of implementation of all MS features must be done in accordance with the appropriate GSM specifications. For all present and future MS features, manufacturers have the responsibility to ensure that the MS features will neither conflict with the air interface nor cause any interference to the network or any other MS or its own MS, and these requirements shall be recognized during the Type Approval process.
In the following tables 1, 2 and 3 the basic, supplementary and additional MS features are listed. Mandatory features are marked by "M". Optional features are marked by "0".
Additional MS features not listed in table 3 are permitted without the requirement for this table to be amended, provided that these new features do not affect the mandatory air interface requirements.
Unless otherwise stated for a particular feature, the feature supported by the Subscriber Identity Module (SIM) takes priority over the same feature supported by the Mobile Equipment (ME).
Table 1: Basic MS features
Name
Mandatory (M)
Optional (O)
1.1
Display of Called Number
M*
1.2
Indication of Call Progress Signals
M*
1.3
Country/PLMN Indication
M*
1.4
Country/PLMN Selection
M
1.5
Keypad
O
(note 1)
1.6
IMEI
M
1.7
Short Message
M
(note 4)
1.8
Short Message Overflow Indication
M
1.9
DTE/DCE Interface
O
1.10
ISDN "S" Interface
O
1.11
International Access Function ("+" key)
O
(note 1)
1.12
Service Indicator
M*
1.13
Autocalling restriction capabilities
(note 2)
1.14
Emergency Calls capabilities
M
(note 3)
1.15
Dual Tone Multi Frequency function (DTMF)
M
(note 5)
1.16
Subscription Identity Management
M
1.17
On/Off switch
O
1.18
Subaddress
O
1.19
Support of Encryption A5/1 and A5/2
M
1.20
Short Message Service Cell Broadcast
M
1.21
Short Message Service Cell Broadcast DRX
O
1.22
Service Provider Indication
O
1.23
Support of the extended SMS CB channel
O
1.24
Support of Additional Call Set-up MMI Procedures
O
1.25
1.26
1.27
1.28
1.29
1.30
1.31
Network Identity and Timezone
Ciphering Indicator
Network's indication of alerting in the MS
Network initiated Mobile Originated connection
Support of Localised Service Area
Enhanced circuit switched data (ECSD)
Enhanced general packet radio service (EGPRS)
O
M*
O
O
O
O
O
(NI Alert in MS)
Descriptions are given in annex B.
* Mandatory where a human interface is provided, i.e. may be in-appropriate for MS driven by external equipment.
NOTE 1: The physical means of entering the characters 0‑9, +, * and # may be keypad, voice input device, DTE or others, but it is mandatory that there shall be the means to enter this information.
NOTE 2: MTs with capabilities for Autocalling, or to which call initiating equipment can be connected via the "R" or "S" interface, shall restrict repeated call attempts according to the procedures described in annex A.
NOTE 3: Emergency calls shall be possible according to Teleservice 12 (see GSM 02.03 [2] and GSM 02.30 [7]). This feature is only required to be provided by ME supporting Telephony.
NOTE 4: Support of reception by the ME and storage of SMS MT in the SIM is mandatory, but its display is optional. Reception and storage of a message shall be indicated by the MS.
NOTE 5: The use of DTMF is only mandatory when the speech teleservice is being used or during the speech phase of alternate speech/data and alternate speech/facsimile teleservices.
Table 2: Supplementary MS features
Name
Mandatory (M)
Optional (O)
2.1
Control of Supplementary Services
(note 1)
NOTE 1: See annex B, subclause B.2.1.
Descriptions are given in annex B to GSM 02.07.
Table 3: Additional MS features
Name
Mandatory (M)
Optional (O)
3.1
Abbreviated Dialling
O
3.2
Fixed Number Dialling
O
3.3
Barring of Dialled Numbers
O
3.4
DTMF Control Digits Separator
O
3.5
Selection of Directory No in Messages
O
3.6
Last Numbers Dialled
O
3.7
ME-SIM lock
O
3.8
Service Dialling Numbers
O
Descriptions are given in the appendix to GSM 02.07.
Annex A (normative):
Automatic calling repeat call attempt restrictions
Call set up attempts referred to in this annex are assumed to be initiated from peripheral equipment or automatically from the MT itself.
A repeat call attempt may be made when a call attempt is unsuccessful for the reasons listed below (as defined in GSM 04.08 [12]).
These reasons are classified in three major categories:
1) "Busy destination":
Cause number 17 User busy.
2) "Unobtainable destination - temporary":
Cause number 18 No user responding; |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 19 User alerting, no answer; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 27 Destination out of order; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 34 No circuit/channel available; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 41 Temporary failure; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 42 Switching Equipment congestion; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 44 Requested circuit/channel not available; | 47 Resources unavailable, unspecified.
3) "Unobtainable destination - permanent/long term":
Cause number 1 Unassigned (unallocated) number; |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 3 No route to destination; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 22 Number changed; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 28 Invalid number format (uncompleted number); | 38 Network out of order.
NOTE 1: Optionally, it is allowed to implement cause number 27 in Category 3, instead of Category 2, as this is desirable already in Phase 1.
The table below describes a repeat call restriction pattern to any B number. This pattern defines a maximum number (n) of call repeat attempts; when this number n is reached, the associated B number shall be blacklisted by the MT until a manual re-set at the MT is performed in respect of that B number. When a repeat attempt to anyone B number fails, or is blacklisted, this does not prevent calls being made to other B numbers.
For the categories 1 and 2 above, n shall be 10; for category 3, n shall be 1.
call attempts
Minimum duration between Call attempt
Initial call attempt
-
1st repeat attempt
5 sec
2nd repeat attempt
1 min
3rd repeat attempt
1 min
4th repeat attempt
1 min
5th repeat attempt
3 min
.
.
nth repeat attempt
3 min
The number of B numbers that can be held in the blacklist is at the manufacturers discretion but there shall be at least 8. However, when the blacklist is full the MT shall prohibit further automatic call attempts to any one number until the blacklist is manually cleared at the MT in respect of one or more B numbers.
When automatic calling apparatus is connected to an MT1 or MT2, or where an MTO is capable of auto-calling, then the MT shall process the call requests in accordance with the sequence of repeat attempts defined above, i.e. requests for repeat attempts with less than the minimum allowed duration between them shall be rejected by the MT.
A successful call attempt to a number which has been subject to the call restrictions shown above (i.e. an unsuccessful call set up attempt has previously occurred) shall reset the "counter" for that number.
The "counter" for an unsuccessfully attempted B number shall be maintained in 24 hours or until the MT is switched off.
The automatic calling repeat call attempt restrictions apply to speech and data services.
NOTE 2: The restrictions only apply to unsuccessful Call Control activity, not to Radio Resource Management or to Mobility Management, so multiple attempts at radio channel access are not limited by this mechanism.
Annex B (normative):
Description of Mobile Station features
The section numbers refer to the items in tables 1, 2 and 3. The implementation (optional or mandatory) is shown in these tables.
B.1.1 Display of called number
This feature enables the caller to check before call setup whether the selected number is correct.
B.1.2 Indication of call progress signals
Indications shall be given such as tones, recorded messages or visual display based on signalling information returned from the PLMN. On data calls, this information may be signalled to the DTE.
Call progress indicators are described in GSM 02.40 [8].
B.1.3 Country/PLMN indication
The country/PLMN indicator shows in which GSM PLMN the MS is currently registered. This indicator is necessary so that the user knows when "roaming" is taking place and that the choice of PLMN (GSM 02.11 [4] clause 5) is correct. Both the country and PLMN will be indicated. When more than one visited GSM PLMN is available in a given area such information will be indicated.
NOTE: The indication is described in GSM 02.30 [7].
B.1.4 Country/PLMN selection
When more than one GSM PLMN is available in a given area, the procedures for selection of PLMN are in conformity with GSM 02.11 [4].
B.1.5 Keypad
A physical means of entering numbers, generally, though not necessarily, in accordance with the layout shown in figure B.1.
See also GSM 02.30 [7] (Man-Machine Interface).
Additional keys may provide the means to control the Mobile Station (e.g. to initiate and terminate calls).
1
2
3
4
5
6
7
8
9
*
0
#
Figure B.1
B.1.6 IMEI
IMEI = International Mobile Station Equipment Identity.
Each MS shall have a unique identity and shall transmit this on request from the PLMN. For details see GSM 02.16 [5] and GSM 03.03 [10]. The IMEI is incorporated in a module which is built within the MS and is physically secured. The implementation of each individual module shall be carried out by the manufacturer.
B.1.7 Short message indication and acknowledgement
This feature allows the delivery of short messages to a MS from a service centre. Such messages are submitted to the service centre by a telecommunications network user who can also request information of the status of the message by further interrogation of the service centre. The service centre then transmits the message to an active MS user.
The MS must therefore provide an indication to the user that a message has been received from the service centre and must also send an acknowledgement signal to the PLMN to show that this indication has been activated. The PLMN then returns this acknowledgement to the service centre.
The short message service teleservice is described in specification GSM 02.03 [2].
B.1.8 Short message overflow indication
An indication shall be given to the SM user of the short message service when an incoming message cannot be received due to insufficient available memory.
B.1.9 DTE/DCE interface
A standard connector for attachment of a DTE to the MS and use in conjunction with data services, as defined in the 07 series specifications.
B.1.10 ISDN "S" terminal interface
A standard connector for attachment of equipment to ISDN standard I.420.
B.1.11 International access function
Provision is made for a direct, standard method of gaining international access. For this purpose the MS may have a key whose primary or secondary function is marked "+". This is signalled over the air interface and would have the effect of generating the international access code in the network. It may be used directly when setting up a call, or entered into the memory for abbreviated dialling.
This feature is of benefit since the international access code varies between CEPT countries, which might cause confusion to a user, and prevent the effective use of abbreviated dialling when roaming internationally. Users may still place international calls conventionally, using the appropriate international access code.
B.1.12 Service Indicator (SI)
An indication is given to the user that there is adequate signal strength (as far as can be judged from the received signal) to allow a call to be made, and that the MS has successfully registered on the selected PLMN. This may be optionally combined with the Country/PLMN Indication (subclause B.1.3).
B.1.13 Autocalling restriction capabilities
See annex A.
B.1.14 Emergency Calls capabilities
See clause 2.
B.1.15 Dual Tone Multi Frequency (DTMF)
The MS shall be capable to initiate DTMF in accordance with specifications GSM 02.03 [2] and GSM 03.14 [11]. Optionally, the MS may provide a suppress function which allows the user to switch off the DTMF function.
B.1.16 Subscription identity management
The IMSI is contained in a SIM, "Subscriber Identity Module". If the SIM is removable by the user, its removal detaches the MS, causing a call in progress to be terminated, and preventing the initiation of further calls (except emergency calls - see GSM 02.30 [7]).
The SIM may be in one of two physical sizes, both of which have identical electrical characteristics. The larger "ID‑1 SIM" is generally entered into the ME by the user. The card has a polarization mark (see annex C). The ME shall have an indication of how to obtain correct polarization of the card. The smaller "plug-in SIM" is generally mounted internally within the ME.
B.1.17 On/Off switch
The MS may be provided with a means of switching its power supply on and off. Switch-off shall be "soft", so that on activation, the MS completes the following housekeeping functions: termination of a current call, detach (where applicable) and storing required data in the SIM (see GSM 02.17 [6]) before actually switching off. As far as possible, this procedure should also apply on power failure (e.g. remote switch-off or low battery).
B.1.18 Sub-Address
This feature allows the mobile to append and/or receive a sub-address to a Directory Number, for use in call set-up, and in those supplementary services that use a Directory Number.
B.1.19 Support of encryption A5/1 and A5/2
Provision is made for support of up to 7 different algorithms, and the support of no encryption. It is mandatory for A5/1, A5/2 and non encrypted mode to be implemented on mobile stations. Other algorithms are optional.
B.1.20 Short Message Service Cell Broadcast
The Short Message Service Cell Broadcast enables the mobile station to receive short messages from a message handling system.
The short message service cell broadcast teleservice is described in specification GSM 02.03 [2].
B.1.21 Short Message Service Cell Broadcast DRX
This feature enables a mobile station to save on battery utilization, by allowing the mobile station to not listen during the broadcast of messages the subscriber is not interested in.
B.1.22 Service Provider Indication
When available and the MS is in idle mode, the MS shall indicate the Service Provider name. The Service Provider name is stored in the SIM {(max. 16 characters, including spaces)}. The SIM will indicate two options: (1) indication of Service Provider name in parallel to the indication of the PLMN the MS is registered-to; (2) indication of the Service Provider name alternatively to the indication of the PLMN the MS is registered-to. When roaming, the Service Provider name shall only be indicated in parallel to the PLMN the MS is registered-to. If the MS is unable to display the full name of the Service Provider the name is cut from the tail end. The storage of Service Provider name and choice of option shall be under control of the network operator.
B.1.23 Support of the extended Short message cell broadcast channel
This feature allows a mobile station by supporting of the extended Short message cell broadcast channel to enhance the capacity of the service. The support of the extended channel has low priority, i.e. the MS can interrupt the reading of this channel if idle mode procedures have to be executed.
B.1.24 Support of Additional Call Set-up MMI Procedures
This feature allows the user, through direct MS interaction, or the service provider of the user, to specify the user’s preferred emergency call MMI (e.g. 911 for US citizens or 999 for UK citizens) for use in any (i.e. home or visited) PLMN. This would be stored in the SIM and the ME would read this and use any entry of these digits to set up an emergency call. It may be possible to store more than one instance of this field.
B.1.25 Network Identity and Timezone
The feature provides the means for serving PLMNs to transfer current identity, universal time and the local timezone to mobile stations, and for the mobile stations to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the ME or have changed their name since the ME was sold. Additionally time and timezone information can be utilized by MEs as desired.
The network name time and timezone information will normally be transferred from the network to the ME:
1) Upon registering on the network.
2) When the MS geographically relocates to a different Local Time Zone.
3) When the network changes its Local Time Zone, e.g. between summer and winter time.
4) When the network changes its identity.
5) At any time during a signalling connection with Mobile Station.
Further details of this feature are described in GSM 02.42.
B.1.26 Ciphering Indicator
The ciphering indicator feature allows the ME to detect that ciphering is not switched on and to indicate this to the user, as defined in GSM 02.09.
The ciphering indicator feature may be disabled by the home network operator setting data in the "administrative data" field (EFAD) in the SIM, as defined in GSM 11.11.
If this feature is not disabled by the SIM, then whenever a connection is in place, which is, or becomes unenciphered, an indication shall be given to the user.
Ciphering itself is unaffected by this feature, and the user can choose how to proceed.
B.1.27 Network's indication of alerting in the MS
This feature provides the means for serving PLMNs to transfer to a Mobile Station an indication that may be used by the MS to alert the user in a specific manner in the following cases:
- mobile terminating call
- network initiated USSD
- network initiated Mobile Originated (MO) connection, if the ME supports the "network initiated MO connection " feature.
8 different indications are defined, whether the mobile terminating traffic is a call or USSD or related to the network initiated MO connection procedure. These indications are sent by the network and received by the MS :
- Three of these indications are used as levels, reflecting some kind of urgency : level 0 indicates that the MS shall not alert the user for USSD and remain silent in the case of call, level 2 shall be considered by the MS as more important than level 1 for the purpose of alerting the user.
- The five other indications are used as categories, identifying different types of terminating traffic. The MS shall inform the user in a specific manner for each of these five categories. Nevertheless, the possible forms of the alert (different ringing tones, displayed text, graphical symbols...) is still up to the mobile manufacturer (some forms of alerts can be simultaneously used, e.g. ringing tones and text on the display).
The management of the feature by the MS requires for the handling of categories that :
- the SIM stores for each category an informative text (maximum 25 characters per category) describing the type of terminating traffic associated with the category. This information could be used by the ME when alerting the user (display on the screen). It is necessary for the network operator to be able to change the meaning of each category.
- The user has the ability to set up his/her own association between the type of terminating traffic (identified by each category) and the different types of alert provided by the ME. To help the user in this choice, the ME uses the informative text associated with each category (as stored in the SIM). The ME should keep this association when switched off.
Default settings should also be defined in the ME for the following cases :
- when the ME receives a call, USSD or a request for a network initiated MO connection with no alerting indication,
- when the ME receives a call, USSD or a request for a network initiated MO connection with a category of alerting not defined in the SIM.
These default settings should be separated per type of mobile terminated traffic received (call, USSD or request for a network initiated MO connection).
An ME supporting the feature shall act according to the following points in case of mobile terminating traffic :
- when a mobile terminating traffic is received without any indication (level or category), the ME shall act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic).
- if a level is indicated, the ME shall use an alert enabling the user to differentiate between the three levels.
- if a category is indicated, then :
- if the SIM used in the ME does not store any information on that feature, the ME shall ignore the category received with any mobile terminating traffic and act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic).
- if the category is not defined in the SIM, the ME shall act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic).
- if the category is defined in the SIM, the ME shall use the alert associated with this category. In addition, it would be very useful for the user to be notified of the informative text associated with this category (e.g on the display).
Some interactions between this feature and other services related to alerting are described below :
- the call waiting service has priority on this feature, i.e. the call waiting tone will be played and not the alert derived by this feature. If possible, two different indications should be given to the user (e.g. the call waiting tone and a text on the display indicating call waiting, and in addition a text relative to the type of the new call received).
- the presentation of the calling line identity takes priority on this feature, if it is not possible to display this information and another information related to this feature.
- In case of interaction between this feature and ME specific features to alert the user (e.g. whole silent mode), the user should still be able to differentiate between the different levels or different types of terminating traffic, even if the alert itself may be changed.
B.1.28 Network initiated Mobile Originated (MO) connection
The "Network Initiated Mobile Originated connection" feature allows the network to ask the mobile station to establish a mobile originated connection. The serving PLMN provides the mobile station with the necessary information which is used by the mobile station to establish the connection.
Currently only the network initiated mobile originated call feature is specified. It is mandatory for CCBS ME and is used in the case of a CCBS recall.
B.1.29 Support of Localised Service Area (SoLSA)
The localised service area concept shall give the operator the basis to offer subscribers different services (e.g. tariffs or access rights) depending on the (cell based) location of the subscriber. For SoLSA features see GSM 02.43 [15])
B.1.30 ECSD
The same date rates as for HSCSD are supported, but due to the 8PSK modulation scheme this can be achieved by using fewer time slots, as described in GSM 02.34 [16].
B.1.31 EGPRS
The same set of services as for GPRS is supported but higher data rates are possible due to the 8PSK modulation scheme, as described in GSM 02.60 [17]. The 8PSK modulation scheme can be supported by the MS either only in down link direction or both in down and up link directions.
B.2.1 Support of supplementary services
Support of Call Barring and Call Forwarding Supplementary Services is mandatory. Support of other Supplementary Services is optional. Support of Unstructured SS Data, as described in GSM 02.90 [9] and GSM 02.30 [7], is optional.
If defined for a given Supplementary Service, the Functional Signalling shall be used, i.e. Unstructured SS Data signalling shall not be used. If an MS does not support the functional signalling for a given SS, the MS cannot declare that it supports that SS.
B.3.1 Abbreviated dialling
The directory number or part of it is stored in the mobile station together with the abbreviated address. After retrieval the directory number may appear on the display.
Abbreviated dialling numbers stored in the ME or SIM may contain wild characters.
It is permitted to extend the number by adding digits (by means of the keypad, R interface or a second abbreviated, or fixed dialling, number (and/or subaddress)) when setting up a call.
If wild characters are used to indicate missing digits, each wild character shall be replaced for network access or supplementary service operation, by a single digit entered at the keypad. The completed directory number is transmitted on the radio path.
B.3.2 Fixed number dialling
This feature provides a mechanism so that by the use of an electronic lock it is possible to place a bar on calling any numbers other than those pre-programmed in the SIM.
Under control of PIN 2, "Fixed Dialling Mode" may be enabled or disabled. The mode selected is stored in the SIM.
Fixed Dialling Numbers (FDNs) are stored in the SIM in the Fixed Dialling Number field. FDN entries may take the function of an Abbreviated Dialling Number/Supplementary Service Control (ADN/SSC), Overflow and/or sub-address. Fixed Dialling Numbers stored in the SIM may contain wild card characters.
The Fixed Dialling feature is optional, however when Fixed Dialling Mode is enabled, an ME supporting the feature shall;
- Prevent non FDN entries from being called.
- Only allow modification, addition or deletion of Fixed Number Dialling entries under control of PIN2.
- Allow calls to numbers stored as FDN entries.
- Support the reading and substitution of wildcards in any position of an FDN entry, via the ME MMI.
- Allow the user to replace each wildcard of an FDN entry by a single digit, on a per call basis without using PIN2. The digit replacing the wildcard may be used for network access or supplementary service operation.
- Only allow Supplementary Service (SS) Control (in Dedicated or Idle mode) if the SS control string is stored as an FDN entry.
- Allow the extension of an FDN entry by adding digits to the Fixed Dialling number on a per call basis.
- Allow the emergency number (112) to be called, even if it is not an FDN entry.
- Allow normal access to ADN fields (i.e. allow ADN entries to be modified, added or deleted) and the keyboard.
- Allow use of ADNs subject to the FDN filter.
When FDN is disabled, an ME supporting FDN shall;
- Allow FDN entries to be read as though they were normal ADN entries.
- Only allow modification, addition or deletion of Fixed Number Dialling entries under control of PIN2.
- Allow normal access to ADN fields and the keyboard.
If the ME does not support FDN, the MS shall not allow the making or receiving of calls when Fixed Dialling is enabled. However, emergency calls (112 and other user defined emergency numbers) shall still be possible.
NOTE: Wildcards are stored on the SIM. The wildcard coding is given in GSM 11.11.
B.3.3 Barring of Dialled Numbers
This feature provides a mechanism so that by the use of an electronic lock it is possible to place a bar on calling any numbers belonging to a pre-programmed list of numbers in the SIM.
Barred Dialling Numbers stored in the SIM may contain wild characters.
Under control of PIN2, "Barred Dialling Mode" may be enabled or disabled. The selected mode is stored in the SIM.
Under PIN2 control, it shall be possible to add, modify or delete a particular "Barred Dialling Number" (BDN) and to allocate or modify its associated comparison method(s). This BDN may have the function of an abbreviated dialling number / supplementary service control (ADN/SSC), overflow and/or sub-address.
When BDN is inactive, no special controls are specified, and the barred dialling numbers may be read (though not modified or deleted, except under PIN2 control) as if they were normal abbreviated dialling numbers. Access to keyboard and normal abbreviated dialling numbers (including sub-address) is also permitted.
When Barring of Dialled Numbers is active:
- Considering a number dialled by the user, if it exists a BDN for which there is a successful comparison (see below) between that BDN and the dialled number, then the ME shall prevent the call attempt to that number. If there is no BDN to fulfil those conditions, the call attempt is allowed by the ME.
With each BDN is associated one (or a combination of) comparison method(s) used between that BDN and the number dialled by the user. At least three different comparison methods are possible:
- The comparison is made from the first digit of that BDN, from the first digit of the dialled number and for a number of digits corresponding to the length of the BDN.
- The comparison is made from the first digit of that BDN, from any digit of the dialled number and for a number of digits corresponding to the length of the BDN.
- The comparison is made backwards from the last digit of that BDN, from the last digit of the dialled number and for a number of digits corresponding to the length of the BDN.
- If a BDN stored in the SIM contains one or more wild characters in any position, each wild character shall be replaced by any single digit when the comparison between that BDN and the dialled number is performed.
- If a BDN contains a sub-address, and the same number without any sub-address or with that sub‑address is dialled, the ME shall prevent the call attempt to that number.
- Numbers specified as "barred" may only be modified under PIN2 control.
- If the ME does not support barring of dialled numbers, the MS shall not allow the making or receiving calls. However, this feature does not affect the ability to make emergency calls.
If "Fixed Number Dialling" and "Barring of Dialled Numbers" are simultaneously active, the dialled number shall be checked against the two features before the ME allows the call attempt. In that case, a dialled number will only be allowed by the ME if it is in the FDN list and if the comparison between that number and any number from the BDN list is not successful.
The MS may support other selective barrings, e.g. applying to individual services (e.g. telephony, data transmission) or individual call types (e.g. long distance, international calls).
B.3.4 DTMF control digits separator
Provision has been made to enter DTMF digits with a telephone number, and upon the called party answering the ME shall send the DTMF digits automatically to the network after a delay of 3 seconds (± 20 %). The digits shall be sent according to the procedures and timing specified on GSM 04.08 [12].
The first occurrence of the "DTMF Control Digits Separator" shall be used by the ME to distinguish between the addressing digits (i.e. the phone number) and the DTMF digits. Upon subsequent occurrences of the separator, the ME shall pause again for 3 seconds (± 20 %) before sending any further DTMF digits.
To enable the separator to be stored in the address field of an Abbreviated Dialling Number record in the SIM, the separator shall be coded as defined in GSM 11.11 [14]. The telephone number shall always precede the DTMF digits when stored in the SIM.
The way in which the separator is entered and display in the ME, is left to the individual manufacturer's MMI.
MEs which do not support this feature and encounter this separator in an ADN record of the SIM will treat the character as "corrupt data" and act accordingly.
B.3.5 Selection of directory number in messages
The Short Message (Point to Point MT or MO, or Cell Broadcast), Network Initiated USSD or Network Response to Mobile Originated USSD message strings may be used to convey a Directory Number which the user may wish to call. This can be indicated by enclosing the directory number in a pair of inverted commas (" ").
If the displayed message contains these characters enclosing a directory number, a call can be set up by user action. Normal (unspecified) or International format (using + symbol) may be used.
The message may contain more than one directory number, in which case it is for the user to select the one required.
B.3.6 Last Numbers Dialled (LND)
The mobile station may store the Last "N" Numbers dialled in the SIM and/or the ME. "N" may take the value up to 10 in the SIM. It may be any value in the ME. The method of presentation of these to the user for setting up a call is the responsibility of the MS but if these numbers are stored in both the SIM and the ME, those from the SIM shall take precedence. The security for handling this is defined in GSM 02.17 [6].
B.3.7 ME-SIM lock
This feature controls the ability of the MS to access networks according to whether the ME matches the SIM based on one or more of the following criteria:
- Subscriber identity (IMSI).
- Group identifier level 1 (e.g. Service Provider identity).
- Group identifier level 2.
- PLMN identity (MCC+MNC).
One or more of these criteria may be activated. When any are activated, the ME shall be locked to the SIM such that the MS shall only make network registration attempts when there exists a bit-exact match between corresponding data elements on the ME and SIM for each of the activated criteria.
Secure means shall be provided to prevent unauthorized changes to the lock status or the contents of any of the data fields above on the SIM or ME.
B.3.8 Service Dialling Numbers
The Service Dialling Numbers feature allows for the storage of numbers related to services offered by the network operator/service provider in the SIM (e.g. customer care). The user can use these telephone numbers to make outgoing calls, but the access for updating of the numbers shall be under the control of the operator.
NOTE: No MMI is envisaged to be specified for these numbers and it is left to mobile manufacturer implementations.
Annex C (normative):
GSM-MoU ID1 SIM layout
NOTE: The symbol may be printed in the same location on the rear as well as the front face.
Annex D (informative):
Change history
Change history
SMG No.
TDoc. No.
CR. No.
Subclause affected
New version
Subject/Comments
SMG#22
304/97
A011
B.3.2
5.3.0
FDN Spec addresses wild card implementation
SMG#22
507/97
A014
Table 1
(1.26)
Subclause B.1.26
5.3.0
Introduction of mandatory ciphering indication
SMG#24
971/97
A015
Table 1 "basic MS features" and a new section B1.26 is introduced.
5.4.0
R97
$(NI Alert in MS)$: Introduction of the new work item "network's indication of alerting in the MS". With this feature, the user will be able to discriminate between different types of mobile terminated traffic.
SMG#24
972/97
A016
B1.25 was corrected
5.4.0
R96
Alignment of NITZ - Network name, time and timezone information will be transferred from the network to the ME: At any time during a signalling connection with mobile station.
SMG#25
6.0.0
Creation of version 6.0.0 as part of GSM release 1997
SMG#26
98-0317
A017
Introduction, 2, B.1.27, B.1.28 (new)
Verify with Anouch Chichmanian, not all referenced sections are there !!
6.1.0
R97
A new mechanism is introduced in Release 97 to allow the network to make the MS initiate a call. As an example, this mechanism is used for CCBS recall. A new MS feature "network initiated MO connection" is therefore added in GMS 02.07 to cover this case and to anticipate future applicability, e.g. to SMS or supplementary services.
SMG#26
98-0317
A018
B.1.27
6.1.0
R97
Extension of the network's indication of alerting in the MS to the new mechanism "network initiated Mobile Originated connection" defined in release 97.
SMG#27
98-0548
A019
1.1, 2, B.1.29 (new)
7.0.0
R98
Addition of the SoLSA feature
SMG#29
P-99-383
A020
2 (Table1), Annex B
8.0.0
R99
The new modulation scheme (8PSk) used in EDGE leads to the definition of new features for the Mobile Stations.
History
Document history
V6.1.0
July 1998
Publication
V7.0.0
October 1998
Unpublished
V8.0.0
July 1999
Unpublished |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 1 Scope | The present document defines requirements for call progress and related information to be provided to users of the GSM system. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man‑Machine Interface (MMI) of the Mobile Station (MS)".
[3] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
[4] CEPT Recommendation T/CS 20-15: "Tones and announcements".
[5] CEPT Recommendation T/S F23: "Relative aux définitions et caractéristiques audibles des tonalités et des annonces parlées".
[6] ANSI T1.607: “Digital Subscriber Signalling Sytem No.1-Layer 3 Signalling Specification for Circuit Switched Bearer Service”. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 1.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 1.3 General | There are aspects of the Man Machine Interface (MMI) of the GSM Network which relate to users, but which are not covered by GSM 02.30, which deals specifically with the MMI of the Mobile Station (MS). The present TS covers the means by which mobile users, and callers to a GSM network, will be given information regarding progress of their calls.
Indications of call progress, such as ringing, engaged, unobtainable, and no radio channel, may in principle be verbal message, tones, displayed text or graphical symbols. Which combination of these applies may depend on the message, the MS and selection by the user or PLMN operator. However, verbal announcements will generally be reserved for situations which are peculiar to a mobile network, where users may be unfamiliar with any tone chosen to indicate conditions such as "call diversion" or "subscriber not available".
It may also be desirable to add comfort indications (e.g. tones, noise, music, clicks) while a call is being connected, since silence may cause an unfamiliar user to believe that nothing is happening.
Generally, on data calls, and on the data part of alternate speech/data or speech-followed-by-data calls, PLMN generated network tones and announcements should be muted. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2 Supervisory tones | |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.1 General | Supervisory Tones, indicating primarily ringing, engaged and unobtainable numbers, may be generated by both the PLMN and PSTN.
Except for ring tone, all tones indicating call progress to a MS user shall be generated in the MS, on the basis of signals from the network where available, and are according to the standard defined in the present document.
Tones sent to a caller to a MS will be generated in the network, generally local to the caller, and will be to the standard of his local exchange, except for mobile to mobile calls, where the tones will be generated in the calling MS. For mobile terminated calls, the ring tone will be generated in the called MSC (except OACSU). |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.2 Method | In the interests of early release of the traffic channel on failure to succeed in setting up a (mobile originated) call, where possible supervisory tones should be indicated over signalling channels. The MS will then generate the required tones. However, if the network generates an in-band announcement this will be indicated to the MS. In this case the MS shall connect the user to the announcement until instructed to release the call, either by the user or by the network. An alternate procedure may apply for MS able to generate appropriate announcements internally (see clause 3).
The ring tone will be sent over the traffic channel, since this channel must be available for traffic immediately it is answered (exception: Off Air Call Set Up). The Ring Tone is therefore generated by the PLMN or PSTN supporting the called phone.
On failed mobile terminated call attempts, the called MSC will either signal to the caller, if this is possible, or else will generate the required supervisory tones.
"Alert" is not a supervisory tone. The indication is signalled, and the MS may generate any form of indication to the user that the MS is being called. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.3 Standard tones | MS generated tones will be generally in accordance with CEPT (GSM 900 and DCS 1800), or ANSI T1.607 (PCS 1900 for NA) recommendations, where appropriate, and are listed in table 1. Any network originated tones will be according to PLMN or PSTN choice. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.4 Applicability | This method will apply in all cases where signalling is capable of indicating the supervisory tone required. However, for connection to certain fixed networks where this signalling is not possible, fixed network tones will be carried over the traffic channel.
Mobile Stations may employ any suitable technique to indicate supervisory information. However, if tones are employed, they shall be in accordance with the present document. The use of these tones in the MSC is preferred.
NOTE 1: The tones and/or announcement to the calling party should not be provided if the Information transfer capability is set to UDI.
NOTE 2: For a call with information transfer capability set to 3.1 kHz, the use of tones and/or announcement may cause the expiry of an awaiting answer timer in a modem or fax machine. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.5 Point of introduction | Introduction E1. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.6 Comfort tones | If desired by the PLMN operator, the network may optionally introduce "comfort tones" while the call is being connected, during what would otherwise be silence. This would be overridden by indication of a supervisory tone, an announcement or by traffic. PLMNs may offer this feature optionally to incoming or outgoing callers.
The "comfort tones" may take the form of tones, clicks, noise, music or any other suitable form, provided that they cannot be confused with other indications that might be expected.
This feature is intended to indicate to the user that his call is progressing, to prevent him terminating the call prematurely.
Table 1: Supervisory tones in GSM MSs
Tone
Frequency
Tolerance
Type
GSM 900/
DCS 1800
PCS 1900
for NA
GSM 900 /
DCS 1800
PCS 1900
for NA
1
Dial tone (optional)
425Hz
350Hz added to 440Hz
15Hz
Continuous
Continuous
2 *
Subscriber Busy (Called Number)
425Hz
480Hz added to 620Hz
15Hz
Tone on 500ms
Silence 500ms
Tone on 500ms
Silence 500ms
3 *
Congestion
425Hz
480Hz added to 620Hz
15Hz
Tone on 200ms
Silence 200ms
Tone on 250ms
Silence 250ms
4
Radio Path
Acknowledgement (Mobile
Originated only) (optional)
425Hz
425Hz
15Hz
Single tone 200ms
Single tone 200ms
5
{Radio Path Not Available
{Call Dropped – Mobile originated only
425Hz
425Hz
15Hz
200ms} On/off 200ms} for 3
burst
200ms} On/off 200ms} for 3
burst
6 *
Error/Special Information}
Number Unobtainable }
Authentication Failure }
950Hz
1400Hz
1800Hz
950Hz
1400Hz
1800Hz
50Hz
50Hz
50Hz
{Triple Tone
{Tones on 330ms
{Silence 1.0s
{Triple Tone
{Tones on 330ms
{Silence 1.0s
7
Call Waiting Tone
425 Hz (tolerance 15Hz), on for 200ms, off for 600ms on for 200ms, off for 3s, on for 200ms, off for 600ms on for 200ms. This tone is superimposed on the audio traffic received by the called user. Alternate tones are acceptable but not preferred.
440 Hz, on for 300 ms, 9.7s off followed by (440 Hz, on for 100 ms off for 100 ms, on for 100 ms, 9.7s off and repeated as necessary) This tone is superimposed on the audio traffic received by the called user.
Definition of these and other tones, together with advice on announcements, may be found in CEPT T/CS 20-15 and in T/SF
23.
* The duration of these tones is an implementation option. However, in each case, the MS should be returned immediately to the
idle state, and will be able to originate/receive calls, which will override these tones.
Ringing Tone (Alternative
national options permitted)
425Hz
440Hz added to 480Hz
15Hz
Tone on 1s Silence 4s
Tone on 2s
Silence 4s
For application of Call Control Cause Information Elements to these tones, see Annex A, GSM 02.40. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 3 Recorded announcements | In present networks, both fixed and cellular, the language of recorded announcements and displayed information is invariably that of the country of origin. However, this is generally undesirable in a multi-lingual environment such as is encountered on a pan-European network with international roaming. It is therefore probably desirable to minimise the number of such announcements.
Advanced MSs may be designed which have the ability to generate announcements in the form desired by the user, e.g. in the language preferred by the user. In this case, it becomes necessary to block any verbal announcements sent from the network towards the MS, to avoid clashes with those generated by the MS. The MS may be allowed to block in-band announcements in case appropriate announcements according to the Cause Information Elements (annex A) can be generated. The default setting of the MS shall be "non blocking", which could be set by MMI command to "blocking".
Announcements generated by the PLMN and sent to callers to that PLMN will generally be in the language of the PLMN. However, on some fixed networks it will be possible for the message to be signalled back to the caller's local exchange, which will then generate the announcement in its local language.
Annex A (normative):
Application of call control cause information elements to supervisory tones
The Cause Information Elements are listed and defined in GSM 04.08. This annex lists these elements and indicates which supervisory tone should be generated in response. It should be noted that some conditions (e.g. radio path not available, dropped call) may be deduced by the MS, rather than signalled explicitly over the air interface. All causes not listed below should result in the generation of tone 6. In case of multiple calls a tone should only be generated if it does not disturb an ongoing active call. "-" indicates no tone required.
Cause Tone
CC (see table 1)
16 Normal Clearing 1
17 User Busy 2
22 Number Changed -
30 Response to STATUS ENQUIRY -
31 Normal, unspecified -
34 No circuit/channel available 3
41 Temporary Failure 3
42 Switching Equipment Congestion 3
44 Requested circuit/channel not available 3
49 Quality of Service Unavailable 3
58 Bearer Capability not available 3
Annex B (informative):
Change history
Change history
SMG No.
TDoc. No.
CR. No.
Subclause affected
New version
Subject/Comments
Annex B First introduced at SMG#27
21
A001
Annex A
Update and approve Annex A
SMG#27
98-0549
A002
0.1 Normative references
2.3Standard tones
2.6 Comfort tones
Procedure for call progress indications.
Harmonization between GSM 02.40 version 5.0.0 and J-STD-007 Volume 7.
History
Document history
V6.0.0
April 1999
Publication
V7.0.1
July 1999
Publication |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 1 Scope | The present document defines network functions which are necessary to support services and facilities provided by PLMNs. A summary of the network functions is given in Table 1, where also an indication is given whether the network must support the function. The table also indicates whether or not a function requires internetworking signalling between PLMNs (i.e. use of Mobile Application Part, Technical Specification GSM 09.02).
All functions require signalling on the radio path as specified in Technical Specification GSM 04.08. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary service".
[3] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects".
[4] GSM 02.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description - Stage 1".
[5] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification".
[6] GSM 03.07: "Digital cellular telecommunications system (Phase 2+); Restoration procedures".
[7] GSM 03.08: "Digital cellular telecommunications system (Phase 2+); Organisation of subscriber data".
[8] GSM 03.12: "Digital cellular telecommunications system (Phase 2+); Location registration procedures".
[9] GSM 03.13: "Digital cellular telecommunications system (Phase 2+); Discontinuous Reception (DRX) in the GSM system".
[10] GSM 03.14: "Digital cellular telecommunications system (Phase 2+); Support of Dual Tone Multi-Frequency signalling (DTMF) via the GSM system".
[11] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions".
[12] GSM 03.22: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode".
[13] GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point to Point (PP)".
[14] GSM 03.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description; Stage 2".
[15] GSM 03.64: "Digital cellular telecommunications system (Phase 2+); Overall Description of the General Packet Radio Service (GPRS) Radio Interface; Stage 2".
[16] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2".
[17] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2".
[18] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2".
[19] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 2".
[20] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2".
[21] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2".
[22] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2".
[23] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
[24] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control".
[25] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification".
[26] GSM 12.00: "Digital cellular telecommunications system (Phase 2+); Objectives and structure of Network Management (NM)".
[27] GSM 12.01: "Digital cellular telecommunications system (Phase 2+); Common aspects of GSM Network Management (NM)".
[28] GSM 12.07: "Digital cellular telecommunications system (Phase 2+); Operations and performance management".
[29] GSM 12.02: "Digital cellular telecommunications system (Phase 2+); Subscriber, Mobile Equipment (ME) and services data administration".
[30] GSM 12.03: "Digital cellular telecommunications system (Phase 2+); Security management".
[31] GSM 12.04: "Digital cellular telecommunications system (Phase 2+); Performance data measurements".
[32] GSM 12.05: "Digital cellular telecommunications system (Phase 2+); Subscriber related event and call data".
[33] GSM 12.06: "Digital cellular telecommunications system (Phase 2+); GSM Network change control".
[34] GSM 12.10: "Digital cellular telecommunications system (Phase 2+); Maintenance provisions for operational integrity of Mobile Stations (MS)".
[35] GSM 12.11: "Digital cellular telecommunications system (Phase 2+); Maintenance of the Base Station System (BSS)".
[36] GSM 12.13: "Digital cellular telecommunications system (Phase 2+); Maintenance of the Mobile-services Switching Centre (MSC)".
[37] GSM 12.14: "Digital cellular telecommunications system (Phase 2+); Maintenance of location registers".
[38] GSM 12.20: "Digital cellular telecommunications system (Phase 2+); Network Management (NM) procedures and messages".
[39] GSM 12.21: "Digital cellular telecommunications system (Phase 2+); Network Management (NM) procedures and message on the A-bis interface".
[40] GSM 12.22: "Digital cellular telecommunications system (Phase 2+); Interworking of GSM Network Management (NM) procedures and messages at the Base Station Controller (BSC)". |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 1.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2 Network functions for basic service provision | |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1 Call handling | This set of functions enables the establishment of communications between a mobile subscriber and another network subscriber in one of the following types of network PSTN, ISDN, PSPDN, CSPDN and other PLMNs. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.1 Call from a mobile subscriber registered in VLR | This is the normal case where the call is routed according to the dialled number. After the call, the MSC will send the charging information to the HLR, a billing entity and/or store the charging data on tapes or discs as described in Technical Specification GSM 12.05. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.2 Call from a mobile subscriber not registered in VLR | When the VLR receives a request for call set-up parameters from an MSC for an MS originating call, where the MS is not registered in the VLR, the VLR shall initiate a location updating procedure towards the HLR and in response parameters are given concerning category, services and restrictions. The call is then set up as in 2.1.1. This case only happens when a VLR or an MS failure has occurred. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.3 Call to a mobile subscriber | The call is routed (re-routed or forwarded) according to location data obtained from the HLR to the actual MSC and the MS is paged over the standardised radio interface.
For MSs in mode of operation A and B the paging may be performed via SGSN. This optional network function is further described in the Technical Specification GSM 03.60.
Table 1: Overview of network functions
Class of Network
Network Function
Network
Interworking
Function (NF)
Support
with MAP
NF for basic
Call Handling (Note 3)
M
X
service provision
Packet Handling (Note 4)
M
X
Subscriber Authentication
M
X
Emergency calls (Note 3)
M
-
Supplementary Services
M
X
Voice group services (Note 3)
O
X
Short Message Service (SMS)
M
X
Signalling information element confidentiality
M
X
NF for
Location registration
M
X
supporting:
Handover (Note 3)
- in the same BSS
M
-
- in the same MSC
M
-
- in the same PLMN
M
X
Call re-establishment (Note 3)
M
-
Additional NF
Queueing
O
-
for
call handling
OACSU (Note 3)
O
-
Security related services
M
X
Discontinuous reception
M
-
Discontinuous Transmission
M/O
-
Note 2
DTMF (Note 3)
M
-
Network
management
M
X
oriented NF
(Note 1)
NOTE 1: The function will not be fully specified by GSM (national specifications will complement).
NOTE 2: Only the receiver requirements are mandatory, the transmitter requirements support are optional.
NOTE 3: Only applicable for circuit switched services
NOTE 4: Only applicable for packet switched services |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.4 Call handling functions in HLR | The HLR should also support control functions for handling of supplementary services as described for each service in the GSM 03.8x series of Technical Specifications.
The HLR should provide information to the gateway MSC to allow it to route calls directed to a mobile subscriber: either a Mobile Station Roaming Number (MSRN) to allow the call to be routed to the visited MSC or a forwarding number if the call is to be forwarded to a destination different from the original one.
The HLR should provide the identity of the visited MSC to the SMS gateway MSC to allow it to route short messages directed to a mobile subscriber; further detail is given in Technical Specification GSM 03.40. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.5 Call handling functions in VLR | The VLR must provide subscriber parameters to the MSC as required for call handling.
The VLR must also support control functions for handling of supplementary services as described for each service in the GSM 03.8x series of Technical Specifications.
For a MS in mode of operation A or B, the VLR may optionally support establishment and maintenance of an association with an SGSN. This allows paging for a circuit switched call to be performed via SGSN. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.6 Call handling functions in MSC | The MSC must perform normal call routing and call control functions. The MSC will obtain subscriber parameters from its associated VLR.
The MSC must also be capable of performing handover as defined in section 3.2.
In some cases, the MSC must be able to act as a gateway MSC to provide an interface to other circuit-switched networks. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.