- 18 -
TD 67 (WP 1/16)
INTERNATIONAL TELECOMMUNICATION UNION / STUDY GROUP 16TELECOMMUNICATION
STANDARDIZATION SECTOR
STUDY PERIOD 2009-2012 / TD 67 (WP 1/16)
English only
Original: English
Question(s): / 14/16 / Geneva, 26 October - 6 November 2009
TEMPORARY DOCUMENT
Source: / Rapporteur Q14/16
Title: / Baseline text for draft new ITU-T V.AMAT “Asynchronous serial command interface for assistive and multi-functional communication devices”
The following is modified text based upon the original content of TD18/WP1 for V.AMAT. This text follows the instructions given and recorded in the report of Q11/16 from the July 2007 meeting see below).
Note from Rapporteur:
The following is an extract from the Q11/16 section of the WP1/16 report from the July 2007 meeting on the topic of this document.
“It was unanimously agreed that the scope of the proposed new Recommendation shall be limited to document only the AT commands in terms of their definitions and actions they perform. The existing text contained in TD205/WP1 will have to be modified to comply with this agreement.”
The Editor of this document was to remove text which does not pertain to the actual definition of the AT commands that are covered by the intended application.
This text has completed the reformatting that began in the previous version to be consistent with the format as used in the V.25x series of Recommendations.
It was also noticed during the re-formatting process that there are still several open questions such as undefined parameter values and error codes. There are also some descriptions that need additional clarification. It is hoped that this text can be reviewed and improved. If the open questions can be resolved, this text can be considered for consent at this meeting.
- 18 -
TD 67 (WP 1/16)
CONTENTS
1. Scope 3
2. References 3
3. Definitions 3
4. Abbreviations and acronyms 4
4.1 Conventions 4
5. Assistive Device commands 4
5.1 Calendar 4
5.1.1 Read vCalendar 4
5.1.2 Write vCalendar 5
5.2 Modify Display Parameters 5
5.2.1 Read or Write Current Font colour 5
5.2.2 Read and Modify Font size 6
5.2.3 Read or Modify Background colour 6
5.3 Cursor control 7
5.3.1 Pointing Device Click 7
5.3.2 Pointing Device Move 8
5.3.3 Pointing Device Drag 8
Example 9
5.4 Menu 9
5.4.1 Notification of menu changes 9
5.4.2 Navigating on the external device 10
5.5 Screen 11
5.5.1 Send Screen Dump 11
5.6 Speech-to-text 12
5.6.1 Enables Speech-to-Text 12
5.7 Text telephony 12
5.7.1 Sending text 12
5.7.2 Receiving text 13
5.7.3 Setting preference for real-time text 13
5.8 Text-to-speech 14
5.8.1 Configure text-to-speech service 14
5.9 Time-out 15
5.9.1 Change Time-out 15
5.10 Volume 16
5.10.1 Change Volume 16
Appendix I Mobile device functionality and their commands 17
Draft new ITU-T Rec. V.AMAT
Asynchronous serial command interface for assistive and multi-functional communication devices
AAP Summary
[To be added before Consent]
Summary
This Recommendation is applicable to the interconnection of multi-functional communication devices with devices intended to provide Assistive capabilities for those communication devices. It defines a range of serial binary commands that comply to the format and general rules of Recommendation ITU-T V.250 via a range of suitable interfaces.
Source
ITUT Recommendation V.25x was prepared by Question 14 of ITUT Study Group16 (200920012).
1. Scope
This Recommendation builds upon the current Asynchronous DCE control Recommendation ITU-T V.250, to include command protocols to support the interfacing of Assisitive Controlling Devices with communication devices over a range of suitable serial binary data interfaces.
2. References
The following ITU-T Recommendations and other references contain provisions, which, through reference in this text, constitute provisions of this Recommendation.
- ITU-T V.250: "Serial asynchronous automatic dialling and control".
- ETSI TR 102 068: "Human Factors (HF); Requirements for assistive technology devices in ICT".
- ETSI TS 102 223: "Smart Cards; Card Application Toolkit (CAT) (Release 7)".
- Infra-Red Data Association: IrDA Object Exchange (OBEX) Protocol Version 1.4 Available at http://www.irda.org/ [Note from TSB: not an A.5 qualified organization; is there an alternative? Is this really normative?]
- "vCalendar The Electronic Calendaring and Scheduling Exchange Format Version 1.0". [Note from TSB: not an A.5 qualified organization. Is this really normative? Why not make reference to iCal, RFC 2445, an evolution from v Calendar?]
3. Definitions
3.1 Terms defined elsewhere
N/A.
3.2 Terms defined in this Recommendation
For the purposes of the present document, the following terms and definitions apply:
3.2.1 Assistive technology device: Device used by a disabled person to prevent, compensate, relieve or neutralize any resultant handicap and which has the ability to interface to an ICT device. NOTE: the term external device is used for mobile external device or assistive technology device
3.2.2 OBject EXchange Protocol: Protocol for the exchange of data objects between devices.
4. Abbreviations and acronyms
This Recommendation uses the following abbreviations and acronyms:
AT / AttentionIrDA / Infrared Data Association
ISO / International Organization for Standardization
MMS / Multimedia Messaging Service
OBEX / Object Exchange
SMS / Short Message Service
USB / Universal Serial Bus
4.1 Conventions
<Describe any particular notation, style, presentation, etc. used within the Recommendation, if any>
5. Assistive Device commands
Some communication devices provide users with a variety of applications (e.g. games, navigation and location tracking, photograph manipulation, currency conversion) either built-in when purchased, or added later. The use of application functionality at a content and information level is beyond the scope of this recommendation, but all applications shall provide input, output and control functionality that is usable by all users.
The following sections define V.250 like commands that allow Assisitive Devices to interact with multi-functional communication devices over a serial binary data interface.
5.1 Calendar
The following sets of commands allow users to be able to use a calendar function on a multi-functional communication device, including reading and writing calendar objects.
5.1.1 Read vCalendar
Syntax
+CCALR=<begin date>, <end date>
Description
This command causes the reading of vCalendar information within the parameters specified.
The result are the vCalendar objects between the <begin date>, and <end date>.
Defined values
None
Result codes
<vCalendar>,<vCalendar>,<vCalendar>,<vCalendar> OK
+CCALR ERROR: <error code
Implementation
Calendar information is transferred using the vCalendar format.
Test Syntax
+CCALR=?
What is the response to this ?
5.1.2 Write vCalendar
Syntax
+CCALW=<vCalendar>
Description
The +CCALW command writes vCalendar objects.
Defined values
<vCalendar>: vCalendar exchange format.
Result codes
+CCALW: OK
+CCALW: ERROR: <error code
Test Syntax
+CCALW=?
Implementation
Calendar information is transferred using the vCalendar format.
5.2 Modify Display Parameters
The following command set supports the reading and modification of a display appearance. This includes, character and background colour and the font size.
5.2.1 Read or Write Current Font colour
Syntax
+CFCLR=<R>,<G>,<B>
Description
The +CFCLR command sets font/text colours of a visual display.
Defined values
<R>: The value of the colour red, in the range of 0-255.
<G>: The value of the colour green, in the range of 0-255.
<B>: The value of the colour blue, in the range of 0-255.
Result codes
+CFCLR: OK
+CFCLR ERROR: <error code
Read Syntax
+CFCLR?
The receiving device shall transmit one or two strings of information text to the Assistive Device, consisting of:
+CFCLR:<R>,<G>,<B>
Test Syntax
+CFCLR=?
What is the response to this ?
5.2.2 Read and Modify Font size
Syntax
+CFSZ=<size>
Description
The +CFSZ command allows an Assistive Device to modify and set the font size of characters used on display of a multi-functional communication device.
Defined values
<size> is the preferred font size in pixels.
Result codes
+CFSZ: OK
+CFSZ ERROR: <error code
Read Syntax
+CFSZ?
The response to this query is the current font size of the text being displayed of the communication device.
+CFSZ: <size>
Test Syntax
+CFSZ=?
What is the response to this ?
5.2.3 Read or Modify Background colour
Syntax
+CBKG=<R>,<G>,<B>
Description
The +CBKG command sets the background colours of the display of a multi-functional communication device.
Defined values
<R>: The value of the colour red, in the range of 0-255.
<G>: The value of the colour green, in the range of 0-255.
<B>: The value of the colour blue, in the range of 0-255.
Result codes
+CBKG: OK
+CBKG ERROR: <error code>
Read Syntax
+CBKG?
The response to this query is the current background colour set of the display of the communication device.
+CBKG=<R>,<G>,<B>
Test Syntax
+CBKG=?
5.3 Cursor control
Mobility-impaired users may need alternative pointing devices to control the on-screen cursor/pointer. The user shall be able to make a click on a specific coordinate X, Y. The clicks can be various numbers such as single click or double click. Clicks can be done with various buttons, so the buttons being used for the click can also be defined.
5.3.1 Pointing Device Click
Syntax
+CCLIK=<X>,<Y>,< numberOfClicks >,< buttonNumber >
Description
This command provides the option to click on a specific coordinate X, Y with alternative pointing devices. The clicks can be various numbers such as single click or double click.
Defined values
specific coordinate X, Y
<X> is the coordinate in the x-direction and is an integer. (Value range?)
<Y> is the coordinate in the y-direction and is an integer.
<numberOfClicks> defines the number of clicks.
<buttonNumber> defines what button is used for the click.
Result codes
+CCLIK: OK
+CCLIK ERROR: <error code>
Read Syntax
+CCLIK?
The response to this command is <OK>
Test Syntax
+CCLIK=?
The response to this command is the following string
Max <X>, Max <Y>, Max <NumberOfClicks>, Max <buttonNumber>
5.3.2 Pointing Device Move
Syntax
+CMOV=<X>,<Y>
Description
This command allows the user to be able to move the cursor to a specific coordinate X, Y. This command can be used several times in order to show the motion.
Defined values
<X> is the coordinate in the x-direction and is an integer. (Value range?)
<Y> is the coordinate in the y-direction and is an integer.
Result codes
+CMOV: OK
+CMOV ERROR: <error code>
Read Syntax
+CMOV?
OK
Test Syntax
+CMOV=?
Max <X>, Max <Y>
5.3.3 Pointing Device Drag
Syntax
+CDRG=<X>,<Y>, <status>
Description
The user shall be able to drag something with the cursor to a specific coordinate X, Y. This command can be used several times in order to show the motion.
Defined values
<X> is the coordinate in the x-direction and is an integer. (What is the value range?)
<Y> is the coordinate in the y-direction and is an integer.
<status> is an integer value that represents the status of the drag operation.
0 Start Drag
1 Move Drag
2 Release Drag
9 No Drag
Result codes
+CDRG: OK
+CDRG ERROR: <error code>
Read Syntax
+CDRG?
OK
Test Syntax
+CDRG=?
Max <X>, Max <Y>, Max <status>
Example
The following illustrates an example sequence of commands (in the order listed below):
AT+CDRG=27, 39, 0 (27 is X coordinate, 39 is Y coordinate and 0 is Start Drag)
AT+CDRG=30, 42, 1
AT+CDRG=35, 47, 1
AT+CDRG=40, 52, 1
AT+CDRG=45, 57, 1
AT+CDRG=50, 62, 2 (50 is X coordinate, 62 is Y coordinate and 2 is Release Drag)
5.4 Menu
The purpose of the functionality for this set of commands is to the means to customize and provide menus that suit user needs.
5.4.1 Notification of menu changes
Syntax
+CMEN=<n>
Description
Set command controls the presentation of an unsolicited result code
+CMEN: <menu id>, <menu name>, <highlighted item>, <item1>, <item2>,< item …>, < itemN>.
Each time there is a change in the menu on the mobile, the unsolicited result code is transmitted to the external device.
<menu id>: integer type; this is the unique identifier of the menu (more than one menu can have the same name, and it is therefore necessary to have a unique identifier).
<menu name>: text string
<highlighted item>: integer type; this is a number indicating which of the menu items is highlighted. The menu items are numbered from 1 to N. The value 0 indicates that no item is highlighted.
<item> consists of the following:
<item> = <menu item name> ,<menu item type>,<menu item value>
<menu item name>: text string
<menu item type> : 0 normal item (in plain text)
1 radiobutton
2 checkbox
<menuitem value> : 0 unticked
1 ticked
NOTE 1: The <menu item value> is only relevant when the <menu item type> is radio button or checkbox.
NOTE 2: Menus can be displayed as a list of items or as a set of icons on the mobile. However, the logical representation will remain the same as defined in the present sub-clauses.
EXAMPLE 1: "Main menu", "Phone book", "text", "", "Messaging", "text", "", etc
EXAMPLE 2: "Ask to save", "On", "radio", "unselected", "Off", "radio", "selected"
Defined values
<n> : 0 Turn off menu notification.
1 Turn on menu notification.
Result codes
+CMEN:<menu id>, <menu name>, <highlighted item>, <item1>, <item2>,< item …>,< itemN>
+CMEN ERROR: <err >
Read Syntax
+CMEN?
Test Syntax
+CMEN=?
5.4.2 Navigating on the external device
Syntax
+ CNMEN =<menu id>,<operation>
Description
The external device provides the communication device with the user interactions when navigating in menus.
Defined values
<menu id> : integer type; this is the unique identifier of the menu (more than one menu can have the same name, and it is therefore necessary to have a unique identifier).
<operation>: 0 back to previous menu (if any).
1 highlight next menu item.
2 highlight previous menu item.
1 Select/change status of current menu item (e.g. select current menu item or tick check box or radio button if unticked).
Result codes
+ CNMEN: OK
+ CNMEN ERROR: <error code>
Read Syntax
Test Syntax
+ CNMEN =?
5.5 Screen
For visually impaired people, it would be very useful if a copy of the screen can be shown in a larger size on the external device. Also, if would be useful if the contents of the screen as well as the screen dump can be rotated.