hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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;
• the supervising CTS consists of the functional entities to control CTS operation. The main aspect of the supervising CTS is the control of the operation of the local CTS such as:
• control of the frequencies used by the CTS-FP on the CTS Radio Interface;
• control of the CTS FP subscription (of the SIM) of the CTS FP;
• control of the CTS MS subscription (of the SIM) of the CTS MS.
Figure 20: CTS Subsystems
|
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.56 [2], control of the CTS operation can be carried out either via the GSM Network or via the Access Network. In the latter case the Access Network is as a transit network CTS operation control.
A co-ordination between the GSM Network and the Access Networks is not required.
|
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 following:
• services provided on the CTS radio interface as defined in [2] (e.g. MT and MO calls);
• transmission mechanisms related to these services;
• signalling mechanisms related to these services;
• protocol stacks on the CTS radio interface;
• functions and procedures on the CTS radio interface.
|
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* follows the GSM standard.
The transmission on the CTS Fixed Network Interface follows national standards for the fixed network access and is out of the scope of CTS specifications.
History
Document history
V7.0.1
May 1999
Public Enquiry PE 9943: 1999-05-26 to 1999-10-22
(as EN 301 405)
V7.1.0
May 2000
Vote V 20000721: 2000-05-22 to 2000-07-21
V7.1.1
August 2000
Publication
|
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 the purpose of relaying short messages and alerts between Short Message Service Centres and Gateway/Interworking MSCs (GMSC) for the Short Message Service (SMS). One approach is based upon use of the complete OSI reference model (see X.200), another approach is based upon the use of only the lower three OSI layers, and another approach is based upon the use of CCITT Signalling System No. 7 (see Q.700).
Alternative protocol stacks are specified via ASN.1 encoding rules (see X.208 and X.209). These alternative protocol stacks are examples for the implementation of the Short Message Relay Layer (SM‑RL). The requirements placed upon the Short Message Relay Layer are briefly described in clause 9 of GSM 03.40.
Specifications are based upon individual contributions. Any judgement concerning functionality, completeness and advantages/disadvantages of implementation is intentionally omitted.
|
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.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
[2] GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point-to-Point (PP)".
[3] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification".
[4] GSM 12.20: "Digital cellular telecommunication system (Phase 2); Network Management (NM) procedures and messages".
[5] CCITT Recommendation E.164: "Numbering plan for the ISDN era".
[6] CCITT Recommendation Q.700: "Introduction to CCITT Signalling System No.7".
[7] CCITT Recommendation Q.931: Integrated services digital network.(ISDN) User-Network interface layer 3 specification for basic control".
[8] CCITT Recommendation Q.932: "Generic procedures for the control of ISDN supplementary services".
[9] CCITT Recommendation Q.941: "ISDN user-network interface protocol profile for management".
[10] CCITT Recommendation Q.1400: "Architecture framework for the development of signalling and organisation, administration and maintenance protocols using OSI concepts".
[11] CCITT Recommendation X.2 (1988): "International data transmission services and optional user facilities in public data networks and ISDNs".
[12] CCITT Recommendation X.200: "Reference Model of Open Systems Interconnection for CCITT Applications".
[13] CCITT Recommendation X.208: "Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1)".
[14] CCITT Recommendation X.209: "Specification of Abstract Syntax Notation One (ASN.1)".
[15] CCITT Recommendation X.215: "Session service definition for open systems interconnection for CCITT applications".
[16] CCITT Recommendation X.216: "Presentation service definition for open systems interconnection for CCITT applications".
[17] CCITT Recommendation X.217: "Association control service definition for open systems interconnection for CCITT applications".
[18] CCITT Recommendation X.219: " Remote operations: model, notation and service definition".
[19] CCITT Recommendation X.223: "Use of X.25 to provide the OSI connection-mode network service for CCITT Applications".
[20] CCITT Recommendation X.224: "Transport protocol specification for Open Systems Interconnection for CCITT Applications".
[21] CCITT Recommendation X.225: "Session protocol specification for Open Systems Interconnection for CCITT Applications".
[22] CCITT Recommendation X.226: "Presentation protocol specification for Open Systems Interconnection for CCITT Applications".
[23] CCITT Recommendation X.227: "Information technology - Open Systems Interconnection - protocol specification for the association".
[24] CCITT Recommendation X.229: "Remote operations Protocol specification".
|
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 Layer via ACSE (see X.217 and X.227) and ROSE (see X.219 and X.229). Only the Kernel functional unit of the Presentation Layer is used. Only Kernel and Duplex functional units are used in the Session Layer (see X.215 and X.225).
|
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 MSC can invoke a SMRSE operation at any time.
The new SMRSE service element is first defined in this section, and then specified in ASN.1 notation in section 2.2.
SMRSE definition
This service element defines the following services:
SMR-BIND This operation must be invoked by that party which established the application association; only after that may the remaining SMRSE services be used. This operation reports either success or failure (result or error).
SMR-MO-DATA This operation may be invoked by the application entity in the MSC; it is used to relay one SMS transfer layer PDU from the IWMSC to the SC. This operation reports either success or failure.
SMR-MT-DATA This operation may be invoked by the application entity in the SC; it is used to relay one SMS transfer layer PDU from the SC to the GMSC, to be further relayed to the MS addressed. This operation reports either success or failure, after the full relay attempt to the MS.
SMR-ALERT This operation may be invoked by the application entity in the MSC. It is used as the GMSC-to-SC indication of the fact that an MS which was previously unattainable has recovered operation. This operation does not report any outcome.
SMR-UNBIND This operation must be invoked by that party which invoked the SMR-BIND operation, as the last SMRSE operation before releasing the application association. This operation reports success only.
Of the services defined above, SMR-MO-DATA and SMR-MT-DATA semantically mean the relay of short messages across the SC-MSC-connection; SMR-ALERT similarly implements the alerting operation. The SMR-BIND service is used to exchange identifications, passwords, etc., and in order to negotiate the usage of the other services. The SMR-UNBIND service prepares for the release of the application association.
|
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 GSM 12.20 but the value 040 is arbitrary, and the last three arcs are allocated in this module.
1st module of 3:
SMS-UsefulDefinitions
SMS-usefulDefinitions { iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) usefulDefinitions(0) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
EXPORTS id-ot-SC, id-ot-MSC, id-port, id-ac-so, id-ac-st, id-SMRSE, id-as-SMRSE;
IMPORTS
ID ::= OBJECT IDENTIFIER
-- root for all sms allocations
mobile-domain ID ::= {iso identified-organization etsi(40) mobile-domain(0) }
gsm-messaging ID ::= { mobile-domain gsm-messaging(4) }
gsm-sms1 ID ::= { gsm-messaging gsm-sms1(10)}
-- categories
id-mod ID ::= { gsm-messaging 1 } -- modules
id-ot ID ::= { gsm-messaging 2 } -- object type
id-pt ID ::= { gsm-messaging 3 } -- port types
id-ac ID ::= { gsm-messaging 4 } -- appl. contexts
id-ase ID ::= { gsm-messaging 5 } -- ASEs
id-as ID ::= { gsm-messaging 6 } -- abstract syntaxes
-- modules
usefulDefinitions ID ::= { gsm-sms1 0 }
relayProtocol ID ::= { gsm-sms1 1 }
relayAbstractService ID ::= { gsm-sms1 2 }
-- object types
id-ot-SC ID ::= { id-ot 0 }
id-ot-MSC ID ::= { id-ot 1 }
-- port types
id-port ID ::= { id-pt 0 }
-- application contexts
id-ac-so ID ::= { id-ac 0 } -- SC does BIND
id-ac-st ID ::= { id-ac 1 } -- MSC does BIND
-- application service elements
id-SMRSE ID ::= { id-ase 0 }
-- abstract syntaxes
id-as-SMRSE ID ::= { id-as 0 }
END
2nd module of 3
RelayAbstractService
RelayAbstractService { iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) relayAbstractService(2) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
-- EXPORTS everything
IMPORTS
BIND, UNBIND
FROM Remote-Operations-Notation
{ joint-iso-ccitt remote-operations(4) notation(0) }
OBJECT, PORT, ABSTRACT-BIND, ABSTRACT-UNBIND,
ABSTRACT-OPERATION, ABSTRACT-ERROR
FROM AbstractServiceNotation
{ joint-iso-ccitt mhs-motis(6) asdc(2) modules(0) notation(1) }
id-ot-SC, id-ot-MSC, id-port
FROM SMS-UsefulDefinitions
{ iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) usefulDefinitions(0) } ;
-- upper bound settings
ub-operator-name-length INTEGER ::= 20
ub-agreem-name-length INTEGER ::= 20
ub-X121Address-length INTEGER ::= 15
ub-password-length INTEGER ::= 20
-- Objects
-- The SC and the MSC are modelled as atomic objects, sC-Object and MSC-Object. Each object
-- has one port for the interconnection. ([S] and [C] indicate supply and consumption of services,
-- respectively).
sC-Object OBJECT
PORTS { sMR-port [C] }
::= id-ot-SC
mSC-Object OBJECT
PORTS { sMR-port [S] }
::= id-ot-MSC
-- Port
sMR-port PORT
CONSUMER INVOKES { Forward-MS-Terminated-Short-Message }
SUPPLIER INVOKES { Forward-MS-Originated-Short-Message, Alert- SC }
::= id-port
-- Bind
SMR-Bind ::=
ABSTRACT-BIND
TO { sMR-port }
BIND
ARGUMENT SMR-Bind-Parameters
RESULT SMR-Bind-confirm
BIND-ERROR SMR-Bind-failure
-- Unbind
-- The UNBIND is a harsh release of the association: all outstanding operations are aborted, and
-- SMR-ALERT requests may be lost if they collide with the SMR-UNBIND request. The SC and
-- the MSC should negotiate (during SMR-BIND) the use of services on the association (the
-- operations parameter - list of operation types for the association) in such a way that no harmful
-- losses of operations occur.
SMR-Unbind ::= ABSTRACT-UNBIND
FROM { sMR-port }
UNBIND
ARGUMENT Time-when-connected
RESULT Time-when-disconnected
-- Association control parameters
SMR-Bind-Parameters ::= SEQUENCE {
initiatorID [0] Name,
password [1] Password OPTIONAL,
pswNeeded [2] BOOLEAN,
iniType [3] Telecom-System-Type,
operations [4] List-of-Operations
}
-- Above and in SMR-Bind-confirm
-- initiatorID/respID: identify the initiating/responding telecommunication subsystem
-- password: may assist in authentication
-- pswNeeded (BIND only): requests password into SMR-Bind SMR-Bind-confirm
-- iniType/respType: identify the types of the systems
-- operations: lists the SM relay operations requested and supported on the association:
-- operations listed in both the BIND and the CONFIRM may be used (i.e. this is a negotiation
-- between SC and MSC)
-- transient (CONFIRM only): forces the association (and the underlying connections) transient: it
-- must be UNBouND as soon as there are no operations to be performed
Name ::= SEQUENCE {
operator [0] Operator OPTIONAL,
bilateralAgreem [1] BilateralAgreem OPTIONAL,
dataNetworkAddress [2] X121Address OPTIONAL,
iSDNAddress SMS-Address OPTIONAL
}
-- operator is a text string containing the name of the SC/PLMN operator. bilateralAgreem is a
-- text string identifying the bilateral agreement between the SC and the PLMN operators which
-- allows for this association to be established.
-- dataNetworkAddress is the PSPDN X.121 address of the SC/MSC issuing the BIND or
-- CONFIRM, occurring only if a PSPDN is used.
-- iSDNAddress is the PLMN address of the SC as seen by the MSs (same datum in both BIND
-- and CONFIRM).
-- Any pair of subsets of these parameters may be used to identify the SC and the MSC to one
-- another.
Operator ::= PrintableString (SIZE(0..ub-operator-name-length))
BilateralAgreem ::= PrintableString (SIZE(0..ub-agreem-name-length))
X121Address ::= NumericString (SIZE(0..ub-X121Address-length))
- SMS-Address is specified later in this module.
Password ::= PrintableString (SIZE(0..ub-password-length))
Telecom-System-Type ::= INTEGER {
short-Message-Service-Centre (0),
public-Land-Mobile-Network (1)
-- Extensions are possible: additional
-- telecommunication subsystems might adopt this
-- service element for their interconnection.
}
List-of-Operations ::=
BIT STRING {
sMR-MO-Data-by-MSC (0),
sMR-MT-Data-by-SC (1),
sMR-Alert-by-MSC (2)
-- Extensions are possible: additional operations may be defined within this service
-- element. Existing systems should tolerate unknown values, but negotiate not to
-- perform unknown operations.
}
SMR-Bind-confirm ::= SEQUENCE {
respId [0] Name,
password [1] Password OPTIONAL,
respType [3] Telecom-System-Type,
operations [4] List-of-Operations,
transient [5] BOOLEAN,
connectTime [6] Time-when-connected
}
SMR-Bind-failure ::= SEQUENCE {
connect-failure-reason [0] Connect-failure,
alternative-system [1] Name OPTIONAL
}
-- connect-failure-reason contains one of the error indications given in the following table.
-- alternative-system is included when the SC/PLMN operator wishes to indicate that the MSC/SC
-- might try to establish an association with another SC/MSC.
Error indications
Reason
not-entitled
The responder is not entitled to accept a request for an association between itself and the initiator.
temporary-overload
The responder is not capable of establishing an association due to temporary overload.
temporary-failure
The responder is not capable of establishing an association due to a temporary failure (having impact on an entity at SM-RL or at layers above).
incorrect-ID-or-password
The responder will not accept the request to establish an association between itself and the initiator due to incorrect identity or password.
not-supported
The responder does not recognize the telecommunication subsystem type of the initiator, or cannot support any of the operations suggested on the association.
Connect-failure ::= INTEGER
{ not-entitled (0),
temporary-overload (1),
temporary-failure (2),
incorrect-ID-or-password (3),
not-supported (4)
}
Time-when-disconnected ::= UTCTime
Time-when-connected ::= UTCTime
-- The SMR-MT-DATA operation
-- SMR-MT-DATA
Forward-MS-Terminated-Short-Message ::=
ABSTRACT-OPERATION
ARGUMENT RPDataMT
RESULT RPAck
ERRORS { Unknown-subscriber,
Teleservice-not-provisioned,
Call-barred,
Facility-not-supported,
Memory-capacity-exceeded,
Absent-subscriber,
MS-busy-for-MT-SMS
SMS-lower-layer-capabilities-not-prov,
Error-in-MS,
Illegal-subscriber,
Illegal-equipment,
System-failure
}
-- SMR-MT-DATA error alternatives listed below
Unknown-subscriber ::=
ABSTRACT-ERROR
PARAMETER RPError
Teleservice-not-provisioned ::=
ABSTRACT-ERROR
PARAMETER RPError
Call-barred ::=
ABSTRACT-ERROR
PARAMETER RPError
Illegal-subscriber ::=
ABSTRACT-ERROR
PARAMETER RPError
Illegal-equipment ::=
ABSTRACT-ERROR
PARAMETER RPError
System-failure ::=
ABSTRACT-ERROR
PARAMETER RPError
Facility-not-supported ::=
ABSTRACT-ERROR
PARAMETER RPError
Memory-capacity-exceeded ::=
ABSTRACT-ERROR
PARAMETER RPError
Absent-subscriber ::=
ABSTRACT-ERROR
PARAMETER RPError
MS-busy-for-MT-SMS ::=
ABSTRACT-ERROR
PARAMETER RPError
SMS-lower-layer-capabilities-not-prov ::=
ABSTRACT-ERROR
PARAMETER RPError
Error-in-MS ::=
ABSTRACT-ERROR
PARAMETER RPError
-- SMR-MT-DATA parameters
-- SMR-MT-DATA parameters
RPDataMT ::= SEQUENCE {
mt-priority-request [0] BOOLEAN,
mt-more-messages-to-send [1] BOOLEAN OPTIONAL,
mt-message-reference RP-MR,
-- if more messages to send mechanism is used, the mt-message-reference value
-- must remain unchanged until all the messages to the same destination
-- have been sent.
mt-originating-address SMS-Address,
mt-destination-address SMS-Address,
mt-user-data RP-UD
}
-- SMR-MT-DATA acknowledgement
RPAck ::= SEQUENCE {
message-reference RP-MR
}
RPError ::= SEQUENCE {
msg-waiting-set [1] BOOLEAN,
message-reference RP-MR,
rp-msidsn SMS-Address OPTIONAL
-- must be an international ISDN address
rp-user-data RP-UD OPTIONAL
}
RP-MR ::= [APPLICATION 2] INTEGER (0..255)
RP-UD ::= [APPLICATION 3] OCTET STRING (SIZE (1..164))
-- Definition of Short Message Service address
SMS-Address ::= [APPLICATION 0] SEQUENCE {
address-type INTEGER { unknown-type(0),
international-number(1),
national-number(2),
network-specific-number(3),
short-number(4),
alphanumeric-number(5),
abbreviated-number(6) },
numbering-plan INTEGER { unknown-numbering(0),
iSDN-numbering(1),
data-network-numbering(3),
telex-numbering(4),
national-numbering(8),
private-numbering(9),
ERMES-numbering(10) },
address-value CHOICE {
octet-format
SemiOctetString
-- other formats are for further study
}
}
SemiOctetString ::= OCTET STRING (SIZE(1..10)) -- each octet contains
-- two binary coded
-- decimal digits
-- The SMR-MO-DATA and SMR-ALERT operations
-- SMR-MO-DATA
Forward-MS-Originated-Short-Message ::=
ABSTRACT-OPERATION
ARGUMENT RPDataMO
RESULT RPAck
ERRORS { SC-congestion,
MS-not-SC-Subscriber,
Invalid-Sme-address,
System-failure
}
-- SMR-ALERT
Alert-SC ::=
ABSTRACT-OPERATION
ARGUMENT RPAlertSC
-- SMR-MO-DATA error alternatives
SC-congestion ::=
ABSTRACT-ERROR
PARAMETER RPError
MS-not-SC-Subscriber ::=
ABSTRACT-ERROR
PARAMETER RPError
Invalid-Sme-address ::=
ABSTRACT-ERROR
PARAMETER RPError
System-failure ::=
ABSTRACT-ERROR
PARAMETER RPError
-- Parameters
-- SMR-MO-DATA parameters
RPDataMO ::= SEQUENCE {
mo-message-reference RP-MR,
mo-originating-address SMS-Address,
mo-user-data RP-UD
}
-- SMR-ALERT parameters
RPAlertSC ::= SMS-Address
-- must be an international ISDN address
END
3rd module of 3
RelayProtocol
RelayProtocol { iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) relayProtocol(1) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
-- EXPORTS everything
IMPORTS
-- application service elements and application contexts
aCSE, APPLICATION-SERVICE-ELEMENT, APPLICATION-CONTEXT
FROM Remote-Operations-Notation-extension
{ joint-iso-ccitt remote-operations(4)
notation-extension(2) }
rOSE FROM Remote-Operations-APDUs
{ joint-iso-ccitt remote-operations(4) apdus(1) }
-- object identifiers
id-ac-so, id-ac-st, id-SMRSE, id-as-SMRSE
FROM SMS-UsefulDefinitions
{ iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) usefulDefinitions(0) }
-- abstract service parameters
Forward-MS-Terminated-Short-Message,
Forward-MS-Originated-Short-Message, Alert-SC,
SMR-Bind, SMR-Unbind,
Unknown-subscriber, Teleservice-not-provisioned,
Call-barred, Facility-not-supported, Absent-subscriber,
MS-busy-for-MT-SMS
Invalid-Sme-address, Memory-Capacity-Exceeded,
SMS-lower-layer-capabilities-not-prov, Error-in-MS,
Illegal-subscriber, Illegal-equipment,
System-failure, SC-congestion, MS-not-SC-Subscriber
FROM RelayAbstractService
{ iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) relayAbstractService(2) } ;
aS-ACSE OBJECT IDENTIFIER ::=
{joint-iso-ccitt association-control(2)
abstractSyntax(1) apdus(0) version (1) }
-- Application contexts
-- Two different application contexts are specified:
-- one for the case when the SC BINDs (and UNBINDs),
-- and the other for the case when the MSC BINDs (and UNBINDs).
-- There is only one application service element, however (see "Application service elements" below.)
sC-BINDs-and-UNBINDs
APPLICATION-CONTEXT
APPLICATION-SERVICE-ELEMENTS { aCSE }
BIND SMR-Bind
UNBIND SMR-Unbind
REMOTE OPERATIONS { rOSE }
INITIATOR CONSUMER OF { sMRSE }
ABSTRACT SYNTAXES { id-as-SMRSE , aS-ACSE }
::= id-ac-so
mSC-BINDs-and-UNBINDs
APPLICATION-CONTEXT
APPLICATION-SERVICE-ELEMENTS { aCSE }
BIND SMR-Bind
UNBIND SMR-Unbind
REMOTE OPERATIONS { rOSE }
RESPONDER CONSUMER OF { sMRSE }
ABSTRACT SYNTAXES { id-as-SMRSE , aS-ACSE }
::= id-ac-st
-- Application service elements
sMRSE APPLICATION-SERVICE-ELEMENT
CONSUMER INVOKES { forward-MS-Terminated-Short-Message}
SUPPLIER INVOKES { forward-MS-Originated-Short-Message,
alert-SC }
::= id-SMRSE
-- Remote operations
forward-MS-Terminated-Short-Message
Forward-MS-Terminated-Short-Message
::= 1
-- Note: localValue-words omitted, since they are typically not used, and likely to be removed
-- from the OPERATION and ERROR macros in ROSE.
forward-MS-Originated-Short-Message
Forward-MS-Originated-Short-Message
::= 2
alert-SC Alert-SC
::= 3
-- Remote errors
unknown-subscriber
Unknown-subscriber
::= 1
teleservice-not-provisioned
Teleservice-not-provisioned
::= 11
call-barred Call-barred
::= 13
illegal-subscriber
Illegal-subscriber
::= 9
illegal-equipment
Illegal-equipment
::= 44
system-failure
System-failure
::= 36
facility-not-supported
Facility-not-supported
::= 21
memory-capacity-exceeded
Memory-capacity-exceeded
::= 22
absent-subscriber
Absent-subscriber
::= 29
mS-busy-for-MT-SMS
mS-busy-for-MT-SMS
::= 30
sMS-lower-layers-capabilities-not-prov
SMS-lower-layer-capabilities-not-prov
::= 19
error-in-MS
Error-in-MS
::= 20
sC-congestion
SC-congestion
::= 101
mS-not-SC-Subscriber
MS-not-SC-Subscriber
::= 103
invalid-sme-address
Invalid-sme-address
::=104
END
|
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 have been specified on the session layer and the SMR-UNBIND mapped on that negotiated release. However, the Session negotiated release functional unit requires also the Session half duplex functional unit. The negotiated release functional unit is not used anywhere else in the GSM specifications, hence it was not adopted here either.)
The proper completion of all the SMRSE operations is guarantied by avoiding collisions between SMR‑UNBIND and other operations. This is achieved by following application rules which restrict the invocation of different operations on the association. Two alternative sets of application rules are given in 2.3.1 and 2.3.2 in the sequel; additional sets are possible.
|
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 is negotiated within the SMR-BIND service as follows:
name of parameter value in request and report
operations {sMR-MO-Data-by-MSC,sMR-MT-Data-by-SC, sMR-Alert-by-MSC}
transient FALSE (in report only)
The association is used fully asymmetrically, the parties invoke SMR-MO-DATA, SMR-MT-DATA, and SMR-ALERT operations as needed.
The SMR-UNBIND operation is not normally invoked on the association.
|
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.
Within the SMR-BIND service, only one type of operations is negotiated for use on the association. (As an exception, an association for both SMR-MO-DATA and SMR-ALERT is allowed below.) The operations of that type must be invoked by the initiator of the SMR-BIND. The responder of the SMR-BIND accepts the one type of operations and forces the association transient.
The following is an example of negotiating this within the SMR-BIND service; here, the SMR-MT-DATA operations are to be initiated by the SC.
name of parameter value
iniType short-Message-Service-Centre
respType public-Land-Mobile-Network
operations { sMR-MT-Data-by-SC }
transient TRUE
The association for SMR-MO-DATA or SMR-ALERT is negotiated according to the same principle, the MSC being the initiator of the SMR-BIND.
As an exception to the single type of operations rule, the following SMR-BIND negotiation for both SMR-MO-DATA and SMR-ALERT is allowed in this application rule set:
name of parameter value
iniType public-Land-Mobile-Network
respType short-Message-Service-Centre
operations { sMR-MO-Data-by-MSC, sMR-Alert-by-MSC }
transient TRUE
The association may be used for invoking operations of the negotiated type(s) as long as there are such operations to be invoked. (In other words, until all short messages or/and alerts to that direction have been relayed.)
If SMR-ALERT is not allowed on the association, the SMR-UN-BIND operation may be invoked on the association as soon as all operations on the association have been completed (by REPORT or ERROR). If SMR-ALERT is allowed, a guard time since the last SMR-ALERT invocation (if any) must have elapsed also (to guarantee that the SMR-ALERTs have been processed - there will be no responses).
This set of application rules effectively makes the association asymmetric: all operations are invoked by the same party, hence collisions are not possible.
|
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 protocol connections on top of the transport connection (including the SMR-BIND operation); and
c) the time needed (request to result) for the actual remote operation (SMR-MO-DATA or SMR-MT-DATA) relaying the SM.
If semi-permanent connections are used, only the delay (c) is likely to occur.
As an aid to the organizations discussing these delays in actual implementations, the following time/count-valued constants are defined in the remainder of this section:
T-failure-delay
A/tr-typical-delay
A/tr-failure-delay
A/pe-typical-delay
A/pe-failure-delay
R/MO/1-typical-delay
R/MO/n-typical-delay
R/MO-failure-delay
R/MT-typical-delay
R/MT-failure-delay
R-OK-load
R-error-load
R/MO-OK-outstanding
R/MT-OK-outstanding
The delay (a) is dependent on the network being used. A delay exceeding T-failure-delay when establishing a transient transport connection should be treated as a failure, despite the worst-case delay specification of the network used.
The delay (b) for transient connections is typically A/tr-typical-delay, and a delay exceeding A/tr-failure-delay should be treated as a failure.
The delay (b) for semi-permanent connections is typically A/pe-typical-delay, and a delay exceeding A/pe-failure-delay should be treated as a failure.
The delay (c) for the SMR-MO-DATA service is typically R/MO/1-typical-delay if no other SMR-MO-DATAs are outstanding, and R/MO/n-typical-delay if there are other SMR-MO-DATAs outstanding. In either case, a delay exceeding R/MO-failure-delay should be treated as a failure.
The delay (c) is typically R/MT-typical-delay for the SMR-MT-DATA service (PLMN delays involved), and a delay exceeding R/MT-failure-delay should be treated as a failure.
Concerning throughput and overloading, a SMRSE responder is capable of processing R-OK-load SMRSE operations per minute and properly rejects (via error) up to R-error-load operations per minute if the actual processing throughput is exceeded. (Failing SMR-ALERTs do not cause any response, though.) The maximum number of outstanding SMR-MO-DATA operations on an application association must not exceed R/MO-OK-outstanding, if all operations are to be properly processed. The corresponding limitation for SMR-MT-DATAs is R/MT-OK-outstanding.
|
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 system-failure
FacilityNotSupported facility-not-supported
SystemFailure system-failure
UnexpectedDataValue system-failure
UnidentifiedSubscriber unknown-subscriber
UnkwownSubscriber unknown-subscriber
AbsentSubscriber absent-subscriber
SubscriberBusyForMT-SMS MS-busy-for-MT-SMS
SC - GMSC to MAP
sc-Congestion SM-Delivery-Failure (#4)
invalid-sme-address SM-Delivery-Failure (#5)
ms-not-sc-subscriber SM-Delivery-Failure (#6)
system failure SystemFailure
#0 memory capacity exceeded (MT only)
#1 equipment protocol error (MT only)
#2 equipment not SM equipped (MT only)
#4 SC-Congestion (MO only)
#5 invalid Sme address (MO only)
#6 Subscriber not SC Subscriber (MO only)
|
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 proposes to map application layer protocols ACSE and ROSE via a convergence function to network layers defined by CCITT Recommendations Q.931 and Q.932.
The complexity of dealing with the many different network layer protocols is avoided by mapping the application protocols to the Network Layer Service defined by X.213. ACSE and ROSE are specifically defined in terms of the full OSI stack. The use of ACSE and ROSE is avoided by incorporating the functionality provided by ACSE and ROSE into SMS protocols. The convergence function is therefore embedded in SMS protocols just as the use of ACSE and ROSE is embedded into SMS protocols defined by Section 2.
|
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. This operation reports either success (via SMR-Bind-Confirm) or failure (via SMR-Bind-Failure).
SMR-BIND will be mapped to/from N-CONNECT request/indication with SMR-Bind parameters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets the SMR-Bind parameters may be carried by the first N-DATA request/indication following establishment of the network layer connection - see Section 3.4).
SMR-BIND-CONFIRM:
This operation must be invoked by a party to accept an application association.
SMR-BIND-CONFIRM will be mapped to/from N-CONNECT confirm/response with SMR-BIND-CONFIRM parameters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then SMR-BIND-CONFIRM may be carried as the second N-DATA request/indication following establishment of the network layer connection - see Section 3.4).
SMR-BIND-FAILURE:
This operation must be invoked by a party to reject an attempted application association.
SMR-BIND-FAILURE will be mapped to/from N-DISCONNECT request/indication with SMR‑BIND‑FAILURE parameters carried in NS-user-data (if the network layer does not support NS‑user‑data of 128 octets then SMR-BIND-FAILURE parameters will not be carried by the network layer - i.e. NS‑user‑data will be discarded).
SMR-UNBIND:
This operation must be invoked by a party to release the application association.
SMR-UNBIND will be mapped to/from N-DISCONNECT request/indication with SMR-UNBIND parameters be carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then SMR-UNBIND parameters may be carried by the N-DATA request/indication preceding N-DISCONNECT - see Section 3.4).
SMR-MO-DATA:
This operation may be invoked by the application entity in the GMSC ; it is used to relay one SMS transfer layer PDU from the GMSC to the SC. This operation reports success (via RPAck) or failure (via RPError).
SMR-MO-DATA will be mapped to/from N-DATA request/indication.
SMR-MT-DATA:
This operation may be invoked by the application entity in the SC ; it is used to relay one SMS transfer layer PDU from the SC to the GMSC. This operation reports success (via RPAck) or failure (via RPError) after the full relay attempt to the MS.
SMR-MT-DATA will be mapped to/from N-DATA request/indication.
SMR-ALERT:
This operation may be invoked by the application entity in the GMSC. It is used as the GMSC-to-SC indication of the fact that an MS which was previously unattainable has recovered operation. This operation does not report any outcome.
SMR-ALERT will be mapped to/from N-DATA request/indication.
RPAck:
This operation is invoked by the application entity in the GMSC or the SC ; it is used as the GMSC-to-SC indication that a particular short message has been received by an MS and as the SC-to-GMSC indication that a short message has been received by the SC.
RPAck will be mapped to/from N-DATA request/indication.
RPError:
This operation is invoked by the application entity in the GMSC or the SC ; it is used as the GMSC-to-SC indication that a particular short message has not been successfully received by an MS and is needed as the SC-to-GMSC indication that a short message has not been successfully received by the SC.
RPError will be mapped to/from N-DATA request/indication.
|
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-UsefulDefinitions
SMS-usefulDefinitions { iso identified-organization etsi(040)
mobile-domain(0) gsm-messaging(4)
gsm-sms2(11) usefullDefinitions(0) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
IMPORTS
ID ::= OBJECT IDENTIFIER
-- root for all sms allocations
mobile-domain ID ::= {iso identified-organization etsi(40) mobile-domain(0) }
gsm-messaging
ID ::= { mobile-domain gsm-messaging(4) }
-- categories
gsm-sms2 ID ::= { gsm-messaging 11}
-- modules
usefullDefinitions ID::= {gsm-sms2 0}
relayProtocol ID::= {gsm-sms2 1}
END
2nd module of 2
RelayProtocol
RelayProtocol { iso identified-organization etsi(040)
mobile-domain(0) gsm-messaging(4) gsm-sms2(11)
relayprotocol(1) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
-- EXPORTS everything
-- The SMR-Bind-Parameters will be the User Data field in the N-CONNECT request/indication
-- message.
SMR-Bind-Parameters ::= SEQUENCE {
initiatorID [0] Name,
password [1] Password OPTIONAL,
pswNeeded [2] BOOLEAN,
iniType [3] Telecom-System-Type
}
-- Above and in SMR-Bind-confirm
-- initiatorID/respID identify the initiating/responding telecommunication subsystem
-- password may assist in authentification
-- pswneeded (BIND only) requests password into SMR-Bind SMR-Bind-confirm
-- initype/resptype identify the types of the systems
-- transient (CONFIRM only) forces the association (and the underlying connections) transient : it must be UNBouND as soon as there are no operations to be performed
Name ::= SEQUENCE {
operator [0] Operator OPTIONAL,
bilateralAgreem [1] BilateralAgreem OPTIONAL,
dataNetworkAddress [2] X121Address OPTIONAL,
iSDN Address SMS-Address OPTIONAL
}
-- operator is a text string containing the name of the SC/PLMN operator. bilateralagreem is a text
-- string identifying the bilateral agreement between the SC and the PLMN operators which allows
-- for this association to be established.
-- dataNetworkAddress is the PSPDN X.121 address of the SC/MSC issuing the BIND or
-- CONFIRM, occurring only if a PSPDN is used.
-- iSDNAddress is the PLMN address of the SC as seen by the MSs (same datum in both BIND
-- and CONFIRM).
-- Any pair of subsets of theses parameters may be used to identify the SC and the MSC to one
-- another.
-- upper bound settings
ub-operator-name-length INTEGER ::= 20
ub-agreem-name-length INTEGER ::= 20
ub-X121Address-length INTEGER ::= 15
ub-password-length INTEGER ::= 20
Operator ::= PrintableString (SIZE (0..ub-operator-name-length))
BilateralAgreem ::= PrintableString (SIZE (0..ub-agreem-name-length))
X121Address ::= NumericString (SIZE (0..ub-X121Address-length))
-- Definition of Short Message Service address
SMS-Address ::= [APPLICATION 0] SEQUENCE {
adress-type INTEGER { unknown-type (0),
international-number (1),
national-number (2),
network-specific-number (3),
short-number (4) },
numbering-plan INTEGER {unknown-numbering (0),
iSDN-numbering (1),
data-network-numbering (3),
telex-numbering (4),
national-numbering (8),
private-numbering (9) },
address-value CHOICE {
octet-format
SemiOctetString
-- other formats are for further study
}
}
-- each octet contains two binary coded decimal digits
SemiOctetString ::= OCTET STRING (SIZE (1..10))
Password ::= PrintableString(SIZE(0..ub-password-length))
Telecom-System-Type ::= INTEGER {
short-Message-Service-Centre (0),
public-Land-Mobile-Network (1)
-- Extensions are possible: additional telecommunication subsystems
-- might adopt this service element for their interconnection.
}
-- SMR-Bind-confirm will be the User Data in the N-CONNECT response/confirm message
SMR-Bind-confirm ::= SEQUENCE {
respID [0] Name,
password [1] Password OPTIONAL,
respType [3] Telecom-System-Type,
transient [5] BOOLEAN,
connectTime [6] Time-when-connected
}
-- The following defines the choices and tags for the N-DISCONNECT request/indication User Data.
RELAYdiscs ::= CHOICE {
bindfail [1] SMR-Bind-failure,
unbindreq [2] SMR-Unbind
}
SMR-Bind-failure ::= SEQUENCE {
connect-failure-reason
[0] Connect-failure,
alternative-system
[1] Name OPTIONAL
}
-- connect-failure-reason contains one of the error given in the following table. alternative-system
-- is included when the SC/PLMN operator wishes to indicate that the MSC/SC might try to
-- establish an association with another SC/MSC.
-- Connection Failure Reason
-- not-entitled: The responder is not entitled to accept a request for an association between itself
-- and the initiator.
-- temporary-overload: The responder is not capable of establishing an association due to
-- temporary overload.
-- temporary-failure: The responder is not capable of establishing an association due to a
-- temporary failure (having impact on an entity at SM-RL or at layers above).
-- incorrect-ID-or-password: The responder will not accept the request to establish an association
-- between itself and the initiator due to incorrect identity or password.
-- not-supported: The responder does not recognize the telecommunication subsystem type of the
-- initiator, or cannot support any of the operations suggested on the association.
Connect-failure ::= INTEGER {
not-entitled (0),
temporary-overload (1),
temporary-failure (2),
incorrect-ID-or-password (3),
not-supported (4)
}
SMR-Unbind ::= Time-when-connected
Time-when-connected ::= UTCTime
-- The following defines the choices and tags for the N-DATA request/indication User Data
RELAYapdus ::= CHOICE {
rpdatamt [1] RPDataMT,
rpdatamo [2] RPDataMO,
rpalertsc [3] RPAlertSC,
rpack [4] RPAck,
rperror [5] RPError
}
RPDataMT ::= SEQUENCE {
mt-priority-request [0] BOOLEAN,
mt-more-messages-to-send [1] BOOLEAN OPTIONAL,
mt-message-reference RP-MR,
mt-originating-address SMS-Address,
mt-destination-address SMS-Address,
mt-user-data RP-UD
}
RPDataMO ::= SEQUENCE {
mo-message-reference RP-MR,
mo-originating-address SMS-Address,
mo-user-data RP-UD
}
RP-MR ::= [APPLICATION 2] INTEGER (0..255)
RP-UD ::= [APPLICATION 3] OCTET STRING (SIZE (1..164))
RPAck ::= SEQUENCE {
message-reference RP-MR
}
Error-reason ::= INTEGER {
unknown-subscriber (1),
teleservice-not-provisioned (11),
call-barred (13),
sMS-lower-layer-capabilities-not-prov (19),
error-in-MS (20),
facility-not-supported (21),
memory-capacity-exceeded (22),
absent-subscriber (29),
illegal-subscriber (9),
illegal-equipment (44),
system-failure (36),
sC-congestion (101),
mS-not-SC-Subscriber (103),
invalid-sme-address (104)
}
RPError ::= SEQUENCE {
error-reason Error-reason,
msg-waiting-set BOOLEAN,
message-reference RP-MR
}
RPAlertSC ::= SMS-Address
-- must be an international ISDN address
END
|
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 designated as the entity responsible for re-establishing the association.
Following receipt of N-RESET any unacknowledged SMR-MT-DATA or SMR-MO-DATA will be retransmitted.
|
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 completed via RPAck or RPError and by some guard timer being applied following SMR‑ALERT.
|
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 remain a provider option. The following figures are therefore provided in order to indicate how SMR-BIND, SMR-BIND-CONFIRM and SMR-UNBIND should be mapped to/from an OSI Network Service definition which support 128 bytes of NS-user-data in network connection and network connection release phases.
NOTE 1: SMR-BIND parameters are carried as NS-user-data
NOTE 2: SMR-BIND-CONFIRM is carried in NS-user-data
NOTE 3: SMR-UNBIND parameters are carried as NS-user-data
|
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-operations (SC<--> GMSC/IWMSC) are not part of GSM 09.02, but an addition to be used in the SC-GMSC/IWMSC interface.
To separate the additions from the MAP in GSM 09.02, the additions are herein called SMS-MAP.
The SMS-MAP Operations- and SMS-MAP Signalling Procedures chapters have been divided into subchapters for interworking with MAP version 1, and MAP version 2.
NOTE: MAP version 2 was not finalized when the present document was written. This may imply changes to the SMS-MAP version 2 operations and signalling procedures, when MAP version has been finalized.
|
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. The SMS-MAP protocol terminates in the GMSC for SC originated short message signalling, and in the IWMSC for GSM PLMN originated short message signalling (MAP is used for short message signalling within/between PLMNs).
Application Entity Identification
The SSN for the Service Centre Application Entity enables co-location of an SC and a GSM MAP-AE (e.g. an MSC).
|
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 received by an SMS-MAP network entity, the operation should be rejected with the InvokeProblem set to Unrecognized Operation.
Error handling
- Mistyped Parameter. A Reject with cause Mistyped Parameter is sent in the following cases:
- A parameter tag is not one of those associated with the operation invoked or the type specification corresponding to the parameter tag is violated by the actual value.
- If an SMS-MAP parameter contains a value outside the defined value range.
- If a mandatory parameter is missing in an Invoke component.
- If the parameter contains a value within the defined value range, but has a not permitted value, the UnexpectedDataValue Error is sent.
Basic Encoding Rules for SMS-GMSC
Length octets
Primitive Information Elements:
- definite short form if the actual length is less than 128
- definite long form without leading zero octets if the actual length is greater or equal to 128
Constructed Information Elements
- definite short form if the actual length is less than 128
- definite long form without leading zero octets if the actual length is greater or equal to 128
- indefinite form
Encoding of a boolean value
The boolean is FALSE if the octet is zero.
The boolean is TRUE if the octet has any non-zero value.
SMS-MAP VERSION 1 OPERATIONS
Forward Mobile Terminated Short Message (SC --> GMSC)
Forward Mobile Originated Short Message (IWMSC --> SC)
Service Centre Alert (IWMSC --> SC)
Forward Mobile Terminated Short Message (SC --> GMSC)
Operation Code=250
Class=1
ASN.1 Formal Description
ForwardMTShortMessage ::= OPERATION
PARAMETER SEQUENCE{
msIsdn [0] IMPLICIT IsdnAddressString,
sm-RP-PRI [1] IMPLICIT BOOLEAN,
serviceCentreAddress [2] IMPLICIT IsdnAddressString,
sm-RP-UI SM-RP-UI}
RESULT
ERRORS {UnknownSubscriber,
TeleserviceNotProvisioned,
FacilityNotSupported,
CallBarred,
AbsentSubscriber,
SystemFailure,
UnexpectedDataValue,
MemoryCapacityExceeded,
ErrorInMS,
SMSLowerLayerCapabilitiesNotProvisioned,
IllegalMS}
Comments Invoke Component:
- sm-RP-PRI and sm-RP-UI are not analyzed by the GMSC. They are sent transparently through the GMSC in the SMS-MAP operations Send Routing Information For Short Message (SM-RP-PRI), and Forward Short Message (SM-RP-UI).
- msIsdn is the destinating RP-address, and serviceCentreAddress the originating RP-address.
- serviceCentreAddress is accepted only in international E.164 number format.
- msIsdn is accepted only in national or international E.164 number format.
Comments Error Component:
- The UnexpectedDataValue error is sent when the serviceCentreAddress is not international E.164 number, msIsdn is not national or international E.164 number.
Mapping of errors between the Send Routing Information For Short Message (MAP) and Forward Mobile Terminated Short Message (SMS-MAP) operations
Send Routing Information For Forward Mobile Terminated
Short Message (MAP) Short Message (SMS-MAP)
Error Component received by Error Component to be sent by GSMC
GMSC:
UnknownSubscriber UnknownSubscriber
CallBarred CallBarred
TeleServiceNotProvisioned TeleServiceNotProvisioned
AbsentSubscriber AbsentSubscriber
(MWD-SET=TRUE if the SC-Address already is included in the MWD-list in HLR.)
FacilityNotSupported FacilityNotSupported
SystemFailure SystemFailure
DataMissing SystemFailure
UnexpectedDataValue SystemFailure
Reject component received SystemFailure
Abort indication received SystemFailure
Operation Timeout SystemFailure
Mapping of errors between the Forward Short Message (MAP) and Forward Mobile Terminated Short Message (SMS-MAP) operations
Forward Short Message Forward Mobile Terminated
(MAP) Short Message (SMS-MAP)
Error component received by Error component to be sent by GMSC:
GMSC:
AbsentSubscriber AbsentSubscriber
(If the Set MWD (GMSC --> HLR) successful, AbsentSubscriber with MWD-SET=TRUE is sent towards the SC.)
FacilityNotSupported FacilityNotSupported
IllegalMS IllegalMS
SystemFailure SystemFailure
UnexpectedDataValue SystemFailure
UnidentifiedSubscriber SystemFailure
SM-DeliveryFailure
with cause
memoryCapacityExceeded (0) MemoryCapacityExceeded
msProtocolError (1) ErrorInMS
msNotEquiped (2) SMSLowerLayersCapabilities-NotProvisioned
unknownServiceCentre (3) Not applicable for MT-SMS
scCongestion (4) Not applicable for MT-SMS
invalidSmeAddress (5) Not applicable for MT-SMS
msNotScSubscriber (6)) Not applicable for MT-SMS
Reject component received:
with cause
'Unrecognized Operation' FacilityNotSupported
other Reject reason SystemFailure
Abort indication received SystemFailure
Operation Timeout SystemFailure
Forward Mobile Originated Short Message (IWMSC --> SC)
Operation Code=249
Class=1
ASN.1 Formal Description
ForwardMOShortMessage ::= OPERATION
PARAMETER SEQUENCE{
msIsdn [2]IsdnAddressString,
serviceCentreAddress [4]IsdnAddressString,
sm-RP-UI SM-RP-UI}
RESULT
ERRORS {SC-Congestion,
MSNotSCSubscriber,
InvalidSMEAddress,
UnexpectedDataValue}
Comments Invoke Component:
- msIsdn is the originating RP-address.
- serviceCentreAddress is an international E.164 number.
Mapping of errors between the Forward Mobile Originated Short Message (SMS-MAP) and Forward Short Message (MAP)
Forward Mobile Originated Forward Short Message (MAP)
Short Message (SMS-MAP)
Error component received Error component to be sent
by IWMSC: by IWMSC:
SC-Congestion SM-DeliveryFailure with Cause:
SC-Congestion
MSNotSCSubscriber SM-DeliveryFailure with Cause:
msNotSCSubscriber
InvalidSMEAddress SM-DeliveryFailure with Cause:
invalidSMEAddress
UnexpectedDataValue SystemFailure
Reject component received:
with cause
'Unrecognized Operation' SystemFailure
other Reject reason SystemFailure
Abort indication received SystemFailure
Operation Timeout SystemFailure
Service Centre Alert (IWMSC --> SC)
Operation Code=251
Class=4
ASN.1 Formal Description
ServiceCentreAlert ::= OPERATION
PARAMETER SEQUENCE{
msIsdn IsdnAddressString,
serviceCentreAddress IsdnAddressString}
Comments Invoke Component:
- serviceCentreAddress is an international E.164 number.
- msIsdn is a national or an international E.164 number depending on in what kind of form it is received from the HLR.
SMS-MAP VERSION 2 OPERATIONS
Forward Mobile Terminated Short Message (SC --> GMSC)
Forward Mobile Originated Short Message (IWMSC --> SC)
Service Centre Alert (IWMSC --> SC)
Inform Service Centre (IWMSC --> SC)
Forward Mobile Terminated Short Message (SC --> GMSC)
Operation Code=250
Class=1
ASN.1 Formal Description
ForwardMTShortMessage ::= OPERATION
PARAMETER SEQUENCE{
msIsdn [0] IMPLICIT IsdnAddressString,
sm-RP-PRI [1] IMPLICIT BOOLEAN,
serviceCentreAddress [2] IMPLICIT IsdnAddressString,
sm-RP-UI SM-RP-UI,
moreMessagesToSend NULL OPTIONAL}
RESULT
ERRORS {UnknownSubscriber,
TeleserviceNotProvisioned,
CallBarred,
FacilityNotSupported,
AbsentSubscriber,
SystemFailure,
UnexpectedDataValue,
MemoryCapacityExceeded,
ErrorInMS,
SMSLowerLayerCapabilitiesNotProvisioned}
Comments Invoke Component:
- sm-RP-PRI and sm-RP-UI are not analysed by the GMSC. They are sent transparently through the GMSC in the SMS-MAPoperations Send Routing Information For Short Message (SM-RP-PRI),and Forward Short Message (SM-RP-UI).
- msIsdn is the destinating RP-address, and serviceCentreAddress theoriginating RP-address.
- serviceCentreAddress is accepted only in international E.164 number format.
- msIsdn is accepted only in national or international E.164 number format.
- The moreMessagesToSend parameter indicates if more mobile terminatedShort Messages shall be sent on the opened dialogue (transaction). This controls which message the visited MSC shall report the operation outcome in, Continue or End (see chapter: SMS-MAP Signalling Sequences, SMS-MAP Version 2).
Comments Error Component:
- Error UnexpectedDataValue is sent when serviceCentreAddress is not international E.164 number, msIsdn is not national or international E.164 number.
Mapping of errors between the Send Routing Information For Short Message (MAP) and Forward Mobile Terminated Short Message (SMS-MAP) operations
Send Routing Information For Forward Mobile Terminated
Short Message (MAP) Short Message (SMS-MAP)
Error Component received by Error Component to be sent by GMSC:
GMSC:
UnknownSubscriber UnknownSubscriber
CallBarred CallBarred
TeleServiceNotProvisioned TeleServiceNotProvisioned
AbsentSubscriber AbsentSubscriber (May be sent together with an Inform-SC invoke component, See Note 1.)
FacilityNotSupported FacilityNotSupported
SystemFailure SystemFailure
DataMissing SystemFailure
UnexpectedDataValue SystemFailure
Reject component received SystemFailure
Abort indication received SystemFailure
Operation Timeout SystemFailure
NOTE 1: The AbsentSubscriber error is empty in MAP-version 2. has been included in the MWD-list. These two components are grouped together in the same MAP-message. The same principle will be used in SMS-MAP, i.e. the AbsentSubscriber will be empty, and if received, the Inform-SC operation will be invoked towards the SC.
Mapping of errors between the Forward Short Message (MAP) and Forward Mobile Terminated Short Message (SMS-MAP)operations
Forward Short Message Forward Mobile Terminated
(MAP) Short Message (SMS-MAP)
Error component received by Error component to be sent by GMSC:
GMSC:
UnidentifiedSubscriber SystemFailure
(May be sent together with an Inform-SC invoke component,
See Note 2.)
AbsentSubscriber AbsentSubscriber
(May be sent together with an Inform-SC invoke component, See Note 2.)
FacilityNotSupported FacilityNotSupported
DataMissing SystemFailure
SystemFailure SystemFailure
UnexpectedDataValue SystemFailure
SM-DeliveryFailure
(with cause
memoryCapacityExceeded (0), MemoryCapacityExceeded
(May be sent together with an Inform-SC invoke component. See Note 2.)
msProtocolError (1), ErrorInMS
msNotEquiped (2), SMSLowerLayersCapabilities-NotProvisioned
unknownServiceCentre (3), Not applicable for MT-SMS
scCongestion (4), Not applicable for MT-SMS
invalidSmeAddress (5), Not applicable for MT-SMS
msNotScSubscriber (6)) Not applicable for MT-SMS
Reject component received:
with cause
Unrecognized Operation' FacilityNotSupported
other Reject reason SystemFailure
Abort indication received SystemFailure
Operation Timeout SystemFailure
NOTE 2: If one of the three following errors:
1) SM-DeliveryFailure with cause memoryCapacityExceeded
2) UnidentifiedSubscriber
3) AbsentSubscriber
is returned by the visited MSC to the GMSC, the Set MWD operation may be invoked towards HLR. If the outcome is successful, an Inform-SC invoke component should be sent together with the appropriate error component from the GMSC to the SC (see mapping above). Note that Inform-SC is not sent from HLR as a response to the Set MWD procedure (as in the Send Routing Info For SM case), and must be generated by the GMSC, if the Set MWD procedure is successful.
Forward Mobile Originated Short Message (IWMSC --> SC)
Operation Code=249
Class=1
ASN.1 Formal Description
ForwardMOShortMessage ::= OPERATION
PARAMETER SEQUENCE{
msIsdn [2] IsdnAddressString,
serviceCentreAddress [4] IsdnAddressString,
sm-RP-UI SM-RP-UI}
RESULT
ERRORS {SC-Congestion,
MSNotSCSubscriber,
InvalidSMEAddress,
UnexpectedDataValue}
Comments Invoke Component:
- msIsdn is the originating RP-address.
- serviceCentreAddress is an international E.164 number.
Mapping of errors between the Forward Mobile Originated Short Message (SMS-MAP) and Forward Short Message (MAP)
Forward Mobile Originated Forward Short Message (MAP)
Short Message (SMS-MAP)
Error component received Error component to be sent
by IWMSC: by IWMSC:
SC-Congestion SM-DeliveryFailure with Cause:
SC-Congestion
MSNotSCSubscriber SM-DeliveryFailure with Cause:
msNotSCSubscriber
InvalidSMEAddress SM-DeliveryFailure with Cause:
invalidSMEAddress
UnexpectedDataValue SystemFailure
Reject component received:
with cause
'Unrecognized Operation SystemFailure
other Reject reason SystemFailure
Abort indication received SystemFailure
Operation Timeout SystemFailure
Service Centre Alert (IWMSC --> SC)
Operation Code=251
Class=1
ASN.1 Formal Description
ServiceCentreAlert::= OPERATION
PARAMETER SEQUENCE{
msIsdn IsdnAddressString,
serviceCentreAddress IsdnAddressString}
RESULT
ERRORS {SystemFailure,
DataMissing,
UnexpectedDataValue}
Comments Invoke Component:
- serviceCentreAddress is an international E.164 number.
- msIsdn is a national or an international E.164 number dependingon in what kind of form it is received from the HLR.
NOTE: Alert Service Centre has been changed to a Class3 operation in version 2.
Inform Service Centre (IWMSC --> SC)
Operation Code=248
Class=4
ASN.1 Formal Description
InformServiceCentre ::= OPERATION
PARAMETER SEQUENCE{
msIsdn IsdnAddressString OPTIONAL,
mwStatus MWStatus OPTIONAL)
This operation is sent to an SC to report if a subscriber has been included in the MWD-list in HLR, what MSISDN that is stored (only included if the MSISDN in the Send Routing Information For SM differs from an already stored MSISDN in the MWD-list), and report the status of the MCEF and MNRF flags in HLR. The invoke component is always grouped with an error component of the Forward Mobile Terminated Short Message operation when sent to an SC. Which error component, is described in the Mapping of Errors chapters for the Forward Mobile Terminated Short Message operation.
Comments Invoke Component:
- msIsdn is a national or an international E.164 number depending on in what kind of form it is received from the HLR.
|
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 Procedure
Forward Mobile Originated Short Message Procedure
Service Centre Alert Procedure
SMS-MAP VERSION 2 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
Operation = Inform-SC
Timer: T-insc
Value: 5-10 s
Forward Mobile Terminated Short Message Procedure
NOTE: If the 'moreMessagesToSend' flag is set to TRUE in the Forward Mobile Terminated SM invoke component, theResult component shall be sent in a Continue message.If it is set to FALSE, in an End message.
Forward Mobile Originated Short Message Procedure
Service Centre Alert Procedure
Inform-Service Centre Procedure
NOTE: The Inform-SC invoke component is always grouped with an error component of Forward Mobile Terminated Short Message operation, when sent to an SC. Which error component, is decsribed in the Mapping of Errors chapters for the Forward Mobile Terminated Short Message operation.
|
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 indicating the reason may be provided.
Error Code Value = 13
ASN.1 Formal Description
CallBarred ::= ERROR
Parameter
cause ENUMERATED {barringServiceActive (0),
operatorBarring (1)} - optional
- ErrorInMS
This error is returned if a terminated short message transfer fails due to an error in the MS, e.g. protocol error.
Error Code Value = 50
ASN.1 Formal Description
ErrorInMS ::= ERROR
- FacilityNotSupported
This error is returned due to no provision of the short message service in the VPLMN.
Error Code Value = 21
ASN.1 Formal Description
FacilityNotSupported ::= ERROR
- MemoryCapacityExceeded
This error is returned if an MS has no memory capacity available to receive a mobile terminated short message.
Error Code Value = 52
ASN.1 Formal Description
MemoryCapacityExceeded ::= ERROR
- MSNotSCSubscriber
This error is returned if an MS that originates a short message to a certain SC, is not a subscriber in this SC.
Error Code Value = 54
ASN.1 Formal Description
MSNotSCSubscriber ::= ERROR
- IllegalMS
This error is returned if the authentication procedure towards an MS fails.
Error Code Value = 9
ASN.1 Formal Description
IllegalMS ::= ERROR
- InvalidSMEAddress
This error is returned by an SC if the SME-Address included in a mobile originated short message is invalid (syntactically incorrect).
Error Code Value = 55
ASN.1 Formal Description
IllegalMS ::= ERROR
- SC-Congestion
This error is returned by an SC if congestion occurs at reception of a mobile originated short message.
Error Code Value = 53
ASN.1 Formal Description
SC-Congestion ::= ERROR
- SMSLowerLayersCapabilitiesNotProvisioned
This error is returned if a mobile terminated short message transfer fails due to failure in the lower layers, e.g. due to information contained in the Classmark, or the MSC not being able to establish a SAPI=3 connection towards the MS.
Error Code Value = 51
ASN.1 Formal Description
SMSLowerLayersCapabilitiesNotProvisioned ::= ERROR
- SystemFailure
This error is returned by any network entity, when it cannot perform an operation due to failure in another entity.
Error Code Value = 34
ASN.1 Formal Description
SystemFailure ::= ERROR
Parameter NetworkResource OPTIONAL
NetworkResource should be set to the id of the entity responsible for the system failure condition.
- TeleserviceNotProvisioned
This error is returned if the given msIsdn number does not comprise the indicated short message service.
Error Code Value = 11
ASN.1 Formal Description
TeleserviceNotProvisioned ::= ERROR
No parameters.
- UnexpectedDataValue
This error is returned by any network entity, when a parameter with an unexpected data value, without type violation is received, or when an optional element appears when it is not needed in the context.
Error Code Value = 36
ASN.1 Formal Description
UnexpectedDataValue ::= ERROR
- UnknownSubscriber
This error is returned when an HLR is requested to perform an operation and no IMSI or msIsdn has been allocated in HLR for the subscriber (forwarded from GMSC to SC when this error is received by an HLR).
Error Code Value = 1
ASN.1 Formal Description
UnknownSubscriber ::= ERROR
VERSION 1 SPECIFIC ERRORS
- AbsentSubscriber
This error is returned when the subscriber is detached or not reachable. A parameter indicating whether or not the serviceCentreAddress has been included in the HLR message waiting list may be included.
Error Code Value = 27
ASN.1 Formal Description
AbsentSubscriber ::= ERROR
mwd-Set BOOLEAN OPTIONAL
VERSION 2 SPECIFIC ERRORS
- AbsentSubscriber
This error is returned when the subscriber is detached or not reachable.
Error Code Value = 56
ASN.1 Formal Description
AbsentSubscriber ::= ERROR
|
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: Extension indicator
1 No extension
- Bit 7-5: Nature of address indicator
001 international number
010 national significant number
- Bit 4-1: Numbering plan indicator
0001 ISDN/Telephony Number Plan (REC E.164)
b) Subsequent octets representing address digits encoded as a TBCD-STRING parameter.
IsdnAddressString
ASN.1 Formal Description
IsdnAddressString ::= AddressString (SIZE (1..10))
Max Length = 10 octets
Coded as AddressString, but with a maximum length of 10 octets.
NetworkResource
ASN.1 Formal Description
NetworkResource ::= ENUMERATED{
pLMN (0),
hLR (1),
vLR (2),
previous-VLR (3),
controlling-MSC (4),
vMSC (5),
eIR (6),
radioSubsystem (7)}
Max Length = 1 octet
SM-RP-UI
(SM-RP-UI will be sent transparently through SMS-GMSC.)
ASN.1 Formal Description
SM-RP-UI ::= OCTET STRING (SIZE (1..maxSignalInfoLength))
maxSignalInfoLength INTEGER ::= 200 octets *
TBCD-String
ASN.1 Formal Description
TBCD-STRING ::= OCTET STRING
- digits 0 to 9, two digits per octet,
- each digit encoded 0000 to 1001,
- 1111 used as filler when there is an odd number of digits.
Bit 4 to 1 of octet n encoding digit 2(n-1)+1
Bit 8 to 5 of octet n encoding digit 2n
VERSION 2 SPECIFIC DATA TYPES
MWStatus
ASN.1 Formal Description
MWStatus ::= OCTET STRING (SIZE 1)
- bits 4-7: 0000 (not used)
- bits 2-3: status of MW flags
- 00 not set
- 01 MNRF set
- 10 MCEF set
- 11 MCEF and MNRF set
- bit 1: status of MWD
- 0 SC address not included
- 1 SC address included
|
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 classes 2 and 5 are replaced by TCAP operation classes 1 and 4 respectively.
- TCAP provides a connectionless service. The services provided by SMR-BIND, SMR-BIND-CONFIRM, SMR-BIND-FAILURE and SMR-UNBIND are therefore not required and Sections 2.3 and 2.4 are not applicable.
Annex A (informative):
Change Request History
Change history
SMG No.
TDoc. No.
CR. No.
Section affected
New version
Subject/Comments
SMG#08
4.2.0
ETSI Publication
SMG#18
244/96
A005
4.4.0
Missing Parameters
SMG#20
5.0.0
Release 1996 version
SMG#27
6.0.0
Release 1997 version
SMG#29
7.0.0
Release 1998 version
History
Document history
V7.0.0
August 1999
Publication
|
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 purpose of fulfilling the service requirements of the primitives specified for the CBC - BSC interface in GSM 03.41.
One approach is based upon the use of the complete OSI reference model (see X.200), another approach is based upon the use of only the lower 3 OSI layers, and another approach is based upon the use of CCITT Signalling System No. 7 (see Q.700).
Specifications are based upon individual contributions. Any judgement concerning functionality, completeness and advantages/disadvantages of implementation is intentionally omitted.
|
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.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
[2] GSM 03.41: "Digital cellular telecommunications system (Phase 2+); Technical realization of Short Message Service Cell Broadcast (SMSCB)".
[3] GSM 12.20: "Digital cellular telecommunication system (Phase 2); Network Management (NM) procedures and messages".
[4] CCITT Recommendation Q.700: "Introduction to CCITT Signalling System No.7".
[5] CCITT Recommendation Q.931: Integrated services digital network.(ISDN) User-Network interface layer 3 specification for basic control".
[6] CCITT Recommendation Q.932: "Generic procedures for the control of ISDN supplementary services".
[7] CCITT Recommendation Q.941: "ISDN user-network interface protocol profile for management".
[8] CCITT Recommendation Q.1400: "Architecture framework for the development of signalling and organisation, administration and maintenance protocols using OSI concepts".
[9] CCITT Recommendation X.2 (1988): "International data transmission services and optional user facilities in public data networks and ISDNs".
[10] CCITT Recommendation X.200: "Reference Model of Open Systems Interconnection for CCITT Applications".
[11] CCITT Recommendation X.213: "Information technology - Network service definition for Open Systems Interconnection".
[12] CCITT Recommendation X.215: "Session service definition for open systems interconnection for CCITT applications".
[13] CCITT Recommendation X.217: "Association control service definition for open systems interconnection for CCITT applications".
[14] CCITT Recommendation X.219: " Remote operations: model, notation and service definition".
[15] CCITT Recommendation X.225: "Session protocol specification for Open Systems Interconnection for CCITT Applications".
[16] CCITT Recommendation X.227: "Information technology - Open Systems Interconnection - protocol specification for the association".
[17] CCITT Recommendation X.229: "Remote operations Protocol specification".
[18] GSM 10.01: "Digital cellular telecommunication system (Phase 2+); GSM features and releases"
|
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 application layer protocols ACSE and ROSE via a convergence function to network layers defined by CCITT Recommendations Q.931 and Q.932.
The complexity of dealing with the many different network layer protocols is avoided by mapping the application protocols to the Network Layer Service defined by X.213. ACSE and ROSE are specifically defined in terms of the full OSI stack. The use of ACSE and ROSE is avoided by incorporating the functionality provided by ACSE and ROSE into the CBS protocol. The convergence function is embedded in the CBS protocol.
|
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 used. This operation reports either success (via CBSE-Bind-Confirm) or failure (via CBSE-Bind-Failure).
CBSE-BIND will be mapped to/from N-CONNECT request/indication with CBSE-BIND parameters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then CBSE-BIND parameters may be carried by the first N-DATA request/indication following establishment of the network layer connection - see subclause 2.4).
This operation is retained for backward compatibility with Phase 2 systems.
NOTE: This PDU should be used in the case of a Phase 2+ entity communicating with a Phase 2 entity.
CBSE-VBIND
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 used. This operation reports either success (via CBSE-Bind-Confirm) or failure (via CBSE-Bind-Failure).
CBSE-VBIND will be mapped to/from N-CONNECT request/indication with CBSE-VBIND parameters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then CBSE-VBIND parameters may be carried by the first N-DATA request/indication following establishment of the network layer connection - see subclause 2.4).
This operation is used in Phase 2+ systems.
CBSE-BIND-CONFIRM
This operation must be invoked by a party to accept an application association.
CBSE-BIND-CONFIRM will be mapped to/from N-CONNECT confirm/response with CBSE-BIND-CONFIRM parameters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then CBSE-BIND-CONFIRM may be carried as the second N-DATA request/indication following establishment of the network layer connection - see Section 2.4).
On receipt of a CBSE-BIND PDU, the recipient must assume that the sender is supporting the Phase 2 version of the interface and must reply with an untagged CBSE-BIND-CONFIRM. If a CBSE-VBIND PDU is received, the recipient must reply with a tagged CBSE-BIND-CONFIRM as a substructure of CBSEapdus.
CBSE-BIND-FAILURE
This operation must be invoked by a party to reject an attempted application association.
CBSE-BIND-FAILURE will be mapped to/from N-DISCONNECT request/indication with CBSE-BIND-FAILURE parameters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then CBSE-BIND-FAILURE parameters shall be carried by the N-DATA request/indication preceding N-DISCONNECT.
GSM phase2 compliance:
If the network layer does not support NS-user-data of 128 octets then CBSE-BIND-FAILURE parameters will not be carried by the network layer - i.e. NS-user-data will be discarded).
CBSE-UNBIND
This operation must be invoked by a party to release the application association.
CBSE-UNBIND will be mapped to/from N-DISCONNECT request/indication with CBSE-UNBIND parameters be carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then CBSE-UNBIND parameters shall be carried by the N-DATA request/indication preceding N-DISCONNECT - see Section 2.4 ).
GSM phase 2 compliance:
If the network layer does not support NS-user-data of 128 octets then reception of N-DISCONNECT shall be interpreted as a CBSE-UNBIND even if the N-DISCONNECT is not preceded by a N-DATA packet carrying the CBSE-UNBIND parameters.
$start$(Phase2PBscCellLists)$
CBSE-WRITE-REPLACE, CBSE-KILL, CBSE-REPORT,
CBSE-STATUS-CBCH-QUERY, CBSE-STATUS-CBCH-QUERY-RESP, CBSE-STATUS-MESS-QUERY, CBSE-STATUS-MESS-QUERY-RESP, CBSE-REJECT, CBSE-RESTART-IND, CBSE-RESTART-IND-PHASE2P, CBSE-RESET, CSE-FAILURE-IND, CSE-FAILURE-IND-PHASE2P, CBSE-SET-DRX, CBSE-SET-DRX-RESP
Application data units CBSE-WRITE-REPLACE, CBSE-KILL, CBSE-REPORT, CBSE-STATUS-CBCH-QUERY, CBSE-STATUS-CBCH-QUERY-RESP, CBSE-STATUS-MESSAGE-QUERY, CBSE-STATUS-MESS-QUERY-RESP., CBSE- REJECT, CBSE -RESTART-IND, CBSE -RESTART-IND-PHASE2P, CBSE-RESET, CBSE-FAILURE-IND, CBSE-FAILURE-IND-PHASE2P, CBSE-SET-DRX, CBSE-SET-DRX-RESP provide the services specified via primitives Write-Replace, Kill, Report, Status-CBCH, Status-CBCH-Response, Status-Message, Status-Message-Response, Reject, Restart-Indication, Restart-Indication-Phase2P, Reset, Failure-Indication, Failure-Indication-Phase2P, Set-DRX and Set-DRX-Response respectively in GSM 03.41.
$end$(Phase2PBscCellLists)$
These application data units will be mapped to/from N-DATA request/indication.
|
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 IDENTIFIER
mobile-domain ID ::= {ccitt identified-organization (4) etsi (0) mobile-domain(0)}
-- root for all sms allocations
gsm-messaging ID ::= { mobile-domain gsm-messaging(4) }
-- categories
gsm-sms3 ID ::= { gsm-messaging 12 }
END
2nd module of 2:
Application Protocol
ApplicationProtocol {
ccitt identified-organization (4) etsi (0) mobile-domain(0)
gsm-messaging(4) gsm-sms3 (12) applicationProtocol(11) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
-- CBSE-BIND will be carried as N-CONNECT request/indication
-- CBSE-BIND-Parameters will carried in the User Data field of the N-CONNECT
-- request/indication message.
-- Note that this structure should be used by Phase 2 systems only.
CBSE-BIND-Parameters ::= SEQUENCE {
initiatorID [0] Name,
password [1] Password OPTIONAL
}
-- Above and in CBSE-BIND-CONFIRM
-- initiatorID/respID: identify the initiating/responding telecommunication subsystem
-- password: may assist in authentication
-- CBSE-VBIND-Parameters will only be used as an element of CBSEapdus in the
-- User Data field of the N-CONNECT request/indication message.
-- Note that this structure should be used by Phase 2+ and higher systems only.
CBSE-VBIND-Parameters ::= SEQUENCE {
initiatorID [0] Name,
password [1] Password OPTIONAL,
version [2] Version
}
-- Above
-- initiatorID/respID: identify the initiating/responding telecommunication subsystem
-- password: may assist in authentication
-- version: identify the interface version supported, defined below
Name ::= SEQUENCE {
operator [0] Operator OPTIONAL,
bilateralAgreem [1] BilateralAgreem OPTIONAL,
dataNetworkAddress [2] Xl2lAddress OPTIONAL,
iSDNAddress [3] CBS-Address OPTIONAL
}
-- operator is a text string containing the name of the CBC/PLMN operator. bilateralagreem is a text
-- string identifying the bilateral agreement between the CBC and the PLMN operators which allows
-- for this association to be established.
-- dataNetworkAddress is the PSPDN X.121 address of the CBC/BSC issuing the BIND or
-- CONFIRM, occurring only if a PSPDN is used.
-- iSDNAddress is the PLMN address of the CBC (same datum in both BIND and CONFIRM).
-- Any pair of subsets of these parameters may be used to identify the CBC and the BSC to one
-- another.
-- upper bound settings
Operator ::= PrintableString (SIZE (0..20))
BilateralAgreem ::= PrintableString (SIZE (0 .. 20))
Xl2lAddress ::= NumericString (SIZE(0..15))
-- Definition of Cell Broadcast Short Message Service address
CBS-Address ::= [APPLICATION 0] SEQUENCE {
address-type INTEGER { unknown-type(0),
international-number(1),
national-number(2),
network-specific-number(3),
short-number(4) },
numbering-plan INTEGER { unknown-numbering(0),
iSDN-numbering(1),
data-network-numbering(3),
telex-numbering(4),
national-numbering(8),
private-numbering(9) },
address-value CHOICE {
octet-format
SemiOctetString
-- other formats are for further study
}
}
-- each octet contains two binary coded decimal digits
SemiOctetString ::= OCTET STRING (SIZE(1..10))
Password ::= PrintableString (SIZE(0..20))
-- Version provides one of the indications given in the following table.
-- Any future substantive interface definition changes must be added to this table.
Table 1
Version indication
Document Version
Compatible with previous version
release-97
This mandates adherence to 03.49 version 6.0.0.
No (see Note 1)
reserved-1
reserved-2
reserved-3
reserved-4
reserved-5
reserved-6
Note 1: PDUs not backwards compatible with Phase 2 include, but may not be limited to, Report, Reject, Status-CBCH-Resp, and Status-Mess-Resp.
Version ::= INTEGER {
release-97 (0),
reserved-1 (1),
reserved-2 (2),
reserved-3 (3),
reserved-4 (4),
reserved-5 (5),
reserved-6 (6)
}
-- CBSE-BIND-CONFIRM will carried as N-CONNECT response/confirm
-- CBSE-BIND-CONFIRM parameters will be carried in User Data of the N-CONNECT
-- response/confirm message
CBSE-BIND-CONFIRM-Parameters ::= SEQUENCE {
respId [0] Name,
password [1] Password OPTIONAL
}
-- The following defines the choices and tags for the N-DISCONNECT.request/indication User Data.
Applic-protocol-discs ::= CHOICE {
bindfail [1] CBSE-BIND-FAILURE,
unbindreq [2] CBSE-UNBIND
}
CBSE-BIND-FAILURE ::= Connect-failure-reason
-- connect-failure-reason provides one of the error indications given in the following table.
Table 2
Error indications
Reason
not-entitled
The responder is not entitled to accept a request for an association between itself and the initiator.
temporary-overload
The responder is not capable of establishing an association due to temporary overload.
temporary-failure
The responder is not capable of establishing an association due to a temporary failure.
incorrect-ID-or-password
The responder will not accept the request to establish an association between itself and the initiator due to incorrect identity or password.
version-unsupported
The version specified is not supported by the recipient.
--
Connect-failure-reason ::= INTEGER {
not-entitled (0),
temporary-overload (1),
temporary-failure (2),
incorrect-ID-or-password (3),
version-unsupported (4)
}
CBSE-UNBIND ::= NULL
-- The following defines the choices and tags for the N-DATA.request/indication User Data
CBSMSEapdus ::= CHOICE {
cbse-WRITE-REPLACE [1] Write-Replace,
cbse-KILL [2] Kill,
cbse-REPORT [3] Report,
cbse-STATUS-CBCH-QUERY [4] Status-CBCH,
cbse-STATUS-CBCH-QUERY-RESP [5] Status-CBCH-Resp,
cbse-STATUS-MESSAGE-QUERY [6] Status-Message,
cbse-STATUS-MESS-QUERY-RESP [7] Status-Mess-Resp,
cbse-REJECT [8] Reject,
cbse-RESTART-IND [9] Restart-Ind,
cbse-RESET [10] Reset,
cbse-FAILURE-IND [11] Failure-Ind,
cbse-SET-DRX [12] Set-DRX,
cbse-SET-DRX-RESP [13] Set-DRX-Resp,
cbse-VBIND [14] CBSE-VBIND-Parameters,
cbse-BIND-CONFIRM [15] CBSE-BIND-CONFIRM-Parameters,
cbse-BIND-FAILURE [16] CBSE-BIND-FAILURE,
cbse-UNBIND [17] CBSE-UNBIND,
cbse-RESTART-IND-PHASE2P [18] Restart-Ind-Phase2P, -- $(Phase2PBscCellLists)$
cbse-FAILURE-IND-PHASE2P [19] Failure-Ind-Phase2P -- $(Phase2PBscCellLists)$
}
-- PDU parameter definitions from 03.41
Message-Identifier ::= INTEGER (0 .. 65535)
Serial-Number ::= INTEGER (0 .. 65535)
No-of-Pages ::= INTEGER (1 .. 15)
Cell-List ::= SEQUENCE {
length INTEGER, -- number of cells in the list
disc Cell-Id-Disc,
list SEQUENCE OF Cell-Id
}
Channel ::= INTEGER {
basic-channel (0),
extended-channel (1)
}
Category ::= INTEGER {
high-priority (0),
normal-priority (1),
background (2)
}
Repetition-Period ::= INTEGER (1 .. 1024)
No-of-Broadcast-Req ::= INTEGER (0 ..65535)
No-of-Broadcasts-Compl-List ::= SEQUENCE OF SEQUENCE {
cell-id Cell,
no-of-broadcasts-compl INTEGER,
no-of-broadcasts-compl-info No-of-Broadcasts-Compl-Info-Type OPTIONAL
}
Cell-Id ::= OCTET STRING (SIZE(4))
-- Note:
-- If Cell-Id-Disc equals ciOnly then only the last 2 octets of
-- Cell-ID are to be considered
-- If Cell-Id-Disc equals lacOnly then only the first 2 octets of
-- Cell-ID are to be considered. The unused octets are filler octets
-- If Cell-Id-Disc equals allCells, Cell-ID only contains filler octets
Schedule-Period ::= INTEGER (0 .. 40)
Reserved-Slots ::= INTEGER (0 .. 40)
Failure-List ::= SEQUENCE OF SEQUENCE {
cell-id Cell,
cause Failure-Reason,
diagnostic Diagnostic-Info OPTIONAL
}
Cbch-Loading-List ::= SEQUENCE OF SEQUENCE{
cell-id Cell,
cbch-loading Cbch-Loading
-- indicates the predicted short term load, expressed as a percentage
-- (min:0, max: 100)
}
Cbch-Loading ::= INTEGER(0..100)
Failure-Reason ::= INTEGER {
parameter-not-recognised (0),
unused-failure-reason-1 (1), -- not used
parameter-value-invalid (2),
valid-CBS-message-not-identified (3),
cell-identity-not-valid (4),
unrecognised-primitive (5),
missing-mandatory-element (6),
bss-capacity-exceeded (7),
cell-memory-exceeded (8),
bss-memory-exceeded (9),
unspecifed-error (10),
incompatible-DRX-parameter (11),
unused-failure-reason-12 (12), -- not used
cell-broadcast-not-supported (13),
cell-broadcast-not-operational (14),
extended-channel-not-supported (15),
message-reference-already-used (16)
}
Diagnostic-Info ::= OCTET STRING (SIZE (1..20))
Data-Coding-Scheme ::= INTEGER (0 .. 255)
Page-Inf ::= SEQUENCE {
message-info-useful-octets Message-Info-Useful-Octets,
message-info-page Message-Info-Page
}
Message-Info-Useful-Octets ::= INTEGER (0..82)
Recovery-Indication ::= BOOLEAN
-- TRUE indicates data is available
-- False indicates data is lost
-- Definitions used by the PDU parameters
Message-Info-Page ::= OCTET STRING (SIZE(82))
Cell-Id-Disc ::= OCTET STRING (SIZE(1))
-- values from the following table
lacAndCi OCTET STRING (SIZE(1)) ::= '1'H -- 2 Octet lac, followed by 2 Octet Cell Id
ciOnly OCTET STRING (SIZE(1)) ::= '2'H -- Cell Id only
lacOnly OCTET STRING (SIZE(1)) ::= '5'H -- 2 Octet lac only, all cells in this LAC (NOT USED BY BSC)
allCells OCTET STRING (SIZE(1)) ::= '6'H -- all cells in this BSS (NOT USED BY BSC)
Cell ::= SEQUENCE {
disc Cell-Id-Disc,
id Cell-Id
}
No-of-Broadcasts-Compl-Info-Type::= INTEGER {
unknown (0),
overflow (1)
}
-- Definitions of PDUs
Write-Replace ::= SEQUENCE {
message-Identifier Message-Identifier,
new-Serial-Number Serial-Number,
no-of-Pages No-of-Pages,
data-coding-scheme Data-Coding-Scheme,
cell-list Cell-List,
repetition-Period Repetition-Period,
no-of-broadcast-req No-of-Broadcast-Req,
cbs-Page-Inf SEQUENCE OF [15] Page-Inf,
old-Serial-Number [3] Serial-Number OPTIONAL,
category [2] Category OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
Kill ::= SEQUENCE {
message-Identifier Message-Identifier,
old-Serial-Number Serial-Number,
cell-List Cell-List,
channel-indicator [4] Channel OPTIONAL
}
Report ::= SEQUENCE {
message-Identifier Message-Identifier,
serial-Number Serial-Number,
no-of-Broadcasts-Compl-List [0] No-of-Broadcasts-Compl-List OPTIONAL,
failure-List [1] Failure-List OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
Status-CBCH ::= SEQUENCE{
cell-List Cell-List,
channel-indicator [4] Channel OPTIONAL
}
Status-CBCH-Resp ::= SEQUENCE{
cbch-loading-List [0] Cbch-Loading-List OPTIONAL,
failure-List [1] Failure-List OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
Status-Message ::= SEQUENCE {
message-Identifier Message-Identifier,
old-Serial-No Serial-Number,
cell-List Cell-List,
channel-indicator [4] Channel OPTIONAL
}
Status-Mess-Resp ::= SEQUENCE {
message-Identifier Message-Identifier,
old-serial-number Serial-Number,
no-of-Broadcasts-Compl-List [0] No-of-Broadcasts-Compl-List OPTIONAL,
failure-List [1] Failure-List OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
Reject::= SEQUENCE {
cause Failure-Reason,
diagnostic Diagnostic-Info OPTIONAL,
message-Identifier [7] Message-Identifier OPTIONAL,
serial-Number [3] Serial-Number OPTIONAL
}
-- $start$(Phase2PBscCellLists)$
-- The Restart-Ind PDU is retained for backward compatibility with Phase 2 systems,
-- and may be used in Phase 2+ systems
Restart-Ind ::= SEQUENCE {
cell-list Cell-List,
recovery-Indication Recovery-Indication OPTIONAL
}
-- coding of the recovery-Indication states is Data-available TRUE, Data-lost FALSE
-- The Restart-Ind-Phase2P PDU is used in Phase 2+ systems
Restart-Ind-Phase2P ::= CHOICE {
restart-list1 [0] SEQUENCE {
cell-list Cell-List,
recovery-Indication Recovery-Indication OPTIONAL
},
restart-list2 [1] SEQUENCE {
cell-list SEQUENCE OF Cell,
recovery-Indication Recovery-Indication OPTIONAL
}
}
-- $end$(Phase2PBscCellLists)$
Reset ::= SEQUENCE {
cell-list Cell-List
}
Set-DRX ::= SEQUENCE {
cell-list Cell-List,
schedule-Period [6] Schedule-Period OPTIONAL,
reserved-Slots [2] Reserved-Slots OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
-- $start$(Phase2PBscCellLists)$
Set-DRX-Resp ::= SEQUENCE {
cell-list [0] SEQUENCE OF Cell OPTIONAL,
failure-List [1] Failure-List OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
-- $end$(Phase2PBscCellLists)$
-- $start$(Phase2PBscCellLists)$
-- The Failure-Ind PDU is retained for backward compatibility with Phase 2 systems,
-- and may be used in Phase 2+ systems
Failure-Ind ::= SEQUENCE{
cell-list Cell-List
}
-- $start$(Phase2PBscCellLists)$
-- The Failure-Ind-Phase2P PDU is used in Phase 2+ systems
Failure-Ind-Phase2P ::= CHOICE {
failure-list1 [0] SEQUENCE {
cell-list Cell-List
},
failure-list2 [1] SEQUENCE OF Cell
}
-- $end$(Phase2PBscCellLists)$
END
|
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 designated as the entity responsible for re-establishing the association.
Following receipt of N-RESET any command sent by the CBC, for which no corresponding response has been received by the CBC, will be re-sent to the BSC.
|
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 interim period support of 128 bytes of NS-user-data in network connection and network connection release phases will remain a provider option. The following figures are therefore provided in order to indicate how CBSE-BIND, CBSE-BIND-CONFIRM, CBSE-BIND-FAILURE and CBSE-UNBIND should be mapped to/from an OSI Network Service definition which does not support 128 bytes of NS-user-data in network connection and network connection release phases.
NOTE 1: CBSMSE-BIND parameters are carried as NS-user-data.
NOTE 2: CBSMSE-BIND-CONFIRM is carried as NS-user-data.
NOTE 3: CBSMSE-BIND-FAILURE is carried as NS-user-data
NOTE 4: CBSMSE-UNBIND parameters are carried as NS-user-data.
Figure 2
|
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 to the Presentation Layer via ACSE (see X.217 and X.227) and ROSE (see X.219 and X.229). Only the Kernel functional unit of the Presentation Layer is used. Only the Kernel and Duplex functional units are used in the Session Layer (see X.215 and X.225).
|
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 operation at any time.
The new CBRSE service element is first defined in the following subclause, and then specified in ASN.1 notation in subclause 3.2.
CBRSE definition
This service element defines the following services:
CBRSE-BIND This operation will normally be invoked by the CBC to establish the application association, but in exceptional circumstances (e.g. following loss of data) the BSC may invoke the operation; only thereafter the remaining CBRSE services may be used. This operation reports either success or failure (result or error).
CBR-WRITE-REPLACE, CBR-KILL, CBR-STATUS-CBCH-QUERY, CBR-STATUS-MESSAGE-QUERY, CBR-RESET, CBR-SET-DRX
These operations may be invoked by the application entity in the CBC; They are used to relay commands from the CBC to a given BSC. The operations report either success or failure.
$start$(Phase2PBscCellLists)$
CBR-RESTART-IND, CBR-RESTART-IND-PHASE2P, CBR-FAILURE-IND, CBR-FAILURE-IND-PHASE2P
This operation may be invoked by the application entity in the BSC. The operation reports success or failure.
$end$(Phase2PBscCellLists)$
CBR-UNBIND This operation must be invoked by the CBC as the last CBRSE operation before releasing the application association. This operation reports success only.
Of the services defined above, CBR-WRITE-REPLACE semantically means the relay of cell broadcast messages across the CBC-BSC-connection in order to add them to the message list in the BSC, whereas CBR-KILL is used to delete messages from the message list. The CBR-STATUS-CBCH-QUERY command inquires after the current loading of a specific cell broadcast channel, while the CBR-STATUS-MESSAGE-QUERY command requests status information concerning a specific message. The CBR-SET-DRX command sets the DRX related parameters. These five services combine the primitives defined in GSM 03.41, which can be invoked by the CBC.
The CBR-BIND service is used to exchange identifications, passwords, etc., and in order to negotiate the usage of the other services. The CBR-UNBIND service prepares for the release of the application association.
|
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-domain(0)
gsm-messaging(4) gsm-sms4(13) usefulDefinitions(0) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
EXPORTS id-cb-ot-CBC, id-cb-ot-BSC, id-cb-port,
id-cb-ac-so, id-cb-CBRSE, id-cb-as-CBRSE;
ID ::= OBJECT IDENTIFIER
mobile-domain ID ::= { ccitt identified-organization (4) etsi (0) mobile-domain (0)}
-- root for all sms allocations
gsm-messaging ID ::= { mobile-domain gsm-messaging (4) }
gsm-sms4 ID ::= {gsm-messaging (13)}
-- categories
id-cb-mod ID ::= { gsm-messaging 1 } -- modules
id-cb-ot ID ::= { gsm-messaging 2 } -- object type
id-cb-pt ID ::= { gsm-messaging 3 } -- port types
id-cb-ac ID ::= { gsm-messaging 4 } -- appl. contexts
id-cb-ase ID ::= { gsm-messaging 5 } -- ASEs
id-cb-as ID ::= { gsm-messaging 6 } -- abstract syntaxes
-- modules
usefulDefinitions ID ::= { gsm-sms4 0 }
relayProtocol ID ::= { gsm-sms4 1 }
relayAbstractService ID ::= { gsm-sms4 2 }
-- object types
id-cb-ot-CBC ID ::= { id-cb-ot 0 }
id-cb-ot-BSC ID ::= { id-cb-ot 1 }
-- port types
id-cb-port ID ::= { id-cb-pt 0 }
-- application contexts
id-cb-ac-so ID ::= { id-cb-ac 0 }
-- application service elements
id-cb-CBRSE ID ::= { id-cb-ase 0 }
-- abstract syntaxes
id-cb-as-CBRSE ID ::= { id-cb-as 0 }
END
2nd module of 3
RelayAbstractService
RelayAbstractService {
ccitt identified-organization (4) etsi (0) mobile-domain(0)
gsm-messaging(4) gsm-sms4(13) relayAbstractService(2) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
IMPORTS
BIND, UNBIND
FROM Remote-Operations-Notation {
joint-iso-ccitt remote-operations(4) notation(0) }
OBJECT, PORT, ABSTRACT-BIND, ABSTRACT-UNBIND,
ABSTRACT-OPERATION, ABSTRACT-ERROR
FROM AbstractServiceNotation {
joint-iso-ccitt mhs-motis(6) asdc(2) modules(0) notation(1) }
id-cb-ot-CBC, id-cb-ot-BSC, id-cb-port
FROM CBS-UsefulDefinitions{
ccitt identified-organization (4) etsi (0) mobile-domain(0)
gsm-messaging(4) gsm-sms4(13) usefulDefinitions(0) }
-- upper bound settings
ub-operator-name-length INTEGER ::= 20
ub-agreem-name-length INTEGER ::= 20
ub-X121Address-length INTEGER ::= 15
ub-password-length INTEGER ::= 20
-- Objects
-- The CBC and the BSC are modelled as atomic objects, cBC--Object and bSC-Object. Each
-- object has one port for the interconnection. ([S] and [C] indicate supply and consumption of
-- services, respectively).
cBC-Object OBJECT
PORTS { cBR-port [S] }
::= id-cb-ot-CBC
bSC-Object OBJECT
PORTS { cBR-port [C] }
::= id-cb-ot-BSC
-- Port
cBR-port PORT
CONSUMER INVOKES {CBR-Restart-Ind
-- $start$(Phase2PBscCellLists)$
CBR-Restart-Ind-Phase2P
CBR-Failure-Ind
CBR-Failure-Ind-Phase2P
-- $end$(Phase2PBscCellLists)$
}
SUPPLIER INVOKES { CBR-Write-Replace
CBR-Kill
CBR-Status-CBCH-Query
CBR-Status-Message-Query
CBR-Reset
CBR-Set-DRX
}
::= id-cb-port
-- The CBR-Bind operation
-- Both, BIND and UNBIND operations, are exclusively within the responsibility of the CBC. The
-- BIND operation is therefore always requested by the CBC
-- Note that this structure should be used by Phase 2 systems only.
CBR-Bind ::=
ABSTRACT-BIND
TO { cBR-port }
BIND
ARGUMENT CBR-Bind-Parameters
RESULT CBR-Bind-confirm
BIND-ERROR CBR-Bind-failure
-- The CBR-Unbind operation
-- The UNBIND is a harsh release of the association and all outstanding operations are aborted.
-- UNBIND is always requested by the CBC. The CBC and the BSC should negotiate (during
-- CBR-BIND) the use of services on the association (the operations parameter - list of operation
-- types for the association) in such a way that no harmful losses of operations occur.
CBR-Unbind ::=
ABSTRACT-UNBIND
FROM { cBR-port }
UNBIND
ARGUMENT Time-when-connected
RESULT Time-when-disconnected
- Association control parameters
CBR-Bind-Parameters ::= SEQUENCE {
initiatorID [0] Name,
password [1] Password OPTIONAL,
pswNeeded [2] BOOLEAN,
iniType [3] Telecom-System-Type,
operations [4] List-of-Operations,
transient [5] BOOLEAN
}
-- Above and in SMR-Bind-confirm
-- initiatorID/respID: identify the initiating/responding telecommunication subsystem
-- password: may assist in authentication
-- pswNeeded (BIND only):requests password into SMR-Bind, SMR-Bind-Confirm
-- iniType/respType: identify the system entity
-- operations: lists the SM relay operations requested and supported on the association:
-- operations listed in both the BIND and the CONFIRM may be used (i.e. this is a negotiation
-- between CBC and BSC)
-- transient:forces the association (and the underlying connections), transient: it must be
-- UNBouND as soon as there are no operations to be performed
Name ::= SEQUENCE {
operator [0] Operator OPTIONAL,
bilateralAgreem [1] BilateralAgreem OPTIONAL,
dataNetworkAddress [2] X121Address OPTIONAL,
iSDNAddress [3] CBS-Address OPTIONAL
}
-- operator is a text string containing the name of the CBC/PLMN operator. bilateralAgreem is a
-- text string identifying the bilateral agreement between the CBC and the PLMN operators
-- which allows for this association to be established.
-- dataNetworkAddress is the PSPDN X.121 address of the CBC/BSC issuing the BIND or
-- CONFIRM, occurring only if a PSPDN is used.
-- iSDNAddress is the PLMN address of the CBC as seen by the MSs (same datum in both BIND
and CONFIRM).
-- Any pair of subsets of these parameters may be used to identify the CBC and the BSC to one
-- another.
Operator ::= PrintableString (SIZE(0..ub-operator-name-length))
BilateralAgreem ::= PrintableString (SIZE(0..ub-agreem-name-length))
X121Address ::= NumericString (SIZE(0..ub-X121Address-length))
-- CBS-Address is specified later in this module.
Password ::= PrintableString (SIZE(0..ub-password-length))
-- Version provides one of the indications given in the following table.
-- Any future substantive interface definition changes must be added to Table 1.
-- For definitions see Table 1.
Version ::= INTEGER {
release-97 (0),
reserved-1 (1),
reserved-2 (2),
reserved-3 (3),
reserved-4 (4),
reserved-5 (5),
reserved-6 (6)
}
Telecom-System-Type ::= INTEGER {
cell-Broadcast-Service-Centre (0),
public-Land-Mobile-Network (1)
-- Extensions are possible: additional telecommunication subsystems -- might adopt this service element for their interconnection.
}
List-of-Operations ::= BIT STRING {
cBR-From-CBC-Write-Replace (0),
cBR-From-CBC-Kill (1),
cBR-From-CBC-Status-CBCH-Query (2),
cBR-From-CBC-Status-Message-Query (3),
cBR-From-BSC-Restart-Ind (4),
cBR-From-CBC-Reset (5),
cBR-From-BSC-Failure-Ind (6),
cBR-From- CBC-Set-DRX (7),
cBR-From-BSC-VBind-Request (8),
cBR-From-BSC-Bind-Confirm (9),
cBR-From-BSC-Bind-Failure (10),
cBR-From-BSC-UnBind (11),
-- $start$(Phase2PBscCellLists)$
cBR-From-BSC-Restart-Ind-Phase2P (12),
cBR-From-BSC-Failure-Ind-Phase2P (13)
-- $end$(Phase2PBscCellLists)$
-- Extensions are possible: additional operations may be defined
-- within this service element. Existing systems should tolerate
-- unknown values, but negotiate not to perform unknown
-- operations.}
-- Note that this element replaces the CBR-Bind structure for Phase 2+ and beyond.
CBR-VBind-Request ::=
ABSTRACT-VBIND
TO { cBR-port }
BIND
ARGUMENT CBR-VBind-Parameters
RESULT CBR-Bind-confirm
BIND-ERROR CBR-Bind-failure
CBR-Bind-confirm ::= SEQUENCE {
respId [0] Name,
password [1] Password OPTIONAL,
respType [3] Telecom-System-Type,
operations [4] List-of-Operations,
transient [5] BOOLEAN,
connectTime [6] Time-when-connected
}
CBR-Bind-failure ::= SEQUENCE {
connect-failure-reason
[0] Connect-failure
}
-- connect-failure-reason contains one of the error indications given in the following table.
Table 3
Error indications
Reason
not-entitled
The responder is not entitled to accept a request for an association between itself and the initiator.
temporary-overload
The responder is not capable of establishing an association due to temporary overload.
temporary-failure
The responder is not capable of establishing an association due to a temporary failure (having impact on an entity at SM-RL or at layers above).
incorrect-ID-or-password
The responder will not accept the request to establish an association between itself and the initiator due to incorrect identity or password.
not-supported
The responder does not recognize the telecommunication subsystem type of the initiator, or cannot support any of the operations suggested on the association.
version-unsupported
The version specified is not supported by the recipient.
--
Connect-failure ::= INTEGER {
not-entitled (0),
temporary-overload (1),
temporary-failure (2),
incorrect-ID-or-password (3),
not-supported (4),
version-unsupported (5)
}
Time-when-disconnected ::= UTCTime
Time-when-connected ::= UTCTime
-- The CBR-Write-Replace operation
CBR-Write-Replace ::=
ABSTRACT-OPERATION
ARGUMENT Write-Replace
RESULT Report
ERRORS {Parameter-not-recognized,
Parameter-value-invalid,
Valid-CBS-message-not-identified,
Cell-identity-not-valid,
Unrecognized-primitive,
Missing-mandatory-element,
BSS-capacity-exceeded,
Cell-memory-exceeded,
BSS-memory-exceeded,
Cell-broadcast-not-supported,
Cell-broadcast-not-operational,
Extended-channel-not-supported,
Message-reference-already-used, Unspecified-error
}
-- The CBR-Kill operation
CBR-Kill ::=
ABSTRACT-OPERATION
ARGUMENT Kill
RESULT Report
ERRORS {Parameter-not-recognized,
Parameter-value-invalid,
Cell-identity-not-valid,
Valid-CBS-message-not-identified,
Unrecognized-primitive,
Missing-mandatory-element,
Cell-broadcast-not-supported,
Cell-broadcast-not-operational,
Extended-channel-not-supported,
Unspecified-error
}
-- The CBR-Status-CBCH-Query operation
CBR-Status-CBCH-Query ::=
ABSTRACT-OPERATION
ARGUMENT Status-CBCH
RESULT Status-CBCH-Resp
ERRORS {Parameter-not-recognized,
Parameter-value-invalid,
Cell-identity-not-valid,
Unrecognized-primitive,
Missing-mandatory-element,
Cell-broadcast-not-supported,
Cell-broadcast-not-operational,
Extended-channel-not-supported,
Unspecified-error
}
-- The CBR-Status-Message-Query operation
CBR-Status-Message-Query ::=
ABSTRACT-OPERATION
ARGUMENT Status-Message
RESULT Status-Mess-Resp
ERRORS {Parameter-not-recognized,
Parameter-value-invalid,
Cell-identity-not-valid,
Valid-CBS-message-not-identified,
Unrecognized-primitive,
Missing-mandatory-element,
Cell-broadcast-not-supported,
Cell-broadcast-not-operational,
Extended-channel-not-supported,
Unspecified-error
}
-- The CBR-Restart-Ind operation
CBR-Restart-Ind ::=
ABSTRACT-OPERATION
ARGUMENT Restart-Ind
RESULT
ERRORS {Parameter-not-recognised,
Parameter-value-invalid,
Cell-identity-not-valid,
Unrecognized-primitive,
Missing-mandatory-element,
Unspecified-error
}
-- $start$(Phase2PBscCellLists)$
-- The CBR-Restart-Ind-Phase2P operation
CBR-Restart-Ind-Phase2P ::=
ABSTRACT-OPERATION
ARGUMENT Restart-Ind-Phase2P
RESULT
ERRORS {Parameter-not-recognised,
Parameter-value-invalid,
Cell-identity-not-valid,
Unrecognized-primitive,
Missing-mandatory-element,
Unspecified-error
}
-- $end$(Phase2PBscCellLists)$
-- The CBR-Reset operation
CBR-Reset ::=
ABSTRACT-OPERATION
ARGUMENT Reset
RESULT
ERRORS {Parameter-not-recognized,
Parameter-value-invalid,
Cell-identity-not-valid,
Unrecognized-primitive,
Missing-mandatory-element,
Cell-broadcast-not-supported,
Unspecified-error
}
-- The CBR-Failure-Ind operation
CBR-Failure-Ind ::=
ABSTRACT-OPERATION
ARGUMENT Failure-Ind
RESULT
ERRORS {Parameter-not-recognized,
Parameter-value-invalid,
Cell-identity-not-valid,
Unrecognized-primitive,
Missing-mandatory-element,
Unspecified-error
}
-- $start$(Phase2PBscCellLists)$
-- The CBR-Failure-Ind-Phase2P operation
CBR-Failure-Ind-Phase2P ::=
ABSTRACT-OPERATION
ARGUMENT Failure-Ind-Phase2P
RESULT
ERRORS {Parameter-not-recognized,
Parameter-value-invalid,
Cell-identity-not-valid,
Unrecognized-primitive,
Missing-mandatory-element,
Unspecified-error
}
-- $end$(Phase2PBscCellLists)$
-- The CBR-Set-DRX operation
CBR-Set-DRX ::=
ABSTRACT-OPERATION
ARGUMENT Set-DRX
RESULT Set-DRX-Resp
ERRORS {Parameter-not-recognized,
Parameter-value-invalid,
Valid-CBS-message-not-identified,
Cell-identity-not-valid,
Unrecognized-primitive,
Missing-mandatory-element,
BSS-capacity-exceeded,
Unspecified-error,
Cell-broadcast-not-supported,
Cell-broadcast-not-operational,
Extended-channel-not-supported,
Incompatible-DRX-parameter
}
-- CBR operation ARGUMENT lists
-- PDU parameter definitions from 03.41
Message-Identifier ::= INTEGER (0 .. 65535)
Serial-Number ::= INTEGER (0 .. 65535)
No-of-Pages ::= INTEGER (1 .. 15)
Cell-List ::= SEQUENCE {
length INTEGER, -- number of cells in the list
disc Cell-Id-Disc,
list SEQUENCE OF Cell-Id
}
Channel ::= INTEGER {
basic-channel (0),
extended-channel (1)
}
Category ::= INTEGER {
high-priority (0),
normal-priority (1),
background (2)
}
Repetition-Period ::= INTEGER (1 .. 1024)
No-of-Broadcast-Req ::= INTEGER (0 ..65535)
No-of-Broadcasts-Compl-List ::= SEQUENCE OF SEQUENCE {
cell-id Cell,
no-of-broadcasts-compl INTEGER,
no-of-broadcasts-compl-info No-of-Broadcasts-Compl-Info-Type OPTIONAL
}
Cell-Id ::= OCTET STRING (SIZE(4))
-- Note:
-- If Cell-Id-Disc equals ciOnly then only the last 2 octets of
-- Cell-ID are to be considered
-- If Cell-Id-Disc equals lacOnly then only the first 2 octets of
-- Cell-ID are to be considered. The unused octets are filler octets
-- If Cell-Id-Disc equals allCells, Cell-ID only contains filler octets
Schedule-Period ::= INTEGER (0 .. 40)
Reserved-Slots ::= INTEGER (0 .. 40)
Failure-List ::= SEQUENCE OF SEQUENCE {
cell-id Cell,
cause Failure-Reason,
diagnostic Diagnostic-Info OPTIONAL
}
Cbch-Loading-List ::= SEQUENCE OF SEQUENCE{
cell-id Cell,
cbch-loading Cbch-Loading
-- indicates the predicted short term load, expressed as a percentage
-- (min:0, max: 100)
}
Cbch-Loading ::= INTEGER(0..100)
Failure-Reason ::= INTEGER {
parameter-not-recognised (0),
unused-failure-reason-1 (1), -- not used
parameter-value-invalid (2),
valid-CBS-message-not-identified (3),
cell-identity-not-valid (4),
unrecognised-primitive (5),
missing-mandatory-element (6),
bss-capacity-exceeded (7),
cell-memory-exceeded (8),
bss-memory-exceeded (9),
unspecifed-error (10),
incompatible-DRX-parameter (11),
unused-failure-reason-12 (12), -- not used
cell-broadcast-not-supported (13),
cell-broadcast-not-operational (14),
extended-channel-not-supported (15),
message-reference-already-used (16)
}
Diagnostic-Info ::= OCTET STRING (SIZE (1..20))
Data-Coding-Scheme ::= INTEGER (0 .. 255)
Page-Inf ::= SEQUENCE {
message-info-useful-octets Message-Info-Useful-Octets,
message-info-page Message-Info-Page
}
Message-Info-Useful-Octets ::= INTEGER (0..82)
Recovery-Indication ::= BOOLEAN
-- TRUE indicates data is available
-- False indicates data is lost
-- Definitions used by the PDU parameters
Message-Info-Page ::= OCTET STRING (SIZE(82))
Cell-Id-Disc ::= OCTET-STRING (SIZE(1))
-- values from the following table
lacAndCi OCTET STRING (SIZE(1)) ::= '1'H -- 2 Octet lac, followed by 2 Octet Cell Id
ciOnly OCTET STRING (SIZE(1)) ::= '2'H -- Cell Id only
lacOnly OCTET STRING (SIZE(1)) ::= '5'H -- 2 Octet lac only, all cells in this LAC (NOT USED BY BSC)
allCells OCTET STRING (SIZE(1)) ::= '6'H -- all cells in this BSS (NOT USED BY BSC)
Cell ::= SEQUENCE {
disc Cell-Id-Disc,
id Cell-Id
}
No-of-Broadcasts-Compl-Info-Type::= INTEGER {
unknown (0),
overflow (1)
}
Write-Replace ::= SEQUENCE {
message-Identifier Message-Identifier,
new-Serial-Number Serial-Number,
no-of-Pages No-of-Pages,
data-coding-scheme Data-Coding-Scheme,
cell-list Cell-List,
repetition-Period Repetition-Period,
no-of-broadcast-req No-of-Broadcast-Req,
cbs-Page-Inf SEQUENCE OF [15] Page-Inf,
old-Serial-Number [3] Serial-Number OPTIONAL,
category [2] Category OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
Kill ::= SEQUENCE {
message-Identifier Message-Identifier,
old-Serial-Number Serial-Number,
cell-List Cell-List,
channel-indicator [4] Channel OPTIONAL
}
Status-CBCH ::= SEQUENCE{
cell-List Cell-List,
channel-indicator [4] Channel OPTIONAL
}
Status-Message ::= SEQUENCE {
message-Identifier Message-Identifier,
old-Serial-No Serial-Number,
cell-List Cell-List,
channel-indicator [4] Channel OPTIONAL
}
-- $start$(Phase2PBscCellLists)$
-- The Restart-Ind PDU is retained for backward compatibility with Phase 2 systems,
-- and may be used in Phase 2+ systems
Restart-Ind ::= SEQUENCE {
cell-list Cell-List,
recovery-Indication Recovery-Indication OPTIONAL
}
-- coding of the recovery-Indication states is Data-available TRUE, Data-lost FALSE
-- The Restart-Ind-Phase2P PDU is used in Phase 2+ systems
Restart-Ind-Phase2P ::= CHOICE {
restart-list1 [0] SEQUENCE {
cell-list Cell-List,
recovery-Indication Recovery OPTIONAL
},
restart-list2 [1] SEQUENCE {
cell-list SEQUENCE OF Cell,
recovery-Indication Recovery OPTIONAL
}
}
-- The Failure-Ind PDU is retained for backward compatibility with Phase 2 systems,
-- and may be used in Phase 2+ systems
Failure-Ind ::= SEQUENCE{
cell-list Cell-List
}
-- The Failure-Ind-Phase2P PDU is used in Phase 2+ systems
Failure-Ind-Phase2P ::= CHOICE {
failure-list1 [0] SEQUENCE {
cell-list Cell-List
},
failure-list2 [1] SEQUENCE OF Cell
}
-- $end$(Phase2PBscCellLists)$
Reset ::= SEQUENCE{
cell-list Cell-List
}
Set-DRX ::= SEQUENCE {
cell-list Cell-List,
schedule-Period [6] Schedule-Period OPTIONAL,
reserved-Slots [2] Reserved-Slots OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
Report ::= SEQUENCE {
message-Identifier Message-Identifier,
serial-Number Serial-Number,
no-of-Broadcasts-Compl-List [0] No-of-Broadcasts-Compl-List OPTIONAL,
failure-List [1] Failure-List OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
Status-CBCH-Resp ::= SEQUENCE{
cbch-loading-List [0] Cbch-Loading-List OPTIONAL,
failure-List [1] Failure-List OPTIONAL,
channel-indicator [4] Channel OPTIONAL
Status-Mess-Resp ::= SEQUENCE {
message-Identifier Message-Identifier,
old-serial-number Serial-Number,
no-of-Broadcasts-Compl-List [0] No-of-Broadcasts-Compl-List OPTIONAL,
failure-List [1] Failure-List OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
-- $start$(Phase2PBscCellLists)$
Set-DRX-Resp ::= SEQUENCE {
cell-list [0] SEQUENCE OF Cell OPTIONAL,
failure-List [1] Failure-List OPTIONAL,
channel-indicator [4] Channel OPTIONAL
}
-- $end$(Phase2PBscCellLists)$
-- CBR operation errors listed below
Parameter-not-recognized ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Parameter-value-invalid ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Valid-CBS-message-not-identified ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Cell-Identity-not-valid ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Unrecognized-primitive ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Missing-mandatory-element ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
BSS-capacity-exceeded ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Cell-memory-exceeded ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
BSS-memory-exceeded ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Unspecified-error ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Incompatible-DRX-parameter ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Cell-broadcast-not-supported ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Cell-broadcast-not-operational ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Extended-channel-not-supported ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
Message-reference-already-used ::=
ABSTRACT-ERROR
PARAMETER Diagnostic-Info OPTIONAL
-- Definition of Cell Broadcast Relay Service address
CBS-Address ::= [APPLICATION 0] SEQUENCE {
address-type INTEGER { unknown-type (0),
international-number (1),
national-number (2),
network-specific-number (3),
short-number (4) },
numbering-plan INTEGER { unknown-numbering (0),
iSDN-numbering (1),
data-network-numbering (3),
telex-numbering (4),
national-numbering (8),
private-numbering (9)}
address-value CHOICE { octet-format
SemiOctetString
--other formats are for further study}
}
SemiOctetString ::= OCTET STRING (SIZE(1..10))
-- each octet contains two binary coded decimal digits
END
3rd module of 3
RelayProtocol
RelayProtocol {
ccitt identified-organization (4) etsi (0) mobile-domain(0)
gsm-messaging (4) gsm-sms4 (13) relayProtocol(1) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
IMPORTS
-- application service elements and application contexts
aCSE, APPLICATION-SERVICE-ELEMENT, APPLICATION-CONTEXT
FROM Remote-Operations-Notation-extension {
joint-iso-ccitt remote-operations(4) notation-extension(2) }
rOSE
FROM Remote-Operations-APDUs {
joint-iso-ccitt remote-operations(4) apdus(1) }
-- object identifiers
id-cb-ac-so, id-cb-CBRSE, id-cb-as-CBRSE,
FROM CBS-UsefulDefinitions{
ccitt identified-organization (4) etsi (0) mobile-domain(0)
gsm-messaging(4) gsm-sms4 (13) usefulDefinitions(0) } ;
aS-ACSE OBJECT IDENTIFIER ::=
{ joint-iso-ccitt association-control (2) abstractSyntax(1) apdus(0) version(1) }
-- abstract service parameters
CBR-Bind, CBR-Unbind, CBR-Write-Replace, CBR-Kill,
CBR-Status-CBCH-Query,
-- $start$(Phase2PBscCellLists)$
CBR-Status-Message-Query, CBR-Reset, CBR-Restart-Ind, CBR-Restart-Ind-Phase2P,
CBR-Failure-Ind, CBR-Failure-Ind-Phase2P, CBR-Set-DRX,
-- $end$(Phase2PBscCellLists)$
Parameter-not-recognized, Parameter-value-invalid,
Valid-CBS-message-not-identified, Cell-identity-not-valid,
Unrecognized-primitive,
Missing-mandatory-element, BSS-capacity-exceeded,
Cell-memory-exceeded, BSS-memory-exceeded, Unspecified-error, Incompatible-DRX-parameter,
Cell-broadcast-not-supported, Cell-broadcast-not-operational, Extended-channel-not-supported
FROM RelayAbstractService{
ccitt identified-organization (4) etsi (0) mobile-domain(0)
gsm-messaging(4) gsm-sms4(13) relayAbstractService(2) } ;
-- Application contexts
-- Only one application contexts is specified: the CBC is exclusively responsible for the BIND and
-- UNBIND operations.
cBC-BINDs-and-UNBINDs
APPLICATION-CONTEXT
APPLICATION-SERVICE-ELEMENTS { aCSE }
BIND CBR-Bind
UNBIND CBR-Unbind
REMOTE OPERATIONS { rOSE }
INITIATOR CONSUMER OF { cBRSE }
ABSTRACT SYNTAXES { id-cb-as-CBRSE , aS-ACSE }
::= id-cb-ac-so
-- Application service elements
cBRSE APPLICATION-SERVICE-ELEMENT
CONSUMER INVOKES { CBR-Restart-Ind
-- $start$(Phase2PBscCellLists)$
CBR-Restart-Ind-Phase2P
CBR-Failure-Ind
CBR-Failure-Ind-Phase2P
-- $end$(Phase2PBscCellLists)$
CBR-From-BSC-VBind-Request
CBR-From-BSC-Bind-Confirm
CBR-From-BSC-Bind-Failure
CBR-From-BSC-UnBind
}
SUPPLIER INVOKES { CBR-Write-Replace
CBR-Kill
CBR-Status-CBCH-Query
CBR-Status-Message-Query
CBR-Reset
CBR-Set-DRX
CBR-From-BSC-VBind-Request
CBR-From-BSC-Bind-Confirm
CBR-From-BSC-Bind-Failure
CBR-From-BSC-UnBind
}
::= id-cb-SMRSE
-- Remote operations
cbr-write-replace CBR-Write-Replace
::= 1
-- Note: localValue - words are omitted, since they are
-- typically not used, and likely to be removed from
-- the OPERATION and ERROR macros in ROSE.
cbr-kill CBR-Kill
::= 2
cbr-status-CBCH-query CBR-Status-CBCH-Query
::= 3
cbr-status-message-query CBR-Status-Message-Query
::= 4
cbr-restart-ind CBR-Restart-Ind
::= 5
cbr-reset CBR-Reset
::= 6
cbr-failure-ind CBR-Failure-Ind
::= 7
cbr-set-DRX CBR-Set-DRX
::= 8
-- $start$(Phase2PBscCellLists)$
cbr-restart-ind-phase2p CBR-Restart-Ind-Phase2P
::= 9
cbr-failure-ind-phase2p CBR-Failure-Ind-Phase2P
::= 10
-- $end$(Phase2PBscCellLists)$
-- Remote errors, the localValues are provisional
parameter-not-recognized Parameter-not-recognized
::= 0
parameter-value-invalid Parameter-value-invalid
::= 2
valid-CBS-message-not-identified Valid-CBS-message-not-identified
::= 3
cell-identity-not-valid Cell-identity-not-valid
::= 4
unrecognized-primitive Unrecognized-primitive
::= 5
missing-mandatory-element Missing-mandatory-element
::= 6
bss-capacity-exceeded BSS-capacity-exceeded
::= 7
cell-memory-exceeded Cell-memory-exceeded
::= 8
bss-memory-exceeded BSS-memory-exceeded
::= 9
unspecified-error Unspecified-error
::= 10
incompatible-DRX-parameter Incompatible-DRX-Parameter
::= 11
cell-broadcast-not-supported Cell-broadcast-not-supported
::= 13
cell-broadcast-not-operational Cell-broadcast-not-operational
::= 14
extended-channel-not-supported Extended-channel-not-supported
::= 15
message-reference-already-used Message-reference-already-used
::= 16
END
|
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). This is negotiated within the CBR-BIND service as follows:
name of parameter value in request and report
operations {cBR-From-CBC-Write-Replace,
cBR-From-CBC-Kill,
cBR-From-CBC-Status-CBCH-Query,
cBR-From-CBC-Status-Message-Query,
cBR-From-BSC-Restart-Ind,
cBR-From-BSC-Reset,
cBR-From-BSC-Failure-Ind,
cBR-From-CBC-Set-DRX,
cBR-From-BSC-VBind-Request,
cBR-From-BSC-Bind-Confirm,
cBR-From-BSC-Bind-Failure,
cBR-From-BSC-UnBind,
-- $start$(Phase2PBscCellLists)$
cBR-From-BSC-Restart-Ind-Phase2P,
cBR-From-BSC-Failure-Ind-Phase2P
-- $end$(Phase2PBscCellLists)$
}
transient FALSE
$start$(Phase2PBscCellLists)$
The CBC invokes cBR-From-CBC-Write-Replace, cBR-From-CBC-Kill, cBR-From-CBC-Status-CBCH-Query, cBR-From-CBC-Status-Message-Query, cBR-From-CBC-Reset, cBR-From-CBC-Set-DRX operations as needed. The BSC invokes cBR-From-BSC-Restart-Ind, cBR-From-BSC-Restart-Ind-Phase2P, cBR-From-BSC-Failure-Ind and cBR-From-BSC-Failure-Ind-Phase2P.
$end$(Phase2PBscCellLists)$
The CBR-UNBIND operation is not normally invoked on the association.
|
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-BIND service, only one type of operation is negotiated for use on the association. The operation of that type must be invoked by the CBC or by the BSC in exceptional circumstances (e.g. in order to invoke CBR-RESET). The BSC or CBC accepts the one type of operation and forces the association transient.
The following is an example of a negotiation procedure within the CBR-BIND service, where the CBR-Write-Replace operation is initiated by the CBC.
name of parameter value
iniType cell-Broadcast-Service-Centre
respType public-Land-Mobile-Network
operations { cBR-From-CBC-Write-Replace }
transient TRUE
The association for cBR-From-CBC-Kill, cBR-From-CBC-Status-CBCH-Query or cBR-From-CBC-Status-Message-Query, cBR-From-CBC-Reset, cBR-From-CBC-Set-DRX are negotiated according to the same principle, the CBC always being the initiator of the CBR-BIND.
The association may be used for invoking operations of the negotiated type(s) as long as there are such operations to be invoked (in other words, until all commands have been relayed).
|
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 and management protocols. The protocol specified in Section 3 of this report can be carried via an SS7 protocol stack consisting of TCAP, SCCP and MTP (see Q.700 series) with minor adaptations:
- ROSE operation classes 2 and 5 are replaced by TCAP operation classes 1 and 4 respectively.
- TCAP provides a connectionless service. The services provided by CBRSE-BIND, CBR‑UNBIND, CBR-Bind-confirm and CBR-Bind-failure are therefore not required and subclause 3.3 is not applicable.
PLMN networks may provide interworking between either of the protocols specified by clause 2 or 3 and the SS7 protocol stack for the purpose of fulfilling the service requirements of the primitives specified for the CBC - BSC interface in GSM 03.41.
Annex A (informative):
Document change history
SPEC
SMG#
CR
PHASE
VERS
NEW_VERS
SUBJECT
03.49
s25
A032
R97
5.7.0
6.0.0
Version Control for the CBC-BSC interface
03.49
s25
A033
R97
5.7.0
6.0.0
Write-Replace ASN.1
03.49
s26
A034
R97
6.0.0
6.1.0
CBC-BSC interface compatibility
03.49
s29
R98
7.0.0
Specification version upgrade to Release 1998 version 7.0.0
7.0.0
History
Document history
V7.0.0
August 1999
Publication
|
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.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] CCITT F.200 series Recommendations, Fascicle II.5: "Telematic, data transmission and teleconference services-Operations and quality of service".
[2] CCITT T.300 series Recommendations, Fascicle VII.5: "Terminal equipment and protocols for telematic services".
[3] CCITT X.200 series Recommendations, Fascicle VIII.4 Data communication networks: services an facilities, interfaces".
[4] CCITT X.300 series Recommendations, Fascicle VIII.6: "Data communication networks: interworking between networks, mobile data transmission systems,internetwork management".
[5] CCITT X.400 series Recommendations, Fascicle VIII.7: "Data communication networks: message handling systems".
[6] CCITT T.0 series Recommendations, Fascicle VII.3 Terminal equipment and protocols for telematic services (T.60,T.61,T.62)".
[7] CCITT T.65 series Recommendations, Fascicle VII.5: "terminal equipment and telematic services (T.70)".
[8] CCITT X.1 series Recommendations, Fascicle VIII.2: "Data communication networks: services and facilities, interfaces (X.21,X.31,X.32)".
[9] CCITT X.40 series Recommendations, Fascicle VIII.3: "Data communication networks: transmission, singnalling and switching, network aspects, maintenance and administrative arrangements( X.52,X.71,X.75)".
[10] CCITT V series Recommendations, Fascicle VIII.1: " Data communication over the telephone network (V.110)".
[11] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
[12] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)".
[13] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)".
[14] GSM 03.10: "Digital cellular telecommunication system (Phase 2+); GSM Public Land Mobile Network (PLMN) connection types".
[15] GSM 03.70: "Digital cellular telecommunication system (Phase 2+); Routeing of calls to/from Public Data Networks (PDN)".
[16] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
[17] GSM 07.03: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities".
[18] GSM 09.01: "Digital cellular telecommunication system (Phase 2+); General network interworking scenarios".
[19] GSM 09.04: "Digital cellular telecommunication system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Circuit Switched Public Data Network (CSPDN)".
[20] GSM 09.06: "Digital cellular telecommunications system (Phase 2+); Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services".
[21] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
|
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 Packet Layer Protocol
TDS Teletex Document Store
TID Terminal Identification (CCITT F.200)
Ttx Teletex
Ttx-MS Teletex Mobile Station (i.e. a MS with Ttx terminal connected)
Ttx-TE Teletex Terminal Equipment
Tx Telex
VCS Virtual Circuit Service
|
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 continuously.
Teletex subscriber equipment shall be in accordance with the CCITT recommendations T.60, T.61, T.62, and T.70. Especially it shall
a) have unique terminal identifications (TID);
b) be able to send and/or receive documents without terminal operator intervention;
c) have a certain set of indications to the terminal operator;
d) in principle be able to accept calls continuously, if call numbers are published in the directories (In order to meet this requirement, it is allowed to use a document storage facility which can be network or customer premises based.);
e) be able to prepare documents being forwarded to the telex service using appropriate conversion facilities within the network.
According to the CCITT T.70 (version 1988) the teletex service may be offered in the following types of networks:
a) the Circuit Switched Public Data Network (CSPDN);
b) the Packet Switched Public Data Network (PSPDN);
c) the Public Switched Telephone Network (PSTN); and
d) the Integrated Services Digital Network (ISDN).
The interworking between the different networks may be based on CCITT X.300-series of recommendations.
|
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 a GSM PLMN can participate in the internationally available teletex service, i.e. all teletex terminals, for which a call number is published in the service directory, can communicate with each other.
the following basic assumptions will apply:
a) In principle no specific network interworking functions shall be necessary in a VPLMN for the support of teletex.
b) No specific additional bearer service other than those defined in GSM 02.02 shall be needed in a VPLMN.
c) Ttx specific IWFs, if any, must not have any impact on the MS of a roaming subscriber.
d) Both PSTN and ISDN, if available, may be used as a transit network to the PSPDN.
e) Presently no service interworking (especially for telex) directly from the GSM PLMN is provided. Conversion facilities within the fixed networks shall be used.
NOTE: A mobile terminated call may be forwarded to a document storage facility called Teletex Document Store (TDS), if available, when the addressed Ttx-MS is temporarily unable to accept a call. The provision and the location of such a store is at the PLMN operator's discretion (e.g. within the PLMN or within a fixed network).
|
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 compatibility at the radio interface. For the time being this may be a national option.
Further configurations may be possible.
X.25
(X.21, X.21bis
V-series)
Figure 1/GSM 03.44: Reference Configuration of a Teletex Mobile Station
|
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 PLMN (see section 4.2)
Figure 2/GSM 03.44: Global Network Configuration
For service interworking with telex the national fixed network based Ttx/Tx conversion facility (CF) shall be used. For roaming subscribers this results in an international access. Whether the conversion facilities are prepared to receive such calls is not in the scope of the present document.
|
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 IWF is at the PLMN operator's discretion.
The PLMN and the particular PDN may be connected directly or via (a) transit network(s).
1) Direct interworking PLMN to PSPDN
2) Interworking PLMN to PSPDN via ISDN
3) Interworking PLMN to PSPDN via PSTN
4) Interworking PLMN to PSPDN via ISDN/PSTN
5) Direct interworking PLMN to CSPDN with protocol conversion
NOTE: This is a national option, because specific functionality in the IWF is needed .
6) Interworking PLMN to CSPDN via ISDN with protocol conversion
NOTE: This is a national option, because specific functionality in the IWF is needed .
7) Direct interworking PLMN to ISDN with protocol conversion
NOTE: Presently this interworking case applies only to the Ttx service within an ISDN using T.70-CSPDN protocols.
Figure 3/GSM 03.44: Network Interworking Scenarios
For the interworking PLMN to the different networks the following GSM specifications apply:
PLMN to CSPDN: GSM 09.04
PLMN to PSPDN: GSM 09.06
PLMN to PSTN/ISDN: GSM 09.07
|
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 compatibility information element may not be included in the call setup message to the MS in case of a mobile terminated call. Therefore a Ttx-MS shall not reject an incoming call due to the absence of this element.
Table 1/GSM 03.44: High layer compatibility information element for teletex
High layer characteristics
Identification
Teletex (basic teletex)
Document application profile
for formatted mixed mode *)
Document application profile
for processable mode *)
*) for future use
Annex A (informative):
Teletex Document Store (TDS)
A.1 Introduction
A TDS is an optional functional unit, the provision of which is necessary, if the PLMN operator wishes that mobile terminated calls should not fail due to temporary absence of a Ttx-MS. A particular TDS can be in charge of one or more PLMNs. Each PLMN is the HPLMN of the Ttx-MSs, that TDS is acting for.
The provision and location of a TDS is at the PLMN operator's discretion (e.g. within the HPLMN or within a fixed network).
It is not intended to receive documents instead of the Ttx terminal in general, but only occasionally, if the MS does not accept a call. This may include e.g. temporary user initiated unconditional call forwarding.
Whether use of unconditional call forwarding is required in general, when the Ttx-MS is roaming in a another GSM PLMN, depends e.g. on the signalling capabilities of the concerned networks.
Some requirements can be identified from the user point of view either being a subscriber to a PLMN or to a fixed network.
These requirements are that a TDS must
a) be able to receive and store documents for a Ttx terminal (subscriber) it is in charge for;
b) act instead of the terminal as being the terminal itself (negotiation of options), especially there must not be any unacceptable impact on the remote fixed network based Ttx terminal which forces the user of that terminal to change his/her communication habits;
c) to be responsible for the delivery of the documents to the terminal it is in charge for.
A minimum set of functions is necessary to fulfil the requirements. To perform those functions, however, a TDS can be e.g. a separate stand-alone system or part of a Message Handling System MHS (based on X.400- and/or T.300-series of CCITT recommendations).
Once a document has been received and is stored in the document store the way to access and/or retrieve the document is not in the scope of the present document. However, it should be noted that usually a Ttx terminal can only make use of the teletex protocols. During the process of receiving documents from another Ttx terminal located in a PLMN or in a fixed network the TDS has to behave like a Ttx terminal anyway (see also requirements above).
A.2 Minimum Set of Functions
The following function must be allocated to a TDS:
- Ttx document reception;
- Ttx document storage capability (document store);
- either automatic forwarding Ttx documents to the Ttx-TE (subscriber) or document retrieval by the authorized Ttx-TE;
- operation and maintenance facilities.
A.3 Receiving Teletex Documents into the Document Store
The Ttx document reception function of the TDS may be accessed e.g. using call forwarding facilities of the connected network. These facilities, if used, are activated by the network, whenever there is a match with the associated conditions, e.g. the addressed Ttx-TE in the PLMN does not answer the mobile terminated call. The address of the TDS must therefore be known to the network as forwarded-to address.
A.4 Getting Teletex Documents from the Document Store
The way of having access to the received documents and the detailed procedures are outside of the scope of the present document.
Annex B (informative):
Change Request History
Change history
SMG No.
TDoc. No.
CR. No.
Section affected
New version
Subject/Comments
SMG#07
4.0.1
ETSI Publication
SMG#20
5.0.0
Release 1996 version
SMG#27
6.0.0
Release 1997 version
SMG#29
7.0.0
Release 1998 version
History
Document history
V7.0.0
August 1999
Publication
|
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. For these applications the necessary mapping and local knowledge between application interface and network is described. The only modifications needed in ETS 300 838 [14] to fulfil this requirements are covered by changes of the parameter description. These changes of parameters are defined in clauses 4 and 5 of this ETS.
An application compliant with this ETS shall not imply compliance with ETS 300 838 (HPCI).
Clause 4 is meant to replace subclause 5.7 message parameters of ETS 300 838 [14]. which defines the parameters of the profile A of the HPCI.
NOTE 1: Clause 4is for further study.
Clause 5 replaces subclause 6.8 parameter description of ETS 300 838, which defines the parameters of the profile B of the HPCI.
The second part defines GSM specific features. New GSM‑API applications need extensions to ETS 300 838 [14] which are defined in section 6 and 7of this ETS.
These sections are meant as an addition to ETS 300 838 [14]. They do not replace any clause of ETS 300 838 [14].
Clause 6 defines the extensions according to the profile A of ETS 300 838 [14].
NOTE 2: Clause 6 is for further study.
Clause 7 defines the extensions according to the profile B of ETS 300 838 [14] (bit compatible to COMMON ISDN API).
The messages and the operating system dependent part of ETS 300 838 [14] will not be changed for GSM‑API.
|
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 when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies.
[1] GSM 01.04 (ETR 350): "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.04 (ETS 300 918): "Digital cellular telecommunications system (Phase 2+); General on supplementary services".
[3] GSM 02.30 (ETS 300 907): "Digital cellular telecommunications system (Phase 2+); Man‑Machine Interface (MMI) of the Mobile Station (MS)".
[4] GSM 03.38 (ETS 300 900): "Digital cellular telecommunications system (Phase 2+); Alphabets and language‑specific information".
[5] GSM 03.40 (ETS 300 901): "Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point to Point (PP)".
[6] GSM 03.41 (ETS 300 902): "Digital cellular telecommunications system (Phase 2+); Technical realization of Short Message Service Cell Broadcast (SMSCB)".
[7] GSM 04.08 (ETS 300 940): "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
[8] GSM 04.11 (ETS 300 942): "Digital cellular telecommunications system (Phase 2+); Point‑to‑Point (PP) Short Message Service (SMS) support on mobile radio interface".
[9] GSM 04.80 (ETS 300 950): "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding".
[10] GSM 04.90 (ETS 300 957): "Digital cellular telecommunications system; Unstructured supplementary services operation ‑ Stage 3".
[11] GSM 05.08 (ETS 300 911): "Digital cellular telecommunications system (Phase 2+); Radiosubsystem link control".
[12] GSM 09.02 (ETS 300 974): "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification".
[13] GSM 11.11 (ETS 300 977): "Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module ‑ Mobile Equipment (SIM ‑ ME) interface".
[14] ETS 300 383 (1997): "Integrated Services Digital Network (ISDN); Harmonized Programmable Communication Interface (HPCI) for ISDN".
[15] ETS 300‑102‑1 (1990): "Integrated Services Digital Network (ISDN), Usernetwork interface layer 3, Specifications for basic call control".
[16] ITU‑T Recommendation Q931 (1993): "Digital subscriber Signalling System No. one (DSS1) ‑ ISDN user network interface layer 3 specification for basic call control".
[17] ISO 7776 (1986): "Information Processing systems; Data communications; High‑level data link control procedures: Description of the X.25 LAPD compatible DTE data link procedures".
[18] IBM publication: "IBM Synchronous Data Link Control Concepts" (GA27‑3093).
[19] ITU‑T Recommendation Q921 (1993): "ISDN user network interface ‑ Data link layer specification".
[20] ITU‑T Recommendation T.30 (1993): "Procedures for document facsimile transmission in the general switched telephone Network".
[21] Request For Comment (RFC) 1661: "The Point‑to‑Point Protocol (PPP)".
[22] Request For Comment (RFC) 1618: "PPP over ISDN".
[23] CCITT Recommendation T.90 (1992): "Characteristics and protocols for terminals for telematic services in ISDN".
[24] ISO 8208 (1990): "Information technology: Data communications; X.25 Packet Layer Protocol for Data Terminal Equipment".
[25] ITU‑T Recommendation X.213 (1992): "Information technology ‑ Network service definition for Open Systems".
[26] ITU‑T Recommendation X.400: "Reference model open System interconnection for CCITT applications".
[27] ITU‑T Recommendation X.200: "Message handling system and service overview".
[28] ETS 300 097 (1992): "Integrated Services Digital Network (ISDN), Connected Line Identification Presentation (COLP) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol part 1; Protocol implementation description".
|
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 will make a SIM file available for an application. See GSM 11.11 [13].
RP cause This is an error cause used in the GSM Short Messages Service at the SMR (Short Message Relay) layer. All causes are listed in GSM 04.11 [16].
|
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 GSM 03.41 [6].
DCS Data Coding Scheme. It defines an alphabet and/or a class and/or a language for a message. It is used for the SMS and the CBS. See GSM 03.38 [4].
DTMF Dual Tone Multi Frequency.
GSM‑API GSM Application Programming Interface.
HPCI Harmonized Programmable Communication Interface
MI Message Identifier. Each page of a CBS message is identified by a MI.
PIN Code Personal Identification Number. See GSM 11.11 [13].
PLMN Public Land Mobile Network.
PPP Point to Point Protocol.
RLP Radio Link Protocol.
SC Service Centre. It is the network element which handle the SMS messages. SeeGSM 03.40 [5].
SIM Subscriber Identity Module. See GSM 11.11 [13] for a full description of the SIM files.
SMS Short Message Service. It is a specific GSM service used to send point to point short messages. See GSM 03.40 [5] for a complete description.
SMS Command It is a TPDU initiated from a mobile station which invoke an operation in the service centre. See GSM 03.40 [5].
SS Supplementary Services. All GSM supplementary services are defined in GSM 02.04 [2].
TPDU Transfer Protocol Data Unit. It is used in the Short Messages Service. See GSM 03.40 [5].
|
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 case there is no private Profile B coding for these parameters. These parameters are coded as Profile B structures starting with a length octet and the remainder of the parameter being coded as defined in ETS 300 102‑1 [15] / Q.931 [16] or GSM specifications from octet three onwards. References to the contents of a structure in this clause always use index 0 to identify the first octet of information, i.e. the octet following the length octet.
Parameters may not be omitted, instead an empty structure shall be used. An empty structure shall be coded as a single octet containing a value of 0.
Reserved structures shall be coded as empty structures. Reserved parameter values shall not be used by GSM‑API applications. In case of COMMON‑ISDN‑API applications using these reserved structures respective parameter values the behaviour of GSM‑API is described below.
Default values as described in the following subclause shall be implemented in Profile B. They need not be valid for external ISDN equipment; in that case the external equipment defines the default values for its usage.
Parameters may again contain parameters which are referred to as "sub parameters".
The GSM specific extensions of some of the ETS 300 838 [14] profile B parameters are mentioned in this subclause even if they are related to the GSM specific part in clause 7.
These values shall be used by either the application and the GSM‑API if and only if the application has asked for GSM support as described in the clause 7.3 of this ETS.
|
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 parameter has the following structure:
struct B channel information;
struct reserved, shall be ignored;
struct User user data (coded according to ETS 300 102‑1 [15] / Q.931 [16]);
struct reserved, shall be ignored.
This information element appears in:
ALERT_REQ
CONNECT_REQ
CONNECT_IND
CONNECT_RESP
DISCONNECT_REQ
INFO_REQ
|
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 extending its contents in future changes. At the moment, it is coded as a structure of two bytes length and has one element:
word Channel:
0 use B channel (default value);
1 reserved, shall be rejected;
2 reserved, shall be rejected.
This sub parameter appears in parameter:
Additional information.
|
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 and framing;
word B2 protocol : Data link layer;
word B3 protocol : Network layer;
struct reserved, shall be ignored;
struct B2 configuration : Data link layer parameter;
struct B3 configuration : Network layer parameter;
This information element appears in:
CONNECT_REQ
CONNECT_RESP
SELECT_B_PROTOCOL_REQ
|
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 the selected B2 protocol:
### B2 protocol 0: link Address A, default is 0x03
### B2 protocol 2: link Address, default is 0xC1
### B2 protocol 3: bit 0: ´0´ ‑ automatic TEI assignment procedure shall be used. ´1´ ‑ the TEI value shall be used as fixed TEI. In this case Bit 7 ‑ Bit 1: TEI value
byte
Address B
This parameter has different meaning and default values depending on the selected B2 protocol:
### B2 protocol 0: link Address B, default is 0x01
### B2 protocol 2: not applicable
### B2 protocol 3: not applicable
byte
Modulo Mode
Mode of operation:
### 8 ‑ normal operation (Default)
### 128 ‑ extended operation
byte
Window Size
Window size, default is 7.
struct
XID
This parameter has different meaning and default values depending on the selected B2 protocol:
### B2 protocol 0: not applicable
### B2 protocol 2: this is the content of the XID response which is sent when a XID command is received.
### B2 protocol 3: not applicable
This sub parameter appears in parameter:
B protocol
|
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).
For B3 protocols 1, 2 and 3 (T.90NL, ISO8208, X.25 DCE) the following structure is defined:
word
LIC
Lowest incoming channel, default is 0
word
HIC
Highest incoming channel, default is 0
word
LTC
Lowest two‑way channel, default is 1
word
HTC
Highest two‑way channel, default is 1
word
LOC
Lowest outgoing channel, default is 0
word
HOC
Highest outgoing channel, default is 0
word
Modulo Mode
Mode of operation:
### 8 ‑ normal operation (default)
### 128 ‑ extended operation
word
Window Size
Used to configure non‑standard defaults for the transmit and receive window size, default is 2
For B3 protocol 4 (Fax G3) the following structure is used:
word
resolution
0: standard
1: high
word
format
0: SFF (Default, description in annex B)
1: Plain FAX Format (modified Huffman coding)
2: PCX
3: DCX
4: TIFF
5: ASCII
6: Extended ANSI
7: Binary‑File transfer
struct
station id
ID of the calling station. Coded in ASCII
struct
head line
Headline sent on each fax page. Coded in ASCII
This sub parameter appears in parameter:
B protocol
5.2.10 BC
BC (struct)
reserved, shall be ignored
This information element appears in:
CONNECT_IND
CONNECT_REQ
|
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 information element, see ETS 300 102 [15]).
At the calling side the value supplied by the application shall be transmitted over the network, 0x80 is the suggested default value.
At the called side the value received from the network shall be passed to the application.
Bytes 1..n
Number digits of the called party number information element.
This information element appears in:
CONNECT_IND
CONNECT_REQ
|
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 transmitted over the network, 0x80 is the suggested default value (NSAP according X.213 [25]). In this case, the first subaddress information octet should have the value 0x50.
At the called side, the value received from the network shall be passed to the application.
Bytes 1..n
Contents of the called party subaddress information element.
This information element appears in:
CONNECT_REQ
CONNECT_IND
|
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 application shall be transmitted over the network, 0x80 is the suggested default value (NSAP according X.213 [25]). In this case, the first subaddress information octet should have the value 0x50.
At the called side, the value received from the network shall be passed to the application.
Bytes 1..n
Contents of the calling party subaddress information element.
This information element appears in:
CONNECT_IND
CONNECT_REQ
LISTEN_REQ
|
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 elements.
Some of the CIP values only define a Bearer Capability (CIP 1 to 9) and some values define a combination of Bearer Capability and High Layer Compatibility (CIP 16 to 34). A Low Layer Compatibility information element is not defined with the CIP. The Low Layer Compatibility information element may be provided by the application if necessary. The following CIP values are defined:
CIP value
Service
Relation to call
0
no predefined profile
1
Speech
voice call
2
unrestricted digital information
UDI call using RLP(see note)
3
restricted digital information
UDI call using RLP(see note)
4
3,1 kHz audio
voice call
5
7 kHz audio
reserved, shall be rejected
6
video
reserved, shall be rejected
7
packet mode
reserved, shall be rejected
8
56 kBit/s rate adaptation
UDI call using RLP(see note)
9
unrestricted digital information with tones/announcements
reserved, shall be rejected
10..15
reserved
16
Telephony
Bearer Capability according to CIP 1.
High Layer Compatibility:
coding standard: CCITT
interpretation: First characteristics identification is to be used
Presentation: High layer protocol profile
High layer characteristics identification: Telephony
Coding of HLC:
<0x7D, 0x02, 0x91, 0x81>
17
Facsimile Group 2/3
fax G3 call
18
Facsimile Group 4 Class 1
Bearer Capability according to CIP 2.
High Layer Compatibility:
coding standard: CCITT
interpretation: First characteristics identification is to be used
Presentation: High layer protocol profile
High layer characteristics identification: Facsimile Group 4 Class 1
Coding of HLC:
<0x7D, 0x02, 0x91, 0xA1>
19
Teletex service basic and mixed mode and facsimile service Group 4 Classes II and III
Bearer Capability according to CIP 2.
High Layer Compatibility:
coding standard: CCITT
interpretation: First characteristics identification is to be used
Presentation: High layer protocol profile
High layer characteristics identification. Teletex service and facsimile service Group 4
Coding of HLC:
<0x7D, 0x02, 0x91, 0xA4>
(continued)
(continued)
CIP value
Service
Relation to call
20
Teletex service basic and processable mode
Bearer Capability according to CIP 2.
High Layer Compatibility:
coding standard: CCITT
interpretation: First characteristics identification is to be used
Presentation: High layer protocol profile
High layer characteristics identification. Teletex service basic and processable mode
Coding of HLC:
<0x7D, 0x02, 0x91, 0xA8>
21
Teletex service basic mode
Bearer Capability according to CIP 2.
High Layer Compatibility:
coding standard: CCITT
interpretation: First characteristics identification is to be used
Presentation: High layer protocol profile
High layer characteristics identification. Teletex service basic mode
Coding of HLC:
<0x7D, 0x02, 0x91, 0xB1>
22
International inter working for Videotex
Bearer Capability according to CIP 2.
High Layer Compatibility:
coding standard: CCITT
interpretation: First characteristics identification is to be used
Presentation: High layer protocol profile
High layer characteristics identification. International inter working for Videotex
Coding of HLC:
<0x7D, 0x02, 0x91, 0xB2>
23
Telex
Bearer Capability according to CIP 2.
High Layer Compatibility:
coding standard: CCITT
interpretation: First characteristics identification is to be used
Presentation: High layer protocol profile
High layer characteristics identification: Telex
Coding of HLC:
<0x7D, 0x02, 0x91, 0xB5>
24
Message Handling Systems according to X.400 [26]
Bearer Capability according to CIP 2.
High Layer Compatibility:
coding standard: CCITT
interpretation: First characteristics identification is to be used
Presentation: High layer protocol profile
High layer characteristics identification: Message Handling Systems according X.400
Coding of HLC:
<0x7D, 0x02, 0x91, 0xB8>
(continued)
(concluded)
CIP value
Service
Relation to call
25
OSI application according to X.200 [27]
Bearer Capability according to CIP 2.
High Layer Compatibility:
coding standard: CCITT
interpretation: First characteristics identification is to be used
Presentation: High layer protocol profile
High layer characteristics identification: OSI application according X.200
Coding of HLC:
<0x7D, 0x02, 0x91, 0xC1>
26
7 kHz Telephony
reserved, shall be rejected
27
Video Telephony, first connection
reserved, shall be rejected
28
Video Telephony, second connection
reserved, shall be rejected
32
Modem
modem call 8 data bits, no parity, 1 stop bit. Used only, if GSM services are requested.
33
Modem
modem call 7 data bits, even parity, 1 stop bit. Used only, if GSM services are requested.
34
In Call modification TS.61
use of In Call modification (TS.61 only). Used only, if GSM services are requested.
NOTE: RLP can be disabled by manufacturer specific mechanism. User rate and other subscription dependent parameter are manufacturer dependent and not part of GSM‑API. They should be configurable by manufacturer specific mechanism.
This information element appears in:
CONNECT_REQ
CONNECT_IND
|
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 message is sent to the application when the bit position within the CIP mask of any matching CIP value is set to "1". The CIP value in the CONNECT_IND message is set to the highest matching CIP value.
The following rules are defined to find matching CIPs:
1) CIP values which define a Bearer Capability only (CIP 1 to CIP 9) shall generate a match with any incoming call which includes a Bearer Capability with the same information. Additional information included in the Bearer Capability information element shall be ignored. The match shall be generated regardless of any Low Layer Compatibility or High Layer Compatibility received.
2) CIP values which define a Bearer Capability and a High Layer Compatibility (CIP 16 to CIP 28) shall generate a match with any incoming call which includes a Bearer Capability and a High Layer Compatibility with the same identical information. The match shall be generated regardless of any Low Layer Compatibility received.
Bit 0 in the CIP mask has a special meaning. When no other matching bit is set in the CIP mask but the Bit 0, a CONNECT_IND is sent to the application with a CIP value of 0. In this case the application may evaluate the parameters Bearer Capability, Low Layer Compatibility and High Layer Compatibility to decide whether it is compatible to the call or not. Examples:
Service
Bits to be set in the CIP mask
Telephony Application
1 For calls within ISDN from equipment which does not send High Layer Compatibility info.
|
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 element, see ETS 300 097 [28]).
In the direction application to Profile B, the value supplied by the application shall be transmitted over the network, 0x00 is the suggested default value.
In the direction Profile B to application, the value received from the network shall be passed to the application. The extension bit shall always be cleared.
Byte 1
Presentation and screening indicator (byte 3a of the connected number information element).
In the direction application to Profile B, the value supplied by the application shall be transmitted over the network, 0x80 is the suggested default value.
In the direction Profile B to application, the value received from the network shall be passed to the application. If this byte was not transmitted over the network, the controller provides the value 0x80 (user provided, not screened).
Bytes 2..n
Number digits of the connected number information element.
This information element appears in:
CONNECT_ACTIVE_IND
CONNECT_RESP
|
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 transmitted over the network, 0x80 is the suggested default value (NSAP according X.213 [25]). In this case, the first subaddress information octet should have the value 0x50.
At the called side, the value received from the network shall be passed to the application.
Bytes 1..n
Contents of the connected subaddress information element.
This information element appears in:
CONNECT_ACTIVE_IND
CONNECT_RESP
|
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 range from 1 to 127 (0 reserved). Bit 7 additionally contains the information, if the message is used for internal (0) or external (1) equipment. Controllers are numbered sequentially and can be designed to handle external equipment additional to internal functionality or exclusively provide access to external equipment. External equipment e.g. is a handset.
Definition of external equipment behaviour, e.g. B channel handling, is not covered by Profile B.
Format for controller:
0
0
0
Ext./Int.
Controller
31
16
8
7
6 0
This information element appears in:
CONNECT_REQ
FACILITY_REQ
FACILITY_CONF
FACILITY_IND
FACILITY_RESP
LISTEN_REQ
LISTEN_CONF
MANUFACTURER_REQ
MANUFACTURER_CONF
MANUFACTURER_IND
MANUFACTURER_RESP
|
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:
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.