hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8.1.1 Get Service State | Get Service State
These messages are used, to get information of the current Service State. An application may use the request of this function to ask for the information.
If the application asked for the GSM service "enable Service State indication", the indication of this function will be sent whenever the Service State changes.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
512
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
512
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
512
Diagnostic
word
0 no diagnostic
0x8101 no network
0x82xx reject cause from network according to GSM 04.08 [7]. In the field "xx" the reject cause value is coded.
Service status
word
0 no service
1 attempt to camp
2 emergency calls only
3 attempt to register
4 normal service
Roam status
word
This parameter is only valid, if the Service Status is "normal service"
0 the current PLMN is the Home PLMN
1 the current PLMN is a visited PLMN
PLMN
struct
If the Service Status is "normal service" this parameter contains the current PLMN according to GSM 04.08 [7]. In any other service status it is coded as an empty structure.
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
512 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8.1.2 RX Level and RX Quality | RX Level and RX Quality
These messages are used, to get information of the current receiving field strength and receiving quality.
An application can only request for this information. An automatic indication is not defined.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
513
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
513
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
513
RX level
word
RX level according to GSM 05.08 [11]
RX quality
word
RX quality according to GSM 05.08 [11]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
513 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8.1.3 Get SIM Present Info | Get SIM Presence Info
These messages are used, to get information if the SIM card is physically present and ready for access. An application may use the request of this function to ask for the information.
If the application asked for the GSM service "enable SIM presence indication", the indication of this function will be sent whenever the criterium changes.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
514
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
54
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
514
SIM present
word |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 UDI mode with ISO3309 HDLC framing. This is the default B1 protocol; | 1 analogue mode; |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 2 UDI mode without any additional framing; | 3 reserved, shall be rejected;
4 fax G3 mode; |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5 UDI mode with ISO3309 HDLC framing (for compatibility to existing applications); | 6 analogue mode (for compatibility to existing applications).
protocol 0 and 5 shall establish an UDI connection where layer two frames additionally are encapsulated by an HDLC framing structure with byte stuffing according to ISO 3309.
This sub parameter appears in parameter:
B protocol |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Transparent; | 2 SDLC [18];
3 LAPD according Q.921 [19] for D channel X.25;
4 T.30 [20] for fax group 3;
5 Point to Point Protocol (PPP [21] [22]);
6 Transparent (ignoring framing errors of B1 protocol).
This sub parameter appears in parameter:
B protocol |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Transparent. This is the default B3 protocol; | 1 T.90NL with compatibility to T.70NL according to T.90 Appendix II [23];
2 ISO 8208 [24] (X.25 DTE‑DTE); |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 3 X.25 DCE; | 4 T.30 [20] for fax group 3.
This sub parameter appears in parameter:
B protocol |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 4 For calls from the analogue network. (not necessary in GSM‑API) | 17 For calls within ISDN.
Non standard 64 kBit/s data applications
2 No checking of High Layer Compatibility information is provided. The application should verify that no High Layer Compatibility information is received.
Non standard 56 kBit/s data applications
8 No checking of High Layer Compatibility information is provided. The application should verify that no High Layer Compatibility information is received.
Fax Group 4 application
2 For calls from equipment which does not send High Layer Compatibility information. The application should verify that no High Layer Compatibility information is received.
18 For call from equipment which sends High Layer Compatibility information.
This information element appears in:
LISTEN_REQ |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 DTMF (Dual Tone Multi Frequency); | 256 GSM specific functions.
GSM specific functions identified by this facility selector are described in clause 7.
This information element appears in:
FACILITY_REQ
FACILITY_CONF
FACILITY_IND
FACILITY_RESP |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Parameter does not apply (coded as empty structure); | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 DTMF (Dual Tone Multi Frequency): | DTMF digits
byte array
Received characters, coded as IA5‑char. "0" to "9", "*", "#", "A", "B", "C" or "D"
This information element appears in:
FACILITY_IND |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Parameter does not apply (coded as structure with a length of 0); | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Parameter does not apply (coded as structure with a length of 0) | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Parameter does not apply (coded as structure with a length of 0) | This information element appears in:
FACILITY_RESP |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Accept the call; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Ignore the call; | 2 reject call, normal call clearing;
3 reject call, user busy;
4 reject call, requested circuit/channel not available;
5 reject call, facility rejected;
6 reject call, channel unacceptable;
7 reject call, incompatible destination;
8 reject call, destination out of order;
0x8xxx GSM‑API specific reason. Used only, if GSM services are requested;
0x83xx GSM cause from the network according to GSM 04.08 [7]. In the field "xx" the cause value received within a cause information element (octet 4) from the network is indicated;
0x84xx RP cause from the network according to GSM 04.11 [8]. In the field "xx" the cause value received within a RP cause information element from the network is indicated.
This information element appears in:
CONNECT_B3_RESP
CONNECT_RESP |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Register GSM support | The facility message parameter for this function are described below. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Register GSM Support (as described above); | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 2 Send Short Message; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 3 Receive Short Message; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 4 Receive Cell Broadcast Message; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5 In Call Modification; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 6 Read SIM Data; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7 Update SIM Data; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 8 Invalidate SIM File; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 9 Rehabilitate SIM File; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 10 Get SIM File Status; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 11 Handle PIN code; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 12 Get available PLMNs; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 13 Set PLMN mode; | 14 ‑ 255 reserved for basic GSM functions.
The facility message parameter for these basic functions are described in the following subclauses. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 256 Restrict SS information; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 257 Mobile originated SS transaction; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 258 Clear Mobile originated SS transaction; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 259 Receive SS message; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 260 Call Hold; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 261 Call Retrieve; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 262 Call Ussd; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 263 Receive Call related Facility; | 264 ‑ 511 reserved for GSM Supplementary Services functions; |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 512 Get Service State; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 513 Get RX Level and RX Quality; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 514 Get SIM Presence Info; | 515 ‑ ... reserved. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 SIM is not present | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 SIM is present and accessible | Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
54
Annex A (informative): GSM Supplementary Services Message flow
A.1 Restrict SS information
This Message Flow chart describes the flow for restriction of SS information.
Application MS Network
| facility_req(funct = 256) | |
| ------------------------------------------------------------->| |
| | |
| facility_conf(funct = 256) | |
| <-------------------------------------------------------------| |
| | |
| |
| SS Transaction may be started |
| |
| |
| facility_req(funct = 256) | |
| ------------------------------------------------------------->| |
| | |
| facility_cnf(funct = 256) | |
| <------------------------------------------------------------ | |
| | |
A.2 Mobile Originated SS transaction
This Message Flow chart describes the flow of GSM‑API and GSM layer 3 messages according to the GSM 04.80 [9] series as used for CF, CB etc.
Application MS Network
| facility_req(funct = 257) | register |
| ------------------------------------------------------------->| ------------------------------------------------------------> |
| | |
| facility_cnf(funct = 257) | |
| <------------------------------------------------------------ | |
| | |
| facility_ind(funct = 257) | release_compl. /facility |
| <------------------------------------------------------------ | <------------------------------------------------------------ |
| | |
| facility_resp(funct = 257) | |
| ------------------------------------------------------------->| |
A.3 Receive SS Message (Forward Check Indication)
This Message Flow Chart describes the spontaneous incoming SS message for Forward Check. The applications response is local.
Application MS Network
| | register |
| |<-------------------------------------------------------------|
| | |
| | release_compl. |
| |------------------------------------------------------------->|
| | |
| facility_ind(funct = 259) | |
| <------------------------------------------------------------ | |
| | |
| facility_resp(funct = 259) | |
| ------------------------------------------------------------->| |
A.4 Mobile originated USSD
This Message Flow Chart describes the Message Flow for mobile originated USSD according to GSM 04.90 [10].
Application MS Network
| facility_req(funct = 257) | register |
| ------------------------------------------------------------->| ------------------------------------------------------------> |
| | |
| facility_cnf(funct = 257) | |
| <------------------------------------------------------------ | |
Network requests further information (optional)
| facility_ind(funct = 259) | facility |
| <------------------------------------------------------------ | <------------------------------------------------------------ |
| | |
| facility_resp(funct = 259) | facility |
|-------------------------------------------------------------->|-------------------------------------------------------------->|
End of transaction
| facility_ind(funct = 257) | release_compl. /facility |
| <------------------------------------------------------------ | <------------------------------------------------------------ |
| | |
| facility_resp(funct = 257) | |
| ------------------------------------------------------------->| |
A.5 Mobile terminated USSD
This Message Flow Chart describes the message flow for mobile terminated USSD according to GSM 04.90 [10].
Application MS Network
| facility_ind (funct = 259) | register |
| <-------------------------------------------------------------| <--------------------------------------------------|
| | |
| facility_rsp(funct = 259) | |
| ------------------------------------------------------------> | --------------------------------------------------> |
Multiple Network request or notification (optional)
| facility_ind(funct = 259) | facility |
| <------------------------------------------------------------ | <--------------------------------------------------|
| | |
| facility_resp(funct = 259) | facility |
| ------------------------------------------------------------->| -------------------------------------------------->|
End of transaction
| | release_compl |
| | <--------------------------------------------------|
A.6 Call related USSD
Application MS Network
| facility_req (funct = 262) | cc_facility |
| ------------------------------------------------------------->| -------------------------------------------------->|
| | |
| facility_conf(funct = 262) | |
| ------------------------------------------------------------->| |
A.7 Call hold
This Message Flow chart describes the flow for call hold. The flow for call retrieve is equivalent.
Application MS Network
Call (identified by PLCI) is active
| facility_req(funct = 260, PLCI) | hold (TI) |
| ------------------------------------------------------------->| -------------------------------------------------->|
| | |
| facility_cnf(funct = 260, PLCI) | |
| <------------------------------------------------------------ | |
| | |
|facility_ind(funct = 264, Reason = 0 or cause) | hold ack. or hold rej. |
| <------------------------------------------------------------ | <--------------------------------------------------|
| | |
| facility_resp(funct = 260) | |
| ------------------------------------------------------------->| |
A.8 Receiving a Call related Facility
Application MS Network
| facility_ind (funct = 263) | cc_facility (except. charging info) |
| <-------------------------------------------------------------| <--------------------------------------------------|
| | |
| facility_resp (funct = 263) | |
| ------------------------------------------------------------->| |
Annex B (informative): Change history
SMG#
SPEC
PHASE
CR
VERS
NEW_VERS
SUBJECT
S20
07.08
2+
NEW
2.0.0
5.0.0
GSM API
s21
07.08
2+
A001
5.0.0
5.1.0
GSM API RP-Ack PDU
s24
07.08
R96
A002
5.1.0
5.2.0
Correction of references
History
Document history
December 1996
Public Enquiry PE 119: 1996‑12‑02 to 1997‑03‑28
February 1998
Vote V 9817: 1998-02-24 to 1998-04-24
May 1998
First Edition |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 1 Scope | The present document specifies the third version of the Integrated Services Digital Network (ISDN) - Global System for Mobile communications (GSM) Public Land Mobile Network (PLMN) signalling interface. The present document is applicable to the interconnection of PLMN and ISDN.
The ISUP interface defined is the trunk signalling interface between the PLMN and the ISDN. It is assumed that the interface between PLMN and ISDN can occur at any point in a national network, provided that the exchange in the national network has this ISDN-PLMN signalling interface.
This signalling interface is based on ISUP version 3 (as given in EN 300 356-1 [1] to EN 300 356-20 [19]). The functionality in the GSM system is based on GSM Phase 2+ Release 1998.
NOTE 1: Support of new functionality in the GSM system applicable for this interface may be included in subsequent versions of the present document or may be published as a new EN.
Connection types:
The following ISUP version 3 connection types can be supported:
- speech;
- 3,1 kHz audio;
- 64 kbit/s unrestricted;
- 64 kbit/s unrestricted preferred;
- 2 64 kbit/s unrestricted;
- 384 kbit/s unrestricted;
- 1 536 kbit/s unrestricted;
- 1 920 kbit/s unrestricted.
NOTE 2: 2 64 kbit/s, 384 kbit/s, 1 536 kbit/s, 1 920 kbit/s unrestricted and 64 kbit/s unrestricted preferred connection types are not supported by the GSM access, however the connection types may be used in order to support other access methods via the GSM network.
Supplementary services:
The following ISUP version 3 supplementary services can be supported:
- Calling Line Identification Presentation (CLIP)/
Calling Line Identification Restriction (CLIR);
- Connected Line Identification Presentation (COLP)/
Connected Line Identification Restriction (COLR);
- Terminal portability (TP);
- User-to-User Signalling (UUS);
- Closed User Group (CUG);
- Subaddressing (SUB);
- Malicious Call Identification (MCID);
- Conference call, add-on (CONF);
- Explicit Call Transfer (ECT);
- Call Forwarding Unconditional (CFU)/
Call Forwarding on Busy (CFB)/
Call Forwarding on No Reply (CFNR);
- Call Deflection (CD);
- Call Hold (HOLD);
- Call Waiting (CW);
- Completion of Calls to Busy Subscriber (CCBS);
- Completion of Calls on No Reply (CCNR);
- Three party (3PTY).
The support of supplementary services on this interface does not necessarily imply that the supplementary services are supported in one or the other of the networks interconnected.
The Direct Dialling In (DDI) supplementary service and Multiple Subscriber Number (MSN) supplementary service have no impact on this interface.
This interface can be used within national networks, however messages and parameters that are marked for national use in EN 300 356-1 [1] are not described in the present document. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 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] EN 300 356-1 (V3.2): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 1: Basic services [ITU‑T Recommendations Q.761 to Q.764 (1997), modified]".
[2] EN 300 356-2 (V3.2): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 2: ISDN supplementary services [ITU‑T Recommendation Q.730 (1997), modified]".
[3] EN 300 356-3 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 3: Calling Line Identification Presentation (CLIP) supplementary service [ITU‑T Recommendation Q.731, clause 3 (1993), modified]".
[4] EN 300 356-4 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 4: Calling Line Identification Restriction (CLIR) supplementary service [ITU‑T Recommendation Q.731, clause 4 (1993), modified]".
[5] EN 300 356-5 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 5: Connected Line Identification Presentation (COLP) supplementary service [ITU‑T Recommendation Q.731, clause 5 (1993), modified]".
[6] EN 300 356-6 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 6: Connected Line Identification Restriction (COLR) supplementary service [ITU‑T Recommendation Q.731, clause 6 (1993), modified]".
[7] EN 300 356-7 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 7: Terminal Portability (TP) supplementary service [ITU‑T Recommendation Q.733, clause 4 (1993), modified]".
[8] EN 300 356-8 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 8: User-to-User Signalling (UUS) supplementary service [ITU‑T Recommendation Q.737, clause 1 (1997), modified]".
[9] EN 300 356-9 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 9: Closed User Group (CUG) supplementary service [ITU‑T Recommendation Q.735, clause 1 (1993), modified]".
[10] EN 300 356-10 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 10: Subaddressing (SUB) supplementary service [ITU-T Recommendation Q.731, clause 8 (1992), modified]".
[11] EN 300 356-11 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 11: Malicious Call Identification (MCID) supplementary service [ITU‑T Recommendation Q.731, clause 7 (1997), modified]".
[12] EN 300 356-12 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 12: Conference call, add-on (CONF) supplementary service [ITU‑T Recommendation Q.734, clause 1 (1993), modified]".
[13] EN 300 356-14 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 14: Explicit Call Transfer (ECT) supplementary service [ITU-T Recommendation Q.732, clause 7 (1996), modified]".
[14] EN 300 356-15 (V3.2): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 15: Diversion supplementary services [ITU-T Recommendation Q.732, clauses 2 to 5 (1997), modified]".
[15] EN 300 356-16 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 16: Call Hold (HOLD) supplementary service [ITU‑T Recommendation Q.733, clause 2 (1993), modified]".
[16] EN 300 356-17 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 17: Call Waiting (CW) supplementary service [ITU-T Recommendation Q.733, clause 1 (1992), modified]".
[17] EN 300 356-18 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 18: Completion of Calls to Busy Subscriber (CCBS) supplementary service [ITU-T Recommendation Q.733, clause 3 (1997), modified]".
[18] EN 300 356-19 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 19: Three-Party (3PTY) supplementary service [ITU-T Recommendation Q.734, clause 2 (1996), modified]".
[19] EN 300 356-20 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 20: Completion of Calls on No Reply (CCNR) supplementary service".
[20] ITU‑T Recommendation Q.763 (1993): "Signalling System No. 7; ISDN user part formats and codes".
[21] GSM 03.50: "Digital cellular telecommunications system (Phase 2); Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system".
[22] GSM 03.81: "Digital cellular telecommunications system (Phase 2); Line identification supplementary services; Stage 2".
[23] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services; Stage 2".
[24] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services; Stage 2".
[25] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services; Stage 2".
[26] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Service Data (USSD) - Stage 2".
[27] GSM 03.93: "Digital cellular telecommunications system (Phase 2+); Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2".
[28] GSM 09.04: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Circuit Switched Public Data Network (CSPDN)".
[29] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
[30] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification".
[31] ETS 300 008: "Integrated Services Digital Network (ISDN); Signalling System No.7; Message Transfer Part (MTP) to support international interconnection".
[32] ITU-T Recommendation E.164 (1997): "The international public telecommunication numbering plan".
[33] GSM 03.96: "Digital cellular telecommunications system (Phase 2+); Name identification supplementary services; Stage 2".
[34] GSM 02.97: "Digital cellular telecommunications system (Phase 2+); Multiple Subscriber Profile (MSP) Phase 1; Service description, Stage 1". |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
3PTY Three-Party
ACM Address Complete Message
AoC Advice of Charge
CB Call Barring
CCBS Completion of Calls to Busy Subscriber
CCNR Completion of Calls on No Reply
CD Call Deflection
CFB Call Forwarding Busy
CFNR Call Forwarding No Reply
CFNRc Call Forwarding on Mobile Subscriber Not Reachable
CFU Call Forwarding Unconditional
CLIP Calling Line Identification Presentation
CLIR Calling Line Identification Restriction
COLP Connected Line Identification Presentation
COLR Connected Line Identification Restriction
CONF Conference calling
CPG Call Progress message
CUG Closed User Group
CW Call Waiting
DDI Direct Dialling In
ECT Explicit Call Transfer
GMSC Gateway MSC
GSM Global System for Mobile communications
HLC High Layer Compatibility
HLR Home Location Register
HOLD Call Hold
HPLMN Home Public Land Mobile Network
IAM Initial Address Message
ISDN Integrated Services Digital Network
ISUP ISDN User Part
MAP Mobile Application Part
MCID Malicious Call Identification
MPTY MultiParty
MS Mobile Station
MSC Mobile-service Switching Centre
MSISDN Mobile Station ISDN number
MSN Multiple Subscriber Number
MSRN Mobile Station Roaming Number
MTP Message Transfer Part
NI Network Indicator
PLMN Public Land Mobile Network
SUB Subaddressing
TP Terminal Portability
USSD Unstructured Supplementary Service Data
UUS User-to-User Signalling
VLR Visitor Location Register
VMSC Visited MSC |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 4 General principles | The gateway exchanges in both networks behave like international incoming or outgoing gateways in the relevant cases as described in EN 300 356-1 [1] to EN 300 356-20 [19], with the exceptions indicated within the present document. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5 Exceptions and clarifications for basic call | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.1 Formats and codes | The formats and codes specified in EN 300 356‑1 [1] with the exceptions and clarifications described in the table in annex D shall be applicable. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2 Basic call signalling procedures | The basic call procedures of EN 300 356-1 [1] apply with the following exceptions and clarifications. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.1 Signalling procedures for connection type allowing fallback | The gateway in the preceding network (PLMN or ISDN) shall perform fallback according to the procedures defined in EN 300 356-1 [1] when the succeeding network does not support fallback. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.2 Echo control procedure | The enhanced echo control procedure according to EN 300 356-1 [1] is not supported. Instead the simple echo control procedure described in EN 300 356-1 [1] is applicable.
According to GSM 03.50 [21], for speech and 3,1 kHz audio connection types an acoustic echo control shall be provided in the MS. The PLMN may provide electric echo control.
Echo control procedures are not applicable to 64 kbit/s, 2 64 kbit/s, 384 kbit/s, 1 536 kbit/s or 1 920 kbit/s unrestricted connection types.
Examples of echo control procedures are shown in annex E. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.3 Calls from the PLMN to the fixed network | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.3.1 Gateway in the PLMN | The Initial Address Message (IAM) sent by the gateway in the PLMN shall be coded taking into account the following exceptions and clarifications. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.3.1.1 Initial address message | Called party number
The called party number parameter may contain a Mobile Station Roaming Number (MSRN).
- Internal network number indicator:
0 if the MSRN is included;
1 otherwise.
The use of the internal network number indicator is an option.
User service information
The IAM shall always include a user service information parameter for calls to the fixed network when the ISDN access indicator is set to ISDN. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4 Calls from the fixed network to the PLMN | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.1 Gateway in the fixed network | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.1.1 Initial address message | Called party number
The called party number parameter contains the MSISDN or MSRN:
- Internal network number indicator:
0 if MSRN is included;
1 if MSISDN is included.
NOTE: The value of the internal network number indicator is set in the exchange having the relevant knowledge, and is passed transparently through the fixed network. Due to interworking with old signalling systems, an MSRN may be received with the internal network number indicator set to "0" or "1".
The use of the internal network number indicator is an option. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.2 Gateway in the PLMN | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.2.1 Address complete message | Significant delays may be incurred while interrogating location registers and while paging the terminating MS.
Due to the possible delays involved in setting up mobile calls, the PLMN needs to take special action to ensure that timer T7 (awaiting address complete timer) does not expire.
For this reason, whenever a call enters the PLMN, the PLMN shall run a timer, the PLMN/ISDN early Address Complete Message (ACM) timer (value 5 to 20 seconds). The timer is to be started after receiving the complete number. If the timer expires, an address complete message is sent. The PLMN shall stop the timer on sending a first backward message (address complete message or connect message).
The ACM shall contain the backward call indicators set to "0" except for:
Backward call indicators
- Charge indicator:
00 (no indication);
01 (no charge); or
10 (charge).
NOTE: The setting of the charge indicator is network specific.
- ISDN access indicator:
1 (ISDN) (preferred value, see table D.1).
- Echo control device indicator:
set according to echo control procedure described in annex E.
- ISDN user part indicator:
1 (ISDN user part used all the way).
Once the PLMN gateway has sent backwards one ACM message for a call (either because it has internally generated the ACM message or because it has transited an ACM message received from another node) it shall not send further ACM messages. Information in a subsequent ACM received in the PLMN gateway shall be mapped to a call progress message. The Event indicator in the CPG message is set according to the mapping rules defined in EN 300 356‑15 [14]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6 Exceptions and clarifications for supplementary services | Supplementary services are used according to EN 300 356‑1 [1] to EN 300 356‑20 [19]. When considering supplementary services, there exists a symmetry about this interface although the ISDN services may not be the same as the PLMN services. For each service supported by EN 300 356‑2 [2] to EN 300 356‑20 [19] or GSM 03.81 [22] to GSM 03.90 [26] and GSM 03.93 [27], the operation of the service in each direction needs to be considered. Supplementary services supported by the interface but not by one of the connected networks shall be handled according to EN 300 356‑1 [1] to EN 300 356‑20 [19], i.e. the gateway concerned acts like an international gateway.
Exceptions and clarifications for the coding are described in table D.1, unless otherwise stated. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1 Considerations on ISDN supplementary services | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1 Handling of number parameters related to supplementary services | The following text applies when referenced for the appropriate parameters.
Number parameters related to supplementary services sent across the ISDN-PLMN interface shall have the following coding of the nature of address indicator.
National significant number (000 0011) shall be used in the following cases:
- for a number allocated to a fixed access when the fixed access, the sending gateway and the receiving gateway are in the same country;
- for a number allocated to an MS registered in its HPLMN when the MS, the sending gateway and the receiving gateway are in the same country.
International number (000 0100) shall be used for all other cases.
If the gateway has to modify a parameter to satisfy the above requirement, it shall modify the nature of address indicator and modify the number in accordance with the new nature of address. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.1 Calling Line Identification Presentation/Restriction (CLIP/CLIR) supplementary services | EN 300 356‑3 [3] and EN 300 356‑4 [4] apply with the exceptions below:
Calling party number and generic number
Handling of calling party number and the appropriate generic number shall be made according to subclause 6.1.1.
For mobile originated calls the calling line identity is mapped into the calling party number parameter.
If the Generic Number parameter with a number qualifier set to "additional calling party number" is received in a PLMN then the calling party number parameter shall be discarded by the mobile access.
The PLMN shall not check for consistency in the screening indicators of the calling party number and the additional calling party number.
Actions at the Mobile gateway exchange when supporting transfer of calling party number and generic number parameters via MAP interfaces
The support of transfer of calling party number and generic number parameters via MAP interfaces shall have no impact on the actions to be performed at the mobile gateway exchange (GMSC) for the transfer of information relating to the CLIP and CLIR supplementary services on the ISUP interface.
The following actions shall be performed at the GMSC for the mapping of calling party number and generic number parameters to the MAP C interface:
The GMSC shall transfer neither the calling party number nor the generic number parameter to the MAP interface if the presentation indicator of the received calling party number parameter is set to "address not available".
The GMSC shall convert the calling party number conveyed in the calling party number parameter to an international number (if necessary) and set the nature of address indicator to "international number". The address presentation restricted indicator and the screening indicator shall be transferred transparently.
If the generic number parameter is received and its number qualifier indicates "additional calling party number" and the numbering plan indicator is coded "ISDN (Telephony) numbering plan (ITU-T Recommendation E.164 [32])", then the generic number parameter shall be treated in the same manner as the calling party number parameter.
The generic number parameter shall not be mapped if its number qualifier indicates "additional calling party number" and the screening indicator is coded "user provided, verified and failed".
The address presentation restricted indicator of the generic number parameter shall be set to the same value as the address presentation restricted indicator of the calling party number parameter ("presentation restricted" or "presentation allowed"). |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.2 Connected Line Identification Presentation/Restriction (COLP/COLR) supplementary services | EN 300 356‑5 [5] and EN 300 356‑6 [6] apply with the exceptions below:
Connected number and generic number
Handling of connected number and the appropriate generic number shall be made according to subclause 6.1.1. For mobile terminated calls the connected line identity is to be mapped into the connected number parameter. If the generic number parameter with a number qualifier set to "additional connected number" is received in a PLMN then the connected number parameter shall be discarded by the mobile access. The PLMN shall not check for consistency in the screening indicators of the connected number and the additional connected number. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.3 Terminal Portability (TP) supplementary service | EN 300 356‑7 [7] applies.
NOTE: Terminal Portability is supported by the protocol, however the service is not provided for the GSM access. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.4 User-to-User Signalling (UUS) supplementary service | EN 300 356‑8 [8] applies.
NOTE: The maximum length of the user-user parameter of the setup message at the GSM access is restricted to 35 octets. When a GSM PLMN receives a longer user-to-user information element in the IAM message the User-to-user information element will be discarded without indication. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.5 Closed User Group (CUG) supplementary service | EN 300 356‑9 [9] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.6 Subaddressing (SUB) supplementary service | EN 300 356‑10 [10] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.7 Malicious Call Identification (MCID) supplementary service | EN 300 356‑11 [11] applies with the exceptions below:
Calling party number and generic number
Handling of calling party number and the appropriate generic number shall be made according to subclause 6.1.1.
NOTE: Malicious Call Identification is supported by the protocol, however the service is not provided for the GSM access. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.8 Conference call, add-on (CONF) supplementary service | EN 300 356‑12 [12] applies with the exception below:
Notification messages may be sent from the ISDN to the PLMN according to GSM 03.84 [23].
NOTE: Conference call is supported by the protocol, however the service is not provided for the GSM access. The corresponding service in GSM is the multiparty service defined by the GSM standards. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.9 Explicit Call Transfer (ECT) supplementary service | EN 300 356‑14 [13] applies with the exceptions below:
Call Transfer Number
Handling of call transfer number shall be made according to subclause 6.1.1. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.10 Diversion supplementary services (Call Forwarding Unconditional (CFU)/Call Forwarding on Busy (CFB)/Call Forwarding on No Reply (CFNR)/Call Deflection (CD)) | EN 300 356‑15 [14] applies with the exceptions below:
Original called number, redirecting number and redirection number
Handling of original called number, redirecting number and redirection number shall be made according to subclause 6.1.1. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.11 Call Hold (HOLD) supplementary service | EN 300 356‑16 [15] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.12 Call Waiting (CW) supplementary service | EN 300 356‑17 [16] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.13 Completion of Calls to Busy Subscriber (CCBS) supplementary service | EN 300 356‑18 [17] applies with the exception below:
If the GMSC has the knowledge that the CCBS service is not supported the diagnostics in the Release message will be set to indicate "CCBS not possible" (for cause values 17 or 34). |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.14 Completion of Calls on No Reply (CCNR) supplementary service | EN 300 356‑20 [19] applies with the exception below:
NOTE: Completion of Calls on No Reply is supported by the protocol, however the service is not provided for the GSM access. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.15 Three party (3PTY) supplementary service | EN 300 356‑19 [18] applies with the exceptions below:
Notification messages may be sent from the ISDN to the PLMN according to GSM 03.84 [23].
NOTE: Three party is supported by the protocol, however the service is not provided for the GSM access. The 3PTY service can be a part of the multiparty service as defined by the GSM standards. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2 Considerations on GSM unique supplementary services | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.1 Call Forwarding on Mobile Subscriber Not Reachable (CFNRc) supplementary service | EN 300 356‑15 [14] applies with the exceptions below:
Original Called Number, Redirecting Number and Redirection Number
Handling of original called number, redirecting number and redirection number shall be made according to subclause 6.1.1. For calls that have been redirected (because of mobile subscriber not reachable) via the GSM-system, the Redirecting Reason shall be set to Mobile Subscriber Not Reachable. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.2 Advice of Charge (AoC) supplementary service | No impact on the ISDN-PLMN- interface. The service is described in GSM 03.86 [24]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.3 Call Barring (CB) supplementary service | No impact on the ISDN-PLMN interface. The service is described in GSM 03.88 [25]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.4 Unstructured Supplementary Service Data (USSD) | No impact on the ISDN-PLMN interface. The service is described in GSM 03.90 [26]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.5 Calling Name Presentation supplementary service (CNAP) | No impact on the ISDN-PLMN interface. The service is described in GSM 03.96 [33]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.6 Multiple Subscriber Profile (MSP) supplementary service | No impact on the ISDN-PLMN interface. The service is described in GSM 02.97 [34]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.7 Multi Party (MPTY) supplementary service | The service is described in ETS 300 545 [26].
Notification messages of the MPTY supplementary service may be mapped on the ISDN-PLMN interface into notification messages of the ISDN Conference call (CONF) supplementary service defined in EN 300 356-12 [12]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 7 Message Transfer Part (MTP) protocol requirements | The Message Transfer Part (MTP) protocol shall conform to the requirements in ETS 300 008 [31] with the appropriate value for the Network Indicator (NI).
It is preferred that NI value 10 (national network) is used within GSM networks as in the fixed national network. Based on national agreement, any NI value may be applied on the interface between GSM networks and the fixed networks.
Annex A (informative):
Considerations on teleservices
A.1 Relation between ISDN teleservices and GSM teleservices
Teleservices may be identified on the ISDN-PLMN interface in the User Teleservice Information parameter. High Layer Compatibility (HLC) information elements are passed transparently in the access transport parameter. Support of teleservices is an end-to-end aspect. However, the relationships between some ISDN teleservices and GSM teleservices are listed for information.
Table A.1: Relationship between ISDN teleservices and GSM teleservices
ISDN teleservices
GSM teleservices
Telephony
Telephony, Emergency call
Facsimile Group 2/3
Automatic facsimile group 3
Facsimile Group 4 Class 1
Not used
Teletex
Not used
Not used
Alternate speech and facsimile group 3
Not used
SMS, Point-To-Point, Mobile Originated
Not used
SMS, Point-To-Point, Mobile Terminated
Not used
SMS Cell Broadcast
Videotex
Not used
Telex
Not used
Message Handler System
Not used
Videotelephony
Not used
Videoconferencing
Not used
Annex B (informative):
Considerations on bearer services
The mapping between parameters in the GSM call set up request message and the ISDN call set up request message is described in GSM 09.04 [28] to GSM 09.07 [29].
Annex C (informative):
Mapping of parameters between ISUP and MAP
Mapping of parameters between ISUP and MAP will take place for Mobile terminating calls where the MSC (acting as gateway MSC) has to interrogate the home location register in order to obtain routeing information (the HLR needs to retrieve the routeing information from the VLR). The interface between MSC and VLR is an internal interface, mapping of parameters on this interface are not described in this specification.
C.1 Mapping of parameters from IAM to MAP_SEND_ROUTING_INFORMATION req.
Table C.1: Mapping of parameters from IAM to MAP_SEND_ROUTING_INFORMATION req
IAM
MAP_SEND_ROUTING_INFORMATION req.
Called Party Number
MSISDN
Closed user group interlock code
CUG Interlock
Optional forward call indicators
- Closed user group indicator
CUG Outgoing Access
Redirection information
- Redirection counter
Number of Forwarding
Access Transport/User Service Information
Network signal information
NOTE: Mapping of Network signal information is described in GSM 09.02 [30].
C.2 Mapping of parameters from MAP_SEND_ROUTING_INFORMATION rsp. to IAM
Table C.2: Mapping of parameters from MAP_SEND_ROUTING_INFORMATION rsp. to IAM
MAP_SEND_ROUTING_INFORMATION rsp.
IAM
CUG Interlock
Closed user group interlock code
CUG Outgoing Access
Optional forward call indicators
- Closed user group indicator
MSRN (note 1)
Called Party Number
(if no call forwarding is performed)
Forwarding Data (note 2)
- ForwardedToNumber
- ForwardedToSubaddress
- ForwardingOptions
notification to forwarding party
forwarding reason
Called Party Number
Access Transport
- Called Party Subaddress
Redirection information
NOTE 1: This parameter will not be present if the parameter Forwarding Data is returned.
NOTE 2: This parameter will not be present if the MSRN is returned.
Annex D (informative):
Formats and codes
D.1 Unrecognized messages and parameters
The receipt of unrecognized messages and parameters are handled using standard message and parameter compatibility rules defined in EN 300 356-1 [1].
D.2 Exceptions and clarifications to clause 3 of ITU‑T Recommendation Q.763 as modified by EN 300 356-1
Table D.1: Exceptions and clarifications to clause 3 of ITU‑T Recommendation Q.763 [20]
as modified by EN 300 356‑1 [1]
Q.763 [20]
clause
Title
Remarks
3.5
Backward call indicators
Bit M: terminating PLMN subscribers to be considered as ISDN terminations (this is the preferred situation, but other coding may be agreed between the PLMN and ISDN operators).
3.12
Cause indicator
For the coding of the location field, the exchanges at the interface between the mobile and fixed ISDN networks need not to be considered as an international interface.
The appropriate support of cause 20 within the originating network (e.g. provision of an announcement) is a matter of the network provider.
3.23
Forward call indicators
Bit A: the ISDN-PLMN interface can be an interface within the national network, and then the national/international indicator to be passed on transparently on this interface. It is assumed that the national/international indicator is set to:
1 = "call to be treated as an international call"
for incoming international calls in an international gateway exchange in the fixed or mobile network, and that otherwise it is coded:
0 = "call to be treated as a national call".
Bit I: originating PLMN subscribers to be considered as ISDN terminations (this is the preferred situation, but other codings may be agreed between the PLMN and ISDN operators).
3.45
Redirection information
The redirection counter is incremented when the call is forwarded, however the mechanism for the allocation of a Mobile Station Roaming Number (MSRN) is not to be considered as an instance of call forwarding.
Annex E (informative):
Examples of echo control procedures
E.1 Outgoing call in a Mobile-service Switching Centre (MSC)
If the requested bearer is "speech" or "3,1 kHz", the echo control device indicator is set to "1" (outgoing included) in the IAM sent by the MSC.
An incoming half echo control device is "reserved" on the outgoing circuit of the MSC.
If the backward call indicators parameter received in the ACM indicates that an incoming half echo control device is included, the "reserved" incoming half echo control device of the outgoing circuit of the MSC is disabled.
If the backward call indicators parameter received in the ACM indicates that an incoming half echo control device is not included, the "reserved" incoming half echo control device of the outgoing circuit of the MSC is enabled.
If the requested bearer is "64 kbit/s unrestricted", the echo control device indicator is set to "0" (outgoing not included). No echo devices are reserved.
E.2 Incoming call in the MSC
1) If the nature of the connection indicators parameter indicates that an outgoing half echo control device is included, any outgoing half echo control device on the incoming circuit of the MSC is disabled.
- If the MSC is a Visited Mobile-service Switching Centre (VMSC), the backward call indicators parameter sent in the ACM indicates that an incoming half echo control device is enabled.
- If the MSC is a Gateway Mobile-service Switching Centre (GMSC) or in case of call forwarding, the incoming half echo control device of the outgoing circuit is "reserved" and the echo control device indicator sent in the IAM is passed on:
- if the backward call indicators parameter received in the ACM indicates that an incoming half echo control device is included the incoming half echo control device of the outgoing circuit of the MSC is disabled;
- if the backward call indicators parameter received in the ACM indicates that an incoming half echo control device is not included the incoming half echo control device of the MSC is enabled. The backward call indicators in ACM are changed accordingly.
2) If the nature of the connection indicators parameter indicates that an outgoing half echo control device is not included, the outgoing half echo control device on the incoming circuit of the MSC is reserved.
- If the MSC is a VMSC, the outgoing half echo control device is enabled and the backward call indicators parameter sent in the ACM indicates that an incoming half echo control device is included.
- If the MSC is a GMSC or if the call is to be forwarded and the MSC knows that an outgoing half echo control device is necessary (e.g. called MS, forwarding to an international destination):
- the outgoing half echo control device on the incoming circuit is enabled and the echo control parameter sent in the IAM indicates "outgoing half echo control device included";
- the incoming half echo control device of the outgoing circuit is "reserved";
- if the backward call indicators parameter received in the ACM indicates that an incoming half echo control device is included the incoming half echo control device of the outgoing circuit of the MSC is disabled. The backward call indicators in ACM are passed on unchanged;
- if the backward call indicators parameter received in the ACM indicates that an incoming half echo control device is not included the incoming half echo control device of the MSC is enabled. The backward call indicators in ACM are changed accordingly.
- If the MSC is a GMSC or if the call is to be forwarded and the MSC knows that an outgoing half echo control device is not necessary:
- the outgoing half echo control device on the incoming circuit is disabled and the echo control parameter in the IAM is passed on;
- the incoming half echo control device on the outgoing circuit is disabled.
E.3 Examples of echo control procedure
The following additional notations are used in figures E.1 to E.13:
G Gateway in the fixed network
(o.i) outgoing half echo control device included
(o.ni) outgoing half echo control device not included
(i.i) incoming half echo control device included
(i.ni) incoming half echo control device not included
(*) echo control device "reserved"
* echo control device enabled
x echo control device disabled
i incoming half echo control device
o outgoing half echo control device
E.3.1 Call from a mobile station to a mobile station via the fixed network
Figure E.1
E.3.2 Call from a mobile station to fixed network with no echo control device
Figure E.2
E.3.3 Call from a mobile station to fixed network with echo control device
Figure E.3
E.3.4 Call from fixed network with no echo control device to a mobile station roaming in a PLMN of another country
Figure E.4
E.3.5 Call from fixed network with echo control device to a mobile station roaming in a PLMN of another country
Figure E.5
E.3.6 Call from fixed network with no echo control device to a mobile station
Figure E.6
E.3.7 Call from fixed network with echo control device to a mobile station
Figure E.7
E.3.8 Call forwarded by the VMSC
Figure E.8
E.3.9 Call forwarded by the VMSC to the fixed network with no echo control device
Figure E.9
E.3.10 Call with no outgoing echo control device included in a preceding exchange forwarded by the VMSC to the fixed network with no echo control device in the terminating network. The VMSC knows that an outgoing half echo control device is not necessary
Figure E.10
E.3.11 Call with no outgoing echo control device included in a preceding exchange forwarded by the VMSC to the fixed network with echo control device in the terminating network. The VMSC knows that an outgoing half echo control device is not necessary
Figure E.11
E.3.12 Call with no outgoing echo control device included in a preceding exchange forwarded by the VMSC to the fixed network with no echo control device in the terminating network. The VMSC knows that an outgoing half echo control device is necessary
Figure E.12
E.3.13 Call with no outgoing echo control device included in a preceding exchange forwarded by the VMSC to the fixed network with echo control device in the terminating network. The VMSC knows that an outgoing half echo control device is necessary
Figure E.13
Bibliography
The following material, though not specifically referenced in the body of the present document (or not publicly available), gives supporting information.
- ETS 300 121 (1992): "Integrated Services Digital Network (ISDN); Application of the ISDN User Part (ISUP) of CCITT Signalling System No.7 for international ISDN interconnections (ISUP version 1)".
- GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services; Stage 2".
- GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2".
- GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services; Stage 2".
- GSM 09.05: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Packet Switched Public Data Network (PSPDN) for Packet Assembly/Disassembly (PAD) facility access".
- GSM 09.06: "Digital cellular telecommunications system (Phase 2+); Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services".
History
Document history
V7.0.2
September 1999
Public Enquiry PE 9957: 1999-09-01 to 1999-12-31
V7.1.0
April 2000 |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 1 Scope | The purpose of this document is to describe the project plan for the Mobile Station Execution Environment (MEXE) work item standardisation.
This document is a ‘living document’ and permanently updated by PT SMG. Proposals for change shall be forwarded to PT SMG, where the latest version can be obtained any time. The MEXE specification rapporteurs should make sure that this document can always reflects the latest status of work. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 1.1 References | |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 1.2 Abbreviations | MNCRS WG4 Mobile Network Computer Reference Standard Working Group 4 |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2 General Considerations for MEXE | |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.1 Support tools for specification work | ETSI FTP Server (docboc.etsi.fr or docbox.etsi.org):
SMG4 /../SMG/SMG4/WI_mexe .
Email distribution list: SMG4_mexe@list.etsi.fr (Subscription for contributors from SMG1, SMG4, SMG9 and SMG10, instructions on how to subscribe in Tdoc SMG4 97p488) |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2 Decisions at SMG | Workitem Rapporteur
John Candish (NORTEL); email: jfc@nortel.com |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2.1 SMG#22 | SMG#22 agreed to establish a small project team that elaborated a workitem description backed by a feasibility study on mobile station application execution environment. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2.2 SMG#23 | SMG#23 agreed the workitem description and the feasibility study conditionally. The condition is that the relationship between the SMG work and the WAP consortium can be clarified before WAP is taken into account. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2.3 SMG#24 (bis) | SMG4 is mandated to communicate directly to MNCRS and WAP, provided that the WAP consortium is open for new members. A LS had been sent to WAP from SMG#24bis, although some concerns were expressed afterwards. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2.4 SMG#25 | It was noted that preceding SMG's had agreed co-operation with WAP under condition of open participation rights for interested parties.
SMG#25 asked SMG4 to organise a technical review meeting of the WAP papers. which was convened as a MExE Workshop on 27-28 April in Sophia Antipolis hosted by ETSI. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 3 Co-operation with other groups |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.