hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.5.2 Short messages | Requirement: Service n°4 "allocated and activated". Request: The SIM seeks for the identified short message. If this message is found, the ME performs the reading procedure with EFSMS. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 107 (GSM 11.11 version 6.3.0 Release 1997) If service n°35 is "allocated and activated" and the s... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.5.3 Advice of Charge (AoC) | Requirement: Service n°5 "allocated and activated". Accumulated Call Meter. Request: The ME performs the reading procedure with EFACM. The SIM returns the last updated value of the ACM. Initialization: The ME performs the updating procedure with EFACM using the new initial value. Increasing: The ME performs the increas... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.5.4 Capability configuration parameters | Requirement: Service n°6 "allocated and activated". Request: The ME performs the reading procedure with EFCCP. Update: The ME performs the updating procedure with EFCCP. Erasure: The ME sends the identification of the requested information to be erased. The content of the identified record in EFCCP is marked as "free". |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.5.5 PLMN selector | Requirement: Service n°7 "allocated and activated". ETSI ETSI TS 100 977 V6.3.0 (2000-05) 108 (GSM 11.11 version 6.3.0 Release 1997) Request: The ME performs the reading procedure with EFPLMNsel. Update: The ME performs the updating procedure with EFPLMNsel. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.5.6 Cell broadcast message identifier | Requirement: Service n°14 "allocated and activated". Request: The ME performs the reading procedure with EFCBMI. Update: The ME performs the updating procedure with EFCBMI. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.5.7 Group identifier level 1 | Requirement: Service n°15 "allocated and activated". Request: The ME performs the reading procedure with EFGID1. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.5.8 Group identifier level 2 | Requirement: Service n°16 "allocated and activated". Request: The ME performs the reading procedure with EFGID2. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.5.9 Service Provider Name | Requirement: Service n°17 "allocated and activated". Request: The ME performs the reading procedure with EFSPN. 11.5.10 Voice Group Call Services Requirement: Service n°18 "allocated and activated". Voice Group Call Service Request: The ME performs the reading procedure with EFVGCS. Voice Group Call Service Status Requ... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.6 SIM Application Toolkit related procedures | SIM Application Toolkit is an optional feature. The higher level procedures, and contents and coding of the commands, are given in GSM 11.14 [27]. Procedures relating to the transmission of commands and responses across the SIM/ME interface are given in this section. A SIM or ME supporting SIM Application Toolkit shall... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.6.1 Initialization procedure | A SIM supporting SIM Application Toolkit shall indicate this through relevant data in EFPhase and EFSST, as defined in the relevant sections above. An ME supporting SIM Application Toolkit shall perform initialization as defined in the SIM Initialization section above. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.6.2 Proactive polling | An ME supporting proactive SIM (part of SIM Application Toolkit) shall support the polling procedure as defined above. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.6.3 Support of commands | A SIM or ME supporting SIM Application Toolkit shall support the commands TERMINAL PROFILE, ENVELOPE, FETCH and TERMINAL RESPONSE. These commands shall never be used if either the SIM or ME does not support SIM Application Toolkit. Therefore standard SIMs and MEs do not need to support these commands. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.6.4 Support of response codes | A SIM or ME supporting SIM Application Toolkit shall support the response status words (SW1 SW2) '91 XX', '93 00' and '9E XX. The SIM shall send '9E XX' only to an ME indicating in TERMINAL PROFILE that it supports the handling of these status words. These responses shall never be used if either the SIM or ME does not ... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.6.5 Command-response pairs | Using the terminology where the ME issues a command and the SIM a response, ending in status words SW1 SW2, a command-response pair is considered as a single transaction. Each transaction is initiated by the ME and terminated by the SIM. One transaction must be completed before the next one can be initiated. This proto... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.6.6 Independence of normal GSM and SIM Application Toolkit tasks | Normal GSM operation (relating to general, CHV related, GSM security related, and subscription related procedures) and SIM Application Toolkit operation shall be logically independent, both in the SIM and in the ME. Specifically, this means: - the currently selected EF and current record pointer in the normal GSM task ... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.6.7 Use of BUSY status response | If for any reason the SIM Application Toolkit task of the SIM cannot process an ENVELOPE command issued by the ME at present (e.g. other SIM Application Toolkit processes are already running, and this additional one would cause an overload), the SIM can respond with a status response of '93 00'. The ME may re-issue the... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 11.6.8 Use of NULL procedure byte | The NULL procedure byte provides a mechanism for the SIM to obtain more time before supplying the response part of a command-response pair, during which time the ME is unable to send further commands to the SIM. If a SIM Application Toolkit activity in the SIM runs for too long, this may prevent the ME from sending "no... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 1 Scope | The present document defines the rate adaptation functions to be used in GSM PLMN Mobile Stations (MS)s for adapting terminal interface data rates to the Mobile Station - Base Station System (MS-BSS) interface data rates in accordance with GSM 03.10 [3]. The provision of these functions will depend on the services a pa... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 2.1 Abbreviations and definitions | Abbreviations used in the present document are listed in GSM 01.04. Overall data stream: The data stream in those parts of the network where the data flow is not split into multiple channels. Substream: Stream of data with explicit or implicit numbering between splitter and combiner functions. Channel: A physical full ... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 3 General approach | GSM 03.10 defines the PLMN connection types necessary to support the GSM PLMN data and telematic services. Within the MS there are several different data rate adaptation functions - and a Split/Combine-function in case of a multislot data configuration - which are combined as shown in GSM 03.10 as part of the connectio... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 3.1 Overview of data rates and configurations | In Table 1, an overview of the supported transparent air-interface user rates is given. For each rate, also intermediate rates per channel between BTS and MSC, overall radio interface rates, and channel configurations are given. For single slot connections the intermediate rates are per channel carrying the overall dat... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 4 The RA0 Function | |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 4.1 Asynchronous-to-Synchronous Conversion (RA0) | The RA0 Function is only used with asynchronous interfaces. Incoming asynchronous data is padded by the addition of stop elements to fit the same or nearest higher synchronous rate defined by 2 to the power n ( where n≤6) times 600 bit/s, 14,4 kbit/s or 28,8 kbit/s. Thus both 75 bit/s and 300 bit/s user data signalling... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 4.2 Break signal | The RA0 shall detect and transmit the break signal in the following fashion: If the converter detects 2M to 2M+3 bits, all of start polarity, where M is the number of bits per character in the selected format including start and stops bits, the converter shall transmit 2M+3 bits of start polarity. If the converter dete... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 4.3 Overspeed/Underspeed | A RA0 shall insert additional stop elements when its associated terminal is transmitting with a lower than nominal character rate. If the terminal is transmitting characters with an overspeed of up to 1 %, the asynchronous-to- synchronous converter may delete stop elements as often as is necessary to a maximum of one f... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 4.4 Parity Bits | Possible parity bits included in the user data are considered as data bits by the RA0 function (and RA1 function). ETSI ETSI TS 100 945 V7.1.0 (2000-08) 11 (GSM 04.21 version 7.1.0 Release 1998) |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 4.5 Flow Control | Where applicable, this function is as specified in the relevant terminal adaptation function Specification (see GSM 07 series). |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 5 The RA1 Function | This function is used to adapt between the synchronous user rates, or the output of the RA0 function and the intermediate rate of 8, 16, 32 or 64 kbit/s. |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 5.1 Adaptation of synchronous data rates up to 38,4 kbit/s | Synchronous user rate Intermediate rate ≤2,4 kbit/s 8 kbit/s 4,8 kbit/s 8 kbit/s 9,6 kbit/s 16 kbit/s 14,4 kbit/s 32 kbit/s 19,2 kbit/s 32 kbit/s 28,8 kbit/s 64 kbit/s 38,4 kbit/s 64 kbit/s A CCITT V.110 80 bits frame is constructed using the user data bits received (from the RA0 in the asynchronous case), the values o... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 5.1.1 Network Independent Clocking | Synchronous data signals received by the MT from the DTE at the MS or by IWF from the modem on the PSTN may not be synchronized to the PLMN. The following method shall be used to enable transfer of those data signals and the corresponding bit timing information via the V.110 frames. Such a situation would exist where t... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 5.1.1.1 Multiframe Structure | The transmitting end of the GSM PLMN connection shall establish a multiframe structure utilizing bit E7 consisting of four frames by setting E7 in every fourth frame to binary 0. This structure is identical to the use of E7 in V.110 (and X.30) except that such a multiframe structure will exist for all user data rates. ... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 5.1.1.2 Encoding and compensation | The V.110 transmitter will use the following 5-bit code words, as shown in figure 2, to indicate the four possible states of compensation required for network independent clocking. c1 c2 c3 c4 c5 No compensation 1 1 1 1 1 Negative compensation 1 0 0 1 0 Positive compensation of a zero 0 1 0 0 1 Positive compensation of... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 6 The RA1'' function | The RA1'' function is used for converting between synchronous user rates of 48 and 56 kbit/s and the 'intermediate' rate of 64 kbit/s. (RA1'' is a GSM-specific term which is used for the one-step adaptation of 48 and 56 kbit/s rates into 64 kbit/s as specified in ITU-T V.110. For the purposes of GSM specifications the ... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 6.2 Rate adaptation of 56 kbit/s user rate to 64 kbit/s | A CCITT V.110 64 bits frame is constructed using the user data bits received. The CCITT V.110 64 bit frame shown in figure 14 is used. The D bits are used for conveying the user data. The order of transmission of the 64 bit frame is from left to right and top to bottom. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 14 (GSM 04.... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 7 The RA2 Function | This procedure is based on the RA2 function as specified in CCITT V.110. It is used to rate adapt to/from the intermediate rates of 8, 16 or 32 kbit/s from/to the 64 kbit/s rate used at the S interface. Intermediate rate Rate at the S interface 8 kbit/s 64 kbit/s 16 kbit/s 64 kbit/s 32 kbit/s 64 kbit/s 64 kbit/s 64 kbi... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8 The RA1/RA1' Function | The RA1/RA1' function is used in transparent cases to convert between the intermediate rate and the input rate to the channel coder function for transmission over the radio interface. This conversion also appears on the infrastructure side in both transparent and non-transparent cases as specified in GSM 08.20 except f... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.1 Single slot rates | Intermediate rate Radio interface rate 8 kbit/s 3,6 kbit/s 8 kbit/s 6 kbit/s 16 kbit/s 12 kbit/s 32 kbit/s 14,5 kbit/s There are four data rates (known as Radio Interface rates) used for data transfer to the channel coder. These are 14,5 kbit/s, 12 kbit/s, 6 kbit/s and 3.6 kbit/s, and in order to adapt the 8,16, and 32... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.1.1 Radio interface rate of 14,5 kbit/s | In this case one modified CCITT V.110 frame is received/sent from/to the network every 2.5 ms (see GSM 05.03). The RA1/RA1' function adds/subtracts the 17-bit synchronisation pattern, the F-, E-, X-, and S-bits to/from the 80-bit V.110- frames. Bits M1 and M2 are transmitted along with the modified 36-bit V.110 frames ... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.1.1.1 Multiframe structure over the radio-interface | Bit M1 carries a 31-bit PN multiframe code 0000 1001 0110 0111 1100 0110 1110 101. One multiframe bit is transmitted every 20 ms, which means that one whole multiframe consists of 248 36-bit 2.5 ms frames. Bit M2 carries V.24 circuit status information, network independent clocking (NIC) information and substream numbe... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.1.2 Radio Interface rate of 12 kbit/s | In this case one modified CCITT V.110 60 bit frame is received/sent from/to the network every 5ms (see GSM 05.03 ). The RA1/RA1' function will add/subtract the 17 bit synchronization pattern and the E1,E2 and E3 bits to/from each CCITT V.110 80 bit frame as follows: The modified CCITT V.110 60 bits frame received/sent ... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.1.3 Void | |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.1.4 Radio Interface rate of 6 kbit/s | In this case one modified CCITT V.110 60 bit frame is received/sent from/to the network every 10 ms (see GSM 05.03). The RA1/RA1' function will add/subtract the 17 bit synchronization pattern and the E1,E2 and E3 bits to/from each CCITT V.110 80 bit frame as follows: The modified CCITT V.110 60 bits frame received/sent... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.1.5 Radio Interface rate of 3,6 kbit/s (transparent services only) | In this case one modified CCITT V.110 36 bit frame is received/sent from/to the network every 10ms (see GSM 05.03 [3]). The RA1/RA1' function will add/subtract the 17 bit synchronization pattern and the E1,E2 and E3 bits to/from each CCITT V.110 80 bit frame as follows: The modified CCITT V.110 36 bits frame received/s... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.1.6 Synchronisation | Two interfaces are involved in the TAF regarding the need for data frame synchronisation, i.e. the TAF/air-interface and TAF/TE interface. For detailed definition of the synchronisation procedures refer to GSM 07.01. |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.1.7 Idle frames | Whenever no data is received from the radio interface (e.g. frame stealing applies, layer 2 fill frames are received, etc.) idle frames shall be sent to the DTE. These are V.110 frames with frame alignment pattern according to CCITT recommendation. V.110 [11] and all data, status and E-bits set to binary "1". |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.2 Multislot rates | In multislot operation the transmission is performed using parallel substreams between the Split/Combine-functions. |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.2.1 TCH/F14.4 multislot operation | The information carried by the M2-sequences is read per substream; i.e. the substream number and a complete NIC-code are transferred through one substream. A NIC-code is carried on as many substreams as is necessary to cover all NIC-compensations that have taken place. On channels where no NIC-compensation is carried, ... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.2.6 AIUR of 56 kbit/s; Intermediate rate of 64 kbit/s; | Radio interface rate of 5 × 12 kbit/s One modified CCITT V.110 60 bit frame (Figure 10) is received/sent from/to the network every 5 ms (see GSM 05.03) resulting in an radio-interface rate of 12 kbit/s per channel. A modified CCITT V.110 60 bits radio-interface frame: D1 D2 D3 D4 D5 D6 T1 D7 D8 D9 D10 D11 D12 T2 D13 D1... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.2.8 AIUR of 64 kbit/s; Radio interface rate of 6 x 12 kbit/s | One modified CCITT V.110 60 bit frame (Figure 10) is received/sent from/to the network every 5 ms (see GSM 05.03) resulting in an radio-interface rate of 12 kbit/s per channel. A modified CCITT V.110 60 bits radio-interface frame: D1 D2 D3 D4 D5 D6 T1 D7 D8 D9 D10 D11 D12 T2 D13 D14 D15 D16 D17 D18 T3 D19 D20 D21 D22 D... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 8.2.9 AIUR of 64 kbit/s; Radio interface rate of 5 x 14,5 kbit/s | For AIUR 64 kbit/s the 64 data bits in the 64-bit V.110 frames are extracted and sent through the substreams in 36-bit frames as described in subclause 8.1. An M1/M2-bit pair is sent over the air-interface along each data block every 20 ms. This pair of bits carries the multiframe and substream numbering information as... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 9 The RA1' Function | This function is used to adapt between the synchronous user data rates, or the output of the RA0 function and the radio interface data rates of 3.6, 6, 12 or 14,5 kbit/s. |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 9.1 Synchronous user rates up to 9,6 kbit/s | Synchronous user rate Rate at the radio interface ≤2,4 kbit/s 3.6 kbit/s 4,8 kbit/s 6 kbit/s 9,6 kbit/s 12 kbit/s or 2x6 kbit/s The modified CCITT V.110 36 or 60 bit frame structures for each user rate are shown in figures 5 - 9. The meaning of the bits is described in clause 5. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 23... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 10 The Split/Combine and Padding-functions | These functions are associated with multislot connections. The Split/Combine function splits/recombines the overall data stream to/from the substreams. The Padding function inserts filling into one of the substreams in cases where the total capacity of the substreams is larger than necessary to achieve the required AIU... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 10.2 Substream numbering in transparent operation | In transparent multislot data configurations of more than one TCH/F the parallel data substreams between the Split/Combine-functions carry inband substream numbering. The status bits S1, S3, and the X-bit between data bits D12 and D13 (Figures 5 and 6) are used for transferring this substream numbering information (S1 ... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 10.2.1 Substream numbering for TCH/F14.4 channel coding | Bit M1 carries the multiframe sequence 0000 1001 0110 0111 1100 0110 1110 101. The number of the substream in which a multiframe is sent is carried four times in a 31-bit period of theM2-sequence. In the three-bit number code the bit in the lowest bit position is the MSB (See table in subclause 8.1.1.1). ETSI ETSI TS 1... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 10.3 Substream Synchronisation | Two interfaces are involved in the TAF regarding the need for the data frame synchronisation, i.e the TAF/multichannel interface and the TAF/TE interface. The Split/Combine function is responsible for controlling the synchronisation and resynchronisation procedures as described in GSM 07.01. |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 10.4 Network independent clocking | The data frames carrying an NIC-multiframe (subclause 5.1.1) indicating a positive or negative compensation are distributed into the substreams according to subclause 10.1. 10.4.1 Network Independent Clocking for TCH/F14.4 channel coding (both single- and multilinks) In the following, 'a data bit position' means a non-... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 10.4.1.1 Negative compensation | a) From overall data stream to substreams When only one substream is used and the data is mapped to the radio interface blocks, the 'extra null bit', which is set to '1', (subclause 5.1.1) is mapped to the first data bit position of the radio interface block which carries the fifth N-bit in the 31-block multiframe stru... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 10.4.1.2 Positive compensation | a) From overall data stream to substreams An NIC-code indicating positive compensation means that the data bit from the overall data stream preceeding the bit mapped into the first position of the data block conveying the second N-bit is carried encoded by the five N-bits. If more than one substream is used, and if mor... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 10.5.1 Padding for TCH/F14.4 channel coding | Padding for TCH/F14.4 channel coding is presented in the corresponding parts of clause 8. |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 10.6 Handling of the E1-E3 bits in multislot operation | Between the Split / Combine functions the substreams carry the code associated with the substream rate as defined in Figure 4. When the substreams are combined the code is set to correspond to the overall AIUR according to Figure 4. |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 11 Support of Non-Transparent Bearer Services | In the case of non-transparent services, the RA1' function provides access to the 12 and 6 kbit/s radio interface data rates. (Alignment of RLP frames with the four TDMA slots makes it physically impossible to provide 3,6 kbit/s.) The RA1' function is not applied in case of TCH/F14.4 channel coding (Radio interface rat... |
2bb426455d2411cdccbe99bd7277a7ab | 100 945 | 12 Figures on Frame structures | Octet No. Bit number 1 2 3 4 5 6 7 8 0 0 0 0 0 0 0 0 0 1 1 D1 D2 D3 D4 D5 D6 S1 2 1 D7 D8 D9 D10 D11 D12 X 3 1 D13 D14 D15 D16 D17 D18 S3 4 1 D19 D20 D21 D22 D23 D24 S4 5 1 E1 E2 E3 E4 E5 E6 E7 6 1 D25 D26 D27 D28 D29 D30 S6 7 1 D31 D32 D33 D34 D35 D36 X 8 1 D37 D38 D39 D40 D41 D42 S8 9 1 D43 D44 D45 D46 D47 D48 S9 Fig... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 1 Scope | In this specification the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.8x and 04.9x-series specify the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivat... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 1.1 Normative references | References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" befor... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 1.2 Abbreviations | Abbreviations used in this specification are listed in GSM 01.04. ETSI TS 100 941 V6.0.1 (1998-07) 9 GSM 04.10 version 6.0.1 Release 1997 2 Generic procedures for the control of supplementary services |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.1 Overview of the generic protocol and its scope | One generic protocol is defined for the control of supplementary services at the radio interface. This protocol operates at layer 3 of the radio interface and assumes the use of layers 1 and 2 conform to GSM 05-series and GSM 04.04, GSM 04.05 and GSM 04.06. The generic protocol uses the acknowledged information transfe... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.1 General | This clause specifies the functional signalling procedures for the control of supplementary services at the radio interface. The Functional protocol utilizes functions and services provided by GSM 04.08 basic call control procedures and the functions of the data link layer as defined in GSM 04.06. The defined procedure... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.2 Separate Messages Category | The messages defined in this clause are specified as separate functional messages for the request, acknowledgement and rejection of specific procedures. These procedures can only be performed during the active phase of a call. The functions of these messages are not to be duplicated or overlapped by the ones of the Com... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.3 Common Information Element Category | The Common Information Element Category uses operations defined in GSM 04.80 for supplementary services signalling. Procedures are initiated by sending an operation including an invoke component. The invoke component may yield a Return Error, Return Result or Reject component (also included in an operation) depending o... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.4 Call related supplementary service procedures | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.4.1 Supplementary service procedures at call establishment or call clearing | For call related supplementary service procedures initiated at call establishment or call clearing, the messages for call control specified in GSM 04.08 are utilized to transport Facility information elements. This enables, for example the originating mobile user to send a supplementary service invoke component within ... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.4.1.1 Encoding of the Facility IEI for different supplementary services | The table 2.1 shows the encoding of the Facility IEI within the SETUP message for different supplementary services. Table 2.1: Encoding of the Facility IE within the SETUP message Service Facility IE Encoding CUG simple recall alignment 2.2.4.1.2 Supplementary service procedures at network initiated mobile originating ... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.4.2 Supplementary service procedures during the call | For call related supplementary service procedures during the active state of a call, the FACILITY message is used for the exchange of the Facility information elements. Note that the FACILITY message can also be used for this purpose in all states after the SETUP message has been sent. If the supplementary service proc... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.4.3 Handling of protocol errors in call related SS procedures | Messages containing a Facility information element shall be checked for protocol errors before the contents of the Facility IE is acted on. The checks shall be performed in the following order: 1) The message carrying the Facility IE shall be checked for protocol errors as specified in GSM 04.08. If a protocol error is... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.4.4 Handling of other errors in call related SS procedures | If the tests specified in subclause 2.2.4.3 have been passed without the detection of a protocol error, the receiver will attempt to process the contents of the Facility Information Element. If errors occur during this processing (e.g. system failure, or information in the Facility IE is incompatible with the requested... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.5 Call independent supplementary service procedures | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.5.1 Introduction | For supplementary service procedures independent of any call, the initiating side must establish a MM-connection between the network and the MS according to the rules given in GSM 04.07 and 04.08. The MS or the network starts the transaction by transferring a REGISTER message across the radio interface. This transactio... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.5.2 Handling of protocol errors in call independent SS procedures | Messages containing a Facility information element shall be checked for protocol errors before the contents of the Facility IE is acted on. The checks shall be performed in the following order: 1) The message carrying the Facility IE shall be checked for protocol errors as specified in subclause 3.7. If a protocol erro... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.5.3 Handling of other errors in call independent SS procedures | If the tests specified in subclause 2.2.5.2 have been passed without the detection of a protocol error, the receiver will attempt to process the contents of the Facility Information Element. If errors occur during this processing (e.g. system failure, or information in the Facility IE is incompatible with the requested... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.6 Multiple supplementary service invocations | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.6.1 Call related supplementary service procedures | Simultaneous requests for different supplementary service procedures (i.e. using more than one operation in the Facility information element) are permitted. Interactions between different operations shall be managed by processing the operations in the order in which they appear in the Facility information element. |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.6.2 Call independent supplementary service procedures | Where permitted by the relevant stage 3 specification, multiple operations may be sent on the same transaction. It is possible for several call independent SS transactions to be used simultaneously. Call independent SS transactions can also exist in parallel with other CM-Layer and MM transactions. The handling of mult... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.7 Recovery procedures | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.7.1 Call related supplementary service recovery procedures | There are no additional recovery procedures for call related supplementary service signalling on the radio path. The recovery procedures as specified for the basic service apply. |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.7.2 Call independent supplementary service recovery procedures | In case a transaction is not terminated according to the normal procedure as described in technical specifications GSM 04.8x and 04.9x-series, the network side has to ensure that the transaction is terminated e.g. by a supervision timer. ETSI TS 100 941 V6.0.1 (1998-07) 15 GSM 04.10 version 6.0.1 Release 1997 2.2.8 Gen... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.8.1 Call related component errors | If the call related transaction is still in progress then a reject component shall be sent. Any message which contains a Facility Information Element may be used. In general, the transaction (call) associated with the rejected operation shall not be automatically released by the entity that detects the error. The trans... |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.8.2 Call independent component errors | |
09d74d05684eb66f6a6137f7ddbe7123 | 100 941 | 2.2.8.2.1 Single component errors | The reject component shall be sent in a RELEASE COMPLETE message. If the component containing the error was itself sent in a RELEASE COMPLETE message then the contents of the component shall be ignored, and no reject component is sent. |
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 pr... |
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 ... |
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 ... |
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 <---------------------------------------------------------------------------... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.