Broadcasts NVRAM status change to the plugins.

Cancels a command handling request. Calling this API in editor mode also causes ATEXT to reset the information about the plugin currently handling byte-by-byte data. This causes the next command to be handled in normal mode.

Cancels ECOM plugin uninstall/install/version report receiving

Cancels a pending receiving request.

Establishes a session with server and connect to corresponding extension plugins specified by parameter TATExtensionInterface.

Gets the remaining reply of a previous handled command.

Gets the next special command RSS file entry. These commands are commands with a matching start but with any ending sequence. Command "ATD*99***1#" is one of these and the number of these commands should be kept minimal.

Handles a command. This API supports two modes: Normal mode (!EReplyTypeEditor) for normal use cases Editor mode (EReplyTypeEditor) for special AT commands with text mode

Notes for parameters below: (1) Command to be handled is used in normal mode only. Editor mode is entered when the first EReplyTypeEditor reply is received (5). Editor mode is ended when the first !EReplyTypeEditor reply is received (5). (2) Data received is character set independent; this API is called byte-by-byte in editor mode. (3) The reply string is not used in editor mode's text input. Only editor mode's start condition (prompt) and end condition (!EReplyTypeEditor) handle the possibly existing reply string. (4) The remaining reply length setting is not used in editor mode's text input. It is only used in editor mode's start condition (prompt) and end condition (!EReplyTypeEditor) (5) Normal mode: Other than EReplyTypeEditor reply. Editor mode: Started with EReplyTypeEditor, continued with EReplyTypeEditor, Ended with !EReplyTypeEditor Note: the first reply with EReplyTypeEditor is the "prompt". Subsequent replies with EReplyTypeEditor are ignored.

Note: The editor mode supported by this API should only be used for commands not requiring support for signals. These commands include cases such as DCD signal required by command AT+CMGS.

Marks URC handling ownership.

Number of plugins

Receives ECOM plugin uninstall/install/version reports

Receives unsolicited result code from extension plugins.

Reports change to a value of a character

Reports about external handle command error condition. This is for cases when for example DUN decided the reply contained an error condition but the plugin is still handling the command internally. Example: "AT+TEST;+TEST2" was given in command line; "AT+TEST" returns non-EReplyTypeError condition and "AT+TEST2" returns EReplyTypeError. As the plugin(s) returning the non-EReplyTypeError may still have some ongoing operation then these plugins are notified about the external EReplyTypeError in command line processing. It is to be noted that HandleCommandCancel() is not sufficient to stop the processing as the command handling has already finished.

Reports about abort condition in command handling. This is for cases when for example DUN decided an abort condition was received from DTE (ITU-T V.250 5.6.1). This API is for notifying the plugin that abort was requested. However the plugin currently handling the command may ignore the request if it doesn't support abort for the command or it may return the changed condition with HandleCommandCompleted()

Reporter for reporting when client side has updated its internal information after ReceiveEcomPluginChange()

Reports change to quiet mode. The quiet mode is off by default.

Reports change to verbose mode. The verbose mode is on by default.

Synchronously closes the session Optional: client can do either Close() or SynchronousClose()+Close()

Connected interface