hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 1 Scope | The present document specifies the stage 2 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN. Two implementations of IST are described: an implementation based on CAMEL, and an implementation based on a... |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 3 Definitions and abbreviations | |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 3.1 Definitions | For the purposes of the present document, the following definition apply: Subscriber activities: subscriber activities that must be terminated. These can be call related events (e.g. call set-up, call termination) or the invocation of call related and call independent supplementary services (e.g. Call Hold, Call Waitin... |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given is GSM 01.04 and the following apply: FDS Fraud Detection System FIGS Fraud Information Gathering System IST Immediate Service Termination MO Mobile Originated MT Mobile Terminated O-CSI Originating CAMEL Subscription Information T-CSI Terminating CAMEL ... |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 4 Information flows | |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 4.1 CAMEL implementation | For the Customised Applications for Mobile network Enhanced Logic (CAMEL) implementation of Immediate Service Termination (IST) for a particular subscriber, an "IST" command (in reality, the CAMEL message "ReleaseCall") must be sent by the gsmSCF of the home PLMN to the gsmSSF controlling the call, for all the calls of... |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 4.2 Non-CAMEL implementation | FFS |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 5 Functional behaviour - CAMEL implementation | This clause describes the implementation of IST using CAMEL. CAMEL can be used to terminate all the mobile originated (MO), mobile terminated (MT) and forwarded (CF) calls of a subscriber, provided there is a control relationship between the CAMEL server (the gsmSCF) in the HPLMN and the MSC (visited MSC or GMSC) (the ... |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 5.1 Subscriber settings | The subscriber is marked as a CAMEL subscriber by setting Originating CAMEL Subscription Information (O-CSI) and Terminating CAMEL Subscription Information (T-CSI) in the subscriber data stored in the HLR of the HPLMN. The O-CSI is sent to the VPLMN when the subscriber first registers in the VPLMN; the T-CSI is sent to... |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 5.2 DP Settings | A call cannot be terminated using CAMEL unless there is a control relationship between the gsmSCF and the gsmSSF controlling the call. To ensure that the IST command can be used at any point in the duration of a call, right up to the end of the call, there must be a control relationship until the end of the call. A "co... |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 5.3 Call termination | The HPLMN will be informed of the call attempts (MO, MT and CF) of the subscriber with message InitialDP. This message will give the address of the gsmSSF (=MSC) controlling the call. The call can be terminated by the gsmSSF at any time by sending message ReleaseCall to the controlling gsmSSF. The gsmSSF will then term... |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 6 Functional behaviour - Non-CAMEL implementation | FFS |
51d44a05e2c4070c4af708d7e99e7359 | 101 967 | 7 Control of IST | Definition of the method used by a PLMN to decide which subscribers to use IST upon is outside the scope of the present document. However, it is likely that the decision will be made by some sort of FDS within the PLMN. The interface between the FDS and the PLMN node that sends the IST command to the VPLMN (the CAMEL s... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 1 General | |
0a2b0663459bef39399bde42584d2507 | 101 642 | 1.1 Scope | The present document gives the principles on which the detailed interface specifications in the rest of the GSM 08.0X series of Technical Specifications are based. The set of fixed equipment accessed from the MSC through one particular instance of the interface will be later referred to as a Base Station System (BSS). ... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 1.2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 1.3 Definitions and abbreviations | Abbreviations used in the present document are listed in GSM 01.04 ETSI ETSI TS 101 642 V7.0.0 (1999-08) 8 (GSM 08.02 version 7.0.0 Release 1998) 2 Functional division between Base Station System (BSS) and MSC Functional split Item/Task BSS MSC,VLR,HLR Terrestrial Channel Management channel allocation X X blocking indi... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.1 Terrestrial channel management | |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.1.1 Terrestrial channel allocation | Terrestrial channel allocation will be handled in the following manner. The link between the MSC and the BSS will be considered by the BSS and the MSC as a route on "n" circuits. Within this route, certain of the circuits may not be able to support all types of traffic (e.g., data calls or half rate connections). This ... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.1.2 Blocking of terrestrial channels | The entity not allocating the circuits shall be able to remotely block the terrestrial channel and remove it from service. This is signalled across the BSS/MSC interface using the appropriate signalling exchange as defined in GSM 08.08. Local blocking of terrestrial channels on the side allocating the circuits may be s... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2 Radio channel management | |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.1 Channel configuration management | The channel configuration management will be controlled between BSS and maintenance centre, the MSC holding no direct data concerning the allocation of radio timeslots etc. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.2 Radio TCH management | |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.2.1 Radio channel allocation | The BSS shall choose the radio channel to be used on the appropriate cell, based on information received from the MSC, which defines the channel type, channel coding and all other parameters relevant to defining channel type. The chosen radio channel shall be connected to the terrestrial channel in order to support the... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.2.2 TCH radio link supervision | Radio link supervision of dedicated radio resources shall be the responsibility of the BSS. If communication with the mobile is lost then the BSS can request that the call be cleared. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.2.3 Frequency hopping management | Frequency hopping management shall be performed by the BSS. That is the BSS shall store and transmit all hopping parameters for the cell(s) that it controls, the hopping shall be performed such that it is not visible on the BSS/MSC interface. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.2.4 Idle channel observation | The quality of idle radio channels shall be measured by the BSS and a condensed form of the information passed back to the MSC. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.2.5 TCH power control | All power control functions shall be performed between MS and BSS. No real time power control commands shall be sent across the BSS/MSC interface. ETSI ETSI TS 101 642 V7.0.0 (1999-08) 10 (GSM 08.02 version 7.0.0 Release 1998) |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.2.6 TCH channel release | The release of a dedicated resource is primarily controlled by the MSC. However for radio propagation reasons the BSS can request of the MSC that a call be released. The necessary protocols are defined in GSM 08.08. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.3 BCCH CCCH management | All BCCH data shall be either stored at or derived locally by the BSS. CCCH random accesses shall be controlled autonomously by the BSS, paging messages shall be received from the MSC via the BSS/MSC interface. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.3.1 Scheduling of BCCH and CCCH messages | The scheduling for all BCCH and CCCH messages shall be performed by the BSS. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.4 DCCH Management | |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.4.1 DCCH link supervision | Radio link supervision of dedicated radio resources shall be the responsibility of the BSS. If communication with the mobile is lost then the BSS can request that the call be cleared. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.4.2 DCCH channel release | The release of a dedicated resource is primarily controlled by the MSC. However for radio propagation reasons the BSS can request of the MSC that a call be released. The necessary protocols are defined in GSM 08.08. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.4.3 DCCH power control | All power control functions shall be performed between MS and BSS. No real time power control commands shall be sent across the BSS/MSC interface. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.2.4.4 Radio Channel Allocation | The BSS shall choose the DCCH to be used on the appropriate cell. This shall be performed initially after the random access to the CCCH has been made by the MS. The chosen DCCH may at a later stage in the call be connected to the terrestrial channel in order to support the service, this is controlled by the appropriate... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.3 Resource indication | The status of idle radio channels is reported to the MSC using the protocol described in GSM 08.08. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.4 Channel coding decoding | The encoding decoding and interleaving shall be performed by the BSS. The type of channel coding and interleaving is derived from the information in the assignment message from the MSC. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.5 Transcoding/rate adaptation | Rate adaptation or transcoding shall be performed by the BSS. The selection of the appropriate function shall be based on information received from the MSC. ETSI ETSI TS 101 642 V7.0.0 (1999-08) 11 (GSM 08.02 version 7.0.0 Release 1998) |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.6 Interworking function (data calls) | The interworking function required for data calls to other networks shall be performed on the MSC side of the MSC/BSS interface. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.7 Measurement information | |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.7.1 Measurement information reported from the MS | Measurement information reported from MSs with dedicated radio resources shall be processed by the BSS. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.7.2 Uplink measurement information | The BSS shall process uplink information. The results of the processing of the "Measurement information reported from the MS" and the "Uplink measurement information" may be transmitted to the MSC as described in GSM 08.08. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.7.3 Traffic information | Traffic information concerning the traffic environment outside a BSS is not passed from MSC to BSS. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.8 Handover | Handovers (both internal and external) can occur for one of several reasons e.g. radio propagation, traffic distribution, O and M activity, equipment failure. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.8.1 Internal handover within one cell | Internal handover within one cell can be supported within a BSS. It is optional for an BSS to be able to perform autonomous internal handover. The MSC will be informed when an autonomous internal handover has been completed (see GSM 08.08). |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.8.2 Internal handover between cells | Internal Handover between cells on the same BSS can be supported within an BSS. Multi cell BSSs would normally be expected to support internal inter cell handover, however it is optional that they do so. The MSC will be informed when an autonomous internal handover has been completed (see GSM 08.08). |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.8.3 External handover | This type of handover includes inter MSC handover as discussed in GSM 03.09. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.8.3.1 Recognition that a handover is required for a radio reason | The BSS shall be able to generate an indication that a handover is required to the MSC using the protocols defined in GSM 08.08. No additional guidance is given in the GSM 08.0X series concerning the algorithm within the BSS that generates either an internal handover, or an indication to the MSC that an external handov... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.8.3.2 Recognition that a handover is required for a traffic reason | The BSS shall be able to generate an indication to the MSC that a handover is required for traffic reason (e.g. directed retry) using the protocols defined in GSM 08.08. Within a multi BSS area only the MSC has a perspective of the overall traffic loading. The MSC may therefore originate inter BSS traffic handovers due... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.8.3.3 Decision of Target Cell | The choice of the target cell in an external traffic handover shall be made by the MSC, based on information received from the BSS. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.8.3.4 Execution | Having received an indication from an BSS that an external handover is required, the decision of when and whether an external handover should take place shall be made by the MSC. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.9 Mobility management | All transactions concerning mobility management (as specified in GSM 04.08) shall take place transparently between the MS and MSC/VLR/HLR, using the protocols described in Technical Specifications GSM 08.08 and GSM 08.06. The only exception to this rule is that of paging which is scheduled by the BSS on the appropriate... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.10 Call control | Call control will be the responsibility of the MSC/HLR/VLR. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.11 Security features | Information on security aspects are found in GSM 03.20. The BSS/MSC interface supports all of the required interchange of encryption keys. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.11.1 User data confidentiality | Encryption and decryption of user data (e.g. speech) takes place within the mobile station and within the BSS. In order to decrypt/encrypt user data the encryption device used for the call must be loaded with the relevant key and algorithm. The key and the permitted algorithms are supplied by the MSC. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.11.2 User identity confidentiality | This feature is supported by using a TMSI rather than an IMSI, over the radio path. The translation between TMSI and IMSI is performed at the MSC and within the mobile. Both TMSI and IMSI are carried transparently by the BSS-MSC interface as far as possible. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.11.3 Signalling information confidentiality | As for user data. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 2.11.4 Authentication of users | Authentication is carried out at the mobile and at the MSC/VLR/HLR. The MSC to BSS interface is required to transport the necessary challenge and response messages. ETSI ETSI TS 101 642 V7.0.0 (1999-08) 13 (GSM 08.02 version 7.0.0 Release 1998) |
0a2b0663459bef39399bde42584d2507 | 101 642 | 3 Transcoder/rate adapter integration | The transcoder will be functionally integrated into the BSS. It is not considered to be a stand alone piece of equipment. The control of the transcoder will therefore take place directly via the BSS, an explicit control interface between BSS and transcoder will not be defined. Dependent on the relative costs of transmi... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 5 Classes of signalling messages | The signals between BSS and MSC are classified under three headings: i) DTAP messages ¶¶¶¾¶¶ BSSAP messages ii) BSS management ¶¶¶» iii) BSS O&M Where DTAP BSSMAP and BSSAP are as defined in GSM 08.08. Layer 3 call control messages will as far as possible pass transparently through the BSS. The discrimination between B... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 6 Support of services and features other than speech | |
0a2b0663459bef39399bde42584d2507 | 101 642 | 6.1 Data services | In order to ensure that the requirements of GSM 03.10 are met, the support of data services will entail the following 7 actions being taken: i) the speech coder being deactivated in the mobile; ii) a rate adaptation function being activated in the mobile; iii) an appropriate channel coding being activated in the mobile... |
0a2b0663459bef39399bde42584d2507 | 101 642 | 6.2 Supplementary services | All signalling concerned with supplementary services is passed transparently through the BSS via the DTAP. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 7 Interface structures | The definition of the MSC to BSS interface follows a layered approach. This is shown in figure 1. In the case of a digital link being used between the BSS and MSC, the signalling will be carried in one of the 64kbits/s timeslots. |
0a2b0663459bef39399bde42584d2507 | 101 642 | 8 Operation and maintenance | Operation and maintenance information is required to flow between the BSS and O & M functions. The BSS to MSC interface provides for this type of information see GSM 12.01. ETSI ETSI TS 101 642 V7.0.0 (1999-08) 15 (GSM 08.02 version 7.0.0 Release 1998) BSS-SIDE MSC-SIDE A-INTERFACE To other processes within the BSS BSS... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the test specifications for Diameter protocol on the Gx interface as specified in TS 129 212 [1] in compliance with the relevant requirements and in accordance with the rel... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 129 212 (V10.5.0): "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Gx/Sd reference point (3GPP TS 29.212 version 10.5.0 Release 10)". [2] ETSI TS 101 606-2: "IMS Network Te... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 3 Definitions and abbreviations | |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [5] and TS 129 212 [1] apply. |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [3], ISO/IEC 9646-6 [4], ISO/IEC 9646-7 [5] and TS 129 212 [1] apply. |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4 Abstract Test Method (ATM) | This clause describes the ATM used to test the Diameter protocol on the Gx interface at the PCEF side and at the PCRF side. |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4.1 Test architecture | |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4.1.1 Test method | The test method chosen is the remote test method. Remote test method means that the test tool (the test machine + the executable test suite) shall behave as a PCRF when the IUT is a PCEF and shall behave as a PCEF when the IUT is a PCRF. As the exchange between the test system and the IUT is at the diameter message lev... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4.1.2 Test machine configuration | |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4.1.2.1 Test configurations for PCEF testing | The Gx interface is located between PCRF and the SUT. The GTP interfaces are used to trigger the SUT. Figure 1: Test architecture with PCEF as SUT |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4.1.2.2 Test configurations for PCRF testing | The Gx interface is located between PCEF and PCRF. The Rx interface is located between PCEF and the SUT. Figure 2: Test architecture with PCRF as SUT ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 9 |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4.1.3 Interconnection of TS and SUT | |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4.1.3.1 PCEF Role | Figures 3 and 4 show the interconnection of TS and SUT in terms of signalling message flows. Diameter messages are transferred over the DIAM port. Lower Layer Primitives are transferred over the LLPP port. Some PCEF tests may require additional triggering via the GTP ports. This configuration can be disabled using PIXI... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4.1.3.2 PCRF Role | Figures 5 and 6 show the interconnection of TS and SUT in terms of signalling message flows. Diameter messages are transferred over the DIAM port. Lower Layer Primitives are transferred over the LLPP port. Some PCRF tests may require additional triggering via the Rx interface (see figure 6). system:LLIMS TS port:DIAMP ... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 4.1.3.3 Test Adapter | For execution of the tests the Test Adapter (TA) shall be developed. There are two possibilities to communicate over TA: • ATS provides only Diameter messages; or • ATS provides Diameter messages and LL primitives. |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5 ATS conventions | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the naming conventions and... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.1 Testing conventions | |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.1.1 Test cases Preamble and Postamble | As described in the test method clause the test tool shall behave as a PCRF when the IUT is a PCEF and shall behave as a PCEF when the IUT is a PCRF. For that reason the test case preambles and postambles are named as follows: IUT is a PCRF (example TC_PCRF_IPS_01) f_preamble_PCEF f_postamble_PCEF NOTE 1: The tester al... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.2 Naming conventions | |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.2.1 General guidelines | The naming conventions are based on the following underlying principles: • In most cases, identifiers should be prefixed with a short alphabetic string (specified in table 1) indicating the type of TTCN-3 element it represents. • Suffixes should not be used except in those specific cases identified in table 2. • Prefix... |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.2.2 Test case grouping | The ATS structure is based on the Test Purposes for the Diameter protocol on the Gx interface as defined in TS 101 606-2 [2]. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 13 |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.2.3 Test case identifiers | The test cases have been divided according to the functionalities into several groups. The test case names are built up according to the following scheme: Table 2: TC identifier naming convention scheme Identifier: "<tc>"_"<iut >"_"<scope >"_"<number>" <tc> = Test Case: fixed to "TC" <iut> = type of IUT: PCRF or PCEF <... |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 1 Scope | The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the test specifications for the Diameter protocol on the Gx interface as specified in TS 129 212 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 4... |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 129 212: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Gx/Sd reference point (3GPP TS 29.212 version 10.5.0 Release 10)". [2] ETSI TS 101 606-1: "IMS Network Testing (INT... |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 6 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 3 Definitions and abbreviations | |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 129 212 [1] and the following apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [3]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3]. Test Purpose (TP): Refer to ... |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 129 212 [1] and the following apply: TP Test Purpose TSS Test Suite Structure |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 4 Test configurations | |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5 Test Suite Structure (TSS) and Test Purposes (TP) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.