hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1 Facility message parameter | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.1 Send Short Messages | Send Short Messages
The application uses this message to send a TPDU, which contains a Short Message (SMS‑SUBMIT‑REQUEST) or a SMS‑COMMAND. The destined Service Centre is defined by the Service Centre Address.
The TP Message Reference of the Short Message which is placed within the TPDU is handled by GSM‑API. To handle subsequent messages related to the delivered Short Message, this reference is given to the application within the Confirmation.
The result of the delivery is indicated by the parameter Reason of the subsequent FACILITY_IND (function = 2).
Reason = 0: Sending the Short Message/SMS Command has been successful
Reason = 0x81xx: Sending the Short Message/SMS Command has been unsuccessful because of a GSM specific local reason given in the field "xx"
Reason = 0x84xx Sending the Short Message/SMS Command has been unsuccessful because of a network related error. The cause value (RP‑cause according to GSM 04.11 [8]) is given in the field "xx"
In case of a successful submission, the service centre might provide the SMS-SUBMIT-REPORT RP-ACK according to GSM 03.40 [5]. This will be presented in the parameter SMS-Data of the FACILITY_IND (function = 2).
In case of an unsuccessful submission, the service centre might provide the TP-Failure Cause according to GSM 03.40 [5]. This will be presented in the parameter SMS-Data of the FACILITY_IND (function = 2).
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
2
SMS Data
struct
The parameter has the following structure:
struct: TS Service Centre Address coded according to GSM 04.11 [8]
TPDU: The TPDU is coded as an array of octets. (Note 1)
NOTE 1: The length of the TPDU can be calculated as:
Length of struct "SMS Data" ‑ (Length of struct "TS Service Centre Address" + 1)
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
2
TP Message Reference
word
Coded according to GSM 03.40 [5]
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
2
TP Message Reference
word
Coded according to GSM 03.40 [5]
Reason
word
0 successful delivery
0x81xx: unsuccessful delivery local reason presented in "xx"
0x84xx unsuccessful delivery RP cause according to GSM 04.11 [8] is given in "xx"
SMS Data
struct
This optional parameter contains the following information if it is provided by the service centre:
In case of a successful submission the SMS-SUBMIT-REPORT RP-ACK according to GSM 03.40 [5].
In case of an unsuccessful submit the TP-Failure Cause according to GSM 03.40 [5].
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
2 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.2 Receive Short Message | Receive Short Message
This Message is used to handle delivered short messages and SMS‑STATUS‑REPORTS.
If the application has selected the GSM service "Short Message Received Indication", only the class and the storage location of the message will be indicated.
If the application has enabled the GSM service "Transfer of received Short Message to the application", the indication will additionally contain the SMS data.
NOTE 1: The content of a class 0 Short Message and a SMS‑STATUS‑REPORT will always be forwarded to the application, if either of the above mentioned GSM services is selected.
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
3
SMS storage
struct
octet 0: Bit mask to monitor memory status
[0]: SIM storage full. If this bit is set, the SIM storage is full or not available
[1]: Manufacturer specific storage full If this bit is set, the manufacturer specific storage is full or not available
octet 1: This octet describes the handling of the received short message.
0 rejected because SIM SMS storage full
1 rejected because memory capacity exceeded
2 not stored (class 0 Short Message)
3 stored on the SIM the record number in which the Short Message is stored is given in the subsequent octet. (record numb according to GSM 11.11 [13])
4 stored manufacturer specific the location of the storage is given in the subsequent octets
SMS data
struct
Contains:
struct: TS Service Centre Address coded according to GSM 04.11 [8]
TPDU: The TPDU is coded as an array of octets. (Note 1)
NOTE 2: The length of the TPDU can be calculated as:
Length of struct "SMS Data" ‑ (Length of struct "TS Service Centre Address" + 1)
If the application has selected the GSM service "Short Message Received Acknowledge", the FACILITY_RESP (function = 3) will trigger the SMS-DELIVER-REPORT to be sent to the service centre. In this case the application has to take care not to delay the response for longer then the RP-ACK time-out, as specified in GSM 04.08 [7]. The application might include the SMS-DELIVER-REPORT RP-ACK in the parameter SMS-Data of the FACILITY_RESP (function = 3).
If the application has not selected the GSM service "Short Message Received Acknowledge", the SMS-DELIVER-REPORT will be handled below the GSM-API. The parameter SMS-Data shall be coded as an empty struct in this case.
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
3
SMS-Data
struct
This optional parameter might be used by the application to send the SMS-DELIVER-REPORT RP-ACK to the service centre, if the GSM service "Short Message Received Acknowledge" has been selected. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.3 Receive Cell Broadcast Messages | Cell Broadcast Messages
These message are used to handle the Cell Broadcast service.
With the request, the application can restrict the receipt of Cell Broadcast messages to a limited number of Message Identifiers (parameter MI list) or/and Data coding schemes (parameter DCS list).
The indication is sent for each page of a Cell Broadcast Message. The message identifiers and the data coding scheme are coded according to GSM 03.38 [4]
The maximum length of the list of Message Identifiers is manufacturer specific. It will be given in the confirmation message of the request for GSM support.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
4
MI list
struct
word: 1. Message identifier
:
word: n. Message identifier
DCS list
struct
octet: 1. data coding scheme
:
octet: n. data coding scheme
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
4
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
4
CBS data
struct
Contains one page of CB message coded according to GSM 03.41 [6]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
4 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.4 In Call Modification | In Call Modification
The application uses this message to send a Modify to the network. The CIP value is used, to create the GSM HLC and BC to be sent to the Network. The CIP value can be 16(Telephony) or 17(Fax).
The In Call Modification Indication can be initiated by:
- The result of a modify request, which can be a modify complete (Reason = 0) or a modify reject (Reason = GSM specific cause), or
- A modify initiated by the network (Reason = 0).
The In Call Modification Response contains:
- A local response to a modify complete or modify reject coming from the network (Rejection = 0, CIP=0, LLC=empty struct);
- A modify complete (Rejection = 0) or a modify reject (Rejection = GSM specific cause) as a response to a modify previously sent by the network.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
5
CIP Value
word
Compatibility Information Profile
LLC
struct
Low Layer Compatibility
Reverse Call Setup
struct
optional octet, coded according to GSM 04.08 [7]
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
5
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
5
Reason
word
GSM specific reason
CIP Value
word
Compatibility Information Profile
LLC
struct
Low Layer Compatibility
Reverse Call Setup
struct
optional octet, coded according to GSM 04.08 [7]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
5
Reject
word
GSM specific reject
CIP Value
word
Compatibility Information Profile
LLC
struct
Low Layer Compatibility
NOTE: In case of a successful In Call Modification, the application shall use the Profile B message SELECT_B_PROTOCOL_REQ to change the B protocol after receiving the indication (in both cases mobile originated/terminated modify before sending the response. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.5 Read SIM Data | Read SIM Data
The SIM data consists of transparent, linear fixed and cyclic files. GSM‑API offers a similar way to access all these types of files. Within the request, the application gives the identifier of the file. An immediate local confirmation is given and the result is sent within one or several indications. This indication contains the data of the requested file or an error cause given by the SIM. (e.g. "no CHV initialized" or "pattern not found".).
In case of a linear fixed or cyclic file, the application has two choices to read.
1) If the parameter read criterium is empty (empty struct), the whole file is read.
As the result each record is sent in one indication. The SIM More Data identifier is 0 for the last indication (no more data is sent).
2) The application may give the record number in the parameter read criterium.
The record number is coded in one byte, 1 £ record number £ 255 (according to GSM 11.11 [13]).
In this case the requested record is sent in one indication and the SIM More Data identifier is 0.
In case of a linear fixed file the application has a third choice to read, by giving a pattern in the parameter read criterium. The pattern is coded as a sequence of bytes with maximum length = 16 as defined in GSM 11.11 [13]. GSM‑API will send one indication per record which starts with the pattern. The last indication is identified by the SIM More Data identifier = 0. If no record is found, this is treated like an error given by the SIM as described above.
In cases of a linear fixed or cyclic file, the resulting indication contains the record number of the read record.
In case of a transparent file the whole data of the file is given within one indication. The parameter read criterium has no meaning and shall be coded as an empty struct. The parameter record number of the indication shall be "0" in case of a transparent file.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
6
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF_ID
word
elementary file, according to GSM 11.11 [13]
read criterium
struct
1. case
empty struct => read all records of a file
2. case
Byte 0 = 1 read one record given by the record number
Byte 1: 1 £ record number £ 255
3. case
Byte 0 = 2 read records which starts with pattern
Byte 1 1 £ length of pattern £ 16
Byte2 pattern
:
Byte n
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
6
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
word
elementary file, according to GSM 11.11 [13]
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
6
SIM_SW1
word
first status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_SW2
word
second status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
word
elementary file, according to GSM 11.11 [13]
SIM More Data
word
0: no more data available
all other values: next data will follow
record number
word
1. linear fixed or cyclic file
the parameter contains in the low byte the number of the read record
2. transparent file
record number = "0"
SIM Data
struct
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
6 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.6 Update SIM Data | Update SIM Data
Using these messages, an application can update all types if files, (transparent linear fixed or cyclic files) of the SIM.
In case of a linear fixed file, the application sends one request per record. The request contains the record number which may vary from 1 to 255 (according to GSM 11.11 [13]). When a sequence of records of a linear fixed file is updated (e.g. the whole file is updated), the application should update the records in order of the record number to make an optimized update possible.
In case of a transparent‑ or a cyclic file, the record number shall be "0".
For each request, the application receives a local confirmation and an indication which contains the result given by the SIM. The application has to wait for this indication before it will sent new data to the SIM (next record or new file).
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
7
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
word
elementary file, according to GSM 11.11 [13]
record number
word
1. linear fixed of cyclic file
the parameter contains in the low byte the number of the record
2. transparent file
record number = "0"
SIM Data
struct
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
7
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
word
elementary file, according to GSM 11.11 [13]
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
7
SIM_SW1
word
first status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_SW2
word
second status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
word
elementary file, according to GSM 11.11 [13]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
7 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.7 Invalidate SIM file | Invalidate SIM file
These messages are used to invalidate a file of the SIM according to GSM 11.11 [13]. After the request, the application receives a local confirmation. The result of the SIM is given in the subsequent indication for this function.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
8
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF_ID
word
elementary file, according to GSM 11.11 [13]
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
8
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
word
elementary file, according to GSM 11.11 [13]
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
8
SIM_SW1
word
first status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_SW2
word
second status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
word
elementary file, according to GSM 11.11 [13]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
8 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.8 Rehabilitate SIM file | Rehabilitate SIM file
These messages are used to rehabilitate a file of the SIM according to GSM 11.11 [13]. After the request, the application receives a local confirmation. The result of the SIM is given in the subsequent indication for this function.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
9
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF_ID
word
elementary file, according to GSM 11.11 [13]
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
9
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
word
elementary file, according to GSM 11.11 [13]
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
9
SIM_SW1
word
first status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_SW2
word
second status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
word
elementary file, according to GSM 11.11 [13]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
9 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.9 Get SIM File Status | Get SIM File Status
These messages are used to get the status and additional information of a file.
If the status of a dedicated file or of the main file is requested, the parameter SIM_EF_ID is empty.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
10
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF_ID
struct
This parameter contains the following subparameter:
word elementary file identifier according to GSM 11.11 [13]
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
10
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
struct
This parameter contains the following subparameter:
word elementary file identifier according to GSM 11.11 [13]
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
10
SIM_SW1
word
first status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_SW2
word
second status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_DF ID
word
directory, according to GSM 11.11 [13]
SIM_EF ID
struct
This parameter contains the following subparameter:
word elementary file identifier according to GSM 11.11 [13]
status info
struct
This parameter contains the status information as defined in GSM 11.11 [13]
length of alpha identifier
struct
This optional parameter contains the length of the alpha identifier which is according to GSM 11.11 [13] defined for some elementary files.
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
10 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.10 Handle PIN code | Handle PIN code
The request to handle the PIN code offers different operations. For each operation, dependent of the value of parameter SIM PINOperation the other parameter have different meaning (all coded according to GSM 11.11 [13]):
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
11
SIM PINOperation
word
1..8, see below
SIM PINCode
struct
see below
SIM PINCodeAdd
struct
see below
SIM PINOperation
SIM PINCode:
SIM PINCodeAdd:
1: verify CHV1
CHV1
not used
2: verify CHV2
CHV2
not used
3: change CHV1
old CHV1
new CHV1
4: change CHV2
old CHV2
new CHV2
5: disable CHV1
CHV1
not used
6: enable CHV1
CHV1
not used
7: unblock CHV1
unblock CHV
new CHV1
8: unblock CHV2
unblock CHV
new CHV2
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
11
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
11
SIM_SW1
word
first status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
SIM_SW2
word
second status word, given by the SIM as a response to a command.
High byte: 0
low byte: according to GSM 11.11 [13]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
11 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.11 Get available PLMNs | Get available PLMNs
With these messages the application requests a list of currently available GSM networks (PLMNs). For each PLMN additional information is given (if the PLMN is forbidden, allowed or if it is the PLMN the MS is currently registered on).
In case of a rejection of the available PLMN request, this will be indicated in parameter Reason of the corresponding Indication.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
12
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
12
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
12
Reason
word
GSM specific reason
PLMN List
struct
4 octets, may be repeated.
Octet 0: Bit field, coded as follows:
[0]: PLMN is allowed
[1]: PLMN is the PLMN, which the MS is actually registered on
[2‑15]: reserved
Octet 1..3: PLMN coded according to GSM 04.08 [7]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
12 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6.1.12 Set PLMN Mode | Set PLMN Mode
The application uses this message to select the mode of registration to a network. If the PLMN is not given, automatic mode is selected. In this case, the MS tries to register:
1) to the home PLMN. If this is not possible;
2) to one of the selected PLMN (given on the SIM). If this is not possible;
3) to another available PLMN.
If the NEW_PLMN is present, the MS is in manual mode. It tries only to register to the given PLMN. The default mode is not part of this specification.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
13
New PLMN
struct
PLMN coded according to GSM 04.08 [7], or empty struct
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
13
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
13
Reason
word
GSM specific reason
New PLMN
struct
PLMN coded according to GSM 04.08 [7]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
13 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7 GSM Supplementary Service functions | This subclause describes the extension of ETS 300 838 [14] profile B (COMMON‑ISDN‑API) to control GSM Supplementary Services.
The ASN1 coder/decoder is placed below the GSM‑API. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.1 Overview | The extension for GSM Supplementary services offers the control of call independent and call related supplementary services. Only one SS transaction can take place in each direction at the same time. Whenever an application will try to start a second Mobile Originated SS transaction, it will be rejected with the info value = 0x1107 "internal busy condition". Thus no transaction identifier is needed.
Functions defined for GSM‑API (Facility selector 256) GSM Supplementary Services: |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.2 Enable GSM Supplementary Service Functionality | The Facility messages to "Register GSM Support are used to enable GSM supplementary services. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.3 GSM Supplementary Services Parameters | The following subclauses describe parameters, which are used in the Facility messages for GSM Supplementary Services.
7.7.3.1 ss_operation
ss_operation (word)
This parameter describes the content of the GSM Supplementary Services related Facility messages or the Info Element parameter in case of a GSM facility.
Defined values of ss_operation are:
0 Used if a Release Complete message which terminates the SS transaction is received from the network without any additional information like a cause or a facility.
0x43xx GSM cause from the network according to GSM 04.08 [7]. In the field "xx" the cause value received within the cause information element (octet 4) from the network is indicated.
0xA1xx Invoke message
In the field "xx" the ss_operation_code according to GSM 04.80 [9] is indicated;
0xA2xx Return Result message
In the field "xx" the ss_operation_code according to GSM 04.80 [9] is indicated;
0xA3xx Return Error message
In the field "xx" the ss_error_code according to GSM 04.80 [9] is indicated;
0x80xx Reject (general problem) message
In the field "xx" the ss_general_problem_code according to GSM 04.80 [9] is indicated;
0x81xx Reject (invoke problem) message
In the field "xx" the ss_invoke_problem_code according to GSM 04.80 [9] is indicated;
0x82xx Reject (return result problem) message
In the field "xx" the ss_return_resutl_problem_code according to GSM 04.80 [9] is indicated;
0x83xx Reject (return_error_problem) message
In the field "xx" the ss_return_error_problem_code according to GSM 04.80 [9] is indicated. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.3.2 Forwarding Feature | Forwarding Feature (struct)
The forwarding feature contains an optional basic_service_code, optional ss_status, optional forw_to_num, optional forw_to_subadr and optional no_reply_cond_time.
It appears in the forw_feat_list parameter of the FACILITY_CONF message (function 257 Mobile Originated SS transaction).
Forwarding Feature Parameter:
basic_service_
code
struct
Byte 0 code_flag
= 0 => teleservice
= 1 => bearer service
Byte 1 service code (acc. to GSM 09.02 [12])
ss_status
struct
Byte 0 SS status (acc. to GSM 09.02 [12])
forw_to_num
struct
contains the forwarded to number parameter coded as an ISDN‑Address String according to GSM 09.02 [12]
forw_to_subaddr
struct
contains the forwarded to subaddress parameter coded as an ISDN‑Subaddress String according to GSM 09.02 [12]
no_reply_cond_
time
struct
Byte 0 no reply condition time parameter according to GSM 09.02 [12] (integer value from 5 .. 30) coded in one Octet. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4 Facility message parameter | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.1 Restrict SS Information | Restrict SS Information
This message is sent from the application to the protocol to restrict SS‑related information from the protocol to the application.
If the protocol receives from the network information related to Basic Service Codes of the last request to restrict SS information , (e.g. "forw_feat" in the "forw_feat_list") then this information will be included in the messages described below.
Every new message overrides the last selections.
If no request for SS information restriction was sent or no Basic Service Code is specified (empty basic_service_code_list) then all information will be given to the application.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
256
basic_service_
code_list
struct
contains n (n ³ 0) basic service codes
1. service code (if n > 0):
Byte 0 code_flag
= 0 => teleservice
= 1 => bearer service
Byte 1 service code (acc. to GSM 09.02 [12])
:
n. service code:
Byte 2 x (n ‑ 1) code_flag
Byte 2 x n ‑ 1 service code
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
256 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.2 Mobile Originated SS Transaction | Mobile Originated SS Transaction
These messages are used to start and end a Mobile originated SS transaction.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
257
ss_ussd_string
struct
ss_ussd_coding_
scheme
struct
Byte 0 CellBroadcastDataCodingScheme as defined in GSM 03.38 [4]
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
257
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
257
ss_operation
word
ss_code
struct
Byte 0 SS code (acc. to GSM 09.02 [12])
basic_service_
code
struct
Byte 0 code_flag
= 0 => teleservice
= 1 => bearer service
Byte 1 service code (acc. to GSM 09.02 [12])
ss_status
struct
Byte 0 SS status (acc. to GSM 09.02 [12])
ss_ussd_coding_
scheme
struct
Byte 0 CellBroadcastDataCodingScheme as defined in GSM 03.38 [4]
ss_ussd_string
struct
clir_restr_opt
struct
Byte 0 = 0 => permanent
= 1 => temporary default restriction
= 2 => temporary default allowed
override_
category
struct
Byte 0 = 0 => override enable
= 1 => override disable
forw_feat_list
struct
contains a list of forwarding features
Byte 0 n = number of forwarding features (if any)
struct 1. forwarding feature
:
struct n. forwarding feature
call_barring_
cause
struct
Byte 0 = 0 => barring service active
= 1 => operator barring
pw_reg_fail_
cause
struct
Byte 0 = 0 => undetermined
= 1 => invalid format
= 2=> new password mismatch
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
257 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.3 Clear Mobile Originated SS Transaction | Clear Mobile Originated SS Transaction
These messages are used to clear a Mobile originated SS transaction.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
258
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
258 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.4 Receive SS Message | Receive SS Message
These messages are used to handle:
1) The spontaneous reception of an incoming SS transaction (Forward check indication).
2) The message transfer for unstructured SS data.
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
259
ss_operation
word
ss_code
struct
Byte 0 SS code (acc. to GSM 09.02 [12])
ss_status
struct
Byte 0 SS status (acc. to GSM 09.02 [12])
notification
struct
Byte 0 SS Notification (acc. to GSM 04.80 [9])
Byte 1 SS Indication mask. Bit field coded as follows:
[0]: call waiting
[1]: call on hold
[2]: call is retrieved
[3]: MPTY
[4]: CLIR Suppression rejected
[5]: call Activation (only phase 1)
[6]: Erasure (only phase 1)
[7]: not used
ss_ussd_coding_
scheme
struct
Byte 0 CellBroadcastDataCodingScheme as defined in GSM 03.38 [4]
ss_ussd_string
struct
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
259 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.5 Call Hold | Call Hold
These messages are used to handle the call related part of the Call Hold Supplementary service. The PLCI of the FACILITY messages describes the identifier of the call, which will be put on "Hold".
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
260
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
260
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
260
Reason
word
0: successful request for Call Hold
0x83xx: request for Call Hold rejected. The field "xx" contains the cause coded according to GSM 04.08 [7]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
260 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.6 Call Retrieve | Call Retrieve
These messages are used to handle the call related part of the Call Retrieve Supplementary service. The PLCI of the FACILITY messages describes the identifier of the call, which will be retrieved.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
261
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
261
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
261
Reason
word
0: successful request for Call Retrieve
0x83xx request for Call Retrieve rejected, The field "xx" contains the cause coded according to GSM 04.08 [7]
Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
261 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.7 Call Related Ussd | Call Related Ussd
These messages are used to handle the Call Related Ussd Supplementary service. The PLCI of the FACILITY_REQ/CONF/IND/RESP messages describes the identifier of the call.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
262
ss_ussd_string
struct
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
262 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.8 Receive Call Related Facility | Receive Call Related Facility
These messages are used to receive the information of a call related facility. The related call is identified by the PLCI of the FACILITY_IND and FACILITY_RESP message.
Facility Indication Parameter:
Facility selector
word
256: GSM support
Function
word
263
ss_operation
word
ss_code
struct
Byte 0 SS code (acc. to GSM 09.02 [12])
ss_status
struct
Byte 0 SS status (acc. to GSM 09.02 [12])
notification
struct
Byte 0 SS Notification (acc. to GSM 04.80 [9])
Byte 1 SS Indication mask. Bit field coded as follows:
[0]: call waiting
[1]: call on hold
[2]: call is retrieved
[3]: MPTY
[4]: CLIR Suppression rejected
[5]: call Activation (only phase 1)
[6]: Erasure (only phase 1)
[7]: not used
ss_ussd_string
struct
Facility Response Parameter:
Facility selector
word
256: GSM support
Function
word
263 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8 Extended GSM functionality | This subclause defines additional functions for GSM‑API (Facility selector 256): |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8.1 Facility Message parameter | |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.