hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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
| |
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. • Prefixes and suffixes should be separated from the body of the identifier with an underscore ("_"): EXAMPLE 1: c_sixteen, t_wait_max. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 12 • Only module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. • The start of second and subsequent words in an identifier should be indicated by capitalizing the first character. Underscores should not be used for this purpose. EXAMPLE 2: f_authenticateUser. Table 1 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix, suffixes (if any) and capitalization. Table 1: TTCN-3 naming convention Language element Naming convention Prefix Suffix Example Notes Module Use upper-case initial letter DiameterGx_ none DiameterGx_Steps TSS grouping Use all upper-case letters none none TP_PCEFRole_IPS Message template Use lower-case initial letter m_ none m_authApplicationId Message template with wildcard or matching expression Use lower-case initial letters mw_ none mw_subscriptionId Port instance Use upper-case initial letter none none DiameterPort Constant Use lower-case initial letter c_ none c_maxRetransmission Function Use lower-case initial letter f_ none f_authentication() Altstep Use lower-case initial letter a_ none a_receive() Variable Use lower-case initial letter v_ none v_basicId PICS values Use all upper case letters PC_ _ none PC_PCRF_DATA_CON Note PIXIT values Use all upper case letters PX_ none PX_DIAMETER_IP_ADDR Note Parameterization Use lower-case initial letter p_ none p_macId Enumerated Value Use lower-case initial letter e_ none e_synCpk NOTE: In this case it is acceptable to use underscore as a word delimiter.
|
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 <scope> = group IPS Initial Provisioning Session MSI Modification of Session Information INV Invalid Behaviour ST Session Termination PCC PCC rules EMS Emergency services UMC Usage monitoring control IRS IMS Restoration Support MPS Multimedia Priority Support SDC Sponsored Data Connectivity RAU Reporting Accumulated Usage <number> = sequential number (01-99) NOTE: This naming scheme results into a one-to-one correspondence between the test purpose identifiers as defined in TS 101 606-2 [2] and the test case identifiers. The TP identifier of the test case TC_xxx_01 is TP_xxx_01. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 14 Annex A (normative): DIAMETER Gx Abstract Test Suite (ATS) This ATS has been produced using the Testing and Test Control Notation (TTCN-3) according to ES 201 873-1 [7]. A.1 The TTCN-3 Module The TTCN-3 library modules corresponding to the ATS are contained in archive ts10160603v010101p0.zip which accompanies the present document. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 15 Annex B (normative): DIAMETER Gx Partial PIXIT proforma for IUT PCRF Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the Partial PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed Partial PIXIT. The PIXIT Proforma is based on ISO/IEC 9646-6 [4]. Any additional information which may be needed can be found in this international standard document. B.1 Identification summary Table B.1 PIXIT Number: Test Laboratory Name: Date of Issue: Issued to: B.2 ATS summary Table B.2 Protocol Specification: TS 129 212 [1] Protocol to be tested: ATS Specification: TS 101 606-3 Abstract Test Method: TS 101 606-3 clause 4 B.3 Test laboratory Table B.3 Test Laboratory Identification: Test Laboratory Manager: Means of Testing: SAP Address: B.4 Client identification Table B.4 Client Identification: Client Test manager: Test Facilities required: ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 16 B.5 SUT Table B.5 Name: Version: SCS Number: Machine configuration: Operating System Identification: IUT Identification: PICS Reference for IUT: Limitations of the SUT: Environmental Conditions: B.6 Protocol layer information B.6.1 Protocol identification Table B.6 Name: TS 129 212 [1] Version: PICS References: B.6.2 Configuration Tables in this clause need to be filled by the IUT Manufacturer to specify how the IUT needs to be configured with IUT specific values or describe IUT specific procedures required for complete testing of the IUT. Table B.7: PIXIT for the Gx interface Gx PIXIT Summary 1 PX_DIAMETER_GX_ETS_IPADDR charstring, IP address of the test system 2 PX_DIAMETER_GX_SUT_IPADDR charstring, IP address of the system under test 3 PX_DIAMETER_GX_ETS_PORT charstring, Port number of the test system 4 PX_DIAMETER_GX_SUT_PORT charstring, Port number of the system under test 5 PX_SessionID UTF8String, Session-Id AVP (AVP Code 263) 6 PX_Logical_Access_ID octetstring, the logical Access ID in case of xDSL IP-CAN type 7 PX_Physical_Access_ID UTF8String, the physical Access ID in case of xDSL IP-CAN type 8 PX_OriginHost charstring, the Origin-Host AVP (AVP Code 264) 9 PX_OriginRealm charstring, the Origin-Realm AVP (AVP Code 296) 10 PX_DestinationHost charstring, the Destination-Host AVP (AVP Code 293) 11 PX_DestinationRealm charstring, the Destination-Realm AVP (AVP Code 283) 12 PX_UE_framedIpAddress octetstring the Framed-IP-Address AVP (AVP Code 8) 13 PX_UE_framedIp6Address octetstring, the Framed-IPv6-Prefix AVP (AVP Code 97) 14 PX_SUBSCRIPTION_ID_TYPE enumerated type, Subscription_Id_Ty_Type, avp_Data within Subscription_Id_Type_AVP 15 PX_SUBSCRIPTION_ID_DATA UTF8String, avp_Data within Subscription_Id_AVP ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 17 Gx PIXIT Summary 16 PX_IP_CAN_TYPE enumerated type, IP_CAN_Type, avp_Data within IP_CAN_Type_AVP 17 PX_RAT_TYPE enumerated type, RAT_Type, avp_Data within RAT_Type_AVP 18 PX_APN_AGGREGATE_MAX_BITRATE_UL_AVP_DATA UInt32, avp_Data within APN_Aggregate_Max_Bitrate_UL_AVP 19 PX_3GPP_MS_TIMEZONE_DATA octetstring, avp_Data within ThreeGPP_MS_TimeZone_DATA 20 PX_CALLED_STATION_ID_DATA UTF8String, avp_Data within Called_Station_Id_AVP 21 PX_PDN_CONNECTION_ID_DATA octetstring, avp_Data within PDN_Connection_ID_AVP 22 PX_BEARER_USAGE_DATA enumerated type, Bearer_Usage, avp_Data within Bearer_Usage_AVP 23 PX_ANCA_ipv4 The ANCA (Access-Network-Charging-Address) in IPv4Addr format 24 PX_ANCA_ipv6 The ANCA (Access-Network-Charging-Address) in type IPv6Addr format 25 PX_SGW_AGW_ipv4 The SGW_AGW address (3GPP-EPS and 3GPP2 accesses) in IPv4Addr format 26 PX_SGW_AGW_ipv6 The SGW_AGW address (3GPP-EPS and 3GPP2 accesses) in IPv6Addr format 27 PX_ACCESS_NETWORK_CHARGING_IDENTIFIER_VALUE octetstring, avp_Data within Access_Network_Charging_Identifier_Value_AVP 28 PX_ROUTING_RULE_IDENTIFIER_VALUE octetstring, avp_Data within Routing_Rule_Identifier_AVP 29 PX_NETWORK_REQUEST_SUPPORT enumerated type Network_Request_Support, avp_Data within Network_Request_Support_AVP is of enumerated type Network_Request_Support 30 PX_CHARGING_RULE_NAME_DATA octetstring, avp_Data within Charging_Rule_Name_AVP 31 PX_PCC_RULE_STATUS enumerated type, PCC_Rule_Status, avp_Data within PCC_Rule_Status_AVP 32 PX_PRECEDENCE_DATA UInt32, avp_Data within Precedence_AVP 33 PX_PACKET_FILTER_IDENTIFIER_DATA octetstring, avp_Data within Packet_Filter_Identifier_AVP 34 PX_RULE_FAILURE_CODE enumerated type, PCC_Rule_Status, avp_Data within Rule_Failure_Code_AVP 35 PX_OFFLINE_DATA enumerated type, PCC_Rule_Status, avp_Data within Offline_AVP 36 PX_MPS_IDENTIFIER octectstring, avp_Data within MPS_Identifier_AVP (parameter is part of AAR message) 37 PX_ONLINE_DATA enumerated type, PCC_Rule_Status, avp_Data within Online_AVP Table B.8: PIXIT for the Rx interface Rx PIXIT Summary 1 PX_DIAMETER_RX_ETS_IPADDR charstring, IP address of the test system 2 PX_DIAMETER_RX_SUT_IPADDR charstring, IP address of the system under test 3 PX_DIAMETER_RX_ETS_PORT charstring, Port number of the test system 4 PX_DIAMETER_RX_SUT_PORT charstring, Port number of the system under test 5 PX_ANCA_ipv4 charstring, The ANCA (Access-Network-Charging-Address) in IPv4Addr format 6 PX_ANCA_ipv6 charstring, The ANCA (Access-Network-Charging-Address) in type IPv6Addr format ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 18 Annex C (normative): DIAMETER Gx Partial PIXIT proforma for IUT PCEF Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the Partial PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed Partial PIXIT. The PIXIT Proforma is based on ISO/IEC 9646-6 [4]. Any additional information which may be needed can be found in this international standard document. C.1 Identification summary Table C.1 PIXIT Number: Test Laboratory Name: Date of Issue: Issued to: C.2 ATS summary Table C.2 Protocol Specification: TS 129 212 [1] (3GPP TS 29.212 version 10.5.0 Release 10) Protocol to be tested: ATS Specification: TS 101 606-2 [2] Abstract Test Method: TS 101 606-3, clause 4 C.3 Test laboratory Table C.3 Test Laboratory Identification: Test Laboratory Manager: Means of Testing: SAP Address: C.4 Client identification Table C.4 Client Identification: Client Test manager: Test Facilities required: ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 19 C.5 SUT Table C.5 Name: Version: SCS Number: Machine configuration: Operating System Identification: IUT Identification: PICS Reference for IUT: Limitations of the SUT: Environmental Conditions: C.6 Protocol layer information C.6.1 Protocol identification Table C.6 Name: TS 129 212 [1] (3GPP TS 29.212 version 10.5.0 Release 10) Version: PICS References: C.6.2 Configuration Tables in this clause need to be filled by the IUT Manufacturer to specify how the IUT needs to be configured with IUT specific values or describe IUT specific procedures required for complete testing of the IUT. Table C.7: PIXIT for the Gx interface Gx PIXIT Summary 1 PX_DIAMETER_GX_ETS_IPADDR charstring, IP address of the test system 2 PX_DIAMETER_GX_SUT_IPADDR charstring, IP address of the system under test 3 PX_DIAMETER_GX_ETS_PORT charstring, Port number of the test system 4 PX_DIAMETER_GX_SUT_PORT charstring, Port number of the system under test 5 PX_SessionID UTF8String, the Session-Id AVP (AVP Code 263) 6 PX_OriginHost charstring, the Origin-Host AVP (AVP Code 264) 7 PX_OriginRealm charstring, the Origin-Realm AVP (AVP Code 296) 8 PX_DestinationHost charstring, the Destination-Host AVP (AVP Code 293) 9 PX_DestinationRealm charstring, the Destination-Realm AVP (AVP Code 283) 10 PX_UE_framedIpAddress octetstring the Framed-IP-Address AVP (AVP Code 8) 11 PX_UE_framedIp6Address octetstring, the Framed-IPv6-Prefix AVP (AVP Code 97) 12 PX_BEARER_IDENTIFIER octetstring, avp_Data within Bearer_Identifier_AVP 13 PX_UNKNOWN_RATING_GROUP UInt32, avp_Data within Rating_Group_AVP 14 PX_CHARGING_RULE_NAME_DATA octetstring, avp_Data within Charging_Rule_Name_AVP 15 PX_CHARGING_RULE_NAME_DATA2 octetstring, avp_Data (2nd rule) within Charging_Rule_Name_AVP ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 20 Gx PIXIT Summary 16 PX_CHARGING_RULE_NAME_DATA3 octetstring, avp_Data (3rd rule) within Charging_Rule_Name_AVP 17 PX_CHARGING_RULE_NAME_DATA_NONEXIST octetstring, avp_Data within Charging_Rule_Name_AVP 18 PX_CHARGING_RULE_BASE_NAME_DATA octetstring, avp_Data within PX_CHARGING_RULE_BASE_NAME_DATA 19 PX_PACKET_FILTER_IDENTIFIER_DATA octetstring, avp_Data within Packet_Filter_Identifier_AVP 20 PX_MONITORING_KEY octectstring, avp_Data within MONITORING_KEY_AVP (parameter is part of RAR/CCR message) 21 PX_MONITORING_KEY2 octectstring, avp_Data within MONITORING_KEY_AVP (parameter is part of RAR/CCR message) 22 PX_REVALIDATION_TIME octectstring, avp_Data within Revalidation_Time_AVP (parameter is part of RAR message) 23 PX_ACTIVATION_TIME octectstring, avp_Data within Rule_Activation_Time_AVP (parameter is part of Charging_Rule_Install_AVP) 24 PX_DEACTIVATION_TIME octectstring, avp_Data within Rule_DeActivation_Time_AVP (parameter is part of Charging_Rule_Install_AVP) 25 PX_EMERGENCY_APN UTF8String, avp_Data within Called_Station_Id_AVP (parameter is part of Called_Station_Id_AVP) 26 PX_GTPsupport Boolean indicator, TRUE if GTP interface is accessible to triggrt Diameter events ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 21 Annex D (normative): DIAMETER Gx PCTR Proforma for IUT PCRF Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PCTR proforma in this annex so that it can be used for its intended purposes and may further publish the completed PCTR. The PCTR proforma is based on ISO/IEC 9646-6 [4]. Any additional information which may be needed can be found in this International standard document. D.1 Identification summary D.1.1 Protocol conformance test report Table D.1 PCTR Number: PCTR Date: Corresponding SCTR Number: Corresponding SCTR Date: Test Laboratory Identification: Test Laboratory Manager: Signature: D.1.2 IUT identification Table D.2 Name: Version: Protocol specification: PICS: Previous PCTR if any: D.1.3 Testing environment Table D.3 PIXIT Number: ATS Specification: TS 101 606-3 Abstract Test Method: TS 101 606-3, clause 4 Means of Testing identification: Date of testing: Conformance Log reference(s): Retention Date for Log reference(s): ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 22 D.1.4 Limits and reservation Additional information relevant to the technical contents or further use of the test report, or the rights and obligations of the test laboratory and the client, may be given here. Such information may include restriction on the publication of the report. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... D.1.5 Comments Additional comments may be given by either the client or the test laboratory on any of the contents of the PCTR, for example, to note disagreement between the two parties. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... D.2 IUT Conformance status This IUT has or has not been shown by conformance assessment to be non-conforming to the specified protocol specification. Strike the appropriate words in this sentence. If the PICS for this IUT is consistent with the static conformance requirements (as specified in clause C.3 in the present document) and there are no "FAIL" verdicts to be recorded (in clause C.6 in the present document) strike the words "has or", otherwise strike the words "or has not". D.3 Static conformance summary The PICS for this IUT is or is not consistent with the static conformance requirements in the specified protocol. Strike the appropriate words in this sentence. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 23 D.4 Dynamic conformance summary The test campaign did or did not reveal errors in the IUT. Strike the appropriate words in this sentence. If there are no "FAIL" verdicts to be recorded (in clause C.6 of the present document) strike the words "did or" otherwise strike the words "or did not". Summary of the results of groups of test: ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... D.5 Static conformance review report If clause C.3 indicates non-conformance, this clause itemises the mismatches between the PICS and the static conformance requirements of the specified protocol specification. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 24 D.6 Test campaign report Table D.4: PCRF test cases ATS Reference Selected? Run? Verdict Observations (Reference to any observations made in clause D.7) TC_PCRF_IPS_01 Yes/No Yes/No TC_PCRF_IPS_02 Yes/No Yes/No TC_PCRF_IPS_03 Yes/No Yes/No TC_PCRF_IPS_04 Yes/No Yes/No TC_PCRF_IPS_05 Yes/No Yes/No TC_PCRF_IPS_06 Yes/No Yes/No TC_PCRF_MSI_01 Yes/No Yes/No TC_PCRF_MSI_02 Yes/No Yes/No TC_PCRF_MSI_03 Yes/No Yes/No TC_PCRF_MSI_04 Yes/No Yes/No TC_PCRF_MSI_05 Yes/No Yes/No TC_PCRF_MSI_06 Yes/No Yes/No TC_PCRF_INV_01 Yes/No Yes/No TC_PCRF_INV_02 Yes/No Yes/No TC_PCRF_ST_01 Yes/No Yes/No TC_PCRF_ST_02 Yes/No Yes/No TC_PCRF_ST_03 Yes/No Yes/No TC_PCRF_PCC_01 Yes/No Yes/No TC_PCRF_PCC_02 Yes/No Yes/No TC_PCRF_PCC_03 Yes/No Yes/No TC_PCRF_PCC_04 Yes/No Yes/No TC_PCRF_PCC_05 Yes/No Yes/No TC_PCRF_PCC_06 Yes/No Yes/No TC_PCRF_PCC_07 Yes/No Yes/No TC_PCRF_PCC_08 Yes/No Yes/No TC_PCRF_PCC_09 Yes/No Yes/No TC_PCRF_EMS_01 Yes/No Yes/No TC_PCRF_UMC_01 Yes/No Yes/No TC_PCRF_IRS_01 Yes/No Yes/No TC_PCRF_IRS_02 Yes/No Yes/No TC_PCRF_MPS_01 Yes/No Yes/No TC_PCRF_MPS_02 Yes/No Yes/No TC_PCRF_SDC_01 Yes/No Yes/No TC_PCRF_SDC_02 Yes/No Yes/No D.7 Observations Additional information relevant to the technical content of the PCTR is given here. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 25 Annex E (normative): DIAMETER Gx PCTR Proforma for IUT PCEF Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PCTR proforma in this annex so that it can be used for its intended purposes and may further publish the completed PCTR. The PCTR proforma is based on ISO/IEC 9646-6 [4]. Any additional information which may be needed can be found in this International standard document. E.1 Identification summary E.1.1 Protocol conformance test report Table E.1 PCTR Number: PCTR Date: Corresponding SCTR Number: Corresponding SCTR Date: Test Laboratory Identification: Test Laboratory Manager: Signature: E.1.2 IUT identification Table E.2 Name: Version: Protocol specification: PICS: Previous PCTR if any: E.1.3 Testing environment Table E.3 PIXIT Number: ATS Specification: TS 101 606-3 Abstract Test Method: TS 101 606-3, clause 4 Means of Testing identification: Date of testing: Conformance Log reference(s): Retention Date for Log reference(s): ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 26 E.1.4 Limits and reservation Additional information relevant to the technical contents or further use of the test report, or the rights and obligations of the test laboratory and the client, may be given here. Such information may include restriction on the publication of the report. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... E.1.5 Comments Additional comments may be given by either the client or the test laboratory on any of the contents of the PCTR, for example, to note disagreement between the two parties. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... E.2 IUT Conformance status This IUT has or has not been shown by conformance assessment to be non-conforming to the specified protocol specification. Strike the appropriate words in this sentence. If the PICS for this IUT is consistent with the static conformance requirements (as specified in clause C.3 in the present document) and there are no "FAIL" verdicts to be recorded (in clause C.6 in the present document) strike the words "has or", otherwise strike the words "or has not". E.3 Static conformance summary The PICS for this IUT is or is not consistent with the static conformance requirements in the specified protocol. Strike the appropriate words in this sentence. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 27 E.4 Dynamic conformance summary The test campaign did or did not reveal errors in the IUT. Strike the appropriate words in this sentence. If there are no "FAIL" verdicts to be recorded (in clause C.6 of the present document) strike the words "did or" otherwise strike the words "or did not". Summary of the results of groups of test: ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... E.5 Static conformance review report If clause C.3 indicates non-conformance, this clause itemises the mismatches between the PICS and the static conformance requirements of the specified protocol specification. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 28 E.6 Test campaign report Table E.4: PCEF test cases ATS Reference Selected? Run? Verdict Observations (Reference to any observations made in clause D.7) TC_PCEF_IPS_01 Yes/No Yes/No TC_PCEF_IPS_02 Yes/No Yes/No TC_PCEF_IPS_03 Yes/No Yes/No TC_PCEF_IPS_04 Yes/No Yes/No TC_PCEF_IPS_05 Yes/No Yes/No TC_PCEF_IPS_06 Yes/No Yes/No TC_PCEF_MSI_01 Yes/No Yes/No TC_PCEF_MSI_02 Yes/No Yes/No TC_PCEF_MSI_03 Yes/No Yes/No TC_PCEF_MSI_04 Yes/No Yes/No TC_PCEF_MSI_05 Yes/No Yes/No TC_PCEF_ST_01 Yes/No Yes/No TC_PCEF_ST_02 Yes/No Yes/No TC_PCEF_PCC_01 Yes/No Yes/No TC_PCEF_PCC_02 Yes/No Yes/No TC_PCEF_PCC_03 Yes/No Yes/No TC_PCEF_PCC_04 Yes/No Yes/No TC_PCEF_PCC_05 Yes/No Yes/No TC_PCEF_PCC_06 Yes/No Yes/No TC_PCEF_PCC_07 Yes/No Yes/No TC_PCEF_PCC_08 Yes/No Yes/No TC_PCEF_PCC_09 Yes/No Yes/No TC_PCEF_PCC_10 Yes/No Yes/No TC_PCEF_PCC_11 Yes/No Yes/No TC_PCEF_PCC_12 Yes/No Yes/No TC_PCEF_PCC_13 Yes/No Yes/No TC_PCEF_PCC_14 Yes/No Yes/No TC_PCEF_PCC_15 Yes/No Yes/No TC_PCEF_PCC_16 Yes/No Yes/No TC_PCEF_PCC_17 Yes/No Yes/No TC_PCEF_PCC_18 Yes/No Yes/No TC_PCEF_PCC_19 Yes/No Yes/No TC_PCEF_PCC_20 Yes/No Yes/No TC_PCEF_EMS_01 Yes/No Yes/No TC_PCEF_EMS_02 Yes/No Yes/No TC_PCEF_UMC_01 Yes/No Yes/No TC_PCEF_RAU_01 Yes/No Yes/No TC_PCEF_RAU_02 Yes/No Yes/No TC_PCEF_RAU_03 Yes/No Yes/No TC_PCEF_RAU_04 Yes/No Yes/No TC_PCEF_RAU_05 Yes/No Yes/No TC_PCEF_RAU_06 Yes/No Yes/No TC_PCEF_RAU_07 Yes/No Yes/No TC_PCEF_IRS_01 Yes/No Yes/No TC_PCEF_IRS_02 Yes/No Yes/No ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 29 E.7 Observations Additional information relevant to the technical content of the PCTR is given here. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 30 History Document history V1.1.1 September 2012 Publication
|
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 406 [5].
|
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 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.
|
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); Diameter Conformance testing for Gx interface; Part 1: Protocol Implementation Conformance Statement (PICS)". [3] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [4] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [5] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [6] IETF RFC 3588: "Diameter Base Protocol". [7] ETSI TS 129 213: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping (3GPP TS 29.213 version 10.3.0 Release 10)". [8] ETSI TS 129 214: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 version 10.5.0 Release 10)".
|
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 ISO/IEC 9646-1 [3].
|
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)
| |
97ecb7ef16158b2b662fc69af5cd18a7
|
101 606-2
|
5.1 Test Suite Structure
| |
97ecb7ef16158b2b662fc69af5cd18a7
|
101 606-2
|
5.1.1 TP naming convention
|
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 7 Table 1: TP identifier naming convention scheme Identifier: <TP>_<iut>_<scope>_<nn> <tp> = Test Purpose: fixed to "TP" <iut> = type of IUT: PCRF or PCEF <scope> = group IPS Initial Provisioning Session MSI Modification of Session Information INV Invalid Behaviour ST Session Termination PCC PCC rules EMS Emergency services UMC Usage monitoring control IRS IMS Restoration Support MPS Multimedia Priority Support SDC Sponsored Data Connectivity RAU Reporting Accumulated Usage <nn> = sequential number (01 to 99)
|
97ecb7ef16158b2b662fc69af5cd18a7
|
101 606-2
|
5.1.2 Test strategy
|
As the base standard TS 129 212 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 101 606-1 [2].
|
97ecb7ef16158b2b662fc69af5cd18a7
|
101 606-2
|
5.1.3 TP structure
|
Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPs more readable and checkable. A particular structure has been used which is illustrated in table 2. This table should be read in conjunction with any TP, i.e. please use a TP as an example to facilitate the full comprehension of table 2. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 8 Table 2: Structure of a single TP TP part Text Example Header <Identifier> see table 1 <clause number in base TS 129 212 [1] > clause 4.4.1 <PICS reference> A.2/3 Summary Short free text description of the test objective Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to IP-CAN session establishment. Initial condition (optional) Free text description of the condition that the IUT has reached before the test purpose applies. The IUT has received AF provisions information about the AF signalling flows between UE and AF. Start point Ensure that the IUT in the <state> see RFC 3588 [6] clause 5.6 Open state and/or further actions before stimulus if the action is sending/receiving see below for message structure having sent an AA-Request Stimulus <trigger>, see below for message structure on receipt of a Capabilities-Exchange- Request (see note 2) or <goal> to require PCC supervision ... Reaction <action>. sends, saves, does, etc. if the action is sending see below for message structure <next action>, etc. Message structure <message type> Capabilities-Exchange-Answer, etc. (see note 2) a) containing a(n) <avp name> AVP b) indicating <coding of the field> and back to a) or b) (see note 3) Vendor-Id, etc. NOTE 1: Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from one TP to the next. NOTE 2: All messages shall be considered as "valid and compatible" unless otherwise specified in the test purpose. This includes the presence of all mandatory AVPs as specified in RFC 3588 [6] and in TS 129 212 [1], clause 5. NOTE 3: An AVP can be embedded into another AVP. This is expressed by indentations, e.g. if Message1 contains AVP1 and AVP2 where AVP1 has AVP3 embedded this will be expressed like this: sends/receives Message 1 containing AVP1 containing AVP3 indicating ... containing AVP2 indicating ...
|
97ecb7ef16158b2b662fc69af5cd18a7
|
101 606-2
|
5.2 Test Purposes
|
All PICS items referred to in this clause are as specified in TS 101 606-1 [2] unless indicated otherwise by another numbered reference. PICS items are only meant for test selection, therefore only PICS items with status optional or conditional are explicitly mentioned. Call flow information for described test purposes is specified in TS 129 213 [7].
|
97ecb7ef16158b2b662fc69af5cd18a7
|
101 606-2
|
5.2.1 PCRF Role
|
Test Selection: IUT takes the role of the PCRF; PICS A.2.1 ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 9
|
97ecb7ef16158b2b662fc69af5cd18a7
|
101 606-2
|
5.2.1.1 Session request
|
TP_PCRF_IPS_01 Standards Reference: 4.5.1 (item 1), 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to IP-CAN session establishment. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Subscription-Id AVP containing the user identification containing an IP-CAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio access technology containing a Framed-IP-Address AVP indicating the full IP address of the UE, sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6- Address-Prefix AVP. TP_PCRF_IPS_02 Standards Reference: 4.5.1 ¶1, 4.3a.4.1 ¶3, 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory and optional AVPs in a CC-Request received due to IP-CAN session establishment. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Subscription-Id AVP containing the user identification containing an IPCAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio access technology containing a Framed-IP-Address AVP containing the Framed-IP-Address containing a Called-Station-ID AVP containing the PDN information containing a PDN Connection-ID AVP containing the PDN connection identifier containing a 3GPP-MS-TimeZone AVP containing the UE time zone information containing an Access-Network-Charging-Identifier-Gx AVPs containing the Access-Network-Charging-Address containing a Network-Request-Support AVP containing an indicator for support of network-initiated bearer request procedures containing a QoS-Information AVP containing an APN-Aggregate-Max-Bitrate-DL/UL AVPs containing the APN-AMBR containing a Bearer-Usage AVP containing an indicator for default bearer request containing a Routing-Rule-Install AVP containing one or more Routing-Rule-Definition AVPs containing Routing-Filter AVP, sends a CC-Answer containing PCC rules. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6-Address- Prefix AVP. The Routing-Rule-Install AVP is configured as for installation of IP flow mobility routing rule. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 10 TP_PCRF_IPS_03 Standards Reference: 4.5.10 ¶2 and 3 PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to an IP-CAN session establishment with bearer control mode selection. Test purpose: Ensure that the IUT, on receipt of a CC-Request containing all mandatory AVPs and containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Network-Request-Support AVP, sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS containing a Bearer-Control-Mode AVP. Comments: TP_PCRF_IPS_04 Standards Reference: 4.5.1 (item 1, 2nd paragraph) PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to an IP-CAN session establishment that supports multiple IP-CAN bearers. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Default_EPS_Bearer_QoS AVP containing the QoS_Class_Identifier AVP containing the Allocation_Retention_Priority AVP sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: Usage of Default_EPS_Bearer_QoS_AVP is optional. TP_PCRF_IPS_05 Standards Reference: 4.5.1 (item 1, 3rd paragraph) PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to 3GPP-EPS and 3GPP2 accesses. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a AN-GW-Address AVP containing the IPv4 or IPv6 addresses of SGW/AGW sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: TP_PCRF_IPS_06 Standards Reference: 4.5.1 (item 1, 4th paragraph) PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to xDSL IP-CAN Type. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Subscription-Id AVP containing a Logical-Access-ID AVP containing a Physical-Access-ID AVP sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 11
|
97ecb7ef16158b2b662fc69af5cd18a7
|
101 606-2
|
5.2.1.2 Session modification
|
TP_PCRF_MSI_01 Standards Reference: 4.5.1 ¶2, 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to IP-CAN session modification. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing previously provisioned PCC rule(s) and their status containing an Event-Trigger AVP containing the reason for the IP-CAN session modification, sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: TP_PCRF_MSI_02 Standards Reference: 4.5.1 ¶2, 4.3a.4.1 ¶3, 4.5.2(1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory and optional AVPs in a CC-Request received due to IP-CAN session modification. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing an Access-Network-Charging-Address AVP containing an Access-Network-Charging-Identifier-Gx AVP containing a Charging-Rule-Report AVP containing previously provisioned PCC rule(s) and their status containing an Event-Trigger AVP containing the reason for the IP-CAN session modification containing a Routing-Rule-Install AVP containing one or more Routing-Rule-Definition AVPs containing a Routing-Filter AVP, sends a CC-Answer containing PCC rules. Comments: The Routing-Rule-Install AVP is configured as for installation of IP flow mobility routing rule. TP_PCRF_MSI_03 Standards Reference: 4.5.1 (item 2, 2nd dashed list, 1st dash), 4.5.2 1st dashed list (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due a UE request for allocation of new resources. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing an Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Packet-Filter-Operation AVP indicating ADDITION containing a Packet-Filter-Information AVPs containing a Precedence AVP containing a Packet-Filter-Content AVP containing a QoS-Information AVP, sends a CC-Answer containing PCC rules. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 12 TP_PCRF_MSI_04 Standards Reference: 4.5.1 (item 2, 2nd dashed list, 2nd dash), 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due a UE request for modification of existing resources. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing an Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Packet-Filter-Operation AVP indicating MODIFICATION containing a Packet-Filter-Information AVPs containing a Packet-Filter-Identifier AVP containing a packet filter identifier, sends a CC-Answer containing PCC rules. Comments: TP_PCRF_MSI_05 Standards Reference: 4.5.1 (item 2, 2nd dashed list, 3rd dash), 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due a UE request for deletion of resources. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Packet-Filter-Operation AVP indicating DELETION containing a Packet-Filter-Information AVPs containing a Packet-Filter-Identifier AVP, sends a CC-Answer containing PCC rules. Comments: TP_PCRF_MSI_06 Standards Reference: 4.5.10 ¶2 and 3 PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to IP-CAN session modification with bearer control mode selection. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing all mandatory AVPs and containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Network-Request-Support AVP, sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS containing a Bearer-Control-Mode AVP. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 13
|
97ecb7ef16158b2b662fc69af5cd18a7
|
101 606-2
|
5.2.1.3 Invalid behaviour
|
TP_PCRF_INV_01 Standards Reference: 4.5.1 (last paragraph in clause), 4.5.12 ¶1 PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to the failure of installation/activation of PCC rules. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing ( a Charging-Rule-Name AVP indicating failed PCC rule or a Charging-Rule-Base-Name AVP indicating failed PCC rule ) containing a PCC-Rule-Status AVP containing a Rule-Failure-Code AVP, sends a CC-Answer containing an Experimental-Result AVP indicating DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED. Comments: TP_PCRF_INV_02 Standards Reference: 4.5.1, 4.5.15.2.1 ¶2 and 3 PICS item: Summary: Verify that the IUT can reject a request for PCC rules for an emergency service. Test purpose: Ensure that the IUT, on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing an IP-CAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio access technology containing a Framed-IP-Address AVP indicating the full IP address of the UE containing a Called-Station-Id AVP indicating the Emergency APN containing a Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Subscription-Id AVP indicating IMSI, sends a CC-Answer containing an Experimental-Result AVP indicating DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6- Address-Prefix AVP. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 14
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.