hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 5.2.2 Test case identifiers | The test case names are built up according to the following scheme: "<TC>"_"<Group index>"_"<TC number>" where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in Table 1 (which uniquely identifies the path of groups/subgroups); c) <TC number> is a running 3-digit deci... |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 5.3 ATS specification framework | |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 5.3.1 ATS Library | For this ATS the TTCN-3 library modules are basically organized as: 1) AtsCommon modules. 2) LibIms modules. 3) LibSip modules (RFC 3261 [4]). 4) LibCommon modules (taken from an improved version of TS 102 351 [8]). NOTE: Due to the common LibSip and LibIms library approach with some other parallel running projects the... |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 5.3.2 Use of TTCN-3 | For the purposes of the present document, the description of the use of TTCN-3 described in clause 5.3.2 of TS 102 790-3 [3] applies. ETSI ETSI TS 186 010-3 V3.1.1 (2012-01) 10 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document,... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 1 Scope | The present document specifies the test suite structure and test purposes of the Subaddressing (SUB) service, based on IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3. Within the Next Generation Network (NGN) the stage 3 description is specif... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 283 003: "Telecommunications and Internet con... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] IETF RFC 3966 (2004): "The tel URI for Telephone... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 3 Definitions and abbreviations | |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 181 002 [3] and RFC 3261 [4] apply. |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement HOLD communication HOLD IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Service Data Network NGN Next Generation Network PSTN Public Switched Telephone Network SDP Session Description Protocol SIP Session I... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 4 Test Suite Structure (TSS) | SUB originating_UE SUB_U01_xxx originating_P-CSCF SUB_N01_xxx destination_P-CSCF SUB_N02_xxx destination_UE SUB_U02_xxx ISUP-SIP SS SUB TP607xxx SIP-ISUP SS SUB TP508xxx ETSI ETSI TS 186 012-2 V1.0.0 (2008-06) 7 |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5 Test Purposes (TP) | |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.1 Introduction | For each test requirement a TP is defined. |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.1.1 TP naming convention | TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 1). Table 1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = s... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.1.2 Test strategy | As the base standard ES 283 003 [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 186 012-1 [2]. The criteria applied include the following: • whether or not a test case can be built from the TP is not considered. |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.2 Test Purposes for Subaddressing (SUB) | |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.2.1 Actions at the originating UA | TSS SUB/originating_UE TP SUB_U01_001 SUB reference [5] clause 4.5.2 Selection expression PICS 1/1 Test purpose UE sends a subaddress in the From header in the initial INVITE Ensure that the originating user equipment is able to send an ISDN calling party subaddress in the From header of the INVITE Preconditions: SIP h... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.2.2 Actions at the originating P-CSCF | TSS SUB/originating_P-CSCF TP SUB_N01_001 SUB reference [5] clause 4.5.2 Selection expression PICS 1/2 Test purpose Ensure that the originating P-CSCF in able to transfer an ISDN subaddress in the From header and To header of the received INVITE into the P-Asserted-Identity and Request-URI Preconditions: SIP header val... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.2.3 Actions at the destination P-CSCF | TSS SUB/destination_P-CSCF TP SUB_N02_001 SUB reference [5] clause 4.5.2 Selection expression PICS 1/2 Test purpose Ensure that the terminating P-CSCF is able to pass an ISDN subaddress in the P-Asserted-Identity header and Request-URI header of the INVITE Preconditions: SIP header values: INVITE: P-Asserted-Identity: ... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.2.4 Actions at the destination UA | TSS SUB/destination_UE TP SUB_U02_001 SUB reference [5] clause 4.5.2 Selection expression PICS 1/1 Test purpose Ensure that the terminating user equipment is able to send an ISDN connected subaddress in the From header of the UPDATE Preconditions: Originating user is provided with TIP SIP header values: INVITE: support... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.3 Test purposes for the ISUP/SIP Interworking | |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.3.1 Outgoing Call Interworking from ISUP to SIP at O-MGCF | TP607001 SUB Reference [5]: 4.7.4.5.2 Selection criteria: PICS 1/4 TSS reference: ISUP-SIP/SS/SUB/ Preconditions: Test purpose: The calling party subaddress is mapped in the isub parameter of the From header Ensure that the calling party subaddress in the ATP parameter of the received IAM is interworked in the isub par... |
560084848a2ed6b1ea0dc96661573a92 | 186 012-2 | 5.3.2 Incoming Call Interworking from SIP to ISUP at I-MGCF | TP508001 SUB Reference [5]: 4.7.4.5.1 Selection criteria: PICS 1/4 TSS reference: SIP-ISUP/SS/SUB/ Preconditions: Test purpose: The isub parameter of the From header in an INVITE is mapped in the calling party subaddress in the IAM Ensure that the isub parameter in the From header of the received INVITE in interworked ... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 1 Scope | The present document is for an initial release of an IMS/PES performance benchmark. The same tests can be used also for legacy PSTN/ISDN networks or for inter-working tests between PSTN/ISDN emulation subsystem and legacy PSTN and ISDN. The metrics measured and reported are for performance of this subsystem under a com... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 186 025-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark Part 1: Core Concepts". [2] ETSI TS 186 025-2 (V2.2.1): "Telecommunicatio... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-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. [i.1] ITU-T Recommendation T.30 (2005): "Procedures for document facsimile transmission in the general switched telephone network". [i.2] ITU-T Recommendati... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 3 Definitions and abbreviations | |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Reference load A: intended to represent the normal upper mean level of activity which Administrations would wish to provide for on customer lines and inter-exchange activities Reference load B: intended to represent an increased level ... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: BA ISDN Basic Access BC Bearer Capability BHCA Busy Hour Call Attempts CAPS Call Attempts Per Second Erl Erlang IMS IP Multimedia Subsystem ISDN Integrated Services Digital Network ISUP ISDN User Part MGC Media Gate way Controller MGW Media Ga... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4 Initial benchmark traffic set and traffic-time profile | This clause defines the load profiles to simulate ISDN - non-ISDN environments. The data used in this traffic -time profile are based on profiles from Austria and Germany. ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 7 |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1 Initial benchmark traffic-time profile | Following assumptions are valid for the calculations: The required call processing capacity depends on the number of calls offered to the exchange. The basic formula to calculate the required BHCA is: BHCA = A × 3 600 / tm A = traffic for Reference load A [i.4] tm = mean holding time Access Types Traffic per subscriber... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1.1 MSAN 500 PSTN users | • Local exchange with 500 analog subscribers • Originating BHCA • A = number of subscribers × originating traffic per subscriber = 500 × 0,02 = 10 Erl • tm = mean holding time for originating traffic = 100 s • BHCA = 360 • Load A = 0,1 CAPS Table 1: MGW Traffic Load for 500 POTS subscriber Type of Call Traffic mix Traf... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1.2 MSAN 500 POTS/ISDN mixed users | • 100 % Voice Traffic • 333 POTS Lines • 166 ISDN Lines ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 9 POTS: - Local exchange with 333 analog subscribers - Originating BHCA - A = number of subscribers × originating traffic per subscriber = 333 × 0,02 = 6,66 Erl - tm = mean holding time for originating traffic = 100 s - BHCA... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1.3 MSAN 500 POTS/ISDN mixed users with data traffic | • 90 % Voice Traffic • 9 % Fax /Modem Traffic • 1 % Data ISDN Traffic • 333 POTS Lines • 166 ISDN Lines POTS: Voice - Local exchange with 300 analog subscribers - Originating BHCA - A = number of subscribers × originating traffic per subscriber = 300 × 0,02 = 6 Erl - tm = mean holding time for originating traffic = 100... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1.4 MSAN with 500 ISDN subscribers (2 lines) | • 100 % Voice Traffic • A = number of subscribers × originating traffic per ISDN subscriber (2 lines)= 500 × 0,1 = 50 Erl • tm = mean holding time for originating traffic = 100 s • BHCA = 1 800 BHCA • Load A = 0,5 CAPS Type of Call Traffic mix Traffic (Erl) Cps Intra-MGW 25 % 25 0,125 Inter-MGW 50 % 50 0,25 Inter-domai... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1.5 MSAN with 1 000 analog subscribers | • 100 % Voice Traffic • A = number of subscribers × originating traffic per subscriber = 1 000 × 0,02 = 20 Erl • tm = mean holding time for originating traffic = 100 s • BHCA = 20 × 3 600 / 100 = 720 BHCA • Load A = 0,2 CAPS Type of Call Traffic mix Traffic (Erl) Cps Intra-MGW 25 % 5 0,05 Inter-MGW 50 % 10 0,1 Inter-do... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1.6 MSAN / TRUNKING MGW with 16 PRA | • 100 % Voice Traffic • A = number of subscribers × originating traffic per subscriber = 480 × 0,5 = 240 Erl • BHCA = 480 × 18 = 8 640 • Load A = 480 x 0,005= 2,4 CAPS |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1.7 MSAN/TRUNKING MGW with 16 PRA mixed users with data traffic | • 90 % Voice Traffic • 10 % Fax /Modem Traffic ISDN PRA: Voice - A = number of channels × originating traffic per ISDN PRA channel = 432 × 0,5 = 216 Erl - BHCA = 432 x 18 = 7 776 ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 12 - Load A = 432 x 0,005= 2,16 CAPS ISDN PRA VBD Data - Local exchange with 48 analog subscribers (1... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1.8 Load A = 0,2 CAPS 4.1.8 MSAN/TRUNKING MGW with 100 PRA | • 100 % Voice Traffic • A = number of channels × originating traffic per ISDN PRA channel = 3 000 × 0,5 = 1 500 Erl • BHCA = 3 000 × 18 = 54 000 • Load A = 3 000 x 0,005= 15 CAPS |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.1.9 MSAN/TRUNKING MGW with 1024 PRA | • 100 % Voice Traffic • A = number of channels × originating traffic per ISDN PRA channel = 30 720 × 0,5 = 15 360 Erl • BHCA = 30 720 × 18 = 552 960 • Load A = 30 720 x 0,005= 154 CAPS NOTE: Group 3 faxes conform to the ITU-T Recommendations T.30 [i.1] and T.4 [i.2]. The horizontal and vertical resolutions are allowed ... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.2 Initial benchmark traffic set | |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.2.1 ISDN/PSTN mixed initial benchmark traffic set | Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution TS 186 025-2 [2], clause 5.1: Session Set-Up/ ISDN-ISDN Use-Case 1 TS 186 025-2 [2], clause 5.1.1.1 ISDN - ISDN Scenario 1.1 Basic call with BC= speech - enblock sending I_ I_S_1.1 10 % Poisson, mean selected by traffic-t... |
d3966a0ea81147b6e3bc9145cdba95fe | 186 025-3 | 4.2.2 PSTN initial benchmark traffic set | Use Case Section Test Scenario Scenario ID Type Scenario % of System Load Scenario Arrival Distribution TS 186 025-2 [2], clause 5.1: Session Set-Up/ PSTN- PSTN Use-Case 4 TS 186 025-2 [2], clause 5.1.4.1 PSTN - ISDN Scenario 4.1 Basic call. The call is released from the calling user P_P_S_4.1 44,5 % TS 186 025-2 [2], ... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 1 Scope | The present document defines initial benchmark tests through definitions of traffics sets and traffic profiles. The benchmark is defined for the IMS network as a whole, as well as for several subsystems of an IMS network. The benchmark is designed so that nodes composing a subsystem can also be benchmarked alone. The i... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 2 References | |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 2.2 Informative 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. NOTE: While any hyperlinks in... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 3 Definitions and abbreviations | |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in Recommendation ITU-T Q.3930 [3] apply. |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AKA Authentication and Key Agreement BC Bearer Capability CC Completion of Communications on No Reply CCBS Completion of Calls to Busy Subscriber CCNR Completion of Calls to No Reply CFB Call forwarding busy CFNR Call forwarding not reply CFU ... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 4 Benchmark tests | ETSI TS 186 008-1 [1] and ETSI TS 186 008-2 [2] have defined the framework for defining and executing an IMS performance benchmark. The present document specifies a benchmark test, which may be implemented and performed as-is, or which may serve as an example for future benchmark tests developed by a service provider o... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 4.1 Benchmark test goals | A benchmark test may be used either for comparison (e.g. comparing the performance of two products), or for prediction (e.g. the configuration specified for a benchmark test is similar enough to a service providers requirements that the result of the test can be used as an estimate of the performance of their deployed ... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 4.2 Initial benchmark traffic set and traffic-time profile | As described in details in ETSI TS 186 008-1 [1], a benchmark test measures the behaviour of a SUT for a specified traffic set and traffic-time profile. A traffic set is composed of a mixture of test scenarios, whose relative frequency of occurrence is specified by traffic set parameters; the traffic-time profile is a ... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 4.3 Initial benchmark test implementation | The present document does not dictate the specific implementation of a test scenario. The test scenarios are defined in ETSI TS 186 008-2 [2] as protocol diagrams. These scenarios are implemented either by a commercial test system provider or as part of a benchmark test run. Example implementations include using the ET... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 4.3.1 SUT Configuration | The initial benchmark supports a Session Control Subsystem SUT configuration as defined in ETSI TS 186 008-2 [2], clause 4. Release 1 does not specify reliability or availability requirements. The availability architecture and design objective target of the SUT should be described in the test report. 100 105 110 115 12... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 4.3.2 Preamble | The preamble defines the steps necessary to configure the SUT for a benchmark run. The following steps shall be completed before the initial benchmark test run. 1) The SUT shall be started from a cold boot. 2) "Total Provisioned Subscribers" shall be provisioned in the database. 3) The initial "Percent Registered Subsc... |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 4.3.3 Test Execution | The initial benchmark test shall contain StepNumber stair steps in the profile. The test execution is valid if the profile has steps in the DOC underload range and at least one step in the DOC overload range. |
852ab15656945a1ce0e6c84a2dcfd35d | 186 008-3 | 4.3.4 Graphs | The following graphs shall be plotted in the benchmark report: • Scenario success rate: - X-Axis: time (s). - Y-Axis 1: Scenario Attempts Per Second for the traffic set. - Y-Axis 2: Percentage of Inadequately Handled Scenario Attempts. • Scenario average transaction response time{for each identified scenario in the tra... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 1 Scope | The present document describes the performance benchmark methology for the IMS based services MMTel, Video Telephony and IMS/ PES. The terminology and concepts are described in TR 101 577 [i.11]. The present document is the second part of the multi-part deliverable which consists of four parts. TS 186 008-1 [i.1] defin... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] Void. [2] ETSI TS 123 002 (V11.4.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 version 11.4.0 Release 11)". |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-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. [i.1] ETSI TS 186 008-1: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 1: Core Concepts ". [i.2] ETSI TS 186 008-3: "IMS Network Testing (... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 3 Definitions and abbreviations | |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 3.1 Definitions | For the purposes of the present document, the IMS benchmarking terms and definitions given in TR 101 577 [i.11] apply. |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 121 905 [i.7] and the following apply: PES IMS- based PSTN/ISDN Emulation Sub-system ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 8 |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4 System Under Test (SUT) subsystems | |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4.1 IMS/MMtel | An IMS/NGN benchmark is required to allow not only a complete IMS network but also subsystems of a network corresponding to discrete products that may be available from a supplier. To address this requirement in this multi-part deliverable, a series of subsystems are defined, which will serve as a System Under Test (SU... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4.1.1 Session Control Subsystem (SCS) | The Session Control Subsystem (SCS) consists of the P-CSCF, I-CSCF, and S-CSCF, and HSS components, as depicted in figure 2. A valid SCS configuration consists of the set of x-CSCF building blocks, as well as the database functions HSS and SLF that support their functionality. The reference points for the SCS are the G... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4.1.2 HSS subsystem | This subsystem refers to the HSS. |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4.1.3 P-CSCF subsystem | The P-CSCF consists of the P-CSCF component, as depicted in figure 3. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 10 A valid P-CSCF configuration consists of the set of P-CSCF building blocks. The reference points for the subsystem are the Gm reference point between the UE traffic generator and the home and visited P-CSCFs... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4.1.4 S/I-CSCF subsystem | The S/I-CSCF Subsystem consists of the S-CSCF, I-CSCF, HSS, and SLF components, as depicted in figure 4. A valid S/I-CSCF configuration consists of the set of S-CSCF and I-CSCF building blocks, as well as the database functions HSS and SLF that support their functionality. The reference points for the subsystem are the... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4.2 IMS/PES | The System Under Test (SUT) subsystems for IMS/PES is described in TS 186 025-2 [i.21]. |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4.3 IMS to IMS/PES | The IMS and IMS/PES configuration are depicted in figure 5. MGC SIP UA MGF MGF UA AGCF RTP FM SIP UA FM MGC S-CSCF S-CSCF AS AS P-CSCF Figure 5: MMtel and IMS/PES configuration |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4.4 IMS/LTE Basic Configuration | Figure 6: IMS/LTE Basic Configuration ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 12 |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 4.5 VoLTE | The VoLTE components, are depicted in figure 7. IMS UA MME S-GW HSS P-CSCF IMS-ALG IMS-AGW P-GW V-PCRF UE eNodeB IMS Core LTE-Uu S11 S5 SGi LTE-Uu I/S-CSCF Sh I S C Cx Ut Ut VPLMN HPLMN H-PCRF Mx IMS UA UE Diameter Agent Diameter Agent S6a S9 S9 S6a Diameter App ID = 0 IBCF/TRGW Ici/Izi eNodeB MME S-GW P-GW S5 S6a P-CS... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 5 Use cases | The following use cases, and corresponding tests, are currently defined. This clause attempts to define a set of basic use-cases and further ones can be defined similarly. These newly defined use-cases, or modifications to the ones presented here, will have to be described in a similar manner in the test report. |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 5.1 IMS | |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 5.1.1 Registration/de-registration use-case 1 | Registration is the first use-case that is employed when using an IMS network. During this operation the UE announces its contact location to the home domain registrar in order for the home network to route terminating messages towards it. It is performed by an UE when it is turned on. De-registration is the last opera... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 5.1.1.1 Definition | The registration/de-registration is the process by which a UE announces, updates or deletes its location information to the home domain"s registrar. This operation is authenticated and a secure communication channel for subsequent signaling is set-up between the UE and the network. |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 5.1.1.2 Scenarios | While the scenario describe actions on the part of the UE, the portion of the signaling path between the UE and the complete IMS system outside the System Under Test configuration are simulated by the test environment with test system characteristics fixed with stated values. 5.1.1.2.1 Use Case 1- Scenario 1 - Successf... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 5.1.1.2.7 Use Case 1- Scenario 7 - Re-registration - user currently registered | To refresh the registration timer the UE sends a re-registration request before the expiration time expires. This should be sent either 600 seconds before the expiration time if the registration time was greater than 1 200 seconds, or when half the registration time has passed when the registration time was under equal... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 5.1.1.2.8 Use Case 1- Scenario 8 - Re-subscription - user currently registered | As the subscription might have a different expiration timer as the registration, re-subscription is not necessarily linked to re-registration. The process is detailed in figure 10. Figure 10: Re-subscription - user currently registered signaling flow |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 5.1.1.2.9 Use Case 1- Scenario 9 - Re-registration - user roaming | When the UE is roaming to another visited network, the procedures are similar to those of initial registration. As there are no security association set-up with the new P-CSCF, the initial REGISTER request will be authenticated. The network will internally take care of the old registration, without any UE interaction. |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 5.1.1.2.10 Use Case 1- Scenario 10 - UE initiated de-registration | When the UE requires terminating immediately the registration it can do so by issueing a REGISTER request with an expiration timer set to "0". |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6 Session set-up/tear-down scenarios | This use-case corresponds to a normal 2-party call. The "session set-up" part refers to the establishment of the call and the "session tear-down" to its destroyal. Before this scenario is performed, the respective User Endpoints which belong to the particular SUT domain and involved in the communication have to be succ... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.1 MMTel to MMTel | MMTEL to MMTEL Use case 2 Scenario 1 Successful call - This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reser... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.2 IMS/PES to IMS/PES | The Use Cases for IMS/PES are described in TS 186 025-2 [i.21]. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 24 |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.3 MMTel - IMS/PES | |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.3.1 ISDN to MMTel Use case 3 | ISDN to MMTel Use case 3 Scenario 1 Basic call with BC= ITC_value - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g.... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.3.2 MMTel to ISDN Use case 4 | MMTel to ISDN Use case 4 Scenario 1 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS pa... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.3.3 MMTel to PSTN Use case 5 | MMTel to PSTN Use case 5 Scenario 1 Basic call. The call is released from the called user. This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS par... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.3.4 PSTN to MMTEL Use case 6 | PSTN to MMTel Use case 6 Scenario 1 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS pa... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.4 VoLTE to IMS/PES | |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.4.1 ISDN to VoLTE Use case 7 | ISDN to VoLTE Use Case 7 Scenario 1 Basic call with BC= ITC_value - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g.... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.4.2 VoLTE to ISDN Use case 8 | VoLTE to ISDN Use Case 8 Scenario 1 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS pa... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.4.3 VoLTE - PSTN Use case 9 | VoLTE to PSTN Use Case 9 Scenario 1 Basic call. The call is released from the called user. This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS par... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.4.4 PSTN to VoLTE Use case 10 | PSTN to VoLTE Use case 10 Scenario 1 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS p... |
268bbc2f61f0ede46bb8b3903229f5bf | 186 008-2 | 6.5 VoLTE to VoLTE Use case 11 | VoLTE to VoLTE Use case 11 Scenario 1 Successful call - This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource rese... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.