hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 3 Definition of terms, symbols and abbreviations | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 119 471 [i.5], ETSI TS 119 472-1 [3] and the following apply: PID/EAA Provider's Registrar: entity in charge of registering the PID/EAA Provider's information necessary to allow for their electronic identification and authentication towards European D... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 3.2 Symbols | Void. |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARF Architecture and Reference Framework EAA Electronic Attestation of Attributes EDP Embedded Disclosure Policy EUDI European Digital Identity HAIP High Assurance Interoperability Profile JWS JSON Web Signature JWT JSON Web Token ETSI ETSI TS... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 3.4 Notation | The present document assigns one identifier for each requirement. These identifiers result from the concatenation of the following three components: 1) A topic identifier, for signalling the topic targeted by the requirement. 2) The number of the clause where the requirement is defined. 3) A number of 2 digits. In each... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4 EAA issuance flows | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.1 General requirements | GEN-REQ-4.1-01: The EUDI Wallet shall implement the profile of the protocol defined in OpenID4VCI [2] specified by the requirements defined for the Wallet in OpenID4VC-HAIP [1], clause 4 and its subclauses, unless specified otherwise in the present document. GEN-REQ-4.1-02: When PID Providers and the EAA Providers are ... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.2.1 General requirements | ISS-MDATA-4.2.1-01: The Issuer Metadata shall be a signed metadata according to clause 12.2.3 of OpenID4VCI [2] with a JSON Web Signature (JWS hereinafter) specified in IETF RFC 7515 [8]. ISS-MDATA-4.2.1-02: The signing certificate of the signature on the Issuer Metadata shall be the access certificate of the PID/EAA P... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.2.2 Provision of access certificates of PID/EAA Provider to EUDI Wallet | ISS-MDATA-ACC_CERT-4.2.2-01: The JWS signing the Issuer Metadata shall contain, in its Protected Header, the x5c header parameter as specified in IETF RFC 7515 [8]. ISS-MDATA-ACC_CERT-4.2.2-02: The x5c header parameter shall contain the base64 (IETF RFC 4648 [7]) encoding of the DER-encoded access certificate of the PI... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.2.4 Provision of PID/EAA reuse policy | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.2.4.1 General requirements | The present clause specifies requirements for a PID/EAA reuse policy, for controlling the number of times that the Wallet Unit may present the PID/EAA to Relying Parties. ISS-MDATA-EAA-REUSE-POL-4.2.4.1-01: The credential_metadata child parameter of credential_configurations_supported parameter in the Issuer Metadata m... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.2.4.2 ARF pre-defined PID/EAA reuse policy | NOTE 1: The present clause profiles the parameter credential_reuse_policy for the case where the PID/EAA reuse policy is as specified in Annex 2 of EUDI Wallet ARF [i.1] (requirement ISSU_37 and related). ISS-MDATA-EAA-REUSE-POL-4.2.4.2-01: If the id member has the value "arf_annex_ii" the options array member shall be... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.2.5 Provision of Embedded Disclosure Policy | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.2.5.1 Introduction (informative) | As specified in [i.3] 'embedded disclosure policy' means a set of rules, embedded in an electronic attestation of attributes by its provider, that indicates the conditions that a wallet-relying party has to meet to access the electronic attestation of attributes. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 15 In line with ... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.2.5.2 Requirements for the data model of Embedded Disclosure Policy | ISS-MDATA-EBD-4.2.5.2-01: The Embedded Disclosure Policy shall be identified by a unique URI. ISS-MDATA-EBD-4.2.5.2-02: The Embedded Disclosure Policy may be accessible via this URI. ISS-MDATA-EBD-4.2.5.2-03: The Embedded Disclosure Policy associated with EAA shall be identified by including its unique URI. The EAA pro... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.3 Requirements for the Credential Offer | ISS-CRED-OFFER-4.3-01: PID/EAA Providers shall support at least one of the following Grant Types: "authorisation_code" or "urn:ietf:params:oauth:grant-type:pre-authorised_code", as defined in clause 4.1.1 of OpenID4VCI [2]. |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.4 Requirements for the Pushed Authorisation Request | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.4.1 Scope of application | AUTH-REQ-4.4.1-01:The requirements defined in clause 4.4 of the present document, and its subclauses, shall only apply to the PID/EAA Providers that implement the Authorisation Code Flow as specified in clause 3.5 of OpenID4VCI [2]. |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.4.2 Requirements for contents of the Pushed Authorisation Request | AUTH-REQ-4.4.2-01: The Pushed Authorisation Request shall include the Wallet Instance Attestation (WIA) as an OAuth-Client-Attestation parameter, as specified in Appendix E of OpenID4VCI [2], and IETF draft-ietf-oauth-attestation-based-client-auth-07 [5]. NOTE 1: The contents of the WIA are specified in section 2.3.3 o... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.4.3 Requirements for processing the Pushed Authorisation Request | AUTH-REQ-PROC-4.4.3-01: When a PID/EAA Provider receives a WIA, then it shall check that the signature of the JWT verifies under the Wallet Provider's public key as found on the Trusted List of Wallet Providers. AUTH-REQ-PROC-4.4.3-02: When a PID/EAA Provider receives a WIA, then it shall check that it has not expired.... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.5 Requirements for the Token Request | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.5.1 Requirements for contents of the Token Request | TOKEN-REQ-4.5.1-01: The Token Request shall include the Wallet Instance Attestation (WIA) as an OAuth-Client-Attestation parameter, as specified in Appendix E of OpenID4VCI [2], and IETF draft-ietf-oauth-attestation-based-client-auth-07 [5]. NOTE: The contents of the WIA are specified in section 2.3.3 of EUDI Wallet TS... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.5.2 Requirements for processing the Token Request | TOKEN-REQ-PROC-4.5.2-01: When a PID/EAA Provider receives a WIA, then it shall check that the signature of the JWT verifies under the Wallet Provider's public key as found on the Trusted List of Wallet Providers. TOKEN-REQ-PROC-4.5.2-02: When a PID/EAA Provider receives a WIA, then it shall check that it has not expire... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.6 Requirements for the Credential Request | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.6.1 Requirements for contents of the Credential Request | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.6.1.1 Common requirements | CRED-REQ-4.6.1.1-01: If the PID/EAA is cryptographically bound to the device, the Credential Request shall include the proofs parameter. CRED-REQ-4.6.1.1-02: The proofs parameter shall contain either the jwt child member or the attestation child member. NOTE 1: Using proofs->jwt, the WU sends proof of possession of pri... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.6.1.2 Using proofs->jwt mechanism | CRED-REQ-4.6.1.2-01: The jwt JSON array member shall have 1 element. CRED-REQ-4.6.1.2-02: The element in the jwt member shall contain the nonce claim in their corresponding JWT Bodies, obtained from the Nonce Endpoint of the PID/EAA Provider. CRED-REQ-4.6.1.2-03: The element in the jwt array member shall contain the ke... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.6.1.3 Using proofs->attestation mechanism | CRED-REQ-4.6.1.3-01: The attestation array member shall contain only one element. CRED-REQ-4.6.1.3-02: The element in the attestation array member shall contain the nonce claim in its JWT Body, obtained from the Nonce Endpoint of the PID/EAA Provider. CRED-REQ-4.6.1.3-03: The element in the attestation array member sha... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.6.2 Requirements for processing the Credential Request | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.6.2.1 Requirements for processing Credential Request with proofs->jwt | CRED-REQ-PROC-4.6.2.1-01: The PID/EAA Provider shall verify that the signature of the key_attestation parameter in the element of the jwt array member (the WUA), verifies under the Wallet Provider's public key as found on the Trusted List for Wallet Providers. CRED-REQ-PROC-4.6.2.1-02: The PID/EAA Provider shall verify... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.6.2.2 Requirements for processing Credential Request with proofs->attestation | CRED-REQ-PROC-4.6.2.2-01: The PID/EAA Provider shall verify that the signature of the element of the attestation array member (the WUA) verifies under the Wallet Provider's public key as found on the Trusted List for Wallet Providers. CRED-REQ-PROC-4.6.2.2-02: The PID/EAA Provider shall generate as many PIDs/EAAs as el... |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 4.7 Requirements for the Notification Request | NOT-REQ-4.7-01: If the EUDI Wallet supports notifications, then it shall send one or more Notification Requests per notification_id value received from the PID/EAA Provider. |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 5 Crypto suites | CRYPTO-5-01: In addition to the crypto suites specified in OpenID4VC-HAIP [1], the EUDI Wallet and the PID/EAA Providers shall support the A128GCM algorithm and the A256GCM algorithm specified in NIST SP 800.38D [10]. |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 6 Security considerations | SEC-6-01: The security considerations in clause 13 of OpenID4VCI [2] shall apply. SEC-6-02: The privacy considerations in clause 15 of OpenID4VCI [2] shall apply. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 20 Annex A (normative): Requirements for issuance of X509-AC EAAs A.1 Introduction The present annex defines specific... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 1 Scope | The present document specifies the protocol conformance testing for testing a MCVideo Server for compliance to the Mission Critical Video (MCVideo) over LTE protocol requirements defined by 3GPP. The present document addresses only MCVideo Server-Client communication scenarios. It does not cover e.g. MCVideo Server-EPS... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 2 References | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 3 Definitions of terms, symbols and abbreviations | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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). ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 15 F... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 3.2 Symbols | Void. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 16 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 4 General | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 4.1 Test methodology | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 MCVideo Client. A declaration by the MCVideo Server supplier (to use the Implementation Conformance Statement (ICS) proforma specified in ETSI TS 136 579-4 [2] (3GPP TS 36.579-4)) is used to determine whether a... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 4.1.2 Test interfaces and facilities | Detailed descriptions of the MCVideo test interfaces and special facilities for testing are provided in ETSI TS 136 509 [4] (3GPP TS 36.509). |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 4.2 Implicit testing | For some 3GPP MCVideo 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. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 18 For all test cases in the present document unless s... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 4.6 Generic setup procedures | A set of basic generic procedures for MCVideo 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. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5 MCVideo Server - MCVideo Client Configuration | 5.1 MCVIDEO Server - MCVIDEO Client / Configuration / Authentication / User Authorisation / UE Configuration / User Profile / Key generation |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo Client) activates an MCVideo application and requests MCVideo initialisation } then { IUT (MCVideo Server) provides the initial UE configuration and performs MCVideo User Authentication and provides id_token, access_token and ... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.1.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 482 [27] (3GPP TS 24.482), clauses 6.3.1, A.2.1.3, A.2.3, ETSI TS 124 484 [28] (3GPP TS 24.484), clauses 4.3.1, 4.3.3, 4.4, 6.2.3, 6.2.4.1, 6.3.1.2, 6.3.2.3, 6.3.13.3.2.2, 6.3.13.3.2.3, 9.2.1, 9.2.1A, 9.3.1, 9.3.1A, 9.4.1, ... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.1.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 (MCVideo 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 (MCVideo Server) respond by sending an HTTP 200 (OK... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 (... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.2.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and supports new MCVideo terminated group } ensure that { when { the UE (MCVideo Client) initiates creation of the terminated group by sending a HTTP PUT request } then { IUT (MCVideo Server) responds to the UE (MCVideo Client) with a HTTP 201 (Created) } } (2) with { ... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.2.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 481 [29] (3GPP TS 24.481), clauses 5.4, 5.2A, 6.2.4, 6.3.3.3, 6.3.13.3.2.2, 6.3.13.3.3, 7.2.12.1, 6.3.2.3, 6.3.14.3.1 and 6.3.15.3.1, ETSI TS 133 180 [7] (3GPP TS 33.180) clauses 7.3.2 and 7.3.3.2. Unless otherwise stated t... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.2.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 IUT (MCVideo 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 IUT (MCVideo Server) correctly perform pr... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 (MCVideo Client). 5.3 MCVIDEO Server - MCVIDEO Client / Configuration / Group Affiliation / Implicit Aff... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.3.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) having received the provisioned MCVideo Client's group information or a pointer to the group information, indicating that the MCVideo Client is authorized to affiliate with the specified group} ensure that { when { the SS-UE1 (MCVideo client ) requests for own affiliation status and to s... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.3.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 481 [29] (3GPP TS 24.481), clauses 5.4, 5.2A, 6.2.4, 6.3.3.3, 6.3.13.3.2.2, 6.3.13.3.3, 7.2.12.1, ETSI TS 124 281 [8] (3GPP TS 24.281) clauses 8.2.2.2.3, 8.2.2.2.4, 8.2.2.2.5, 8.2.2.2.8 and 8.2.2.2.15. Unless otherwise stat... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.3.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.3.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 IUT (MCVideo Server) correctly perform procedure 'MCVideo Group Affiliation Status Determination and Subscription' as described in Annex A, Table A.3.5.3-1 to subscribe the SS-UE1 (MCVideo Client) to own affiliation... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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. 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.3.5.3-1) Derivation Path: Annex A, Table A.3.5.4-1 Information E... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.4.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo client ) requests to determine the currently active MCVideo service settings with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (2) with { IUT (MCVi... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.4.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 7.1, 7.2.4, 7.3.3, 7.3.4, 7.3.5, 7.3.1A, 7.3.6.1 and 7.3.6.2. Unless otherwise stated these are Rel-14 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.1] "This clause describe... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.4.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.4.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 IUT (MCVideo Server) correctly perform procedure 'MCX Subscription and Notification' as described in Annex A, Table A.2.7.3-1 to determine the currently active MCVideo service settings of the SS-UE1 (MCVideo Client)... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 SUBSCRIBE from the SS-UE1 (Step 1, Table 5.4.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-... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.5.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { IUT (MCVideo Server) requests to update the existing CSK } then { IUT (MCVideo Server) sends a SIP MESSAGE message to the SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having registered the clients } ensure that { when { the SS-UE1 ... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.5.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.7, ETSI TS 133 180 [7] (3GPP TS 33.180), clauses 9.2.1.1, 9.2.1.2, 9.2.1.4 and 5.8.1, and ETSI TS 124 581 [9] (3GPP TS 24.581), clauses 13.1, 13.2 and 13.3.2. Unless otherwise stated the... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.5.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.5.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 IUT (MCVideo Server) 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 MCVideo Server and SS-UE1 (MCVideo Client)?... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 MESSAGE from the IUT (MCVideo Server) (Step 1, Table 5.5.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GP... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.6.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) having registered the clients } ensure that { when { the SS-UE1 (MCVideo Client) initiates an E2E group call with manual commencement mode and with implicit transmission request and without implicit granted } then { IUT (MCVideo Server) accepts the call from the initiator and establishes... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.6.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 8.2.2.2.16, 8.2.2.3.9 and 8.2.2.3.10. Unless otherwise stated these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 8.2.2.2.16] "Upon receiving a SIP SUBSCRIBE reques... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.6.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 5.6.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E group call establishment, manual commencement' as described in Annex A, Table A.3.2.3-1 to establish a group call with manual commencement mode, and with... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 SUBSCRIBE from the SS-UE1 (Step 2, Table 5.6.3.2-1; Step 1, Annex A, Table A.2.7.3-1) Derivation Path: Annex A, Table A.2.7.4-1, condition PR... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6 MCVideo Server - MCVideo Client operation | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1 Group call | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1 Pre-arranged Group Calls | 6.1.1.1 MCVideo Server - MCVideo Client / Pre-arranged Group Call / On-demand / Automatic Commencement Mode / Transmission Control / Upgrade to Emergency Group Call / Cancel Emergency State / Upgrade to Imminent Peril Group Call / Cancel Imminent Peril State |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having registered the clients} ensure that { when { the SS-UE1 (MCVideo Client) initiates a pre-arranged group call with automatic commencement mode and implicit transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and establishes ... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.1.3.1.1, 9.2.1.3.2, 9.2.1.3.3.1, 9.2.1.4.1.1, 9.2.1.4.1.2, 9.2.1.4.2, 9.2.1.4.3, 6.3.2.2.5.2, 6.2.3.1.2, 6.2.3.1.1, 9.2.1.2.1.3, 9.2.1.2.1.4, 9.2.1.2.1.5, 6.4, and ETSI TS 124 581 [9] (... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.1.3 Test description | 6.1.1.1.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo Server will communicate, Parameters are set to the default parameters for the basic E-UTRA S... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.2.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having registered the clients} ensure that { when { the SS-UE1 (MCVideo Client) initiates an emergency pre-arranged group call with automatic commencement mode and implicit transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and e... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.1.3.1.1, 9.2.1.3.2, 9.2.1.3.3.1, 9.2.1.4.1.1, 9.2.1.4.1.2, 9.2.1.4.2, 9.2.1.4.3, 6.3.2.2.5.2, 6.2.3.1.2, 6.2.3.1.1, and ETSI TS 124 581 [9] (3GPP TS 24.581), clauses 6.3.2.2, 6.3.3, 6.4... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.2.3 Test description | 6.1.1.2.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo Server will communicate, Parameters are set to the default parameters for the basic E-UTRA S... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.3.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having registered the clients} ensure that { when { the SS-UE1 (MCVideo Client) initiates a pre-arranged group call with automatic commencement mode and without transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and establishes t... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.3.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.1.3.1.1, 9.2.1.3.2, 9.2.1.3.3.1, 9.2.1.4.1.1, 9.2.1.4.1.2, 9.2.1.4.2, 9.2.1.4.3, 6.3.2.2.5.2, 6.2.3.1.2, 6.2.3.1.1, and ETSI TS 124 581 [9] (3GPP TS 24.581), clauses 6.3.2.2, 6.3.3, 6.4... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.3.3 Test description | 6.1.1.3.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo Server will communicate, Parameters are set to the default parameters for the basic E-UTRA S... |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.4.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having registered the clients} ensure that { when { the SS-UE1 (MCVideo Client) initiates a pre-arranged group call with automatic commencement mode and implicit transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and establishes ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.