hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.6.2 Network initiated supplementary service transaction | MS Network REGISTER <------------------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = Operation (Supplementary service code, Parameter(s))) RELEASE COMPLETE ----------------------------------------------------------------------------... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.1 General | These procedures only apply to messages where the protocol discriminator is set to indicate call independent SS operations according to the rules in GSM 04.07 and GSM 04.80. Messages that do not meet this criteria are treated according to other GSM technical specifications. This subclause specifies procedures for handl... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.2 Message too short | When a message is received that is too short to contain a complete message type information element, that message shall be ignored. |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.3 Unknown or unforeseen transaction identifier | The MS shall ignore messages with the transaction identifier value set to "111". If the transaction identifier value is not "111" the following procedures shall apply to the MS: a) If a RELEASE COMPLETE message is received specifying a transaction identifier that is not recognized as relating to a call independent SS t... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.4 Unknown or unforeseen message type | If the MS receives a message type not defined for the protocol discriminator or not implemented by the receiver, then a RELEASE COMPLETE message shall be sent with cause value #97 "message type non-existent or not implemented". If the MS receives a message type not consistent with the transaction state then a RELEASE C... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.5 Non-semantical mandatory Information Element Error | When on receipt of a message: - an "imperative message part" error; or - a "missing mandatory IE" error; is diagnosed, or when a message containing: - a syntactically incorrect mandatory IE; or - an IE unknown in the message, but encoded as "comprehension required" (see GSM 04.08); or - an out of sequence IE encoded as... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.6 Unknown and Unforeseen IEs in the non-imperative part | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.6.1 IEIs unknown in the message | The MS shall ignore all IEs unknown in the message which are not encoded as "comprehension required". The network shall take the same approach. |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.6.2 Out of sequence IEs | The MS shall ignore all out of sequence IEs in a message which are not encoded as "comprehension required". The network may take the same approach. ETSI TS 100 941 V6.0.1 (1998-07) 21 GSM 04.10 version 6.0.1 Release 1997 |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.6.3 Repeated IEs | If an information element with format T, TV or TLV (see GSM 04.07) is repeated in a message in which repetition of the information element is not specified, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repe... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.7 Non-imperative message part errors | This category includes: - syntactically incorrect optional IEs; - conditional IE errors. Errors in the content of the Facility IE are handled according to subclause 2.2.8. |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.7.1 Syntactically incorrect optional IEs (other than Facility) | The MS shall treat all optional IEs that are syntactically incorrect in a message as not present in the message The network shall take the same approach. |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 3.7.7.2 Conditional IE errors | When the MS upon receipt of a message diagnoses a "missing conditional IE" error, or an "unexpected conditional IE error", or when it receives a message containing at least one syntactically incorrect conditional IE (other than Facility), it shall send a RELEASE COMPLETE message with cause #100 "conditional IE error". ... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 4 Password management | The password management procedures consist of two independent procedures: - password check; - password registration. |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 4.1 Password check | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 4.1.1 Successful procedure | When the password check procedure is invoked by a parent procedure (e.g. for service activation, service deactivation, password registration), the network sends to the MS an invoke component of the operation "get password" with "password" as the value of the mandatory GuidanceInfo information element. This invoke compo... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 4.1.2 Error cases | If no result is returned by the MS for the "Get password" operation invoked by the network, the password check procedure is terminated. If the password value which is returned by the MS does not match the password value registered in the network, the network increments a counter and sends to the MS a Return Error compo... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 4.2 Password registration | If the served mobile subscriber is given the possibility to control the service by the use of a password, the service provider has to register a password at provision time. Furthermore, the served mobile subscriber can change the call barring password at any time. The password registration procedure is as follows: When... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 4.2.1 Successful procedure | The successful procedure consists of three steps: - the password registration procedure invokes first the password check procedure as it is described above; - if the password check procedure has returned an indication of successful password check, the network sends secondly to the MS, in an invoke component of the oper... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 4.2.2 Error cases | If the subscription option "control of services" is set to "by the service provider" or if the WPA is greater than 3 an attempt to register a password will be denied by the network (see GSM 03.11). If the counter for wrong password attempts is smaller than four, the network will return to the MS an error component with... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 4.3 Cross phase compatibility | When password procedures are initiated by an MS which does not provide an SS version indicator and where errors occur in password procedures, the network shall not send the protocol error values "DataMissing", "CallBarred" or "NumberOfPWAttemptsViolation". When an MS that supports version 2 of the SS-protocol receives ... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5 Supplementary service cross phase compatibility | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.1 Cross phase, or cross protocol version, interworking | Due to the phased approach to GSM standardization it is possible for a service to be changed, or new services to be added, between different versions of the standard. Since GSM supports the features "terminal mobility" and "roaming" and is a system of open interfaces, it is possible for entities supporting different ve... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.2 Objectives | The objectives of these procedures are as follows: - to allow flexibility of implementation, i.e. allow different combinations of services to be supported at different versions within a single entity; - to allow SSs to evolve from version to version of the standards; - to decouple SS protocol from other protocols; - to... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.3 Supplementary service compatibility philosophy | The purpose of the SS compatibility procedures is to ensure that when a service is invoked the highest common version of the service protocol is used in the entities supporting that service. The highest protocol version gives the best level of service to the subscriber. The commonality of versions between entities prov... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.4 Compatibility mechanisms | Two signalling indicators are used in the MS to network direction to provide information on the general capabilities of the MS and on specific SS protocol versions. A protocol extension mechanism is also used for protocol evolution. NOTE: These compatibility mechanisms are flexible, and could be applied in ways outside... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.4.1 SS screening indicator | The SS screening indicator is sent by the MS at the beginning of the radio connection to allow the network to assess the capabilities of the MS and hence determine, - whether a particular network initiated SS operation may be invoked; or - what version of a network initiated SS operation should be invoked. The SS scree... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.4.2 SS version indicator | The SS version indicator is sent by the MS and is associated with one or more related SS operations. It indicates to the network the correct version of radio interface protocol and procedures to use for those SS operations. For call related SSs the version indicator is valid for the invocation period of the SS operatio... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.4.3 Protocol extension mechanism | A protocol extension mechanism is used in the common information element category supplementary service protocol to allow controlled evolution of the protocol. The purpose of this mechanism is to allow optional information to be introduced into operations without causing receiving entities, who do not recognize this in... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5 SS compatibility procedures | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.1 Screening indicator procedures | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.1.1 MS procedure | If a MS supports Phase 2 GSM 04.10 error handling and the Phase 2 GSM 04.80 extension mechanism it shall send the screening indicator to the network during layer 3 connection establishment. The value of the indicator shall indicate Phase 2. The sending of the screening indicator does not depend upon the invocation of a... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.1.2 Network procedure | At layer 3 connection establishment with the MS, the network shall check for the SS screening indicator and note, for the duration of the connection, whether the indicator was sent, and if sent, the value of the indicator. On invocation of any network initiated SS operation (unless an SS version indicator has taken pre... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.2 SS version indicator procedures | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.2.1 MS procedure | If an SS operation has been initiated at the MS, and the MS supports Phase 2 GSM 04.10 error handling and the Phase 2 GSM 04.80 extension mechanism and the operations used by the mobile initiated procedure are implemented according to the Phase 2 GSM standards, then: - in the case of call independent activity, the MS s... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.2.1.1 MS procedure for version 3 or higher operations | The relevant stage 3 specification for each service shall state if the operation requires the use of SS version indicator 3 or higher for MS initiated operations. The SS version indicator is used within the network to define the MAP Application Context used for a specific operation (see GSM 09.02). An MS initiating an ... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.2.2 Network procedure | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.2.2.1 Call independent SS activity | When a new transaction is set up for call independent SS activity the network shall check for the SS version indicator and note, for the duration of the transaction, whether the indicator was present, and if present, the value of the indicator. The network shall use this indication to establish the correct MAP applicat... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.2.2.2 Call related SS activity | When a call related common information element SS operation is received by the network, the network shall check the GSM 04.08 carrier message for the SS version indicator. The network shall note whether the indicator was present, and if present, what value was provided. The network shall use this information to operate... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.3 Extension mechanism procedures | The handling of the extension mechanism (ellipsis) is a detailed protocol matter and is described in the MAP version 2, GSM 09.02. ETSI TS 100 941 V6.0.1 (1998-07) 30 GSM 04.10 version 6.0.1 Release 1997 |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.4 SS version indicator - MAP context interworking | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.4.1 Call independent interworking | The compatibility mechanisms described in these subclauses concern the radio interface. The fixed network protocol MAP also specifies compatibility mechanisms. The interworking between these mechanisms occurs at the MSC/VLR. The MSC shall operate and set up contexts according to the version indicated by the MS wherever... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.5.4.2 Call related interworking | No interworking identified. |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 5.6 Development of future protocol versions | As a general rule all future versions of protocol should be designed such that they are a superset of the previous protocol. This provides backward compatibility. Optional information shall be introduced, where appropriate, in the extensible parts of operations. Non-compatible protocol changes, i.e. the introduction of... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 6 Forward Check SS Indication | The forward check SS indication procedure is used when supplementary services data in the HLR may have become corrupted. The procedure is initiated by the network to inform the user to verify his supplementary services data. The procedure consists of the network sending the ForwardCheckSSIndication operation on a call ... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 1 Scope | The present document defines the service offered by the physical layer (GSM 05-series of Technical Specifications) of the MS-BS interface (GSM 05- and 04-series of Technical Specifications). Its main objective is to be a guidance for the interface between the GSM Technical Specifications in the 05-series and the 04-ser... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 1.2 Definitions and abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 2 Interfaces to the physical layer | The physical layer (layer 1) is the lowest layer in the OSI Reference Model and it supports all functions required for the transmission of bit streams on the physical medium. These bit streams are transferred on traffic channels, packet data traffic channels and control channels as defined in GSM 04.03. NOTE: For GSM a... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 2.1 Interface to the Data Link Layer | The physical layer interfaces the data link layer. On this interface control channels are supported. The data link layer is specified in GSM 04.05 and 04.06. Communication between the Physical Layer and the Data Link Layer is in an abstract way performed by means of PH-primitives. They do not constrain implementations.... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 2.2 Interface to radio resource management | The physical layer interfaces the radio resource management (RR-management) entity of layer 3 in the MS and in the network. Communication is performed in an abstract way by means of MPH-primitives. They do not constrain implementations. The primitives exchanged with the RR-management entity are related to the assignmen... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 2.3 Interface to other functional units | The physical layer interfaces other functional units in the MS and in the network for supporting traffic channels. These interfaces are described in the 06 and 07 series of Technical Specifications. |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 3 Service of the physical layer | The physical layer supports transfer of bit streams on the radio medium according to the Technical Specifications of the 05-series. The scope of the 05-series of Technical Specifications is the definition of a framework for operation on the radio medium. The application of this framework on the radio medium results in ... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 3.1 Service Access Point | In the Reference Model for Open System Interconnection, Service Access Points (SAPs) of a layer are defined as gates through which services are offered to an adjacent higher layer (figure 3.1). Through a SAP the physical layer offers a service to the data link layer. The SAP is used both for the control of the service ... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 3.2 Service of the physical layer | * Access capabilities: The physical layer offers a transmission service on a limited set of logical channels. The BS and MS access capabilities and the characteristics of logical channels (SAPs) are defined in GSM 04.03. NOTE: Between GSM 04.03 and the GSM 05-series there is a slight difference in terminology. The "cha... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 3.2.1 Specific services of the physical layer in the MS | The access capability service of the physical layer in the MS differs depending on the nature of the channel (traffic, packet data traffic or broadcast/common channels). - Establishment of dedicated physical channels: Establishment of dedicated physical channels on the physical layer is controlled by the radio resource... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 4 Primitives of the physical layer | The Physical layer interacts with other entities as illustrated in figure 2.1. The interactions with the data link layer of Dm channels and the interactions with the RLC/MAC layer of packet data physical channels are shown in terms of primitives where the primitives represent the logical exchange of information and con... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 4.3 Primitive types | The primitive types defined in the present document are: a) REQUEST: The REQUEST primitive type is used when a higher layer is requesting a service from a lower layer. ETSI ETSI TS 100 936 V7.0.0 (1999-08) 12 (GSM 04.04 version 7.0.0 Release 1998) b) INDICATION: The INDICATION primitive type is used by a layer providin... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 4.4 Parameter definition | Primitives contain a variable amount of parameters. The primitives with included parameters are listed in table 4.1. Table 4.1: Primitives of the physical layer message unit channel control parameters system information absolute frame No. primitive entity direction measurement MPH-INFO-REQ MS/BS RR(L3) PH(L1) x x MPH-I... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 5 Physical layer procedures | The main body of physical layer procedures is specified in GSM 04.08, GSM 04.60 and 05.08. |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 5.1 States of the physical layer | In the physical layer of the MS the following states are defined: NULL: the equipment is switched off; SEARCHING BCH: the physical layer tracks the best BCCH; BCH: the physical layer listens to a BCCH/CCCH or PBCCH/PCCCH and is able to do random access; TUNING DCH: the physical layer seizes on a respective dedicated ph... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 5.2 Control procedures | Requirements and examples of procedures for idle mode and for packet mode operation of the MS are specified in GSM 02.11 and 05.08. In the idle mode and packet mode procedures the physical layer tracks the best cell and may tune on their BCCH/PBCCH in order to enable layer 3 to read the system information of the BCCH/P... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 5.3 Physical layer interface procedures | Three types of primitives are defined for the communication between the physical layer and the data link layer both in the MS and the network. When a control channel or a packet data physical channel is being established, a PH-CONNECT-INDICATION is offered to the data link layer or the RLC/MAC layer, the one which is a... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 6 Physical layer protocol header | The physical layer implements a peer-to-peer protocol for the control of timing advance and power control at the operation on dedicated physical channels, and further, for the control of timing advance at the operation on packet data physical channels. For this purpose a two octet physical header is defined on all bloc... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 6.1 Physical layer protocol fields and procedures | Procedures for handling the ordered and actual power level fields are specified in GSM 05.05 and 05.08. The ordered MS power level field and the actual MS power level field are coded as the binary representation of the "power control level", see GSM 05.05. Procedures for handling the ordered and actual timing advance f... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7 Block transmission | |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.1 SACCH downlink block format | The originally 23 octets of SACCH blocks are used downlink in the following way: bit numbering <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 Spare Ordered MS power level octet 1 Spare Ordered timing advance octet 2 octet octet 3 numbering 21 octets V : : : : : : lay... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.2 SACCH uplink block format | The originally 23 octets of SACCH blocks are used uplink in the following way: ETSI ETSI TS 100 936 V7.0.0 (1999-08) 16 (GSM 04.04 version 7.0.0 Release 1998) bit numbering <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 Spare Actual MS power level octet 1 Spare Actua... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.3 FACCH/SDCCH/CCCH/BCCH/CBCH downlink block format | The originally 23 octets blocks are used downlink in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 octet 1 23 octets : : : : : : layer 2 frame octet 23 NOTE: The numbering convention specified in GSM 04.06 and 04.12 applies. Figure 7.3: FACCH/SDCC... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.4 FACCH/SDCCH uplink block format | The originally 23 octets blocks are used uplink in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 octet 1 23 octets : : : : : : layer 2 frame octet 23 NOTE: The numbering convention specified in GSM 04.06 applies. Figure 7.4: FACCH/SDCCH uplink blo... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.6 PDTCH block type 2 (CS-2) format | The originally 271 bit blocks are used in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 octet 1 271 bit : : : : : : RLC/MAC block octet 34 NOTE: The numbering convention specified in GSM 04.60 applies. Figure 7.6: PDTCH block type 2 (CS-2) format ... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.7 PDTCH block type 3 (CS-3) format | The originally 315 bit blocks are used in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 octet 1 315 bit : : : : : : RLC/MAC block octet 39 octet 40 NOTE: The numbering convention specified in GSM 04.60 applies. Figure 7.7: PDTCH block type 3 (CS-3... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.8 PDTCH block type 4 (CS-4) format | The originally 431 bit blocks are used in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 octet 1 431 bit : : : : : : RLC/MAC block octet 54 NOTE: The numbering convention specified in GSM 04.60 applies. Figure 7.8: PDTCH block type 4 (CS-4) format ... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.10 PTCCH downlink block format | The originally 184 bit (23 octets) blocks are used downlink in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 Spare Ordered timing advance for MS assigned TAI = 0 octet 1 Spare Ordered timing advance for MS assigned TAI = 1 octet 2 : : : : : : Spar... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.11 PTCCH uplink block formats | Two alternative PTCCH uplink block formats are specified. The originally 8 bit (1 octet) blocks are used uplink in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 8 fixed bits: "01111111" octet 1 Figure 7.11 (sheet 1 of 2): PTCCH uplink block format... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 7.12 Order of bit transmission | On channels for normal burst transmission having a block format with an integer N number of octets, the N octets are mapped onto 8N bits, d(0) to d(8N-1), defined in GSM 05.03 clause 4 and 5 as follows: Bit m of octet n shall be transmitted as bit d((n-1)*8+m-1) with m=(1..8) and n=(1..N). On channels for normal burst ... |
63a686576ef1d4deefbf019203f7ac12 | 100 936 | 8 Vocabulary | The terminology used in the present document is as follows: - Idle mode: In this mode the MS is not allocated any dedicated physical channel; it listens to the CCCH and the BCCH. - Dedicated mode: In this mode the MS is allocated a dedicated physical channel, at least containing two logical channels, only one of them b... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 0 Scope | The present document specifies the network functions needed to provide the security related service and functions specified in GSM 02.09. The present document does not address the cryptological algorithms that are needed to provide different security related features. This topic is addressed in annex C. Wherever a cryp... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 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... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 0.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. Specific abbreviations used in annex A are listed in clause A.3. Specific CTS related abbreviations used in annex E are listed in clause E.1.3. ETSI ETSI TS 100 929 V7.2.0 (1999-11) 11 (GSM 03.20 version 7.2.0 Release 1998) |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 1 General | The different security related services and functions that are listed in GSM 02.09 are grouped as follows: - Subscriber identity confidentiality; - Subscriber identity authentication; - Signalling information element and connectionless user data confidentiality and data confidentiality for physical connections (cipheri... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2 Subscriber identity confidentiality | |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.1 Generality | The purpose of this function is to avoid the possibility for an intruder to identify which subscriber is using a given resource on the radio path (e.g. TCH (Traffic Channel) or signalling resources) by listening to the signalling exchanges on the radio path. This allows both a high level of confidentiality for user dat... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.2 Identifying method | The means used to identify a mobile subscriber on the radio path consists of a TMSI (Temporary Mobile Subscriber Identity). This TMSI is a local number, having a meaning only in a given location area; the TMSI must be accompanied by the LAI (Location Area Identification) to avoid ambiguities. The maximum length and gui... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3 Procedures | This subclause presents the procedures, or elements of procedures, pertaining to the management of TMSIs. |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3.1 Location updating in the same MSC area | This procedure is part of the location updating procedure which takes place when the original location area and the new location area depend on the same MSC. The part of this procedure relative to TMSI management is reduced to a TMSI re-allocation (from TMSIo with "o" for "old" to TMSIn with "n" for "new"). The MS send... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3.2 Location updating in a new MSCs area, within the same VLR area | This procedure is part of the location updating procedure which takes place when the original location area and the new location area depend on different MSCs, but on the same VLR. The procedure is schematized on figure 2.2. ... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3.3 Location updating in a new VLR; old VLR reachable | This procedure is part of the normal location updating procedure, using TMSI and LAI, when the original location area and the new location area depend on different VLRs. The MS is still registered in VLRo ("o" for old or original) and requests registration in VLRn ("n" for new). LAI and TMSIo are sent by MS as identify... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3.4 Location Updating in a new VLR; old VLR not reachable | This variant of the procedure in subclause 2.3.3 arises when the VLR receiving the LAI and TMSIo cannot identify the VLRo. In that case the relation between TMSIo and IMSI is lost, and the identification of the MS in clear is necessary. The procedure is schematized in figure 2.4. ... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3.5 Reallocation of a new TMSI | This function can be initiated by the network whenever a radio connection exists. The procedure can be included in other procedures, e.g. through the means of optional parameters. The execution of this function is left to the network operator. When a new TMSI is allocated to an MS the network must prevent the old TMSI ... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3.6 Local TMSI unknown | This procedure is a variant of the procedure described in subclauses 2.3.1 and 2.3.2, and happens when a data loss has occurred in a VLR and when a MS uses an unknown TMSI, e.g. for a communication request or for a location updating request in a location area managed by the same VLR. This procedure is schematized in fi... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3.7 Location updating in a new VLR in case of a loss of information | This variant of the procedure described in 2.3.3 arises when the VLR in charge of the MS has suffered a loss of data. In that case the relation between TMSIo and IMSI is lost, and the identification of the MS in clear is necessary. The procedure is schematized in figure 2.7. ... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3.8 Unsuccessful TMSI allocation | If the MS does not acknowledge the allocation of a new TMSI, the network shall maintain the association between the old TMSI and the IMSI and between the new TMSI and the IMSI. For an MS-originated transaction, the network shall allow the MS to identify itself by either the old TMSI or the new TMSI. This will allow the... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 2.3.9 Combined location area updating with the routing area updating | This subclause is only applicable if GPRS is supported. This procedure is part of the location updating of a General Packet Radio Service (GPRS) class A or B mobile when the Gs-interface (SGSN MSC/VLR signalling interface) is implemented. This procedure is not relevant if the Gs-interface is not implemented. The locati... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 3 Subscriber identity authentication | |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 3.1 Generality | The definition and operational requirements of subscriber identity authentication are given in GSM 02.09. The authentication procedure will also be used to set the ciphering key (see clause 4). Therefore, it is performed after the subscriber identity (TMSI/IMSI) is known by the network and before the channel is encrypt... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 3.2 The authentication procedure | The authentication procedure consists of the following exchange between the fixed subsystem and the MS. - The fixed subsystem transmits a non-predictable number RAND to the MS. - The MS computes the signature of RAND, say SRES, using algorithm A3 and some secret information: the Individual Subscriber Authentication Key... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 3.3 Subscriber Authentication Key management | The Subscriber Authentication Key Ki is allocated, together with the IMSI, at subscription time. Ki is stored on the network side in the Home Public Land Mobile Network (HPLMN), in an Authentication Centre (AuC). A PLMN may contain one or more AuC. An AuC can be physically integrated with other functions, e.g. in a Hom... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 3.3.1 General authentication procedure | When needed for each MS, the BSS/MSC/VLR requests security related information from the HLR/AuC corresponding to the MS. This includes an array of pairs of corresponding RAND and SRES. These pairs are obtained by applying Algorithm A3 to each RAND and the key Ki as shown in figure 3.1. The pairs are stored in the VLR a... |
c26f502af59545c0bddf8ce8e94c7b28 | 100 929 | 3.3.2 Authentication at location updating in a new VLR, using TMSI | During location updating in a new VLR (VLRn), the procedure to get pairs for subsequent authentication may differ from that described in the previous subclause. In the case when identification is done using TMSI, pairs for authentication as part of security related information are given by the old VLR (VLRo). The old V... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.