hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
dc99f11e189ece5e1f94f5fea750aabc
|
02.07
|
44 Requested circuit/channel not available;
|
47 Resources unavailable, unspecified.
3) "Unobtainable destination - permanent/long term":
Cause number 1 Unassigned (unallocated) number;
|
dc99f11e189ece5e1f94f5fea750aabc
|
02.07
|
3 No route to destination;
| |
dc99f11e189ece5e1f94f5fea750aabc
|
02.07
|
22 Number changed;
| |
dc99f11e189ece5e1f94f5fea750aabc
|
02.07
|
28 Invalid number format (uncompleted number);
|
38 Network out of order.
NOTE 1: Optionally, it is allowed to implement cause number 27 in Category 3, instead of Category 2, as this is desirable already in Phase 1.
The table below describes a repeat call restriction pattern to any B number. This pattern defines a maximum number (n) of call repeat attempts; when this number n is reached, the associated B number shall be blacklisted by the MT until a manual re-set at the MT is performed in respect of that B number. When a repeat attempt to anyone B number fails, or is blacklisted, this does not prevent calls being made to other B numbers.
For the categories 1 and 2 above, n shall be 10; for category 3, n shall be 1.
call attempts
Minimum duration between Call attempt
Initial call attempt
-
1st repeat attempt
5 sec
2nd repeat attempt
1 min
3rd repeat attempt
1 min
4th repeat attempt
1 min
5th repeat attempt
3 min
.
.
nth repeat attempt
3 min
The number of B numbers that can be held in the blacklist is at the manufacturers discretion but there shall be at least 8. However, when the blacklist is full the MT shall prohibit further automatic call attempts to any one number until the blacklist is manually cleared at the MT in respect of one or more B numbers.
When automatic calling apparatus is connected to an MT1 or MT2, or where an MTO is capable of auto-calling, then the MT shall process the call requests in accordance with the sequence of repeat attempts defined above, i.e. requests for repeat attempts with less than the minimum allowed duration between them shall be rejected by the MT.
A successful call attempt to a number which has been subject to the call restrictions shown above (i.e. an unsuccessful call set up attempt has previously occurred) shall reset the "counter" for that number.
The "counter" for an unsuccessfully attempted B number shall be maintained in 24 hours or until the MT is switched off.
The automatic calling repeat call attempt restrictions apply to speech and data services.
NOTE 2: The restrictions only apply to unsuccessful Call Control activity, not to Radio Resource Management or to Mobility Management, so multiple attempts at radio channel access are not limited by this mechanism.
Annex B (normative):
Description of Mobile Station features
The section numbers refer to the items in tables 1, 2 and 3. The implementation (optional or mandatory) is shown in these tables.
B.1.1 Display of called number
This feature enables the caller to check before call setup whether the selected number is correct.
B.1.2 Indication of call progress signals
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 GSM 02.40 [8].
B.1.3 Country/PLMN indication
The country/PLMN indicator shows in which GSM PLMN the MS is currently registered. This indicator is necessary so that the user knows when "roaming" is taking place and that the choice of PLMN (GSM 02.11 [4] clause 5) is correct. Both the country and PLMN will be indicated. When more than one visited GSM PLMN is available in a given area such information will be indicated.
NOTE: The indication is described in GSM 02.30 [7].
B.1.4 Country/PLMN selection
When more than one GSM PLMN is available in a given area, the procedures for selection of PLMN are in conformity with GSM 02.11 [4].
B.1.5 Keypad
A physical means of entering numbers, generally, though not necessarily, in accordance with the layout shown in figure B.1.
See also GSM 02.30 [7] (Man-Machine Interface).
Additional keys may provide the means to control the Mobile Station (e.g. to initiate and terminate calls).
1
2
3
4
5
6
7
8
9
*
0
#
Figure B.1
B.1.6 IMEI
IMEI = International Mobile Station Equipment Identity.
Each MS shall have a unique identity and shall transmit this on request from the PLMN. For details see GSM 02.16 [5] and GSM 03.03 [10]. The IMEI is incorporated in a module which is built within the MS and is physically secured. The implementation of each individual module shall be carried out by the manufacturer.
B.1.7 Short message indication and acknowledgement
This feature allows the delivery of short messages to a MS 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 MS user.
The MS 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 GSM 02.03 [2].
B.1.8 Short message overflow indication
An indication shall be given to the SM user of the short message service when an incoming message cannot be received due to insufficient available memory.
B.1.9 DTE/DCE interface
A standard connector for attachment of a DTE to the MS and use in conjunction with data services, as defined in the 07 series specifications.
B.1.10 ISDN "S" terminal interface
A standard connector for attachment of equipment to ISDN standard I.420.
B.1.11 International access function
Provision is made for a direct, standard method of gaining international access. For this purpose the MS may have a key whose primary or secondary function is marked "+". This is signalled over the air 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.
B.1.12 Service Indicator (SI)
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, and that the MS has successfully registered on the selected PLMN. This may be optionally combined with the Country/PLMN Indication (subclause B.1.3).
B.1.13 Autocalling restriction capabilities
See annex A.
B.1.14 Emergency Calls capabilities
See clause 2.
B.1.15 Dual Tone Multi Frequency (DTMF)
The MS shall be capable to initiate DTMF in accordance with specifications GSM 02.03 [2] and GSM 03.14 [11]. Optionally, the MS may provide a suppress function which allows the user to switch off the DTMF function.
B.1.16 Subscription identity management
The IMSI is contained in a SIM, "Subscriber Identity Module". If the SIM is removable by the user, its removal detaches the MS, causing a call in progress to be terminated, and preventing the initiation of further calls (except emergency calls - see GSM 02.30 [7]).
The SIM may be in one of two physical sizes, both of which have identical electrical characteristics. The larger "ID‑1 SIM" is generally entered into the ME by the user. The card has a polarization mark (see annex C). The ME shall have an indication of how to obtain correct polarization of the card. The smaller "plug-in SIM" is generally mounted internally within the ME.
B.1.17 On/Off switch
The MS may be provided with a means of switching its power supply on and off. Switch-off shall be "soft", so that on activation, the MS completes the following housekeeping functions: termination of a current call, detach (where applicable) and storing required data in the SIM (see GSM 02.17 [6]) before actually switching off. As far as possible, this procedure should also apply on power failure (e.g. remote switch-off or low battery).
B.1.18 Sub-Address
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.
B.1.19 Support of encryption A5/1 and A5/2
Provision is made for support of up to 7 different algorithms, and the support of no encryption. It is mandatory for A5/1, A5/2 and non encrypted mode to be implemented on mobile stations. Other algorithms are optional.
B.1.20 Short Message Service Cell Broadcast
The Short Message Service Cell Broadcast enables the mobile station to receive short messages from a message handling system.
The short message service cell broadcast teleservice is described in specification GSM 02.03 [2].
B.1.21 Short Message Service Cell Broadcast DRX
This feature enables a mobile station to save on battery utilization, by allowing the mobile station to not listen during the broadcast of messages the subscriber is not interested in.
B.1.22 Service Provider Indication
When available and the MS is in idle mode, the MS shall indicate the Service Provider name. The Service Provider name is stored in the SIM {(max. 16 characters, including spaces)}. The SIM will indicate two options: (1) indication of Service Provider name in parallel to the indication of the PLMN the MS is registered-to; (2) indication of the Service Provider name alternatively to the indication of the PLMN the MS is registered-to. When roaming, the Service Provider name shall only be indicated in parallel to the PLMN the MS is registered-to. If the MS 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 choice of option shall be under control of the network operator.
B.1.23 Support of the extended Short message cell broadcast channel
This feature allows a mobile station 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 MS can interrupt the reading of this channel if idle mode procedures have to be executed.
B.1.24 Support of Additional Call Set-up MMI Procedures
This feature allows the user, through direct MS interaction, or the service provider of the user, to specify the user’s preferred emergency call MMI (e.g. 911 for US citizens or 999 for UK citizens) for use in any (i.e. home or visited) PLMN. This would be stored in the SIM and the ME would read this and use any entry of these digits to set up an emergency call. It may be possible to store more than one instance of this field.
B.1.25 Network Identity and Timezone
The feature provides the means for serving PLMNs to transfer current identity, universal time and the local timezone to mobile stations, and for the mobile stations 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 MS 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 Station.
Further details of this feature are described in GSM 02.42.
B.1.26 Ciphering Indicator
The ciphering indicator feature allows the ME to detect that ciphering is not switched on and to indicate this to the user, as defined in GSM 02.09.
The ciphering indicator feature may be disabled by the home network operator setting data in the "administrative data" field (EFAD) in the SIM, as defined in GSM 11.11.
If this feature is not disabled by the SIM, then whenever a connection is in place, which is, or becomes unenciphered, an indication shall be given to the user.
Ciphering itself is unaffected by this feature, and the user can choose how to proceed.
B.1.27 Network's indication of alerting in the MS
This feature provides the means for serving PLMNs to transfer to a Mobile Station an indication that may be used by the MS 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.
8 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 MS :
- Three of these indications are used as levels, reflecting some kind of urgency : level 0 indicates that the MS shall not alert the user for USSD and remain silent in the case of call, level 2 shall be considered by the MS 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 MS 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 MS requires for the handling of categories that :
- the SIM 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 ME 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 ME. To help the user in this choice, the ME uses the informative text associated with each category (as stored in the SIM). The ME should keep this association when switched off.
Default settings should also be defined in the ME for the following cases :
- when the ME receives a call, USSD or a request for a network initiated MO connection with no alerting indication,
- when the ME receives a call, USSD or a request for a network initiated MO connection with a category of alerting not defined in the SIM.
These default settings should be separated per type of mobile terminated traffic received (call, USSD or request for a network initiated MO connection).
An ME 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 ME shall use an alert enabling the user to differentiate between the three levels.
- if a category is indicated, then :
- if the SIM used in the ME does not store any information on that feature, the ME 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, 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 the category is defined in the SIM, the ME 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 ME 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.
B.1.28 Network initiated Mobile Originated (MO) connection
The "Network Initiated Mobile Originated connection" feature allows the network to ask the mobile station to establish a mobile originated connection. The serving PLMN provides the mobile station with the necessary information which is used by the mobile station to establish the connection.
Currently only the network initiated mobile originated call feature is specified. It is mandatory for CCBS ME and is used in the case of a CCBS recall.
B.1.29 Support of Localised Service Area (SoLSA)
The localised service area concept shall give the operator the basis to offer subscribers different services (e.g. tariffs or access rights) depending on the (cell based) location of the subscriber. For SoLSA features see GSM 02.43 [15])
B.1.30 ECSD
The same date rates as for HSCSD are supported, but due to the 8PSK modulation scheme this can be achieved by using fewer time slots, as described in GSM 02.34 [16].
B.1.31 EGPRS
The same set of services as for GPRS is supported but higher data rates are possible due to the 8PSK modulation scheme, as described in GSM 02.60 [17]. The 8PSK modulation scheme can be supported by the MS either only in down link direction or both in down and up link directions.
B.2.1 Support of supplementary services
Support of Call Barring and Call Forwarding Supplementary Services is mandatory. Support of other Supplementary Services is optional. Support of Unstructured SS Data, as described in GSM 02.90 [9] and GSM 02.30 [7], is optional.
If defined for a given Supplementary Service, the Functional Signalling shall be used, i.e. Unstructured SS Data signalling shall not be used. If an MS does not support the functional signalling for a given SS, the MS cannot declare that it supports that SS.
B.3.1 Abbreviated dialling
The directory number or part of it is stored in the mobile station together with the abbreviated address. After retrieval the directory number may appear on the display.
Abbreviated dialling numbers stored in the ME or SIM may contain wild characters.
It is permitted to extend the number by adding digits (by means of the keypad, R interface or a second abbreviated, or fixed dialling, number (and/or subaddress)) when setting up a call.
If wild characters are used to indicate missing digits, each wild character shall be replaced for network access or supplementary service operation, by a single digit entered at the keypad. The completed directory number is transmitted on the radio path.
B.3.2 Fixed number dialling
This feature provides a mechanism so that by the use of an electronic lock it is possible to place a bar on calling any numbers other than those pre-programmed in the SIM.
Under control of PIN 2, "Fixed Dialling Mode" may be enabled or disabled. The mode selected is stored in the SIM.
Fixed Dialling Numbers (FDNs) are stored in the SIM in the Fixed Dialling Number field. FDN entries may take the function of an Abbreviated Dialling Number/Supplementary Service Control (ADN/SSC), Overflow and/or sub-address. Fixed Dialling Numbers stored in the SIM may contain wild card characters.
The Fixed Dialling feature is optional, however when Fixed Dialling Mode is enabled, an ME supporting the feature shall;
- Prevent non FDN entries from being called.
- Only allow modification, addition or deletion of Fixed Number Dialling entries under control of PIN2.
- Allow calls to numbers stored as FDN entries.
- Support the reading and substitution of wildcards in any position of an FDN entry, via the ME MMI.
- Allow the user to replace each wildcard of an FDN entry by a single digit, on a per call basis without using PIN2. The digit replacing the wildcard may be used for network access or supplementary service operation.
- Only allow Supplementary Service (SS) Control (in Dedicated or Idle mode) if the SS control string is stored as an FDN entry.
- Allow the extension of an FDN entry by adding digits to the Fixed Dialling number on a per call basis.
- Allow the emergency number (112) to be called, even if it is not an FDN entry.
- Allow normal access to ADN fields (i.e. allow ADN entries to be modified, added or deleted) and the keyboard.
- Allow use of ADNs subject to the FDN filter.
When FDN is disabled, an ME supporting FDN shall;
- Allow FDN entries to be read as though they were normal ADN entries.
- Only allow modification, addition or deletion of Fixed Number Dialling entries under control of PIN2.
- Allow normal access to ADN fields and the keyboard.
If the ME does not support FDN, the MS shall not allow the making or receiving of calls when Fixed Dialling is enabled. However, emergency calls (112 and other user defined emergency numbers) shall still be possible.
NOTE: Wildcards are stored on the SIM. The wildcard coding is given in GSM 11.11.
B.3.3 Barring of Dialled Numbers
This feature provides a mechanism so that by the use of an electronic lock it is possible to place a bar on calling any numbers belonging to a pre-programmed list of numbers in the SIM.
Barred Dialling Numbers stored in the SIM may contain wild characters.
Under control of PIN2, "Barred Dialling Mode" may be enabled or disabled. The selected mode is stored in the SIM.
Under PIN2 control, it shall be possible to add, modify or delete a particular "Barred Dialling Number" (BDN) and to allocate or modify its associated comparison method(s). This BDN may have the function of an abbreviated dialling number / supplementary service control (ADN/SSC), overflow and/or sub-address.
When BDN is inactive, no special controls are specified, and the barred dialling numbers may be read (though not modified or deleted, except under PIN2 control) as if they were normal abbreviated dialling numbers. Access to keyboard and normal abbreviated dialling numbers (including sub-address) is also permitted.
When Barring of Dialled Numbers is active:
- Considering a number dialled by the user, if it exists a BDN for which there is a successful comparison (see below) between that BDN and the dialled number, then the ME shall prevent the call attempt to that number. If there is no BDN to fulfil those conditions, the call attempt is allowed by the ME.
With each BDN is associated one (or a combination of) comparison method(s) used between that BDN and the number dialled by the user. At least three different comparison methods are possible:
- The comparison is made from the first digit of that BDN, from the first digit of the dialled number and for a number of digits corresponding to the length of the BDN.
- The comparison is made from the first digit of that BDN, from any digit of the dialled number and for a number of digits corresponding to the length of the BDN.
- The comparison is made backwards from the last digit of that BDN, from the last digit of the dialled number and for a number of digits corresponding to the length of the BDN.
- If a BDN stored in the SIM contains one or more wild characters in any position, each wild character shall be replaced by any single digit when the comparison between that BDN and the dialled number is performed.
- If a BDN contains a sub-address, and the same number without any sub-address or with that sub‑address is dialled, the ME shall prevent the call attempt to that number.
- Numbers specified as "barred" may only be modified under PIN2 control.
- If the ME does not support barring of dialled numbers, the MS shall not allow the making or receiving calls. However, this feature does not affect the ability to make emergency calls.
If "Fixed Number Dialling" and "Barring of Dialled Numbers" are simultaneously active, the dialled number shall be checked against the two features before the ME allows the call attempt. In that case, a dialled number will only be allowed by the ME if it is in the FDN list and if the comparison between that number and any number from the BDN list is not successful.
The MS may support other selective barrings, e.g. applying to individual services (e.g. telephony, data transmission) or individual call types (e.g. long distance, international calls).
B.3.4 DTMF control digits separator
Provision has been made to enter DTMF digits with a telephone number, and upon the called party answering the ME shall send the DTMF digits automatically to the network after a delay of 3 seconds (± 20 %). The digits shall be sent according to the procedures and timing specified on GSM 04.08 [12].
The first occurrence of the "DTMF Control Digits Separator" shall be used by the ME to distinguish between the addressing digits (i.e. the phone number) and the DTMF digits. Upon subsequent occurrences of the separator, the ME shall pause again for 3 seconds (± 20 %) before sending any further DTMF digits.
To enable the separator to be stored in the address field of an Abbreviated Dialling Number record in the SIM, the separator shall be coded as defined in GSM 11.11 [14]. The telephone number shall always precede the DTMF digits when stored in the SIM.
The way in which the separator is entered and display in the ME, is left to the individual manufacturer's MMI.
MEs which do not support this feature and encounter this separator in an ADN record of the SIM will treat the character as "corrupt data" and act accordingly.
B.3.5 Selection of directory number in messages
The Short Message (Point to Point MT or MO, or Cell Broadcast), Network Initiated USSD or Network Response to Mobile Originated USSD message strings may be used to convey a Directory Number which the user may wish to call. This can be indicated by enclosing the directory number in a pair of inverted commas (" ").
If the displayed message contains these characters enclosing a directory number, a call can be set up by user action. Normal (unspecified) or International format (using + symbol) may be used.
The message may contain more than one directory number, in which case it is for the user to select the one required.
B.3.6 Last Numbers Dialled (LND)
The mobile station may store the Last "N" Numbers dialled in the SIM and/or the ME. "N" may take the value up to 10 in the SIM. It may be any value in the ME. The method of presentation of these to the user for setting up a call is the responsibility of the MS but if these numbers are stored in both the SIM and the ME, those from the SIM shall take precedence. The security for handling this is defined in GSM 02.17 [6].
B.3.7 ME-SIM lock
This feature controls the ability of the MS to access networks according to whether the ME matches the SIM based on one or more of the following criteria:
- Subscriber identity (IMSI).
- Group identifier level 1 (e.g. Service Provider identity).
- Group identifier level 2.
- PLMN identity (MCC+MNC).
One or more of these criteria may be activated. When any are activated, the ME shall be locked to the SIM such that the MS shall only make network registration attempts when there exists a bit-exact match between corresponding data elements on the ME and SIM for each of the activated criteria.
Secure means shall be provided to prevent unauthorized changes to the lock status or the contents of any of the data fields above on the SIM or ME.
B.3.8 Service Dialling Numbers
The Service Dialling Numbers feature allows for the storage of numbers related to services offered by the network operator/service provider in the SIM (e.g. customer care). The user can use these telephone numbers to make outgoing calls, but the access for updating of the numbers shall be under the control of the operator.
NOTE: No MMI is envisaged to be specified for these numbers and it is left to mobile manufacturer implementations.
Annex C (normative):
GSM-MoU ID1 SIM layout
NOTE: The symbol may be printed in the same location on the rear as well as the front face.
Annex D (informative):
Change history
Change history
SMG No.
TDoc. No.
CR. No.
Subclause affected
New version
Subject/Comments
SMG#22
304/97
A011
B.3.2
5.3.0
FDN Spec addresses wild card implementation
SMG#22
507/97
A014
Table 1
(1.26)
Subclause B.1.26
5.3.0
Introduction of mandatory ciphering indication
SMG#24
971/97
A015
Table 1 "basic MS features" and a new section B1.26 is introduced.
5.4.0
R97
$(NI Alert in MS)$: Introduction of the new work item "network's indication of alerting in the MS". With this feature, the user will be able to discriminate between different types of mobile terminated traffic.
SMG#24
972/97
A016
B1.25 was corrected
5.4.0
R96
Alignment of NITZ - Network name, time and timezone information will be transferred from the network to the ME: At any time during a signalling connection with mobile station.
SMG#25
6.0.0
Creation of version 6.0.0 as part of GSM release 1997
SMG#26
98-0317
A017
Introduction, 2, B.1.27, B.1.28 (new)
Verify with Anouch Chichmanian, not all referenced sections are there !!
6.1.0
R97
A new mechanism is introduced in Release 97 to allow the network to make the MS initiate a call. As an example, this mechanism is used for CCBS recall. A new MS feature "network initiated MO connection" is therefore added in GMS 02.07 to cover this case and to anticipate future applicability, e.g. to SMS or supplementary services.
SMG#26
98-0317
A018
B.1.27
6.1.0
R97
Extension of the network's indication of alerting in the MS to the new mechanism "network initiated Mobile Originated connection" defined in release 97.
SMG#27
98-0548
A019
1.1, 2, B.1.29 (new)
7.0.0
R98
Addition of the SoLSA feature
SMG#29
P-99-383
A020
2 (Table1), Annex B
8.0.0
R99
The new modulation scheme (8PSk) used in EDGE leads to the definition of new features for the Mobile Stations.
History
Document history
V6.1.0
July 1998
Publication
V7.0.0
October 1998
Unpublished
V8.0.0
July 1999
Unpublished
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
1 Scope
|
The present document defines requirements for call progress and related information to be provided to users of the GSM system.
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
1.1 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man‑Machine Interface (MMI) of the Mobile Station (MS)".
[3] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
[4] CEPT Recommendation T/CS 20-15: "Tones and announcements".
[5] CEPT Recommendation T/S F23: "Relative aux définitions et caractéristiques audibles des tonalités et des annonces parlées".
[6] ANSI T1.607: “Digital Subscriber Signalling Sytem No.1-Layer 3 Signalling Specification for Circuit Switched Bearer Service”.
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
1.2 Abbreviations
|
Abbreviations used in the present document are listed in GSM 01.04.
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
1.3 General
|
There are aspects of the Man Machine Interface (MMI) of the GSM Network which relate to users, but which are not covered by GSM 02.30, which deals specifically with the MMI of the Mobile Station (MS). The present TS covers the means by which mobile users, and callers to a GSM network, will be given information regarding progress of their calls.
Indications of call progress, such as ringing, engaged, unobtainable, and no radio channel, may in principle be verbal message, tones, displayed text or graphical symbols. Which combination of these applies may depend on the message, the MS and selection by the user or PLMN operator. However, verbal announcements will generally be reserved for situations which are peculiar to a mobile network, where users may be unfamiliar with any tone chosen to indicate conditions such as "call diversion" or "subscriber not available".
It may also be desirable to add comfort indications (e.g. tones, noise, music, clicks) while a call is being connected, since silence may cause an unfamiliar user to believe that nothing is happening.
Generally, on data calls, and on the data part of alternate speech/data or speech-followed-by-data calls, PLMN generated network tones and announcements should be muted.
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
2 Supervisory tones
| |
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
2.1 General
|
Supervisory Tones, indicating primarily ringing, engaged and unobtainable numbers, may be generated by both the PLMN and PSTN.
Except for ring tone, all tones indicating call progress to a MS user shall be generated in the MS, on the basis of signals from the network where available, and are according to the standard defined in the present document.
Tones sent to a caller to a MS will be generated in the network, generally local to the caller, and will be to the standard of his local exchange, except for mobile to mobile calls, where the tones will be generated in the calling MS. For mobile terminated calls, the ring tone will be generated in the called MSC (except OACSU).
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
2.2 Method
|
In the interests of early release of the traffic channel on failure to succeed in setting up a (mobile originated) call, where possible supervisory tones should be indicated over signalling channels. The MS will then generate the required tones. However, if the network generates an in-band announcement this will be indicated to the MS. In this case the MS shall connect the user to the announcement until instructed to release the call, either by the user or by the network. An alternate procedure may apply for MS able to generate appropriate announcements internally (see clause 3).
The ring tone will be sent over the traffic channel, since this channel must be available for traffic immediately it is answered (exception: Off Air Call Set Up). The Ring Tone is therefore generated by the PLMN or PSTN supporting the called phone.
On failed mobile terminated call attempts, the called MSC will either signal to the caller, if this is possible, or else will generate the required supervisory tones.
"Alert" is not a supervisory tone. The indication is signalled, and the MS may generate any form of indication to the user that the MS is being called.
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
2.3 Standard tones
|
MS generated tones will be generally in accordance with CEPT (GSM 900 and DCS 1800), or ANSI T1.607 (PCS 1900 for NA) recommendations, where appropriate, and are listed in table 1. Any network originated tones will be according to PLMN or PSTN choice.
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
2.4 Applicability
|
This method will apply in all cases where signalling is capable of indicating the supervisory tone required. However, for connection to certain fixed networks where this signalling is not possible, fixed network tones will be carried over the traffic channel.
Mobile Stations may employ any suitable technique to indicate supervisory information. However, if tones are employed, they shall be in accordance with the present document. The use of these tones in the MSC is preferred.
NOTE 1: The tones and/or announcement to the calling party should not be provided if the Information transfer capability is set to UDI.
NOTE 2: For a call with information transfer capability set to 3.1 kHz, the use of tones and/or announcement may cause the expiry of an awaiting answer timer in a modem or fax machine.
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
2.5 Point of introduction
|
Introduction E1.
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
2.6 Comfort tones
|
If desired by the PLMN operator, the network may optionally introduce "comfort tones" while the call is being connected, during what would otherwise be silence. This would be overridden by indication of a supervisory tone, an announcement or by traffic. PLMNs may offer this feature optionally to incoming or outgoing callers.
The "comfort tones" may take the form of tones, clicks, noise, music or any other suitable form, provided that they cannot be confused with other indications that might be expected.
This feature is intended to indicate to the user that his call is progressing, to prevent him terminating the call prematurely.
Table 1: Supervisory tones in GSM MSs
Tone
Frequency
Tolerance
Type
GSM 900/
DCS 1800
PCS 1900
for NA
GSM 900 /
DCS 1800
PCS 1900
for NA
1
Dial tone (optional)
425Hz
350Hz added to 440Hz
15Hz
Continuous
Continuous
2 *
Subscriber Busy (Called Number)
425Hz
480Hz added to 620Hz
15Hz
Tone on 500ms
Silence 500ms
Tone on 500ms
Silence 500ms
3 *
Congestion
425Hz
480Hz added to 620Hz
15Hz
Tone on 200ms
Silence 200ms
Tone on 250ms
Silence 250ms
4
Radio Path
Acknowledgement (Mobile
Originated only) (optional)
425Hz
425Hz
15Hz
Single tone 200ms
Single tone 200ms
5
{Radio Path Not Available
{Call Dropped – Mobile originated only
425Hz
425Hz
15Hz
200ms} On/off 200ms} for 3
burst
200ms} On/off 200ms} for 3
burst
6 *
Error/Special Information}
Number Unobtainable }
Authentication Failure }
950Hz
1400Hz
1800Hz
950Hz
1400Hz
1800Hz
50Hz
50Hz
50Hz
{Triple Tone
{Tones on 330ms
{Silence 1.0s
{Triple Tone
{Tones on 330ms
{Silence 1.0s
7
Call Waiting Tone
425 Hz (tolerance 15Hz), on for 200ms, off for 600ms on for 200ms, off for 3s, on for 200ms, off for 600ms on for 200ms. This tone is superimposed on the audio traffic received by the called user. Alternate tones are acceptable but not preferred.
440 Hz, on for 300 ms, 9.7s off followed by (440 Hz, on for 100 ms off for 100 ms, on for 100 ms, 9.7s off and repeated as necessary) This tone is superimposed on the audio traffic received by the called user.
Definition of these and other tones, together with advice on announcements, may be found in CEPT T/CS 20-15 and in T/SF
23.
* The duration of these tones is an implementation option. However, in each case, the MS should be returned immediately to the
idle state, and will be able to originate/receive calls, which will override these tones.
Ringing Tone (Alternative
national options permitted)
425Hz
440Hz added to 480Hz
15Hz
Tone on 1s Silence 4s
Tone on 2s
Silence 4s
For application of Call Control Cause Information Elements to these tones, see Annex A, GSM 02.40.
|
ba0f3e809f4055a7af9e98ebb7feeab9
|
02.40
|
3 Recorded announcements
|
In present networks, both fixed and cellular, the language of recorded announcements and displayed information is invariably that of the country of origin. However, this is generally undesirable in a multi-lingual environment such as is encountered on a pan-European network with international roaming. It is therefore probably desirable to minimise the number of such announcements.
Advanced MSs may be designed which have the ability to generate announcements in the form desired by the user, e.g. in the language preferred by the user. In this case, it becomes necessary to block any verbal announcements sent from the network towards the MS, to avoid clashes with those generated by the MS. The MS may be allowed to block in-band announcements in case appropriate announcements according to the Cause Information Elements (annex A) can be generated. The default setting of the MS shall be "non blocking", which could be set by MMI command to "blocking".
Announcements generated by the PLMN and sent to callers to that PLMN will generally be in the language of the PLMN. However, on some fixed networks it will be possible for the message to be signalled back to the caller's local exchange, which will then generate the announcement in its local language.
Annex A (normative):
Application of call control cause information elements to supervisory tones
The Cause Information Elements are listed and defined in GSM 04.08. This annex lists these elements and indicates which supervisory tone should be generated in response. It should be noted that some conditions (e.g. radio path not available, dropped call) may be deduced by the MS, rather than signalled explicitly over the air interface. All causes not listed below should result in the generation of tone 6. In case of multiple calls a tone should only be generated if it does not disturb an ongoing active call. "-" indicates no tone required.
Cause Tone
CC (see table 1)
16 Normal Clearing 1
17 User Busy 2
22 Number Changed -
30 Response to STATUS ENQUIRY -
31 Normal, unspecified -
34 No circuit/channel available 3
41 Temporary Failure 3
42 Switching Equipment Congestion 3
44 Requested circuit/channel not available 3
49 Quality of Service Unavailable 3
58 Bearer Capability not available 3
Annex B (informative):
Change history
Change history
SMG No.
TDoc. No.
CR. No.
Subclause affected
New version
Subject/Comments
Annex B First introduced at SMG#27
21
A001
Annex A
Update and approve Annex A
SMG#27
98-0549
A002
0.1 Normative references
2.3Standard tones
2.6 Comfort tones
Procedure for call progress indications.
Harmonization between GSM 02.40 version 5.0.0 and J-STD-007 Volume 7.
History
Document history
V6.0.0
April 1999
Publication
V7.0.1
July 1999
Publication
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
1 Scope
|
The present document defines network functions which are necessary to support services and facilities provided by PLMNs. A summary of the network functions is given in Table 1, where also an indication is given whether the network must support the function. The table also indicates whether or not a function requires internetworking signalling between PLMNs (i.e. use of Mobile Application Part, Technical Specification GSM 09.02).
All functions require signalling on the radio path as specified in Technical Specification GSM 04.08.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
1.1 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary service".
[3] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects".
[4] GSM 02.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description - Stage 1".
[5] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification".
[6] GSM 03.07: "Digital cellular telecommunications system (Phase 2+); Restoration procedures".
[7] GSM 03.08: "Digital cellular telecommunications system (Phase 2+); Organisation of subscriber data".
[8] GSM 03.12: "Digital cellular telecommunications system (Phase 2+); Location registration procedures".
[9] GSM 03.13: "Digital cellular telecommunications system (Phase 2+); Discontinuous Reception (DRX) in the GSM system".
[10] GSM 03.14: "Digital cellular telecommunications system (Phase 2+); Support of Dual Tone Multi-Frequency signalling (DTMF) via the GSM system".
[11] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions".
[12] GSM 03.22: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode".
[13] GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point to Point (PP)".
[14] GSM 03.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description; Stage 2".
[15] GSM 03.64: "Digital cellular telecommunications system (Phase 2+); Overall Description of the General Packet Radio Service (GPRS) Radio Interface; Stage 2".
[16] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2".
[17] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2".
[18] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2".
[19] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 2".
[20] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2".
[21] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2".
[22] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2".
[23] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
[24] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control".
[25] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification".
[26] GSM 12.00: "Digital cellular telecommunications system (Phase 2+); Objectives and structure of Network Management (NM)".
[27] GSM 12.01: "Digital cellular telecommunications system (Phase 2+); Common aspects of GSM Network Management (NM)".
[28] GSM 12.07: "Digital cellular telecommunications system (Phase 2+); Operations and performance management".
[29] GSM 12.02: "Digital cellular telecommunications system (Phase 2+); Subscriber, Mobile Equipment (ME) and services data administration".
[30] GSM 12.03: "Digital cellular telecommunications system (Phase 2+); Security management".
[31] GSM 12.04: "Digital cellular telecommunications system (Phase 2+); Performance data measurements".
[32] GSM 12.05: "Digital cellular telecommunications system (Phase 2+); Subscriber related event and call data".
[33] GSM 12.06: "Digital cellular telecommunications system (Phase 2+); GSM Network change control".
[34] GSM 12.10: "Digital cellular telecommunications system (Phase 2+); Maintenance provisions for operational integrity of Mobile Stations (MS)".
[35] GSM 12.11: "Digital cellular telecommunications system (Phase 2+); Maintenance of the Base Station System (BSS)".
[36] GSM 12.13: "Digital cellular telecommunications system (Phase 2+); Maintenance of the Mobile-services Switching Centre (MSC)".
[37] GSM 12.14: "Digital cellular telecommunications system (Phase 2+); Maintenance of location registers".
[38] GSM 12.20: "Digital cellular telecommunications system (Phase 2+); Network Management (NM) procedures and messages".
[39] GSM 12.21: "Digital cellular telecommunications system (Phase 2+); Network Management (NM) procedures and message on the A-bis interface".
[40] GSM 12.22: "Digital cellular telecommunications system (Phase 2+); Interworking of GSM Network Management (NM) procedures and messages at the Base Station Controller (BSC)".
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
1.2 Abbreviations
|
Abbreviations used in the present document are listed in GSM 01.04.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2 Network functions for basic service provision
| |
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.1 Call handling
|
This set of functions enables the establishment of communications between a mobile subscriber and another network subscriber in one of the following types of network PSTN, ISDN, PSPDN, CSPDN and other PLMNs.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.1.1 Call from a mobile subscriber registered in VLR
|
This is the normal case where the call is routed according to the dialled number. After the call, the MSC will send the charging information to the HLR, a billing entity and/or store the charging data on tapes or discs as described in Technical Specification GSM 12.05.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.1.2 Call from a mobile subscriber not registered in VLR
|
When the VLR receives a request for call set-up parameters from an MSC for an MS originating call, where the MS is not registered in the VLR, the VLR shall initiate a location updating procedure towards the HLR and in response parameters are given concerning category, services and restrictions. The call is then set up as in 2.1.1. This case only happens when a VLR or an MS failure has occurred.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.1.3 Call to a mobile subscriber
|
The call is routed (re-routed or forwarded) according to location data obtained from the HLR to the actual MSC and the MS is paged over the standardised radio interface.
For MSs in mode of operation A and B the paging may be performed via SGSN. This optional network function is further described in the Technical Specification GSM 03.60.
Table 1: Overview of network functions
Class of Network
Network Function
Network
Interworking
Function (NF)
Support
with MAP
NF for basic
Call Handling (Note 3)
M
X
service provision
Packet Handling (Note 4)
M
X
Subscriber Authentication
M
X
Emergency calls (Note 3)
M
-
Supplementary Services
M
X
Voice group services (Note 3)
O
X
Short Message Service (SMS)
M
X
Signalling information element confidentiality
M
X
NF for
Location registration
M
X
supporting:
Handover (Note 3)
- in the same BSS
M
-
- in the same MSC
M
-
- in the same PLMN
M
X
Call re-establishment (Note 3)
M
-
Additional NF
Queueing
O
-
for
call handling
OACSU (Note 3)
O
-
Security related services
M
X
Discontinuous reception
M
-
Discontinuous Transmission
M/O
-
Note 2
DTMF (Note 3)
M
-
Network
management
M
X
oriented NF
(Note 1)
NOTE 1: The function will not be fully specified by GSM (national specifications will complement).
NOTE 2: Only the receiver requirements are mandatory, the transmitter requirements support are optional.
NOTE 3: Only applicable for circuit switched services
NOTE 4: Only applicable for packet switched services
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.1.4 Call handling functions in HLR
|
The HLR should also support control functions for handling of supplementary services as described for each service in the GSM 03.8x series of Technical Specifications.
The HLR should provide information to the gateway MSC to allow it to route calls directed to a mobile subscriber: either a Mobile Station Roaming Number (MSRN) to allow the call to be routed to the visited MSC or a forwarding number if the call is to be forwarded to a destination different from the original one.
The HLR should provide the identity of the visited MSC to the SMS gateway MSC to allow it to route short messages directed to a mobile subscriber; further detail is given in Technical Specification GSM 03.40.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.1.5 Call handling functions in VLR
|
The VLR must provide subscriber parameters to the MSC as required for call handling.
The VLR must also support control functions for handling of supplementary services as described for each service in the GSM 03.8x series of Technical Specifications.
For a MS in mode of operation A or B, the VLR may optionally support establishment and maintenance of an association with an SGSN. This allows paging for a circuit switched call to be performed via SGSN.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.1.6 Call handling functions in MSC
|
The MSC must perform normal call routing and call control functions. The MSC will obtain subscriber parameters from its associated VLR.
The MSC must also be capable of performing handover as defined in section 3.2.
In some cases, the MSC must be able to act as a gateway MSC to provide an interface to other circuit-switched networks.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.1.7 Call handling functions in SGSN
|
For a MS in mode of operation A or B, the SGSN may optionally support establishment and maintenance of an association with a VLR. This allows paging for a circuit switched call to be performed via SGSN.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.2 Subscriber identity authentication
|
The purpose of subscriber identity authentication is defined in Technical Specification GSM 02.09.
The authentication mechanism is defined in Technical Specification GSM 03.20 and corresponding procedures on the MS-BSS interface are defined in Technical Specification GSM 04.08.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.3 Emergency call
| |
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.3.1 General
|
The land mobile system should be capable of efficient handling of emergency calls fromMS. The signalling procedures on the radio path for emergency calls are given in Technical Specification GSM 04.08.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.3.2 Routeing
|
The call should be routed automatically to an appropriate emergency centre based on the geographical location of the MS(e.g. based on the identity of the cell on which the call is established).
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.4 Supplementary services
|
PLMN may offer supplementary services as shown in Technical Specification GSM 02.04. The support of supplementary services will require control procedures in HLRs, VLRs and MSCs in addition to the control procedure in the fixed network. The technical realisation of supplementary services is given in the GSM 03.8x series of Technical Specifications.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.5 Voice group services
|
The PLMN may offer the voice group services. These are the voice group call service (VGCS) and voice broadcast service (VBS), as shown in GSM 02.68 and GSM 02.69, respectively. The support of the voice group call and voice broadcast services will require control procedures in HLRs, VLRs, MSCs and Group Call Register (GCR) and possibly control procedures in the fixed network. The technical realisation of these services is given in GSM 03.68 and GSM 03.69, respectively.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.6 Short Message Service
|
This set of functions allows the transfer of short messages i either direction between a mobile station and a short message service centre. More detailed information is given in Technical Specification GSM 03.40.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.6.1 Short Message Handling functions in the HLR
|
The HLR should be able to provide information to allow a short message to be routed from the SMS gateway MSC to the visited MSC and/or visited SGSN and then to the required MS.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.6.2 Short Message Handling Functions in the VLR
|
The VLR should provide subscriber parameters to the MSC as required for handling short messages.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.6.3 Short Message Handling Functions in the MSC
|
The MSC should perform the functions of relaying short messages in both directions between the fixed network of the PLMN and the BSS.
In some cases the MSC should be able to act as an SMS Gateway MSC to relay short messages from a Short Message Service Centre (SC) to a PLMN, or an SMS Interworking MSC to relay short messages from a PLMN to an SC.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.6.4 Short Message Handling Functions in the SGSN
|
The SGSN should perform the functions of relaying short messages in both directions between the fixed network of the PLMN and the BSS. The SGSN should also provide subscriber parameters required for handling the short messages relaying function. The SGSN should also download (from HLR or another SGSN) and store subscriber parameters required for handling the short message relaying functions.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.7 Signalling information element confidentiality
|
A procedure should be implemented providing for the confidentiality of signalling information elements on the radio path. In Technical Specification GSM 02.09 the signalling information elements which need to be protected are given.
The Encryption Key is calculated in both the MS and the network. Detailed information is given in Technical Specification GSM 03.20.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.8 Packet Handling
|
This set of functions enables routing of packets between an MS and a network host in one of the following types of network: PSPDN, networks based on the Internet Protocol (IP) and other PLMNs.
2.8.1 Packet handling functions in SGSN.
The SGSN should perform the functions of routing packets in both directions between one or more GGSN’s and the BSS. The SGSN should also download (from HLR or another SGSN) and store subscriber parameters required for handling the packet routing functions.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.8.2 Packet handling functions in GGSN
|
The GGSN should act as a gateway that provides interface(s) to other packet data networks. The GGSN should further perform the functions of routing packets in both directions between these networks and one or more SGSN’s. The GGSN should also download (from SGSN) and store subscriber parameters required for handling the packet routing functions.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
2.8.3 Packet switched service functions in HLR
|
The HLR should provide permanent storage of subscriber data.
The HLR should provide the identity of the visited SGSN to the SMS gateway MSC to allow it to route short messages directed to a mobile subscriber; further detail is given in Technical Specification GSM 03.40.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
3 Network functions for supporting cellular operation
| |
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
3.1 Location registration
| |
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
3.1.1 Definitions
|
Location registration means that the PLMNs keep track of where MSs are located in the system area. The location information is stored in functional units called location registers. Functionally there are four types of location registers:
- the home location register (HLR) where the current location and all subscriber parameters of a MSare permanently stored;
• the visitor location register (VLR) where all relevant parameters concerning a MS are stored aslong as the station is within the area controlled by that visitor location register.
• the serving GPRS support node (SGSN) where all relevant parameters concerning a MS using packet switched services are stored as long as the MS is controlled by that SGSN,
- the GGSN node where routing information for all static PDP addresses related to a mobile subscriber is stored.
See also Technical Specification GSM 03.02 where the network architecture is described.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
3.1.2 Procedures
|
Procedures related to location registration are specified in Technical Specification GSM 03.12.
They comprise:
i) location updating which enables the MS to inform the network that its location area has to be updated, i.e. the MS has received a location area identity which is different from that contained in its memory. In order to avoid unnecessary updating, the current location area identity should be stored in a non-volatile memory in the MS;
ii) location cancellation which is used to delete an MS from a VLR or from an SGSN;
iii) periodic location updating which enables the location of stationary MSs to be confirmed at a rate determined by the operator;
iv) as a network option, IMSI detach/attach operation. When a MS has informed the network that it is IMSI detached, the network is aware that the subscriber is not active;
v) routing updating which enables the MS to inform the network that its routing area has to be updated;
vi) periodic routing updating which enables the location of stationary MSs to be confirmed at a rate determined by the operator;
vii) GPRS detach/attach operation. When a MS has informed the network that it is GPRS detached, the network is aware that the subscriber is not active;
viii) cell updating which enables the MS to inform the network that its cell has been updated.
The procedures i) to iv) are defined for circuit switched services, and ii) and v) to viii) are defined for packet switched services. Combined procedures for circuit and packet switched services are also defined in GSM 03.60 for GPRS. The procedure i) may be combined with v), iii) may be combined with vi) and iv) may be combined with vii).
The procedures also include mechanisms for restoration of location registers after failure. These procedures are defined in Technical Specification GSM 03.07.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
3.1.3 Information stored in location registers
|
Information to be stored in location registers is listed in Technical Specification GSM 03.08.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
3.2 Handover
| |
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
3.2.1 Definitions
|
The following case are required:
i) handover between physical channels of the same Base Station System (BSS). This capability could be used in the following situations:
- when the physical channel carrying the call is subject to interference or other disturbances;
- when a physical channel or channel equipment carrying a call has be to be taken out of service for maintenance or other reasons;
ii) handover between Base Station Systems (BSSs) of the same MSC;
iii) handover between BSSs of different MSCs of the same PLMN.
Cases ii) and iii) are used in order to ensure continuity of the connection when an MS moves from one BSS area to another.
For case iii) two procedures are defined:
a) basic handover procedure where the call is handed over from the controlling MSC (MSC-A) to another MSC (MSC-B);
b) subsequent handover procedure where the call is handed over from MSC-B to MSC-A or to a third MSC (MSC-B').
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
3.2.2 Procedures
|
The procedures are described in Technical Specification GSM 03.09.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
3.3 Call re-establishment
|
Re-establishment of a call may be performed when a traffic channel (TCH) has been lost during the call, e.g. when a handover could not be completed in time.
Call re-establishment is only performed on TCHs and when the call is in the connected state (see Technical Specification GSM 04.08). The procedures are specified in Technical Specification GSM 04.08.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4 Additional network functions for call handling
| |
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.1 Queuing
|
As a PLMN option MS originating and/or MS terminating calls may be queued at the BSS. (NOTE: this queuing is additional to that for normal call handling). However, the following condition must be met:
- for MS terminating calls the queuing must not conflict with abnormal release conditions in the fixed network. In general, calls that may have passed international circuits should not be queued, i.e. it should not be applied to calls where the originating network is not known to the PLMN.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.2 Off-Air-Call-Set-Up (OACSU)
| |
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.2.1 General
|
OACSU may be implemented in PLMNs in order to increase the call handling capacity of the PLMN.
OACSU may be implemented in PLMNs on an optional basis subject to the following conditions:
i) OACSU should not be used for calls to an international number;
ii) OACSU should not be used for incoming international calls, except where bilateral agreement has been reached to allow such an application of OACSU. For the avoidance of doubt, OACSU shall not be applied to calls where the call type or originating network is not known by the PLMN;
iii) foreign MSs not supporting the OACSU procedure should be allowed to access the PLMNs where OACSU is used;
iv) MSs supporting OACSU should be capable of operating in PLMNs where OACSU is not implemented;
v) OACSU should only be used for telephone calls.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.2.2 Signalling procedures
|
Signalling procedures supporting OACSU are specified in Technical Specification GSM 04.08.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3 Security related services
|
PLMNs will offer three security related services on the radio path: confidentiality of the user identity, confidentiality of user data and confidentiality of signalling information elements and connectionless user data.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3.1 Identity confidentiality
|
This service provides for the privacy of the identities of subscribers. An intruder cannot identify which subscriber is using a certain resource on the radio path. Instead of IMSI a temporary identity is used.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3.1.1 Circuit switched services
|
This identity (TMSI) is a local number only valid in a given location area. The TMSI is allocated by the VLR and is sent to the MS in a ciphered mode, when ciphering is available as a network option. The IMSI and IMEI should also be transmitted in ciphered mode, whenever the procedure allows this, and when ciphering is available as a network option.
The structure of the TMSI is defined in Technical Specification GSM 03.03.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3.1.2 Packet switched services
|
The packet temporary mobile subscriber identity (P-TMSI) is a local number only valid in a given routing area. The P-TMSI is allocated by the SGSN and is sent to the MS in a ciphered mode, when ciphering is available as a network option.
The structure of the TLLI is defined in Technical Specification GSM 03.03.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3.2 User data confidentiality
|
This service provides for the confidentiality of anything transmitted on a traffic channel.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3.2.1 Circuit switched services
|
Encryption/decryption is done in the MS and BSS with a key which is calculated in both the MS and network. Detailed information is given in Technical Specification GSM 03.20.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3.2.2 Packet switched services
|
Encryption/decryption is done in the MS and SGSN with a key which is calculated in both the MS and network. Detailed information is given in Technical Specification GSM 03.20.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3.3 Signalling Information Element Confidentiality
|
This service provides for the confidentiality of anything transmitted on a signalling channel
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3.3.1 Circuit switched services
|
Signalling information to control the service offered to a subscriber or connectionless user data can be encrypted/decrypted. Encryption/decryption is done in the MS and BSS with a key which is calculated in both the MS and the network. Detailed information is given in Technical Specification GSM 03.20.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.3.3.2 Packet switched services
|
Signalling information to control the service offered to a subscriber can be encrypted/decrypted. Encryption/decryption is done in the MS and SGSN with a key which is calculated in both the MS and the network. Detailed information is given in Technical Specification GSM 03.20.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.4 Discontinuous Reception
|
Discontinuous reception is a technique used to reduce the battery consumption ofMSs. The operation of the technique is specified in Technical Specification GSM 03.13. This function must be supported by the network, but is optional forMSs.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.5 Discontinuous Transmission
|
Discontinuous transmission is a technique used to reduce overall interference level on the radio interface, and to reduce the battery consumption in the MSs. The operation of the technique is specified in Technical Specification GSM 05.08. This function must be supported by the MSs, whereas only the receiver requirements are mandatory in the network.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
4.6 Support of DTMF
|
DTMF is supported as defined in Technical Specification GSM 03.14.
|
5a0e7a8690c6d7a6c171103231d5c462
|
03.01
|
5 Network management oriented network functions
|
Network management functions are dealt with in the 12 series of GSM Technical Specifications. An overview is given in Technical Specification GSM 12.00.
Annex A (informative):
Change Request History
Change history
SMG No.
TDoc. No.
CR. No.
Section affected
New version
Subject/Comments
SMG#07
4.0.4
ETSI Publication
SMG#17
101/96
B001
5.0.0
Inclusion of "Voice group services" as network function
Release 1996 version
SMG#18
287/96
A003
5.1.0
Queuing indication to the MS in case of Mobile Originating Calls
SMG#27
6.0.0
Release 1997 version
SMG#28
P-99-153
A004
6.1.0
SMG#29
7.0.0
Release 1998 version
History
Document history
V7.0.0
September 1999
Publication
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
1 Scope
|
The present document describes the support of Videotex service within the GSM PLMN network, taking into account the service definition as per CCITT Recommendation F.300 and Bearer Services specified in GSM 02.02 for a GSM PLMN.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] ETS 300 072: "Terminal Equipment (TE): Videotext presentation layer protocol Videotext presentation layer syntax".
[2] ETS 300 073: "Videotext presentation layer data syntax; Geometric Display".
[3] ETS 300 075: "Terminal Equipment (TE): Videotext processable data".
[4] ETS 300 079: "Integrated Services Digital Network (ISDN); Syntax based Videotex End-to-end protocols circuit mode DTE-DTE".
[5] ETS 300 080: "Integrated Services Digital Network (ISDN); Lower layer protocols for telematic terminals".
[6] ETS 300 218: "Integrated Services Digital Network (ISDN); Syntax based Videotex Lower layer protocols using packet mode (X.31 Case A abd Case B)".
[7] ETS 300 221: "Terminal Equipment (TE): Syntax based Videotex Lower layer protocols using packet mode access over the Public Switched Telephone Network (PSTN)".
[8] ETS 300 222: "Framework of Videotext Terminal Protocols".
[9] ETS 300 223: "Terminal Equipment (TE): Syntax based Videotex End-to-end protocols".
[10] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
[11] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)".
[12] GSM 03.10: "Digital cellular telecommunication system (Phase 2+); GSM Public Land Mobile Network (PLMN) connection types".
[13] GSM 03.70: "Digital cellular telecommunication system (Phase 2+); Routeing of calls to/from Public Data Networks (PDN)".
[14] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
[15] GSM 07.02: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities".
[16] GSM 07.03: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities".
[17] GSM 08.20: "Digital cellular telecommunication system (Phase 2+); Rate adaption on the Base Station System ‑ Mobile‑services Switching Centre (BSS ‑ MSC) interface".
[18] CCITT Recommendation E.163: "Numbering plan for the international telephone service".
[19] CCITT Recommendation E.164: "Numbering plan for the ISDN era".
[20] CCITT Recommendation F.300: "Videotext service".
[21] CCITT Recommendation X.31: "Support by Packet Mode Terminal Equipment in ISDN".
[22] CCITT Recommendation X.32: "Interface between Data Terminal Equipment (DTE) and Data Circuit Terminating Equipment (DCE) for terminals operating in Packet Mode and accessing a PSPDN through a PSTN or an ISDN or a CSPDN".
[23] CCITT Recommendation X.75: "Packet -switched signalling system between public networks providing data transmission services".
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
2.1 Abbreviations
|
In addition to those below, abbreviations used in the present document are listed in GSM 01.04.
AU Access Unit
SBVT Syntax Based Videotex Terminal
VAP Videotex Access Point
VSC Videotex Service Centre
VTX host The computer dedicated to Videotex service
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
3 Service definition
|
The Videotex service is an interactive service that by means of proper access points and standardized procedures provide the access to data base information stored in host computers external to the PLMN, via public telecommunication networks.
The basic elements considered for a Videotex system are:
- the user terminal;
- the telecommunication network;
- the Videotex host computer or Videotex service access function (PAD/VAP/VSC).
The specific features that are relevant to the service are:
- a Videotex call is usually a mobile originated call, but mobile terminated call are supported as well;
- it is an interactive service;
- the requested information is generally in form of text and/or pictures;
- the information access is under the control of the user;
- there are different Videotex syntax standards , depending on high layer attributes of the service (Profile 1, Profile 2, Profile 3, Profile 4, "ASCII"), ETS 300 073 (Geometric Display), ETS 300 075 (Processable Data), ETS 300 177 (Photographic Syntax).
Common end-to-end protocols for syntax-based Videotex are specified in ETS 300 223 and ETS 300 079.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
3.1 Videotex service in the GSM context
|
Figure1 shows the basic concept underlying all the GSM Bearer Services, as defined in GSM 02.02.
The most general case is the GSM PLMN interworking with a Transit Network (PSTN and/or ISDN, none), interconnected to a Terminating Network (PSPDN, PSTN and/or ISDN).
Figure 1/03.43: GSM Bearer Service scheme
As the information transfer mode attribute on the PLMN is always "Circuit", and the information transfer capability is always "UDI", the end-to-end Bearer Service attributes depend mainly on the combination of Transit/Terminating networks utilized in the overall connection.
This means that both "circuit mode" and "packet mode" bearer services are appropriate for Videotex on a GSM PLMN; in particular (see table 4/GSM 02.02):
- BS 21 to BS 26, covering data circuit duplex asynchronous rates up to 9 600 bit/s;
- BS 41 to BS 44 covering PAD access asynchronous rates up to 9 600 bit/s;
- BS 31 to BS 34, covering data circuit duplex synchronous rates up to 9 600 bit/s;
- BS 51 to BS 53, covering packet mode synchronous rates up to 9 600 bit/s;
Concerning packet mode services, the GSM PLMN network supports both:
- basic packet/PAD mode, allowing the GSM users to access dial-in asynchronous (PAD) or synchronous (AU/PH) ports of a PSPDN (to which individual subscriber is subscribed to), using respectively BS 2x or BS 3x GSM Bearer Services;
- dedicated packet/PAD mode, allowing the GSM users a "seemingly immediate" access to the PSPDN word, without any explicit intermediate passage on the transit network to access the PSPDN port; BS 4x and BS 5x are used in this case.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
4 Network architecture
|
As identified in CCITT Recommendation F.300, various configurations are permitted for the structure of a Videotex system. A terminal can be connected to a Videotex host server:
- directly by a telecommunication network;
- via a Packet Assembly/Disassembly (PAD);
- via a Videotex Access Point (VAP);
- via a Videotex Service Centre (VSC) which may also act as a Videotex host.
All these configurations can be supported by a GSM PLMN, as detailed in the following network schemes.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
4.1 Videotex host directly connected to PSTN/ISDN
|
When it is assumed that the Videotex centre is directly connected to the PSTN/ISDN, the network scheme is as shown in figureig.2 /03.43.
Figure 2/03.43: VTX host directly connected to PSTN/ISDN
With reference to the general scheme in figure1/03.43, the terminating network (in this case working as transit network as well) uses a 3,1 kHz audio information transfer capability; at both ends of the terminating network (MSC/IWF and VTX host) a voiceband modem is allocated, whose actual bit-rate is selected in the BC-IE at Call Establishment, within the GSM standard rates (maximun 9 600 bit/s).
BS 2x series apply in this case.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
4.2 Videotex host accessed via PAD
|
Figure 3/03.43 summarizes this configuration, outlining all possible network alternatives.
Figure 3/03.43: VTX host accessed via PAD
The main service alternative concerns basic/dedicated PAD access.
In case of basic PAD access, the transit network (PSTN and/or ISDN) is utilized to access the PAD, remotely located with respected to MSC/IWF; the Videotex customer has to make a E.164 Call to the desired PAD, then a second step is necessary to access the Videotex host.
BS 2x are utilized in this case; the information transfer capability on the transit network is 3.1 kHz audio (PSTN or ISDN).
In case of dedicated PAD access, two options are still possible (see GSM 09.05):
- the PAD is remotely located with respect to the IWF, and automatically connected to IWF, via a dedicated circuit or a data circuit on a public network (PSTN or ISDN), so that the Videotex user has "direct" access to the PAD;
- the PAD is located in the MSC/IWF and connected to the PSPDN via X.25 or X.75.
The dedicated PAD access provides the shortest possible connection from the PLMN to a PAD for both home subscribers staying in the home PLMN and foreign subscribers roaming in a visited PLMN.
BS 4x are utilized for dedicated PAD access.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
4.3 Videotex host accessed via VAP
|
Figure 4/03.43 summarizes this configuration, outlining all possible network alternatives.
Figure 4/03.43: VTX host accessed via VAP
Circuit Mode access to the VAP via ISDN transit network (and BS 3x) is according to ETS 300 079 and ETS 300 080.
Concerning Packet Mode access to VAP, again the main choice concerns basic/dedicated packet mode.
In case of basic packet mode configuration, the transit network is utilized to access a conventional X.32 dial port in the PSPDN or a PH function (X.31 Case A), remotely located with respected to MSC/IWF and functionally operating as VAP with respect to Videotex service.
The Videotex customer has to make a E.164/E.163 Call to the desired dial port/PH, then a second step is necessary to access the Videotex host.
BS 3x are utilized in this case; the information transfer capability on the transit network is 3,1 kHz audio (PSTN or ISDN) or UDI (ISDN).
In case of dedicated packet mode, the PH is logically part of the PLMN. The interface between the PH and the PSPDN is X.75 or proprietary; two options are still possible for its physical location:
- the PH is remotely located with respect to the IWF;
- the PH (VAP function) is located in the PLMN.
BS 5x are utilized in this case.
The dedicated packet mode provides the shortest possible connection from the PLMN to a PSPDN for both home subscribers staying in the home PLMN and foreign subscribers roaming in a visited PLMN.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
4.4 Videotex host accessed via VSC
|
Though the Videotex Access Function is explicitly separate with respect to the Videotex host, no impact results on the overall Network architecture.
Actually the VSC can be considered a front-end function of the same Videotex host (either physically separate or integrated), so that all the above configuration in principle apply.
In particular the network schemes in Figures 3, 4/03.43 are appropriate, and all the above considerations on basic/dedicated PAD access/packet mode are still relevant.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
5 Reference configuration of the Mobile Station (MS)
|
The following types of reference configuration of the MS are possible:
Figure 5/03.43: Reference Configuration of the MS
The definitions of the functional blocks shown in figure 5 are reported in GSM 04.02.
Concerning specific Videotex functions of the terminal, full support of end-to-end protocols for Syntax-based Videotex is granted in a GSM PLMN, within the limitation of 9 600 bit/s as maximum speed, due to inherent bounds of GSM system.
In this respect, TE2 shall be:
- either a conventional Videotex terminal operating in asynchronous circuit mode on a V.series standard interface;
- or a fully compliant SBVT equipment operating in synchronous packet mode as per ETS 300 221 standard (lower layers) and ETS 300 223.
TE1 shall be a typical ISDN-SBVT equipment, operating according to either ISDN Circuit mode (ETS 300 079 and ETS 300 080 standards) or ISDN packet mode (ETS 300 218 and 300 223 standards).
MT0 integrates in a single equipment both Videotex and mobile termination functions.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
6 Bearer Service configuration and settings
|
Support of Videotex service on the the GSM PLMN is via GSM standard Bearer Services, as specified in various GSM Technical Specificationa. In the following specific reference on the main technical aspects are reviewed.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
6.1 Connection Types
|
Transparent or non-transparent network support can be requested to the GSM PLMN for Videotex service.
The information transfer protocol models are those in figure 6/GSM 03.10, models 1a, 2a, 3a, 4a for ISDN-related MS configurations, and models 1b, 2b, 3b, 4b for PSTN-related MS configurations.
Concerning "Circuit mode" Videotex, the choice between transparent (error prone, fixed delay connection) and non-transparent (error resilient, variable delay connection) network support affects just the QOS general attribute.
For "packet mode" Videotex the transparent support, due to inherent constraints will only work in case of access to a X.32 dial port (see section 8.7/GSM 09.06); therefore "Dedicated packet mode" Videotex is only possible with non-transparent support.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
6.2 Terminal Adaption functions
|
The TAFs used for Videotex are the asynchronous and synchronous standards defined in GSM 07-series; rate adaption functions are those specified in GSM 04.21 and GSM 08.20.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
6.3 Signalling aspects
|
All GSM standard rates (up to 9 600 bit/s) can be used for Videotex on a GSM PLMN; appropriate settings in BC-IE and LLC (where applicable) fix the rate on the GSM connection, and identify the voiceband modem to be used (when applicable) by the IWF.
When a 1 200/75 bit/s Bearer Capability is requested, the 75 bit/s rate is intended for MS to Network direction only; no provision for "reversing" the channel rates is provided on the GSM Network.
GSM 07.01 is the reference for all technical aspects concerning BC/LLC/HLC on a GSM PLMN.
|
157bacc4edc4bb5d3eed6ec0265827dd
|
03.43
|
6.4 Network interworking
|
Ad-hoc Specifications are devoted in the GSM normative to explicitly cover the aspects of PLMN interworking; being Videotex service a generic application running on top of GSM standard Bearer services, all technical aspects in those GSM specifications apply.
The reference are:
- GSM 09.07, which details interworking requirements towards PSTN/ISDN;
- GSM 09.05 and GSM 09.06, which detail interworking requirements towards PSPDN;
- GSM 03.70, defining general Call routing scenarios to/from PDNs.
Concerning packet mode it should be stressed that X.31 Case B is currently not feasible within PLMN (see section 7.4/GSM 09.06).
Moreover for dedicated packet mode, whilst Mobile Originated Calls are fully supported, Mobile Terminated Calls are not supported (see section 9.1/GSM 09.06).
Annex A (informative):
Change Request History
Change history
SMG No.
TDoc. No.
CR. No.
Section affected
New version
Subject/Comments
SMG#07
4.1.2
ETSI Publication
SMG#20
5.0.0
Release 1996 version
SMG#27
6.0.0
Release 1997 version
SMG#29
7.0.0
Release 1998 version
History
Document history
V7.0.0
August 1999
Publication
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
7 Indicates GSM Phase 2+ Release 1998;
|
x the second digit is incremented for technical enhancements, corrections, updates, etc
y the third digit is incremented when editorial only changes have been incorporated in the specification.
National transposition dates
Date of adoption of this EN:
21 July 2000
Date of latest announcement of this EN (doa):
31 October 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e):
30 April 2001
Date of withdrawal of any conflicting National Standard (dow):
30 April 2001
Introduction
This system architecture stage 2 description is part of the overall standard for a GSM based Cordless Telephony System (GSM-CTS).
The system is intended to provide a cordless connection between the PSTN/ISDN network or a GSM network and GSM-based CTS Mobile Stations (GSM-MS) via a private CTS Fixed Part (CTS-FP).
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
1 Scope
|
The present document defines the stage 2 description for the Cordless Telephony System (CTS) based on GSM radio. As the second stage of a three-level structure, it is derived from the stage 1 service description.
As mentioned already in the stage 1 description, a phased approach is indispensable to have an early first specification ready for market needs. The first phase focuses on the requirements necessary to elaborate the radio interface and the security aspects for an application supporting the speech tele-service (including DTMF support) in a residential single cell environment.
The standardisation of the physical layers of the GSM-CTS fixed network interface is not in the scope of the present document.
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
1 GSM 01.04: "Abbreviations and Acronyms", Version 5.0.0.
[2] GSM 02.56: "Digital cellular telecommunications system (Phase 2+), Phase 1; GSM Cordless Telephony System (CTS), Phase 1; Service Description; Stage 1".
[3] GSM 03.03 "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification".
[4] GSM 03.20: "Digital cellular telecommunication system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1, Security related network functions; stage 2".
[5] GSM 03.52 "Digital cellular telecommunication system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1, Lower layers of the CTS radio interface".
6 GSM 03.40: " Digital Cellular Telecommunications System (Phase 2+); Technical Realisation of the Short Message Service (SMS) Point-to-Point (PP)".
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
3 Definitions and abbreviations
| |
fcc930975597116eb21de958d20d3f3d
|
03.56
|
3.1 Definitions
|
Besides the definitions according to the CTS stage 1 service description [2] the following definitions are applicable to the present document:
Fixed network: A PSTN or ISDN network.
Access network: the network on which the CTS-FP is connected and which carries the incoming and outgoing calls to the CTS-FP. It could be either a fixed network or a GSM network.
CTS radio interface: The radio interface between CTS-MS and CTS-FP.
CTS-MSIx: CTS Local Mobile Subscriber Identity related to the xth CTS-MS initialised on a CTS-FP
CTS-MS attachment: CTS-MS attachment is a procedure which a CTS-MS initiates when the CTS-MS detects that it is within coverage of a CTS-FP to which the CTS-MS is enrolled.
CTS-MS detachment: CTS-MS detachment is a procedure that the CTS-MS initiates, and indicates to the CTS-FP that the CTS-MS will be no longer reachable by the CTS-FP.
Enrollment: The procedure by which a CTS-MS is made known to a CTS-FP in order that the CTS-FP can provide CTS service.
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
3.2 Abbreviations
|
The following list describes the abbreviations and acronyms used in the present document. The GSM abbreviations explained in GSM 01.04 [1] are not included below.
CTS Cordless Telephony System
CTS FRA CTS Frequency allocation functional entity
CTS HLR CTS Home Location Register Functional entity
CTS-FP CTS-Fixed Part
CTS-MS CTS-Mobile Station
CTS-MSI CTS Mobile Subscriber Identity in the CTS-FP
CTS-MSN CTS Mobile Station Number
CTS-SAP CTS Service Access Point
CTS-SIM CTS Subscriber Identity Module
DPLMN Donor PLMN
GFL Generic Frequency List
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
4 Main concepts
| |
fcc930975597116eb21de958d20d3f3d
|
03.56
|
4.1 CTS definition
|
The CTS operator can provide a CTS service which allows (using a modified GSM radio interface) to provide a cordless telephone service attached to the fixed network or to a cellular network. The services offered by CTS are limited to the type of network to which the CTS-FP is connected. In order to offer this service the CTS operator needs to have an agreement with a GSM operator in order to use the frequencies belonging to his PLMN by the CTS FP. This type of PLMN is termed to be a Donor PLMN (DPLMN).
NOTE: The CTS operator may be a GSM operator.
Depending upon the operator agreements a person wanting to operate a CTS-FP (the CTS FP subscriber) may be required to have at least three subscriptions: one with the CTS operator, and one with the GSM operator; and in addition to these subscriptions the CTS FP subscriber needs to have either a subscription to a fixed or GSM operator to which the CTS FP is to be connected or access to a fixed line interface.
The frequencies which the CTS service uses may be controlled by the operator which holds the license for the GSM frequency band used for the service.
The CTS FP subscriber can have agreements with other CTS MS subscribers to use his base station.
The role model is described in [2].
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
4.2 CTS Network
|
A CTS network is defined to be made up of one or more CTS cells. When a CTS network has more than one cell these cells are synchronised (in frequency, at TDMA frame edges and TDMA frame number) on the radio interface.
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
4.3 CTS Role models
| |
fcc930975597116eb21de958d20d3f3d
|
03.56
|
4.3.1 CTS FP owner's role model
|
CTS role model for a CTS FP subscriber
In order to receive a valid CTS-GFL the CTS-FP owner needs to have a subscription (2) with a CTS operator. This subscription is materialised by a CTS-SIM card stored in the CTS-FP. The CTS operator has an agreement (3) with a DPLMN part of a GSM operator1 to use its frequencies for CTS allocation.
When the CTS-FP is used in licence exempt mode, the CTS-FP owner does not need to have a subscription (2) with a CTS operator. In this case the frequency allocation to CTS usage is made directly by national authorities.
CTS-FP owner shall also enrol (4) at least one CTS-MS, which has a valid GSM subscription (5) with the GSM operator1.
In parallel, CTS-FP owner needs a subscription (1) with an access network operator in order establish communication over the network. This access network could be either a fixed network or a GSM network depending of CTS-FP capabilities. When the CTS-FP is connected to a GSM network, this GSM operator does not need to have any relation with the GSM operator1 who provides CTS frequencies (DPLMN).
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
4.3.2 CTS MS subscriber's role model
|
CTS MS subscriber's role model
The CTS-MS subscriber has a valid subscription (1) with a GSM operator who allows CTS operations. In case of roaming, the VPLMN shall confirm the authorisation to do CTS operations to this CTS-MS.
The CTS MS subscriber has agreement (2) with one CTS-FP owner that allows him to enrol on his CTS FP.
In order to enrol on a CTS-FP, a CTS-MS subscriber may need a subscription (3) with the CTS-operator who control (4) this CTS-FP. This CTS-operator may have an agreement (5) with the GSM-operator of this CTS-MS.
NOTE: this GSM operator may be different from the one who provides frequencies to the CTS-operator.
In order to have access to value added Fixed Mobile Convergence services (e.g. unified number), the CTS-MS subscriber needs a subscription (6) with a FMC service provider. These services and this subscription are outside of the scope of the GSM-CTS standard.
|
fcc930975597116eb21de958d20d3f3d
|
03.56
|
4.4 CTS Radio interface
|
The CTS radio interface is based on the use of a modified GSM radio interface as specified in [5].
The concept is to construct a modified GSM radio interface which requires no change of ME hardware, only software need be changed. The modified GSM radio interface shall (on both uplink and downlink) only cause minimal disturbance to the DPLMN.
In order to achieve this, three concepts have been adopted:
• A modified low power radio interface using GSM burst formats that cause limited disturbance to present GSM mobiles and infrastructure, see [5];
• Adaptive Frequency Allocation (AFA), see [5];
• Total Frequency Hopping (TFH), see [5].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.