hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4.4 Interface CTS FRA/BSC | This interface is used when download of radio parameters shall be performed to the CTS-FP via GSM layer 3 signalling. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.3 CTS sub-systems | The CTS can be split in two subsystems, the local CTS and the supervising CTS:
• the local CTS consists of a CTS-FP and one or several CTS-MS, which are enrolled at the CTS-FP.
The main aspect of the local CTS is that the user communication is provided via the CTS Radio interface and the CTS Access Network Interface;
•... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.4 Network Access | As the purpose of the CTS, the Access Network is accessed by the CTS-MS via the CTS-FP for user communication.
A CTS-MS can, depending on services subscribed, access the GSM network for user communication. This case is covered by the GSM specifications and not considered in the CTS specifications.
According to GSM 02.5... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 11 CTS main parameters | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 11.1 Radio Resource Management parameters | The Radio Resource Management specific parameters are defined in [5]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 11.2 Identification parameters | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 11.3 Security specific parameters | The security related parameters such as authentication and ciphering keys are defined in [4]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 12 The local CTS | The following elements are part of the local CTS:
• CTS-FP;
• One or several CTS-MS.
The following interfaces have relevance for the local CTS:
• the CTS Radio Interface Um* for signalling and user communication;
• the CTS Access Network Interface Cf or Um for user communication.
Aspects of the local CTS are the follow... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 12.1 Transmission and Signalling Planes | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 12.1.1 Transmission Plane | According to GSM 02.56 [2] user communication is restricted to speech in the first phase of CTS specification. The transmission plane is segmented in two parts, the transmission on the CTS Radio Interface and the transmission on the CTS Access Network Interface.
The transmission of speech on the CTS Radio Interface Um*... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 1 Scope | No mandatory protocol between the Service Centre (SC) and the Mobile Switching Centre (MSC) below the transfer layer is specified by GSM; this is a matter of agreement between SC and PLMN operators.
The present document specifies three approaches to the specification of protocol stacks of communication protocols for th... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 1.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... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 1.3 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2 An OSI Protocol Stack For Interconnecting SCs and MSCs | This clause specifies a stack of communication protocols in terms of the OSI Reference Model (see X.200) and therefore makes use of all seven layers for the purpose of relaying short messages and alerts between SC and MSC for the Short Message Service. The SMS application layer (layer 7) is mapped to the Presentation L... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.1 Service elements on the application layer | An association (class 3) between SMRSEs is formed via ACSE and ROSE operations (class 2 and 5) are used to implement the Short Message Relay Layer described in clause 9 of GSM 03.40. This results into a asynchronous symmetric situation where both (the application entity in) the SC and (the application entity in) the MS... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.2 Detailed specification of the SMRSE services | On the following pages, the new SMRSE service element is specified with the ASN.1 notation, together with the entire SM-RL protocol.
The Abstract Syntax Notation of
the Short Message Relay Service Element
SMRSE
NOTE: The first two arcs of the object identifier are arbitrarily allocated, the name "etsi" is adopted from ... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.3 Application rules for avoiding collisions between SMR-UNBIND and the other SMRSE operations | There may be a collision between the SMR-UNBIND operation and another operation. This may cause the unwanted abortion of SMR-MO-DATA or SMR-MT-DATA operations, and/or the loss of SMR-ALERT operations.
(In order to guarantee the completion of all the SMRSE operations, the Session negotiated release functional unit might... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.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 SC and the MSC is maintained for ever.
Within the SMR-BIND service, all operations are allowed on the association; semi-permanent connection is accepted (by not forcing the connection transient). This... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.3.2 Application rule set 2 Transient asymmetric connection | This set of application rules is to be used e.g. in situations where one SC has connections with many MSCs or vice versa, 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.
... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.4 Timing terminology | The overall delay of a short message relay operation between an SC and an MS may be affected i.e. by the following delays:
a) transport connection establishment time between an SC and an MSC (including the time spent establishing a new network connection, if needed);
b) the time needed to establish the higher layer pro... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.5 Error Cause Mapping | MAP to SC - MSC
IllegalSubscriber illegal-subscriber
IllegalEquipment illegal-equipment
TeleServiceNotProvisioned teleservice-not-provisioned
SM-DeliveryFailure (#0) memory-capacity-exceeded
SM-DeliveryFailure (#1) error-in-MS
SM-DeliveryFailure (#2) sms-not-provisioned
CallBarred call-barred
DataMissing... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3 A Protocol Stack which utilises an Application-Network Layer convergence function for interconnecting SCs and MSCs | A convergence function (see Draft CCITT Recommendation Q.941 - Report R 22 May 1990) which maps an application entity protocol directly to the Network Layer service defined by X.213 can provide a practical alternative to ACSE, ROSE and OSI layers 6, 5 and 4 specified in Section 2.
Draft CCITT Recommendation Q.941 propo... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.1 SMRSE Definition | The Short Message Service Relay Element (SMRSE) is defined in terms of the following service :
SMR - BIND:
This operation must be involved by the party which is responsible for establishing the application association ; only after the application association has been established may be remaining SMRSE services be used.... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.2 ASN1 Specification | The Abstract Syntax Notation of
the Short Message Relay Service Element
SMRSE
NOTE: The first two arcs of the object identifier are arbitrarily allocated, the name "etsi" is adopted from GSM 12.20 but the value 040 is arbitrary, and the last three arcs are allocated in this module.
1st module of 2:
SMS-UsefulDefinition... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.3 Application Rules for Avoidance of Collision of SMRSE Operations | For the purpose of establishing the association between SMRSEs in MSC and SC then either the MSC or the SC shall be designated as the entity responsible for initiating the association by the operation SMR‑Bind.
Following premature release of the association by N-DISCONNECT then either the MSC or the SC shall be designa... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.3.1 Semi-permanent Connections | On a semi-permanent connection the SMR-UNBIND operation is not normally invoked following an application association. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.3.2 Transient Connection | In a situation where an SC has several connections to an MSC, or an MSC has several connections to MSCs, and a public data network connection may be maintained for the duration of the relay and/or alert operations the association may be ended via SMR-UNBIND as soon as all operations on the association have been complet... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.4 Non Support of 128 bytes of NS-user-data in Network Connection and Network Connection Release phases | It is generally intended to make the support of 128 bytes of NS-user-data mandatory (see Sections 12.2.8 and 13.2.3 of X.213). CCITT Recommendation X.2 regards provision of Fast Select as essential, thereby ensuring support of 128 bytes of NS-user-data in network connection and network connection release phases will re... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.5 Error Cause Mapping | As section 2.5. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4 SS7 Protocol Stacks | |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.1 Introduction | Concepts described in Q.1400 (see CCITT Study Group XI Report R219, April 1992) are followed. These concepts enable
- specification of an application layer such as SMS-MAP (see section 4.2)
- use of the protocol specified in Section 2 of GSM 03.47 to be supported (with minor modifications) |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.2 Application Layer Protocol SMS-MAP | |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.2.1 Introduction | The present document specifies a CCITT No.7 based interface for interconnecting Short Message Service Centres (SCs) and Gateway/Interworking MSCs (GMSCs and IWMSCs). The interface is based on the Mobile Application Part (MAP, GSM 09.02) protocol stack and principles.
The proposed protocol stack and specific MAP-operati... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.2.2 Protocol Stack | The SMS Mobile Application Part (SMS-MAP) provides the necessary signalling procedures required for information exchange between the network entities, GMSC/IWMSC and Service Centre (SC).
SMS-MAP uses the services of TCAP, SCCP and MTP of CCITT No.7.
NOTE: SMS-MAP is restricted to signalling between SCs and a GMSC/IWMSC... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.2.3 SMS-MAP Version Handling | Interworking with MAP version 2 requires an upgraded version of SMS-MAP. For SMS-MAP (SC <--> GMSC/IWMSC) version negotiation, the principles outlined in MAP version 2 shall be used (GSM 09.02). |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.2.4 Operations | GENERAL RULES
- Components in messages (SMS-MAP protocol violation). If a component, which according to the present document shall be received in a specific message, e.g. a Result component in an End message, is received in another message, the dialogue should be aborted.
- If an operation which is not supported is rec... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.2.5 SMS-MAP SIGNALLING SEQUENCES | SMS-MAP VERSION 1 SIGNALLING PROCEDURES
Timers
Operation = Forward Mobile Terminated Short Message
Timer: T-fmtsm
Value: 15-180 s
Operation = Forward Mobile Originated Short Message
Timer: T-fmosm
Value: 15-30 s
Operation = Service Centre Alert
Timer: T-sca
Value: 5-10 s
Forward Mobile Terminated Short Message Procedur... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.2.6 Errors | ERRORS COMMON FOR VERSION 1 AND VERSION 2
- CallBarred
This error is returned, when a short message delivery failsdue to barring conditions attached to the subscriber. Barring conditions can be attached to the subscriber due to a active call barring supplementary service or by operator initiated barring. A parameter in... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.2.7 SMS-MAP Parameter Data Types | DATA TYPES COMMON FOR VERSION 1 AND VERSION 2
AddressString
ASN.1 Formal Description
AddressString ::= OCTET STRING (SIZE (1..maxAddressLength))
a) First octet including a one bit Extension Indicator, 3 bits Nature Of Address and 4 bits Numbering Plan Indicator.
The following codes are handled by SMS-GMSC:
- Bit 8: ... |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 4.3 Support of Application Layer Specified by section 2 of GSM 03.47 | Q.1400 specifies the use of OSI concepts via SS7 for the development of signalling and operations & management protocols. The protocol specified in Section 2 of the present document can be carried via an SS7 protocol stack consisting of TCAP, SCCP and MTP (see Q.700 series) with minor adaptations:
- ROSE operation clas... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 1 Scope | No mandatory protocol between the Cell Broadcast Centre (CBC) and the Base Station Controller (BSC) is specified by GSM; this is a matter of agreement between CBC and PLMN operators.
The present document specifies three alternative approaches to the specification of protocol stacks of communication protocols for the pu... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 1.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 2 A protocol stack which utilises an application-network layer convergence function for interconnecting CBC and BSC | A convergence function (see Draft CCITT Recommendation Q.941 Report R 22 May 1990) which maps an application entity protocol directly to the Network Layer service defined by X.213 can provide a practical alternative to ACSE, ROSE and OSI layers 6, 5 and 4.
Figure 1
Draft CCITT Recommendation Q.941 proposes to map appli... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 2.1 CBSE Definition | The Cell Broadcast Short Message Service Element (CBSE) is defined in terms of the following service:
CBSE-BIND
This operation must be invoked by the party which is responsible for establishing the application association; only after the application association has been established may the remaining CBSE services be us... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 2.2 ASN1 Specification | The Abstract Syntax Notation of the Cell Broadcast Short Message Service Element
CBSE
1st module of 2:
CBS-UsefulDefinitions
CBS-UsefulDefinitions {
ccitt identified-organization (4) etsi (0) mobile-domain (0)
gsm-messaging (4) gsm-sms3 (12) usefulDefinitions (10) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
ID ::= OBJECT IDE... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 2.3 Application Rules for Avoidance of Collision of CBSE Operations | For the purpose of establishing the association between CBSEs in CBC and BSC then either the CBC or the BSC shall be designated as the entity responsible for initiating the association by the operation CBSE-BIND.
Following premature release of the association by N-DISCONNECT then either the CBC or the BSC shall be desi... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 2.4 Non Support of 128 bytes of NS-user-data in Network Connection and Network Connection Release phases | It is generally intended to make the support of 128 bytes of NS user-data mandatory (see Sections 12.2.8 and 13.2.3 of X.213). CCITT Recommendation X.2 regards provision of Fast Select as essential, thereby ensuring support of 128 bytes of NS-user-data in network connection and network connection release phases. For an... |
fe1707efb60289dcd438dbd3ae2a9dd3 | 03.49 | 3 An OSI Protocol Stack For Interconnecting CBC and BSC | This clause specifies a stack of communication protocols in terms of the OSI Reference Model (see X.200) and therefore makes use of all seven layers for the purpose of fulfilling the service requirements of the primitives specified for the CBC - BSC interface in GSM 03.41. The CBS application layer (layer 7) is mapped ... |
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: |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.