Política estatal y programas de incentivo a la producción

sending state intermediate state receiving state 1/4 2/4 3/4 4/4 server-bound message client-bound message Sending info intermediate info receiving info

waiting-for-response state Figure 3 – Behaviour during submit and receive

WIB shall implement a wait-for-response behaviour. The purpose of the wait-for- response behaviour is to prevent the user from using the menus to start executing local scripts while a script is expected to be received from the network. To describe this functionality two states are defined for the WIB execution: normal execution state and wait-for-response state. The wait-for-response state is entered either as part of the default behaviour or as part of a forced behaviour, see below. When WIB is in the wait-for-response-state it shall block further execution of scripts initiated through menu selections by the user. WIB shall instead issue a PLAY TONE proactive SIM command to alert the user that menu selection is not allowed. Optionally, an Alpha Identifier and/or icon can be posted as a parameter

1.3 - Im ple m en tation Sp ecification e nt nu mber: M P M0 2:0 111 R e vision :P A 29

to the PLAY TONE proactive SIM command, resulting in that the Alpha

Identifier and/or icon is displayed on the ME when the tone is played. WIB shall after a number of user retries, specified by the persevere-counter in

EFWIBConfiguration, exit the wait-for-response state and again allow menu selections.

The persevere counter in EFWIBConfiguration indicates how many times the menu

selection is blocked before WIB allows the execution of the associated script. If the persevere counter is '0' the function is disabled, if '1', WIB will block one menu selection but allow the second attempt et cetera.

If alpha identifier and/or icon are present in the EFText, they are passed along as

parameters to the PLAY TONE proactive SIM command. 7.9.1 Default behavior

When a server bound message is submitted to the network due to the execution of a Submit or Submit Extended WIB command and the TAR to be used is of type Pull then WIB shall enter a wait-for-response-state.

The wait-for-response-state is exited when the next client-bound message is received from the network and on the same TAR on which the outgoing message was sent.

The wait-for-response-state shall not be entered when submit WIB command is to be executed on a TAR defined as being of type Push or Administration in EFTAR.

When executing event-triggered scripts, wait-for-response state shall not be entered. If a script is received on a Push TAR and contains a Set Return TAR value WIB command that sets the TAR to a Pull TAR, the wait-for-response state shall be entered since the next Submit is executed on the Pull TAR. 7.9.2 Forced Behaviour

The Submit Extended WIB command contains two attributes to override the default behaviour. It allows setting of the wait-for-response behaviour regardless of TAR type. The WIB command contains a "force" flag and an "action" flag. The "force" flag is indicating if the "action" flag is valid or not. The "action" flag indicates whether WIB shall enter wait-for-response-state or not. The behaviour of the Submit Extended WIB command is specified in 5.1.11.

7.9.3 Default Progress Information

The default progress information consists of two parts, called the intermediate- info and the receiving-info, each part having its own alpha identifier and/or icon configured in EFText. The default progress information is shown when WIB is in a

- Im ple m en tation Sp ecification e nt nu mber: M P M0 2:0 111 R e vision :P A 29

the respective alpha identifiers or icons. If default progress information is activated, WIB shall display the progress of receiving 03.40 messages.. The intermediate-info is displayed as soon as the WIB has entered the wait-for- response-state after the submit WIB command and is displayed until the next incoming client-bound message is received.

If the incoming client-bound message consists of several segments, WIB shall display the receiving-info. When receiving concatenated messages, WIB shall begin to display the receiving-info when receiving the segment containing the sequence number with the value 1. The receiving-info is thereafter updated for each new received segment.

The alpha identifier for receiving-info may contain the escape characters %C, %T and %P where C is the order of the current short message being received, T is the total number of short messages expected and P is the percentage of messages received. Only the integer part of the percentage shall be given. WIB shall replace the occurrences of these escape sequences with its current values before

displaying.

For example if the alpha identifier for receiving-info contains the text

"Receiving…(%C/%T)" then the resulting screen display shall be "Receiving… (1/3)" when the first message of three has been received. If the Alpha Identifier contains the text "Receiving %P%%", the resulting display shall be "Receiving 33%" after reception of the first message out of three."

To be able to use the actual '%' in its original form it must be preceded with an extra '%', that is "%%".

The display of the default progress information may be overridden by the Submit Extended WIB command. The alpha identifiers and/or icons for intermediate-info or receiving-info supplied in the Submit Extended WIB command replace their counterparts in the default progress information, or the attribute settings of the Submit Extended WIB command disable completely the use of the default progress information.

The display mechanism used for showing progress information shall not violate the ability to receive new incoming messages. The display mechanism shall not require any user action.