4 Procedures

02.303GPPMan-machine Interface (MMI) of the Mobile Station (MS)TS

4.1 General

This clause defines the MMI of the service access procedures, and supplementary service control procedures. These procedures are defined as logical procedures and in general no mandatory methods are specified. In order to make the descriptions continuous and clear requirements in GSM 02.07 [3], 02.11 [4], 02.17 [5] and 02.40 [7] have been included or are referenced. The mapping between the MMI procedures and the call control entity is specified in GSM 04.08 [16].

4.2 MS access

The MS access procedure is comprised of the initial actions the user has to take before calls can be established or received. This procedure includes e.g. insertion of subscriber-card and entering the PIN-code.

As there exist different types of MS and as requirements in other GSM specifications allow different options the MS access procedure may differ between Mobile Stations. The method for describing the MS access procedures is by using a Mealy-graph, see annex A.

The graph shows the MS access for simple MS e.g. hand-held and they may be different for more complex stations. It should also be noted that the exact sequences of events are not described, these may be chosen by the manufacturers. Nevertheless, the related requirements in the other GSM specifications referenced in subclause 4.1 are applicable.

4.3 Definition of functions

The following functions are applicable and mandatory for the logical procedures for Mobile originated and terminated calls and for the control of Supplementary Services:

ACCEPT: Acceptance of a mobile terminated call.

SELECT: Entry of information.

SEND: Transmission of the entered information to the network.

INDICATION: Requirements in GSM 02.40 [7] are applicable. Other indications may be given in addition throughout the procedure.

END: Termination of or disconnection from the call. The execution of the END-function may be caused by either party involved in the call by e.g. termination, loss of coverage, invalidation of payment.

4.4 Call Control

4.4.1 General

Voice calls to and from a Mobile Station shall be controlled in accordance with the procedures described below. "Data calls" are expected to be controlled in a similar way but are not here specified.

4.4.2 Voice calls

The voice call is either a normal telephony call or an emergency call.

4.4.2.1 Mobile originated calls

The following sequence of functions shall be used:

SELECT: Entry of called address information.

SEND: Transmission of the called address.

INDICATION: See subclause 4.3.

END: Termination of the call.

4.4.2.2 Emergency calls

With Mobile Stations supporting Telephony, it shall be possible to place an emergency call by entering 112 with GSM 900 and GSM 1800, 911 for GSM 1900 in the U.S.A. and Canada, or 08 for GSM 1900 in Mexico, followed by SEND in the manner specified in subclause 4.4.2.1. When a dual or multi-band terminal supporting GSM 1900 and another band is registered on a GSM 900, GSM 1800 or GSM 1900 network, it shall support the initiation of an emergency call by entry of 112, 911 or 08 unless a data call is requested. It may also be possible for a user to enter a preferred emergency MMI code of up to six digits (such as 999) followed by SEND to invoke an emergency call. In this latter case, the preferred code shall be stored in the SIM and the ME recognizes any dialled instance of this code to set up the emergency call. Additional means to place such a call are also allowed, e.g. provision of a dedicated button.

The MS must support the initiation of an emergency call to "112", “911” for GSM 1900 in the U.S.A. and Canada, or “08” for GSM 1900 in Mexico, without a SIM present in the MS, regardless of the call being accepted or not by the network (national option to require IMSI).

NOTE: In addition to the above procedure, calls to national emergency services may be made in the way standard for the country of the serving PLMN. However, with the exception of code "112", “911” for GSM 1900 for U.S.A. and Canada, or “08” for GSM 1900 for Mexico, these are not treated within the PLMN as "Teleservice Emergency call" unless the ME recognizes the code as an emergency code as described above, and would require a valid IMSI.

4.4.2.3 Mobile terminated calls

The following sequence of functions shall be used:

INDICATION: Alert to the user that she is being called.

ACCEPT: Acceptance of the incoming call by the user.

INDICATION: See subclause 4.3.

END: Termination of the call.

User Determined User Busy (UDUB): If, on being alerted by an incoming call, the called user enters "0 SEND", this shall set UDUB for that call, which shall either invoke call forwarding on busy, if active and operative, or else present BUSY to the calling party.

4.5 Supplementary Services Control

4.5.1 General

The supplementary services shall be controlled in accordance with the procedures described below. All Mobile Stations with MMI shall be able to be controlled in this way, to minimize the confusion of users using different types of Mobile Station (quite likely, due to the use of the SIM IC card) and to permit the introduction by a PLMN operator of new supplementary services, not defined at the time of the design of a Mobile Station. These procedures are based on those recommended by CEPT/SF and CCITT Recommendation E.131.

The specified MMI shall be supported by the L3 signalling between the MS and the MSC, see GSM 04.80 [17].

In addition to these specified MMI procedures the MS may be equipped with additional enhanced MMI procedures (e.g. dedicated keys, menu procedures…), left to the discretion of the manufacturer. These procedures shall also be converted in accordance with GSM 04.80 [17].

4.5.2 Structure of the MMI

The following sequence of functions shall be used for the control of Supplementary Services:

SELECT: Entry of the procedure information (may be a digit or a sequence of characters).

SEND: Transmission of the information to the network.

INDICATION: See subclause 4.3.

The MS shall support the MMI procedure specified as:

Activation : *SC*SI#

Deactivation : #SC*SI#

Interrogation : *#SC*SI#

Registration : *SC*SI# and **SC*SI#

Erasure : ##SC*SI#

This structure consists of the following parts:

– Service Code, SC( (2 or 3 digits);

– Supplementary Information, SI (variable length).

The procedure always starts with *, #, **, ## or *# and is finished by #. Each part within the procedure is separated by *.

The service code uniquely specifies the Supplementary Service, either as a defined GSM Supplementary Service or as a spare service code. All spare service codes shall be reserved for future use.

The MS shall determine from the context whether, an entry of a single *, activation or registration was intended.

For example, a call forwarding request with a single * would be interpreted as registration if containing a forwarded-to number, or an activation if not.

The supplementary information (SI) may comprise e.g. a PIN code or Directory Number. Where a particular service request does not require any SI, "*SI" is not entered, e.g. Activation becomes *SC#SEND. Where further supplementary information is required this is again entered as *SI, e.g. *SC*SIA*SIB#SEND. SIB may be used to specify the tele or bearer service expressed as a Basic Service Group to which this supplementary service request applies, SIC may be used to specify the value of the "No Reply Condition Timer".

Use of SIA, SIB, SIC for a particular procedure is optional. The procedure to be adopted where these are not all used is as follows:

*SI# shall be entered in any of the following formats:

* SIA * SIB * SIC #

* SIA * SIB #

* SIA * * SIC #

* SIA #

* * SIb * SIC #

* * SIB #

* * * SIC #

#

The denotation of the Supplementary Information and the order of entry are specified in annex B. Supplementary Information Codes for the Teleservices and Bearer Services are given in annex C.

The following procedures shall be used for application of supplementary services to the call set-up procedure:

*SCn*SI#DN SEND;

where SC is the service code defined in annex B and *SI is an optional field which may be applicable to service SC. The "n" is a single digit used to indicate the numbering plan, profile, priority, etc. according to the service being applied. For simplicity of presentation, the leading * is shown on the assumption that the action is to activate (switch on) the required service. However, for a deactivation (or switch off), this would become:

#SCn*SI#DN SEND;

It is assumed that the *# (interrogation) will not apply to call set-up.

Where more than one supplementary service is applicable to the call set-up, these shall be concatenated with any applicable supplementary information immediately following the applicable service code.

For example, if SCn and SI refer to one applicable supplementary service and scn and si to another, then the generic procedure becomes:

*SCn*SI#scn*si#DN SEND.

NOTE: The order of entry of SC and sc is a user option, provided that any supplementary information follows immediately after the relevant SC.

Where SI is not applicable according to the definition of the supplementary service, then *SI is omitted. Where its use is optional, but not selected for a particular call set-up, it may be omitted or entered as an extra * if this is necessary to avoid ambiguity of interpretation.

NOTE: By using the # as a separator, most cases are expected to be unambiguous.

4.5.3 Handling of supplementary services

4.5.3.1 Handling of defined GSM supplementary services

The MMI procedure for the defined GSM Supplementary Services shall be converted to the mobile radio interface Layer 3, as specified in GSM 04.80 [17]. An appropriate message should be given/displayed to the user in accordance with the "return result/error" from the network.

The service codes for the defined GSM Supplementary Services are given in annex B.

4.5.3.2 Handling of not-implemented supplementary services

The MS shall act in accordance with figure 4.5.3.2 when digits are entered to the MS to determine whether to interpret these as call set-up requests or supplementary service control procedures etc.. This may involve a mechanism, referred to as Unstructured SS Data, which allows the support of GSM SS services which are not implemented by means of the GSM specified functional signalling. See also GSM 02.90 [10].

Figure 4.5.3.2

The following definitions are applicable to the interpretation of figure 4.5.3.2:

1) In a call:

A MS is "in a call" from the time that signalling related to the establishment or attempted establishment of a MO or MT call commences and before the call or call attempt ends, and (if applicable) the ME has stopped generating tones related to this call to the user.

2) MS manufacturer defined procedure:

The term "MS manufacturer defined procedure" shall not include the following two cases:

(i) input which can be interpreted as being of the following form, whether or not in a call:

CX [string]# followed by SEND;

where

string is any combination of numeric digits, *, #;

and

C comprises 1, 2 or 3 digits from the set (*,#);

and

X comprises 1, 2 or 3 numeric digits or the fourth numeric digit is non-zero;

(ii) input of the following form in a call (as defined above):

"Entry of 1 or 2 characters defined in the GSM 03.38 [15] Default Alphabet followed by SEND".

3) #-string:

Input of the form.

"Entry of any characters defined in the GSM 03.38 [15] Default Alphabet (up to the maximum defined in GSM 04.80 [17]), followed by #SEND".

4) Short string:

"Entry of 1 or 2 characters defined in the GSM 03.38 [15] Default Alphabet followed by SEND".

5) Call setup string:

MMI input in accordance with the call set-up procedures as defined in GSM 04.08 [16] and terminated by SEND.

If the network has initiated an operation which explicitly (in the signalling) requires a response from the user, then the user shall be able to enter a response in the form of any string of characters followed by SEND. The mobile shall also provide an MMI command to terminate the dialogue with a NULL response.

The use of END shall release all calls in progress (see also subclause 4.5.5.2), terminate any outstanding unstructured SS operations, and release any connection used for unstructured SS operations.

4.5.4. Registration of new password

The following procedure permits the user to change the password relating to use of Supplementary Services. The only control procedure supported is Registration of a new password, which replaces any previous password for the same service. The password may not be Erased or Interrogated.

Procedure:

* 03 * ZZ * OLD_PASSWORD * NEW_PASSWORD * NEW_PASSWORD #

The MS shall also support the alternative procedure:

** 03 * ZZ * OLD_PASSWORD * NEW_PASSWORD * NEW_PASSWORD #

where, for Barring Services, ZZ = 330;

for a common password for all appropriate services, delete the ZZ, entering:

* 03 ** OLD_PASSWORD * NEW_PASSWORD * NEW_PASSWORD #

The MS shall also support the alternative procedure:

** 03 ** OLD_PASSWORD * NEW_PASSWORD * NEW_PASSWORD #

the MS will then indicate to the user whether the new password request has been successful or not. If the new password request is rejected (e.g. due to entry of incorrect old password) the old password remains unchanged, until it is successfully changed by correctly repeating the procedure. Refer to GSM 02.04 [2] regarding repeated entry of incorrect password.

NOTE: The procedures shall be followed by SEND as described in subclause 4.5.2.

4.5.5 Handling of supplementary services within a call

4.5.5.1 Call Deflection, Call Waiting, Call Hold, MultiParty Services, Explicit Call Transfer and Completion of Calls to Busy Subscriber general principles

During a call, the following general procedures shall be available, where applicable, for the subscriber to control the operation of

– Call Deflection

– Call Waiting

– Call Hold

– MultiParty Services

– Explicit Call Transfer

– $(CCBS)$: Completion of Calls to Busy Subscriber

including their interactions. It should be noted that not all control procedures described in GSM 02.72, 02.83, 02.84, 02.91, and 02.93 are specified in this subclause.

Procedures:

Entering 0 followed by SEND – Releases all held calls or sets User Determined User Busy (UDUB) for a waiting call.

Entering 1 followed by SEND – Releases all active calls (if any exist) and accepts the other (held or waiting) call.

Entering 1X followed by SEND – Releases a specific active call X.

Entering 2 followed by SEND – Places all active calls (if any exist) on hold and accepts the other (held or waiting) call.

Entering 2X followed by SEND – Places all active calls on hold except call X with which communication shall be supported.

Entering 3 followed by SEND – Adds a held call to the conversation.

Entering 4 followed by SEND – Connects the two calls and disconnects the subscriber from both calls (ECT).

Entering 4 * "Directory Number" – Redirect an incoming or a waiting call to the specified followed by SEND directory number.

Entering 5 followed by SEND – $(CCBS)$: Activates the Completion of Calls to Busy Subscriber Request.

Entering "Directory Number" – Places all active calls (if any exist) on hold and sets up a followed by SEND new call to the specified Directory Number.

Entering END – Releases the subscriber from all calls (except a possible waiting call).

"X" is the numbering (starting with 1) of the call given by the sequence of setting up or receiving the calls (active, held or waiting) as seen by the served subscriber. Calls hold their number until they are released. New calls take the lowest available number.

Where both a held and a waiting call exist, the above procedures shall apply to the waiting call (i.e. not to the held call) in conflicting situation.

4.5.5.2 Call Waiting (CW)

During a call, provided this service is active for the called party, if a second call attempts to make contact, a "call waiting" indication will be presented to the called party.

To clear the current call and accept the waiting call, enter 1 followed by SEND, within the time out period. Alternatively, either party in the existing, active, call may release that call. The call waiting indication then becomes an "alert", and the call may be accepted as a normal call within the time-out period.

To hold the current call and accept the waiting call, enter 2 followed by SEND, within the time out period.

To ignore the waiting call, take no action.

To set User Determined User Busy (UDUB) for the waiting call, enter 0 followed by SEND, within the time out period.

To redirect the waiting call to another destination, enter 4 * "Directory Number" followed by SEND, within the time out period.

4.5.5.3 Call hold

During a call, the initial call may be held while another call is made by entering the second directory number followed by SEND.

To shuttle between the two calls enter 2 followed by SEND irrespective of whether the second call was acquired using the Call Hold or acceptance of Call Waiting procedures.

If no waiting call exists, by entering 0 followed by SEND the held call is cleared.

To clear an active call and return to the held call enter 1 followed by SEND. This is only possible if no waiting call exists.

4.5.5.4 MultiParty

Having established calls to these two parties with one call active and the other on hold, enter 3 followed by SEND for a multiparty conversation.

To add another remote party, the same procedure applies. Another call is established and either this call or the existing multiparty call is placed on hold. Entering 3 followed by SEND brings all these parties together in an enlarged multiparty call.

To choose one party for a private communication, putting the rest of the multiparty on hold, enter 2X followed by SEND, where X defines the call with which communication shall be supported.

To return to the multiparty, with the previously active call placed on hold, enter 2 followed by SEND.

To release a specific party enter 1X followed by SEND, where X is defined as above.

If the served mobile subscriber enters END, all calls including the multiparty are released. The multiparty is terminated.

4.5.5.5 Explicit Call Transfer

Having established calls to these two parties with one call active and the other on hold, enter 4 followed by SEND to transfer the calls.

If a subscriber has one active, one held and one waiting call, and by entering 4 SEND the active and held call are connected, after the successful completion of the transfer, the served subscriber shall be offered the normal notification that there is a new waiting call, as for a normal terminating call.

4.5.5.6 Special case

Provided both Call Hold and Call Waiting is active, it is possible to have one active and one held call and then a third call attempting to make contact. In this case, to clear the active call and accepting the waiting call (the held call not affected) enter 1 followed by SEND (If entering 2 followed by SEND the call state shall not be affected).

Alternatively, either party in the active call may release that call. The held call will remain held. Within the time-out period the waiting call may then be accepted by entering 2 followed by SEND. It shall also be allowed to accept the waiting call by entering 1 followed by SEND.

As and additional alternative, the (controlling) subscriber B may enter END, in which case the active and the held calls are released. The call waiting indication then becomes an "alert" and the previously waiting call may be accepted as a normal call within the time-out period.

4.5.5.7 Call Deflection

If informed about an incoming call this call may be redirected to an another destination by entering 4 * "Directory Number" followed by SEND.

4.5.5.8 Completion of calls to busy subscribers – $(CCBS)$

In a situation where a calling party A encounters busy of congestion on the B side, the network may offer the possibility to apply the CCBS supplementary service. If subscriber A, after being notified that CCBS is possible and during the period where the retention timer is running (minimum 15 seconds), enters 5 followed by SEND, this shall be interpreted as CCBS activation. Entering of 5 SEND by subscriber A in any other situation as described above shall not be interpreted as CCBS activation.

4.5.6 Other handling of supplementary services

4.5.6.1 Multiple Subscriber Profile – $(MSP)$

4.5.6.1.1 Registering an alternative profile

An alternative profile is registered by entering the profile ID of the new profile, as illustrated:

* 59n # SEND

Where n is the identity of the profile desired.

An indication is given to the user showing whether this procedure was successful.

The ID of the registered profile and other provisioned profiles may be determined by interrogation on entering *#59# SEND

The profile so registered shall be used for all further MS originated activities and CISS operations unless another profile is selected, or an alternative profile is registered.

4.5.6.1.2 Selecting an alternative profile on a per call basis

An alternative profile to the registered profile is selected by entering the profile ID of the new profile along with the desired Directory Number, as illustrated:

DN *59n# SEND

Where n is the identity of the profile desired

Continued processing of the call shall implicitly indicate that the selection was successful, there shall be no explicit indication given to the user concerning successful execution this selection procedure.

It is assumed that *# (i.e. interrogation) will not apply to call set-up.

4.6 SIM interfaces

4.6.1 Entry of PIN and PIN2

After insertion of the IC card while the MS is switched on, or when the MS is switched on while the IC card is inserted, or when the MS is switched on in the case of a plug-in SIM, an indication is given to the user that the PIN must be entered, unless the PIN is not applicable.

If the user wishes to perform a function protected by PIN2, an indication shall be given to the user that PIN2 must be entered.

The PIN or PIN2 being entered is not revealed in any way. The PIN or PIN2 check is performed by entering the # function.

4.6.2 Change of PIN or PIN2

The following procedure permits the user to change the PIN or PIN2 in the SIM:

PIN: **04*OLD_PIN*NEW_PIN*NEW_PIN#

PIN2: **042*OLD-PIN2*NEW_PIN2*NEW_PIN2#

Note that the SEND function is not used in these procedures.

An indication is given to the user showing whether this procedure was successful.

4.6.3 Unblocking of PIN or PIN2

The following procedure permits the user to unblock the PIN or PIN2:

PIN: **05*PIN_UNBLOCKING_KEY*NEW_PIN*NEW_PIN#

PIN2: **052*PIN2_UNBLOCKING_KEY*NEW_PIN2*NEW_PIN2#

Note that the SEND function is not used in these procedures.

The new PIN or PIN2 must be entered whether or not it is intended to change the PIN or PIN2. An indication is given to the user showing whether this procedure was successful.

4.6.4 Reading the abbreviated dialling code

An abbreviated dialling code shall be able to be read using the following procedure:

N(N)(N)#

Alternative additional procedures are also permitted.

4.6.5 Status information – return codes

The SIM gives status information, as responses to instructions, in two-byte codes (see GSM 11.11 [21] clause "Status Conditions Returned by the Card"). Some of the possible return codes are deeply related to the user’s actions and should therefore be indicated to her.

It is mandatory to give the user the appropriate indication (respectively) when the following codes appear:

code description;

92 40 – Memory Problem (eg. Update impossible);

98 04 – Access conditions not fulfilled (eg. secret code verify rejected);

98 40 – Unsuccessful CHV verification, no attempt left (eg. Secret code locked);

6F XX – Technical problem with no diagnostic given.

The status information indication can be a dedicated lamp, text-string or others, as long as it is unambiguously made available to the user via the MMI.

As regards all other codes, it is left to the manufacturers’ discretion whether and how the user shall be informed.

4.7 Presentation of IMEI

The following procedure shall instruct the ME to display its IMEI:

*#06#

The procedure shall be accepted and performed with and without an inserted SIM. The ME shall then display the 14 digits of the IMEI (not including the spare digit), the Check Digit and optionally the Software Version Number as defined in GSM 02.16 [6] (as a single string, in that order).