hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
2.2.8.2.2 Multiple component errors
|
If a single Facility IE contains more than one component then a RELEASE COMPLETE message with the cause "Facility rejected" and without any component shall be sent. ETSI TS 100 941 V6.0.1 (1998-07) 16 GSM 04.10 version 6.0.1 Release 1997
|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3 Supplementary service support procedures
| |
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3.1 General
|
This clause describes the supplementary service support procedures at the radio interface. These procedures are provided by the supplementary service support entity defined in GSM 04.07. The supplementary service support procedures provide the means to transfer messages for the call independent supplementary service procedures. These procedures are regarded as the user of the supplementary service support.
|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3.2 Supplementary service support establishment
|
At the beginning of each call independent supplementary service procedure a supplementary service support must be established.
|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3.2.1 Supplementary service support establishment at the originating side
|
If the entity that uses the supplementary support procedures wants to send a REGISTER message, the supplementary service support entity shall first request the establishment of an MM-connection. This MM-connection is established according to GSM 04.08 and 04.07. If the network is the initiating side then MM-connection establishment may involve paging the MS. The supplementary service support entity shall send the REGISTER message as the first CM-message on the MM-connection. The REGISTER message is sent to the corresponding peer entity on the MM-connection and the supplementary service support shall be regarded as being established. 3.2.2 Supplementary service support establishment at the terminating side At the terminating side a supplementary service support is regarded as being established when an MM-connection is established. According GSM 04.08 this can be ascertained by the receipt of the first message, with a new transaction identifier. For successful establishment of supplementary service support this message shall be a REGISTER message. If the terminating side wishes to reject the establishment of supplementary services support then it may be immediately initiate supplementary services support release (see subclause 3.4).
|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3.3 Supplementary service support information transfer phase
|
Upon the establishment of the supplementary service support both users may exchange FACILITY messages by use of the supplementary service support.
|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3.4 Supplementary service support release
|
At the end of each call independent supplementary service procedure the established supplementary service support is released. The side closing the transaction shall release the transaction by sending the RELEASE COMPLETE message to its corresponding peer entity. Both supplementary service support entities release the MM-connection locally. ETSI TS 100 941 V6.0.1 (1998-07) 17 GSM 04.10 version 6.0.1 Release 1997
|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3.5 Recovery procedures
|
The supplementary service support does not provide recovery procedures, i.e. the operations are transparent to the supplementary service support.
|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3.6 Message flow (single operation example)
|
This subclause contains examples of message flows for a single transaction consisting of a single operation. These examples may not show all possibilities.
|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3.6.1 Mobile station initiated supplementary service transaction
|
MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = Operation (Supplementary service code, Parameter(s))) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------------------ Facility (Return result = Operation (Parameter(s))) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) RELEASE COMPLETE (note) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - RELEASE COMPLETE (note) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > NOTE: To prevent transactions being kept open following exceptional cases, either side of the transaction may release it by sending a RELEASE COMPETE message without a Facility IE. Figure 3.1: Mobile station initiated supplementary service transaction ETSI TS 100 941 V6.0.1 (1998-07) 18 GSM 04.10 version 6.0.1 Release 1997
|
09d74d05684eb66f6a6137f7ddbe7123
|
100 941
|
3.6.2 Network initiated supplementary service transaction
|
MS Network REGISTER <------------------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = Operation (Supplementary service code, Parameter(s))) RELEASE COMPLETE ------------------------------------------------------------------------------------------------------------------------------------> Facility (Return result = Operation (Parameter(s))) RELEASE COMPLETE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> Facility (Return error (Error)) RELEASE COMPLETE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> Facility (Reject (Invoke_problem)) RELEASE COMPLETE (note 1, note 3) - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> RELEASE COMPLETE (note 3) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOTE 1: If the network initiated operation does not require a result, reject or error to be returned then the MS shall release the transaction by sending a RELEASE COMPLETE message without a Facility Information Element. NOTE 2: For network initiated unstructured SS data alternative procedures for connection release apply; refer to GSM 03.90 and GSM 04.90. NOTE 3: To prevent transactions being kept open following exceptional cases, either side of the transaction may release it by sending a RELEASE COMPETE message without a Facility IE. Figure 3.2: Network initiated supplementary service transaction ETSI TS 100 941 V6.0.1 (1998-07) 19 GSM 04.10 version 6.0.1 Release 1997 3.7 Handling of unknown, unforeseen, and erroneous protocol data
|
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 handling of unknown, unforeseen and erroneous protocol data by the receiving entity. The procedures are called "error handling procedures", but they also define a compatibility mechanism for future extension of the protocol. Most error handling procedures are mandatory in the MS, but optional in the network. Detailed error handling procedures may vary from PLMN to PLMN. In this subclause, the following terminology is used: - An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved" in GSM 04.80 or GSM 04.08. However, it is not a syntactical error if a type 4 IE specifies a length indicator greater than that defined. The component part of the Facility information element is handled by a separate mechanism, and errors in the component part are not covered by this subclause. The following procedures are listed in order of precedence. Handling of errors in the contents of the Facility IE is described in subclause 2.2.8, and is outside the scope of this subclause.
|
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 transaction that is in progress then the message shall be ignored. b) If a FACILITY message is received specifying a transaction identifier that is not recognized as relating to a call independent SS transaction that is in progress then a RELEASE COMPLETE message shall be sent with cause value #81 "invalid call reference value". c) If a REGISTER message is received specifying a transaction identifier that is not recognized as relating to a call independent SS transaction that is in progress and with a transaction identifier flag incorrectly set to "1", this message shall be ignored. The network may follow the same procedures. ETSI TS 100 941 V6.0.1 (1998-07) 20 GSM 04.10 version 6.0.1 Release 1997
|
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 COMPLETE message shall be sent with cause value #98 "message not compatible with control state". The network may follow the same procedures.
|
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 "comprehension required"; is received, the MS shall proceed as follows: a) If the message is not RELEASE COMPLETE it shall send a RELEASE COMPLETE message with cause "#96 - Invalid mandatory information". b) If the message is RELEASE COMPLETE, it shall be treated as a normal RELEASE COMPLETE message. The network may follow the same procedures.
|
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 repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. The network may follow the same procedures.
|
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". The network may follow the same procedure. ETSI TS 100 941 V6.0.1 (1998-07) 22 GSM 04.10 version 6.0.1 Release 1997
|
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 component is embedded in a FACILITY message, since the password check procedure is always invoked during an existing transaction. The MS will return to the network the required password in the return result component of the operation. This return result component is embedded in a FACILITY message, see figure 4.1. If the provided password is right the password check procedure returns to the parent procedure an indication of successful password check. MS Network REGISTER (note) ===========================================================================> Facility FACILITY <------------------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = GetPassword (GuidanceInfo = "password")) FACILITY ------------------------------------------------------------------------------------------------------------------------------------> Facility (Return result = GetPassword (Password)) RELEASE COMPLETE (note) <=========================================================================== NOTE: This message is part of the initiating SS operation. Figure 4.1: Password check: successful procedure
|
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 component indicating "Negative Password Check". The counter is reset as soon as the right password is returned. If the served mobile subscriber enters a wrong call barring "password" three consecutive times, the subscription option "control of services" is set to "by the service provider" in the network: thus the network makes the use of password impossible for any subscriber operation. The password check procedure returns to the parent procedure an indication of Password Attempts Violation. The password can be made valid by the service provider only. ETSI TS 100 941 V6.0.1 (1998-07) 23 GSM 04.10 version 6.0.1 Release 1997
|
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 the mobile subscriber wants to register a new password the old password, the new password and the repeat of the new password shall be entered into the MS. Then the MS sends to the network an invoke component of the operation "register password". The common SS-code for call restriction services shall be used, but if the service code is not entered by the user the MS shall include the SS-code referring to all supplementary services.
|
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 operation "get password" with "new password?" as the value of the mandatory GuidanceInfo information element. This invoke component is embedded in a FACILITY message. The MS will return to the network the required new password in the return result component of the operation. This return result component is embedded in a FACILITY message; - the network sends thirdly to the MS an invoke component of the operation "get password" with "new password again?" as the value of the mandatory GuidanceInfo information element. This invoke component is embedded in a FACILITY message. The MS will return again to the network the required new password in the return result component of the operation. This return result component is embedded in a FACILITY message. If the two values of the provided passwords are identical, the network confirms the registration of the new password by sending to the MS the return result component of the operation "register password", with the new password as a mandatory information element, see figure 4.2.
|
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 the error value "SS_SubscriptionViolation". If the counter is larger than three, the error value "Password Attempts Violation" is returned. If the password check procedure returns an indication of negative password check, the network will send to the MS a return error component of the operation "register password" with the error value "negativePasswordCheck". If the new password is not repeated twice identically by the mobile subscriber, the network returns to the MS an error component of the "register password" operation with the error value "passwordRegistrationFailure". The diagnostic "newPasswordsMismatch" may be passed as an error parameter. The old password remains registered. If no result is returned by the MS for the "Get password" operation invoked by the network the "register password" procedure is terminated, and the old password remains registered. ETSI TS 100 941 V6.0.1 (1998-07) 24 GSM 04.10 version 6.0.1 Release 1997 If the format of a new password which is returned by the MS is invalid (e.g. the value does not belong to the [0000-9999] range), the network sends to the MS an error component of the "register password" operation with the error value "passwordRegistrationFailure". The diagnostic "invalidFormat" may be passed as an error parameter. The old password remains registered. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = Register Password (SS-Code)) FACILITY <------------------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = GetPassword (GuidanceInfo = "password")) FACILITY ------------------------------------------------------------------------------------------------------------------------------------> Facility (Return result = GetPassword (Password)) FACILITY <------------------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = GetPassword (GuidanceInfo = "new password")) FACILITY ------------------------------------------------------------------------------------------------------------------------------------> Facility (Return result = GetPassword (Password)) FACILITY <------------------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = GetPassword (GuidanceInfo = "new password again")) FACILITY ------------------------------------------------------------------------------------------------------------------------------------> Facility (Return result = GetPassword (Password)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------------------ Facility(Return result = Register Password (Password)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The figure illustrates successful outcome only. In case of input errors by the mobile subscriber, the information flow may be interrupted as defined in GSM 03.11. Figure 4.2: Password registration procedure ETSI TS 100 941 V6.0.1 (1998-07) 25 GSM 04.10 version 6.0.1 Release 1997
|
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 the guidance values "badPW-TryAgain" or "badPW-FormatTryAgain" it shall release the transaction and notify the mobile user in the same way as if the error value "negativePasswordCheck" has been returned by the network in reply to the parent operation.
|
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 versions of the standards to have to interwork. This clause describes the supplementary service procedures which provide this interworking. This clause describes compatibility procedures for radio interface SS operations. In this clause the term "SS operation" refers to one of the operations sent in the Facility IE as defined in GSM 04.80 and GSM 09.02. An "MS initiated operation" is an SS operation where the MS sends the invoke component. A corresponding definition applies to network initiated operations.
|
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 guarantee the best quality of service in situations where different entities support different versions of that service.
|
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 provides compatibility. The basic philosophy is that the MS shall provide the network with information about its capabilities in order that the network may adjust to the capabilities of the MS. This ensures that compatible information is sent to the MS. This process is not required in the other direction, i.e. the network does not provide the MS with capability information. The network is expected to be able to cope with unexpected information cleanly and due to network evolution will generally be more advanced than operating MSs. In this description the terms "phase" and "version" are used with respect to supplementary services. In this context "phase" means a particular collection of GSM standards or an implementation according to that phase of standards. In each phase of GSM standards "versions" of a service or protocol are described. Therefore it is sometimes applicable to refer to which version of a service is supported. ETSI TS 100 941 V6.0.1 (1998-07) 26 GSM 04.10 version 6.0.1 Release 1997
|
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 the scope of this standard. In general, MSs and networks should support complete implementations of supplementary services (e.g. mobile initiated USSD) including all elements that are not explicitly indicated as manufacturer or operator options. Complete support for a service also implies that the necessary compatibility indicators are set to appropriate values. If the MS or network does not implement all the elements necessary to support a service then the user may receive only a subset of the complete service. Such a MS or network is outside the scope of this standard and may: - provide a version of the service that is unpredictable or inconsistent; - fail to meet important service requirements; - be incompatible with other entities.
|
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 screening indicator is only relevant to network initiated SS operation and is valid for the duration of a radio connection. The coding of the SS screening indicator is described in GSM 04.08 and GSM 04.80.
|
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 operation to which it was attached (i.e. the validity of the invoke ID). For call independent SSs the indicator is valid for the duration of the call independent transaction. The SS version indicator takes precedence over the screening indicator during its period of validity. The coding of the SS version indicator is described in GSM 04.08 and GSM 04.80.
|
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 information, to reject the entire operation. ETSI TS 100 941 V6.0.1 (1998-07) 27 GSM 04.10 version 6.0.1 Release 1997
|
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 any supplementary service.
|
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 precedence over the screening indicator) the network shall check the screening indicator status. If the screening indicator was not sent, the network shall screen information sent to the MS, i.e. invoke the Phase 1 version of the operation or abort the invocation if only a Phase 2 version is available. If the screening indicator was received, indicating that Phase 2 error handling and extension mechanisms are supported at the MS, the network shall invoke the highest supported version of the operation toward the MS. According to this version of the standards the highest version is Phase 2. However when the next version of standards is available, new services may also be invoked. If the MS does not support the service the error handling or extension mechanism will handle unrecognised information cleanly. If in the future a new value is assigned to the screening indicator, new screening procedures may also be defined for networks of similar or higher capability. These procedures cannot be predicted and no definition is required in this version of the standards. If the value of the screening indicator is unrecognised the network shall attempt to handle network initiated SS operations as if the MS had indicated the highest values supported by the network. The indicator has been defined in such a way that it is ignored when received by a Phase 1 network therefore no Phase 1 procedures are described.
|
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 shall send the SS version indicator at the beginning of the transaction indicating the version of the SS operation being invoked. No further indication shall be sent by the MS during the transaction. No operations shall be sent within the same transaction which are not compliant with the SS version indicated. - in the case of call related activity, the MS shall send the SS version indicator in the GSM 04.08 message containing the invoke component of the related operation. The version of the service being invoked is indicated. This procedure applies on a per operation basis and shall be repeated for each call related operation. ETSI TS 100 941 V6.0.1 (1998-07) 28 GSM 04.10 version 6.0.1 Release 1997
|
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 SS version 3 or higher operation must be able to decode all of the possible returned information from the MAP Version 3 Application Context of the operation invoked. If an SS version 3 or higher operation has been initiated at the MS, then: - in the case of call independent activity, the MS shall send the SS version 3 or higher indicator at the beginning of the transaction indicating the version of the SS operation being invoked. No further indication shall be sent by the MS during the transaction. No operations shall be sent within the same transaction which are not compliant with the SS version indicated. - in the case of call related activity, the MS shall send the SS version 3 or higher indicator in the GSM 04.08 message containing the invoke component of the related operation. The version of the service being invoked is indicated. This procedure applies on a per operation basis and shall be repeated for each call related operation. ETSI TS 100 941 V6.0.1 (1998-07) 29 GSM 04.10 version 6.0.1 Release 1997
|
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 application context in the network for the processing of all operations made on that transaction. The network shall discard this information at the end of the transaction. If the indicator was not present the network shall operate according to Phase 1. If the indicator was present and indicates Phase 2 the network shall operate according to the Phase 2 standards. If the value of the indicator is unrecognised the network shall attempt to handle the communication at its highest possible version. The detailed interworking for this situation is described in subclause 5.5.4. The screening indicator shall not be taken into account for processing transactions that start with MS initiated operations. Special procedures concerning SS version indicator values other than Phase 2 will be described in future standards if required.
|
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 in a compatible way and set up compatible contexts in the fixed network. If the indicator was not present the network shall operate according to Phase 1. If the indicator was present and indicates Phase 2 the network shall operate according to the Phase 2 standards. If the value of the indicator is unrecognised the network shall attempt to handle the communication at its highest possible version. The network shall discard the indicated information when the operation has been completed, i.e. when a result, error or reject is provided. If no response is expected to an operation the indicator is discarded immediately after the operation has been processed. The screening indicator shall not be taken into account for processing MS initiated operations. If the version indicator is received but no supplementary service information is supplied the network shall ignore the indicator. Special procedures concerning SS version indicator values other than Phase 2 will be described in future versions of the standards if required.
|
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 possible. If the MS signals a higher version than the MSC/VLR is capable of supporting, the MSC/VLR shall attempt to support service at the highest version which is supported. If this is not possible then the communication is rejected. Detailed interworking is described in GSM 09.11.
|
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 mandatory protocol elements or new operations shall cause an increment in the protocol version. This shall be reflected in the use of the SS version indicator. Amendments to the Phase 2 services shall specify in the relevant stage 3 specification which value of the SS version indicator to use for MS initiated operations. The extension mechanism shall be introduced wherever possible in new operations or new constructed data types of the common information element SS protocol. Care should also be taken that functional service changes are made in a backwards compatible manner. ETSI TS 100 941 V6.0.1 (1998-07) 31 GSM 04.10 version 6.0.1 Release 1997
|
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 independent SS transaction. The procedure shall create a new network initiated transaction. The new transaction may be used on its own, or in parallel with other call independent SS transactions. The message flow is shown in figure 6.1. MS Network REGISTER <------------------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardCheckSSIndication) RELEASE COMPLETE ------------------------------------------------------------------------------------------------------------------------------------> Figure 6.1: ForwardCheckSSIndication sent on new transaction ETSI TS 100 941 V6.0.1 (1998-07) 32 GSM 04.10 version 6.0.1 Release 1997 Annex A (normative): Notation used for stage 3 description of supplementary services The structure of the signalling used for supplementary services on the Um Interface is defined using diagrams in GSM 04.10 and the GSM 04.8x and 04.9x-series of technical specifications. These SS stage 3 diagrams show example message flows between the MS and the network. Separate diagrams specify how supplementary services signalling shall be used to perform each defined supplementary service function. For signalling that uses the common information element approach, these diagrams are the normative definition of a number of important aspects of the supplementary services signalling: - the diagrams normatively define the allowed responses to each supplementary service operation shown; - the diagrams normatively define which GSM 04.08 or GSM 04.80 message is to be used to transport the supplementary services operations in the Facility IE; - The diagrams normatively define which parameters are allowed and required in the invocation and response of each operation. A.1 General structure of the SS stage 3 diagrams In the SS stage 3 diagrams the messages that correspond to the normal case with successful outcome are shown using solid arrows. Messages for exceptional, or unsuccessful cases are shown using dashed arrows. In general, the diagrams show the initiating operation together with all possible outcomes. Obviously, in practice only one of the possible outcomes shown in the diagrams will occur when the operation is used. An example is given in figure A.1. MS Network Initiating Operation ------------------------------------------------------------------------------------------------------------------------------------> Normal, Successful Outcome <------------------------------------------------------------------------------------------------------------------------------------ Unsuccessful Outcome 1 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Unsuccessful Outcome 2 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Figure A.1: Example of the general structure of the SS stage 3 diagrams ETSI TS 100 941 V6.0.1 (1998-07) 33 GSM 04.10 version 6.0.1 Release 1997 A.1.1 Exceptional release procedures To prevent transactions being kept open following exceptional cases, either side of the transaction may release it by sending a RELEASE COMPETE message without a Facility IE. This procedure can be used to release any call independent SS procedure, at any time while supplementary service support is established. For clarity this is not shown on the specific diagrams in the GSM 04.8x and 04.9x series, though it is still available. MS Network RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - or - RELEASE COMPLETE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> Figure A.2: Exceptional release procedures A.2 Messages used to transport operations The message used to transport the supplementary service operation is shown above the arrow. If a single message or a list of messages is specified then only these messages shall be used to transport the operation shown in the context shown. If the letters "e.g." are included before the message name or a list of messages then the messages shown are only suggested examples. If "e.g." is used then any message that carries the Facility information element which is consistent with the transaction state may be used for the SS operation. ETSI TS 100 941 V6.0.1 (1998-07) 34 GSM 04.10 version 6.0.1 Release 1997 A.3 Contents of messages The contents of messages is specified below the arrow. The diagrams do not show the SS version indicator, or other parts of the message contents unless they are directly related to the service shown. The names of relevant information elements are shown, and the associated contents is shown in brackets. If the information element is the Facility IE then the contents information includes: - the type of component that shall be used for the operation (e.g. invoke, return result, return error, reject); - the name of the operation to be used (for the invoke and return result components only); - the parameters that shall be included in the operation. For the function described by the diagram, only those parameters shown in the diagram are allowed. Unless stated otherwise all the parameters shown in the diagram shall be present when the operation is used for the function described by the diagram. The detailed encoding of the operations and parameters shown in the diagrams is defined in GSM 04.80 and GSM 09.02. Appropriate ASN.1 structures from these specifications shall be used to align with the diagrams. The examples in figure A.2 illustrate the encoding. The first example shows a common information element operation where the operation name is shown. The second example shows a common information element operation where the operation name is not shown. Items in italics would be substituted with the appropriate identifiers. MESSAGE NAME ------------------------------------------------------------------------------------------------------------------------------------> Facility (Component Type = OperationName (parameters)) MESSAGE NAME ------------------------------------------------------------------------------------------------------------------------------------> Facility (Component Type (parameters)) Figure A.2: Examples of the contents of messages ETSI TS 100 941 V6.0.1 (1998-07) 35 GSM 04.10 version 6.0.1 Release 1997 Annex B (informative): Status of Technical Specification GSM 04.10 Status of Technical Specification GSM 04.10 Date Version Remarks Release 92 3.2.3 Last common Phase 1/Phase 2 version June 1991 4.0.0 CR 04.10-13 rev 2 (category D) / CR 04.10-14 rev 1 (category D) CR 04.10-18 (category C) / CR 04.10-19 rev 1 (category B); all approved by GSM#31 April 1992 4.1.0 CR 04.10-22 (category C) / CR 04.10-24 rev 1 (category D) CR 04.10-25 (category D) / CR 04.10-27 (category D; all approved by SMG#02 January 1993 4.2.0 CR 04.10-31 (category D) / CR 04.10-32 rev 2 (category C) CR 04.10-33 rev 1 (category C); all approved by SMG#05 April 1993 4.3.0 CR 04.10-28 rev 3 (category B) / CR 04.10-29 rev 2 (category B) CR 04.10-36 rev 1 (category B) / CR 04.10-37 rev 1 (category C) CR 04.10-38 rev 1 (category C) / CR 04.10-39 (category D) CR 04.10-40 rev 1 (category C); all approved by SMG#06 June 1993 4.4.0 CR 04.10-43 rev 3 (category D) / CR 04.10-45 (category B) CR 04.10-46 (category B); all approved by SMG#07 TS frozen for Phase 2 by SMG#07 October 1993 4.5.0 CR 04.10-47 rev 1 (category F) approved by SMG#08 TS changed to draft prETS 300 558 January 1994 4.6.0 CR 04.10-48 rev 2 (category F) CR 04.10-49 (category F)approved by SMG#09 April 1994 4.7.0 CR 04.10-51 (category F) CR 04.10-52 rev 1 (category F)approved by SMG#10 July 1994 4.8.0 CR 04.10-54 rev 1 (category F) approved by SMG#11 October 1994 4.8.1 TS changed to final draft prETS 300 558 January 1995 4.8.2 TS changed to ETS 300 558 First edition January 1995 Amend ment 1 AR 04.10-A001 rev 1 (category 2) approved by SMG#13 AR 04.10-A002 rev 1 (category 2) ----->Version 4.9.0 February 1996 4.10.0 CR 04.10-A004 rev 1 (category F) approved by SMG#17 August 1996 4.10.1 TS changed to ETS 300 558 Second edition December 1996 5.0.0 TS changed to draft prETS 300 941 (Release 96) May 1997 5.0.1 TS changed to ETS 300 941 first edition March 1998 6.0.0 CR 04.10-A005r3 (CCBS and TEI R97) CR 04.10-A006 (TEI R97); all approved SMG#25 Specification converted to version 6.0.0 for Release 97 July 1998 6.0.1 Specification published as TS 100 941 Text and figures: WinWord 7.0 Stylesheet: etsiw_70.dot Rapporteur: Ian Sharp (Nortel) ETSI TS 100 941 V6.0.1 (1998-07) 36 GSM 04.10 version 6.0.1 Release 1997 History Document history V6.0.1 July 1998 Publication ISBN 2-7437-2417-X Dépôt légal : Juillet 1998
|
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-series. It also specifies the format of signalling channels and the order of bit transmission. As far as possible, the present document makes use of the layering principles of the Reference Model for Open System Interconnection (OSI) as contained in CCITT Recommendations X.200 and X.210.
|
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. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.11: "Digital cellular telecommunications system (Phase 2+); Service accessibility". [3] GSM 03.13: "Digital cellular telecommunications system (Phase 2+); Discontinuous Reception (DRX) in the GSM system". [4] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions". [5] GSM 04.01: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; General aspects and principles". [6] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [7] GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface Channel structures and access capabilities". [8] GSM 04.05: "Digital cellular telecommunications system (Phase 2+); Data Link (DL) layer General aspects". [9] GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". [10] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [11] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [12] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 Supplementary services specification; General aspects". ETSI ETSI TS 100 936 V7.0.0 (1999-08) 6 (GSM 04.04 version 7.0.0 Release 1998) [13] GSM 04.11: "Digital cellular telecommunications system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". [14] GSM 04.12: "Digital cellular telecommunications system (Phase 2+); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". [15] GSM 04.13: "Digital cellular telecommunications system (Phase 2+); Performance requirements on mobile radio interface". [16] GSM 04.21: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Mobile Station - Base Station System (MS - BSS) Interface". [17] GSM 04.22: "Digital cellular telecommunications system (Phase 2+); Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [17a] GSM 04.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station - Base Station System (MS-BSS) interface; Radio Link Control and Medium Access Control (RLC/MAC) layer specification". [18] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". [19] GSM 04.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 3". [20] GSM 04.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 3". [21] GSM 04.83: "Digital cellular telecommunications system; Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". [22] GSM 04.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 3". [23] GSM 04.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 3". [24] GSM 04.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 3". [25] GSM 04.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 3". [26] GSM 04.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Services Data (USSD) - Stage 3". [27] GSM 05.01: "Digital cellular telecommunications system (Phase 2+); Physical layer on the radio path; General description". [28] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". [29] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". [30] GSM 05.04: "Digital cellular telecommunications system (Phase 2+); Modulation". [31] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". [32] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". [33] GSM 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronization". ETSI ETSI TS 100 936 V7.0.0 (1999-08) 7 (GSM 04.04 version 7.0.0 Release 1998) [34] GSM 05.90: "Digital cellular telecommunications system; GSM Electro Magnetic Compatibility (EMC) considerations". [35] CCITT Recommendation X.200: "Reference Model of open systems interconnection for CCITT applications". [36] CCITT Recommendation X.210: "Open systems interconnection layer service definition conventions".
|
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 application the physical layer may also be referred to as the radio subsystem. However, the radio subsystem supports functions additional to those described in the present document. The physical layer interfaces the Data Link Layer, the Radio Link Control and Medium Access Control layer and the supported functional units of the application (figure 2.1). Physical Layer Data Link Layer RLC/MAC layer Radio Resource management (layer 3) to other functional units to upper layers MPH- primitives PH- primitives PH- primitives TCH Figure 2.1: Interfaces with the Physical Layer
|
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. NOTE: The terms physical layer and layer 1, and data link layer and layer 2, will be used synonymously in the present document. The PH-primitives exchanged between the physical layer and the data link layer are used for the transfer of layer 2 frames. They are also used to indicate the establishment of channels to layer 2. ETSI ETSI TS 100 936 V7.0.0 (1999-08) 8 (GSM 04.04 version 7.0.0 Release 1998) 2.1a Interface to the Radio Link Control and Medium Access Control layer The physical layer interfaces the Radio Link Control and Medium Access Control (RLC/MAC) layer. On this interface packet data control channels and packet data traffic channels are supported. The RLC/MAC layer is specified in GSM 04.60. Communication between the Physical Layer and the RLC/MAC layer is in an abstract way performed by means of PH-primitives. They do not constrain implementations. The PH-primitives exchanged between the physical layer and the RLC/MAC layer are used for the transfer of RLC/MAC blocks. They are also used to indicate the establishment of packet data physical channels to the RLC/MAC layer.
|
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 assignment of channels, physical layer system information (including measurement results), etc.
|
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 a transmission service. General characteristics of the service obtained by applying the framework of the 05-series at the operation on the radio medium are described in this clause.
|
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 providing entity (in case this is the physical layer; commands related to the establishment and release of channels) and the transfer of data (in case of the physical layer; the transfer of bits). The physical layer service access points defined in the present document differ from the OSI physical layer Service Access Points; the layer 3 RR-management instead of the data link layer controls the SAPs (establishment and release of channels). ETSI ETSI TS 100 936 V7.0.0 (1999-08) 9 (GSM 04.04 version 7.0.0 Release 1998) transm ission m edium adjacent higher layer adjacent higher layer SAP SAP Figure 3.1: Service Access Point principle On the physical layer of the GSM system a SAP is defined between the physical layer and the data link layer for each control channel (figure 3.2). The characteristics of SAPs (channels) are listed in GSM 04.03. Physical layer BCCH PCH+AGCH RACH SDCCH SACCH FACCH Data Link Layer Figure 3.2: SAPs between the physical layer and the data link layer in the MS Moreover, on the physical layer of the GSM system a SAP is defined between the physical layer and the RLC/MAC layer for the packet data control channels and the packet data traffic channel (figure 3.2a). Multiplexing of these channels is controlled by the RLC/MAC layer, see GSM 04.60. The characteristics of channels are listed in GSM 04.03. Physical layer RLC/MAC layer PBCCH + PPCH + PAGCH + PRACH + PACCH + PDTCH Figure 3.2a: SAP between the physical layer and the RLC/MAC layer in the MS
|
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 "channels" mentioned in GSM 04.03 are "logical channels" according to the GSM 05-series (especially GSM 05.02). The "CCCH", a channel name commonly used in the 04-series, covers the logical channels of the type RACH, PCH and AGCH. Similarly, the “PCCCH” covers the logical channels of the type PPCH, PAGCH and PRACH . ETSI ETSI TS 100 936 V7.0.0 (1999-08) 10 (GSM 04.04 version 7.0.0 Release 1998) Logical channels are multiplexed on physical channels. Physical channels are the units scheduled on the radio medium. Some are reserved by the network for common use (e.g. a combination of CCCH and BCCH), others are assigned to dedicated connections with MSs (dedicated physical channels), or are assigned to a shared usage between MSs for packet switched data traffic (packet data physical channels). In time, the combination of logical channels used on an assigned physical channel may change. Allowed combinations of logical channels on a physical channel are defined in GSM 04.03. Data on SAPs of control channels is exchanged in discrete blocks with a size of 23 or 21 (SACCH) octets. Data on a SAP of packet data traffic channels is exchanged in discrete blocks with a size of 184, 271, 315 or 431 bits. Synchronization between layer 1 and layer 2 (data link layer) is provided for piggy-backing of RR (receive ready) frames, and the starting of timers (T200). See also GSM 04.06. Synchronization between the physical layer and the RLC/MAC layer is provided for the handling of timers, and the multiplexing of logical channels. See also GSM 04.60 . * Error detection: The physical layer offers an error protected transmission service, it includes error detection functions and to a lower level, error correction functions. Erroneous received frames are not offered to the data link layer or the RLC/MAC layer. The probability of one or more errors in a physical block transferred by the physical layer is defined in GSM 05.05. Due to not specified methods of quality detection, the probability of residual errors in transferred blocks may vary between implementations. * Encryption: Security related functions implemented at the physical layer are described in GSM 03.20. An overview of the functions specified in the 05-series which create the service of the physical layer can be found in GSM 05.01.
|
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 resources management of layer 3 (GSM 04.08). During operation on a dedicated physical channel, the physical layer measures the signals of neighbouring base stations and the signal quality of the used dedicated physical channel. Measurements are transferred to layer 3, measurement control information is offered by layer 3. - Establishment of packet data physical channels : Establishment of packet data physical channels on the physical layer is controlled by the radio resource management of layer 3. Packet access and the reservation of radio resource on packet data physical channels is controlled by the RLC/MAC layer in co-operation with layer 3 (GSM 04.60 and GSM 04.08). During operation on packet data physical channels, the physical layer measures the signals of neighbouring base stations and the signal quality of the used packet data physical channel. Measurements are transferred to layer 3, measurement control information is offered by layer 3. - cell/PLMN selection in idle mode or in packet mode: In idle mode or in packet mode, the physical layer selects the best cell with its BCCH/CCCH in close co-operation with layer 3, meeting requirements for PLMN selection specified in GSM 02.11. The idle mode procedures are not modelled within the present document. Examples of procedures for cell selection are described in GSM 05.08. The physical layer performs automatic crossover.
|
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 control between the physical layer and adjacent layers. They do not specify or constrain implementations. The interactions between the physical layer and layer 1 entities for Bm/Lm channels are for further study. For the physical layer two sets of primitives are defined: ETSI ETSI TS 100 936 V7.0.0 (1999-08) 11 (GSM 04.04 version 7.0.0 Release 1998) - Primitives between physical layer and data link layer and RLC/MAC layer respectively: PH - Generic name - Type: Parameters. - Primitives between layer 1 and the RR-management layer 3 entity: MPH - Generic name - Type: Parameters. 4.1 Generic names of primitives between layers 1 and 2 for the transfer of layer 2 frames and RLC/MAC blocks The following primitive generic names are defined on the SAPs between the physical layer and the data link layer: a) PH-DATA: The PH-DATA primitives are used on a SAP to pass message units containing frames used for data link layer and RLC/MAC layer respective peer-to-peer communications to and from the physical layer. b) PH-RANDOM ACCESS: The PH-RANDOM ACCESS (PH-RA) primitives are used on the SAP of the RACH and the PRACH to request and confirm (in the MS) the sending of a random access frame and to indicate (in the network) the arrival of a random access frame. The random access protocols are specified in GSM 04.08 and GSM 04.60 respectively. c) PH-CONNECT: The PH-CONNECT primitive is used on a SAP to indicate that the physical connection on the corresponding control channel or packet data physical channel has been established. d) PH-READY-TO-SEND: The PH-READY-TO-SEND primitive is used by the physical layer to trigger, if applicable, piggy backing, the start of timer for the data link layer or the RLC/MAC layer and the forwarding a data unit to the physical layer. It is passed to the upper layer just before a new physical block is transmitted. e) PH-EMPTY-FRAME: The PH-EMPTY-FRAME primitive can be used by the data link layer and the RLC/MAC layer to indicate that no frame has to be transmitted after receiving the PH-READY-TO-SEND primitive. It enables polling of several upper layer entities by the physical layer and support DTX. 4.2 Generic names of primitives between layer 1 and the RR- management entity of layer 3 The following primitive generic name is defined between layer 1 and the RR-management entity of layer 3: - MPH-INFORMATION: MPH-INFORMATION (MPH-INFO) primitives are used for the control of the physical layer by the RR-management of layer 3. This information activates and deactivates, configures and deconfigures, through connects and disconnects physical and logical channels. It is also used for the transfer of measurements and measurement control information from layer 1 to layer 3.
|
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 providing a service to notify the next higher layer of activities in the layer. This activities are directly related to the occurrence of a REQUEST primitive on the peer-protocol side. c) RESPONSE: The RESPONSE primitive type is used by a layer to acknowledge receipt from the INDICATION primitive type. d) CONFIRM: The CONFIRM primitive type is used by the layer providing the requested service to confirm that the activity has been completed.
|
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-INFO-CON MS/BS PH(L1) RR(L3) x x MPH-INFO-IND MS/BS PH(L1) RR(L3) x x x PH-CONNECT-IND MS/BS PH(L1) DL(L2) RLC/MAC x PH-READY-TO- SEND MS/BS PH(L1) DL(L2) RLC/MAC x x PH-EMPTY-FRAME MS/BS DL(L2) RLC/MAC PH(L1) x PH-DATA-REQ MS/BS DL(L2) RLC/MAC PH(L1) x x PH-DATA-IND MS/BS PH(L1) DL(L2) RLC/MAC x x x PH-RA-REQ MS DL(L2) RLC/MAC PH(L1) x PH-RA-IND BS PH(L1) DL(L2) RLC/MAC x x PH-RA-CON MS PH(L1) DL(L2) RLC/MAC x x Parameters involved in the primitive exchange with the physical layer are: a) Message unit: The message unit contains peer-to-peer information of a layer. It is transferred by the physical layer to the peer layer. ETSI ETSI TS 100 936 V7.0.0 (1999-08) 13 (GSM 04.04 version 7.0.0 Release 1998) b) Channel control parameters: These parameters contain information for channel control, specified in GSM 04.08 and GSM 04.60. c) System information: This information is exchanged in the cell/PLMN selection procedures. It may also contain control information for DRX (sleep mode, see GSM 03.13). d) Absolute Frame Number: The absolute frame number is used (in combination with a random access identifier) to uniquely identify a random access. e) Measurements: This parameter is used to report the quality of a dedicated physical channel (MS and network) and to report the quality of surrounding BCCH carriers (MS only).
|
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 physical channel or packet data physical channel; DCH: the physical layer has seized a respective dedicated physical channel or packet data physical channel and may establish and through connect logical channels. NOTE: BCH = Bcch/ccch physical CHannel or pbcch/pccch physical channel; DCH = Dedicated physical CHannel or packet data physical channel. Figure 5.1 gives a general state diagram of the physical layer. All state transitions of the physical layer are controlled by MPH-INFORMATION primitives. ETSI ETSI TS 100 936 V7.0.0 (1999-08) 14 (GSM 04.04 version 7.0.0 Release 1998) NULL BCH SEARCHING BCH TUNING DCH DCH idle mode packet wait state dedicated mode packet transfer state Figure 5.1: States of the physical layer in the MS The states of the physical layer in the network are not specified. The states in the network will reflect the other characteristics of operation on channels.
|
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/PBCCH. This system information of the BCCH/PBCCH is used in the selection process.
|
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 applicable, on the corresponding SAP. On an established full duplex control channel (DCCHs) in both MS and network, on an established packet data physical channel or on the established BCCH/CCCH in the MS, physical blocks received correctly are offered on the corresponding SAP in PH-DATA-INDICATION primitives. On a full duplex control channel (DCCHs) or on the BCCH/CCCH in the network, the data link layer will offer physical blocks to be transmitted in PH-DATA-REQUEST primitives. On a packet data physical channel, the RLC/MAC layer will offer physical blocks to be transmitted in PH-DATA-REQUEST primitives. In the MS in idle mode or in packet wait state, random accesses on RACH or on PRACH can be offered in PH-RANDOM ACCESS-REQUEST primitives. The physical layer of the MS will perform a random access as soon as possible. The physical layer of the MS will confirm the data link layer or the RLC/MAC layer, the one which is applicable, the transmission of the random access attempt in a PH-RANDOM ACCESS-CONFIRM. This confirmation contains the absolute frame number in which the random access is transmitted. The physical layer of the BS offers correctly received random accesses to the data link layer or the RLC/MAC layer, the one which is applicable, in a PH-RANDOM ACCESS-INDICATION. This indication contains the absolute frame number in which the random access is received. ETSI ETSI TS 100 936 V7.0.0 (1999-08) 15 (GSM 04.04 version 7.0.0 Release 1998)
|
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 blocks transferred via the SACCH, a logical channel always present on a dedicated physical channel. Further more, a 16 octet information field is defined on downlink blocks transferred via the PTCCH, a logical channel present on a packet data physical channel .
|
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 fields are specified in GSM 05.10. The numbers corresponding to the timing advance steps in GSM 05.10 are included binary coded in the 7 bit ordered and actual timing advance fields of the physical layer header. The bit pattern "1111111" indicates that the field does not contain a timing advance value. All other bit combinations (64 to 126 decimal) are reserved. A MS in packet transfer state which is assigned a TAI shall, when receiving a PTCCH downlink block on the packet data physical channel containing PACCH, read the corresponding ordered timing advance field in that PTCCH block. The ordered timing advance fields corresponding to other TAIs than the assigned one shall be ignored .
|
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 : : : : : : layer 2 frame octet 23 NOTE: The numbering convention specified in GSM 04.06 applies. Figure 7.1: SACCH downlink block format
|
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 Actual timing advance octet 2 octet octet 3 numbering 21 octets V : : : : : : layer 2 frame octet 23 NOTE: The numbering convention specified in GSM 04.06 applies. Figure 7.2: SACCH uplink block format
|
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/SDCCH/BCCH/CCCH/CBCH downlink block format
|
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 block format ETSI ETSI TS 100 936 V7.0.0 (1999-08) 17 (GSM 04.04 version 7.0.0 Release 1998) 7.5 PBCCH/PCCCH downlink/PACCH/PDTCH block type 1 (CS-1) format The originally 184 bit (23 octets) blocks are used in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 octet 1 184 bit : : : : : : RLC/MAC block octet 23 NOTE: The numbering convention specified in GSM 04.60 applies. Figure 7.5: PBCCH/PCCCH downlink/PACCH/PDTCH block type 1 (CS-1) format
|
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 ETSI ETSI TS 100 936 V7.0.0 (1999-08) 18 (GSM 04.04 version 7.0.0 Release 1998)
|
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) format
|
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 7.9 PRACH uplink/PACCH uplink short acknowledgement block formats Two alternative PRACH uplink/PACCH uplink short acknowledgement 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 bit RLC/MAC block octet 1 NOTE: The numbering convention specified in GSM 04.60 applies. Figure 7.9 (sheet 1 of 2): PRACH uplink/PACCH uplink short acknowledgement block format ETSI ETSI TS 100 936 V7.0.0 (1999-08) 19 (GSM 04.04 version 7.0.0 Release 1998) The originally 11 bit blocks are used uplink in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 11 bit RLC/MAC block octet 1 octet 2 NOTE: The numbering convention specified in GSM 04.60 applies. Figure 7.9 (sheet 2 of 2): PRACH uplink/PACCH uplink short acknowledgement block 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 : : : : : : Spare Ordered timing advance for MS assigned TAI = 15 octet 16 7 octet 17 octets : : : : : : fill octets: "00101011" octet 23 Figure 7.10: PTCCH downlink block format The field mapping convention in this sub-clause is that when a field is contained within a single octet, the highest bit number of the field represents the highest order value and lowest bit number of the field represents the lowest order value. Spare bits are encoded with the binary value "0". Fill octets are encoded with the binary value "00101011". ETSI ETSI TS 100 936 V7.0.0 (1999-08) 20 (GSM 04.04 version 7.0.0 Release 1998)
|
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 The originally 11 bit blocks are used uplink in the following way: <---------------------------------------------------------------------------------- 8 7 6 5 4 3 2 1 11 fixed bits: "11111111111" octet 1 octet 2 Figure 7.11 (sheet 2 of 2): PTCCH uplink block format The field mapping convention of sub-clause 7.10 applies. In the addition, when a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. In that part of a field contained in a given octet the lowest bit number represents the lowest order value.
|
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 transmission having a block format with a non-integer number of octets, or for transmission having a defined block format but which does not follow the normal burst transmission, the octets are mapped onto M bits, d(0) to d(M-1), defined in GSM 05.03 clause 5 as follows: Bit m of octet n shall be transmitted as bit d(8(n-1) + m-1) with n = (1 .. ((M-1) DIV 8) + 1)) and m = (1 .. min (8, (M - 8(n-1))), and where 'DIV' is the integer division operator.
|
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 being a SACCH. - Packet mode : In this mode the MS is ready to access and operate on a packet data physical channel. The packet mode includes two sub-states: packet wait state and packet transfer state (see GSM 04.60). ETSI ETSI TS 100 936 V7.0.0 (1999-08) 21 (GSM 04.04 version 7.0.0 Release 1998) - Physical block: The physical block is the minimal unit which can be transferred by the physical layer. - Dedicated physical channel: The physical blocks scheduled on the radio medium assigned to a dedicated connection with a MS. - Packet data physical channel : The physical blocks scheduled on the radio medium assigned to a shared usage between MSs for packet switched data traffic. ETSI ETSI TS 100 936 V7.0.0 (1999-08) 22 (GSM 04.04 version 7.0.0 Release 1998) Annex A (informative): Document change history SPEC SMG# CR PHASE VERS NEW_VERS SUBJECT 04.04 s24 A001 R97 5.0.1 6.0.0 Introduction of GPRS 04.04 s29 R98 7.0.0 Specification version upgrade to Release 1998 version 7.0.0 ETSI ETSI TS 100 936 V7.0.0 (1999-08) 23 (GSM 04.04 version 7.0.0 Release 1998) History Document history V7.0.0 August 1999 Publication ISBN 2-7437-3344-6 Dépôt légal : Août 1999
|
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 cryptological algorithm or mechanism is needed, this is signalled with a reference to annex C. The references refers only to functionalities, and some algorithms may be identical or use common hardware.
|
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. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 01.61: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements". [3] GSM 02.07: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) features". [4] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects". [5] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber Identity Modules (SIM) Functional characteristics". [6] GSM 02.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephone System (CTS) Phase 1; Service Description; Stage 1". [7] GSM 02.60: " Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 1". [8] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". [9] GSM 03.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephone System (CTS), Phase 1; CTS Architecture Description; Stage 2". [10] GSM 03.60: " Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 2" [11] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [12] GSM 04.64: " Digital cellular telecommunications system (Phase 2+), General Packet Radio Service (GPRS); Logical Link Control (LLC)". ETSI ETSI TS 100 929 V7.2.0 (1999-11) 10 (GSM 03.20 version 7.2.0 Release 1998) [13] GSM 05.01: "Digital cellular telecommunication system (Phase 2+); Physical layer on the radio path; General description". [14] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". [15] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". [16] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". [17] GSM 11.11: "Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module- Mobile Equipment (SIM-ME) interface".
|
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 (ciphering). It shall be possible to introduce new authentication and ciphering algorithms during the systems lifetime. The fixed network may support more than one authentication and ciphering algorithm. The security procedures include mechanisms to enable recovery in event of signalling failures. These recovery procedures are designed to minimize the risk of a breach in the security of the system. General on figures in the present document: - In the figures below, signalling exchanges are referred to by functional names. The exact messages and message types are specified in GSM 04.08 and GSM 09.02. - No assumptions are made for function splitting between MSC (Mobile Switching Centre), VLR (Visitor Location Register) and BSS (Base Station System). Signalling is described directly between MS and the local network (i.e. BSS, MSC and VLR denoted in the figures by BSS/MSC/VLR). The splitting in annex A is given only for illustrative purposes. - Addressing fields are not given; all information relates to the signalling layer. The TMSI allows addressing schemes without IMSI, but the actual implementation is specified in the GSM 04-series. - The term HPLMN in the figures below is used as a general term which should be understood as HLR (Home Location Register) or AuC (Authentication Centre). - What is put in a box is not part of the described procedure but it is relevant to the understanding of the figure. ETSI ETSI TS 100 929 V7.2.0 (1999-11) 12 (GSM 03.20 version 7.2.0 Release 1998)
|
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 data and signalling and protection against the tracing of a user's location. The provision of this function implies that the IMSI (International Mobile Subscriber Identity), or any information allowing a listener to derive the IMSI easily, should not normally be transmitted in clear text in any signalling message on the radio path. Consequently, to obtain the required level of protection, it is necessary that: - a protected identifying method is normally used instead of the IMSI on the radio path; and - the IMSI is not normally used as addressing means on the radio path (see GSM 02.09); - when the signalling procedures permit it, signalling information elements that convey information about the mobile subscriber identity must be ciphered for transmission on the radio path. The identifying method is specified in the following subclause. The ciphering of communication over the radio path is specified in clause 4.
|
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 guidance for defining the format of a TMSI are specified in GSM 03.03. The network (e.g. a VLR) manages suitable data bases to keep the relation between TMSIs and IMSIs. When a TMSI is received with an LAI that does not correspond to the current VLR, the IMSI of the MS must be requested from the VLR in charge of the indicated location area if its address is known; otherwise the IMSI is requested from the MS. A new TMSI must be allocated at least in each location updating procedure. The allocation of a new TMSI corresponds implicitly for the MS to the de-allocation of the previous one. In the fixed part of the network, the cancellation of the record for an MS in a VLR implies the de-allocation of the corresponding TMSI. To cope with some malfunctioning, e.g. arising from a software failure, the fixed part of the network can require the identification of the MS in clear. This procedure is a breach in the provision of the service, and should be used only when necessary. When a new TMSI is allocated to an MS, it is transmitted to the MS in a ciphered mode. This ciphered mode is the same as defined in clause 4. The MS must store its current TMSI in a non volatile memory, together with the LAI, so that these data are not lost when the MS is switched off. ETSI ETSI TS 100 929 V7.2.0 (1999-11) 13 (GSM 03.20 version 7.2.0 Release 1998)
|
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 sends TMSIo as an identifying field at the beginning of the location updating procedure. The procedure is schematized in figure 2.1. !"! #"! $# % !&' !% ($!!') *$!+, )) ' # !%( , - '. &)! ! /!0 )) ' # Figure 2.1: Location updating in the same MSC area Signalling Functionalities: Management of means for new ciphering: The MS and BSS/MSC/VLR agree on means for ciphering signalling information elements, in particular to transmit TMSIn. ETSI ETSI TS 100 929 V7.2.0 (1999-11) 14 (GSM 03.20 version 7.2.0 Release 1998)
|
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. ! " #$%$" &%$ "'& ("$) * $( "#+'$$*, -'$./ ,, * " & " +" $/ $(+ "/+" $/ *01 "# 2! ! +" $/ *3" ),$ #$+" $/*3" ),$ #$ ! 2! 4$5 ,, * " & NOTE: From a security point of view, the order of the procedures is irrelevant. Figure 2.2: Location updating in a new MSCs area, within the same VLR area Signalling functionalities: Loc.Updating: stands for Location Updating The BSS/MSC/VLR indicates that the location of the MS must be updated. ETSI ETSI TS 100 929 V7.2.0 (1999-11) 15 (GSM 03.20 version 7.2.0 Release 1998)
|
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 identifying fields during the location updating procedure. The procedure is schematized in figure 2.3. 123 - !'4!)4 # !"! #"! $# % !& ' !% ($!!') *$!+, )) ' # !%( ,( !, '45 ( !, - '. &)! !( !,'. &)! !( !, - '!)) - /!0 )) ' # NOTE: From a security point of view, the order of the procedures is irrelevant. Figure 2.3: Location updating in a new VLR; old VLR reachable Signalling functionalities: Sec.Rel.Info.: Stands for Security Related information The MSC/VLRn needs some information for authentication and ciphering; this information is obtained from MSC/VLRo. Cancellation: The HLR indicates to VLRo that the MS is now under control of another VLR. The "old" TMSI is free for allocation. ETSI ETSI TS 100 929 V7.2.0 (1999-11) 16 (GSM 03.20 version 7.2.0 Release 1998)
|
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. " ! , " ($ * 6,$ $" 7$8-$' 2! ! " #$%$" &%$ "'& ("$) * $( "#+'$$*, -'$./ ,, * " & " $(+ "/+" $/ * "1 "#+" $/ 2! ! *3" ),$ #$+" $/*3" ),$ #$+" $/ ! 2! "*$,, " 2! 4$5 ,, * " & NOTE: From a security point of view, the order of the procedures is irrelevant. Figure 2.4: Location Updating in a new VLR; old VLR not reachable ETSI ETSI TS 100 929 V7.2.0 (1999-11) 17 (GSM 03.20 version 7.2.0 Release 1998)
|
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 from being allocated again until the MS has acknowledged the allocation of the new TMSI. If an IMSI record is deleted in the VLR by O&M action, the network must prevent any TMSI associated with the deleted IMSI record from being allocated again until a new TMSI is successfully allocated to that IMSI. If an IMSI record is deleted in the HLR by O&M action, it is not possible to prevent any TMSI associated with the IMSI record from being allocated again. However, if the MS whose IMSI record was deleted should attempt to access the network using the TMSI after the TMSI has been allocated to a different IMSI, then authentication or ciphering of the MS whose IMSI was deleted will almost certainly fail, which will cause the TMSI to be deleted from the MS. The case where allocation of a new TMSI is unsuccessful is described in subclause 2.3.8. This procedure is schematized in figure 2.5. ,, * " & " $(+ "/ 2! *3" ),$ #$ ! 4$5 ,, * " & Figure 2.5: Reallocation of a new TMSI ETSI ETSI TS 100 929 V7.2.0 (1999-11) 18 (GSM 03.20 version 7.2.0 Release 1998)
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.