hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
6.4 Realisation of Work Items
| |
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
6.4.1 Planning and categorisation of the deliverables (and control thereof)
|
Planning:
An initial time plan should be set up at an early point. As a basis, the time plan should include at least the following points:
1. Presentation for principle agreement of the service requirements;
2. Presentation for principle agreement of the architectural/system implications and requirements;
3. Presentation for information of the drafts of all needed deliverables,
4. Presentation for approval of all needed deliverables.
The time plane includes realistically achievable dates for each step and should be part of the Status List.
The WI Status List contains also information/lists about existing and planned permanent and semi-permanent documents related to the WI, e.g. future specifications as well as interim/temporary requirements "specifications", including the responsible TB SG/group, the rapporteur, the state of the documents, expected completion dates, etc.
Categorisation:
Before the substantial work on a Work Item starts, the WI shall be examined in the light of its technical and commercial dependency with respect to the existing specifications as well as with respect to other Work Items. Aspects that must be considered and settled at an early stage are:
- Required versus acceptable time scales;
- Whether the WI has an impact on Mobile Stations or not;
- Whether the WI has an architectural impact or not;
- To which degree the WI needs to be standardise (and hence how much can be left "open", to speed up the work);
- Whether the WI can be technically and/or commercially combined/grouped with other WIs;
- ......
Unless the above aspects are sorted out in the beginning of (or prior to) the work, the risk of getting inefficient and non-optimal specifications increases and the control of the work becomes difficult and unmanageable.
These aspects are also contained in the WI Status List.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
6.4.2 Choice of deliverables
|
The WI will be realised as new specifications and/or amendments to existing specifications; the exact structure lies with the individual TB SGs and the TB. Typically, a new feature may result in at least three completely new specifications (Stages 1, 2 and 3) but also cause amendments to the major protocol specifications.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
6.4.3 Contents of deliverables
| |
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
6.4.3.1 Service Requirements
|
This task, allocated and controlled according to above clauses, consists in describing in details the aim of the work item, as seen by those for which a service is provided, e.g. end users, operators, service providers, etc.
Apart from the general rules on how to write specifications, certain state of the art ways of producing service requirements specifications are established in the TB, but as most new types of service differ in nature and structure from each other, no detailed rules are written.
In many cases it is preferred that prior to the actual service requirements specification being produced, an initial combined service and system/architectural requirements and considerations document is produced, involving both service oriented and implementation expertise. In particular when an ad hoc Task Force is charged with performing a study on a certain WI (aspect) such a starting point document is produced and then used as a basis for the TB SGs when carrying out the detailed work on service requirements/descriptions and technical realisation specifications. Such setting-the-basis documents are generally kept for some time after the actual work on the detailed specifications has progressed to a mature level (mainly for the purpose of easing the understanding and to shorten the interaction and negotiation period between service requirements and system/architectural and technical restrictions).
Such 'setting-the-basis' document can also be used to describe the project management of a work item (to collect all prepared but not yet approved CRs related to the WI in question and so on).
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
6.4.3.2 Technical realisation specifications
|
This covers both the overall architectural and interface specific detailed specifications. The architectural implications and requirements need to be identified at a very early stage, both for the purpose of knowing which parts of the standard (and hence of the UMTS system) are affected by a WI, but also for the purpose of supporting the identification of cross-WI similarities (and hence more overall efficient solutions).
The overall co-ordination of the architectural/system requirements is with a single group as stated above, whilst the ensuing detailed protocol definitions and specifications may be distributed over several groups (according to their scope).
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
6.4.3.3 Test Specifications
|
Changes to the core specifications may have impact on the test specifications. The corresponding changes to test specifications have to be approved before publication the new core specifications.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
6.5 Closing of Work Items
|
When all necessary modifications for a given Work Item (or group of Work Items) are completed all over the scope of the system, and all the corresponding new specifications and Change Requests have been approved and released, then the Work Item is officially closed.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
7 Management documents and tools
|
This clause summarises and lists the various permanent or semi-permanent documents (and means of documenting).
All these documents/tools are within the responsibilities of the PT but are available to SMG delegates. They are made available on a document server (the exact location is published in each TB meeting report).
All data bases are in Microsoft Access format unless otherwise stated.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
7.1 Status List of Specifications
|
This list (data base) contains information about all SMG specifications, in terms of specification number, title, latest approved version, history on version numbers, rapporteur and some other details.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
7.2 Work Item Status List
|
This data base contains information about all SMG work items, in terms of identified future specifications, identified specifications to be amended, supplementary/temporary documentation, expected/planned completion dates and intermediary milestones, and other management information related to specifications, responsible TB Sub-Groups, rapporteurs, completion dates etc..
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
7.3 Change Request data base
|
The Change Request data base records all CRs to specifications.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
7.4 Mailing lists data bases
|
The members data base contains information of all SMG delegates.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
7.5 Electronic tools used/preferred
|
For the various types of documents and parts of documents of SMG, a minimum variety of word processors etc. should be used. The following lists those tools to be used for documents:
Type
Tool(s)
Comments
Text
Microsoft Word 97 (SR-2)
Graphics
Micrografx Designer version 7.0
MS Draw 98
Freeware from Microsoft. The built-in drawing package of Word is not recommended.
SDL, MSC,
Telelogic SDT version 3.2
Rapporteurs can obtain, as a loan, this software from ETSI
TTCN
Telelogic ITEX version 3.4
Databases
Microsoft Access 97 (SR-2)
General Tools
Microsoft Office 97 software Suite (Excel 97, Powerpoint 97, etc.)
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
7.6 WEB and FTP services
|
ETSI (http://www.etsi.org) and 3GPP (http://www.3gpp.org) web pages provide up-to-date information on specification work like: meeting calendar, meeting minutes, meeting documents and latest specifications. FTP links to file server areas of each TB WG can be found via WEB.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
7.7 E-mail reflectors
|
All TB WGs have their own e-mail lists. There are also several additional lists per topic. Further information can be found on WEB pages.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
8 Email decisions
|
TB sub-groups may apply email decision procedures for decisions they are entitled to take, as defined by superior bodies (e.g. on specifications, CRs, Liaison statements, etc). Each TB sub group may set its rules for making email decisions, however, it is required
- that the rules are clearly defined and documented;
- that a delegate having participated in plenary meetings is able to identify that he has possibly missed an email relevant to email decision.
Chapters 8.1-8.6 describe an email decision procedure example.
8.1 Email drafting phase
An email drafting can be launched, either on a dedicated exploder list as a cybermeeting or as an informal discussion between interested delegates. Objectives can extend from debating an existing contribution, a Liaison Statement or a Change Request to progressing the service requirements of a specific Work Item and involving one or more Work Groups within an ad hoc.
In case of "cybermeeting", the chairman of the discussions shall issue an un-ambiguous guideline including:
1. The objectives and agenda of the meeting,
2. Input document(s) to be clearly specified
3. Start date and end date of the debates.
4. Afterwards, summary of results of the "cybermeeting"
The end-goal being to reach an “agreement” on the deliverable, either at the next meeting or via an e-mail approval procedure.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
8.2 Email decision declaration
|
Authority for an Email decision to take place should be agreed usually at plenary meeting. If this is not possible, there shall be a clear mail (i.e. status report) indicating that there will be a email decision. This mail shall be sent on working groups main mailing lists. Target and timeframe need to be clearly indicated. Email decision shall take place using the main WG reflector. A permanent Chairman (i.e. WG chairman or vice chairman) must be nominated who is responsible for managing email desision procedure, including initiation, monitoring and announcing when it is complete.
It is not the objective for email desision procedure to re-open the discussions of a “cyber meeting”. The only use of the main reflector, when approving the outcome of a “cyber meeting”, shall be to accept the outcome of the cyber meeting unchanged (apart from editorial remarks), or reject it.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
8.3 Status reporting
|
During the e-mail desicion period, there shall be clear message stating what the status of each open item is. It is recommended to have a weekly summary of the status of all items, from the previous plenary listing:
• The name of the open item
• The name of the responsible delegate,
• Time left for comments before the deadline & expiration date
• Current work versions of documents: Tdoc number, CR number, Revision number
• Status (Debate ongoing, Agreed, Postponed, Rejected...)
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
8.4 Decision announcement
|
When a decision is made (Agreed, rejected, postponed,..) a clear notification on what has been agreed shall be sent on the WGs’ main mailing list. Notification may be included at status report.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
8.5 Timing
|
Email decision procedure should start latest 3 weeks before plenary:
• Email decision period is two weeks (one status report required).
• Procedure shall be completed one week before the plenary due to practical arrangements.
|
714fea1a3412b60c57d0fb418fe8bfee
|
01.00
|
8.6 General
|
• On exceptional case's when procedure cannot be followed a clear notice from chairman is required.
• Emails on mailing list shall contain a header with meaningful keywords, e.g. S1 Tdoc xxx on Charging or/and CR 22xxA012r4.
• If there are no comments during the allowed period, agreement is granted automatically.
• TB WGs status report to higher body meeting, is emailed to mailing list one week before the meeting. This allows delegated final possibility to review last periods progress.
Annex A (informative): Change control history
SMG#
VERS
SUBJECT
30
8.0.0
Version 8.0.0 created from version 7.2.0
|
7e80bf24517beeb9be2fa8c530e8ca88
|
01.56
|
1 Scope
|
This specification constitutes a requirement specification for a set of associated cryptographic algorithms which is used for Cordless Telephony System (CTS) Radio Interface authentication and key management in the GSM Cordless Telephony System.
This specification is intended to provide ETSI SAGE with the information it requires in order to design and deliver a technical specification for such an algorithm set.
This specification covers the intended use of the algorithm set and use of the algorithm set specification, technical requirements on the algorithm set, requirements on the algorithm set specification and test data, and quality assurance requirements on both the algorithm set and its documentation. The document also outlines the background to the production of this specification.
|
7e80bf24517beeb9be2fa8c530e8ca88
|
01.56
|
1.1 Organisation of this specification
|
The material presented in the subsequent clauses of this specification is organised as follows:
subclause 1.2 provides some background to the production of this specification.
clauses 4 and 5 describe the context in which the algorithm set and its specification are intended to be used.
Clause 4 outlines the intended use of the algorithm set in terms of which organisations shall be entitled to use it, what they shall use it for, where it shall be used, and how it shall be implemented.
Clause 5 describes the intended use of the algorithm specification set in terms of who shall own it, who shall use it, and how and under what conditions the specification shall be provided to those users.
clause 6 specifies the functional requirements for the algorithm set. This covers the type and parameters of the algorithm, the interface to the algorithm set, the envisaged modes of operation of the algorithm set, implementation and operational considerations which may have an impact on the design of the algorithm set and requirements on the resilience of the algorithm set.
clause 7 details requirements on the algorithm set specification and associated test data deliverables.
clause 8 addresses quality assurance requirements, needed to give confidence in the design of the algorithm set and the adequacy of the algorithm set specification and test data.
clause 9 is a summary of the deliverables expected from ETSI SAGE.
|
7e80bf24517beeb9be2fa8c530e8ca88
|
01.56
|
1.2 Motivation
|
Discussions within SMG led to the conclusion that GSM-CTS can only be provided on a commercially solid and successful basis if appropriate security features are integrated into the system. In particular it was decided to standardise mechanisms both authentication and key generation algorithms.
Consequently an annex to GSM 03.20 was produced, which specifies the security features of the CTS. It was also concluded that, in order to support inter-operability between equipment, and in line with the policy for GSM, a set of standard ETSI algorithms for CTS Radio Interface authentication and key management needs to be specified.
The implementation of the algorithm set is mandatory, the implementation shall be in line with this specification.
|
7e80bf24517beeb9be2fa8c530e8ca88
|
01.56
|
2 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.
[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms"
[2] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions; Stage 2.
|
7e80bf24517beeb9be2fa8c530e8ca88
|
01.56
|
3 Definitions and abbreviations
| |
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;
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.