hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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 support SIM Application Toolkit. Therefore standard SIMs and MEs do not need to support them.
|
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 protocol applies to SIM Application Toolkit in the same way as it does to normal operation.
|
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 shall remain unchanged, if still valid, as seen by the ME, irrespective of any SIM Application Toolkit activity; - between successive SIM Application Toolkit related command-response pairs, other normal GSM related command-response pairs can occur. The SIM Application Toolkit task status shall remain unchanged by these command-response pairs. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 111 (GSM 11.11 version 6.3.0 Release 1997)
|
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 command at a later stage. The BUSY status response has no impact on normal GSM operation.
|
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 "normal GSM" commands which are time-critical, e.g. RUN GSM ALGORITHM. A MORE TIME command is defined in GSM 11.14 [27], which ensures that the SIM Application Toolkit task in the SIM gets more processing time, while at the same time freeing the SIM/ME interface. This should be used in preference to NULL procedure bytes ('60'). 11.6.9 Using the TERMINAL PROFILE, ENVELOPE, and TERMINAL RESPONSE commands These commands are part of the set used by SIM Application Toolkit. The use of the these commands, the occasions where they are required, and the command and response parameters associated with the commands, are specified in GSM 11.14 [27]. The ME completes the command parameters/data of the relevant command and sends the command to the SIM. The transmitted data is processed by the SIM in a specific way depending on the tag value in the command parameters. A SIM or ME not supporting SIM Application Toolkit does not need to support these commands. 11.6.10 Using the FETCH command This command is used by SIM Application Toolkit. The use of the this command, the occasions where it is required, and the command and response parameters associated with the command, are specified in GSM 11.14 [27]. It is similar in function to GET RESPONSE, in that it requests response parameters from the SIM, following a '91 XX' status response. The transmitted response data from the SIM is processed by the ME in a specific way depending on the tag value in the response parameters. A SIM or ME not supporting SIM Application Toolkit does not need to support this command. 11.6.11 Data Download via SMS-CB Requirement: Service nΒ°25 "allocated and activated". The ME shall perform the reading procedure with EFCBMID. On receiving a cell broadcast message with an identifier which matches an identifier in EFCBMID, the ME shall pass the CB message to the SIM using the ENVELOPE command. If a match is not found and service no. 14 is "allocated and activated", then the message identifier is checked against those in EFCBMI. 11.6.12 Data Download via SMS-PP Requirement: Service nΒ°26 "allocated and activated". The procedures and commands for Data Download via SMS-PP are defined in GSM 11.14 [27]. 11.6.13 Menu selection Requirement: Service nΒ°27 "allocated and activated". The procedures and commands for Menu Selection are defined in GSM 11.14 [27]. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 112 (GSM 11.11 version 6.3.0 Release 1997) 11.6.14 Call Control Requirement: Service nΒ°28 "allocated and activated". The procedures and commands for Call Control are defined in GSM 11.14 [27]. It is mandatory for the ME to perform the procedures if it has indicated that it supports Call Control in the TERMINAL PROFILE command. When BDN is enabled, the Call control facility of the ME is used by the SIM to support the BDN service. 11.6.15 Proactive SIM Requirement: Service nΒ°29 "allocated and activated". The procedures and commands for Proactive SIM, at the application level, are defined in GSM 11.14 [27]. 11.6.16 Mobile Originated Short Message control by SIM Requirement: Service nΒ°37 "allocated and activated". The procedures and commands for Mobile Originated Short Message control by SIM are defined in GSM 11.14 [27]. It is mandatory for the ME to perform the procedures if it has indicated that it supports Mobile Originated Short Message control by SIM in the TERMINAL PROFILE command. 11.6.17 SIM data download error In case of an ENVELOPE for SIM data download, the SIM can respond with the status words '9E XX' to indicate that response data is available. The ME shall use the GET RESPONSE command to get the response data. The ME shall then send transparently to the network this response data, using the error procedure of the transport mechanism. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 113 (GSM 11.11 version 6.3.0 Release 1997) Annex A (normative): Plug-in SIM This annex specifies the dimensions of the Plug-in SIM as well as the dimensions and location of the contacts of the Plug-in SIM. For further details of the Plug-in SIM see clause 4. 4 max 6 min 11,62 max 13,62 min 7,5 P1 P2 P3 20,8 2,75 max 4,45 min 5,29 max 6,99 min 7,83 max 9,53 min 10,37 max 12,07 min 3,3 0 3Β±0,1 3Β±0,1 15Β±0,1 (6,25) Upper edge Left edge (16,48) 25Β±0,1 R1 0,1 +_ R1 0,1 +_ R1 0,1 +_ R1 0,1 +_ R1 0,1 +_ NOTE: The Plug-in SIM may be "obtained" by cutting away excessive plastic of an ID-1 SIM. The values in parenthesis in figure A.1 show the positional relationship between the Plug-in and the ID-1 SIM and are for information only. Figure A.1: Plug-in SIM ETSI ETSI TS 100 977 V6.3.0 (2000-05) 114 (GSM 11.11 version 6.3.0 Release 1997) Annex B (normative): Coding of Alpha fields in the SIM for UCS2 If 16 bit UCS2 characters as defined in ISO/IEC 10646 [31] are being used in an alpha field, the coding can take one of three forms. If the ME supports UCS2 coding of alpha fields in the SIM, the ME shall support all three coding schemes for character sets containing 128 characters or less; for character sets containing more than 128 characters, the ME shall at least support the first coding scheme. If the alpha field record contains GSM default alphabet characters only, then none of these schemes shall be used in that record. Within a record, only one coding scheme, either GSM default alphabet, or one of the three described below, shall be used. 1) If the first octet in the alpha string is '80', then the remaining octets are 16 bit UCS2 characters, with the more significant octet (MSO) of the UCS2 character coded in the lower numbered octet of the alpha field, and the less significant octet (LSO) of the UCS2 character is coded in the higher numbered alpha field octet, i.e. octet 2 of the alpha field contains the more significant octet (MSO) of the first UCS2 character, and octet 3 of the alpha field contains the less significant octet (LSO) of the first UCS2 character (as shown below). Unused octets shall be set to 'FF', and if the alpha field is an even number of octets in length, then the last (unusable) octet shall be set to 'FF'. Example 1 Octet 1 Octet 2 Octet 3 Octet 4 Octet 5 Octet 6 Octet 7 Octet 8 Octet 9 '80' Ch1MSO Ch1LSO Ch2MSO Ch2LSO Ch3MSO Ch3LSO 'FF' 'FF' 2) If the first octet of the alpha string is set to '81', then the second octet contains a value indicating the number of characters in the string, and the third octet contains an 8 bit number which defines bits 15 to 8 of a 16 bit base pointer, where bit 16 is set to zero, and bits 7 to 1 are also set to zero. These sixteen bits constitute a base pointer to a "half-page" in the UCS2 code space, to be used with some or all of the remaining octets in the string. The fourth and subsequent octets in the string contain codings as follows; if bit 8 of the octet is set to zero, the remaining 7 bits of the octet contain a GSM Default Alphabet character, whereas if bit 8 of the octet is set to one, then the remaining seven bits are an offset value added to the 16 bit base pointer defined earlier, and the resultant 16 bit value is a UCS2 code point, and completely defines a UCS2 character. Example 2 Octet 1 Octet 2 Octet 3 Octet 4 Octet 5 Octet 6 Octet 7 Octet 8 Octet 9 '81' '05' '13' '53' '95' 'A6' 'XX' 'FF' 'FF' In the above example; - Octet 2 indicates there 5 characters in the string - Octet 3 indicates bits 15 to 8 of the base pointer, and indicates a bit pattern of 0hhh hhhh h000 0000 as the 16 bit base pointer number. Bengali characters for example start at code position 0980 (0000 1001 1000 0000), which is indicated by the coding '13' in octet 3 (shown by the italicised digits). - Octet 4 indicates GSM Default Alphabet character '53', i.e. "S". - Octet 5 indicates a UCS2 character offset to the base pointer of '15', expressed in binary as follows 001 0101, which, when added to the base pointer value results in a sixteen bit value of 0000 1001 1001 0101, i.e. '0995', which is the Bengali letter KA. Octet 8 contains the value 'FF', but as the string length is 5, this a valid character in the string, where the bit pattern 111 1111 is added to the base pointer, yielding a sixteen bit value of 0000 1001 1111 1111 for the UCS2 character (i.e. '09FF'). ETSI ETSI TS 100 977 V6.3.0 (2000-05) 115 (GSM 11.11 version 6.3.0 Release 1997) 3) If the first octet of the alpha string is set to '82', then the second octet contains a value indicating the number of characters in the string, and the third and fourth octets contain a 16 bit number which defines the complete 16 bit base pointer to a "half-page" in the UCS2 code space, for use with some or all of the remaining octets in the string. The fifth and subsequent octets in the string contain codings as follows; if bit 8 of the octet is set to zero, the remaining 7 bits of the octet contain a GSM Default Alphabet character, whereas if bit 8 of the octet is set to one, the remaining seven bits are an offset value added to the base pointer defined in octets three and four, and the resultant 16 bit value is a UCS2 code point, and defines a UCS2 character. Example 3 Octet 1 Octet 2 Octet 3 Octet 4 Octet 5 Octet 6 Octet 7 Octet 8 Octet 9 '82' '05' '05' '30' '2D' '82' 'D3' '2D' '31' In the above example - Octet 2 indicates there are 5 characters in the string - Octets 3 and 4 contain a sixteen bit base pointer number of '0530', pointing to the first character of the Armenian character set. - Octet 5 contains a GSM Default Alphabet character of '2D', which is a dash "-". - Octet 6 contains a value '82', which indicates it is an offset of '02' added to the base pointer, resulting in a UCS2 character code of '0532', which represents Armenian character Capital BEN. - Octet 7 contains a value 'D3', an offset of '53', which when added to the base pointer results in a UCS2 code point of '0583', representing Armenian Character small PIWR. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 116 (GSM 11.11 version 6.3.0 Release 1997) Annex C (informative): FDN/BDN Procedures ATR Get Response Verify CHV1 (if not disabled) Get Response (evaluation of invalidation flag) Get Response (evaluation of invalidation flag) (see note1) (see note1) not invalidated (see note 2) invalidated 1 ME: unrestricted operation SIM Phase? Phase 2 Phase 1 Status EF and EFLOCI IMSI ME: unrestricted operation Select DFGSM Select EF LOCI Select EFIMSI Phase 2+ Perform Profile Download (see note3) NOTE 1: In case of enabled FDN and/or enabled BDN, the EF has been invalidated by the SIM at no later than this stage. NOTE 2: Invalidation of only one of the two EFs is not allowed for FDN and BDN. NOTE 3: For SIMs with enabled BDN this procedure is used to check whether the ME supports the Call Control by the SIM facility. Figure C.1: Example of an Initialization Procedure of a FDN/BDN SIM (see subclause 11.2.1) ETSI ETSI TS 100 977 V6.3.0 (2000-05) 117 (GSM 11.11 version 6.3.0 Release 1997) SIM capability request ME supports CC ? 1 no yes ME supports all enabled services (see note 6) ? ME supports FDN and FDN is enabled ? no no yes yes Rehabilitate EFLOCI and EFIMSI Rehabilitate EFLOCI and EFIMSI (note 4) (note 4) EFs rehabilitated ? EFs rehabilitated ? no yes (note 5) no (note 5) yes no operation FDN operation restricted or unrestricted operation, according to the state (enabled/disabled) of the various services (FDN, CC) NOTE 4: In case of "BDN enabled", the SIM only allows rehabilitation of the EFIMSI and EFLOCI, if the ME has indicated its CC-capability to the SIM (by PROFILE_DOWNLOAD). NOTE 5: Possibility for future "restricting" services to use the internal SIM mechanism of invalidation of EFIMSI and EFLOCI. NOTE 6: If the ME does not support all enabled services (e.g. FDN, BDN), it does not operate. In case of enabled BDN, the support of the "Call Control Feature" by the ME is sufficient for operation. For future use, there may be additional "restricting" services, which are not known to the ME. In that case the ME will perform the subsequent rehabilitation procedure but will fail to rehabilitate EFIMSI and EFLOCI (see note 4). Figure C.1: Example of an Initialization Procedure of a FDN/BDN SIM (continued) ETSI ETSI TS 100 977 V6.3.0 (2000-05) 118 (GSM 11.11 version 6.3.0 Release 1997) BDN capability request FDN capability request Figure C.2: SIM capability request Select DF TELECOM Select EF BDN BDN allocated and activated ? yes no Select EF SST Read EFSST Get Response (evaluation of invalidation flag) EFBDN invalidated ? no No BDN SIM yes BDN disabled BDN enabled Figure C.3: BDN capability request (see subclause 11.5.1) ETSI ETSI TS 100 977 V6.3.0 (2000-05) 119 (GSM 11.11 version 6.3.0 Release 1997) (see note 7) yes Select EF SST Read EFSST Telecom Select DF ADN Select EF no no yes no invalidated EF ? ADN FDN enabled FDN disabled No FDN SIM FDN allocated and activated ? Get Response (evaluation of invalidation flag) ADN allocated and activated ? yes NOTE 7: In this case FDN is enabled without the possibility of disabling. Figure C.4: FDN capability request (see subclause 11.5.1) ETSI ETSI TS 100 977 V6.3.0 (2000-05) 120 (GSM 11.11 version 6.3.0 Release 1997) Rehabilitate Rehabilitate IMSI EF Select EF LOCI Select EFIMSI (Note 8) Rehabilitate IMSI EF LOCI EF Rehabilitate EF LOCI (Note 8) NOTE 8: If BDN is enabled in the SIM, and if the Profile download procedure has not indicated that the ME supports Call Control, the EF is not rehabilitated by the SIM. Figure C.5: Procedure to rehabilitate GSM files yes FDN allocated and activated ? no FDNenabled no yes ADN allocated and activated ? FDNnot enabled EF yes no FDNnot enabled invalidated EF ? ADN Boolean Equation: FD = FDA.(NOT(ADA+ADA.ADI) where FD = FDN enabled FDA = FDN allocated and activate ADA = ADN allocated and activate ADI = EFADN invalidated Figure C.6: Coding for state of FDN ETSI ETSI TS 100 977 V6.3.0 (2000-05) 121 (GSM 11.11 version 6.3.0 Release 1997) Annex D (informative): Suggested contents of the EFs at pre-personalization If EFs have an unassigned value, it may not be clear from the main text what this value should be. This annex suggests values in these cases. File Identification Description Value '2F E2' ICC identification operator dependant (see 10.1.1) '2F 05' Extended Language preference 'FFβ¦FF' '6F 05' Language preference 'FF' '6F 07' IMSI operator dependant (see 10.3.2) '6F 20' Ciphering key Kc 'FF...FF07' '6F 30' PLMN selector 'FF...FF' '6F 31' HPLMN search period 'FF' '6F 37' ACM maximum value '000000' (see note 1) '6F 38' SIM service table operator dependant (see 10.3.7) '6F 39' Accumulated call meter '000000' '6F 3E' Group identifier level 1 operator dependant '6F 3F' Group identifier level 2 operator dependant '6F 41' PUCT 'FFFFFF0000' '6F 45' CBMI 'FF...FF' '6F 46' Service provider name 'FF...FF' '6F 48' CBMID 'FF...FF' '6F 49' Service Dialling Numbers 'FF...FF' '6F 74' BCCH 'FF...FF' '6F 78' Access control class operator dependant (see 10.1.12) '6F 7B' Forbidden PLMNs 'FF...FF' '6F 7E Location information 'FFFFFFFF xxFxxx 0000 FF 01' (see note 2) '6F AD' Administrative data operator dependant (see 10.3.15) '6F AE' Phase identification see 10.3.16 '6F 3A' Abbreviated dialling numbers 'FF...FF' '6F 3B' Fixed dialling numbers 'FF...FF' '6F 3C' Short messages '00FF...FF' '6F 3D' Capability configuration parameters 'FF...FF' '6F 40' MSISDN storage 'FF...FF' '6F 42' SMS parameters 'FF...FF' '6F 43' SMS status 'FF...FF' '6F 44' Last number dialled 'FF...FF' '6F 47' Short message status reports '00FFβ¦FF' '6F 4A' Extension 1 'FF...FF' '6F 4B' Extension 2 'FF...FF' '6F 4C' Extension 3 'FF...FF' '6F 4D' Barred dialling numbers 'FF...FF' '6F 4E' Extension 4 'FF...FF' '6F 51' Network's indication of alerting 'FF...FF' '6F 52 GPRS Ciphering key KcGPRS 'FF...FF07' '6F 53 GPRS Location Information 'FFFFFFFF FFFFFF xxFxxx 0000 FF 01' NOTE 1: The value '000000' means that ACMmax is not valid, i.e. there is no restriction on the ACM. When assigning a value to ACMmax, care should be taken not to use values too close to the maximum possible value 'FFFFFF', because the INCREASE command does not update EFACM if the units to be added would exceed 'FFFFFF'. This could affect the call termination procedure of the Advice of Charge function. NOTE 2: xxFxxx stands for any valid MCC and MNC, coded according to GSM 04.08 [15]. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 122 (GSM 11.11 version 6.3.0 Release 1997) Annex E (informative): SIM application Toolkit protocol diagrams. The diagrams in this annex are intended to illustrate the data protocols of the SIM toolkit application in various situations. The SIM application is shown as initiated by SMS Data Download messages. Other possibilities exist (as defined in GSM 11.14) such as data entry from a menu selection. Case 1: Simple Network ME GSM SIM SIM Application SMSSIM _Data_Download/Class_2 ENV(SMS) (SMS) (β9000β) β9000β SMS Ack This shows the simple case where an SMS for SIM updating is received from the network, passed to the SIM by the ME and processed immediately by the SIM application. This requires no ME action except to acknowledge the SMS. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 123 (GSM 11.11 version 6.3.0 Release 1997) Case 2: Simple with short delay Network ME GSM SIM SIM Appl ENV(SMS) (SMS) (β9000β) β9000β SMS Ack β60β (β60β) β60β (β60β) SMSSIM _Data_Download/Class_2 This shows the simple case where an SMS for SIM updating is received from the network, passed to the SIM by the ME and which requires some time to process by the SIM application. The processing time is "not long" and is obtained by the SIM application sending "null procedure bytes" to the ME. Each byte has the effect of restarting the work waiting time so that the ME does not abort the transaction before the SIM application has finished processing the command(s) sent in the SMS. Guidelines on timings: 1. The SMS Ack must be sent back before the network times out and sends the SMS again. 2. Use of null procedure bytes must not be excessive as during this time the ME is unable to issue normal GSM commands to the SIM. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 124 (GSM 11.11 version 6.3.0 Release 1997) Case 3: Simple with short delay and SIM Acknowledgement Network ME GSM SIM SIM Appl ENV(SMS) (SMS) (β9F10β) β9F10β SMS Ack (with SIM Ack) β60β (β60β) β60β (β60β) SMSSIM _Data_Download/Class_2 Get Response (16 bytes) (SIM Ack) SIM Ack This shows the same case as previously where an SMS for SIM updating is received from the network, passed to the SIM by the ME and which requires some time to process by the SIM application. However in this case the SIM application has SIM acknowledgement data to include in the SMS acknowledgement being returned to the network by the ME. Guideline on timings: The SMS Ack must be sent back before the network times out and sends the SMS again. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 125 (GSM 11.11 version 6.3.0 Release 1997) Case 4: A Toolkit command generated by the SIM application as a result of an SMS from the network Network ME GSM SIM SIM Application ENV(SMS) FETCH (SMS) (FETCH) (Command) Command (β91XXβ) (TERMINAL RESPONSE) β91XXβ (β9000β) SMS Ack TERMINAL RESPONSE β60β β9000β (β60β) SMSSIM _Data_Download/Class_2 β60β (β60β) This shows the case where an SMS for SIM updating is received from the network, passed to the SIM by the ME and processed by the SIM application which then generates a command for action by the ME (e.g. PLAYTONE). NOTE: If a positive acknowledgement to the network of completion of execution of the instructions given in the SMS message is required then the SIM application can issue a command to the ME to send a MO SMS. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 126 (GSM 11.11 version 6.3.0 Release 1997) Case 5: A normal GSM command requires processing before the ME can respond to the 91XX from the SIM Network ME GSM SIM SIM Application (SMS) (β91XXβ) ENV(SMS) β91XXβ SMS Ack FETCH (FETCH) (Command) Command GSM Command β91XXβ SMSSIM _Data_Download/Class_2 (TERMINAL RESPONSE) (β9000β) TERMINAL RESPONSE β9000β This shows the case where an SMS for SIM updating is received from the network, passed to the SIM by the ME and processed by the SIM application which then generates a command for action by the ME (e.g. PLAYTONE). However a normal GSM command requires processing before the ME can FETCH the command which the SIM is waiting to give it. The response to the normal GSM command is '91XX' in this case to remind the ME of the outstanding SIM application command request. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 127 (GSM 11.11 version 6.3.0 Release 1997) Case 6: MORE TIME Command Network ME GSM SIM SIM Application (SMS) (β91XXβ) ENV(SMS) β91XXβ SMS Ack FETCH (FETCH) (MORETIME) MORETIME (TERMINAL RESPONSE) (β9000β) TERMINAL RESPONSE β9000β SMSSIM _Data_Download/Class_2 This shows the case where an SMS for SIM updating is received from the network, passed to the SIM by the ME and requires a considerable period of time to be processed by the SIM application. In this case the use of null procedure bytes only is inappropriate as the ME must be given the opportunity to process normal GSM commands. The opportunities gained by the SIM application for processing, and the opportunities for normal GSM commands are shown in the diagram above. The sequence of 91XX, FETCH and MORETIME commands can be repeated if required. Opportunities to process normal GSM commands are shown thus: Opportunities for SIM application processing are shown thus: ETSI ETSI TS 100 977 V6.3.0 (2000-05) 128 (GSM 11.11 version 6.3.0 Release 1997) Case 7: SIM Application Busy Network ME GSM SIM SIM Application ENV(SMSβ) β9300β BUSY SMS NACK SMSSIM _Data_Download/Class_2 While the SIM application is busy processing a SMS for the SIM application arrives from the network and is sent to the SIM by the ME in the usual manner. The SIM operating system recognizes that the SIM application is busy, and it sends a busy response ('9300') to the ME. The ME then sends negative acknowledgement to the network. The responsibility for a retry rests with the network. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 129 (GSM 11.11 version 6.3.0 Release 1997) Annex F (informative): Bibliography 1) EN 726-3 (1994): "Terminal Equipment (TE); Requirements for IC cards and terminals for telecommunication use Part 3: Application independent card requirements". 2) EN 726-4 (1994): "Terminal Equipment (TE); Requirements for IC cards and terminals for telecommunication use Part 4: Application independent card related terminal requirements". 3) ISO/IEC 7816-3/A2 (1994): "Identification cards - Integrated circuit(s) cards with contacts, Part 3: Electronic signals and transmission protocols": "Protocol type select". ETSI ETSI TS 100 977 V6.3.0 (2000-05) 130 (GSM 11.11 version 6.3.0 Release 1997) Annex G (informative): Change history This annex lists all change requests approved for the present document since the first phase2+ version was approved by ETSI SMG. SMG# SMG tdoc SMG9 tdoc VERS CR RV PH CAT SUBJECT Resulting Version S16 709/95 154/95 4.15.0 A008 r96 1 SIM Speed Enhancement 5.0.0 S17 062/96 147/95 5.0.0 A006 r96 B Service Dialling Numbers 5.1.0 060/96 06/96 A009 r96 B ASCI for VGCS and VBS 060/96 06/96 A010 r96 B ASCI for eMLPP 059/96 204/95r A013 r96 C Interaction between FDNs and ADNs 061/96 05/96 A014 r96 D Correction of baud rate for SIM Speed enhancement S18 263/96 57/96 5.1.0 A011 3 r96 B SIM Application Toolkit protocol enhancements 5.2.0 260/96 45/96 A016 r96 A SIM presence detection clarification 261/96 54/96 A018 r96 A Reponse codes and coding of SIM service table 262/96 55/96 A020 r96 A Reference to International Standards S19 374/96 102/96 5.2.0 A012 r96 C Contacting elements 5.3.0 373/96 105/96 A023 r96 A Clarification of clock stop timing 409/96 107/96 A024 1 r96 B Emergency Call Codes (ECC) 374/96 108/96 A025 r96 C Using ranges of CBMIs S20 580/96 206/96 5.3.0 A021 r96 B Barred Dialling Numbers 5.4.0 734/96 197/96 A026 r96 B Addition of Cooperative Network List EF 734/96 197/96 A027 r96 B Addition of ME Depersonalisation feature and EF 702/96 207/96 A031 r96 D RFU bit taken into use in GSM 11.12 s21 101/97 97/079 5.4.0 A032 2 r96 D Ammendment to BDN diagrams in Annex B 5.5.0 101/97 97/086 A033 1 r96 B DFs for MSS/ PCS1900/other use 101/97 97/056 A034 r96 C Reading of EFDCK during SIM initialisation 101/97 97/058 A036 r96 D Administrative Access Conditions 101/97 97/059 A037 r96 B Format of EFCNL to include fields for Corporate Personal. Code 101/97 97/089 A041 r96 B Administrative Data field s22 356/97 183/97 5.5.0 A042 r97 B Extended language preference 5.6.0 356/97 163/97 A044 1 r96 A Clarification of electrical/mechanical SIM/ME interface 356/97 179/97 A045 r96 D Security procedures for 2nd level; DFs located under DF GSM 356/97 187/97 A047 r96 F Number of bytes returned after a SELECT command 356/97 093/97 A048 r96 D Serivce table and "radio interface" 356/97 109/97 A049 r96 F Update Access condition of EFDCK (aligns 11.11 & 02.22) s23 788/97 97/249 5.6.0 A046 2 r97 B Short Message Status Reports 5.7.0 788/97 97/243 A050 r96 F Addition of SDN and BDN in the description of EFCCP 788/97 97/259 A051 1 r97 C SIM and ME behaviour when SIM is disabled and blocked 788/97 97/262 A053 r96 F Response data following an ENVELOPE command 788/97 97/260 A054 r96 F Coding of EFPhase 788/97 97/271 A055 r97 C Changes to Dialling Number Files and extensions 788/97 97/261 A056 r97 B Network's indication of alerting in the MS s24 97-0886 97/365 5.7.0 A052 2 r97 b Introduction of UCS2 5.8.0 97-0886 97/383 A057 r97 c MO SMS control by SIM At SMG #25, it was decided to create a version 6.0.0 of every specification that contained at least one release '97 workitem s25 98-0157 98p052 5.8.0 A058 2 R97 B Addition of EFs for GPRS 6.0.0 98-0157 98p108 A059 R97 F Clarification regarding EFCCP records 98-0157 98p094 A061 1 r96 A Clarification of removal of the SIM s26 98-0398 98p240 6.0.0 A066 R97 F RP-ACK RP-ERROR for SIM data download error. 6.1.0 98-0398 98p263 A069 R97 D Allocation of file ID for IS-41 s28 P-99-184 P-99-096 6.1.0 A079 R97 C Addition of P-TIMSI signature value to EF LOCIGPRS 6.2.0 P-99-188 A081 R97 D Deletion of $(......)$ release markers s31 P-00-137 9-00-090 6.2.0 A099 R97 F Correction to coding of ASCI EF eMLPP. 6.3.0 P-00-137 9-00-093 A102 R97 F Addition of coding for ASCI EFs (VGCS and VBS) P-00-137 9-00-096 A105 R97 F Correction of the byte numbering related to EF LOCIGPRS ETSI ETSI TS 100 977 V6.3.0 (2000-05) 131 (GSM 11.11 version 6.3.0 Release 1997) History Document history V6.1.0 July 1998 Publication V6.2.0 May 1999 Publication V6.3.0 May 2000 Publication
|
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 particular station is designed to support. NOTE: The present document should be considered together with GSM 08.20 [9] (Rate Adaptation on the BSS-MSC Interface) to give a complete description of PLMN rate adaptation.
|
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. β’ 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 telecommunication system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.34: "Digital cellular telecommunications system (Phase 2+); High Speed Circuit Switched Data (HSCSD) -Stage 1". [3] GSM 03.10: "Digital cellular telecommunication system (Phase 2+); GSM Public Land Mobile Network (PLMN) connection types". [4] GSM 03.34: "Digital cellular telecommunications system (Phase 2+); High Speed Circuit Switched Data (HSCSD) - Stage 2 Service Description". [5] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". [6] GSM 07.01: "Digital cellular telecommunication system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". [7] GSM 07.02: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities". [8] GSM 07.03: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities". [9] GSM 08.20: "Digital cellular telecommunication system (Phase 2+); Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [10] CCITT Recommendation V.110: "Support of data terminal equipments (DTEs) with V-Series interfaces by an integrated services digital network". [11] CCITT Recommendation X.30: "Support of X.21,X.21 bis and X.20 bis based terminal equipments (DTEs) by integrated services digital network (ISDN)". ETSI ETSI TS 100 945 V7.1.0 (2000-08) 7 (GSM 04.21 version 7.1.0 Release 1998)
|
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 rate channel on the radio interface (TCH/F) independent of the contents Multislot intermediate rate: Intermediate rate per substream in those parts of the network where the overall data stream is split into substreams. Intermediate rate: Intermediate rate in the overall data stream. Substream rate: The user rate including padding, if applicable, on one individual substream.
|
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 connection type. The rate adaptation functions are RA0, RA1, RA2, RA1', RA1'' and RA1/RA1'. The RA0, RA1 and RA2 are equivalent to those functions described in CCITT recommendation V.110 [11]. The RA1' function is similar to RA1 but has a reduced bit rate output compatible with the coding scheme proposed for data services on the radio interface. The RA1'' function is used for converting between synchronous user rates of 48 and 56 kbit/s and the rate 64 kbit/s. The equivalent function in CCITT recommendation V.110 does not have a name. The RA1/RA1' is a relay function, used as indicated in GSM 03.10. In multislot data-configurations the overall data stream is split into parallel substreams between the Split/Combine- functions.
|
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 data stream, whereas for multislot connections, the intermediate rates are per substream. In Table 2, intermediate rates within the MS, overall radio interface rates, and channel configurations are given for the air-interface user rates. The intermediate rates are per overall data stream. For single slot rates up to 4,8 kbit/s, the used intermediate rate is 8 kbit/s, and for the 9,6 kbit/s single slot rate 16 kbit/s. For TCH/F9.6 and TCH/F4.8 channel codings, the multislot intermediate rates are 16 and 8 kbit/s per TCH/F, respectively. For TCH/F14.4 channel coding, the multislot intermediate rate is 16 kbit/s per TCH/F. Between the TE and the Split/Combine-function at the MS, where the overall data stream is not split, intermediate rates of 8, 16, 32 and 64 kbit/s are applicable. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 8 (GSM 04.21 version 7.1.0 Release 1998) Table 1: AIUR/Multislot intermediate rates Air interface user rate DTE/DCE statuses RA0 RA1'/RA1 RA1'/RAA' RA1' Multislot intermediate rate Frame type Radio interface rate Padding β€600 bit/s X X 8 kbit/s 80 bit frames 3,6 kbit/s 1200 bit/s X X 8 kbit/s 80 bit frames 3,6 kbit/s 2,4 kbit/s X X 8 kbit/s 80 bit frames 3,6 kbit/s 4,8 kbit/s X X 8 kbit/s 80 bit frames 6 kbit/s 9,6 kbit/s X X 16 kbit/s or 2Γ8 kbit/s 80 bit frames 12 kbit/s or 2Γ6 kbit/s 14,4 kbit/s X X 2Γ16 kbit/s or 3Γ8 kbit/s 80 bit frames 2Γ12 kbit/s or 3Γ6 kbit/s P (note 1) 16 kbit/s Note 7 Note 8 14,5 kbit/s 19,2 kbit/s X X 2Γ16 kbit/s or 4Γ8 kbit/s 80 bit frames 2Γ12 kbit/s or 4Γ6 kbit/s 28,8 kbit/s X X 3Γ16 kbit/s 80 bit frames 3Γ12 kbit/s 2 x 16 kbit/s Note 7 Note 8 2Γ14,5 kbit/s 38,4 kbit/s X X 4Γ16 kbit/s 80 bit frames 4Γ12 kbit/s P (note 6) 3 x 16 kbit/s Note7 Note 8 3Γ14,5 kbit/s 48 kbit/s X Note 2 Note 2 5Γ12 kbit/s P (note 6) 4 x 16 kbit/s Note7 Note 8 4Γ14,5 kbit/s 56 kbit/s Note 2 Note 2 5Γ12 kbit/s (note 3) P (note 6) 4x16 kbit/s Note7 Note 8 4Γ14,5 kbit/s 64 kbit/s Note 2 Note 2 6Γ12 kbit/s (note 3) P (note 1) 5Γ14,5 kbit/s (note 6) P=Padding used ETSI ETSI TS 100 945 V7.1.0 (2000-08) 9 (GSM 04.21 version 7.1.0 Release 1998) Table 2: AIUR / Intermediate rates Air interface user rate DTE/DCE statuses RA0 RA1 RA1' Intermediate rate Frame type Radio interface rate Padding β€600 bit/s X X 8 kbit/s 80 bit frames 3,6 kbit/s 1200 bit/s X X 8 kbit/s 80 bit frames 3,6 kbit/s 2,4 kbit/s X X 8 kbit/s 80 bit frames 3,6 kbit/s 4,8 kbit/s X X 8 kbit/s 80 bit frames 6 kbit/s 9,6 kbit/s X X 16 kbit/s 80 bit frames 12 kbit/s or 2Γ6 kbit/s 14,4 kbit/s X X 32 kbit/s 80 bit frames 2Γ12 kbit/s or 3Γ6 kbit/s 1x14,5 kbit/s P (note 1) 19,2 kbit/s X X 32 kbit/s 80 bit frames 2Γ12 kbit/s or 4Γ6 kbit/s 28,8 kbit/s X X 64 kbit/s 80 bit frames 3Γ12 kbit/s 2Γ14,5 kbit/s 38,4 kbit/s X X 64 kbit/s 80 bit frames 4Γ12 kbit/s 3Γ14,5 kbit/s P (note 6) 48 kbit/s X Note 4 Note 4 5Γ12 kbit/s 4Γ14,5 kbit/s P (note 6) 56 kbit/s Note 4 Note 4 5Γ12 kbit/s (note 3) 4Γ14,5 kbit/s P (note 6) 64 kbit/s Note 5 Note 5 6Γ12 kbit/s (note 3) 5Γ14,5 kbit/s P (note 1) (note 6) P =Padding used NOTE 1: For information on the padding procedure, please refer to clause 10 of the present document. NOTE 2: No multislot intermediate rate; substreams combined at the BSS. NOTE 3: AIUR 11,2 kbit/s per channel NOTE 4: For this rate GSM-specific rate adaptation function RA1'' rather than RA1is applied. NOTE 5: For this rate RA1- and RA2- adaptations are not applied. NOTE 6: Padding used as specified for TCH/F14.4 channel codings NOTE 7: At the network side, RA1'/RA1 not applied; instead a TCH/F14,4-specific adaptation RA1'/RAA' used (GSM 08.20) NOTE 8: A 320-bit frame format described in GSM 08.60. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 10 (GSM 04.21 version 7.1.0 Release 1998)
|
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 rates shall be adapted to a synchronous 600 bit/s stream. The resultant synchronous stream is fed to RA1 or RA1'. The RA0 used in GSM is not identical to that described in ITU-T Recommendation V.110 which converts 14,4 and 28,8 kbit/s user rates to 19,2 and 38,4 kbit/s, respectively. Asynchronous user rate Synchronous user rate β€0.6 kbit/s 0.6 kbit/s 1,2 kbit/s 1,2 kbit/s 2,4 kbit/s 2,4 kbit/s 4,8 kbit/s 4,8 kbit/s 9,6 kbit/s 9,6 kbit/s 14,4 kbit/s 14,4 kbit/s 19,2 kbit/s 19,2 kbit/s 28,8 kbit/s 28,8 kbit/s 38,4 kbit/s 38,4 kbit/s
|
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 detects more than 2M+3 bits all of start polarity, the converter shall transmit all these bits as start polarity. The 2M+3 or more bits of start polarity received from the transmitting sides shall be output to the receiving terminal. The terminal must transmit on circuit 103 at least 2M bits stop polarity after the start polarity break signal before sending further data character. The converter shall then regain character synchronism from the following stop to start transition.
|
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 for every eight characters at 1 % overspeed. The converter on the receiving side shall detect the deleted stop elements and reinsert them in the received data stream (circuit 104). The realization of overspeed handling, as described above, at the interface to the associated terminal is implementation dependent. Possible implementations are e.g. the reduction of the length of the stop elements according to V.110 [9] or increased data rates between the TA and terminal.
|
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 of the S bits are deduced from the R interface. Adaptation of 600 bit/s to 8Kbit/s is performed by 8 times consecutive duplication of each user data bit. (Figure 9) Adaptation of 1200 bit/s to 8 Kbit/s is performed by 4 times consecutive duplication of each user data bit. (Figure 8) Adaptation of 2400 bit/s to 8kbit/s is performed by 2 times consecutive duplication of each user data bit. (Figure 7) Adaptation of 4800 bit/s to 8 Kbit/s is performed by transmitting the bit stream with no duplication. (Figure 3) Adaptation of 9600 bit/s to 16 Kbit/s is performed by transmitting the bit stream with no duplication (the emitting period is halved with respect to the 4800 bit/s case). (Figure 3) Adaptation of 14400 bit/s to 32 Kbit/s is performed as for 3600 bit/s to 8 kbit/s (the emitting period is divided by four with respect to the 3600 bit/s case).( Adaptation of 3600 bit/s to 8 kbit/s is performed by transmitting the bit stream with no duplication.) (Figure 12) Adaptation of 19200 bit/s to 32 Kbit/s is performed as for 4800 bit/s to 8 kbit/s (the emitting period is divided by four with respect to the 4800 bit/s case). (Figure 3) Adaptation of 28800 bit/s to 64 Kbit/s is performed as for 3600 bit/s to 8 kbit/s (the emitting period is divided by eight with respect to the 3600 bit/s case). (Figure 12) Adaptation of 38400 bit/s to 64 Kbit/s is performed as for 4800 bit/s 8 kbit/s (the emitting period is divided by eight with respect to the 4800 bit/s case). (Figure 3) The CCITT V.110 80 bit frames shown in Figures 3 and 12 are used. The D bits are used to convey the user data and the S and X bits are used to convey channel control information according to GSM 07.01. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 12 (GSM 04.21 version 7.1.0 Release 1998) The E bits are used to convey the following information: i) User Data Rate - E1, E2, E3 (for single slot operation see Figure 4, and for multislot operation Figure 4 and subclause 10.7) ii) Network Independent Clocking - E4, E5, E6 iii) Multiframe Synchronisation - E7 The order of transmission of the 80 bit frame is from left to right and top to bottom.
|
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 the signals received from the modem at the IWF require its own clock or where the signals received from the DTE at the MS employs its own network independent clock. In any case, the frequency tolerance of the clocks involved is 100 ppm.
|
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. This frame synchronization will be achieved and maintained during the entire call so that corrections for the network independent clocking by the receiving end of the GSM PLMN connection can be easily recognized and applied based on the code words (in c1, c2, c3, c4 and c5) positioned in bits E4, E5 and E6 of two consecutive V.110 frames as illustrated in figure 1. Thus, the multiframe structure allows for one 5-bit code words to be transmitted every two V.110 frames for the purposes of network independent clocking. The two code-words may be different from each other within the multiframe shown in figure 1. Frame E4 E5 E6 E7 MF 0a c1 c2 1 0 MF 1a c3 c4 c5 1 MF 0b c1 c2 1 1 MF 1b c3 c4 c5 1 Figure 1: NIC Multiframe Structure Once Multiframe synchronization is achieved, each code word is independently evaluated to determine the compensation needed, if any. The compensation is applied as explained in section 3.1.2 in V.110 frames MF 1a and MF 1b.
|
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 one 0 0 1 0 0 Figure 2: NIC Code Words ETSI ETSI TS 100 945 V7.1.0 (2000-08) 13 (GSM 04.21 version 7.1.0 Release 1998) When negative compensation is indicated, one less user data bit than normal is transported in the affected frame (MF1a or MF1b). A negative compensation shall cause the receiver to delete the user data bit occupied by bit position D25, since the transmitter sets this to binary 1 and does not utilize this position for user data. At those user data rates where the user data bit is repeated, all copies of D25 shall be discarded. In case of 80-bit frames with 36 data bits, bit D19 is discarded instead. When a positive compensation is indicated, one additional user data bit is transferred by means of the code word. At the receiver, a positive compensation will cause a user data bit of binary value 0 or 1, as indicated by the code word, to be inserted between the user data bits carried in bit positions D24 and D25 (in MF1a or MF1b) of the V.110 frame illustrated in figure 3. In case of 80-bit frames with 36 data bits, the insertion is done to between bits D18 and D19. When no compensation is necessary, or when NIC is applied, the values of E4, E5, E6, E7, on the 4 multi frame scheme is: Frame E4 E5 E6 E7 MF 0a 1 1 1 0 MF 1a 1 1 1 1 MF 0b 1 1 1 1 MF 1b 1 1 1 1 When NIC is not applicable, the MS and the IWF shall disregard the received value of bits E4, E5, E6 and E7 in the data transmission phase. NOTE: NIC is not applicable in the following cases: - transparent asynchronous bearer services; - the facsimile teleservices in the transparent mode; - every transparent bearer services when interworking with an UDI Information Transfer Capability.
|
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 term 'intermediate rate' is used for the resulting 64 kbit/s rate although this is not done in V.110 recommendation.) 6.1 Rate adaptation of 48 kbit/s user rates with DTE/DCE status to 64 kbit/s A CCITT V.110 32 bits frame is constructed using the user data bits received, the values of the S bits are deduced from the R interface. The CCITT V.110 32 bit frame shown in Figure 13 is used. The D bits are used for conveying the user data and the S and X bits are used for conveying channel control information according GSM 07.01.The order of transmission of the 32 bit frame is from left to right and top to bottom.
|
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.21 version 7.1.0 Release 1998)
|
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 kbit/s For the intermediate- and user data rate of 64 kbit/s, the RA2 transmits the bit stream over the S-interface as it is. It considers the 64 kbit/s stream over the S-interface to consist of octets, bits 1 through 8, with bit 1 being transmitted first. The procedure requires that: i) The 8 kbit/s stream occupies bit position 1; ii) The 16 kbit/s bitstream occupies bit positions (1,2); iii) The 32 kbit/s bitstream occupies bit positions (1,2,3,4) ; iv) The order of transmission of the bits of the subrate stream is identical before and after rate adaptation. v) All unused bits in the 64 kbit/s stream are set to binary "1".
|
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 for TCH/F14.4.
|
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 kbit/s intermediate rates to these data rates, three processes are used. Firstly the 17 synchronization bits are removed. Secondly the E1, E2 and E3 bits are removed. For transparent services, the values of the E1, E2, E3 bits are determined at the MT and in case of TCH/F9.6 and TCH/F4.8, at the BTS based on the indication given by outband signalling (either in the User Rate field of the BC-IE of the SETUP message for the MT or in the Channel Type information in the ASSIGNMENT REQUEST message for the BSS). For non transparent services, the coding of the E1, E2 and E3 bits is described in GSM 08.20. Thirdly, in the 3.6 kbit/s case, half the data bits are discarded. These processes result in modified CCITT V.110 frames of sizes 60,60 and 36 bits for the 12, 6 and 3.6 kbit/s data rates respectively. The resultant modified CCITT V.110 frames for the various user data rates are shown in figures 5 - 9. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 15 (GSM 04.21 version 7.1.0 Release 1998) Further procedures for TCH/F14.4 channel coder input rate in subclause 8.1.1.
|
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 every 20 ms over the radio interface (See GSM 05.03). Bit M2 is used by the RA1/RA1'-function for deriving/mapping the E-, S-, and X-bits. Bit M1 is used for multislot synchronisation. The usage of these bits is further elaborated in subclause 8.1.1.1. The modified CCITT V.110 36-bit frame received/sent from/to the network at 14,4 kbit/s: D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 is converted/derived into/from the following 80-bit V.110-frame at 32 kbit/s. The E-, S-, and X-bits are mapped/extracted to/from the M2-bit sequence. 0 0 0 0 0 0 0 0 1 D1 D2 D3 D4 D5 D6 S1 1 D7 D8 D9 D10 F F X 1 D11 D12 F F D13 D14 S3 1 F F D15 D16 D17 D18 S4 1 E1 E2 E3 E4 E5 E6 E7 1 D19 D20 D21 D22 D23 D24 S6 1 D25 D26 D27 D28 F F X 1 D29 D30 F F D31 D32 S8 1 F F D33 D34 D35 D36 S9 For the 36-bit frames the received D-bits are set as they were transmitted. For transparent services E, S, and X-bits are reproduced based on the M2-bit sequence as described in subclause 8.1.1.1. Bits E1, E2, and E3 are set according to the user data rate as shown in Figure 4 for transparent services.
|
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 numbering as indicated in the following figure: bit number 0 1 2 3 4 5 6 7 8 - 11 12- 15 16 - 19 20 - 23 24 - 27 28 - 30 M1: 0 0 0 0 1 0 0 1 0 1 1 0 0 1 1 1 1 1 0 0 0 1 1 0 1 1 1 0 1 0 1 M2: # # # SB SB X # # # X SB SB # # # SB SB X # # # X SB SB NNNN N SB SB where # # # = Substream number (multilink operation) SB = the SB status bit X = the X-status bit NNNNN = Network independent clocking code ETSI ETSI TS 100 945 V7.1.0 (2000-08) 16 (GSM 04.21 version 7.1.0 Release 1998) In the MS to Network direction the information carried by the M2-bit sequence is mapped in the following manner: An M1/M2-bit pair is transmitted along each block of data containing eight modified V.110 36-bit frames. The three-bit #-sequence carries a number identifying each substream (multislot operation); the substreams are numbered 0,1,2 etc. The status- and NIC-information is mapped between the M2-sequence(s) and the V.110-frames. Bits SB and X are mapped to V.24 circuits as specified in GSM 07.01. The SB-bit carries the V.110 SB-status information, and the X-bit the X-status information. Five consecutive N-bits carrying an NIC-code in the M2-sequence indicate 'negative compensation' or 'positive compensation' if such a compensation is required. Otherwise' no compensation' is indicated by the N-bits. N-bit 24 in M2- sequence N-bit 25 in M2- sequence N-bit 26 in M2- sequence N-bit 27 in M2- sequence N-bit 28 in M2- sequence 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 a one 0 0 1 0 0 The Network to MS direction: The status-information is filtered as described in GSM 07.01. To change the SB- or X-status mode, it is required that at least two consecutive SB- or X-bits, respectively, carry the same value. For NIC-procedure, refer to subclause 10.5.1. 8.1.1.2 Radio-interface data block for TCH/F14.4 channel coding A radio-interface data block for a TCH/F14.4 channel consists of 8 36-bit data frames and bits M1 and M2 as shown in the following table: M1 M2 1 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 2 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 3 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 4 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 5 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 6 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 7 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 8 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 The number on the left indicates the order of the data frames in the 290-bit block; the 36-bit frame in position one was received before that in position two etc. One such block is transmitted over the radio interface every 20 ms. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 17 (GSM 04.21 version 7.1.0 Release 1998)
|
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 from/to the radio interface at 12 Kbit/s, D1 D2 D3 D4 D5 D6 S1 D7 D8 D9 D10 D11 D12 X D13 D14 D15 D16 D17 D18 S3 D19 D20 D21 D22 D23 D24 S4 E4 E5 E6 E7 D25 D26 D27 D28 D29 D30 S6 D31 D32 D33 D34 D35 D36 X D37 D38 D39 D40 D41 D42 S8 D43 D44 D45 D46 D47 D48 S9 is converted into the following a CCITT V.110 80 bits frame at 16 Kbit/s: 0 0 0 0 0 0 0 0 1 D1 D2 D3 D4 D5 D6 S1 1 D7 D8 D9 D10 D11 D12 X 1 D13 D14 D15 D16 D17 D18 S3 1 D19 D20 D21 D22 D23 D24 S4 1 E1 E2 E3 E4 E5 E6 E7 1 D25 D26 D27 D28 D29 D30 S6 1 D31 D32 D33 D34 D35 D36 X 1 D37 D38 D39 D40 D41 D42 S8 1 D43 D44 D45 D46 D47 D48 S9 In the case of the non transparent services, bits S1, X, S3, S4, E4, E5, E6, E7, S6, X (second occurrence), S8, and S9 carry bits D'1, D'2, D'3, D'4, D'5, D'6, D'7, D'8, D'9, D'10, D'11, and D'12, respectively. For a modified CCITT V.110 60 bit frames received from the network, the received D, S and X bits or D and D' bits are set to the same value as the transmitted bits. Bits E1, E2, E3 are set according to the user data rate as shown in figure 4 for the transparent services, or the RLP multiframe and DTX indication as per GSM 08.20 in the non transparent case. For modified CCITT V.110 60 bit frames transmitted over the network, the received D, S, and X bits or D and D' are set to the same value as the transmitted bits. Bits E1, E2, E3 are discarded. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 18 (GSM 04.21 version 7.1.0 Release 1998)
|
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 from/to the radio interface at 6 Kbit/s, D1 D2 D3 D4 D5 D6 S1 D7 D8 D9 D10 D11 D12 X D13 D14 D15 D16 D17 D18 S3 D19 D20 D21 D22 D23 D24 S4 E4 E5 E6 E7 D25 D26 D27 D28 D29 D30 S6 D31 D32 D33 D34 D35 D36 X D37 D38 D39 D40 D41 D42 S8 D43 D44 D45 D46 D47 D48 S9 is converted into the following a CCITT V.110 80 bits frame at 8 Kbit/s: 0 0 0 0 0 0 0 0 1 D1 D2 D3 D4 D5 D6 S1 1 D7 D8 D9 D10 D11 D12 X 1 D13 D14 D15 D16 D17 D18 S3 1 D19 D20 D21 D22 D23 D24 S4 1 E1 E2 E3 E4 E5 E6 E7 1 D25 D26 D27 D28 D29 D30 S6 1 D31 D32 D33 D34 D35 D36 X 1 D37 D38 D39 D40 D41 D42 S8 1 D43 D44 D45 D46 D47 D48 S9 In the case of the non transparent services, bits S1, X, S3, S4, E4, E5, E6, E7, S6, X (second occurrence), S8, and S9 carry bits D'1, D'2, D'3, D'4, D'5, D'6, D'7, D'8, D'9, D'10, D'11, and D'12, respectively. For a modified CCITT V.110 60 bit frames received from the network, the received D, S and X bits or D and D' bits are set to the same value as the transmitted bits. Bits E1, E2, E3 are set according to the user data rate as shown in figure 4 for the transparent services, or the RLP multiframe and DTX indication as per GSM 08.20 in the non transparent case. For modified CCITT V.110 60 bit frames transmitted over the network, the received D, S, and X bits or D and D' bits are set to the same value as the transmitted bits. Bits E1, E2, E3 are discarded. It should be noted that this process is identical to that used for the 12 kbit/s case except that the frame repetition rates are halved. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 19 (GSM 04.21 version 7.1.0 Release 1998)
|
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/sent from/to the radio interface at 3.6 Kbit/s, D1 D2 D3 S1 D4 D5 D6 X D7 D8 D9 S3 D10 D11 D12 S4 E4 E5 E6 E7 D13 D14 D15 S6 D16 D17 D18 X D19 D20 D21 S8 D22 D23 D24 S9 is converted into the following a CCITT V.110 80 bits frame at 8 Kbit/s: 0 0 0 0 0 0 0 0 1 D1 D1 D2 D2 D3 D3 S1 1 D4 D4 D5 D5 D6 D6 X 1 D7 D7 D8 D8 D9 D9 S3 1 D10 D10 D11 D11 D12 D12 S4 1 E1 E2 E3 E4 E5 E6 E7 1 D13 D13 D14 D14 D15 D15 S6 1 D16 D16 D17 D17 D18 D18 X 1 D19 D19 D20 D20 D21 D21 S8 1 D22 D22 D23 D23 D24 D24 S9 For modified CCITT V.110 36 bit frames transmitted to the network, E1, E2, E3 are discarded. For modified CCITT V.110 36 bit frames received from the network, E1, E2, E3 are set as shown in figure 2. NOTE: The action to be taken in the case where two bits which should have the same value (e.g. bits noted D1 are received with different values is for further study.
|
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, the N-bits are set to 'no compensation'. For the exact NIC-procedures, refer to subclause 10.5.1. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 20 (GSM 04.21 version 7.1.0 Release 1998) 8.2.2 AIURs up to 38,4 kbit/s using TCH/F9.6 and TCH/F4.8 channel codings Intermediate rate/AIUR Radio interface rate 16 kbit/s / 9,6 kbit/s 2Γ6 kbit/s 32 kbit/s / 14,4; 19,2 kbit/s 2Γ12 or 3Γ6 or 4Γ6 kbit/s 64 kbit/s / 28,8; 38,4 kbit/s 3Γ12 or 4Γ12 kbit/s In these cases, the data stream is mapped from 80-bit intermediate rate frames into modified frames of 60 bits for radio- interface transmission as specified in subclause 8.1 for 12 kbit/s and 6 kbit/s except for the following cases: For AIURs 14,4 and 28,8 kbit/s using channel codings TCH/F4.8 and TCH/F9.6, respectively, four consecutive V.110 80-bit frames (Figure 12) are mapped onto three consecutive modified 60-bit V.110 (Figure 5 or 6) frames at the MS. The 4Γ36 data bits in the 80-bit frames are mapped onto the 3Γ48 data bits in the 60-bit frames. However, bits E4-E7 in the 80-bit frames are mapped onto the E4-E7 bits in the 60-bit frames when their value indicate either positive or negative compensation (NIC; See subclause 5.1.1). The E4-E7 bits that indicate 'No compensation' in the 80-bit frames need not be mapped onto the 60-bit frames. The S- and X-bits in every fourth 80 -bit frame are not mapped onto the 60- bit frames. When radio interface rate of 2 Γ 12 kbit/s is used for carrying AIUR 14,4 kbit/s, padding is used in the 60-bit frames of the higher substream number (Subclause 10.6). For substream numbering information, please refer to subclause 10 of the present document. 8.2.3 AIURs up to 38,4 kbit/s using TCH/F14.4 channel coding Intermediate rate/AIUR Radio interface rate 64 kbit/s / 28,8; 38,4 kbit/s 2Γ14,5 or 3Γ14,5 For AIURs 14,4 and 28,8 kbit/s the 36 data bits in the 80-bit V.110 intermediate rate frames are extracted and sent through the substreams in data blocks containing eight 36-bit frames as described in subclause 8.1. An M1/M2-bit pair is sent over the radio-interface along with each data block every 20 ms. These bits carry the multiframe, substream number, V.24 status, and NIC information as described in subclauses 8.1.1.1 and 8.2.1. For AIUR 38.4 kbit/s the 80-bit V.110 intermediate rate frames carry 48 user data bits. The 290-bit blocks in the substreams of the lower substream numbers carry 288 user data bits while the 290-bit blocks in the substream of the highest substream number carries 192 user data bits; this means that five of the eight 36-bit frames making up the block carry 36 user data bits whereas the sixth frame carries 12 user data bits (5Γ36+12). Frames seven, eight, and the rest of the sixth frame are padded with '1's. The M2-bit sequences are used as described in subclauses 8.1.1.1 and 8.2.1 For NIC-procedures refer to subclauses 8.2.1 and 10.5.1. No NIC-values are transported in association with AIUR 38,4; the N-bits are set to 'no compensation'. 8.2.4 AIUR of 48 kbit/s; Intermediate rate of 64 kbit/s; Radio interface rate of 5 x 12 kbit/s One modified CCITT V.110 60 bit frame (Figure 5) is received/sent from/to a TCH/F every 5 ms (see GSM 05.03) resulting in an radio-interface rate of 12 kbit/s per channel. One 60-bit radio-interface frame is converted into two CCITT V.110 32-bit frames at 64 kbit/s (Figure 13): 1 D1 D2 D3 D4 D5 D6 S1 0 D7 D8 D9 D10 D11 D12 X 1 D13 D14 D15 D16 D17 D18 S3 1 D19 D20 D21 D22 D23 D24 S4 ETSI ETSI TS 100 945 V7.1.0 (2000-08) 21 (GSM 04.21 version 7.1.0 Release 1998) 8.2.5 AIUR of 48 kbit/s; Intermediate rate of 64 kbit/s; Radio interface rate of 4 x 14,5 kbit/s For AIUR 48 kbit/s the 24 data bits in the 32-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, substream, and V.24 status information as described in subclauses 8.1.1.1 and 8.2.1. The 290-bit blocks in the highest numbered substream carry 96 user data bits (2Γ36+24). The M2-bit sequences are used, for the applicable parts, as described in subclauses 8.1.1.1 and 8.2.1. No NIC-values are transported in association with AIUR 48.0; the N-bits are set to 'no compensation'.
|
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 D14 D15 D16 D17 D18 T3 D19 D20 D21 D22 D23 D24 T4 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 D37 D38 D39 D40 D41 D42 D43 D44 D45 D46 D47 D48 D49 D50 D51 D52 D53 D54 D55 D56 NOTE: For information on the T-bits, please refer to subclause 10.2 of the present document. is converted into a CCITT V.110 64 bits frame at 64 kbit/s: D1 D2 D3 D4 D5 D6 D7 1 D8 D9 D10 D11 D12 D13 D14 1 D15 D16 D17 D18 D19 D20 D21 1 D22 D23 D24 D25 D26 D27 D28 1 D29 D30 D31 D32 D33 D34 D35 1 D36 D37 D38 D39 D40 D41 D42 1 D43 D44 D45 D46 D47 D48 D49 1 D50 D51 D52 D53 D54 D55 D56 1 8.2.7 AIUR of 56 kbit/s; Intermediate rate of 64 kbit/s; Radio interface rate of 4 x 14,5 kbit/s For AIUR 56 kbit/s the 56 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 described in subclause 8.1.1.1. The 290-bit blocks in the highest numbered substream carry 256 user data bits (7Γ36+4). The M2-bit sequences are used, for the applicable parts, as described in subclauses 8.1.1.1 and 8.2.1. No V.24 status or NIC-values are transported in association with AIUR 56.0; the N-bits are set to 'no compensation'. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 22 (GSM 04.21 version 7.1.0 Release 1998)
|
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 D23 D24 T4 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 D37 D38 D39 D40 D41 D42 D43 D44 D45 D46 D47 D48 D49 D50 D51 D52 D53 D54 D55 D56 NOTE: For information on the T-bits, please refer to subclause 10.2 of the present document. The data bits are extracted from the 60-bit frames received from the network; six frames, one of which carries padding as explained in subclause 10.6, carry 320 bits of user data per 5 ms resulting in a 64 kbit/s user rate which is sent forward as such.
|
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 described in subclause 8.1.1.1. The 290-bit blocks in the highest numbered substream carry 128 user data bits (3Γ36+20). The M2-bit sequences are used, for the applicable parts, as described in subclauses 8.1.1.1 and 8.2.1. No V.24 status or NIC-values are transported in association with AIUR 64.0; the N-bits are set to 'no compensation'.
|
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 (GSM 04.21 version 7.1.0 Release 1998) 9.2 Synchronous user rates from 9,6 kbit/s onward; TCH/F9.6/4.8 channel codings Synchronous user rate Total rate at the radio interface DTE/DCE statuses 60 Bit frame structure Single slot rate at the radio interface 14,4 kbit/s 24 kbit/s or 18 kbit/s X 9,6 kbit/s or 4,8 kbit/s (Figs. 5 and 15) Note 12 kbit/s or 6 kbit/s 19,2 kbit/s 24 kbit/s X 9,6 kbit/s or 4,8 kbit/s (Fig. 5) 12 kbit/s or 6 kbit/s 28,8 kbit/s 36 kbit/s X 9,6 kbit/s (Fig. 5) 12 kbit/s 38,4 kbit/s 48 kbit/s X 9,6 kbit/s (Fig. 5) 12 kbit/s 48 kbit/s 60 kbit/s X 9,6 kbit/s (Fig. 5) 12 kbit/s 56 kbit/s 60 kbit/s 11,2 kbit/s (Fig.10) 12 kbit/s 64 kbit/s 72 kbit/s 11,2 kbit/s (Figs. 10 and 16) Note 12 kbit/s NOTE: Padding is used in frames making up the data substream of the highest substream number. Modified CCITT V.110 60 bit frames structures are those shown in figures 5, (6,) and 10. The structure to apply is that for the partial user rate. The meaning of the bits is described in clauses 5 and 7. For description of the padding procedure, please refer to clause 10 of the present document. 9.3 Synchronous user rates from 9,6 kbit/s onward; TCH/F14.4 channel coding Synchronous user rate Total rate at the radio interface DTE/DCE statuses Air-interface bit frame structure Single slot rate at the radio interface 14,4 kbit/s 14,5 kbit/s X 36 bits, 290-bit block 14,5 kbit/s 28,8 kbit/s 29.0 kbit/s X 36 bits, 290-bit block 14,5 kbit/s 38,4 kbit/s 43.5 kbit/s X 36 bits, 290-bit block 14,5 kbit/s (note) 48 kbit/s 58.0 kbit/s X 36 bits, 290-bit block 14,5 kbit/s (note) 56 kbit/s 58.0 kbit/s 36 bits, 290-bit block 14,5 kbit/s (note) 64 kbit/s 72.5 kbit/s 36 bits, 290-bit block 14,5 kbit/s (note) NOTE: Padding used as specified for TCH/F14.4 channel coding The format used for transferring a synchronous data stream over the radio-interface is a multiframe consisting of 31 data blocks. Each data block contains bits M1 and M2 followed by 288 user data bits sent/received over the radio-interface every 20 ms. The M1-bit carries a 31-bit PN-sequence used for aligning the multiframe(s), whereas the M2-bit carries substream numbering, status information, and NIC-codes as described in subclauses 8.1.1.1 and 8.2.1. The status information carried by the M2-sequence(s) is interpreted as specified in GSM 07.01. When three consecutive M2-bits carry a substream number, this is interpreted as specified in clause 10. Five consecutive M2-bits carrying NIC- information are interpreted according to subclause 8.1.1.1. For the exact NIC-procedures refer to subclause 10.5.1. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 24 (GSM 04.21 version 7.1.0 Release 1998)
|
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 AIUR. 10.1 Data frame distribution into the substreams/channels by the Split/Combine function 10.1.1 Data frame distribution into the substreams/channels by the Split/Combine function (TCH/F9.6 and TCH/F4.8 channel codings) a) In the transparent case the Split/Combine-function distributes the V.110-frames into the substreams and recombines the overall data stream from the substreams according to the following rules: In the overall data stream 1) the frame in position p in substream q precedes the frame in position p in substream q+1,0β€q < n-1 2) the frame in position p in substream n-1 precedes the frame in position p+1 in substream 0; where in the rules above n is the number of substreams. b) In the non-transparent case the Split/Combine-function distributes the RLP-frames or the four V.110-frames making up an RLP-frame (Reference: GSM 08.20, Clause 10) into channels so that one whole RLP-frame is carried through one channel. Furthermore the RLP-frames are distributed into the available channels so that the resulting delay in the overall data stream is kept as small as possible. The receiving Split/Combine-function recombines the overall data stream according to the inherent RLP-frame numbering, i.e. the N(S)-numbers in the RLP-frame header (GSM 04.22). 10.1.2 Data block distribution into the substreams by the Split/Combine function (TCH/F14.4 channel coding) a) Transparent services The Split/Combine-function distributes the user data carried in the 290-bit blocks (Refer to subclause 8.1.1.2) into the substreams and recombines the overall data stream from the substreams according to the following rules: In the overall data stream: 1) the data block in position m of multiframe in substream q precedes the data block in position m of multiframe in substream q+1, 0β€q < n-1, 0β€mβ€30. 2) the data block in position m of multiframe in substream n-1 precedes the data block in position m+1 of multiframe in substream 0; where in the rules above n is the number of substreams. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 25 (GSM 04.21 version 7.1.0 Release 1998) k-2 k-1 k+6 k+5 k+4 k+3 k+2 k+1 k k+6 k+3 k k+7 k+4 k+1 k+8 k+5 k-1 k+2 k-3 k-2 Substr. q=2 Substr. q=1 Substr. q=0 Overall stream position m frame/ block k Figure 2a: Distribution of data frames or data blocks into the substreams in transparent operation b) Non-transparent services In the non-transparent operation the Split/Combine-function distributes the RLP-frames into substreams so that one whole RLP-frame is carried through one substream. This means that the two 290-bit air-interface blocks carrying one RLP-frame are transmitted through the same substream. Furthermore the RLP-frames are distributed into the available substreams so that the resulting delay in the overall data stream is kept as small as possible The receiving Split/Combine-function recombines the overall data stream according to the inherent RLP-frame numbering, i.e. the N(S)-numbers in the RLP-frame header (GSM 04.22).
|
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 is the MSB and S3 the LSB). The substreams are numbered 0, 1, 2, 3 etc. regardless of the physical channels through which the substreams are transmitted. The highest substream number is one less than the number of physical channels in use at a given time; i.e. the numbering cycle changes when physical channels are either added to or removed from a connection. The S4-bit is used for frame synchronisation between the parallel substreams. This bit follows a 31-bit PN-sequence of 0000 1001 0110 0111 1100 0110 1110 101. This thirty one bit sequence is used for substream resynchronisation in cases where delay has occurred on one or more substream(s); the position of a frame in a substream can be determined modulo 31 by the values of the S4-bit in a sequence of 5 consecutive frames including the frame in question. Provided that the relative delay between substreams is less than 75 ms (i.e. less than a 15-frame displacement), this and the frame distribution rules given in subclause 10.1 are sufficient to determine the correct order of the frames. Bits S6, S8, S9, and the other X-bit are used for conveying channel control information according to the relevant terminal adapter function specification. These rules apply to all multislot data AIURs up to and including 48 kbit/s. When the received 48 kbit/s AIUR is converted into 64 kbit/s rate, the bits extracted from the 60-bit radio interface frames (Figure 5) are mapped into the 32- bit frame format of Figure 13. Here the values for the status bits S1, X, S3, and S4 in the 32-bit frame must be derived from status bits S6, X, S8, and S9 in the radio-interface frame because status bits S1, X, S3, and S4 in the upper right hand corner of the 60-bit frame have been used for data substream numbering as described above. In the 11,2 kbit/s frames used for AIURs 56 and 64 kbit/s (Figure 10) the T1, T2, T3 (T1 the MSB and T3 the LSB) are used for carrying the substream numbering as status bits S1, X, and S3 do according to the definition given in the first paragraph of subclause 10.1. Bit T4 is used for carrying the substream synchronisation sequence just as status bit S4 does in the description given in the second paragraph of subclause 10.2.
|
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 100 945 V7.1.0 (2000-08) 26 (GSM 04.21 version 7.1.0 Release 1998)
|
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-padded bit position in the 290-bit radio interface blocks. The NIC-codes are read per substream, i.e. the sequence of five N-bits in a substream carries one complete NIC-code. If NIC-compensation(s) take(s) place in the overall user data flow :
|
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 structure. The five N-bits encode 'negative compensation' as described in clause 5. If more than one substream is used, and more than one negative compensation should be performed the 'extra null bit' is mapped to the first data bit position of the radio interface block which carries the fifth N-bit in the 31-block multiframe structure in as many substreams as necessary to perform all compensations. In those substreams where no compensation is needed the N-bits are set to 'no compensation'. b) From substreams to overall data stream When a radio interface block carrying the fifth bit of an NIC-code indicating negative compensation is received, the receiver discards the first data bit of the block.
|
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 more than one compensation has taken place in the overall data stream, more than one substream carries a NIC-code indicating 'positive compensation'. In those substreams where no NIC-compensation is needed the N-bits indicate 'no compensation'. b) From substreams to overall data stream When an NIC-code indicating positive compensation is received, an extra '0' or '1' depending on whether a compensation of a '0' or '1' is indicated is mapped to before the first data bit position of the block with which the second bit of the NIC-code is associated. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 27 (GSM 04.21 version 7.1.0 Release 1998) 10.5 Padding TCH/F frames when the AIUR is not a multiple of 9,6 or 4,8 kbit/s When the required AIUR is not a multiple of the rates supported by TCH/F4.8 or TCH/F9.6, padding is used for producing the required AIUR. To achieve the required AIUR the data bits are distributed across the substreams 1 to n as follows: - Substream(s) 1 (to n-1) carry multiples of the rate supported by the channel coding used. - Substream n carries the remaining amount of data bits required to achieve the required AIUR. The remainder of data stream n carries padding bits set to binary value '1'. Padding for AIUR 14,4 kbit/s: The frame of the lower substream number carries full 9,6 kbit/s. The frame of the higher substream number carries 4,8 kbit/s of user data in bit positions D1-D24 while bit positions D25-D48 are inserted with binary "1"s. (Figure 15) Padding for AIUR 64 kbit/s: The frames numbered 1-5 carry full 11,2 kbit/s. Frame number 6 carries 8.0 kbit/s of user data in bit positions D1-D40 while bit positions D41-D56 are inserted with binary "1"s. (Figure 16)
|
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 rate nΓ14.5 kbit/s, 1β€nβ€4). Air interface user rate Radio interface rate 4,8 kbit/s 6 kbit/s 9,6 kbit/s 12 kbit/s or 2Γ6 kbit/s 14,4 kbit/s 14,5 kbit/s or 2Γ12 kbit/s or 3Γ6 kbit/s 19,2 kbit/s 2Γ12 kbit/s or 4Γ6 kbit/s 28,8 kbit/s 2Γ14,5 kbit/s or 3Γ12 kbit/s 38,4 kbit/s 3Γ14,5 kbit/s or 4Γ12 kbit/s 43.2 kbit/s 3Γ14,5 kbit/s 57.6 kbit/s 4Γ14,5 kbit/s ETSI ETSI TS 100 945 V7.1.0 (2000-08) 28 (GSM 04.21 version 7.1.0 Release 1998) 11.1 Support of non-transparent operation for TCH/F9.6 and TCH/F4.8 channel codings This access results in the use of a modified CCITT V.110 60 bit frame for non-transparent services (figure 11). In this case, the RA1' function also provides for alignment of four modified CCITT V.110 60 bit frames sent on the same radio slot corresponding with each complete 240 bit frame to be encoded by the radio subsystem as a single unit (see GSM 05.03). The difference between the non-transparent 60 bit frame and the 60 bit frame for the transparent service is that the bit positions used for status in a transparent frame are used to carry data (designated as D' bits in figure 11). NOTE: The status bits SA, SB, and the X bit are embedded in the L2R-PDU frames (see GSM 07.01, 07.02, and 07.03). The first bit of each RLP frame to be transmitted will correspond to the first bit (D1) of the first 60 bit frame in a four frame sequence and the last bit will correspond to the last bit (D'12) of the last 60 bit frame in a four frame sequence. Each 60 bit frame is filled from left to right starting at D1 (see figure 11). The radio subsystem provides for the synchronous transmission and reception of 240 bit RLP frames through a connection consisting of up to four TCH/Fs. An RLP-frame is received/sent from/to a particular radio channel every 20 ms (12 kbit/s radio interface rate) or every 40 ms (6 kbit/s radio interface rate) irrespective of the user rate. The request to use 6 kbit/s radio interface rate on a Full Rate Channel is indicated in the BC-IE by setting the NIRR bit to 6 kbit/s (Negotiation procedure see GSM 07.01) and selecting a Full Rate Channel and Non-Transparent service. If the entity receiving the BC-IE is unable to support this request then the 12 kbit/s radio interface rate shall be provided automatically. Occasions may arise when there is no RLP frame ready to be transmitted. In this case a frame of 240 zeroes will be transmitted. This frame will be discarded by the distant RLP function, due to FCS failure, but will allow physical link synchronization to be maintained between the MS and the MSC. In the case of an asymmetric connection the BTS shall send V110 idle frames towards the MSC on the channels which are unused in the direction from the MS towards the MSC. This will ensure that the IWF does not interprete V110 frames which are not originated from the MS as complete RLP frames. 11.2 Support of non-transparent operation for TCH/F14.4 channel coding In 14,4 kbit/s channel 576-bit RLP-frames are used. The RA1' function is not applied in this case. Instead the RLP-, or in multislot operation the Split/Combine- function, handles the 290-bit data blocks received/sent from/to the network. The M1- bit is used for indicating the RLP-frame halves: in the first half M1= 0 and in the second half M1=1. Bit M2 is used for DTX-indication between the BSS and MSC as described in GSM 08.20 In cases where no RLP-frame is ready to be transmitted, a sequence of 576 '1's is transmitted. This frame will be discarded by the distant RLP-function due to FCS failure. In the case of an asymmetric connection the BTS shall send idle frames towards the IWF on the channels which are unused in the direction from the MS towards the MSC, as specified in GSM 08.60. This will ensure that the IWF does not interpret sequences of frames which are not originated from the MS as complete RLP frames. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 29 (GSM 04.21 version 7.1.0 Release 1998)
|
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 Figure 3: The CCITT V.110 80 bit RA1 frame structure Intermediate Data Rate 8 kbit/s 16 kbit/s 32 kb/s 64 kb/s E1 E2 E3 600 1 0 0 Note 1200 0 1 0 2400 1 1 0 4800 9600 19200 38400 0 1 1 14400 28800 1 0 1 NOTE: The 300 bit/s user data rate is carried on the 600 bit/s synchronous stream by adding stop elements, see subclause 4.1. Figure 4: Coding of data rates D1 D2 D3 D4 D5 D6 S1 D7 D8 D9 D10 D11 D12 X D13 D14 D15 D16 D17 D18 S3 D19 D20 D21 D22 D23 D24 S4 E4 E5 E6 E7 D25 D26 D27 D28 D29 D30 S6 D31 D32 D33 D34 D35 D36 X D37 D38 D39 D40 D41 D42 S8 D43 D44 D45 D46 D47 D48 S9 Figure 5: Modified CCITT V.110 60 bit frame for 9,6 kbit/s transparent data D1 D2 D3 D4 D5 D6 S1 D7 D8 D9 D10 D11 D12 X D13 D14 D15 D16 D17 D18 S3 D19 D20 D21 D22 D23 D24 S4 E4 E5 E6 E7 D25 D26 D27 D28 D29 D30 S6 D31 D32 D33 D34 D35 D36 X D37 D38 D39 D40 D41 D42 S8 D43 D44 D45 D46 D47 D48 S9 Figure 6: Modified CCITT V.110 60 bit frame for 4,8. kbit/s transparent data ETSI ETSI TS 100 945 V7.1.0 (2000-08) 30 (GSM 04.21 version 7.1.0 Release 1998) a) D1 D2 D3 S1 D4 D5 D6 X D7 D8 D9 S3 D10 D11 D12 S4 E4 E5 E6 E7 D13 D14 D15 S6 D16 D17 D18 X D19 D20 D21 S8 D22 D23 D24 S9 b) 0 0 0 0 0 0 0 0 1 D1 D1 D2 D2 D3 D3 S1 1 D4 D4 D5 D5 D6 D6 X 1 D7 D7 D8 D8 D9 D9 S3 1 D10 D10 D11 D11 D12 D12 S4 1 1 1 0 E4 E5 E6 E7 1 D13 D13 D14 D14 D15 D15 S6 1 D16 D16 D17 D17 D18 D18 X 1 D19 D19 D20 D20 D21 D21 S8 1 D22 D22 D23 D23 D24 D24 S9 Figure 7: a) Modified CCITT V.110 36 bit frame for 2,4 kbit/s transparent data and b) the corresponding intermediate rate frame at 8 kbit/s a) D1 D1 D2 S1 D2 D3 D3 X D4 D4 D5 S3 D5 D6 D6 S4 E4 E5 E6 E7 D7 D7 D8 S6 D8 D9 D9 X D10 D10 D11 S8 D11 D12 D12 S9 b) 0 0 0 0 0 0 0 0 1 D1 D1 D1 D1 D2 D2 S1 1 D2 D2 D3 D3 D3 D3 X 1 D4 D4 D4 D4 D5 D5 S3 1 D5 D5 D6 D6 D6 D6 S4 1 0 1 0 E4 E5 E6 E7 1 D7 D7 D7 D7 D8 D8 S6 1 D8 D8 D9 D9 D9 D9 X 1 D10 D10 D10 D10 D11 D11 S8 1 D11 D11 D12 D12 D12 D12 S9 Figure 8: a) Modified CCITT V.110 36 bit frame for 1,2 kbit/s transparent data and b) the corresponding intermediate rate frame at 8 kbit/s ETSI ETSI TS 100 945 V7.1.0 (2000-08) 31 (GSM 04.21 version 7.1.0 Release 1998) a) D1 D1 D1 S1 D1 D2 D2 X D2 D2 D3 S3 D3 D3 D3 S4 E4 E5 E6 E7 D4 D4 D4 S6 D4 D5 D5 X D5 D5 D6 S8 D6 D6 D6 S9 NOTE: The 300 bit/s user data rate is carried on the 600 bit/s synchronous stream by adding stop elements, see subclause 4.1. b) 0 0 0 0 0 0 0 0 1 D1 D1 D1 D1 D1 D1 S1 1 D1 D1 D2 D2 D2 D2 X 1 D2 D2 D2 D2 D3 D3 S3 1 D3 D3 D3 D3 D3 D3 S4 1 1 0 0 E4 E5 E6 E7 (note) 1 D4 D4 D4 D4 D4 D4 S6 1 D4 D4 D5 D5 D5 D5 X 1 D5 D5 D5 D5 D6 D6 S8 1 D6 D6 D6 D6 D6 D6 S9 NOTE: In order to maintain compatibility with Recommendation X.30 (I.461), for the 600 bit/s user rate bit E7 is coded to enable the 4Γ80 bit multiframe synchronisation. To this end, E7 in the fourth 80 bit frame is set to binary '0'. See Table 6 of ITU-T Recommendation V.110(09/92). Figure 9: a) Modified CCITT V.110 36 bit frame for 600 bit/s transparent data and b) the corresponding intermediate rate frame at 8 kbit/s 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 D23 D24 T4 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 D37 D38 D39 D40 D41 D42 D43 D44 D45 D46 D47 D48 D49 D50 D51 D52 D53 D54 D55 D56 Figure 10: Modified CCITT V.110 60 bit frame for 11,2 kbit/s partial rate D1 D2 D3 D4 D5 D6 D'1 D7 D8 D9 D10 D11 D12 D'2 D13 D14 D15 D16 D17 D18 D'3 D19 D20 D21 D22 D23 D24 D'4 D'5 D'6 D'7 D'8 D25 D26 D27 D28 D29 D30 D'9 D31 D32 D33 D34 D35 D36 D'10 D37 D38 D39 D40 D41 D42 D'11 D43 D44 D45 D46 D47 D48 D'12 Figure 11: Modified CCITT V.110 60 bit frame for non-transparent data ETSI ETSI TS 100 945 V7.1.0 (2000-08) 32 (GSM 04.21 version 7.1.0 Release 1998) 0 0 0 0 0 0 0 0 1 D1 D2 D3 D4 D5 D6 S1 1 D7 D8 D9 D10 F F X 1 D11 D12 F F D13 D14 S3 1 F F D15 D16 D17 D18 S4 1 1 0 1 E4 E5 E6 E7 1 D19 D20 D21 D22 D23 D24 S6 1 D25 D26 D27 D28 F F X 1 D29 D30 F F D31 D32 S8 1 F F D33 D34 D35 D36 S9 F =Fill bits, which are set to 1. Figure 12: The CCITT V.110 80 bit frame for 3.6 kbit/s transparent data (8 kbit/s intermediate rate) 1 D1 D2 D3 D4 D5 D6 S1 0 D7 D8 D9 D10 D11 D12 X 1 D13 D14 D15 D16 D17 D18 S3 1 D19 D20 D21 D22 D23 D24 S4 Figure 13: The CCITT V.110 32 bit 48 kbit/s frame structure (64 kbit/s intermediate rate) D1 D2 D3 D4 D5 D6 D7 1 D8 D9 D10 D11 D12 D13 D14 1 D15 D16 D17 D18 D19 D20 D21 1 D22 D23 D24 D25 D26 D27 D28 1 D29 D30 D31 D32 D33 D34 D35 1 D36 D37 D38 D39 D40 D41 D42 1 D43 D44 D45 D46 D47 D48 D49 1 D50 D51 D52 D53 D54 D55 D56 1 Figure 14: The CCITT V.110 64 bit 56 kbit/s frame structure (64 kbit/s intermediate rate , option without status bits) D1 D2 D3 D4 D5 D6 S1 D7 D8 D9 D10 D11 D12 X D13 D14 D15 D16 D17 D18 S3 D19 D20 D21 D22 D23 D24 S4 E4 E5 E6 E7 1 1 1 1 1 1 S6 1 1 1 1 1 1 X 1 1 1 1 1 1 S8 1 1 1 1 1 1 S9 Figure 15: Modified CCITT V.110 60 bit frame for a padded 9,6 kbit/s transparent data frame carrying 4,8 kbit/s with padding ETSI ETSI TS 100 945 V7.1.0 (2000-08) 33 (GSM 04.21 version 7.1.0 Release 1998) 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 D23 D24 T4 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 D37 D38 D39 D40 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Figure 16: Modified CCITT V.110 60 bit frame for a padded 11,2 kbit/s transparent data frame carrying 8.0 kbit/s with padding D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D21 D22 D23 D24 D25 D26 D27 D28 D29 D30 D31 D32 D33 D34 D35 D36 Figure 17: Modified CCITT V.110 36-bit frame received/sent from/to the network at 14,4 kbit/s ETSI ETSI TS 100 945 V7.1.0 (2000-08) 34 (GSM 04.21 version 7.1.0 Release 1998) Annex A (informative): Stacks of rate adaptation A.1 Stacks of rate adaptation for 9,6/4,8 kbit/s single slot operation For transparent data services, the following stacks of rate adaptation are possible: A/S ASY SYN FAX+FA DTE MT BSS RA1'/RA1 RA2 RA2 RA0 RA1/RA1' RA1' FEC (12 or 6 kbit/s) [S] [R] [R] [R] ETSI ETSI TS 100 945 V7.1.0 (2000-08) 35 (GSM 04.21 version 7.1.0 Release 1998) For the non-transparent services, the following stacks of rate adaptation and functions are possible: A/S ASY SYN FAX+FA DTE MT RA1'/RA1 RA2 RA2 RLP + L2R [S] [R] [R] [R] RA1 RA1' FEC (12 or 6kbit/s) BSS RA0 ETSI ETSI TS 100 945 V7.1.0 (2000-08) 36 (GSM 04.21 version 7.1.0 Release 1998) A.2 Stacks of rate adaptation for 14,4 kbit/s single slot operation For transparent data services, the following stacks of rate adaptation are possible: A/S ASY SYN FAX+FA DTE MT BSS RA1'/RAA' RA2 RA0 RA1/RA1' RA1' FEC (14.5 kbit/s) [S] [R] [R] [R] RAA' RA2 ETSI ETSI TS 100 945 V7.1.0 (2000-08) 37 (GSM 04.21 version 7.1.0 Release 1998) For the non-transparent services, the following stacks of rate adaptation and functions are possible: A/S ASY SYN FAX+FA DTE MT RA2 RLP + L2R [S] [R] [R] [R] FEC (14.5 kbit/s) RA1'/RAA' RAA' BSS RA1 RA0 RA2 ETSI ETSI TS 100 945 V7.1.0 (2000-08) 38 (GSM 04.21 version 7.1.0 Release 1998) A.3 Stacks of rate adaptation for 9,6/4,8 kbit/s multi slot operation For transparent data services, the following stacks of rate adaptation are possible: A/S ASY SYN FAX+FA DTE MT BSS RA1'/RA1 MUX RA2 RA0 RA1/RA1' RA1' FEC (12 or 6 kbit/s) [S] [R] [R] [R] S/C S/C ETSI ETSI TS 100 945 V7.1.0 (2000-08) 39 (GSM 04.21 version 7.1.0 Release 1998) For the non-transparent services, the following stacks of rate adaptation and functions are possible: A/S ASY SYN FAX+FA DTE MT RA2 RLP + L2R [S] [R] [R] [R] RA1 RA1' RA1'/RA1 MUX FEC (12 or 6kbit/s) BSS RA0 S/C ETSI ETSI TS 100 945 V7.1.0 (2000-08) 40 (GSM 04.21 version 7.1.0 Release 1998) A.4 Stacks of rate adaptation for 14,4 kbit/s multi slot operation For transparent data services, the following stacks of rate adaptation are possible: RAAβ MUX A/S ASY SYN FAX+FA DTE MT BSS RA1'/RAAβ RA2 RA0 RA1/RA1' RA1' FEC (14.5 kbit/s) [S] [R] [R] [R] S/C S/C ETSI ETSI TS 100 945 V7.1.0 (2000-08) 41 (GSM 04.21 version 7.1.0 Release 1998) For the non-transparent services, the following stacks of rate adaptation and functions are possible: A/S ASY SYN FAX+FA DTE MT RA2 RLP + L2R [S] [R] [R] [R] RA1 RA0 S/C RA1'/RAAβ FEC (14.5 kbit/s) BSS MUX RAAβ ETSI ETSI TS 100 945 V7.1.0 (2000-08) 42 (GSM 04.21 version 7.1.0 Release 1998) Annex B (informative): An example of mapping Network Independent Clocking information for TCH/F14.4 when the S-interface is deployed: In the following, when data bits are moved forwards or backwards between data frames and blocks, padded bit positions are skipped, and the data is moved between bit positions occupied by data bits, i.e. data bit positions. Negative compensation: a) From overall data stream to substreams When the data is mapped from the V.110-frames to the radio interface blocks, the 'extra null bit' (subclause 5.1.1) is dropped and remapped to the first data bit position of radio interface block number 28, which is the block carrying the fifth N-bit in the 31-block multiframe structure. b) From substreams to overall data stream When a radio interface block carrying the fifth bit of an NIC-code indicating negative compensation is received, the receiver discards the data in the first data bit position of the block. Positive compensation: a) From overall data stream to substreams When the data is mapped from the V.110-frames to the radio interface blocks, the extra bit either 0 or 1 is added to the data flow in the correct position (subclause 5.1.1). This means that the 36-bit frame (inside a radio- interface block) in which this has taken place has a bit overflow; this overflow is carried over to the next frames and to the next radio interface blocks; i.e. bit position 1 of the following frame/block would carry the user data bit that originally was the last non-padded bit in the previous frame/block. The overflow is halted in the block carrying the second bit of the NIC-code; the value of the N-bit carried by this block (by bit M2) is set to either 1 or 0 depending on the value of the bit that would be mapped to the first data bit position of the block if the overflow carry over would continue. If this bit is a 1, the N-bit is set to 0 (positive compensation of a 1); if the bit is a 0, the N-bit is set to 1 (positive compensation of a 0). The bit that has been thus coded is not mapped to the first data bit position but carried by the NIC-code. The following bits are moved up by one data bit position. b) From substreams to overall data stream When a radio interface block indicating positive compensation is received from the radio, the NIC is decoded and the data is mapped into the V.110-frames in the overall data stream. Decoding the NIC means that an 'extra bit' emerges. This bit takes its real place in the overall data stream (before the first data bit position of the block carrying the second bit of the NIC-code.) Thus a bit overflow results. This overflow is carried over the V.110- frames until an air-interface block associated with the M2-bit carrying the fifth bit of the NIC-code (subclause 5.1.1) has been fully received. After such block is received the next two suitable V.110-frames carry an NIC- code; the overflow of one bit which has been carried over a sequence of V.110-frames halts here as the second V.110-frame carries one extra bit; the value of the D-bit following the E4-E7 sequence in the V.110-frame is carried by the NIC-code and the following data bits are moved up by one step in the V.110-frame. ETSI ETSI TS 100 945 V7.1.0 (2000-08) 43 (GSM 04.21 version 7.1.0 Release 1998) Annex C (informative): Change history SMG# SPEC CR PHA VERS NEW_VER SUBJECT s21 04.21 A004 2+ 5.0.0 5.1.0 HSCSD s21 04.21 A005 2+ 5.0.0 5.1.0 Support of 14.4 kbit/s (Radio interface related) s22 04.21 A006 2+ 5.1.1 5.2.0 Corrections and improvements for 14.4 kbit/s s22 04.21 A007 2+ 5.1.1 5.2.0 Clarification to HSCSD s23 04.21 A008 R96 5.2.0 5.3.0 Editorial changes, rate adaptation procedure s24 04.21 A009 R96 5.3.0 5.4.0 Removal of 2*14.4=19.2 Transparent configuration s24 04.21 A010 R96 5.3.0 5.4.0 Update of the protocol stack models in Annex A s25 04.21 A011 R96 5.4.0 5.5.0 Clarification to the association between channel codings and intermediate rates s27 04.21 A012 R98 5.5.0 7.0.0 Synchronisation s27 04.21 A013 R96 7.0.0 7.0.1 Break handling 04.21 7.0.2 7.0.3 Update to Version 7.0.3 for Publication smg#32 04.21 A017 R96 7.0.3 7.1.0 Harmonization of the split/combine function ETSI ETSI TS 100 945 V7.1.0 (2000-08) 44 (GSM 04.21 version 7.1.0 Release 1998) History Document history V7.1.0 August 2000 Publication
|
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, deactivation, invocation and interrogation of supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. GSM 04.08 and GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and 02.9x-series. Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and 03.9x-series. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08.
|
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" before the version identity); or c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or d) publications without mention of a specific version, in which case 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. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1". [4] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". [5] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [6] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 1". [7] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 1". [8] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of charge (AoC) supplementary services - Stage 1". [9] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1". ETSI TS 100 941 V6.0.1 (1998-07) 7 GSM 04.10 version 6.0.1 Release 1997 [10] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Services Data (USSD) - Stage 1". [11] GSM 02.91: "Digital cellular telecommunications system (Phase 2+); Explicit Call Transfer (ECT) supplementary service - Stage 1". [12] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [13] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2". [14] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". [15] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [16] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 2". [17] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". [18] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [19] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". [20] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". [21] GSM 03.91: "Digital cellular telecommunications system (Phase 2+); Explicit Call Transfer (ECT) supplementary service - Stage 2". [22] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [23] GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Stations system (MS - BSS) interface; Channel structures and access capabilities". [24] GSM 04.04: "Digital cellular telecommunications system (Phase 2+); Layer 1; General requirements". [25] GSM 04.05: "Digital cellular telecommunications system (Phase 2+); Data Link (DL) layer; General aspects". [26] GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". [27] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [28] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [27] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". [28] GSM 04.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 3". [29] GSM 04.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 3". ETSI TS 100 941 V6.0.1 (1998-07) 8 GSM 04.10 version 6.0.1 Release 1997 [30] GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". [31] GSM 04.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 3". [32] GSM 04.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 3". [33] GSM 04.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 3". [34] GSM 04.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 3". [35] GSM 04.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 3". [36] GSM 04.91: "Digital cellular telecommunications system (Phase 2+); Explicit Call Transfer (ECT) supplementary service - Stage 3". [37] GSM 05.01: "Digital cellular telecommunications system (Phase 2+); Physical layer on the radio path; General description". [38] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". [39] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". [40] GSM 05.04: "Digital cellular telecommunications system; Modulation". [41] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". [42] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". [43] GSM 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronization". [44] GSM 05.90: "Digital cellular telecommunications system; GSM Electro Magnetic Compatibility (EMC) considerations". [45] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". [46] GSM 09.11: "Digital cellular telecommunications system (Phase 2+); Signalling interworking for supplementary services". [47] CCITT Recommendation Q.774 (White Book): "Specifications of Signalling System No.7; Transaction capabilities procedures".
|
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 transfer service available at the layer 2 - layer 3 interface. The Functional protocol is based on the use of the Facility information element and the FACILITY message as well as other specific functional messages specified in GSM 04.80. Standardized services use a functional protocol. A transparent protocol is also provided. The functional protocol requires the knowledge of the related supplementary service by the mobile equipment supporting it. This facilitates mobile equipment operation without human intervention by defining semantics for the protocol elements which the mobile equipment can process on its own. 2.2 Functional procedures for the control of supplementary services
|
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 procedures specify the basic methodology for the control (e.g. registration, erasure, invocation, etc.) of supplementary services. The first category, called the Separate Message Category utilizes separate message types to indicate a desired function. The hold and retrieve families of messages are identified for this category. The second category called the Common Information Element Category utilizes the Facility information element to transport the protocol defined in GSM 04.80. The use of the Facility information element is common to many services, and its contents indicates what type of procedure is being requested. This category can be signalled both in the mobile to network and the network to mobile directions. The control of supplementary services includes the following cases: a) the request of supplementary service procedures during the establishment of a call; b) the request of supplementary service procedures during the clearing of a call; c) the request of call related supplementary service procedures during the active state of a call; d) the request of supplementary service procedures independent from an active call; e) the request of multiple, different supplementary service procedures within a single message; f) the request of supplementary service procedures related to different calls. The correlation of a call related supplementary service operation and the call which it modifies is provided by use of the transaction identifier (cases a, b, c, e and f). The correlation of supplementary service operations and their responses, is provided by the combination of the transaction identifier of the messages containing the Facility information element and the Invoke identifier present within the Facility information element itself (cases a, b, c, d, e and f). ETSI TS 100 941 V6.0.1 (1998-07) 10 GSM 04.10 version 6.0.1 Release 1997 The identification of different supplementary service operations within one single message is provided by the Invoke identifier present within the Facility information element itself (case e). The identification of supplementary service related operations to different calls is provided by using different messages with the corresponding transaction identifier of the appropriate call (case f), i.e. different transaction identifier values are used to identify each call individually.
|
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 Common Information Element Category. The following separate messages are defined: HOLD RETRIEVE HOLD ACKNOWLEDGE RETRIEVE ACKNOWLEDGE HOLD REJECT RETRIEVE REJECT. For detailed description of the Hold and Retrieve functions see GSM 04.83.
|
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 on the outcome of the procedure. The operation state machines, and procedures for management of Invoke IDs specified in CCITT Recommendation Q.774 White Book are used. A REGISTER message, a FACILITY message or certain existing GSM 04.08 Call Control message is used to carry the Facility information element which includes these operations. These operations request, acknowledge or reject the desired supplementary service procedure.
|
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 a SETUP message and to receive from the network a Return result, Return error, or Reject component type within the Facility information element in an ALERTING message, CONNECT message, or any other appropriate message. When a supplementary service invoke component is included within a SETUP message, the originating mobile station shall encode the Facility information element identifier according to one of the three possible ways (see GSM 04.08): a) simple recall alignment; b) advanced recall alignment; c) recall alignment not essential. Encoding of the Facility IEI within the SETUP message for different supplementary services is described in the subclause 2.2.4.1.1. The three different ways of encoding are required to support the network initiated mobile originating call establishment (see subclause 2.2.4.1.2 and GSM 04.08). ETSI TS 100 941 V6.0.1 (1998-07) 11 GSM 04.10 version 6.0.1 Release 1997
|
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 call establishment The Facility and SS Version IE received in the set-up container of the CC_ESTABLISHMENT message shall be handled according to the following rules: The mobile station shall examine the IEI of the Facility IE. If the Facility IEI coding is "simple recall alignment", the mobile station shall copy the Facility IE and SS Version IE from the set-up container to the SETUP message without verifying or modifying the contents of these information elements. If the Facility IEI is encoded as "advanced recall alignment", the mobile station shall examine the SS Version IE. If the mobile station recognises the protocol defined by the SS Version IE, it shall attempt to decode the Facility IE. If the decoding is successful, and the operation is supported by the mobile station, the mobile station shall copy this Facility IE and SS Version IE to the SETUP message. The mobile station shall also store relevant supplementary service information contained within the Facility IE so that any reply to this Facility IE sent by the network will be properly understood and processed. If the mobile station does not recognise the SS Version IE, or the decoding of the Facility IE is unsuccessful, then the call is rejected as described in GSM 04.08. If the Facility IE is encoded as "recall alignment not essential", the mobile station shall examine the SS Version IE . If the mobile station recognises the protocol defined by the SS Version IE, it shall attempt to decode the Facility IE. If the decoding is successful, and the operation is supported by the mobile station, the mobile station shall copy this Facility IE and SS Version IE into the SETUP message. The mobile station shall also store relevant supplementary service information contained within the Facility IE so that any reply to this Facility IE sent by the network will be properly understood and processed. If the mobile station does not recognise the SS Version IE, or the decoding of the Facility IE is unsuccessful, then the SS Version IE and Facility IE are discarded, and NOT copied into the SETUP message. NOTE: A mobile station may include a Facility IE without an associated SS Version IE. This would indicate that the SS operation is encoded using Phase 1 protocols. ETSI TS 100 941 V6.0.1 (1998-07) 12 GSM 04.10 version 6.0.1 Release 1997
|
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 procedure is related only to a single call, the FACILITY message will use the transaction identifier and protocol discriminator of this call. If the supplementary service procedure affects more then one call, the FACILITY message may use the transaction identifier and protocol discriminator of one of these calls. If a call related FACILITY message is sent using the transaction identifier of a call in progress, and this call is cleared due to call related causes, then the transaction identifier may not be cleared simultaneously in all cases. Depending upon the supplementary service invoked, one of the following will occur: - the network or mobile user may retain both the connection and the transaction identifier association and may send a response within a Facility information element in a FACILITY message prior to the initiation of the normal call clearing procedures; or - the network or mobile user may send a response with a Facility information element in the first clearing message (i.e. DISCONNECT, RELEASE or RELEASE COMPLETE message).
|
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 found then the procedures in GSM 04.08 apply. 2) The contents of the Facility IE shall be checked for protocol errors as specified in subclause 2.2.8. If a protocol error is found then the procedures in subclause 2.2.8 apply.
|
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 operation) then the procedures specified in the individual service specifications apply. Examples of the behaviour that could occur in this case are: - the network or MS clears the call and rejects the supplementary services request by means of a clearing message which contains a Return Error component with the appropriate parameter in the Facility Information Element; - the network and MS continue to process the call according to normal GSM 04.08 call control procedures. The supplementary services request is rejected by means of a FACILITY message or appropriate call control message containing a Return Error component with the appropriate parameter in the Facility Information Element; - the network and MS continue to process the call according to the normal GSM 04.08 call control procedures. The supplementary services request is ignored. ETSI TS 100 941 V6.0.1 (1998-07) 13 GSM 04.10 version 6.0.1 Release 1997
|
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 transaction is identified by the transaction identifier associated with the REGISTER message, and the Invoke identifier present in the component part of the Facility information element. Following the REGISTER message one or more FACILITY messages may be transmitted, all of them related by the use of the same transaction identifier. If the transaction is no longer used, it shall be released by sending a RELEASE COMPLETE message. This procedure is specified in detail in clause 3, and the text in clause 3 takes precedence over this introduction. To convey the supplementary service invocation, the Facility information element is used. The Facility information element present either in the REGISTER message or a subsequent message identifies the supplementary service involved and the type of component (i.e. Invoke, Return result, Return error or Reject component). When the REGISTER or FACILITY message contains a Facility information element and the requested service is available, a FACILITY message containing a Facility information element may be returned. One or more exchanges of FACILITY messages may subsequently occur. To terminate the service interaction and release the transaction identifier value, a RELEASE COMPLETE message is sent as specified for the specific supplementary service procedure. The RELEASE COMPLETE message may also contain the Facility information element.
|
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 error is found then the procedures in subclause 3.7 apply. 2) The contents of the Facility IE shall be checked for protocol errors as specified in subclause 2.2.8. If a protocol error is found then the procedures in subclause 2.2.8 apply.
|
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 operation) then the procedures specified in the individual service specifications apply. An example of the behaviour that could occur in this case is: - the MS or network sends a Facility information element containing a return error component in a FACILITY or RELEASE COMPLETE message. If the FACILITY message is used then the MM Connection may continue to be used for further signalling. ETSI TS 100 941 V6.0.1 (1998-07) 14 GSM 04.10 version 6.0.1 Release 1997
|
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 multiple MM connections is defined in GSM 04.07 and 04.08. For call independent operations a single Facility Information Element shall not contain more than one component.
|
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 Generic protocol error handling for the component part of supplementary services operations If (according to the rules specified in GSM 09.02) a supplementary service operation is to be rejected the operation will be denied, and provided the transaction is still in progress, an appropriate reject component will be returned in a Facility Information Element. The handling of the transaction depends on whether the operation is call related or call independent.
|
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 transaction (call) may be released in some exceptional cases where security related services are involved (e.g. Advice of Charge (Charging)). If this behaviour is required, then it will be specified in the relevant specification for the individual service. When a reject component for a call related operation is received by a MS or MSC then it may initiate release of the transaction (call) if this is a specified action for the service the SS operation relates to. Note that this behaviour is intended to allow security related services to release calls if one entity in the system does not support the service. The normal action should be to allow the call to continue. If the call related transaction has terminated before the operation has been rejected (e.g. the component containing the error was 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 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 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.