4 - Priority scale: High, Medium and Low
6 - Complexity scale: C1, C2, C4 and C8. The complexity scale is exponential,
7 with complexity 1 being the lowest complexity. Complexity is a function
8 of both task 'complexity' and task 'scope'.
10 The general rule of thumb is that a complexity 1 task should take 1-2 weeks
11 for a person very familiar with oFono codebase. Higher complexity tasks
12 require more time and have higher uncertainty.
14 Higher complexity tasks should be refined into several lower complexity tasks
15 once the task is better understood.
21 - Add support for Enhanced SMS (EMS) from 3GPP 23.040. These SMS messages
22 support a richer set of formatting elements, including bold/italic and
23 font size selection. Embedding images and sounds into the SMS is also
24 supported. This task should add support for receiving such SMS messages.
26 Proposed solution is to convert such messages to HTML and embed image /
27 sound data as embedded MIME in the generated HTML stream. The EMS messages
28 will have to be detected (by the presence of particular tags in the SMS)
29 and signaled separately from simple SMS messages.
34 - See / Cancel pending SMS messages over DBus. When oFono sends SMS messages
35 the method call is only returned when the message has been submitted to the
36 network. Instead we should return an object path and allow cancellation of
41 Owner: Yang Gu <yang.gu@intel.com>
43 - Asynchronously acknowledge SMS DELIVER messages sent by the SMS driver
44 to core using ofono_sms_deliver_notify(). This may require the struct
45 ofono_sms_driver to be extended with one more function pointer like:
46 void (*deliver_ack)(unsigned char *pdu, int len, cb_t cb, void *data)
47 because currently messages are automatically acknowledged by either the
48 modem (this is the case of some AT modems) or the driver right after
49 ofono_sms_deliver_notify() and a failure to deliver at an upper level is
50 ignored. The PDU can be an RP-ACK or RP-ERROR message with optional
51 TP-User-Content element, for example if returned from USIM Data Download.
59 - SIM Call History plugin. New UICCs support four new SIM elementary files
60 for storing call history information on the SIM: EFici, EFict, EFoci, EFoct.
61 A plugin should be developed for oFono that will write to these files.
66 - Add support for SIM 'ready' notifications from the driver to the core. Most
67 modem manufacturers initialize the SIM (e.g. cache SIM file system, STK
68 initialization, etc) internally before allowing the telephony stack to
69 access these portions. When the PIN is locked, this can lead to oFono being
70 too fast for the modem and asking it for things before the firmware is ready.
72 The proposal is to introduce a new sim function:
73 void ofono_sim_ready_notify(struct ofono_sim *sim);
75 When oFono determines the SIM PIN is READY, it checks whether
76 ofono_sim_ready_notify has been called. If it hasn't, then it stalls the
77 initialization procedure (and calling post_sim) until
78 ofono_sim_ready_notify is called.
82 Owner: Pekka Pessi <pekka.pessi@nokia.com>
84 - Add support for CPHS Customer Service Profile (CSP). This task adds support
85 for reading the EFcsp file and in particular, interpreting the PLMN mode bit
86 within the 'Value Added Services' service group.
88 Based on the PLMN mode value, manual network selection needs to either be
89 enabled or disabled in the netreg atom. Also to accommodate this, there
90 probably needs to be a new 'forced' mode to indicate that manual network
91 selection is disabled.
95 Owner: Aki Niemi <aki.niemi@nokia.com>
97 - Support SIM authentication: SIM and AKA suites.
101 Owner: Pekka Pessi <pekka.pessi@nokia.com>
103 - Support SIM authentication: GBA_U suite.
110 ISIM is the SIM application for IP Multimedia Subsystem, specified in
111 3GPP TS 31.103. The UICCs can support multiple ISIMs for different IMS
121 - Support HFP AG emulator. We should provide a new HFP_AG_EMULATOR atom type
122 that will implement the Bluetooth HFP AG profile. Voicecall atom, netreg
123 atoms can register command handlers for this atom appropriately.
127 Owner: Frédéric Danis <frederic.danis@linux.intel.com>
129 - Support extensions to HFP AG emulator. Some carkits support additional
130 AT command extensions to the Bluetooth HFP AG standard. Refer to CE4A
131 white paper: "AT-commands for Automotive Premium Phone Integration".
132 Plugins can register additional command handlers appropriately to handle
137 Depends: HFP AG emulator
138 Owner: Frédéric Dalleau <frederic.dalleau@linux.intel.com>
140 - Support HSP AG. Similar to HFP AG emulator but implements the much reduced
141 Bluetooth HSP AG profile.
146 - Support DUN emulator. Implement the Bluetooth DUN profile with only mandatory
147 AT command support. Implement USB DUN as well.
151 Owner: Gustavo F Padovan <padovan@profusion.mobi>
153 Depends: PPP Server mode
155 - Support Bluetooth SPP profile.
164 - Flight Mode support. Add an 'Online' property to the Modem interface that
165 will control the online state of the modem. When Online state is True all
166 atoms are available. When Online state is False, all network related items
167 are removed (e.g. CallSettings) or enter into reduced functionality set
168 where only the SIM is available (e.g. DataConnectionManager, SimManager, etc)
172 Owner: Pekka Pessi <pekka.pessi@nokia.com>
178 - Add support for IPv6 GPRS contexts.
182 Owner: Mika Liljeberg <mika.liljeberg@nokia.com>
188 - PPP Server support. Extend GAtPPP to support PPP Server role, similarly to
189 how existing GSM modems support PPP GPRS contexts.
194 - IPv6 CP support. To support IPv6 based GPRS contexts via PPP, GAtPPP
195 needs to be updated to support IPv6CP from RFC 2472.
200 - ACFC support. Extend GAtPPP to support packets with Address & Control Field
201 Compression enabled. Refer to RFC 1662 for details.
206 - PFC support. Extend GAtPPP to support packets with Protocol field
207 compression enabled. Refer to RFC 1661 for details.
213 - Neighbor Cell Info. Add dedicated atom, D-Bus API and atom driver(s) for
214 Neighbor Cell information.
216 This feature is not discussed in 27.007, thus manufacturer specific commands
221 Owner: Antti Paila <antti.paila@nokia.com>
224 Supplementary Services
225 ======================
227 - Closed User Group (CUG) support.
232 - Call Completion to Busy Subscriber (CCBS) support
234 This feature is not discussed in 27.007, thus manufacturer specific commands
240 - User to User Signaling (UUS) support
245 - Multiple Subscriber Profile (MSP) support
250 - CPHS Support. This includes ALS and CPHS specific elementary files.
255 - Call forwarding state handling change
257 At the moment call forwarding states are not always correct. Any active
258 conditional call forwarding should become quiescent while unconditional call
259 forwarding is activate. If call forwarding unconditional is subsequently
260 deactivated, all the quiescent forwardings should become operative again.
261 I.e. No conditional call forwardin string should be returned while
262 unconditional call forwarding is active even if they exist.
264 If there is an successful attempt to activate/deactivate conditional call
265 forwarding while unconditional call forwarding is active the conditional cache
275 - Supplementary service notifications on remote party actions:
276 - call has been put on hold (+CSSU: 2)
277 - call has been retrieved (+CSSU: 3), and
278 - joining call to a multiparty conference (+CSSU: 4)
282 Owner: Pekka Pessi <pekka.pessi@nokia.com>
284 - Dial strings. Include CLIR prefixes and 2nd stage dial strings in the
285 DialString call property. Add dialstring accessor method to C API.
289 Owner: Lucas De Marchi <lucas.demarchi@profusion.mobi>
291 - Provide feedback of sent DTMF tones. Emit SendingTones signal if modem can
292 provide approximate starting and stopping times for DTMF tones. Signal
293 argument contains a string of DTMF tones to be sent, or empty string when
294 all tones has been sent.
298 Owner: Pekka Pessi <pekka.pessi@nokia.com>
300 - Blacklisting. According to 3GPP TS 22.001 annex E, the TE must provide
301 automatic calling repeat call attempt restrictions.
303 There should be a method to manually reset blacklisting.
312 - Support Refresh proactive command. The specification defines 7 types
315 - NAA File Change Notification
316 - NAA Initialization and File Change Notification
317 - NAA Initialization and Full File Change Notification
319 - NAA Application Reset (2G only)
320 - NAA Session Reset (3G only)
322 The 'NAA Initialization' type will be ignored by oFono, it is assumed
323 this is handled by the modem.
325 For 'UICC Reset', 'NAA Application Reset' and 'NAA Session Reset' oFono
326 will first check whether there are any calls or ussd operations active.
327 If there are, the appropriate response will be sent (e.g. busy on call
328 or screen busy terminal response.) Otherwise a positive response will be
329 sent to the driver. In the case of a 'UICC Reset' the driver / modem
330 can interpret this that it is safe to reset the UICC.
332 Alternatively, the driver / modem can notify the core of the SIM removal
333 / SIM insertion events without using the Refresh proactive command. It
334 is up to the driver / modem to perform a warm reset. In particular, 3GPP
335 31.111 mandates that any change to EFimsi is done by using 'UICC Reset',
336 'NAA Application Reset' or 'NAA Session Reset'. Please see 3GPP 31.111
339 Other types will be handled by oFono flushing the EF cache of the files
340 affected (or the entire SIM cache in case of Full File Change Notifications)
341 and re-reading the affected files. Any properties derived from these
342 Elementary Files will be updated and signaled using PropertyChanged.
347 - Support of the BIP (Bearer Independent Protocol) proactive commands.
348 The specification defines several bearer types. For now, only the packet data
349 service bearer is considered.
351 - OPEN CHANNEL: requests the terminal to open a data channel with
352 parameters indicated in the command. A user confirmation may be
353 requested by the SimToolkitAgent.
354 - CLOSE CHANNEL:requests the terminal to close the specified data
356 - RECEIVE DATA:requests the terminal to return to the UICC data
357 received on the specified channel.
358 - SEND DATA:requests the terminal to send on the specified channel data
359 provided by the UICC.
360 - GET CHANNEL STATUS: requests the terminal to return the current
361 status of all available data channels.
365 Owner: Philippe Nunes <philippe.nunes@linux.intel.com>
367 - Support Setup Event List proactive command.
368 To fully support the class 'e', the following events
369 -Data Available event
370 -Channel status event
371 shall be monitored by oFono if part of the current event list.
372 This list is supplied by the last SETUP EVENT LIST command.
376 Owner: Philippe Nunes <philippe.nunes@linux.intel.com>
381 - Modem Emergency mode. Support network registration and online/offline
382 mode during the emergency calls and related network activity (e.g.,
383 network-initiated location request via supplementary service channel).
385 Proposed solution is to introduce a new Emergency boolean property to the
386 Modem D-Bus interface and new functions to modem interface:
388 - ofono_modem_emergency_mode_inc()
389 - ofono_modem_emergency_mode_dec()
390 - ofono_modem_emergency_mode_get()
391 - ofono_modem_add_emergency_mode_watch()
392 - ofono_modem_remove_emergency_mode_watch()
394 When emergency mode is requested, modem is set to online (if needed) and
395 the watchers are notified. There can be multiple parties requesting
396 emergency mode. When all of them have completed the emergency-related
397 operation and called ofono_modem_emergency_mode_dec(), modem is set to
398 offline (if needed) and the watchers are again notified.
403 - Country / Operator specific emergency numbers. Figure out how to support
404 countries / operators with specific mandated emergency numbers which are
405 not part of the standard emergency number list. This needs to be queried
406 by the voicecall atom every time a new SIM is inserted. The list is
407 assumed to be managed by the modem. If no such functionality is available,
408 then the 3GPP mandated behavior is used.
413 - Network updating the emergency number list. Support the list of emergency
414 numbers dynamically updated by the network.
418 Owner: Petteri Tikander <petteri.tikander@ixonos.com>
424 - Bluetooth SAP Client support. The Telit UC864-G devices support Bluetooth
425 SAP client mode. This requires the use of a modem side-channel to read the
426 APDU & CPDU data and send it to the remote phone device over Bluetooth RFCOMM
432 - PolicyKit support. Add support for PolicyKit checking of all oFono D-Bus
438 - Internet Access Provider database. Have oFono automatically configure
439 GPRS contexts based on an internal database. Database format to be decided.
440 If there are multiple matches in the database, then some user intervention
445 Owner: Jukka Saunamäki <jukka.saunamaki@nokia.com>
447 - Add Location Service API for providing basic E911 support.
448 This will be based on the 27.007 defined AT commands using
449 XML for transport of positioning request and responses.
453 Owner: Jarko Poutiainen <jarko.poutiainen@tieto.com>
455 - Add support for main.conf. This task will add support for general
456 as well as per-atom configuration options that are read and parsed
457 at startup from a configuration file under /etc/ofono.
461 Owner: Aki Niemi <aki.niemi@nokia.com>
466 - Add support for Mobile Originated and Mobile Terminated Voice Call over
467 a CDMA network. This includes management of call state and providing
468 appropriate values for the LineIdentification in each case.
472 Owner: Dara Spieker-Doyle <dara.spieker-doyle@nokia.com>
474 - Add support for Three-Way Calling over a CDMA network. Three-Way Calling
475 provides the subscriber with the capability to add a third party to an
476 established two-party call, so that all three parties may communicate in a
479 In CDMA mode, the originating subscriber of a current conversation can
480 request for a third party to be added to a conversation by sending a Flash
481 With Information Message (FWIM) with dialed digits to the network. Upon
482 setting up a two-way conversation with the added party, the originating
483 subscriber can request to establish a three-way conversation by sending
484 another Flash With Information Message. Upon receiving the second Flash With
485 Information Message, the MSC reconnects the original party to the
486 conversation thus completing the setup of a three-way conversation.
488 CDMA Three-Way Calling is described by Figure B-5 in 3GPP2 C.S0005-E Version
494 - Add support for Call Waiting over a CDMA network. Call Waiting (CW) provides
495 notification of an incoming call to an originating subscriber, while the
496 subscriber's call is in the 2-way state. Subsequently, the originating
497 subscriber can either answer or ignore the incoming call. If the originating
498 subscriber answers the second call, it may alternate between the two calls.
500 In CDMA mode, the originating subscriber of a current conversation will
501 receive either a Flash With Information Message or an Alert With Information
502 Message from the network if there is an additional mobile terminated voice
503 call incoming. The originating subscriber can change conversation parties by
504 sending a Flash With Information Message to the network and the MSC will
505 toggle the speech path between the two conversations.
507 CDMA Call Waiting is described by Figure B-6 in 3GPP2 C.S0005-E Version
513 - Support sending DTMF tones over CDMA network.
518 - Support optional network-based Plus Code Dialing for international calls over
519 a CDMA network. An input key, e.g. the "+" key, or a functional equivalent
520 can be used to replace the international access prefix when dialing. When
521 received, transmitted or stored, an international indicator can be included
522 with the address digits although it is the responsibility of the network to
523 ignore the international indicator when attached to a national number. This
524 is described in Section 2.7.1.3.2.4 of 3GPP2 C.S0005-E v2.0 and Section 1.2
525 of 3GPP2 N.S0027 v1.0.
533 - Support CDMA SMS stack in PDU mode. This includes basic support of
534 SMS Point-to-Point Message, SMS Broadcast Message and SMS Acknowledge
535 Message as per 3GPP2 C.S0015-B version 2.0.
540 - Support sending Wireless Messaging Teleservice (WMT) Submit Message and
541 receiving WMT Deliver Message as defined 3GPP2 C.S0015-B version 2.0.
546 - Support Delivery Acknowledgment. oFono allows requesting of CDMA SMS
547 Delivery Acknowledgment via the MessageManager's
548 UseDeliveryAcknowledgement property. If enabled, oFono's CDMA SMS stack
549 will encode the Reply Option subparameter in the Submit message and
550 process incoming SMS Delivery Acknowledgment Message. oFono will notify
551 UI either via DBus or history plugin API.
556 - Support receiving Voice Mail Notification (VMN) Teleservice Deliver
557 message. CDMA network uses VMN Teleservice to deliver the number of
558 messages stored at the Voice Mail System to the CDMA mobile subscriber.
563 - Support sending Wireless Enhanced Messaging Teleservice (WEMT) Submit
564 Message and receiving WEMT Deliver Messsage as defined 3GPP2 C.S0015-B
567 WMT does not support message fragmentation thus can not be used to for
568 long message. WEMT is devised to support long message and Enhanced
569 Messaging Service (EMS). The WEMT SMS message's CHARi field of the
570 subparameter User Data encapsulate GSM-SMS TP-User Data as defined in
571 Section 9.2.3.24 of 3GPP TS 23.040.
576 - Support sending Wireless Application Protocol (WAP) Teleservice Submit
577 Message and receiving WAP Deliver Messsage as defined 3GPP2 C.S0015-B
583 - Support Call-Back Number. The Call-Back Number subparameter indicates
584 the number to be dialed in reply to a received SMS message.
586 In transmit direction, oFono allows setting of Call-Back Number. If the
587 Call Back Number property is set, CDMA SMS stack will encode Call-Back
588 Number subparameter in the Submit Message.
590 In receiving direction, oFono will process the Call-Back Number
591 subparameter in the incoming Deliver Message and notify UI of the
592 Call-Back Number together with the newly received text message.
597 - Support immediately displayed message. oFono CDMA SMS stack will
598 process the optional Message Display Mode subparameter in the incoming
599 SMS message. If Message Display Mode subparameter indicates the
600 message display mode is Immediate Display, oFono will send
601 ImmediateMessage signal, otherwise oFono will send IncomingMessage
611 - Support Commercial Mobile Alert Service (CMAS) over CDMA systems. CMAS
612 over CDMA system is defined in TIA-1149. The CMAS message is carried in
613 the CHARi field of the User Data subparameter of CDMA SMS Broadcast
619 CDMA Network Acquisition
620 ========================
622 - Support reporting of the received signal strength indicator (RSSI)
623 measurement and of the pilot energy ratio (Ec/Io) measurement, for the
624 currently acquired CDMA network.
628 Owner: Dara Spieker-Doyle <dara.spieker-doyle@nokia.com>
630 - Support reporting of the received signal strength indicator (RSSI)
631 measurement and of the signal to interference-plus-noise ratio (SINR)
632 measurement, for the currently acquired 1xEV-DO data network.
637 - Support reporting of the Enhanced Roaming Indicators (ERI) to indicate the
638 current roaming condition of the CDMA mobile device. Each indicator maps to
639 a unique display number within the Standard and Non-Standard service ranges,
640 as described in Section 8 of 3GPP2 C.R1001-C v1.0.
641 These numbers are stored on the device in the (Enhanced) Preferred Roaming
642 List (PRL) and it is the responsibility of the modem to broadcast the
643 relevant indicator for a currently acquired system. Further details of the
644 system acquisition process are described in 3GPP2 C.S0016-B v1.0.
649 - Support reporting of identifiers of the currently acquired CDMA network,
650 including the System Identifier (SID) and the Network Identifier (NID),
651 It is the responsibility of the modem to broadcast the relevant identifiers
652 for a currently acquired system, and these identifiers are provided by the
653 network. This is described in 3GPP2 C.S0005-E v2.0.
658 - Support International Roaming, including support for reporting the Mobile
659 Country Code (MCC) and the Mobile Network Code (MNC) for the currently
660 acquired network. International Roaming is provided via enhancements to the
661 PRL by encoding the MCC and the (two digit only) MNC in existing SID/NID
662 fields, as described in the CDMA Development Group standards Document "IPRL
663 Enhancements for International Roaming - CDG Doc #86". It is the
664 responsibility of the modem to broadcast the values for the currently
670 CDMA Connection Manager
671 =======================
673 - Support Packet Data Service over CDMA (1xRTT and 1xEV-DO) systems. This
674 includes Mobile Originated connection and disconnection features.
679 - Support Network Initiated disconnection of Packet Data Service over CDMA
680 (1xRTT and 1xEV-DO) systems.