ETSI TC SMG#24 Tdoc SMG Madrid, Spain December 1997

Transcription

1 ETSI TC SMG#24 Tdoc SMG Madrid, Spain December 1997 Source: SMG4 Agenda item: 5.5 Title: Change Requests on GSM 07.05, and on Workitem V.120/RDI interworking The attached CRs are correction to the API specifications and There is a pair of CRs correcting behaviour of networks and MS supporting V.120/RDI. SPEC VERS CR RE V PHA SE CAT SUBJECT STC_DO C strat egic WORKITEM A037 R96 F Unnecessary conversion in Annex A 97p356 No A044 R96 D Update of alternating call figures 97p355 No A045 R96 F V.120/RDI correction 97p384 No V.120/RDI A046 2 F AT+CPIN or AT+CKPD must be mandatory in some cases (phase 2) A047 R96 A AT+CPIN or AT+CKPD must be mandatory in some cases (phase 2+) A036 R96 F Correction of V.120 and RDI interworking 97P504 No P505 No P501 No V.120/RDI Number of Pages:

2 Blank Page

3 SMG4 Tdoc 97P356 CHANGE REQUEST No. A037 Technical Specification GSM version Submitted to SMG for approval without presentation ("non-strategic") [ x ] with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [ R96 ] Work item: Technical enhancements Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ ] Network [ ] Source: SMG4 Date: Subject: Unnecessary conversion in Annex A Category: F - Correction [ X ] A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ x ] C - Functional modification of Feature [ ] D - Editorial modification [ ] Reason for change: É Æ E conversion is not needed because É is in Sections affected, and additional explanation of details of change (if needed): Annex A If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Other comments: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached:

4 Page 2 CR to GSM Version 5.4.0: November 1997 Annex A (Normative): Character Set Conversions for SMS Text Mode Conversion from PCCP437 (PC-8 Code Page 437) to GSM: A0 B0 C0 D0 E0 F F E 1D E C 6F F B 7C 7D F F 08 5D F C A LF - 2A 3A 4A 5A 6A 7A 04 5E B - - 2B 3B 4B - 6B C - - 2C 3C 4C - 6C D CR - 2D 3D 4D - 6D E - - 2E 3E 4E - 6E - 5B F - - 2F 3F 4F 11 6F - 0E : â Ö a 2 : ç Ö Ç 3 : ê Ö e 4 : ë Ö e 5 : ï Ö i 6 : î Ö i 7 : É Ö E 78 : ô Ö o 89 : û Ö u 910 : ÿ Ö y 10 : á Ö a 11 : á Ö a 112 : í Ö i 123 : ó Ö o 134 : ú Ö u Conversion from PCDN (PC-8 Danish/ Norwegian) to GSM: A0 B0 C0 D0 E0 F F E 1D E C 6F F B 7C 7D F F 08 5D F C A LF - 2A 3A 4A 5A 6A 7A 04 5E B - - 2B 3B 4B - 6B C C - - 2C 3C 4C - 6C D CR - 2D 3D 4D - 6D B E - - 2E 3E 4E - 6E - 5B F - - 2F 3F 4F 11 6F - 0E : â Ö a 2 : ç Ö Ç 3 : ê Ö e 4 : ë Ö e 5 : ï Ö i

5 Page 3 CR to GSM Version 5.4.0: November : î Ö i 7 : É Ö E 78 : ô Ö o 89 : û Ö u 910 : ÿ Ö y 10 á Ö a : 11 : á Ö a 112 : í Ö i 123 : ó Ö o 134 : ú Ö u Conversion from (ISO 8859 Latin 1) to GSM: A0 B0 C0 D0 E0 F F D D F F F B 4F 145 7B 6F E 4F 156 0F 6F C 5C 1D 7C F B 04 0C F A LF - 2A 3A 4A 5A 6A 7A B - - 2B 3B 4B - 6B C - - 2C 3C 4C - 6C E 07 7E 0D CR - 2D 3D 4D - 6D E - - 2E 3E 4E - 6E F - - 2F 3F 4F 11 6F E : À Ö A 2 : Á Ö A 3 : Â Ö A 4 : Ã Ö A 5 : È Ö E 6 : É Ö E 67 : Ê Ö E 78 : Ë Ö E 89 : Ì Ö I 910 : Í Ö I 10 : Î Ö I 11 : Î Ö I 112 : Ï Ö I 123 : Ò Ö O 134 : Ó Ö O 145 : Ô Ö O 15 : Õ Ö O 16 : Õ Ö O 167 : Ù Ö U 178 : Ú Ö U 189 : Û Ö U 1920 : Ý Ö Y 20 : á Ö a 21 : á Ö a 212 : â Ö a 223 : ã Ö a 234 : ç Ö Ç 245 : ê Ö e 25 : ë Ö e 26 : ë Ö e 267 : í Ö i 278 : î Ö i 289 : ï Ö i 2930 : ó Ö o 30 : ô Ö o 31 : ô Ö o 312 : õ Ö o 323 : ú Ö u 334 : û Ö u 345 : ý Ö y 35 : ÿ Ö y 36 : ÿ Ö y Conversions from GSM default alphabet to above character sets are otherwise straightforward, but no conversions of the characters listed below tables are applied.

6 SMG4 Tdoc 97P355 CHANGE REQUEST No. A044 Technical Specification GSM version Submitted to SMG for approval without presentation ("non-strategic") [ x ] with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [ x ] Work item: Technical enhancements Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ ] Network [ ] Source: SMG4 Date: Subject: Update of alternating call figures Category: F - Correction [ ] A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ x ] Reason for change: In voice mode disconnection on DTR drop or ATH is optional (as specified in SMG4 tdoc 97P326). Data related intermediate result codes (+CR, +ER, +DR, +ILRR) should be displayed when changing from voice to data mode, but not when creating the call in voice mode. Sections affected, and additional explanation of details of change (if needed): Section 6.6, Annex E, F, G. If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Other comments: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached:

7 Page 2 CR to Draft prets (GSM Version 5.4.0): November Alternating mode call control method This subclause describes the procedure to handle alternating mode calls with AT commands. Procedures are mandatory when alternating mode calls are implemented in the TA. NOTE: ATH and drop DTR will not necessarily cause a hangup from voice mode. If the +CVHU is implemented the behaviour shall be controlled by its setting. Voice followed by data call (bearer service 81) Figure 1 shows commands to start the call, to switch from voice to data (In-Call Modification) and to hang up the call. +CMOD and +FCLASS commands indicate the current settings before dialling or answering command, not that they shall be given just before D or A command. Refer subclause "Cellular result codes +CRC" for possible +CRING result code values. Refer Annex F for a detailed example. MO AT+CMOD=3 AT+FCLASS=0 MT +CRING: VOICE/XXX AT+CMOD=3;+FCLASS=0 ATDxxx; ATA VOICE ATD or ATA or remote initiated DATA AT+CHUP or remote initiated hangup (or ATH or drop DTR) ATH or drop DTR or AT+CHUP or remote initiated hangup HANGUP TA sets +CMOD=0 Voice/ data call (bearer service number 61) Figure 1: Voice followed by data call Figure 2 shows the commands to start the call, to switch between modes (In-Call Modification) and to hang up the call. +CMOD and +FCLASS commands indicate the current settings before dialling or answering command, not that they shall be given just before D or A command. Refer subclause "Cellular result codes +CRC" for possible +CRING result code values. Refer Annex E for a detailed example.

8 Page 3 CR to Draft prets (GSM Version 5.4.0): November 1997 MT voice first +CRING: ALT VOICE/XXX AT+CMOD=2;+FCLASS=0 MO AT+CMOD=2 AT+FCLASS=0 MT data first +CRING: ALT XXX/VOICE AT+CMOD=2;+FCLASS=0 ATA ATDxxx; ATDxxx ATA VOICE AT+CHUP or remote initiated hangup (or ATH or drop DTR) ATD or ATA or remote initiated ATH or drop DTR or remote initiated DATA AT+CHUP or remote initiated hangup HANGUP TA sets +CMOD=0 Voice/ fax call (teleservice number 61) Figure 2: Alternating voice and data call Figure 3 shows the commands to start the call, to switch between modes (In-Call Modification) and to hang up the call. +CMOD and +FCLASS commands indicate the current settings before dialling or answering command, not that they shall be given just before D or A command. The parameter "x" of +FCLASS command can be 1, 1.0, 2 or 2.0. NOTE: The transition from fax mode to voice mode is for further study. MT voice first +CRING: ALT VOICE/FAX AT+CMOD=1;+FCLASS=x MO AT+CMOD=1 AT+FCLASS=x MT fax first +CRING: ALT FAX/VOICE AT+CMOD=1;+FCLASS=x ATA ATDxxx; ATDxxx ATA VOICE ATD or remote initiated FAX AT+CHUP or remote initiated hangup (or ATH or drop DTR) refer ITU-T T.31 [11] and T.32 [12] for different hangup possibilities (also AT+CHUP shall hangup) HANGUP TA sets +CMOD=0 Figure 3: Alternating voice and fax call

9 Page 4 CR to Draft prets (GSM Version 5.4.0): November 1997 Annex E (informative): Mobile originated alternating voice/data call example Figure E.1 illustrates the possible transitions in MO BS 61 call. Responses and result codes generated by TA are in bold face. In this example, data part of the call is asynchronous non-transparent 9600 bps service. OFF-LINE AT+CBST=7,0,1 AT+COLP=1; +CR=1; +DR=1; +ILRR=1 AT+CMOD=2; +FCLASS=0 RLP negotiation failure +COLP: ,145 +CR: REL ASYNC NO CARRIER ATD12345; success +COLP: ,145 connection failure NO CARRIER AT+CEER +CEER: failure cause other possible failure codes BUSY/NO ANSWER/ERROR ATD12345 success +COLP: ,145 +CR: REL ASYNC +DR: NONE +ILRR: CONNECT 9600 remote hangup VOICE ATD (or ATA) remote initiated in-call modification successful AT+CHUP (or ATH or drop DTR ) NO CARRIER in-call modification success +CR: REL ASYNC +DR: NONE +ILRR: CONNECT 9600 in-call modification failure ERROR AT+CEER +CEER: failure cause +CR: REL ASYNC +DR: NONE +ILRR: CONNECT 9600 in-call modification success in-call modification failure ERROR AT+CEER +CEER: failure cause OFF-LINE TA sets +CMOD=0 ATH (or drop DTR) remote initiated in-call modification successful AT+CHUP DATA (V.24 circuit 109 ON) NO CARRIER remote hangup Figure E.1: MO BS 61 call

10 Page 5 CR to Draft prets (GSM Version 5.4.0): November 1997 Annex F (informative): Mobile terminated voice followed by data call example Figure F.1 illustrates the possible transitions in MT BS 81 call. Responses and result codes generated by TA are in bold face. In this example, data part of the call is asynchronous non-transparent 9600 bps service. OFF-LINE AT+CLIP=1; +CR=1; +DR=1; +ILRR=1; +CRC=1 +CRING: VOICE/REL ASYNC +CLIP: ,145 AT+CMOD=3; +FCLASS=0; A success connection failure NO CARRIER AT+CEER +CEER: failure cause general failure ERROR VOICE ATD (or ATA) remote initiated in-call modification successful in-call modification success +CR: REL ASYNC +DR: NONE +ILRR: CONNECT 9600 in-call modification failure ERROR AT+CEER +CEER: failure cause +CR: REL ASYNC +DR: NONE +ILRR: CONNECT 9600 DATA (V.24 circuit 109 ON) remote hangup AT+CHUP (or ATH or drop DTR) ATH (or AT+CHUP or drop DTR) remote hangup NO CARRIER NO CARRIER OFF-LINE TA sets +CMOD=0 Figure F.1: MT BS 81 call

11 Page 6 CR to Draft prets (GSM Version 5.4.0): November 1997 Annex G (informative): Voice call example Figure G.1 illustrates the possible transitions in both MT and MO TS 11 calls. Responses and result codes generated by TA are in bold face. MO without COLP AT+COLP=0 ATD12345; general failure ERROR MT AT+CLIP=1; +CRC=1 +CRING: VOICE +CLIP: ,145 ATA connection failure NO CARRIER AT+CEER +CEER: failure cause success connection failure NO CARRIER AT+CEER +CEER: failure cause (no indication on successful call setup) VOICE call active call setup started (remote ring or other network generated tones) MO with COLP AT+COLP=1 ATD12345; success +COLP: ,145 connection failure NO CARRIER AT+CEER +CEER: failure cause remote busy BUSY general failure ERROR remote hangup AT+CHUP (or ATH or drop DTR) NO CARRIER Figure G.1: TS 11 calls

12 ETSI STC SMG4 Bonn, Germany, 24th - 28th November 1997 Tdoc SMG4 97P384 CHANGE REQUEST No. A045 Technical Specification GSM version Submitted to SMG for approval without presentation ("non-strategic") [ ] with presentation ("strategic") [X] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [R96] Work item: V.120 Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ X ] Network [ ] Source: SMG4 Date: Subject: V.120 Interworking Category: F - Correction [X] A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ ] Reason for change: 1. Addition to section 2 of references to CCITT/ITU-T V.110, V.120 and X Corrections to the description of the +CV120 command. Sections affected, and additional explanation of details of change (if needed): Sections 2 and 6. If other core Specifications are affected, necessary (and attached) Joint CRs:

13 Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached: Other comments: 1. References to CCITT V.110, V.120 and X.31 are missing from section SMG4 agreed document 97p161 with changes at its Whistler meeting. Unfortunately the modified version, 97p329 - CR A039, omitted part of the command description and the default parameter values which had been agreed without changes. This CR corrects this omission.

14 Page 3 Draft prets (GSM version 5.3.0): August 1997 Additions to section 2 [35] CCITT Recommendation V.110: "Support of data terminal equipments (DTEs) with V-Series interfaces by an integrated services digital network". [36] CCITT Recommendation V.120: "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". [37] ITU-T Recommendation X.31: "Support of packet mode terminal equipment by an ISDN". Changes to section V.120 rate adaption protocol +CV120 Table 111: +CV120 parameter command syntax Command Possible response(s) +CV120=[<rah>[,<mfm>[,<mo de>[,<llineg>[,<assign>[, <negtype>]]]]]] +CV120? +CV120: <rah>, <mfm>, <mode>, <llineg>, <assign>, <negtype> +CV120=? +CV120: (list of supported <rah>s), (list of supported <mfm>s), (list of supported <mode>s), (list of supported <llineg>s), (list of supported <assign>s), (list of supported <negtype>s) Description Set command sets the values of the V.120 protocol parameters (defined in CCITT V.120) that are carried in the GSM BC and/or LLC information elements. Read command returns current settings for the V.120 parameters. Test command returns values supported by the TA as a compound value. Defined values <rah> 0 rate adaption header not included 1 rate adaption header included (mandatory for protocol sensitive modes). <mfm> 0 multiple frame establishment not supported, only UI frames allowed 1 multiple frame establishment supported, both I and UI frames allowed. <mode> 0 bit transparent mode of operation 1 protocol sensitive mode of operation. <llineg> 0 no negotiation, LLI = 256 only 1 negotiation allowed. Note - <negtype> indicates the connection over which the negotiation is performed. <assign>

15 0 message originator is "default assignee" 1 message originator is "assignor only". Page 4 Draft prets (GSM version 5.3.0): August 1997 <negtype> 0 negotiation is done using logical link zero 1 negotiation is done with USER INFORMATION messages on a temporary signalling connection. GSM does not support all the possible modes of V.120 operation. However, in order to accommodate possible future additions, the complete set of parameters is included in the command. Currently supported values The permitted values are: 1, 1 or 0, 1, 0, 0, 0. Default values A recommended set of default values is: 1, 1, 1, 0, 0, 0. Implementation Mandatory, if the MS supports V.120 interworking.

16 SMG4 Tdoc97P504 CHANGE REQUEST No. A 046 Technical Specification GSM version Submitted to SMG for approval without presentation ("non-strategic")[ x ] with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ X ] Phase 2+: [ ] Work item: Technical enhancements Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [x ] Network [ ] Source: SMG4 Date: Subject: AT+CPIN or AT+CKPD must be mandatory in some cases Category: F - Correction [ x ] A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ ] Reason for change: Correcting inconsistency with GSM 02.30, where it is stated that one should be able to unblock a blocked SIM card. This CR corrects this by making +CPIN or +CKPD mandatory for MSs supporting AT commands only (i.e. MSs with no keypad). Sections affected, and additional explanation of details of change (if needed): Section 8.3 and 8.7 If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] Phase 2(+) SIM in Phase 1 ME [ ] Other comments:

17 SMG4 Tdoc97P504 First modified section 8.3 Enter PIN +CPIN Table 1: +CPIN parameter command syntax Command Possible response(s) +CPIN=<pin>[,<newpin +CME ERROR: <err> >] +CPIN? +CPIN: <code> +CME ERROR: <err> +CPIN=? Description Set command sends to the ME a password which is necessary before it can be operated (SIM PIN, SIM PUK, PH-SIM PIN, etc.). If the PIN is to be entered twice, the TA shall automatically repeat the PIN. If no PIN request is pending, no action is taken towards ME and an error message, +CME ERROR, is returned to TE. Refer subclause 9.2 for possible <err> values. If the PIN required is SIM PUK or SIM PUK2, the second pin is required. This second pin, <newpin>, is used to replace the old pin in the SIM. NOTE: Commands which interact with ME that are accepted when ME is pending SIM PIN, SIM PUK, or PH-SIM are: +CGMI, +CGMM, +CGMR, +CGSN, D112; (emergency call), +CPAS, +CFUN, +CPIN, +CDIS (read and test command only), and +CIND (read and test command only). Read command returns an alphanumeric string indicating whether some password is required or not. Defined values <pin>, <newpin>: string type values <code> values reserved by this ETS: READY ME is not pending for any password SIM PIN ME is waiting SIM PIN to be given SIM PUK ME is waiting SIM PUK to be given PH-SIM PIN ME is waiting phone-to-sim card password to be given PH-FSIM PIN ME is waiting phone-to-very first SIM card password to be given PH-FSIM PUK ME is waiting phone-to-very first SIM card unblocking password to be given SIM PIN2 ME is waiting SIM PIN2 to be given (this <code> is recommended to be returned only when the last executed command resulted in PIN2 authentication failure (i.e. +CME ERROR: 17); if PIN2 is not entered right after the failure, it is recommended that ME does not block its operation) SIM PUK2 ME is waiting SIM PUK2 to be given (this <code> is recommended to be returned only when the last executed command resulted in PUK2 authentication failure (i.e. +CME ERROR: 18); if PUK2 and new PIN2 are not entered right after the failure, it is recommended that ME does not block its operation) PH-NET PIN ME is waiting network personalisation password to be given PH-NET PUK ME is waiting network personalisation unblocking password to be given PH-NETSUB PIN ME is waiting network subset personalisation password to be given

18 SMG4 Tdoc97P504 PH-NETSUB PUK ME is waiting network subset personalisation unblocking password to be given PH-SP PIN ME is waiting service provider personalisation password to be given PH-SP PUK ME is waiting service provider personalisation unblocking password to be given PH-CORP PIN ME is waiting corporate personalisation password to be given PH-CORP PUK ME is waiting corporate personalisation unblocking password to be given Implementation Optional. Mandatory for MEs not supporting the +CKPD command and supporting AT commands only. Next modified section 8.7 Keypad control +CKPD Table 2: +CKPD action command syntax Command Possible response(s) +CKPD=<keys>[,<time>[,<pause> +CME ERROR: <err> ]] +CKPD=? Description Execution command emulates ME keypad by giving each keystroke as a character in a string <keys>. <time>*0.1 seconds is the time to stroke each key and <pause>*0.1 seconds is the length of pause between two strokes. If emulating fails in an ME error, +CME ERROR: <err> is returned. Refer subclause 9.2 for <err> values. This command should be accepted ( returned) before actually starting to press the keys. Thus unsolicited result codes of key pressings and display events can be returned (refer subclause "Mobile Equipment event reporting +CMER"). Defined values <keys>: string of characters representing keys as listed in the following table (based on PCCA STD-101 Annex table I-3). Colon character (IRA 58) followed by one character can be used to indicate a manufacturer specific key not listed here. All characters from a semicolon character (IRA 59) to the next single semicolon character are treated as alpha entries and are not converted to key equivalents. All semicolon characters inside alpha entries should be duplicated in the TE and stripped to one before entering to the ME. Pause character (IRA 87 or 119) can be used to pause between key pressings for a time specified by <pause>. All IRA values not listed here are reserved. Table 3: Character codes Char IRA Comment (+ some known key symbols) (dec) # 35 hash (number sign) % 37 percent sign (P) * 42 star (*) number keys

19 SMG4 Tdoc97P504 : 58 escape character for manufacturer specific keys ; 59 escape character for string entering < 60 left arrow > 62 right 64 alpha key (α/abc) A/a 65/97 channel A (A) B/b 66/98 channel B (B) C/c 67/99 clear display (C/CLR) D/d 68/100 volume down E/e 69/101 connection end (END) F/f 70/102 function (FCN) L/l 76/108 phone lock (LOCK) M/m 77/109 menu (MENU) P/p 80/112 power (PWR) Q/q 81/113 quiet/mute (MUTE) R/r 82/114 recall last number (R/RCL/MR) S/s 83/115 connection start (SEND) T/t 84/116 store/ memory (STO/M/M+) U/u 85/117 volume up V/v 86/118 down arrow W/w 87/119 pause character X/x 88/120 auxiliary (AUX) Y/y 89/121 delete last character (C) [ 91 soft key 1 ] 93 soft key 2 ^ 94 up arrow <time>, <pause>: seconds (default values are manufacturer specific, but should be so long that a normal ME can handle keystrokes correctly) Implementation Optional. Mandatory for MEs not supporting the +CPIN command and supporting AT commands only.

20 SMG4 Tdoc97P505 CHANGE REQUEST No. A 047 Technical Specification GSM version Submitted to SMG for approval without presentation ("non-strategic") [ x ] with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [x] Work item: Technical enhancements Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [x ] Network [ ] Source: SMG4 Date: Subject: AT+CPIN or AT+CKPD must be mandatory in some cases Category: F - Correction [ x ] A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ ] Reason for change: Correcting inconsistency with GSM 02.30, where it is stated that one should be able to unblock a blocked SIM card. This CR corrects this by making +CPIN or +CKPD mandatory for MSs supporting AT commands only (i.e. MSs with no keypad). Sections affected, and additional explanation of details of change (if needed): Section 8.3 and 8.7 If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] Phase 2(+) SIM in Phase 1 ME [ ] Other comments:

21 SMG4 Tdoc97P505 First modified section 8.3 Enter PIN +CPIN Table 1: +CPIN parameter command syntax Command Possible response(s) +CPIN=<pin>[,<newpin +CME ERROR: <err> >] +CPIN? +CPIN: <code> +CME ERROR: <err> +CPIN=? Description Set command sends to the ME a password which is necessary before it can be operated (SIM PIN, SIM PUK, PH-SIM PIN, etc.). If the PIN is to be entered twice, the TA shall automatically repeat the PIN. If no PIN request is pending, no action is taken towards ME and an error message, +CME ERROR, is returned to TE. Refer subclause 9.2 for possible <err> values. If the PIN required is SIM PUK or SIM PUK2, the second pin is required. This second pin, <newpin>, is used to replace the old pin in the SIM. NOTE: Commands which interact with ME that are accepted when ME is pending SIM PIN, SIM PUK, or PH-SIM are: +CGMI, +CGMM, +CGMR, +CGSN, D112; (emergency call), +CPAS, +CFUN, +CPIN, +CDIS (read and test command only), and +CIND (read and test command only). Read command returns an alphanumeric string indicating whether some password is required or not. Defined values <pin>, <newpin>: string type values <code> values reserved by this ETS: READY ME is not pending for any password SIM PIN ME is waiting SIM PIN to be given SIM PUK ME is waiting SIM PUK to be given PH-SIM PIN ME is waiting phone-to-sim card password to be given PH-FSIM PIN ME is waiting phone-to-very first SIM card password to be given PH-FSIM PUK ME is waiting phone-to-very first SIM card unblocking password to be given SIM PIN2 ME is waiting SIM PIN2 to be given (this <code> is recommended to be returned only when the last executed command resulted in PIN2 authentication failure (i.e. +CME ERROR: 17); if PIN2 is not entered right after the failure, it is recommended that ME does not block its operation) SIM PUK2 ME is waiting SIM PUK2 to be given (this <code> is recommended to be returned only when the last executed command resulted in PUK2 authentication failure (i.e. +CME ERROR: 18); if PUK2 and new PIN2 are not entered right after the failure, it is recommended that ME does not block its operation) PH-NET PIN ME is waiting network personalisation password to be given PH-NET PUK ME is waiting network personalisation unblocking password to be given PH-NETSUB PIN ME is waiting network subset personalisation password to be given

22 SMG4 Tdoc97P505 PH-NETSUB PUK ME is waiting network subset personalisation unblocking password to be given PH-SP PIN ME is waiting service provider personalisation password to be given PH-SP PUK ME is waiting service provider personalisation unblocking password to be given PH-CORP PIN ME is waiting corporate personalisation password to be given PH-CORP PUK ME is waiting corporate personalisation unblocking password to be given Implementation Optional. Mandatory for MEs not supporting the +CKPD command and supporting AT commands only. Next modified section 8.7 Keypad control +CKPD Table 2: +CKPD action command syntax Command Possible response(s) +CKPD=<keys>[,<time>[,<pause> +CME ERROR: <err> ]] +CKPD=? Description Execution command emulates ME keypad by giving each keystroke as a character in a string <keys>. <time>*0.1 seconds is the time to stroke each key and <pause>*0.1 seconds is the length of pause between two strokes. If emulating fails in an ME error, +CME ERROR: <err> is returned. Refer subclause 9.2 for <err> values. This command should be accepted ( returned) before actually starting to press the keys. Thus unsolicited result codes of key pressings and display events can be returned (refer subclause "Mobile Equipment event reporting +CMER"). Defined values <keys>: string of characters representing keys as listed in the following table (based on PCCA STD-101 Annex table I-3). Colon character (IRA 58) followed by one character can be used to indicate a manufacturer specific key not listed here. All characters from a semicolon character (IRA 59) to the next single semicolon character are treated as alpha entries and are not converted to key equivalents. All semicolon characters inside alpha entries should be duplicated in the TE and stripped to one before entering to the ME. Pause character (IRA 87 or 119) can be used to pause between key pressings for a time specified by <pause>. All IRA values not listed here are reserved. Table 3: Character codes Char IRA Comment (+ some known key symbols) (dec) # 35 hash (number sign) % 37 percent sign (P) * 42 star (*) number keys

23 SMG4 Tdoc97P505 : 58 escape character for manufacturer specific keys ; 59 escape character for string entering < 60 left arrow > 62 right 64 alpha key (α/abc) A/a 65/97 channel A (A) B/b 66/98 channel B (B) C/c 67/99 clear display (C/CLR) D/d 68/100 volume down E/e 69/101 connection end (END) F/f 70/102 function (FCN) L/l 76/108 phone lock (LOCK) M/m 77/109 menu (MENU) P/p 80/112 power (PWR) Q/q 81/113 quiet/mute (MUTE) R/r 82/114 recall last number (R/RCL/MR) S/s 83/115 connection start (SEND) T/t 84/116 store/ memory (STO/M/M+) U/u 85/117 volume up V/v 86/118 down arrow W/w 87/119 pause character X/x 88/120 auxiliary (AUX) Y/y 89/121 delete last character (C) [ 91 soft key 1 ] 93 soft key 2 ^ 94 up arrow <time>, <pause>: seconds (default values are manufacturer specific, but should be so long that a normal ME can handle keystrokes correctly) Implementation Optional. Mandatory for MEs not supporting the +CPIN command and supporting AT commands only.

24 ETSI STC SMG4 Bonn, Germany, 24th - 28th November 1997 Tdoc SMG4 97P501 CHANGE REQUEST No. A032r2 Technical Specification GSM version Submitted to SMG for approval without presentation ("non-strategic") [ X ] with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [R96] Work item: V.120 Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ ] Network [ ] Source: SMG4 Date: Subject: V.120 and RDI Interworking Category: F - Correction [X] A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ ] Reason for change: Clarification of existing material and provision of additional material. Sections affected, and additional explanation of details of change (if needed): Section 10. For additional explanation, see next page. If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached: Other comments: None.

25 Page 2 Draft prets (GSM version 5.2.1): April 1997 Notes on the proposed changes Changes are proposed for sections 2, 3 and 10 of GSM TS There are a few additional small changes to section 10 that are not described here. Changes are marked as inserted and deleted text. 1. Section 2. Normative references References are added to CCITT I.464 and Q Section 3. Definitions and abbreviations Definitions are added for - unrestricted 64 kbit/s network, restricted 64 kbit/s network, directly connected restricted 64 kbit/s network, indirectly connected restricted 64 kbit/s network. 3. Tables 6A and 6B The table items on 'other ITC' and 'other rate adaption' have been clarified. The notes on V.120 and RDI interworking have been amended. In particular, direct and indirect RDI interworking scenarios are distinguished. 4. Figure 9: Protocol structure in the MSC/IWF (non-transparent) Figure 9 has been updated to include V.120 and RDI. Also, for clarity, the "RAx" functions on the ISDN side have been labelled "V.110". A stray label, "TE" has been deleted. 5. Section In band signalling mapping flow control Section Break Indication Section Support of out-band flow control Section Establishment of end-to-end terminal synchronizations V.120 material added 6. Section Additional aspects of V.120 interworking This section (formerly entitled 'V.120 interworking') has been restructured and enlarged. 7. Section Interworking with restricted 64 kbit/s networks This has been expanded to describe in more detail how V.110 and V.120 are carried over restricted 64 kbit/s networks and to identify the two RDI interworking scenarios (direct and indirect connection to restricted digital network).

26 Page 3 Draft prets (GSM version 5.5.0): November Normative references The following text is added - [43] CCITT Recommendation I.464: "Multiplexing, rate adaption and support of existing interfaces for restricted 64 kbit/s transfer capability". [44] CCITT Recommendation Q.922 (1992): "DSS 1 Data link layer: ISDN data link layer specification for frame mode bearer services" 3 Definitions and abbreviations The following text is added - unrestricted 64 kbit/s network: A digital network which has 64 kbit/s octet-structured Information Transfer Capability (ITC) with no restrictions on the contents of each octet. restricted 64 kbit/s network: CCITT I.464 defines '"restricted 64 kbit/s transfer capability" as "64 kbit/s octet-structured capability with the exception that an all-zero octet is not permitted". In this specification, the term "restricted 64 kbit/s network" refers not only to networks with the I.464 restriction but also to those in which the 8th bit of each octet is unusable for data transmission. directly connected restricted 64 kbit/s network: A restricted 64 kbit/s network which is connected directly to the MSC/IWF. indirectly connected restricted 64 kbit/s network: A restricted 64 kbit/s network which is connected to the MSC/IWF via an unrestricted 64 kbit/s network. 10 Interworking to the ISDN The text on the following pages has changes -

27 Page 4 Draft prets (GSM version 5.5.0): November 1997 The following tables (6A + 6B) show that only the ISDN BC is used for mapping (exceptions are indicated). NOTE: The ISDN/GSM BC-IE mapping shall be performed as specified in tables 6A and 6B. This must be done to allow setup of a compatible end-to-end connection between two MSs or one MS and an ISDN terminal. It has been acknowledged that octets 5a, 5b, 5c and 5d or a combination of them may also be sent and received in 3,1 khz audio calls. Follow-up versions of ETS (i.e. ETS ), confirm this interpretation. This is especially important for MOC-ISDN terminating calls, where early Customer Premise Equipment (e.g. PABXs), may reject these calls. In the following table the comparison is drawn between parameters in the GSM call set up request message and that of the ISDN call set up request message. In some cases no comparable values are available and these will be marked as such. In these cases reference will need to be made to the table of network interworking in GSM to identify the appropriate choice. In some cases it is not necessary to support a particular option, and in this case those parameters will be annotated appropriately. Table 6A-09.07: Comparable setting of parameters in GSM and ETS (ETSI ISDN user to network signalling) Mobile Originated Octet GSM parameter value as in GSM Octet ETS parameter value 1 Bearer Capability IEI 1 Bearer Capability IEI 2 Length of BC contents 2 Length of BC contents 3 # #4 3 #4 3 #3..1 5a #7..6 Radio channel requirement half rate channel full rate channel dual, full, rate preferred dual, half rate preferred Coding Standard GSM standard coding Transfer mode circuit mode packet mode (note7) Information transfer capability speech unrestricted. digital 3,1 khz audio ex PLMN facsimile group 3 (note 1) other ITC (see octet 5a) 3 # # #5..1 No comparable field Coding Standard CCITT standardized coding Transfer mode circuit mode packet mode Other ITC restricted digital (note 18) (note 18) Information transfer capability speech unrestricted digital 3,1 khz audio see table 4 in GSM no comparable value 4 #7 Compression (note 14) data compression allowed data compression not allowed No comparable field 4 #6..5 Structure SDU integrity unstructured 4a #7..5 Structure (note 4) 4 #4 Duplex mode half duplex full duplex 5d #7 Duplex mode half duplex full duplex 4 #3 Configuration point to point 4a #4..3 Configuration (note 4) point to point

28 Page 5 Draft prets (GSM version 5.5.0): November 1997 (continued)

29 Page 6 Draft prets (GSM version 5.5.0): November 1997 Table 6A (continued): Comparable setting of parameters in GSM and ETS (ETSI ISDN user to network signalling) Mobile Originated 4 #1 Octet GSM parameter value as in GSM Establishment demand 4 NIRR (note 12) meaning Data 4.8kbpsbit/s, FR nt, 6kbpsbit/s radio interface is requested 5 #5..4 5a #5..4 Rate adaptation no rate adaptation (note 2) V.110/X.30 rate adaptation CCITT X.31 flag stuffing No comparable value (note 11) No comparable value (note 11) No comparable value (note 11) other rate adaptation (see octet 5a) 4a # #5..1 Octet ETS parameter value Establishment (note 4) demand No comparable field User information layer 1 protocol no comparable value CCITT standardized rate adaption V.110/X.30 CCITT standardized rate adaption X.31 flag stuffing Recommendation G.711 µ law Recommendation G.711 A law (note 3) Recommendation G kbit/s ADPCM and I.460 No comparable value Other rate adaptation V.120 (note 17) No comparable value 5 #3..1 Signalling access protocol I.440/I.450 X.21 X.28, ded.pad, indiv.nui X.28, ded PAD, univ.nui X.28, non-ded PAD X.32 No comparable field 6 #1 Synchronous/asynchronous synchronous asynchronous 5a #7 Synchronous/asynchronous synchronous asynchronous 6 #5..2 User info. layer 1 protocol default layer 1 protocol 5 #5..1 User info. layer 1 protocol see section under rate adaptation for GSM above 6a #7 Number of stop bits 1 bit 2 bits 5c #7..6 Number of stop bits 1 bit 2 bits 6a #6 Negotiation In band neg. not possible no comparable value 5a #6 Negotiation In band neg. not possible In band neg. possible (note 10) 6a #5 Number of data bits 7 bits 8 bits 5c #5..4 Number of data bits excluding parity if present 7 bits 8 bits (continued)

30 Page 7 Draft prets (GSM version 5.5.0): November 1997 Table 6A (continued): Comparable setting of parameters in GSM and ETS (ETSI ISDN user to network signalling) Mobile Originated Octet 6a #4..1 6b #7..6 6b #5 6b #4 6b #3..1 6c #7..6 6c # #5..1 GSM parameter value as in GSM User rate 0.3 kbit/s 1.2 kbit/s 2.4 kbit/s 4.8 kbit/s 9.6 kbit/s 12 kbit/s (note 7) 1.2 kbit/s / 75 bit/s any value no comparable value Intermediate rate 8 kbit/s 16 kbit/s any value NIC on Tx does not require requires (note7) NIC on Rx cannot accept can accept (note 7) Parity information odd even none forced to 0 forced to 1 Connection element transparent non-transparent (RLP) both, transp. preferred both, non-transp. preferred Modem type none V.21 V.22 V.22bis V.23 V.26ter V.32 modem for undef. interface autobauding type 1 User info. layer 2 protocol X.25 link level ISO 6429, codeset 0 COPnoFlCt videotex profile 1 (note 7) X.75 layer 2 modified (CAPI) 5a #5..1 5b #7..6 5b #5b 5b #4 5c #3..1 5d #6..1 Octet ETS parameter value User rate 0.3 kbit/s 1.2 kbit/s 2.4 kbit/s 4.8 kbit/s 9.6 kbit/s 12 kbit/s 75 bit/s / 1.2 kbit/s 19.2 kbit/s (note 14) Ebits or inband negotiation (note 10) Intermediate rate (note 13) 8 kbit/s or not used 16 kbit/s or not used 32 kbit/s or not used (note 14) NIC on Tx does not require requires (note 8) NIC on Rx cannot accept can accept (note 8) Parity information odd even none forced to 0 forced to 1 No comparable field Modem type (note 9) no comparable value (note 5) V.21 V.22 V.22bis V.23 V.26ter V.32 No comparable value (note 5) No comparable value (note 5, note 10) 6 User info.layer 2 protocol (note 6) X.25 link level no comparable value no comparable value no comparable value X.25 link level

31 Page 8 Draft prets (GSM version 5.5.0): November 1997 Table 6A (concluded): Comparable setting of parameters in GSM and ETS (ETSI ISDN user to network signalling) Mobile Originated 6d #5..1 6e #3..1 6f #4..1 6d #7..6 Fixed network user rate (note 15) FNUR not applicable (note 7) 9,6 kbit/s 12 kbit/s (note 7) 14,4 kbit/s 19,2 kbit/s 28,8 kbit/s 38,4 kbit/s 48,0 kbit/s 56,0 kbit/s 64,0 kbit/s Maximum number of traffic channels 1 TCH 2 TCH 3 TCH 4 TCH 5 TCH 6 TCH 7 TCH (note 7) 8 TCH (note 7) Wanted air interface user rate air interface user rate not applicable (note 7) 9,6 kbit/s 14,4 kbit/s 19,2 kbit/s 28,8 kbit/s 38,4 kbit/s 43,2 kbit/s 57,6 kbit/s interpreted by the network as 38.4 kbit/s (note 7) Other modem type (note 15) No other modem type 5a #5..1 5d #6..1 User rate no comparable value 9,6 kbit/s 12 kbit/s 14,4 kbit/s 19,2 kbit/s 28,8 kbit/s 38,4 kbit/s 48,0 kbit/s 56,0 kbit/s no comparable value (note 16) No comparable fieldno comparable field No comparable valueno comparable field Modem type no comparable value 6e #7..4 6f #7..5 V.34 Acceptable channel coding(s) TCH/F4.8 acceptable TCH/F9.6 acceptable TCH/F14.4 acceptable User initiated modification indicator User initiated modification not required User initiated modification upto 1 TCH/F may be requested User initiated modification upto 2 TCH/F may be requested User initiated modification upto 3 TCH/F may be requested User initiated modification upto 4 TCH/F may be requested V.34 No comparable fieldno comparable field No comparable fieldno comparable field The application rules for coding the information elements ISDN-BC/LLC/HLC as set out in ETR 018 and ETS shall apply. Other field values in the ISDN BC-IE of ETS not supported in GSM are:

32 Information transfer rate: In this case default 64 kbit/s is selected. Page 9 Draft prets (GSM version 5.5.0): November 1997 Symmetry: Flow control on transmission: Flow control on reception: In this case default bi-directional symmetric is selected for all user data rates (note 5). This shall be selected if outband flow control applies. This shall be selected if outband flow control applies. NOTE: Outband flow control is indicated by the absence of the UIL2P parameter for non-transparent connections. User information layer 3 protocol: Octet 7 shall not be sent unless specific application rules are given for particular cases (to be defined by GSM). End-to-end significant User Information layer 3 protocol shall be sent by LLC. NOTE 1: In the case where GSM BC "Information Transfer Capability" indicates "Facsimile group 3" and only a single GSM BC is contained in the call set-up request then this shall be mapped to an ISDN BC with: Coding standard: CCITT Information Transfer capability 3,1 khz audio Transfer mode circuit Information transfer rate 64 kbit/s User layer 1 protocol G711 A Law and - If an HLC is not present, the network will insert a "Facsimile group 2/3" HLC. - If an HLC element is present, the network will pass it through unmodified. In the case where GSM BC "Information Transfer Capability" indicates "Facsimile group 3" and two GSM BCs are contained in the call set-up request, then the same ISDN BC as mentioned above is created. If the first GSM BC indicates "facsimile group 3" an HLC "facsimile group 2/3" will be inserted by the network (if not received from the MS). However if the first GSM BC indicates "speech", the network will not send a HLC, irrespective where a HLC was received from the MS or not. NOTE 2: NOTE 3: NOTE 4: NOTE 5: NOTE 6: NOTE 7: NOTE 8: NOTE 9: This value is present in combination with information transfer capability parameter value "3,1 khz audio Ex PLMN" or "facsimile group 3" and will therefore be mapped to the value "CCITT Recommendation G.711 A Law" of the ETS parameter user layer 1 protocol (see note 3). The value "CCITT Recommendation G.711 A Law" applies only when the ETS parameter information transfer capability indicates "3,1 khz audio" or "speech". Octets 4a and 4b shall not be included because default values apply. In this case octet 5d shall not be included. Octet 6 shall not be sent unless specific application rules are given for a particular case (GSM specified). End-to-end significant user information layer 2 protocol shall be sent by LLC. Not used for currently defined Bearer Services and Teleservices. These values will only be set if the "Information Transfer Capability" indicates "3,1 khz audio", synchronous data transmission is used and octet 5b of the ISDN BC is present. The mapping of the modem type shall be according to Draft ETS /prA1.

33 Page 10 Draft prets (GSM version 5.5.0): November 1997 NOTE 10: NOTE 11: The GSM BC-IE parameter value "autobauding modem type 1" will be mapped to the ISDN BC-IE parameter values "inband negotiation possible" and "user rate indicated by E-bits specified in CCITT Rec I.460 or may be negotiated inband" (octet 5a of ISDN BC-IE). In case of data compression high speed modems, like V.32bis and/or V.34 may be used in the IWF. The ITC value of the GSM BC-IE "speech", "3,1 khz audio Ex PLMN" will indicate these requirements. NOTE 12: For the use of NIRR see GSM NOTE 13: The value of the Intermediate Rate field of the ISDN Bearer Capability information element shall only depend on the values of the User Rate and the Information Transfer Capability in the same information element. The correspondence is: Intermediate Rate = not used if User Rate > than 19.2 kbit/s Intermediate Rate = 32 kbit/s if User Rate = 19,2 kbit/s or 14.4 kbit/s Intermediate Rate = 16 kbit/s if User Rate = 9,6 kbit/s Intermediate Rate = 8 kbit/s otherwise. In case of Audio calls the value of the Intermediate Rate may be set to "not used". NOTE 14: If compression is supported by the MSC and "data compression allowed" is indicated, then the ISDN user rate for UDI calls shall be set as follows. If the parameter FNUR is present the ISDN user rate shall be set to this value. Otherwise the GSM user rate shall be mapped to an equal or any higher ISDN user rate value (in case of V.110 the highest ISDN user rate shall be 19.2 kbit/s). The Intermediate Rate shall be set to an appropriate value.(see subclause ). In case of "3,1 khz audio" the modem must try to negotiate data compression and flow control (see subclause ). In case of "autobauding type 1" high speed modems may be used (see note 10). NOTE 15: NOTE 16: User rate of the GSM-BC is overriden by the fixed network user rate of the GSM BC-IE if available When the MT indicates autobauding, modem for undefined interface or none, the other modem type shall be set to no other modem type ; any other value of the modem type is overridden by the other modem type value (see GSM 07.01). The ISDN-BC will consist of the octets 1 to 4 only, coded: Coding standard: CCITT Information Transfer capability UDI Transfer mode circuit Information transfer rate 64 kbit/s NOTE 17: V.120 interworking is selected. If an LLC element is not present, the network will insert an LLC. If an LLC is present it may be modified. The GSM-BC parameters negotiated with the MS shall be mapped to the LLC parameters according to the rules in this table or to CCITT V.120, respectively. The LLC parameter Rate Adaptation will be set to "V.120". When interworking with unrestricted 64 kbps networks only octets 1 to 3 shall be included in the ISDN BC as shown below: Coding standard: Information Transfer capability CCITT UDI When interworking with unrestricted 64 kbit/s networks the ISDN BC shall be coded according to note 16. When interworking wit