hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply:
Active alarm: an alarm that has not been cleared. An alarm is active until the fault that caused the alarm is corrected and a clear alarm is generated
Alarm: an alarm is an abnormal network entity condition which categorises an event a... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
CCITT The International Telegraph and Telephone Consultative Committee
CM Configuration Management
CMIP Common Management Information Protocol
CMIS Common Management Information Service
CMISE Common Management Information Service Element
EIR E... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4 Fault Management concept | Any evaluation of the network elements' and the overall network health status will require the detection of faults in the network and, consequently, the notification of alarms to the OS (EM and/or NM). Depending on the nature of the fault, it may be combined with a change of the operational state of the logical and/or ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1 Faults and alarms | Faults that may occur in the network can be grouped into one of the following categories:
• Hardware failures, i.e. the malfunction of some physical resource within a NE.
• Software problems, e.g. software bugs, database inconsistencies.
• Functional faults, i.e. a failure of some functional resource in a NE and no har... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.1 Fault detection | When any type of fault described above occurs within a 3G network, the affected network entities must be able to detect them immediately.
The network entities accomplish this task using autonomous self-check circuits/procedures, including, in the case of Nes, the observation of measurements, counters and thresholds. Th... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.2 Generation of alarms | For each detected fault, appropriate alarms shall be generated by the faulty network entity, regardless of whether it is a steady or unsteady fault. Such alarms shall contain all the information provided by the fault detection process as described in subclause 4.1.1.
In order to ease the fault localisation and repair, ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.3 Clearing of alarms | The alarms originated in consequence of faults need to be cleared. To clear an alarm it is necessary to repair the corresponding fault. The procedures to repair faults are implementation dependent and therefore they are out of the scope of the present document, however, in general:
• the equipment faults are repaired b... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.4 Alarm forwarding and filtering | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.5 Storage and retrieval of alarms in/from the NE | For fault management purposes, each NE will have to store and retain the following information:
• a list of all active alarms, i.e. all alarms that have not yet been cleared; and
• alarm history information, i.e. all notifications related to the occurrence and clearing of alarms.
The storage space for alarm history in ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.6 Fault Recovery | After a fault has been detected and the replaceable faulty units have been identified, some management functions are necessary in order to perform system recovery and/or restoration, either automatically by the NE and/or the EM, or manually by the operator.
The fault recovery functions are used in various phases of the... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.7 Support of Maintenance Action | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.8 Configuration of Alarms | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.2 State management | The State Management is a common service defined within Configuration Management (TS 32.106) and used by several management areas, including Fault Management. In this clause, some detailed requirements on State Management as they apply to the Fault Management are defined.
From the point of view of Fault Management, onl... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.2.1 Propagation of state change | Within a managed element, when for any reason a resource changes its state, the change must be propagated, in a consistent way, to all the other resources that are functionally dependent on the first one. Therefore:
• In case of a fault occurring on a resource makes that resource completely out of service, if the curre... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.3 Test management | x Fault management requirements
This clause defines the FM requirements from the OS's perspective. According to the concept described in clause 4, the NEs shall maintain alarm and state change information. This information shall then be forwarded to one or more OS(s), i.e. the OMC and/or NMC. The OMC's role to play in ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5 N interface | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.1 Fault Management concept of Itf-N | An operations system on the network management layer (i.e. the NM) provides fault management services and functions required by the 3G operator on top of the element management layer.
As pointed out in clause 5, the N interface (Itf-N) may connect the network management system either to EMs or directly to the NEs. This... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.2 Management of alarm and state change event reports | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.2.1 Mapping of alarm and related state change event reports | The alarm and state change reports received by the NM relate to functional objects in accordance with the information model of Itf-N. This information model tailored for a multi-vendor capability is different from the information model of the EM-NE interface (if an EM is available) or from the internal resource modelli... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.2.2 Real-time forwarding of event reports | If the Itf-N is in normal operation (the NM connection to the subordinate entities is up), alarm and related state change event reports are forwarded in real-time to the NM via appropriate filtering located in the subordinate entity. These filters may be controlled either locally or remotely by the managing NM (via Itf... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.2.3 Alarm clearing | On the Itf-N, alarm reports containing the value "cleared" of the parameter perceivedSeverity are used to clear the alarms. The correlation between the clear alarm and the related active alarms is performed by means of unambiguous identifiers.
This clearing mechanism ensures the correct clearing of alarms, independentl... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.3 Retrieval of alarm and state information | The retrieval of alarm and state information comprises two aspects:
a) Retrieval of current information
This mechanism shall ensure data consistency about the current alarm/state change information between the NM and its subordinate entities and is achieved by means of a so-called synchronisation ("alignment") procedur... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.3.1 Retrieval of current alarm information on NM request | The present document defines a flexible, generic synchronisation procedure, which fulfils the following requirements:
• The alarm information provided by means of the synchronisation procedure shall be the same (at least for the mandatory parameters) as the information already available in the alarm list. The procedure... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.3.2 Retrieval of current state change information on NM request | The requirements defined above for the alarm synchronisation procedure are valid analogously for the retrieval of current state change information as well.
Nevertheless the state change synchronisation procedure takes into account only the object instances whose state information is different from a combined default st... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.3.3 Logging and retrieval of alarm and state change history information on NM request | The alarm/state change history information may be stored in the subordinate entities in dependence on the NM requirements. The NM is able to create logs for alarms/state change event reports and to define the criteria for storage of alarm/state change information according to [11].
The subsequent retrieval of stored in... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.4 Co-operative alarm acknowledgement on the Itf-N | The acknowledgement of an alarm is a maintenance function that aids the operators in his day to day management activity of his network. An alarm is acknowledged by the operator to indicate he has started the activity to resolve this specific problem. In general a human operator performs the acknowledgement, however a ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.5 Overview of IRPs related to fault management | The N interface is built up by a number of IRPs. The basic structure of the IRPs is defined in [2] and [3].
For the purpose of Fault Management the following IRPs are needed:
• Alarm IRP
• Notification IRP
• Log IRP
(NOTE: This IRP may not be part of Release 1999)
Annex A (informative):
Change history
This annex lists ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 1 Scope | This document outlines the working methods [to be] used by SMG and its sub-groups and by PT SMG in relation to document management, i.e. handling of specifications, updating procedures, change request procedures, version control mechanisms, specifications status information etc. It complements the rules and procedures ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 2 Definitions and Abbreviations | Change Control When a specification has been put under change control, changes to the specification require an approval of formal change requests. Rules for change control are defined in section 4.
Closed A closed major version of a specification is still published; however no changes to the major version of the specif... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 3 General responsibilities of the Project Team | The Project Team for SMG (PT, or PT SMG) is responsible for the project management of the work of the TB. This includes editorship and management of specifications once they have been put under TB change control. It also includes preparation of and support for the meetings (including meeting reports) of the TB and its ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4 Handling of Specifications | This section describes the general procedures and events involved in, and related to, the lifetime of a specification. |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.1 Overview | This section gives an overview on the development of a specification, dealing with the unexceptional cases only, and leaving out details. A more detailed description is given in the remainder of section 4.
A new specification is created in a TB WG. At creation, a rapporteur is nominated. The rapporteur elaborates the f... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.2 Characteristics of a specification | - The specification has a prime responsible TB.
- The specification may have a prime responsible TB WG.
- The specification may have one or more secondary responsible TBs and/or TB WG.
- The specification may have a prime responsible TB Sub-Group below a Working Group as decided by the prime responsible TB WG.
- The s... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.3 Characteristics of a major version of a specification: | A major version 0 or 1 or 2 of a specification has the following characteristics:
- It is either a draft or withdrawn.
- It is TB internal.
A major version w > 2 of a specification has the following characteristics:
- It is either under TB WG Change Control or under TB Change Control or closed or withdrawn.
- It is eit... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.4 Characteristics of a version of a specification | 0.x.y
- draft (or withdrawn)
- TB internal
- no version of the specification has been presented for information to the TB yet
- no major version of the specification is under TB change control yet
1.0.0
- draft (or withdrawn)
- TB internal
- this version 1.0.0 is presented to TB
- for information
- or for information a... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5 Actions on a specification | In the following subsections the concept of "stability" is used , which is linked to the likelihood that a given specification will change more or less significantly before reaching it's final steady. The attributes "low stability", "medium stability" and "good stability" are used. The assessment of stability cannot be... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.1 Actions on a new specification (version 0.x.y) | - A new specification (a specification version 0.0.0) may be created by a TB WG. A rapporteur (more exactly: at least one rapporteur) is assigned by that WG. A prime responsible subgroup of the TB WG may be allocated by the TB WG.
- The rapporteur prepares version 0.1.0 and presents it to the prime responsible TB WG/SG... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.2 Actions on version 1.x.y of a specification | - On decision of the prime responsible TB WG, the PT transforms version 0.x.y of a specification into version 1.0.0, performing the necessary - strictly editorial - cleaning up, and version 1.0.0 is presented by the TB WG to the to the prime responsible TB and to the secondary responsible TB SG(s) for information or fo... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.3 Actions on version 2.x.y of a specification | - On decision of the prime responsible TB WG, the PT transforms version 1.x.y of a specification into version 2.0.0, performing the necessary - strictly editorial - cleaning up, and version 2.0.0 is presented by the prime responsible TB WG to the prime responsible TB for approval; comments of the secondary responsible ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.4 Actions on version w.x.y of a specification (w > 2) | - On decision of the TB, the PT transforms a version v.x.y of a specification into version w.0.0, performing the necessary - strictly editorial - cleaning up.
- The prime responsible TB WG may agree on Change Requests to the most recent version w.x.y of major version w of a specification. It will then propose these CRs... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.5 Actions on the major version of a specification | - The TB may decide to create a new major version >2 of a specification.
- The TB may decide to withdraw a major version of a specification.
- The TB may decide to close a frozen major version of a specification.
- The TB may authorise a major version >2 for publication or decide that it is TB internal.
- The TB may de... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6 Change Request Regime | Modifications to specifications under TB Change Control are decided by the TB, on the basis of Change Requests (CR). These CRs, described in the following sections, shall in principle only be presented to the TB after having been scrutinised by the TB WG responsible for the concerned specification; comments from second... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.1 Change Requests | Whenever an error or an inconsistency is discovered or when a new feature is proposed to be included, a Change Request is produced, normally by the one discovering the error but in consultation with the rapporteur and/or with the PT.
In the case of an essential error corrections, separate Change Requests for each affec... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.2 Change Request forms | To ensure an appropriate and consistent way of presenting and documenting Change Requests, there exist standardised front covers (forms) for CRs as well as rules on how to accurately identify the modified parts of the specification.
The purpose of the CR form itself is to provide the relevant management information of ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.3 Contents of Change Requests | Although the CR form shall indicate the details of change, each CR shall have attached the pages of the specification that are affected by the CR, using the latest version of the major version. These pages shall have the proposed modifications clearly marked, by means of the word processor's "revision mode", i.e. new p... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.4 Handling of the Change Requests | Entry to the TB WG:
A proposed CR should be brought to the relevant TB WG or, if applicable, to the prime responsible TB SG in charge of the specification concerned and discussed there, before presentation to the TB. If possible it should be distributed, by the source, as soon as possible and prior to the coming TB SG ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.5 Updating and release of new versions of the specifications | After TB approval of one or more CRs, the PT produces a new version of the specification (with the version number incremented according to above). |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 5 Availability and distribution of specifications | The latest versions of TB approved and TB WG approved specifications are made available on a TB server (exact location see TB meeting report) by the PT. For specifications (or major versions of specifications) that are not yet under change control, the versions presented to the responsible TB-SG or WG, shall be made av... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 6 Work items | For project management purposes, the work is itemised in Work Items (WI), which are documented, developed and handled as described in this section.
The possible modifications of the specifications are basically of different natures:
- Error corrections; Modifications which correct overlooked errors or inconsistencies i... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 6.1 Creation of a Work Item | When an enhancement of the standard is considered desirable a delegate or delegation can make a proposal by submitting a Work Item Description sheet to the relevant TB or TB WG.
- For new services, features or functions, the TB responsible for Services and System Aspects is the relevant TB. This TB also assigns prime a... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 6.2 Type of Work Items | Modifications of the standard could in principle be of two different types:
- New services/features/functions that in general affects several specifications and several TB-SGs;
- Pure [technical] enhancements that affects a small number of specifications and TB-SGs only (generally only one).
Of these, modifications of ... |
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). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.