hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 5.1 Date of the statement | ......................................................................................................................................................................................... ETSI ETSI TS 102 710-1 V3.1.1 (2011-05) 9 |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 5.2 Implementation Under Test (IUT) identification | IUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... IUT version: ......................................................................................................................................................................................... |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 5.3 System Under Test (SUT) identification | SUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... Hardware configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Operating system: ......................................................................................................................................................................................... |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 5.4 Product supplier | Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 102 710-1 V3.1.1 (2011-05) 10 |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 5.5 Client (if different from product supplier) | Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 5.6 PICS contact person | (A person to contact if there are any queries concerning the content of the ICS) Name: ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 5.7 Global statement of conformance | Are all mandatory capabilities implemented? (Yes/No) ..................... ETSI ETSI TS 102 710-1 V3.1.1 (2011-05) 11 NOTE: Answering "No" to this question indicates non-conformance to the [1] specification. Non-supported mandatory capabilities are to be identified in the ICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma. |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 6 Statement of conformance to TS 129 163 | |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 6.1 Major capabilities | Table 6.1.1: Major capabilities Item Item description Reference Status Support 1 The System Under Test is interconnected with an ISUP network 7.2 o.1 2 The System Under Test is interconnected with an BICC network 7.3 o.1 o.1: It is mandatory to support exactly one of these items. Comments: |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 6.2 Basic call capabilities | Table 6.2.1: Basic call capabilities Item Item description Reference Status Support 1 The System is able to support preconditions requested in the Supported header or Require header? 7.2.3.1.1 o 2 The SUT sends the IAM indicating the COT procedure immediately after the reception of the INVITE and precondition extension is included in the SIP Supported or Require header 7.2.3.1.1 c7211 3 The SUT sends the INVITE request without waiting for an outstanding COT message 7.2.3.2.1.2 o.2 4 the SUT defers sending the INVITE request until receiving a COT message 7.2.3.2.3 o.2 5 The SUT supports the PSTN XML Schema to be used for providing the BearerCapability, Low Layer Compatibility, High Layer Compatibility and Progress indicator embedded as body in SIP messages F.2 o 6 The Forward call indicators Interworking indicator is set to '0', ISDN user part/BICC indicator is set to '1', ISDN access indicator is set to '1' if the TMR in the IAM is sent with the value '64 kbit/s unrestricted' 7.2.3.1.2.3 o 7 The sending of the User Teleservice Information parameter is supported driven from the PSTN XML HighLayerCharacteristics element 7.2.3.1.2.5 c7212 8 The HOP counter procedure is supported and mapping from/to the Max-Forwards header is supported 7.2.3.1.2.9 o 9 The P-Early-Media header is supported 7.2.3.1.4, 7.2.3.1.4A, 7.2.3.1.4B o 10 The SUT generates a Call-Info header field, or an Alert-Info header field to provide media instead of the in-band media received from the PSTN 7.2.3.1.4, 7.2.3.1.4A o 11 The SUT sends an INR message to request the calling party number and not send the INVITE request until receiving an INF message with calling party number If no calling party number is received in the incoming IAM message 7.2.3.2.1.3 o ETSI ETSI TS 102 710-1 V3.1.1 (2011-05) 12 Item Item description Reference Status Support 12 If no calling party number is received in the INF message the SUT reject the communication 7.2.3.2.1.3 c7213 13 The sending of 'dai' parameter is supported 7.2.3.2.2B.2 o 14 The SUT has the knowledge that the call is transited to a PSTN network, the SUT decides not to generate the awaiting answer indication when receiving the 180 Ringing message and backward early media is not authorized 7.2.3.2.4 o 15 The SUT is supporting capabilities associated with the Alert-Info header field 7.2.3.2.4 o 16 the SUT initiates the sending of the awaiting answer indication if the header authorizes backward early media 7.2.3.2.4 o 17 the SUT terminates the sending of the awaiting answer indication if the header authorizes backward early media 7.2.3.2.4 o 18 The Backward call indicators Interworking indicator is set to '0', ISDN user part/BICC indicator is set to '1', ISDN access indicator is set to '1' if the TMR in the IAM was received with the value '64 kbit/s unrestricted' 7.2.3.2.5.1 o 19 Does the SUT instruct the MGW to send media available at the associated URL to the PSTN leg of the communication if a reINVITE is received containing a Call-Info header field? 7.2.3.2.11A o 20 Does the SUT supporting the capabilities associated with the Error-Info header field the SUT instruct the IM-MGW to play out media available at the associated URL towards PSTN 7.2.3.2.12 o 21 The PSTN XML sendingCompleteIndication, if present, is mapped to the sending terminated digit (hexadecimal digit F) in the address signals field of the Called Party Number parameter. 7.2.3.1.2.1 o o.2: It is optional to support exactly one of these items. c7211: IF 7.2.1/1 THEN o ELSE n/a c7212: IF 7.2.1/5 THEN o ELSE n/a c7213: IF 7.2.1/11 THEN o ELSE n/a Comments: Table 6.2.2: Number portability and Carrier based routing Item Item description Reference Status Support 1 Number Portability Separate Directory Number Addressing Method is used 7.2.3.1.2A.1.1 o.3 2 Number Portability Concatenated Addressing Method is used 7.2.3.1.2A.1.2 o.3 3 Number Portability Separate Network Routing Number Addressing Method is used 7.2.3.1.2A.1.3 o.3 4 Number Portability Forward Information parameter is sent 7.2.3.1.2A.2 o 5 Carrier-based routeing supported 7.2.3.1.2B, 7.2.3.2.2B o 6 The Transit Network Selection parameter is sent 7.2.3.1.2B.1 c7221 7 The Carrier Selection Information parameter is sent 7.2.3.1.2B.2 c7221 8 The sending of 'cic' parameter supported 7.2.3.2.2B1 c7221 9 The sending of 'dai' parameter is supported 7.2.3.2.2B.2 c7221 o.3: It is optional to support exactly one of these items. c7221: IF 7.2.2/5 THEN o ELSE n/a ETSI ETSI TS 102 710-1 V3.1.1 (2011-05) 13 Table 6.2.3: Overlap capability Item Item description Reference Status Support 1 The 'In-dialogue Method' is supported 7.2.3.1.3A.2 o 2 The 'Multiple INVITE Method' is supported 7.2.3.1.3A.3 o 3 If the end of the address signalling is determined the SUT inserts the PSTN XML sendingCompleteIndication 7.2.3.2.1.4 c7231 c7231: IF 7.2.1/5 THEN o ELSE n/a Table 6.2.4: ISDN bearer capabilities Item Item description Reference Status Support 1 The SUT supports the interworking of a CLEARMODE codec in the received INVITE request and PSTN XML Bearer Capability element is present 7.2.3.1.1 o 2 The SUT supports the interworking of Transmission Medium Requirement 64 kbit/s received in the IAM 7.2.3.2.1 o |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 6.3 Simulation service capabilities | Table 6.3.1: Simulation service major capabilities Item Item description Reference Status Support 1 The SUT behaviour is related to supplementary services as defined in ITU-T Recommendations Q.730 [i.1] to Q.737 [i.8] when interworking with an IMS which does not use a Multimedia Telephony Application Server (MTAS) providing supplementary services according to 3GPP 7.4 o 2 the SUT behaviour is related to supplementary services as defined in ITU-T Recommendations Q.730 [i.1] to Q.737 [i.8] when interworking with an IMS which uses a Multimedia Telephony Application Server (MTAS) providing supplementary services according to 3GPP 7.5 o ETSI ETSI TS 102 710-1 V3.1.1 (2011-05) 14 Table 6.3.2: Simulation service interworking capabilities Item Item description Reference Status Support 1 The interworking of Calling line identification presentation/restriction (CLIP/CLIR) respectively Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) is supported 7.4.1, 7.5.1 o 2 Connected line presentation and restriction (COLP/COLR) respectively Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) is supported 7.4.2, 7.5.2 o 3 The interworking of Malicious call identification respectively Malicious Communication Identification (MCID) is supported 7.4.4, 7.5.9 o 4 The interworking of Subaddressing (SUB) is supported 7.4.5 o 5 The interworking of Call Forwarding Busy (CFB)/ Call Forwarding No Reply (CFNR)/Call Forwarding Unconditional (CFU)/Call Deflection (CD) respectively Communication Diversion (CDIV) is supported 7.4.6, 7.4.7, 7.5.4 o 6 The interworking of Explicit Call Transfer (ECT) respectively is supported 7.4.8, o 7 The interworking of Call Waiting (CW) is supported 7.4.9 o 8 The interworking of Call Waiting (CW) is supported 7.5.12 o 9 The interworking of Call Hold (HOLD) respectively Communication Hold (HOLD) is supported 7.4.10, 7.5.5 o 10 The interworking of Call Completion on busy subscriber (CCBS) is supported 7.4.11 o 11 The interworking of Completion of Calls on No Reply (CCNR) is supported 7.4.12 o 12 The interworking of Terminal Portability (TP) is supported 7.4.13 o 13 The interworking of Conference calling (CONF)/ Three-Party Service (3PTY) is supported 7.4.14 o 14 The interworking of Closed User Group (CUG) is supported 7.4.16 o 15 The interworking of Multi-Level Precedence and Pre- emption (MLPP) is supported 7.4.17 o 16 The interworking of Global Virtual Network Service (GVNS) is supported 7.4.18 o 17 The interworking of Reverse charging (REV) is supported 7.4.20 o 18 The interworking of User-to-User Signalling (UUS) is supported 7.4.21 o 19 The interworking of Anonymous Call rejection (ACR) is supported 7.4.23 o 20 The interworking Conference call (CONF) is supported 7.5.6 o 21 The interworking of Anonymous Communication Rejection (ACR) and Communication Barring (CB) is supported 7.5.7 o 22 The interworking of Message Waiting Indication (MWI) is supported 7.5.8 o 23 The interworking of Closed User Group (CUG) is supported 7.5.10 o 24 The interworking of CCBS/CCNR is supported 7.5.11 o ETSI ETSI TS 102 710-1 V3.1.1 (2011-05) 15 Table 6.3.3: OIP interworking capabilities Item Item description Reference Status Support 1 The SUT include a network provided E.164 Calling party number if no P-Asserted-Identity was received 7.5.1, 7.2.3.1.2.6 c7331 2 The SUT omits the Address signals of the Calling party number if no P-Asserted-Identity was received 7.5.1, 7.2.3.1.2.6 c7331 3 The SUT set the APRI of the Calling party number to 'Address not available' if no P-Asserted-Identity was received 7.5.1, 7.2.3.1.2.6 c7332 4 The SUT sets the APRI of the Calling party number to 'presentation restricted by network' instead of the 'presentation restricted' if no P-Asserted-Identity was received 7.5.1, 7.2.3.1.2.6 o 5 The SUT omits the additional calling party number parameter if the Calling party number has been omitted if no P-Asserted-Identity was received 7.5.1, 7.2.3.1.2.6 c7332 6 The SUT omits the additional calling party number parameter if the P-Asserted-Identity has been received 7.5.1, 7.2.3.1.2.6 o o.4: It is mandatory to support exactly one of these items. c7331 IF 7.3.3/1 THEN o.4 ELSE n/a c7332 IF 7.3.3/2 THEN o ELSE n/a Table 6.3.4: COLP interworking capabilities Item Item description Reference Status Support 1 The SUT invokes the COLP service by setting the "Connected Line Identity Request indicator" field of the "Optional forward call indicators" parameter in the sent IAM to "requested" 7.4.2.1.1 o Table 6.3.5: CDIV interworking capabilities Item Item description Reference Status Support 1 The SUT maps the escaped Reason header in the second last hi-targeted-uri into the Event indicator of the CPG national values 7.4.6.2.2, table 7.4.6.2.2.7 o 2 The SUT maps the Redirecting reason in the Call diversion information into the Reason header in the second last hi-targeted-to-uri in the History-Info header 7.4.6.3.3, table 7.4.6.3.3.3 table 7.4.6.3.3.4 table 7.4.6.3.3.5 o 3 The SUT maps the cause parameter in the last hi- targeted-uri into the Event indicator national values 7.5.4.2.1 table 7.5.4.2.1.7 o Table 6.3.6: HOLD interworking capabilities Item Item description Reference Status Support 1 The SUT allows to hold and retrieve a session in the early dialogue 7.4.10 o Table 6.3.7: REV interworking capabilities Item Item description Reference Status Support 1 The SUT discards the REV service invocation without affect the call 7.4.20 o.5 2 The SUT returns explicit rejection of the REV service invocation 7.4.20 o.5 o.5: It is optional to support exactly one of these items. ETSI ETSI TS 102 710-1 V3.1.1 (2011-05) 16 Table 6.3.8: User-to-user interworking capabilities Item Item description Reference Status Support 1 The MGCF supports the User-to-user indicator (the User-to-user indicator is recognized) 7.4.21.2, 7.4.21.3, 7.4.21.4 o Table 6.3.9: CONF interworking capabilities Item Item description Reference Status Support 1 The conference event package option is implemented 7.5.6.2 o Table 6.3.10: CUG interworking capabilities Item Item description Reference Status Support 1 The IMS network does not support the CUG supplementary service 7.5.6.2 o |
ebcc32db3e89186add7c8bf973fde240 | 102 710-1 | 6.4 Timers | Table 6.4.1: Timers Item Item description Reference Status Support Values [seconds] Allowed Supported 1 Ti/w1 7.2.3.3 m 4 to 6 (default 4) 2 Ti/w2 7.2.3.3 m 4 to 20 (default 4) 3 Ti/w3 7.2.3.3 m 4 to 6 (default 4) 4 TTIR1 7.2.3.3 o 0,1 to 2 (default 0,1) ETSI ETSI TS 102 710-1 V3.1.1 (2011-05) 17 History Document history V3.1.1 May 2011 Publication |
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 new MAP command. |
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. • For a non-specific reference, the latest version applies. • 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 02.32: "Digital cellular telecommunications system (Phase 2+); Immediate Service Termination (IST); Service description - Stage 1". |
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 Waiting, Call Transfer, Call Forwarding, Unstructured Supplementary Service Data (USSD)). |
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 Subscription Information ETSI ETSI TS 101 967 V7.0.1 (2001-10) 6 (GSM 03.35 version 7.0.1 Release 1998) |
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 the subscriber. Prior to the sending of the IST command, the Mobile Application Part (MAP) command "Cancel Location" should be sent to the VLR at which the subscriber is registered. This will ensure that the subscriber cannot re-commence service at that VLR after the IST command has been executed. See annex B of GSM 02.32. The compilation of the list of MSCs to which the IST command should be sent is outside the scope of the present document. However, if a PLMN operator wishes to implement IST using CAMEL, the list of MSCs to which the IST command should be sent for a subscriber is the list of MSCs with which the CAMEL server has a relationship for that subscriber. If this data is not available directly from the CAMEL server, it may be obtained using Fraud Information Gathering System (FIGS) or an Fraud Detection System (FDS) (if the HPLMN is using CAMEL for IST then it is likely that it will also be monitoring the subscriber’s activities using FIGS level 2 or 3, which use CAMEL). |
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 gsmSSF) controlling the call or forwarding leg. |
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 the GMSC in the response to a request for routeing information. If the subscriber is being monitored using FIGS, it will already be marked as a CAMEL subscriber. If the HPLMN wishes to mark a subscriber as a CAMEL subscriber when the subscriber is already registered in the VPLMN, it modifies the subscriber data in the VPLMN using the command Insert Subscriber Data. |
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 "control relationship" exists where there is at least one armed DP in the gsmSSF. This can be achieved if the DP O/T_Disconnect (which will trigger the sending of an Event_Report_BCSM to the gsmSCF) is set for the call. If the subscriber is being monitored using FIGS level 2 or 3, the subscriber will already be marked as a CAMEL subscriber and DP O/T_Disconnect will already have been set. If the subscriber is not being monitored using FIGS levels 2 or 3 then O/T_Disconnect is set with command Request_Report_BCSM_Event sent to the gsmSSF by the gsmSCF after the gsmSCF has received notification of a call attempt via the Initial_DP message received from the gsmSSF. ETSI ETSI TS 101 967 V7.0.1 (2001-10) 7 (GSM 03.35 version 7.0.1 Release 1998) Initial_DP notifies the gsmSCF of call attempts. If the gsmSCF wishes to be notified of the success or failure of a call attempt, and so not be keeping a register of "calls" that may not have commenced, DP O/T_Answer can be set to inform the gsmSCF when a call is answered by the calling party. If the non-reception of an Event_Report_BCSM indicating call answer is not sufficient indication to the HPLMN of the failure of a call attempt, DPs O_Route_Select_Failure, O/T_Busy, O/T_No_Answer, O/T_Abandon, O/T_Not_Reachable can be set to inform the gsmSCF explicitly if the call attempt fails. If the various failure DPs are not armed, the gsmSCF can still deduce that the call attempt has failed because the gsmSSF will terminate the relationship when the call fails by sending message Abort to the gsmSCF. All these DPs can be set via the Request_Report_BCSM_Event sent to the gsmSSF by the gsmSCF after receiving the InitialDP message. If all these DPs are set then the subscriber is in fact being monitored with the equivalent of FIGS level 2 monitoring. |
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 terminate the call. |
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 server for a CAMEL implementation of IST) is outside the scope of the present document. ETSI ETSI TS 101 967 V7.0.1 (2001-10) 8 (GSM 03.35 version 7.0.1 Release 1998) Annex A (informative): Status of Technical Specification GSM 03.35 Status of Technical Specification GSM 03.35 (IST stage 2) Date Version Comments No Phase 1 version April 1998 0.1.0 to SMG10 plenary, Lund, 6-9 April 1998 by the rapporteur April 1998 0.2.0 output SMG10-WPB, Lund, 6-9 April 1998 June 1998 0.3.0 Minor editorial changes made by rapporteur June 1998 1.0.0 specification to SMG#26 for information July 1998 2.0.0 specification to SMG#27 for approval October 1998 7.0.0 specification approved by SMG#27 October 2001 7.0.1 Editorial Text and figures: WinWord 6.0 Stylesheet: etsiw_70.dot Rapporteur: Tim Wright ETSI ETSI TS 101 967 V7.0.1 (2001-10) 9 (GSM 03.35 version 7.0.1 Release 1998) History Document history V7.0.1 October 2001 Publication |
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). A BSS ensures the coverage of n cells, where n can be 1 or more. The function of a BSS may be further subdivided into a control function, performed by one Base Station Controller (BSC) and a transceiving function, performed by "n" Base Transceiver Station equipments (BTS), one for each cell. However, the study of such a split is outside the scope of the 08.0x series of Technical Specifications, where the BSS will be considered as a whole. The BSS-MSC interface defined in the GSM 08 series of Technical Specifications is designed to support a wide range of possible architectures on both sides. Characteristics like the physical location of the transcoders/rate adaptation inside the BSS (either integrated into the transceivers or very near to the MSC) or the use of traffic or signalling concentration at either side are left to the operators choice. Annex A to the present document contains guidance information concerning the use of remote mobile switching units, which for the purposes of the present document are considered as part of the MSC. Direct connection between two BSSs is not supported by this interface. ETSI ETSI TS 101 642 V7.0.0 (1999-08) 6 (GSM 08.02 version 7.0.0 Release 1998) This interface is based on the use of 1 or more 2 048 kbit/s digital transmission system interfaces. Each 2 048 kbit/s interface provides 31*64 kbit/s channels which can be used for traffic or signalling as the operator requires. The signalling is layered, terminology similar to that in the OSI reference model is used in this series, however the layers referred to are not identical to the equivalently named layer in the OSI model. This interface is defined at the boundary of the MSC and has a per channel bit rate of 64 kbit/s, but the net radio path traffic channel is at a rate of less than 16 kbit/s. A transcoder or rate adapter function is thus needed for the rate conversion. The interface is designed such that the transcoding or rate adaptation function may be geographically situated at either the MSC site or the BSS site, however the transcoder is considered to be part of the BSS. The interface has been designed around the aims of GSM 08.01 allowing each component and the system as a whole to evolve. |
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. • 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.09: "Digital cellular telecommunications system (Phase 2+); Handover procedures". [3] GSM 03.10: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) connection types". [4] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions". [5] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [6] GSM 08.01: "Digital cellular telecommunications system (Phase 2+); Base Station System - Mobile services Switching Centre (BSS - MSC) interface; General aspects". [7] GSM 08.04: "Digital cellular telecommunications system (Phase 2+); Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; Layer 1 specification". [8] GSM 08.06: "Digital cellular telecommunications system (Phase 2+); Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [9] GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". [10] GSM 08.20: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [11] GSM 08.51: "Digital cellular telecommunications system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface; General aspects". ETSI ETSI TS 101 642 V7.0.0 (1999-08) 7 (GSM 08.02 version 7.0.0 Release 1998) [12] GSM 08.52: "Digital cellular telecommunications system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Interface principles". [13] GSM 08.54: "Digital cellular telecommunications system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 1 structure of physical circuits". [14] GSM 08.56: "Digital cellular telecommunications system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 2 specification". [15] GSM 08.58: "Digital cellular telecommunications system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification". [16] GSM 08.60: "Digital cellular telecommunications system (Phase 2+); Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels". [17] GSM 08.61: "Digital cellular telecommunications system (Phase 2+); In-band control of remote transcoders and rate adaptors for half rate traffic channels". [18] GSM 12.01: "Digital cellular telecommunications system (Phase 2+); Common aspects of GSM Network Management (NM)". |
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 indication X X Radio channel management Radio channel configuration management X frequency hopping management X idle channel observation X power control X TCH management channel allocation (choice) X link supervision X channel release X X (Invoked by MSC) BCCH/CCCH management scheduling of messages X DCCH management link supervision X channel release X X (Invoked DCCH allocation X by MSC Radio resource indication report status of idle channels X Channel coding decoding MSC defines on the basis of call type X call type Transcoding/rate adaptation X Interworking Function (data calls) X Measurements reported from MS X uplink X traffic X Handover internal (within one cell){if provided} X MSC informed internal (between cells) {if provided} X MSC informed external recognition radio reason X external recognition traffic reason X X decision X X execution X Mobility Management authentication X location updating X paging X DRX paging (scheduling) X Call control X User data encryption X Key and permitted algorithms from MSC Signalling element encryption X Key and permitted algorithms from MSC ETSI ETSI TS 101 642 V7.0.0 (1999-08) 9 (GSM 08.02 version 7.0.0 Release 1998) |
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 can be managed, according to the configuration, either by the MSC or by the BSS for a given route. The entity in charge of circuit allocation chooses the terrestrial circuit, whilst ensuring that the chosen circuit is able to support the type of connection needed. |
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 supported and will result in the concerned channels not being chosen, no information need flow across the interface in these cases. |
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 call. This connection mechanism is not further defined in these Technical Specifications. |
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 indications in an assignment message from the MSC. |
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 handover is required. ETSI ETSI TS 101 642 V7.0.0 (1999-08) 12 (GSM 08.02 version 7.0.0 Release 1998) |
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 to traffic reasons. |
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 cell. |
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 transmission plant for a particular administration, there is an economic benefit, for larger cells and certain network topologies, in having the transcoder positioned at the MSC site. However, for smaller cells there may actually be a cost penalty due to special multiplexing. When the transcoder is geographically sited at the MSC site, it shall still be considered part of the BSS, and as such is on the BSS side of the BSS-MSC interface. 4 Multiplexing of common and dedicated control channels Common and dedicated control channels will be used for the same call on the radio path. These control channels will be multiplexed onto one or more common signalling channel(s) between the BSS and MSC. This multiplexing function will reside at the BSS. It should be noted therefore that the data links across the air interface are terminated at the BSS. All scheduling of messages via the air interface is controlled by the base station, flow control is therefore required from BSS to MSC to prevent overload of the transmission buffers, this is further detailed in Technical Specifications GSM 08.08 and GSM 08.06. |
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 BSSMAP and DTAP messages is detailed in Technical Specification GSM 08.06. |
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 radio subsystem; iv) an appropriate channel coder being activated in the BSS; v) a rate adaptation function being activated in the BSS; vi) any echo control in the MSC being by-passed or disabled; vii) an appropriate network interworking function being invoked. ETSI ETSI TS 101 642 V7.0.0 (1999-08) 14 (GSM 08.02 version 7.0.0 Release 1998) The MSC to BSS interface will support all necessary signalling for this to be achieved. |
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 BSSAP DTAP BSS MAP Distribution Function BSS OMAP S C C P M T P PHYSICAL LAYER M T P S C C P S C C P M T P Distribution Function DTAP BSS MAP Operation and Maintenance information to PLMN O&M centre To other applications eg. call control BSS OMAP To other users of SCCP and MTP To air interface transmission equipment Terminology: DTAP - Direct Transfer Application Part BSSMAP - BSS Management Application Part BSS OMAP - BSS Operation and Maintenance Application Part SCCP - Signalling Connection and Control Part MTP - Message Transfer Part BSS - Base Station System MSC - Mobile services Switching Centre NOTE: X.25 can be used for transferring O and M information. Figure 1: Signalling protocol reference model ETSI ETSI TS 101 642 V7.0.0 (1999-08) 16 (GSM 08.02 version 7.0.0 Release 1998) Annex A (informative): Remote Mobile Switching Unit (RMSU) A.1 Introduction Between the MSC and some of the BSS sites served by this MSC , it may be advantageous to include a line concentrator, an RMSU. The main purpose of introducing this unit is to reduce the number of terrestrial circuits needed between BSS site and MSCs (signalling and traffic circuits). The benefits of introducing an RMSU will depend on: - relative costs of the transmission plant for the particular administrations; - the costs involved in operating the RMSU; - the complexity of the RMSU, i.e. if it allows interworking with the ISDN or the PSTN for mobile originated calls. In the GSM Technical Specifications the RMSU will be regarded as a remotely controlled part of the MSC, and therefore no detailed specification of the RMSU or the signalling functions needed between the RMSU and the MSC will be given. A.2 Functions provided by the RMSU Below is listed some examples of functions which may be provided by the RMSU: - setting up and clearing of circuits to the BSS and the MSC (remotely controlled by the MSC); - switching of the circuits between MSC and the various BSSs; - blocking and unblocking of circuits; - possibly interworking with the PSTN or ISDN for mobile originated calls, including information exchange with remote control from the MSC; - Operation and maintenance functions of the RMSU. A.3 General requirements In order to be able to establish a BSS configuration without using an RMSU, and then later on introducing this unit, the interface between the BSSs and the RMSU should have the same characteristics as the interface between a BSS and an MSC. The number of subscribers served by an RMSU will be large compared to the number of subscribers served by a single BSS. Therefore, if the RMSU or the signalling links between the RMSU and the MSC go down, this will have a serious impact on the mobile service in a large geographical area. The implementation of the RMSU and the signalling between the RMSU and the MSC therefore has to be made in such a way that the overall reliability requirements specified for the MSC are fulfilled. Some O and M facilities may be required in the RMSU, and the necessary signalling between the RMSU and the O and M functions has to be provided. ETSI ETSI TS 101 642 V7.0.0 (1999-08) 17 (GSM 08.02 version 7.0.0 Release 1998) Annex B (informative): Change Request History Change history SMG No. TDoc. No. CR. No. Section affected New version Subject/Comments SMG#07 4.1.1 ETSI Publication SMG#13 010 4.2.0 Definition of a circuit pool SMG#20 5.0.0 Release 1996 version SMG#21 140/97 A002 5.1.0 CR on GSM 08.02 on Circuit allocation by the BSS SMG#27 6.0.0 Release 1997 version SMG#29 7.0.0 Release 1998 version ETSI ETSI TS 101 642 V7.0.0 (1999-08) 18 (GSM 08.02 version 7.0.0 Release 1998) History Document history V7.0.0 August 1999 Publication ISBN 2-7437-3362-4 Dépôt légal : Août 1999 |
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 relevant guidance given in ISO/IEC 9646-7 [5] and ETS 300 406 [6]. The test notation used in the ATS is TTCN-3 (see ES 201 873-1 [7]). The following test specification and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Abstract Test Suite (ATS) part of the ATS. Annex B provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma for the PCRF part of the ATS. Annex C provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma for the PCEF part of the ATS. Annex D provides the PCTR Proforma for the PCRF part of the ATS. Annex E provides the PCTR Proforma for the PCEF part of the ATS. |
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 are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. |
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 Testing (INT); Diameter Conformance testing for Gx interface; Part 2: Test Suite Structure (TSS) and Test Purposes (TP)". ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 7 [3] ISO/IEC 9646-1: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 1: General concepts". [4] ISO/IEC 9646-6: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 6: Protocol profile test specification". [5] ISO/IEC 9646-7: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 7: Implementation Conformance Statements". [6] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [7] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". |
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 level, the lower layers of the test machine shall be totally conformant with the corresponding lower layers specifications to use the remote test method. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 8 |
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 PIXIT parameter "GTPsupport". GTPv1-U messages are exchanged at ports GTP1 and GTP2 (see figure 4). port:LLPCRF TS port:DIAMP PCRF port:PCRF SUT PCEF map(p_diameterComponent_pcrf:DIAMP, system: PCRF); map(p_diameterComponent_pcrf:LLPP, system: LLPCRF); port:LLPP Figure 3: Interconnection for PCEF role without IP interfaces system:LLPCRF TS gtp1 port:GTP port:DIAMP system:GTP1 system:GTP2 gtp2 port:GTP PCRF system:PCRF SUT PCEF map(p_gtpComponent1:GTP, system: GTP1); map(p_gtpComponent2:GTP, system: GTP2); map(p_diameterComponent_pcrf:DIAMP, system: PCRF); map(p_diameterComponent_pcrf:LLPP, system: LLPCRF); port:LLPP Figure 4: Interconnection for PCEF role with IP interfaces (GTP) ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 10 |
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 PCEF system:PCEF SUT PCRF map(p_diameterComponent_pcef:DIAMP, system: PCRF); map(p_diameterComponent_pcef:LLPP, system: LLPCRF); port:LLPP Figure 5: Interconnection for PCRF role system:LLIMS TS port:DIAMP PCEF system:PCEF_Gx SUT PCRF map(p_diameterComponent_pcef:DIAMP, system: PCRF_Gx); map(p_diameterComponent_pcef:LLPP, system: LLPCRF); map(p_diameterComponent_af:DIAMP, system: AF_Rx); map(p_diameterComponent_af:LLPP, system: LLPCRF); port:LLPP P-CSCF port:DIAMP port:LLPP system:LLIMS system:AF_Rx Figure 6: Interconnection for PCRF role with AF interface (Rx) ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 11 |
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 the implementation conventions. The naming conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the functional structure of the ATS. To define the ATS, the guidelines of the document ETS 300 406 [6] were considered. |
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 also behaves as a Diameter Client. IUT is a PCEF (example TC_PCEF_IPS_01) f_preamble_PCRF f_postamble_PCRF NOTE 2: The tester also behaves as a Diameter Server. |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.2 Naming conventions |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.