hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.7.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.2.7.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.3.3.3-1; Step 1, Annex A, Table A.2.21.3-1) Derivation Path: An... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { SS-UE3 (MCPTT Client) requests the remote initiation of a private call by sending a SIP MESSAGE message } then { IUT (MCPTT Server) sends a SIP MESSAGE message to SS-UE1 (MCPTT Client) and responds with a SIP 200 (OK) to SS-UE3 (MCPTT Client) } } (... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 11.1.7.2.1, 11.1.7.2.2, 11.1.7.3.1, 11.1.7.3.2, 11.1.7.4. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/pa... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client), SS-UE2 (MCPTT Client) and SS-UE3 (MCPTT Client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client), the SS-UE2 (MCPTT client) , the SS-UE3 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.3.2 Test procedure sequence | Table 6.2.8.3.2-1: Main behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE3 (MCPTT client) requests the remote initiation of a private call by SS-UE1 (MCPTT client) to SS-UE2 (MCPTT client) - - - - 2 Check: Does the MCPTT Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 280 Table 6.2.8.3.3-1: SIP MESSAGE from the SS-UE3 (Step 2, Table 6.2.8.3.2-1; Step 1, Annex A, Table A.2.10.3-1) Derivati... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3 Location | 6.3.1 MCPTT Server - MCPTT Client / Location / Event Triggered Location Information report |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { IUT (MCPTT Server) requests to send a location reporting configuration } then { IUT (MCPTT Server) sends a SIP MESSAGE message containing the cell change trigger criteria and the minimum report interval to the SS-UE1 (MCPTT Client) } } (2) with { I... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379), clauses 13.2.2, 13.2.4, 13.3.4.1, 13.3.4.2. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be un... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 285 - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.3.2 Test procedure sequence | Table 6.3.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the MCPTT Server send a location reporting configuration to SS-UE1 (see note 1) - - - - 2 Check: Does the MCPTT Server correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 286 Table 6.3.1.3.3-1: SIP MESSAGE from the MCPTT Server (Step 2, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Der... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { IUT (MCPTT Server) requests to send a location reporting configuration } then { IUT (MCPTT Server) sends a SIP MESSAGE message containing the periodic trigger criteria and the minimum report interval to the SS-UE1 (MCPTT Client) } } (2) with { IUT ... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379), clauses 13.2.3, 13.3.3, 13.3.4.1, 13.3.4.2. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be un... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 136 508 [23] (3GPP TS 36.508) clause 4.4. T... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.3.2 Test procedure sequence | Table 6.3.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the MCPTT Server send a location reporting configuration to SS-UE1? (see note) - - - - 2 Check: Does the MCPTT Server correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.3.1.3.3-1: SIP MESSAGE from the MCPTT Server (Step 2, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4 MBMS | 6.4.1 MCPTT Server - MCPTT Client / MBMS / MBMS Bearer Announcement / MBMS Bearer Listening Status / Transition to MBMS from Unicast / MBMS Floor Control / Transition to Unicast from MBMS |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCPTT Client) initiates establishment of a group call with automatic commencement mode and without implicit floor request } then { IUT (MCPTT Server) accepts the call from the initiator and establishes a pre-arranged group call } } (2) ... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 14.2.2.2, 14.2.3, 14.3.3.1, ETSI TS 124 380 [5] (3GPP TS 24.380) clauses 10.2.2.2, 10.2.3.2, 10.2.3.3, 10.2.3.4, 10.2.3.5, 10.2.3.11, 10.2.3.12, 6.3.4.3.3, 6.3.4.4.2, 6.3.4.4.6. The followin... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) and SS-UE2 (MCPTT client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 136 508 [23] (3GP... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.3.2 Test procedure sequence | Table 6.4.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCPTT client) requests the establishment of a group call to SS-UE2 (MCPTT client) with automatic commencement mode and without implicit floor request. - - - - 2 Check: Does the MCPTT server correctly perform procedure... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.4.1.3.3-1: SIP MESSAGE from the MCPTT Server (Step 4a, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, co... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2 MCPTT Server - MCPTT Client / MBMS / Multi Talker | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCPTT Client) initiates establishment of a group call with automatic commencement mode and without implicit floor request } then { IUT (MCPTT Server) accepts the call from the initiator and establishes a pre-arranged group call } } (2) ... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 14.2.2.2, 14.2.3, 14.3.3.1, ETSI TS 124 380 [5] (3GPP TS 24.380) clauses 10.2.2.2, 10.2.3.2, 10.2.3.3, 10.2.3.3a, 10.2.3.4, 10.2.3.5, 10.2.3.11, 6.3.4.4.2, 6.3.4.4.6, 6.3.4.4.7a. The followi... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) and SS-UE2 (MCPTT client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 136 508 [23] (3GP... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.3.2 Test procedure sequence | Table 6.4.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCPTT client) requests the establishment of a group call to SS-UE2 (MCPTT client) with automatic commencement mode and without implicit floor request. - - - - 2 Check: Does the MCPTT server correctly perform procedure... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.4.2.3.3-1: SIP MESSAGE from the MCPTT Server (Step 4a, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, co... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 1 Scope | The present document specifies the protocol conformance testing for testing a MCData Server for compliance to the Mission Critical Data (MCData) over LTE protocol requirements defined by 3GPP. The present document addresses only MCData Server-Client communication scenarios. It does not cover e.g. MCData Server-EPS, MCD... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 2 References | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 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 referenced document (including any amendments) applies. Referenced documents which a... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 3 Definitions of terms, symbols and abbreviations | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply. NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). For the purpose of the present document, the... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 3.2 Symbols | Void. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply: NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). CSK Client-Server K... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4 General | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.1 Test methodology | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.1.1 Testing of optional functions and procedures | Any function or procedure which is optional, may be subject to a conformance test if it is implemented in the MCData Server. A declaration by the MCData Server supplier (to use the Implementation Conformance Statement (ICS) proforma specified in ETSI TS 136 579-4 [3] (3GPP TS 36.579-4)) is used to determine whether an ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.1.2 Test interfaces and facilities | Detailed descriptions of the MCData test interfaces and special facilities for testing are provided in ETSI TS 136 509 [9] (3GPP TS 36.509). |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.2 Implicit testing | For some 3GPP MCData protocol features conformance is not verified explicitly in the present document. This does not imply that correct functioning of these features is not essential, but that these are implicitly tested to a sufficient degree in tests which are not explicitly dedicated to test the feature. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.3 Repetition of tests | As a general rule, the test cases specified in the present document are highly reproducible and do not need to be repeated unless otherwise stated. 4.4 Handling of differences between conformance requirements in different releases of cores specifications The conformance requirements which determine the scope of each te... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.5 Reference conditions | The reference environments used by all signalling and protocol tests is specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). Where a test requires an environment that is different, this will be specified in the test itself. For all test cases in the present document unless specified otherwise the condition MCDATA app... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.6 Generic setup procedures | A set of basic generic procedures for MCData Client-Server communication are described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). These procedures will be used in numerous test cases throughout the present document. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5 MCData Server - MCData Client Configuration | 5.1 MCDATA Server - MCDATA Client / Configuration / Authentication / User Authorisation / UE Configuration / User Profile / Key generation |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData client) activates an MCData application and requests MCData initialisation } then { IUT (MCData Server) provides the initial UE configuration and performs MCData User Authentication and provides id_token, access_token and refres... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 482 [7] (3GPP TS 24.482) clauses 6.3.1, A.2.1.3, A.2.3, ETSI TS 124 484 [8] (3GPP TS 24.484) clauses 4.3.1, 4.3.4, 4.4, 6.3.13.2.3, 6.3.3.2.3, 6.3.3.2.1, 4.1.4, 10.2.1, 10.2.1A, 10.3.1, 10.3.1A, 10.4.1, 6.2.3, ETSI TS 124 4... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 36 - For the underlying "transport bearer" over which the SS-UE1 (MCData client) and the MCData Server will communicate Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI T... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.3.2 Test procedure sequence | Table 5.1.3.2-1: Main behaviour St Procedure Message Sequence TP Verdict U - S Message 0A The SS-UE1 (MCData client) sends an HTTP GET (initial UE configuration) request to retrieve the initial UE configuration from the Server. --> HTTP GET - - 0B Check: Does the IUT (MCData Server) respond by sending an HTTP 200 (OK) ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.3.3 Specific message contents | Table 5.1.3.3-1: HTTP POST (Step 1, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.3-1, condition AUTH Table 5.1.3.3-2: HTTP POST (Step 3, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.3-1, condition USERAUTH Table 5.1.3.3-3: HTTP POST (... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 and supports new MCData terminated group } ensure that { when { the UE (MCData client) initiates creation of the terminated group by sending a HTTP PUT request } then { IUT (MCData Server) responds to the UE (MCData Client) with a HTTP 201 (Created) } } (2) with { IUT (... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 484 [8] (3GPP TS 24.484) clauses 4.3.1, 4.3.4, 4.4, 6.3.13.2.3, 6.3.3.2.3, 6.3.3.2.1, 4.1.4, 10.2.1, 10.2.1A, 10.3.1, 10.3.1A, 10.4.1, 6.2.3, ETSI TS 124 481 [6] (3GPP TS 24.481) clauses 5.5, 5.2A, 6.2.4, 6.2.2, 6.3.2.2.2, ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) - For the underlying "transport bearer" over which the SS-UE1 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 136 508 [10] (3GPP TS 36.508) clause 4.4... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.3.2 Test procedure sequence | Table 5.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server correctly perform procedure 'MCX Server Terminated Group Creation' as described in Annex A, Table A.2.4.3-1 to create group B? - - 1 P 2 Check: Does the MCData Server correctly perform procedure 'MCX S... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications: • Subclauses referring to messages from UE relate to SS-UE1 (MCX Client). 5.3 MCDATA Server - MCDATA Client / Configuration / Group Affiliation / Implicit Affilia... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.1 Test Purpose (TP) | (1) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is authorized to affiliate with the specified group} ensure that { when { the SS-UE1 (MCData client ) requests for own affiliation status and to subsc... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 484 [8] (3GPP TS 24.484) clauses 4.3.1, 4.3.4, 4.4, 6.3.13.2.3, 6.3.3.2.3, 6.3.3.2.1, 10.2.1, 10.2.1A, 10.3.1, 10.3.1A, 10.4.1, 6.2.3, ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 6.3.5, 8.3.2.3, 8.3.2.4, 8.3.2.5, 8.3.2.8,... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client) - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defi... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.3.2 Test procedure sequence | Table 5.3.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation Status Determination and Subscription' as described in Annex A, Table A.4.11.3-1 to subscribe the SS-UE1 (MCData client) to own affiliation status ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications: ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 80 Table 5.3.3.3-1: SIP SUBSCRIBE from the SS-UE1 (Step 1, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.11.3-1) Derivation ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.1 Test Purpose (TP) | (1) with { IUT (MCData Server) is able to create pre-established session } ensure that { when { the SS-UE1 (MCData client ) requests creation of pre-established session with sending SIP INVITE message } then { IUT (MCData Server) responds with optional SIP 100 Trying and mandatory 200 (OK) message } } (2) with { IUT (M... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 18.1, 18.3.2.2, 18.3.3.2.1, 18.3.2.2.2, 18.3.4.2.1, 18.3.4.2.2. Unless otherwise stated these are Rel-16 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 18.1] "The MCData client... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) - For the underlying "transport bearer" over which the SS-UE1 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 136 508 [10] (3GPP TS 36.508) clause 4.4... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.3.2 Test procedure sequence | Table 5.4.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData server correctly perform test procedure 'MCX Participating Terminated pre-established session establishment' as described in Annex A, Table A.2.13.3-1 to create a pre-established session? - - 1 P 2 Check: Doe... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 5.4.3.3-1: SIP INVITE from the SS-UE1 (Steps 1 and 3, Table 5.4.3.2-1; Step 1, Annex A, Table A.2.13.3-1) Derivation Path: Annex A, Table A.2.13.4-1, condit... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData client ) requests to determine the currently active MCData service settings with SIP SUBSCRIBE message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (2) with { IUT (MCData S... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 7.1, 7.2.4, 7.3.3, 7.3.4, 7.3.1A, 7.3.5, 7.3.6.1, 7.3.6.2. Unless otherwise stated these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.1] "This clause describes t... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) - For the underlying "transport bearer" over which the SS-UE1 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 136 508 [10] (3GPP TS 36.508) clause 4.4... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.3.2 Test procedure sequence | Table 5.5.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server correctly perform procedure 'MCX Subscription and Notification' as described in Annex A, Table A.2.7.3-1 to determine the currently active MCData service settings of the UE (MCData client)? - - 1 P 2 C... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 5.5.3.3-1: SIP SUBSCRIBE from the SS-UE1 (Step 1, Table 5.5.3.2-1; Step 1, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { IUT (MCData Server) requests to update the existing CSK } then { IUT (MCData Server) sends a SIP MESSAGE message to the SS-UE1 (MCData Client) } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 106 (2) with { SS-UE1 (MCData Client) having sent a standalo... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 7.3.7, ETSI TS 133 180 [12] (3GPP TS 33.180) clauses 9.2.1.1, 9.2.1.2, 9.2.1.3, 9.2.1.4, 5.4, 5.2.1, 5.2.2, 5.8.1, 5.8.2, ETSI TS 124 484 [8] (3GPP TS 24.484) clauses 4.3.1, 4.3.4, 4.4, 6.3... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData Client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.3.2 Test procedure sequence | Table 5.6.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to update the existing CSK between the MCData Server and SS-UE1 (MCData Client)? - ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 5.6.3.3-1: SIP MESSAGE from the MCData Server (Step 1, Table 5.6.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData client ) requests to subscribe to functional alias status change notifications with SIP SUBSCRIBE message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } ETSI ETSI TS 104 149-... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 22.2.2.2.3, 22.2.2.2.4, 22.2.2.2.5, 22.2.2.3.3, 22.2.2.3.4, 22.2.2.3.5, 22.2.2.3.6. Unless otherwise stated these are Rel-16 requirements. [ETSI TS 124 282 [13] (3GPP T... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 136 508 [10] (3GPP TS 36.508) clause 4.... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.3.2 Test procedure sequence | Table 5.7.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server correctly perform procedure 'MCData Functional Alias Status Determination and Subscription' as described in Annex A, Table A.4.13.3-1 to determine the current status of a functional alias and to get la... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 5.7.3.3-1: SIP PUBLISH from the SS-UE1 (Step 3, Table 5.7.3.2-1; Step 1, Annex A, Table A.4.14.3-1) Derivation Path: Annex A, Table A.4.14.4-1 Information E... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6 MCData Server - MCData Client operation | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1 Short Data Service | 6.1.1 MCDATA Server - MCDATA Client / Short Data Service (SDS) / Standalone SDS Using Signalling Control Plane / One-to-one Standalone SDS |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests one-to-one Standalone SDS by sending a SIP MESSAGE message with disposition request "DELIVERY" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE2 (MCData Client) and responds with a SIP 202 (Accepted) t... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 9.2.2.3.1, 9.2.2.3.2, 9.2.2.4.1, 9.2.2.4.2, 9.2.2.2.1, 6.2.2.1. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.3.1] "Upon rece... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.3.2 Test procedure sequence | Table 6.1.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a standalone one-to-one SDS message from SS-UE1 (MCData c... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.