hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 3.1 Service elements on the application layer | An association (class 3) between CBRSEs is formed via ACSE and ROSE operations (class 2 and 5) are used to implement the service requirements specified for the CBC - BSC interface in GSM 03.41.
This results in an asynchronous asymmetric situation where the application entity in the CBC or BSC can invoke a CBRSE operati... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 3.2 Detailed specification of the CBRSE services | On the following pages, the new CBRSE service element is specified with the ASN.1 notation, together with the entire protocol.
The Abstract Syntax Notation of
the Cell Broadcast Relay Service Element
CBRSE
1st module of 3:
CBS-UsefulDefinitions
CBS-UsefulDefinitions {
ccitt identified-organization (4) etsi (0) mobile-d... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 3.3 Application rules | The following application rules specify the invocation of different operations on the association. Two alternative sets of application rules are given in 3.3.1 (for semi-permanent connections) and in 3.3.2 (for transient connections); additional sets are possible. |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 3.3.1 Application rule set 1 Semi-permanent symmetric connection | This set of application rules is to be used in situations where the connection (on all the protocol layers) between the CBC and the BSC is maintained for ever.
Within the CBR-BIND service, all operations are allowed on the association; semi-permanent connection is accepted (by not forcing the connection transient). Thi... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 3.3.2 Application rule set 2 Transient asymmetric connection | This set of application rules is to be used e.g. in situations where a CBC has connections with many BSCs, and there is a switched data network connecting them. A data network connection (and the higher layer connections on top of it) is maintained for the duration of the relay or alert operations only.
Within the CBR-... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 4 An SS7 Protocol Stack For Interconnecting CBC And BSC | Concepts described in Q.1400 (see CCITT Study Group XI - Report R219) are used. These concepts enable, with minor modifications, the protocol specified in Section 3 of GSM 03.49 to be supported via an SS7 protocol stack.
Q.1400 specifies the use of OSI concepts via SS7 for the development of signalling and operations a... |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 1 Scope | The present document describes the support of the teletex service by a GSM Public Land Mobile Network (PLMN). |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 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.
• Fo... |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 2.1 Abbreviations | In addition to those below, definitions used in the present document are listed in GSM 01.04.
AU Access Unit (CCITT X.31)
CF Conversion Facility (for Ttx/Tx service interworking)
GMSC Gateway MSC
HDLC High Level Data Link Control
IWU Interworking Unit (CCITT X.71/CCITT X.75)
LAPB Link Access Procedure Balanced
PLP Pack... |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 3 Introduction | |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 3.1 Teletex service definition | The teletex (Ttx) service is an international telematic service as defined in CCITT F.200-series of recommendations.
As an essential characteristic it provides a basic level of compatibility between all terminals participating in the service.
Normally the service shall operate on a fully automatic basis and be open con... |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 3.2 Context for the Support of Teletex in a GSM PLMN | Considering that
a) international roaming of teletex subscribers must be supported;
b) all CEPT countries have PSPDNs;
c) PSPDNs providing an access unit AU (X.31 case A) support procedures according to CCITT X.32;
d) each CEPT country will have an ISDN;
e) ISDNs may provide the VCS;
f) the teletex service supported by... |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 3.3 Reference Configuration of a Teletex Mobile Station | The reference configuration (figure 1/GSM 03.44) is equivalent to those configurations in GSM 07.03.
An explicit TA may be used between the R- and the S-interface reference point.
The configuration TE1-MT1 can only be supported by means of a specialized TAF including protocol conversion, if necessary, to guarantee the ... |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 4 Interworking for Teletex Support | |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 4.1 Global Network Configuration for Teletex | Presently teletex is offered in the CSPDN, the PSPDN, the PSTN, and in the very next future in the ISDN. Figure 2/GSM TS 03.44 shows the different networks to which a GSM PLMN may have to interwork, when supporting the communication between teletex terminals.
*) This interworking requires a Ttx-specific IWF within the ... |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 4.2 Network Interworking Scenarios | The following network interworking scenarios may be derived from the global network configuration. Some scenarios allow for different implementations of an IWF. For the interworking functions needed between the PLMN and the different networks refer to GSM TS 09.06 and 09.07. The choice of interworking scenario and the ... |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 4.3 Mobile-to-mobile Communication | A communication from a mobile to another mobile is treated like a call from/to a fixed network subscriber, e.g. using the packet functions as per GSM 09.06. |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 4.4 Use of GSM Supplementary Services | For supplementary services refer to GSM 09.06 and GSM 09.04.In addition Call forwarding supplementary services may be used to forward a mobile terminated call to a TDS (refer annex). |
9462d069b1108ea61cac6d50d7aa61a9 | 03.44 | 4.5 High Layer Compatibility Information Element | Mobile subscribers using the teletex service may code the high layer compatibility information element as described below. Depending on the network implementation this indication may be used by the network for teletex specific requirements.
Depending on the signalling capabilities of the fixed network the high layer co... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Scope | This European Telecommunication Standard (ETS) defines the GSM Application Programming Interface (GSM‑API) in two parts.
The first part describes, how compatibility to existing application interface ETS 300 838 [14] is covered for the GSM network. So existing PCI applications are able to be used in a GSM environment. F... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 2 Normative references | This ETS incorporates by dated and undated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this ETS only ... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 3 Definitions and abbreviations | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 3.1 Definitions | For the purposes of this ETS, the following definitions and those given in ETS 300 838 [14] apply:
Invalidate SIM File This is a procedure to change the availability of a SIM file. With the invalidate function, the corresponding file will no longer be available. See GSM 11.11 [13].
Rehabilitate SIM File This function w... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 3.2 Abbreviations | For the purpose of this ETS, the following abbreviations apply:
API Application Programming Interface
ASN1 Abstract Syntax Notation Number 1. This notation is used in different GSM services.
CAPI COMMON‑ISDN‑API
CBS Cell Broadcast Service. It is a specific GSM service used to broadcast messages to all subscribers. See ... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 4 Profile A compatible part of GSM‑API | (replaces subclause 5.7 of ETS 300 838 [14]).
For further study. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5 Profile B compatible part of GSM‑API | (replaces subclause 6.8 of ETS 300 838 [14].) |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.1 Overview | This part of GSM‑API defines the parameter description which replaces subclause 6.8 of ETS 300 838 [14] (i.e. Parameter description of Profile B). This replacement is necessary to run existing COMMON‑ISDN‑API applications on a GSM network. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2 Parameter description | This subclause describes the parameters used in ETS 300 838 [14] profile B messages. Each parameter is listed with its type, possible values and reference to the messages in which the parameter appears.
Some parameter values are defined according to ETS 300 102‑1 [15], Q.931 [16] or GSM 04.08 [7] and 04.11 [8]. In that... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.1 Additional Info | Additional Info (struct)
The purpose of the parameter additional info is to exchange signalling protocol specific information of the network. Depending on the signalling protocol only relevant elements of this structure shall be used (e.g. the B channel information has to be ignored in the message DISCONNECT_REQ).
The... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.2 B Channel Information | B Channel Information (struct)
The purpose of the sub parameter B channel information is to choose between B channel data exchange, D channel data exchange or pure user‑user data exchange. If this struct is empty the default value is assumed.
This sub parameter is coded as a structure, to give an easy way of extendin... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.3 B Protocol | B Protocol (struct)
The purpose of the parameter B protocol is to select and configure the B channel protocols. There is a protocol identifier and configuration information for each layer. If this struct is empty the default value is assumed.
The parameter has the following structure:
word B1 protocol : Physical layer... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.4 B1 Protocol | B1 Protocol (word)
The purpose of the sub parameter B1 protocol is to specify the physical layer and framing used for this connection. In GSM‑API following transfer modes shall be supported by the mobile station:
The following values are defined: |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.5 B2 Protocol | B2 Protocol (word)
The purpose of the sub parameter B2 protocol is to specify the data link layer used for this connection.
The following values are defined:
0 ISO 7776 [17] (X.75 SLP) This is the default B2 protocol; |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.6 B3 Protocol | B3 Protocol (word)
The purpose of the sub parameter B3 protocol is to specify the network layer used for this connection.
The following values are defined: |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.7 B1 Configuration | B1 Configuration (struct)
reserved, shall be ignored
This sub parameter appears in parameter:
B protocol |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.8 B2 Configuration | B2 Configuration (struct)
The purpose of the sub parameter B2 configuration is to offer additional configuration information for B2 protocol. It is only used for B2 protocols 0, 2 and 3. The parameter has the following structure:
byte
Address A
This parameter has different meaning and default values depending on th... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.9 B3 Configuration | B3 Configuration (struct)
The purpose of the sub parameter B3 configuration is to offer additional configuration information for B3 protocol. Different structures of this parameter are defined, depending on the B3 protocol:
For B3 protocols 0 (transparent) this parameter does not apply (coded as an empty structure... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.11 Called Party Number | Called Party Number (struct)
The purpose of the parameter called party number information element is to identify the called party of a call. The information element is coded according to ETS 300 102‑1 [15] / Q.931 [16].
Byte 0
Type of number and numbering plan identification (byte 3 of the called party number informat... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.12 Called Party Subaddress | Called Party Subaddress (struct)
The purpose of the parameter called party subaddress is to identify the subaddress of the called party of a call. The information element is coded according to ETS 300 102‑1 [15] / Q.931 [16].
Byte 0
Type of subaddress
At the calling side the value supplied by application shall be trans... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.13 Calling Party Number | Calling Party Number (struct)
reserved, shall be ignored.
This information element appears in:
CONNECT_REQ
CONNECT_IND
LISTEN_REQ |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.14 Calling Party Subaddress | Calling Party Subaddress (struct)
The purpose of the parameter calling party subaddress information element is to identify a subaddress associated with the origin of a call. The information element is coded according to ETS 300 102‑1 [15] / Q.931 [16].
Byte 0
Type of subaddress
At the calling side the value supplied by... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.15 CIP Value | CIP Value (word)
The purpose of parameter CIP Value is to identify a complete profile of compatibility information (Bearer Capability, Low Layer Compatibility and High Layer Compatibility). With this parameter standard applications are not required to do complex coding and decoding of the above mentioned information el... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.16 CIP mask | CIP mask (dword)
The purpose of the parameter CIP mask is to select basic classes of incoming calls. The bit position within this mask identifies the related CIP value. When an incoming call is received, Profile B tries to match this incoming call to the defined CIP values (more than one value may match). A CONNECT_IND... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.17 Connected Number | Connected Number (struct)
The purpose of the parameter connected number information element is to indicate which number is connected to a call. The information element shall be coded according to ETS 300 097 [28].
Byte 0
Type of number and numbering plan identification (byte 3 of the connected number information elemen... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.18 Connected Subaddress | Connected Subaddress (struct)
The purpose of the parameter connected subaddress information element is to identify the subaddress of the connected user of a call. The information element is coded according to ETS 300 097 [28].
Byte 0
Type of subaddress
At the calling side the value supplied by application shall be tran... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.19 Controller | Controller (dword)
The purpose of the parameter controller is to address a hardware unit, that gives access to an ISDN at the application's disposal. A controller supports none, one or several physical and logical connections. The parameter controller is a dword (to be compatible in size with PLCI and NCCI) with the r... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.20 Data | Data (dword)
The purpose of the parameter data is to exchange a 32 bit pointer to the data area containing the information.
This information element appears in:
DATA_B3_REQ
DATA_B3_IND |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.21 Data Length | Data Length (word)
The purpose of the parameter data length is to specify the length of the data.
This information element appears in:
DATA_B3_REQ
DATA_B3_IND |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.22 Data Handle | Data Handle (word)
The purpose of the parameter data handle is to identify the data area in data exchange messages.
This information element appears in:
DATA_B3_REQ
DATA_B3_CONF
DATA_B3_IND
DATA_B3_RESP |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.23 Facility Selector | Facility Selector (word)
The purpose of the parameter facility selector is to identify the requested Profile B facility.
The defined values are:
0 reserved, shall be rejected; |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5.2.24 Facility Request Parameter | Facility Request Parameter (struct)
The purpose of the parameter facility request parameter is to offer additional information concerning the message FACILITY_REQ.
This parameter is coded depending on facility selector as a structure with following elements:
Facility selector: |
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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.