hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.25 Facility Confirmation Parameter | Facility Confirmation Parameter (struct)
The purpose of the parameter facility confirmation parameter is to offer additional information concerning the message FACILITY_CONF.
This parameter is coded depending on facility selector as a structure with following elements:
Facility selector: |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.26 Facility Indication Parameter | Facility Indication Parameter (struct)
The purpose of the parameter facility indication parameter is to offer additional information concerning the message FACILITY_IND.
This parameter is coded depending on facility selector as a structure with following elements:
Facility selector:
0 reserved |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.27 Facility Response Parameter | Facility Response Parameter (struct)
The purpose of the parameter facility respond parameter is to offer additional information concerning the message FACILITY_RESP.
This parameter is coded depending on facility selector as a structure with following elements:
Facility selector: |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.28 Flags | Flags (word)
The purpose of the parameter flags is to exchange additional protocol dependent information about the data.
Bit 0
qualifier bit
Bit 1
more data bit
Bit 2
delivery confirmation bit
Bit 3
expedited data bit
Bit 15
framing error bit, data may be invalid (only with corresponding B2 protocol)
This information e... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.29 HLC | HLC (struct)
reserved, shall be ignored
This information element appears in:
CONNECT_IND
CONNECT_REQ |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.30 Info | Info (word)
The purpose of the parameter info is to provide error information to the application. For each error which can be detected by the controller a unique code is defined, independent from the context of the error.
Profile B shall not generate other information values as defined below. In case of future extensi... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.31 Info Element | Info Element (struct)
The purpose of the parameter info element depends on the value of the parameter info number.
If the info number specifies an information element, the info element contains that information element with the coding as defined in ETS 300 102‑1 [15] / Q.931 [16].
If the info number specifies a chargin... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.32 Info Mask | Info Mask (dword)
The parameter info mask specifies which type of information for a physical connection or controller shall be provided by Profile B. The selected information shall be indicated within the message INFO_IND to the application. A given info mask (set in LISTEN_REQ) is valid until it is superseded by anoth... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.33 Info Number | Info Number (word)
The purpose of the parameter info number specifies the coding of the parameter info element and the type of information which is carried by this INFO_IND message. The high byte is structured as a bit field and indicates which type of information is held in the low byte.
Bit 15
If this bit set to 1 th... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.34 LLC | LLC (struct)
The purpose of the parameter Low Layer Compatibility (LLC) information element is to provide a means which should be used for compatibility checking by an addressed entity (e.g. a remote user or an inter working unit or a high layer function network node addressed by the calling user). The Low Layer Compat... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.35 Manu ID | Manu ID (dword)
The purpose of the parameter Manu ID is to exchange a dword inside MANUFACTURER‑Messages which identifies the manufacturer. Every manufacturer offering MANUFACTURER‑Messages should choose a unique value (e.g. shortcut of company name).
This information element appears in:
MANUFACTURER_REQ
MANUFACTURER_R... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.36 Manufacturer Specific | Manufacturer Specific
The purpose of the parameter manufacturer Specific is to exchange manufacturer specific information.
This information element appears in:
MANUFACTURER_REQ
MANUFACTURER_RESP
MANUFACTURER_CONF
MANUFACTURER_IND |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.37 NCCI | NCCI (dword)
The purpose of the parameter NCCI is to identify a logical connection. The NCCI is given by Profile B during creation of the logical connection. Depending on the layer 3 protocol selection (e.g. ISO 8208 [24]), it is possible to have multiple NCCIs based on one PLCI. The NCCI is a dword with a range from 1... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.38 NCPI | NCPI (struct)
The purpose of the parameter NCPI is to provide additional protocol specific information.
For the layer 3 protocols ISO 8208 [24] and X.25 the parameter data of structure NCPI are coded as follows:
Byte 0
Bit field
[0]: Enable the usage of the delivery confirmation procedure in call set‑up and data packe... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.39 PLCI | PLCI (dword)
The purpose of the parameter PLCI is to describe a physical connection between two endpoints. The PLCI is given by Profile B during creation of the physical connection. The PLCI is a dword with the range from 1 to 255 (0 reserved), coded as described below, and additionally includes the controller.
Format... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.40 Reason | Reason (word)
The purpose of the parameter reason is to provide error information to the application regarding the clearing of a physical connection . The defined values are:
0 normal clearing, no cause available;
0x3301 protocol error layer 1;
0x3302 protocol error layer 2;
0x3303 protocol error layer 3;
0x3304 anothe... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.41 Reason_B3 | Reason_B3 (word)
The purpose of the parameter reason is to provide error information to the application regarding the clearing of a logical connection . The defined values are:
protocol independent:
0 normal clearing, no cause available;
0x3301 protocol error layer 1 (broken line or B channel removed by signalling pro... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.42 Reject | Reject (word)
The purpose of the parameter reject is to define the action of Profile B for incoming calls.
The defined values are |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 6 GSM specific part of GSM‑API (addition to ETS 300 838profile A) | For further study. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7 GSM specific part of GSM‑API (addition to ETS 300 838profile B) | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.1 Overview | Clause 5 of this ETS contains the description of the part of GSM‑API, which is compatible to ETS 300 838 [14] Profile B (COMMON‑ISDN‑API). Following this approach, existing applications of this ETS are able to be used in a GSM environment.
However, to use GSM specific features new GSM‑API applications need extensions t... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.2 GSM specific functionality | The following GSM specific functionality is offered by GSM‑API:
Registration of GSM support:
Support of GSM Tele and Bearer Services:
‑ Modem (usage of modem of the Inter Working Function);
‑ Telephony;
‑ Alternate speech fax (TS 61);
‑ Emergency Calls.
Control of Short Message Service (SMS) and Cell Broadcast Servic... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.3 Extension mechanism | The extension of ETS 300 838 [14] profile B is done in two ways:
1) Some of the existing parameters of ETS 300 838 [14] profile B are extended by GSM specific values. These extensions are described in the subclause 5.1 of this ETS.
2) The FACILITY mechanism of ETS 300 838 [14] profile B will be used to extend this (ISD... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.4 Registration of GSM support | A function for the FACILITY mechanism of ETS 300 838 [14] profile B is defined to register GSM support: |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.4.1 Register GSM support facility message parameter | Register GSM support
The application uses this message to enable GSM functionality. The parameter "GSM Services" is a bit field, which is used to select the GSM services. If a GSM service is selected, the application has to be able to handle the asynchronous events, coming from the network side.
The following rules app... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.5 Support of GSM Tele and Bearer Services | New CIP values are defined to handle the following tele/bearer services
- modem calls (control of the modem of the Inter Working Function);
- Support of Telephony;
- Support of TS 61(Alternate Speech Fax);
These new values are defined in subclause 5.1.1.4. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.5.1 Emergency Calls | According to GSM 02.30 [3], a GSM emergency call will be set up if the parameter Called Party Number of the CONNECT_REQ message is equal to "112". |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.6 Basic GSM functions | Basic Functions defined for GSM‑API (Facility selector 256): |
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... |
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... |
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 ... |
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 ... |
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. Th... |
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... |
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
Fu... |
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 Suppor... |
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, accordi... |
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
1... |
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 b... |
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 a... |
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 v... |
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... |
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).
Forwardi... |
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_... |
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]
Facilit... |
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 ... |
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 Param... |
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 P... |
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 Par... |
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... |
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 St... |
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 ... |
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 wil... |
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 ... |
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 GS... |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.