SMG4/TSG-CN3/TSG-T2
London, 15-19 March 1999	TSGT2#2(99)059

Agenda Item:	

Source:	NTT DoCoMo

Title: 	Comparison Tables about AT Commands of T2-99056 and GSM07.07 and Change Reasons 
	
Document for:	Discussion

___________________________________________________________________________

1.	Introduction
AT commands of GSM07.07 should be changed a little for the 3G Mobile system.  It is described about change points from GSM07.07 and that reasons in this paper. 

2.	Change Points and that Reasons
2.1.	Select TE character set +CSCS

Change points: Add Japanese character set
Reasons: There is no character set of Japanese in GSM 07.07.

Table 1:	Comparison table about +CSCS of GSM07.07 and IrMC.
GSM07.07	Defined values
<chset> (conversion schemes not listed here can be defined by manufacturers):
"GSM"	GSM default alphabet 
"HEX"	character strings consist only of hexadecimal numbers from 00 to FF
"IRA"	international reference alphabet 
"PCCPxxx"	PC character set Code Page xxx
"PCDN"	PC Danish/Norwegian character set
"UCS2"	16-bit universal multiple-octet coded character set
"8859-n"	ISO 8859 Latin n (1‑6) character set
"8859-C"	ISO 8859 Latin/Cyrillic character set
"8859-A"	ISO 8859 Latin/Arabic character set
"8859-G"	ISO 8859 Latin/Greek character set
"8859-H"              ISO 8859 Latin/Hebrew character set	
IrMC	(iii) Defined values 
<chset>(conversion schemes not listed here can be defined by manufactures):
“IRA”	             international reference alphabet 
“GSM”                GMS default alphabet 
“2022-JP”          ISO-2022-JP character set
“SJIS”	            Shift-JIS
“PCCPxxx”         PC character set code page xxx
“PCDN”             C Danish/Norwegian character set
“UCS2”              16-bit universal multiple-octet coded character set 
“8859-n”	           ISO 8859 Latin n(1-6) character set
“8859-C”	           ISO 8859 Latin/Cyrillic character set
“8859-A”	           ISO 8859 Latin/Arabic character set
“8859-G”           ISO 8859 Latin/Greek character set
“8859-H”	           ISO 8859 Latin/Hebrew character set
“HEX”                character strings consist only of hexadecimal numbers from 00 to FF	

2.2.	Direct dialling from phonebooks

Change points: (1) Add the function to handle the property values under Property Name ‘N’ 
	           (2) Add the function to handle the index of object file
	           (3) Add the function to be dialled by the one listed first in the selected entry
Reasons: The direct dialling from the format of the memory by IrMC (VCARD) should be able to use.

Table 2:	Comparison table about D> of GSM07.07 and IrMC.
GSM07.07	1.	D><str>[I][G][;]	
originate call to phone number which corresponding alphanumeric field is <str> (if possible, all available memories should be searched for the correct entry)
2.	D>mem<n>[I][G][;]	
originate call to phone number in memory mem entry location <n> (available memories may be queried with Select Phonebook Storage test command +CPBS=?; mem could be e.g. ME)
3.	D><n>[I][G][;]	
originate call to phone number in entry location <n> (it is manufacturer specific which memory storage of ME, SIM and TA is used; command Select Phonebook Memory Storage +CPBS setting is recommended to be used)	
IrMC	1.	D><str>[;]	
originate call to phone number which corresponding character field is <str> (if possible, all available memories should be searched for the correct entry).  If the format of the memory is specified by VCARD, property values under Property Name 'N' are compared with <str>.
2.	D>mem<n>[;]	
originate call to phone number in memory ‘mem’ entry location <n> (available memories may be those returned by +CPBS=?).  If the format of the memory is specified by VCARD, <n> indicates the index of object file.
3.	D><n>[;]	
originate call to phone number in entry location <n> (it is manufacturer specific which memory storage of SIM and ME is used.) If the format of the memory is specified by VCARD, <n> indicates the index of object file.

Description
ME and SIM can contain phone books which have a phone number and a character field for each phone book entry location. The use of V.25ter dialing command ensures that direct dialing from ME and SIM phone book is possible through ordinary communications software which just gives the phone number field to be filled and then use the D command to originate the call. ( If vCard is the format used for phone book entries, then the phone number to be dialed is the one listed first in the selected entry )	

2.3.	Facility lock +CLCK

Change points: Add the OBEX lock function
Reasons: It should be added functions about OBEX in the 3G Mobile System.
               IrMC specified that object exchange (e.g., phonebooks, calendars, messages and notes) between devices by the IrOBEX protocol.

Table 3:	Comparison table about +CLCK of GSM07.07 and IrMC.
GSM07.07	Defined values
<fac>:
"CS"	CNTRL (lock CoNTRoL surface (e.g. phone keyboard))
"AO" 	BAOC (Barr All Outgoing Calls)
"PS"	 lock Phone to SIM card 
"SC" 	lock SIM card 
"OI" 	BOIC (Barr Outgoing International Calls)
"OX" 	BOIC-exHC (Barr Outgoing International Calls except to Home Country)
"AI" 	BAIC (Barr All Incoming Calls) 
"IR" 	BIC-Roam (Barr Incoming Calls when Roaming outside the home country)
"NM" 	barr incoming calls from numbers Not stored to ME memory
"NS" 	barr incoming calls from numbers Not stored to SIM memory
"NA" 	barr incoming calls from numbers Not stored to Any memory
"AB" 	All Barring services
"AG" 	All outGoing barring services
"AC" 	All inComing barring services
.
.
.	
IrMC	Defined values
<fac>:
"CS"	CNTRL (lock CoNTRoL surface (e.g. phone keyboard))
"AO" 	BAOC (Barr All Outgoing Calls)
"IRDA"	IROBEX
"PS"	 lock Phone to SIM card 
"SC" 	lock SIM card 
"OI" 	BOIC (Barr Outgoing International Calls)
"OX" 	BOIC-exHC (Barr Outgoing International Calls except to Home Country)
"AI" 	BAIC (Barr All Incoming Calls) 
"IR" 	BIC-Roam (Barr Incoming Calls when Roaming outside the home country)
"NM" 	barr incoming calls from numbers Not stored to ME memory
"NS" 	barr incoming calls from numbers Not stored to SIM memory
"NA" 	barr incoming calls from numbers Not stored to Any memory
"AB" 	All Barring services
"AG" 	All outGoing barring services
"AC" 	All inComing barring services
.
.
.	

2.4.	Change password +CPWD

Change points: Add the function, which change password toward the multiple lock function at a time.
Reasons: To make it simplify to use.

Table 4:	Comparison table about +CPWD of GSM07.07 and IrMC
GSM07.07	Defined values
<fac>: 
"P2"	SIM PIN2
refer Facility Lock +CLCK for other values
<oldpwd>, <newpwd>: string type; <oldpwd> shall be the same as password specified for       the facility from the ME user interface or with command Change Password +CPWD and <newpwd> is the new password; maximum length of password can be determined with <pwdlength>
<pwdlength>: integer type maximum length of the password for the facility	
IrMC	Defined values
<fac>: refer Facility Lock +CLCK
"P2" SIM PIN2
Additionally  "G1"  "G2"  "G3"  "G4" can be used.  These parameters indicate the groups of facilities set by manufacturer. ex) Facilities "CS" and "AO" may be set in "G2".  In this case the passwords for "CS" and "AO" are changed by one operation whose <fac> is "G2".
<oldpwd>, <newpwd>: string type; <oldpwd> shall be the same as password specified for the ME user interface or with command Change Password +CPWD and <newpwd> is the new password; maximum length of password can be determined with <pwdlength>
<pwdlength>: integer type maximum length of the password for the facility	

2.5.	Read phonebook entries +CPBR

Change points: Add the function not to return <type> value, when the format is specified by VCARD.
Reasons: VCARD doesn’t have a <type> value.

Table 5:	Comparison table about +CPBR of GSM07.07 and IrMC
GSM07.07	Possible response(s)
[+CPBR: <index1>,<number>,<type>,<text>[[...]
<CR><LF>+CPBR: <index2>,<number>,<type>,<text>]]
+CME ERROR: <err>

Defined values
<type>: type of address octet in integer format (refer GSM 04.08 [8] subclause 10.5.4.7)
	
IrMC	Possible response(s
+CPBR: <index1>,<number>,[<type>],<text>[[...]
<CR><LF>+CPBR: <index2>,<number>,[<type>],<text>]

Defined values
<type>: type of address octet in integer format, corresponding bitmap is "1XXXYYYY" where 
XXX=	0: unknown
		1: international number
		2: national number
		3: network specific number
		4: dedicated access, short code
YYYY=	0: unknown
		1: ISDN/telephony numbering plan (Rec. E.164/E.163)
		3: data numbering plan (Rec.X.121)
		4: telex numbering plan (Rec.F.69)
		8: national numbering plan
		9: private numbering plan
		All other values are reserved.
For more information refer to GSM 04.08 section 10.5.4.7.
When the format of phone book is specified by VCARD, <type>value is not return.

2.6.	Write phonebook entry +CPBW

Change points: Add the function to ignore <type> value, when the format is specified by VCARD.
Reasons: VCARD doesn’t have a <type> value.

Table 6:	Comparison table about +CPBW of GSM07.07 and IrMC
GSM07.07	Defined values
<index>: integer type values in the range of location numbers of phonebook memory
<number>: string type phone number of format <type>
<type>: type of address octet in integer format (refer GSM 04.08 [8] subclause 10.5.4.7) ; default 145 when dialling string includes international access code character "+", otherwise 129	
IrMC	Defined values
<type>   type of address octet in integer format (refer +CPBR) ; default 145 when dialing string includes   international access code character ‘+’, otherwise 129, If the format of phone book is specified by VCARD, <type>value may be ignored.

3.	Reference

[1]	3GPP T2-99056: “3rd Generation Partnership Project (3GPP); Technical Specification Group Terminals (TSG-T); A Proposal for External Interface.”
[2]	Infrared Data Association: “Specifications for Ir Mobile Communications, IrMC, Version 1.0.”