hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.1.3 Stored in the MSC/VLR | CTS MS subscriber CTS subscription may be stored in the MSC/VLR. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2 Information managed per CTS-FP subscriber | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2.1 Stored in the CTS-FP SIM | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2.2 Stored in the CTS-FPE | CTS-SN Telephone Number is stored in non volatile memory in the CTS-FPE. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2.3 Stored in the CTS-SN | CTS-FP subscriber's subscription information may be stored in the CTS-SN. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2.4 Stored in the CTS-HLR | CTS-FP subscriber's subscription information may be stored in the CTS-HLR. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7 Identities | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.1 Identification of the CTS-FP | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.1.1 IFPSI | A CTS specific identity is assigned to a CTS FP subscriber of a CTS service. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.1.2 IFPEI | Each CTS-FP is assigned by the manufacturer a unique IFPEI number see GSM 03.03 [3].
The coding rules of the IFPEI and the rules for changing the IFPEI shall be equal to the rules defined for the IMEI in GSM 03.03 [3]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.1.3 FPBI | The CTS-FP broadcasts (after CTS-FP initialisation has been performed) a beacon which carries information conveying the Fixed Part Beacon Identity which identifies the CTS-FP. The FPBI need not be unique due to the capacity of signalling on the beacon. The FPBI is defined in GSM 03.03 [3]. The use of the beacon and the... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2 Addressing parameters | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.1 Addressing the CTS-FP | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.1.1 CTS-FP Fixed Network dialling number | This is the fixed network dialling number (PSTN/ISDN) to which the CTS-FP is connected. A single CTS-FP may have several fixed network dialling numbers. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.1.2 CTS FP name | It shall be possible to assign a subscriber-defined identifier to each CTS FP. The CTS FP name can e.g. be an icon or an alphanumeric text up to 10 characters. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.2 Addressing the CTS-MS subscriber | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.2.1 MSISDN | The MSISDN is the dialling number at which the CTS-MS can be reached in the cellular network. It may also be used for CTS applications.
In order to address a CTS-MS by its MSISDN, this number has to be known by the CTS-FP and the CTS-MS. The MSISDN may be submitted to the CTS-FP either:
• from the CTS-HLR at CTS-MS enr... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.2.2 CTS-MS Subscriber Identity(CTS-MSI) | The CTS-MSI is an CTS-MS identity which has only local significance between a CTS-MS and CTS-FP pair, its purpose is to maintain the anonymity of the users of the CTS service as specified in [4].
The CTS-MSI is assigned and maintained by the CTS-FP during CTS-MS enrolment, and is reallocated by the CTS-FP during CTS at... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 8 Operation and maintenance aspects | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9 Function and information flows | The following functional flows deal with the initial phase of CTS where roaming is not supported. In this case the DPLMN, HPLMN and the CTS operator need to be the same. If they are the same then this allows the CTS reference model to be simplified as the CTS FRA can be integrated in to the CTS SN thus simplifying the ... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.1 CTS FP management | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.1.1 CTS FP Initialisation | CTS FP initialisation can be envisaged in two phases.
The data flow diagram below shows the flows required for CTS FP initialisation.
Figure 9: CTS FP initialisation
1 The CTS-FP subscriber wants to initialise a CTS-FP. He triggers an MMI procedure. The CTS-SN telephone number is used by the CTS-FP to contact the CTS-S... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.1.2 Update of CTS FP frequencies | The data flow diagrams below shows the flows required for gathering the DPLMN surrounding cells and the updating the CTS FP GFL.
Figure 10: CTS MS Home cell reporting
1 The CTS MS remembers the cells it last camped on from the DPLMN and the time it left each cell.
2 This cell information is given to the CTS FP during s... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 2 Authentication of the CTS FP is made by the CTS SN and HLR | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 3 DPLMN information is given by the CTS FP for location purposes | 4 GFL is updated and the CTS-FP authenticates the CTS-SN.
This procedure also forms part of the CTS-FP initialisation procedure where the Temporary GFL (allocated during the first initialisation) is replaced by the GFL based on location information. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.2 CTS management for CTS MS | The GSM PLMN controls the MS as to whether it can operate CTS. When the CTS-MS access the GSM PLMN it will receive signalling which informs the CTS-MS whether it can perform CTS operations.
Figure 12
1 The MS performs a location update in the DPLMN.
2 Authentication is performed.
3 If CTS is allowed in the PLMN, or thi... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.3 CTS integration to Fixed Mobile Convergence applications | In order to use CTS for FMC applications it is suggested that a hook be provided in order to facilitate FMC applications. To this end it is envisaged to allocate a FMC Telephone Number, for instance on the CTS-FP SIM. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4 Functions related to MS in idle mode for support of CTS | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.1 Cell selection and reselection | The definition of a "suitable cell", as defined in GSM 03.22, is extended with the following criterion:
An CTS-MS with SIM indicating CTS subscription shall always try to select the cell with the highest CTS FP priority according to the information stored on the SIM. The CTS selection parameters last received from the ... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.2 DPLMN Cell information gathering | As the CTS-MS roams through the DPLMN it shall gather information as to the cells it has passed through. This cell information is stamped with the time that the MS either left the cell or lost GSM coverage with the cell. The figure below shows the required functional behaviour.
When the CTS-MS gives this information to... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.3 CTS local mobility | The presence and absence of a CTS-MS needs to be determined by the CTS-FP as part of the local CTS mobility procedures. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.3.1 CTS attachment | CTS attachment is a procedure by which a CTS-MSs presence is made known to the CTS-FP. The attachment to a CTS-FP is made by the CTS-MS when the CTS-MS comes within coverage of the CTS-FP.
The CTS Attach procedure shall replicate the protocol as expected as in GSM, with the exceptions to the local security procedures d... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.3.2 CTS detachment | CTS detachment is a procedure by which a CTS-MSs non presence is made known to the CTS-FP. When a CTS-MS is attached the CTS-FP shall regularly ensure that the CTS-MS is within CTS-FP coverage, if the CTS-MS is found to be out of coverage the CTS-FP will mark the CTS-MS as detached. If the MCTS-MS is powered down withi... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.5 Functions related to active mode support of CTS | 9.5.1 MS connection establishment for MT and MO calls.
When calls are established the CTS FP shall perform Authentication and Ciphering as specified in 03.20. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.5.2 Handover | Handover between instances of CTS radio interfaces shall be supported by the CTS MS when the same CTS FP controls these CTS radio interfaces. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.6 Overview of signalling | Security procedures such as authentication, ciphering and key distribution are defined in order to protect the GSM network and the user communication. CTS operation is initialised by downloading operation control information into the CTS-FP. The operator can change and de-activate CTS operation via the GSM Radio Interf... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10 CTS Architecture | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.1 CTS Elements | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.1.1 CTS Fixed Part | CTS Fixed Part (CTS-FP) is the logical and physical element, which provides the link to the access network. For this purpose it controls on the one side one or more CTS Radio Interface and on the other side one or more access network interface. The interworking between both interfaces is implemented in the CTS-FP inter... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.1.2 CTS Mobile Station | The CTS Mobile Station (CTS-MS) is the logical and physical element which provides to the user cordless access to the fixed network or the GSM network. The CTS-MS consists of GSM Mobile Equipment and a GSM-SIM, both with additional CTS capabilities.
Figure 18: The CTS-MS and its main functional entities |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.1.3 CTS controlling and supporting network entities | In order to control and support the CTS, the following functional entities are situated in the GSM network:
• the CTS-AuC is the functional entity for performing authentication of the CTS-FP SIM;
• the CTS-HLR is the functional entity which contains the data base of the CTS-FP subscribers of the CTS operator. This data... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2 CTS Interfaces | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.1 CTS Radio Interface (Um*) | The CTS Radio Interface is used for local communication between CTS MS and the CTS FP. It provides a cordless connection between these two elements. This interface is referred to as Um* in the CTS specifications.
According to GSM 02.56 [2], the CTS Radio Interface is a modified GSM Radio Interface. CTS is to operate in... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.2 GSM Radio Interface (Um) | On the GSM Radio Interface the CTS-MS shall behave according to the GSM standards. As required in GSM 02.56 [2], means of the GSM Radio Interface shall be used to exchange information relevant for operation control of the CTS. User communication via the GSM Radio Interface is covered by the GSM specifications and not c... |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.3 CTS Access Network Interface | The Access Network Interface is the connection of the CTS-FP to the Fixed or mobile Network for user communication. According to GSM 02.56 [2], this interface shall also be used to transport information which is relevant for operation control. The Fixed Network Interface is referred to as Cf in the CTS specifications. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.3.1 Physical characteristics of the CTS Fixed Network Interface | The physical characteristics of the Fixed Network Interface, e.g. signal levels, shall correspond to national standards. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.3.2 Physical characteristics of the CTS GSM Network Interface | In the case of a CTS-FP connected to GSM, the physical characteristics of the GSM Network Interface, e.g. signal levels, shall correspond to GSM standards. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4 Network internal interfaces | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4.1 Interface CTS SN/CTS HLR (Cd) | The Cd interface between the CTSSN and the HLR may use existing MAP procedures to receive challenge/response pairs to be used for the authentication of the CTS FP SIM when communication is performed via the access network. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4.2 Interface CTS SN/CTS HLR (Cd') | Cd' interface between CTS SN and CTS HLR. The interface is used for CTS FP subscription control. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4.3 Interface CTS SN/CTS FRA | This interface is used when download of radio parameters shall be performed to the CTS-FP via application signalling. |
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 ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.