hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b63685a584764961b7ae3e51726522bc | 104 081 | 6.28 Annex E (informative): Library of Useful Types | The technical contents of Annex E in ETSI ES 201 873-1 (V4.17.1) [i.1] will remain unchanged. 6.29 Annex F (informative): Operations on TTCN‑3 active objects The technical contents of Annex F in ETSI ES 201 873-1 (V4.17.1) [i.1] will be moved to ETSI TR 104 873 (V5.1.1). ETSI ETSI TR 104 081 V5.1.1 (2026-04) 24 |
b63685a584764961b7ae3e51726522bc | 104 081 | 7 Features in extensions | 7.0 General This clause lists the features that became part of ETSI ES 201 873-12 (V5.1.1). Clause 7.1 lists the features that are moved from the core language to ETSI ES 201 873-12 (V5.1.1), while the rest of the clauses list the features that will be moved from the current extensions (ETSI ES 202 781 [i.8] to ETSI ES... |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1 Features moved from TTCN-3 core to extensions | |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.0 General | This clause provides a list of TTCN-3 concepts and features which are moved from the core language ETSI ES 201 873-1 (V4.17.1) [i.1] to ETSI ES 201 873-12 (V5.1.1). |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.1 The concept of procedure-based communication | The whole concept of procedure-based communication (see clause 22.3 in ETSI ES 201 873-1 (V4.17.1) [i.1] will be moved to ETSI ES 201 873-12 (V5.1.1). This change will also have an effect on several additional clauses. Those parts of these clauses that are related to the concept of procedure-based communication will al... |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.2 Automatic type | The concept of Automatic type (see clause 6.5 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1) without the following exception that will remain in the core language: • The automatic typing will only be allowed only if on the right-hand side of the assignment there is a reference or a l... |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.3 Shift operators | Shift operators (see clause 7.1.6 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1). ETSI ETSI TR 104 081 V5.1.1 (2026-04) 25 |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.4 Rotate operators | Rotate operators (see clause 7.1.7 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1). |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.5 The not-implemented function | The not-implemented function (see clause 16.1.6 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1). |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.6 The Label statement | The Label statement (see clauses 18 and 19.7 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1). |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.7 The Goto statement | The Goto statement (see clauses 18 and 19.8 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1). |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.8 Call test component behaviour operation | The Call test component behaviour operation (see clause 21.3.10 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1). |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.1.9 Retrieving attribute values | The Retrieving attribute values operations (see clause 27.8 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1). These operators are primarily relevant for conformance testing and are not essential to the fundamental semantics of TTCN-3. 7.2 Features moved from TTCN-3 extension packages t... |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.2.0 General | The following list includes the handling of the TTCN-3 extensions with respect to the major new release of TTCN-3. The language extensions are: • ETSI ES 202 781 [i.8]; • ETSI ES 202 782 [i.9]; • ETSI ES 202 784 [i.10]; • ETSI ES 202 785 [i.11]; • ETSI ES 202 786 [i.12]; • ETSI ES 203 790 [i.13]; • ETSI ES 203 022 [i.1... |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.2.1 TTCN-3 language extension: Configuration and Deployment Support | Configuration and deployment support (ETSI ES 202 781 [i.8]) will not be supported in the future. ETSI ETSI TR 104 081 V5.1.1 (2026-04) 26 7.2.2 TTCN-3 language extension: TTCN-3 Performance and Real-time Testing For Performance and real-time testing (ETSI ES 202 782 [i.9]): • the predefined function wait; and • the ti... |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.2.3 TTCN-3 language extension: Advanced Parameterization | For Advanced Parameterization (ETSI ES 202 784 [i.10]): • type parameterization will be supported in ETSI ES 201 873-12 (V5.1.1), including default type parameters and nested actual type parameters; • all type references in ports and value parameterization will not be supported in the future. |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.2.4 TTCN-3 language extension: Behaviour Types | A simplified version of the TTCN-3 language extension behaviour types (ETSI ES 202 785 [i.11]) will be supported in ETSI ES 201 873-12 (V5.1.1). • In the function, altstep, and testcase behaviour types definition the following parameters will not be allowed: [ "<" { FormalTypePar [","] } ">" ] "(" [ { ( FormalValuePar ... |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.2.6 TTCN-3 language extension: Extended TRI | The TTCN-3 language extension Extended TRI (ETSI ES 202 789 [i.16]) will not be supported in the future. Parts of this extension will be moved to ETSI ES 201 873-13 (V5.1.1)". |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.2.7 TTCN-3 language extension: Advanced Matching | From the TTCN-3 Language extension Advanced Matching (ETSI ES 203 022 [i.14]), the Dynamic matching will be moved to ETSI ES 201 873-12 (V5.1.1). None of the other features of this extension will be supported in the future. |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.2.8 TTCN-3 language extension: Object-Oriented Features | The technical contents of the TTCN-3 language extension Object-Oriented Features (ETSI ES 203 790 [i.13]) will be supported in the future. It has not yet been decided whether ETSI ES 203 790 [i.13] will remain a separate document or be integrated into ETSI ES 201 873-12 (V5.1.1). ETSI ETSI TR 104 081 V5.1.1 (2026-04) 2... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8 Changes of features | |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.0 General | This clause highlights the proposed changes on the core language, mentioned in clause 6 of the present document. Clause 8.1 lists the proposed changes that are backward-compatible, while clause 8.2 lists the proposed changes that are backward-incompatible. |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1 Backward-compatible changes | |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.0 General | This clause lists the proposed backward-compatible changes to the TTCN-3 core language. |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.1 Introduction of 'root scope' | To simplify scoping rules for predefined functions (see clauses C.1 to C.6 in ETSI ES 201 873-1 (V4.17.1) [i.1]) and Useful TTCN-3 types (see clause E.2 in ETSI ES 201 873-1 (V4.17.1) [i.1]) a 'root' scope will be introduced. In the hierarchy of scope units 'root' scope will be above the 'module definitions part' scope... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.2 Module parameters | All parameterization (see clause 5.4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) in TTCN-3 takes effect dynamically at runtime, except for the module parameters that are supplied by the test environment at the beginning of the execution, and then they do not change their values during test execution. Because of this differen... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.3 Bitstrings, Hexstrings and Octetstrings | Values of types bitstring, hexstring and octetstring (see clause 6.1.1 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will not only be denoted by the uppercase 'B, 'H, 'O characters, but their lowercase equivalents 'b, 'h, 'o will also be enabled, like: '0101'b, 'ABCD'h and 'ABCD'o. |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.4 Character strings | The default string type will be the current universal charstring type. The new and shorter string will be introduced for it, but for backward compatibility reasons the universal charstring keyword will also be kept. The current charstring type will be defined as a subtype of the new string type. This will allow to simp... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.5 Records and sets of single types and Arrays | For the Record and Set of elements of the same type (see clause 6.2.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) the rules describing how many elements a partially initialized record of/set of has, and what happens if a value on the right-hand side of an assignment has different number of elements than that of on the left-h... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.6 Communication port types | Since procedure-based communication will be moved to ETSI ES 201 873-12 (V5.1.1), in the core language only the message-based port type (see clause 6.2.9 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will remain. In message-based port type definitions the keyword message will be optional (it will be kept only for backward comp... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.7 Automatic type | The concept of Automatic type (see clause 6.5 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1) without the following exception that will remain in the core language: • The automatic typing will only be allowed only if on the right-hand side of the assignment there is a reference or a l... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.8 Declaring templates | The proposed backward-compatible modifications related to templates (see clause 15 in ETSI ES 201 873-1 (V4.17.1) [i.1]) are the following: • Templates without a (possibly empty) parameter list are static templates. They will be evaluated only once, at the place of their declaration. NOTE 1: A static template retains t... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.9 Check operation | Because the procedure-based communication operations (see clause 22.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1), the syntax of the Check operation (see clause 22.4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) can be simplified, it will be optional to explicitly refer to the receive ope... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.10 Number of elements of lists (sizeof predefined function) | The functionality of the sizeof predefined function (see clause C.2.2 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be extended. It will be applicable not only for record or set type values and templates, but also for string and record of or set of values or templates. If it is applied for values and templates of: • recor... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.1.11 Conversion functions | Because the universal charstring becomes the 'default' string type, all the to/from character string conversion functions (see clause C.1 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will have to/from universal string equivalents. Currently the following conversion functions of this kind are missing: int2unistr, bit2unistr, h... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2 Backward-incompatible changes | |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.0 General | This clause lists the proposed backward-incompatible changes to the TTCN-3 core language. |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.1 Fuzzy and lazy values and templates and lazy evaluation | The concepts of Fuzzy and lazy values and templates (see clause 4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) and lazy evaluation (see clause 4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be removed. This change will also have an effect on several additional clauses. Those parts of these clauses that are related to the concep... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.2 Embedded fields | The concept of embedded fields (see clause 6.2.1.4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be deleted. |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.3 Array dimensions specified using ranges | The possibility of defining arrays by specifying its lower and upper index (see clause 6.2.7 in ETSI ES 201 873-1 (V4.17.1) [i.1]), like: type integer MyArrayType2[2 .. 5]; will be removed, indexes of the arrays will always start by 0. |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.4 Importing from modules | Importing from modules (see clauses 8.2.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be significantly simplified, only import all will be supported, that is the import of single definitions (module parameters, user defined types, signatures, constants, templates, functions, external functions, altsteps, test cases, and... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.5 Templates | The proposed backward-incompatible modifications related to templates (see clause 15 in ETSI ES 201 873-1 (V4.17.1) [i.1]) is the following: Dynamic templates (templates with a possibly empty parameter list) can only be global templates. NOTE: There are additional, backward-compatible modifications on Templates, see cl... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.6 Range-based loops | The specification of the range-based loops (see clause 19.4.2 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be clarified. In order to be able to iterate over partially initialized range expressions, and to keep the existing functionalities of the assignments (see clause 19.1 in ETSI ES 201 873-1 (V4.17.1) [i.1]), the spec... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.7 Interleave statement | For the interleave statement (see clause 20.4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) the following semantical simplification is proposed: • Complexity is introduced into the interleave statement by allowing reception statements in statement blocks of alternatives in interleave statements. Each reception statement adds t... |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.8 The Trigger operation | The Trigger operation (see clause 22.2.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be deleted. |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.9 With statement | The with statement (see clause 27.2 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be simplified. The display attribute will be deleted. The optional DefinitionRef and AllRef attributes will be deleted. |
b63685a584764961b7ae3e51726522bc | 104 081 | 8.2.10 Display attributes | Because Display attributes (see clause 27.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) is not reported to be used, this feature will be deleted. 8.2.11 Encoding attributes and Dynamic configuration of encoding used by ports The multiple encoding feature (see clause 27.4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) and the Dynamic ... |
b63685a584764961b7ae3e51726522bc | 104 081 | 9 Deleted features | |
b63685a584764961b7ae3e51726522bc | 104 081 | 9.0 General | This clause highlights the proposed features mentioned in clause 6 of the present document that will not be supported in the future by TTCN-3 (V5.1.1). ETSI ETSI TR 104 081 V5.1.1 (2026-04) 34 |
b63685a584764961b7ae3e51726522bc | 104 081 | 9.1 Fuzzy and lazy values and templates and lazy evaluation | The concepts of Fuzzy and lazy values and templates (see clause 4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) and lazy evaluation (see clause 4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be removed. This change will also have an effect on several additional clauses. Those parts of these clauses that are related to the concep... |
b63685a584764961b7ae3e51726522bc | 104 081 | 9.2 Embedded fields | The concept of embedded fields (see clause 6.2.1.4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be deleted. |
b63685a584764961b7ae3e51726522bc | 104 081 | 9.3 Array dimensions specified using ranges | The possibility of defining arrays by specifying its lower and upper index (see clause 6.2.7 in ETSI ES 201 873-1 (V4.17.1) [i.1]), like: type integer MyArrayType2[2 .. 5]; will be removed, indexes of the arrays will always start by 0. |
b63685a584764961b7ae3e51726522bc | 104 081 | 9.4 Importing of single definitions from modules | Importing from modules (see clauses 8.2.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be significantly simplified, only import all will be kept, that is the import of single definitions (module parameters, user defined types, signatures, constants, templates, functions, external functions, altsteps, test cases, and impo... |
b63685a584764961b7ae3e51726522bc | 104 081 | 9.5 The Trigger operation | The Trigger operation (see clause 22.2.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be deleted. |
b63685a584764961b7ae3e51726522bc | 104 081 | 9.6 With statement | The with statement (see clause 27.2 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be simplified: • The display attribute will be deleted. • The optional DefinitionRef and AllRef attributes will be deleted. |
b63685a584764961b7ae3e51726522bc | 104 081 | 9.7 Display attributes | Because Display attributes (see clause 27.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) is not reported to be used, this feature will be deleted. 9.8 Encoding attributes and Dynamic configuration of encoding used by ports The multiple encoding feature (see clause 27.4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) and in connection w... |
b63685a584764961b7ae3e51726522bc | 104 081 | 9.9 Deprecated language features | All deprecated language features (see Annex G in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be deleted. This includes the following: • Group style definition of module parameters (see clause G.1 in ETSI ES 201 873-1 (V4.17.1) [i.1]). • Using all in port type definitions (see clause G.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]... |
b63685a584764961b7ae3e51726522bc | 104 081 | 10 Working procedures | |
b63685a584764961b7ae3e51726522bc | 104 081 | 10.1 General | This clause contains a list of the agreed-upon work processes that are applied during the development of ETSI ES 201 873-1 (V5.1.1), ETSI ES 201 873-12 (V5.1.1), ETSI ES 201 873-13 (V5.1.1), ETSI ES 201 873-7 (V5.1.1), ETSI ES 201 873-9 (V5.1.1), ETSI ES 201 873-10 (V5.1.1), ETSI ES 201 873-11 (V5.1.1), ETSI TR 104 873... |
b63685a584764961b7ae3e51726522bc | 104 081 | 10.2 CR process | The GitLab issue tracker is used to request changes. Change Requests (CRs) are the basis for managing changes and tracking discussions on the standard. The detailed operating procedure of submitting a CR is explained at https://labs.etsi.org/rep/mts/ttcn3/standard/- /blob/main/docs/how-to-make-a-change-request.md. The ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 1 Scope | This Technical Specification (TS) specifies the stage 2 description for the second phase (see GSM 02.78 [2]) of the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms to support services of operators which are not covered by standardized GSM services even when roamin... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 2 Normative references | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - Fo... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 3 Definitions and abbreviations | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 3.1 Definitions | For the purposes of this TS, the following definitions apply: Basic Call State Model (BCSM): The BCSM provides a high-level model of GMSC- or MSC/VLR-activities required to establish and maintain communication paths for users. As such, it identifies a set of basic call activities in a GMSC or MSC/VLR and shows how thes... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 3.2 Abbreviations | Abbreviations used in this specification are listed in GSM 01.04 [1]. For the purposes of this TS, the following abbreviations apply: BCSM Basic Call State Model CAMEL Customized Applications for Mobile network Enhanced Logic DP Detection Point EDP Event Detection Point GMSC Gateway MSC gsmSCF GSM Service Control Funct... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4 Architecture | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.1 Functional Entities used for CAMEL | This subclause describes the functional architecture needed to support CAMEL. Also the additions needed to the basic GSM functionality are described. Figure 1 shows the functional entities involved in calls requiring CAMEL support. The architecture is applicable to the second phase of CAMEL. HLR GMSC gsmSCF MSC Forward... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.2 Interfaces defined for CAMEL | This subclause describes the different interfaces applicable to CAMEL. It specifies on a high level the functions specific to CAMEL. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.2.1 HLR - VLR interface | This interface is used to send the CAMEL related subscriber data to the visited PLMN and for provision of MSRN. The interface is also used to retrieve subscriber status and location information of the mobile subscriber or to indicate suppression of announcement for a CAMEL service. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.2.2 GMSC - HLR interface | This interface is used at terminating calls to exchange routeing information, subscriber status, location information, subscription information and suppression of announcements. The O/T-CSI that is passed to the IPLMN is sent over this interface. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.2.3 GMSC - gsmSSF interface | This is an internal interface. The interface is described in the specification to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.). |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.2.4 gsmSSF - gsmSCF interface | This interface is used by the gsmSCF to control a call in a certain gsmSSF and to request the gsmSSF to establish a connection with a gsmSRF. Relationships on this interface are opened as a result of the gsmSSF sending a request for instructions to the gsmSCF. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.2.5 MSC - gsmSSF interface | This is an internal interface. The interface is described in the specification to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.). |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.2.6 gsmSCF - HLR interface | This interface is used by the gsmSCF to request information from the HLR. As a network operator option the HLR may refuse to provide the information requested by the gsmSCF. This interface is also used for USSD operations, both for gsmSCF-initiated dialogues and MS-initiated dialogues (relayed via HLR). It is a network... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.2.7 gsmSCF - gsmSRF interface | This interface is used by the gsmSCF to instruct the gsmSRF to play tones/announcements to the users. ETSI TS 101 441 V6.2.0 (1998-11) 15 GSM 03.78 version 6.2.0 Release 1997 |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 4.2.8 MSC - gsmSCF interface | This interface is used by the MSC to send supplementary service invocation notifications to the gsmSCF. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 5 Detection Points (DPs) | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 5.1 Definition and description | Certain basic call events may be visible to the GSM Service Control Function (gsmSCF). The DPs are the points in call at which these events are detected. The DPs for Mobile Originated Calls and Mobile Terminated Calls are described in subclauses 0 and 0. A DP can be armed in order to notify the gsmSCF that the DP was e... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 5.1.1 Arming/disarming mechanism | The mechanism by which the DP is armed. A DP may be statically armed or dynamically armed. The following arming rules apply: - DP for mobile terminating call handling is statically armed in GMSC as result of T-CSI delivery from HLR. DP for forwarding leg handling is statically armed in GMSC as result of O-CSI delivery ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 5.1.2 Criteria | Criteria are the conditions that must be met in order for the gsmSSF to request instructions from the gsmSCF. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 5.1.2.1 Criteria for a terminating call | The criteria for a terminating call are checked in the HLR. The HLR may store a list of up to 5 basic service codes, each of which may represent an individual basic service or a basic service group. This list is a triggering list. The basic service criterion is met if the basic service for the call matches a stored ind... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 5.1.2.2 Criteria for an originating call or a forwarded call | The criteria for an originating or forwarded call are checked in the originating or forwarding MSC. NOTE: In the case of a forwarded call, the HLR may decide not to include the CAMEL subscription information in the subscriber data sent to the GMSC if the triggering criteria are not met. The following criteria are appli... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 5.1.3 Relationship | Given that an armed DP was encountered, the gsmSSF provides an information flow via a relationship. A relationship between the gsmSSF and the gsmSCF for the purpose of operator specific service processing is considered to be a CAMEL relationship. There are two types of CAMEL relationships: - A CAMEL control relationshi... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 5.2 DP processing rules | The gsmSSF shall apply the following set of rules during DP processing to ensure a single point of control: - EDPs are disarmed by the gsmSSF as they are encountered and reported to the gsmSCF, or when the leg clears. - A control relationship persists as long as there is 1 or more EDP-R armed for this portion of the ca... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6 Description of CAMEL Subscriber Data | 6.1 Originating/Terminating CAMEL Subscription Information (O/T-CSI) This subclause defines the contents of the Originating/Terminating CAMEL Subscription Information. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.1.1 gsmSCF address | Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routeing. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.1.2 Service Key | The Service Key identifies to the gsmSCF the service logic that should apply ETSI TS 101 441 V6.2.0 (1998-11) 18 GSM 03.78 version 6.2.0 Release 1997 |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.1.3 Default Call Handling | The Default Call Handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.1.4 TDP List | The TDP List indicates on which detection point triggering shall take place. For O-CSI only DP2 is used. For T-CSI only DP12 is used. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.1.5 DP criteria | The DP criteria indicate whether the gsmSSF shall request the gsmSCF for instructions. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.1.6 CAMEL Capability Handling | CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. NOTE: If CAMEL is not supported or if a lower phase of CAMEL is supported in the VLR, the HLR can decide on a subscriber basis to apply ODB, perform normal call handling or perform operator specific handling (eventually... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.2 Other CAMEL data | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.2.1 USSD CAMEL Subscription Information (U-CSI) | The subscription information specified in this subclause is for information only. This subclause defines the contents of the USSD CAMEL Subscription Information (U-CSI). The U-CSI consists of a list of pairs of the following two parameters. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.2.1.1 Service Code | Service code for a specific application in a gsmSCF which interacts with the user by USSD. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.2.1.2 gsmSCF address | Address to be used to access the gsmSCF for a particular subscriber and a particular service code. The address shall be an E.164 number to be used for routeing. 6.2.2 Supplementary Service Invocation Notification CAMEL Subscription Information (SS-CSI) |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.2.2.1 Content of the SS-CSI | This subclause defines the contents of the Supplementary Service Invocation Notification CAMEL Subscription Information (SS-CSI). |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.2.2.1.1 Notification criteria | This data indicates for which supplementary services notifications shall be sent. The supplementary services which may be indicated are ECT, CD and MPTY. ETSI TS 101 441 V6.2.0 (1998-11) 19 GSM 03.78 version 6.2.0 Release 1997 |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.2.2.1.2 gsmSCF address | Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routeing. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.2.3 Location information/Subscriber state Interrogation | This data indicates whether additional subscriber information shall be sent to the GMSC as part of the terminating call handling. - an indication that the HLR shall send the location information of the called subscriber. - an indication that the HLR shall send the subscriber state of the called subscriber. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 6.2.4 Translation Information Flag (TIF-CSI) | A flag (TIF-CSI) in the CAMEL Subscriber data in the HLR indicates, when the subscriber registers a forwarded-to number, that the HLR shall not attempt to perform any translation, number format checks, prohibited FTN checks, call barring checks (cf. 0). If the flag is absent, this indicates that a translation is needed... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.