Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 22.101  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   4…   5…   10…   11…   13…   21…   24…   26a…   28…   30…   A…   A.19…   B…

 

A (Normative)  Description of optional user equipment featuresp. 82

A.1  Display of called numberp. 82

This feature enables the caller to check before call setup whether the selected number is correct.

A.2  Indication of call progress signalsp. 82

Indications shall be given such as tones, recorded messages or visual display based on signalling information returned from the PLMN. On data calls, this information may be signalled to the DTE.
Call progress indicators are described in TS 22.001.

A.3  Country/PLMN indicationp. 82

The country/PLMN indicator shows in which PLMN the UE is currently registered. This indicator is necessary so that the user knows when "roaming" is taking place and that the choice of PLMN is correct. Both the country and PLMN will be indicated. When more than one visited PLMN is available in a given area such information will be indicated.
The PLMN name is either:
  • Stored in the ME and associated with the MCC+MNC combination received on the broadcast channel;
  • NITZ (see TS 22.042) (in which case it overrides the name stored in the ME);
  • stored in the USIM in text and /or graphic format and associated with the MCC+MNC combination, and optionally the LAI, received on the broadcast channel (in which case it overrides the name stored in the UE and - if present - the NITZ name).
It shall be possible to store on the USIM at least 10 PLMN Identifications (MCC+MNC combination and optionally the LAI) for which the same PLMN name shall be displayed.
The PLMN name stored in the USIM has the highest priority, followed by the PLMN name provided by NITZ. The PLMN name stored in the ME has the lowest priority.
If the PLMN name stored in the USIM is not available in text format and the UE is unable to display the graphic format, the PLMN name provided by NITZ has the highest priority, the PLMN name stored in the ME has the next priority.
For a PLMN name provided by NITZ, operators using non-Latin characters of the local language (such as Chinese, Japanese, Korean, Vietnamese, Arabic, Hindi, etc.) may include the network name in Latin characters in addition to characters of the local language.
For a PLMN name provided by NITZ, the roaming UE should skip displaying non-Latin character(s) if the language of those character(s) does not match the language of the MMI for the UE. If this would lead to no remaining Latin character in the PLMN name, the UE should skip displaying the PLMN name provided by NITZ; the PLMN name stored in the ME has the next priority instead.
Up

A.4  Service Provider Name indicationp. 83

The service provider name is stored in the USIM in text and/or optionally graphic format. It shall be possible to associate at least 10 PLMN Identifications (MCC+MNC combination) with the same SP Name.
When registered on the HPLMN, or one of the PLMN Identifications used for Service Provider Name display:
  1. The SP Name shall be displayed;
  2. Display of the PLMN Name is an operator's option by setting the appropriate fields in the USIM (i.e. the Service Provider name shall be displayed either in parallel to the PLMN Name or instead of the PLMN Name).
When registered on neither the HPLMN, nor one of the PLMN Identifications used for Service Provider Name display:
  1. The PLMN name shall be displayed;
  2. Display of the SP Name is an operator's option by setting the appropriate fields in the USIM.
If the UE is unable to display the full name of the Service Provider the name is cut from the tail end. The storage of Service Provider name and options, and choice of options, shall be under control of the network operator.
Up

A.4a  Core Network Operator Name indication |R6|p. 83

It shall be possible for the UE to display the name of the core network operator the user has selected.

A.5  Keypadp. 83

A physical means of entering numbers, generally, though not necessarily, in accordance with the layout shown in Figure A.1.
See also TS 22.030 (Man-Machine Interface).
Additional keys may provide the means to control the UE (e.g. to initiate and terminate calls).
Reproduction of 3GPP TS 22.101, Fig. A.1:
Up

A.6  Short message indication and acknowledgementp. 84

This feature allows the delivery of short messages to a UE from a service centre. Such messages are submitted to the service centre by a telecommunications network user who can also request information of the status of the message by further interrogation of the service centre. The service centre then transmits the message to an active UE user.
The UE must therefore provide an indication to the user that a message has been received from the service centre and must also send an acknowledgement signal to the PLMN to show that this indication has been activated. The PLMN then returns this acknowledgement to the service centre.
The short message service teleservice is described in specification TS 22.003.
Up

A.7  Short message overflow indicationp. 84

An indication shall be given to the user of the short message service when an incoming message cannot be received due to insufficient available memory.

A.8  International access functionp. 84

Provision is made for a direct, standard method of gaining international access. For this purpose the UE may have a key whose primary or secondary function is marked "+". This is signalled over the radio interface and would have the effect of generating the international access code in the network. It may be used directly when setting up a call, or entered into the memory for abbreviated dialling.
This feature is of benefit since the international access code varies between CEPT countries, which might cause confusion to a user, and prevent the effective use of abbreviated dialling when roaming internationally. Users may still place international calls conventionally, using the appropriate international access code.
Up

A.9  Service Indicator (SI)p. 84

An indication is given to the user that there is adequate signal strength (as far as can be judged from the received signal) to allow a call to be made. Additionally the network should be capable of providing, and the UE may display, an indication of the serving cells' capabilities e.g. GPRS, HSDPA, HSUPA.
If indicated by the registered network, the UE in idle mode may display an indication of one of the radio access technologies provided to the UE in the network on which the UE is registered with the following priority order: E-UTRAN, UTRAN, GERAN.
Displaying the serving cell's capabilities and the access technology are mutually exclusive.
Up

A.10  Dual Tone Multi Frequency (DTMF)p. 84

The UE shall be capable of initiating DTMF in accordance with specifications TS 22.003. Optionally, the UE may provide a suppress function which allows the user to switch off the DTMF function.

A.11  On/Off switchp. 84

The UE may be provided with a means of switching its power supply on and off. Switch-off shall be "soft", so that on activation, the UE completes the following housekeeping functions: termination of a current call, detach (where applicable) and storing required data in the SIM/USIM before actually switching off. As far as possible, this procedure should also apply on power failure (e.g. remote switch-off or low battery).

A.12  Sub-Addressp. 84

This feature allows the mobile to append and/or receive a sub-address to a Directory Number, for use in call set-up, and in those supplementary services that use a Directory Number.

A.13  Short Message Service Cell Broadcastp. 85

The Short Message Service Cell Broadcast enables the mobile equipment to receive short messages from a message handling system.
The short message service cell broadcast teleservice is described in specification TS 22.003

A.14  Short Message Service Cell Broadcast DRXp. 85

This feature enables a mobile equipment to save on battery utilization, by allowing the mobile equipment to not listen during the broadcast of messages the subscriber is not interested in.

A.15  Support of the extended Short message cell broadcast channelp. 85

This feature allows a mobile equipment by supporting of the extended Short message cell broadcast channel to enhance the capacity of the service. The support of the extended channel has low priority, i.e. the UE can interrupt the reading of this channel if idle mode procedures have to be executed.

A.16  Network Identity and Timezonep. 85

The feature provides the means for serving PLMNs to transfer current identity, universal time and the local timezone to mobile equipment, and for the mobile equipment to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the ME or have changed their name since the ME was sold. Additionally time and timezone information can be utilized by MEs as desired.
The network name time and timezone information will normally be transferred from the network to the ME:
  1. Upon registering on the network.
  2. When the UE geographically relocates to a different Local Time Zone.
  3. When the network changes its Local Time Zone, e.g. between summer and winter time.
  4. When the network changes its identity.
  5. At any time during a signalling connection with mobile equipment.
Further details of this feature are described in TS 22.042.
Up

A.17  Network's indication of alerting in the UEp. 85

This feature provides the means for serving PLMNs to transfer to a UE an indication that may be used by the UE to alert the user in a specific manner in the following cases:
  • mobile terminating call
  • network-initiated USSD
  • network-initiated Mobile Originated (MO) connection, if the ME supports the "network-initiated MO connection" feature.
Eight different indications are defined, whether the mobile terminating traffic is a call or USSD or related to the network-initiated MO connection procedure. These indications are sent by the network and received by the UE:
  • Three of these indications are used as levels, reflecting some kind of urgency: level 0 indicates that the UE shall not alert the user for USSD and remain silent in the case of call, level 2 shall be considered by the UE as more important than level 1 for the purpose of alerting the user.
  • The five other indications are used as categories, identifying different types of terminating traffic. The UE shall inform the user in a specific manner for each of these five categories. Nevertheless, the possible forms of the alert (different ringing tones, displayed text, graphical symbols...) is still up to the mobile manufacturer (some forms of alerts can be simultaneously used, e.g. ringing tones and text on the display).
The management of the feature by the UE requires for the handling of categories that:
  • the SIM/USIM stores for each category an informative text (maximum 25 characters per category) describing the type of terminating traffic associated with the category. This information could be used by the UE when alerting the user (display on the screen). It is necessary for the network operator to be able to change the meaning of each category.
  • The user has the ability to set up his/her own association between the type of terminating traffic (identified by each category) and the different types of alert provided by the UE. To help the user in this choice, the UE uses the informative text associated with each category (as stored in the SIM/USIM). The UE should keep this association when switched off.
    Default settings should also be defined in the ME for the following cases:
    • when the UE receives a call, USSD or a request for a network-initiated MO connection with no alerting indication,
    • when the UE receives a call, USSD or a request for a network-initiated MO connection with a category of alerting not defined in the SIM/USIM.
    These default settings should be separated per type of mobile terminated traffic received (call, USSD or request for a network-initiated MO connection).
A UE supporting the feature shall act according to the following points in case of mobile terminating traffic:
  • when a mobile terminating traffic is received without any indication (level or category), the ME shall act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic).
  • if a level is indicated, the UE shall use an alert enabling the user to differentiate between the three levels.
  • if a category is indicated, then:
    • if the SIM/USIM used in the UE does not store any information on that feature, the UE shall ignore the category received with any mobile terminating traffic and act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic).
    • if the category is not defined in the SIM/USIM, the UE shall act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic).
    • if the category is defined in the SIM/USIM, the UE shall use the alert associated with this category. In addition, it would be very useful for the user to be notified of the informative text associated with this category (e.g. on the display).
Some interactions between this feature and other services related to alerting are described below:
  • the call waiting service has priority on this feature, i.e. the call waiting tone will be played and not the alert derived by this feature. If possible, two different indications should be given to the user (e.g. the call waiting tone and a text on the display indicating call waiting, and in addition a text relative to the type of the new call received).
  • the presentation of the calling line identity takes priority on this feature, if it is not possible to display this information and another information related to this feature.
  • In case of interaction between this feature and UE specific features to alert the user (e.g. whole silent mode), the user should still be able to differentiate between the different levels or different types of terminating traffic, even if the alert itself may be changed.
Up

A.18  Network-initiated Mobile Originated (MO) connectionp. 87

The "Network-initiated Mobile Originated connection" feature allows the network to ask the mobile equipment to establish a mobile originated connection. The serving PLMN provides the mobile equipment with the necessary information which is used by the mobile equipment to establish the connection.
Currently only the network-initiated mobile originated call feature is specified. It is mandatory for a UE supporting CCBS and is used in the case of a CCBS recall.

Up   Top   ToC