hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 6.3 Start and continuation of the work and responsibilities | An early task when elaborating a work item is to identify the tasks related to the WI and allocate those to the TBs and TB SGs.
In most cases the tasks from a WI can be split immediately in the following areas:
- Service requirements
- System/Architectural requirements and implications
- Protocol specifications
Service... |
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. Presentati... |
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 specificatio... |
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 p... |
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 purpos... |
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).... |
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, responsib... |
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... |
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;
- ... |
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 indic... |
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 ... |
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 ... |
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 i... |
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 us... |
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 ... |
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.
• Fo... |
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-M... |
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 o... |
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 ... |
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 con... |
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 algorit... |
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 admin... |
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 fo... |
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 shoul... |
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 t... |
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 b... |
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 ... |
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 li... |
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 ... |
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 ... |
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 executio... |
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 ... |
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 ... |
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 in... |
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 algor... |
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/outp... |
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):... |
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... |
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.
• Fo... |
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 capabilitie... |
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 "... |
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 s... |
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 Teleservic... |
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 ser... |
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 th... |
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 ch... |
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.
- Fo... |
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 ... |
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... |
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; |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.