hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.2.1 Planning assumptions | Link planning evaluation presented in this clause are theorical links with full clearance along the path, in low and high multipath probability areas, fixed roughness and four rainfall areas; calculations are based on Recommendation ITU-R P.530-17 [i.2] using parameters reported in Table 4 and Table 5. Roughness and dN1 are used in Recommendation ITU-R P.530-17 [i.2] for refractivity gradient calculation and therefore for p0 evaluation: radio planning tools use ITU-R geographical databases for correct p0 evaluation on real links based on different versions of Recommendation ITU-R P.530. The choice of -17 version instead of -19 version is related to the easier p0 evaluation on a theoretical link. Table 4: Long Haul link planning assumptions Planning Parameters - Multipath outage calculation Roughness sa = 200 dN1 -1 000 (high multipath activity) -300 (low multipath activity) Planning Parameters - Rain outage calculation R0.01 (mm/h) 60, 95, 145 Availability objectives Year availability 99,995 % of Reference Modulation System Parameters System Configuration 4+0 CCDP with and without Space Diversity Frequency Bands L6 GHz, 7 GHz, 11 GHz; 28 MHz CS; 128QAM Reference Modulation Antenna diameters 1,8 m (for R0.01 60 mm/h) and 3 m (for R0.01 95 mm/h and 145 mm/h) Space Diversity antenna distance 10 m Sites heights a.s.l. Site 1: 200 m, Site 2: 400 m Table 5: Short Haul link planning assumptions Planning Parameters - Multipath outage calculation Roughness sa = 200 dN1 -300 (low multipath activity) Planning Parameters - Rain outage calculation R0.01 (mm/h) 60, 95, 145 Availability objectives Year availability 99,995 % of Reference Modulation System Parameters System configuration 2+0 CCDP Frequency Bands 7 GHz, 11 GHz; 28 MHz CS; 128QAM Reference Modulation Antenna diameters 0,6 m, 1,2 m Sites heights a.s.l. Site 1: 20 m, Site 2: 30 m |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.2.2 Impacts of rain attenuation and multipath fading | Separate effects of rain attenuation and multipath fading on link availability of lower band have been evaluated for a long haul system without space diversity. As shown in Figure 20 rain attenuation caused huge differences of availability vs. distances for rain rates higher than 60 mm/h: • 60 mm/h: L6 GHz and 7 GHz are always above 99,995 % for reference mode, even better than 99,999 %, while 11 GHz maximum distance is about 35 km. • 145 mm/h: rain attenuation starts having effects also on bands lower than 10 GHz; while L6 GHz is still above 99,995 %, 11 GHz is well below even 99,99 %. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 24 Figure 20: Link availability vs. distance - Rain attenuation only On the contrary, as shown in Figure 21, multipath fading attenuation causes small differences of availability vs. distances across all the three bands considered. Figure 21: Link availability vs. distance - Multipath fading only - single receiver Since space diversity counteracts the effects of multipath fading but has no benefits against the rain, that affects both main and diversity path equally, the behaviour of the different bands may greatly vary according to the different propagation conditions. In clauses 6.2.3, 6.2.4 and 6.2.5 few examples of link planning are reported: performances comparison between low multipath probability area and high multipath probability area have been carried out for long haul and short haul systems in different rainfall areas. For sake of simplicity, the comparison is focused on 7 GHz and 11 GHz. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.2.3 60 mm/h link planning results | Long haul system performances for both single receiver and space diversity configurations shown in Figure 22 confirm that rain attenuation has impact in lower multipath activity areas (dN1: -300), while in high multipath activity areas (dN1: -1 000) space diversity improves link availability reducing the differences among all bands: • Single Receiver configuration: rain attenuation has impact on 11 GHz in areas with lower multipath probability resulting in more than 20 km difference between 7 GHz and 11 GHz, while in areas with high multipath probability link lengths are greatly reduced also for 7 GHz and the differences between the bands are negligible; • Space Diversity configurations: 11 GHz link distances do not improve so much compared single receiver configuration ones, confirming rain attenuation has a huge impact on 11 GHz mainly in areas in areas with lower multipath probability; in these areas space diversity greatly improves 7 GHz performances leading to more than 50 km difference between 7 GHz and 11 GHz, while in high multipath probability areas the improvement is lower and the link difference is reduced to about 10 km. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 25 Figure 22: Link availability vs. distance - Long Haul - 1,8 m antenna - 60 mm/h |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.2.4 95 mm/h link planning results | Rainfall intensity increase strongly limits 11 GHz long haul performances as shown in Figure 23: • Single Receiver configuration: rain attenuation has huge impact on 11 GHz and in areas with lower multipath probability the target objective is achieved only for less than 25 km (half the distance reached by 7 GHz), while if also multipath probability increases 11 GHz does not even reach 20 km. • Space Diversity configurations: 11 GHz performances improve in areas with high multipath probability but the achievable distances remain around 25 km link distances; while 7 GHz performances improve. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 26 Figure 23: Link availability vs. distance - Long Haul - 3 m antenna - 95 mm/h |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.2.5 Short Haul planning results | Short Haul radio performances evaluations have been done for areas with low multipath probability, since such type of radio are mainly deployed for connecting mobile sites to first fibre PoP and not for high-capacity backbones or remote areas connections. Moreover, installation on mobile pole sites does not allow to use big antennas and to implement space diversity combination. The difference between maximum distances that can be covered by 7 GHz and 11 GHz are increasing as rain rate increase strongly limiting 11 GHz applicability in high rainy areas. Figure 24: Link availability vs. distance - Short Haul ETSI ETSI TR 104 142 V1.1.1 (2026-02) 27 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.2.6 Conclusions | In high rainfall areas, 11 GHz is greatly impacted by rain attenuation which remains the limiting factor even in areas with high multipath probability while 7 GHz allows to reach medium-long distances even with smaller antennas. Moreover, space diversity improvement in long haul radios is higher in bands lower than 10 GHz, increasing the spread between 7 GHz and 11 GHz. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.3 Link Length Statistics | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.3.1 Europe link length statistics | ECC Report 173 [i.8] reports link length statistics: the probability of a generic link, in X-axes frequency band, to be shorter than Y-axes values (km) can be determined by the value closest to the (X,Y) point. Figure 25: PtP links length distribution in Low Bands Figure 25 shows that on average bands below 10 GHz allow to reach distances well above 60 km with a typical distance around 50 km, while low bands above 10 GHz have a lower typical distance and on average never exceed 50 km, in line with the planning considerations reported in clause 6.2. A Tier-1 Operator provided an insight of links length distributions across selected European Countries and comparison between bands below and higher than 10 GHz in one selected European Country (Figure 26): • 50 % of the links are between 15 km and 20 km: they are high availability links used for aggregating traffic from multiple mobile sites (e.g. head ring links or first link of a daisy chain or long haul trunk) preventing the use of mid bands as 11 GHz, 13 GHz or 15 GHz that are affected by rain attenuation and cannot reach the required KPI; • remaining 50 % are between 20 km and 50 km: considering that on mobile sites the antenna diameter is strongly limited (typically 0,3 m-0,6 m, never bigger than 1,2 m), such distances cannot be achieved by mid-bands. This limitation is evident in the CDF comparison in one selected country where the gap between low and mid bands is about 10-15 km. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 28 Figure 26: Hop length distribution in low and high bands Europe rainfall rates vary from 15 m/h and 60 mm/h, the highest rainfall rates are reported in the Mediterranean area where the island-mainland links are crucial to ensure the connectivity with highest reliability. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.3.2 Sub-Saharan Africa link distribution | Vendor deployment statistics across different countries in sub-Saharan Africa show maximum link lengths distribution indicative of a long haul and backbone application of MW technology (Figure 27), while the average link length around 20-30 km indicates the use of these bands also on access sites that cannot install antennas larger than 0,9 m to 1,2 m. Almost all rainfall rates are present in this region ranging, for example, from 15 mm/h to 22 mm/h of Namibia up to 95 mm/h to 145 mm/h of Nigeria. Figure 27: Sub-Saharan Africa link lengths distribution |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.3.3 USA link length distribution | Link length of MW links deployed in USA can be retrieved from FCC Universal Licensing Scheme database. Five bands are included in the analysis: 6 GHz, 11 GHz, 18 GHz and 23 GHz. 38 GHz links and all links with 0 km length have not been included. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 29 Figure 28: Link distance distribution 0-50 km Focusing on low bands, 6 GHz and 11 GHz link lengths distribution reported in Figure 29 confirms the radio propagation consideration made in clause 6.2: considering that USA rain rates ranges from 12 mm/h up to 95 mm/h almost all rain zones are present, 11 GHz can achieve distances usually covered with 6 GHz when installed areas with low rain intensity. In fact, in the state of New Mexico (22 mm/h rain intensity) there is the longest 11 GHz link with hop length of 134 km. Figure 29: 6 GHz and 11 GHz link distance distribution 0 km to 100 km As rain rate increases the effects on 11 GHz are evident: in heavy rain regions as Florida, Mississippi and Louisiana (90 mm/h) links longer than 20-25 km are very few and 6 GHz links are 2-3 times longer than 11 GHz ones. The upper limit of 70 km is driven by the link location: the three stated used are flat terrain region and higher distances cannot be physically achieved with realistic tower heights. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 30 Figure 30: Southern States 6 GHz and 11 GHz link distance distribution 0-100 km |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 7 Conclusions | Ubiquitous broadband connectivity is the key requisite of digital era. Notwithstanding the increase of fibre availability, wireless backhaul confirms itself as a strategic asset in communication infrastructure networks and high capacity required to enable the digital transformation can be fulfilled only granting enough spectrum to meet different application scenarios. While high bands (≥ 15 GHz) and mm-wave can deliver ultra-Gbps capacity in urban and suburban areas thanks to wide channels (≥ 112 MHz), low bands (≤ 13 GHz) used in rural areas and on wireless backbones lack enough spectrum to allow channels higher than 56/80 MHz and require multi-channels aggregation. The band delivery statistics collected confirm that bands below 10 GHz still play an important role in modern communication networks: in developed countries there are still many areas where microwave is the only choice for delivering high capacity connection, while in developing countries lack of fibre requires long haul microwave links to deploy cross country ultra-Gbps backbones. Bands below 10 GHz represent about 20 % of past five years microwave deliveries worldwide with the highest shares in Africa and Americas (from 25 % to 33 %). With the exception of North America, 7 GHz and 8 GHz are the most used bands ranging from 70 % to 90 % shares. While L6 GHz and U6 GHz were traditionally used for high capacity long haul links, 7 GHz and 8 GHz are widely used also as last mile connections. Planning simulations done indicate that medium-long distance links cannot rely on other low bands (11 GHz and 13 GHz) not only to ensure the high reliability required by feeder link or aggregation backbones but also to meet the KPI of access links in high rainfall areas. The results are confirmed by link length statistics collected in different regions: Europe 50 km typical distance suggests long haul and feeder links as major application of these bands while average link distance of 20-30 km in Sub-Saharan Africa and USA fits with last mile scenarios. Data and feedbacks collected during the present document preparation confirm the need of keeping enough spectrum in bands below 10 GHz to meet capacity, distance and availability targets required by operators, utilities and enterprises to deliver broadband connectivity. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 31 Annex A: ECC Report 173 responding countries Table A.1: ECC Report 173 [i.8] responding countries Country 2018 2022 Countries considered for the trends Albania Yes Austria Yes Yes Yes Azerbaijan Yes Belgium Yes Bosnia and Herzegovina Yes Yes Yes Bulgaria Yes Yes Yes Croatia Yes Yes Yes Cyprus Yes Czech Republic Yes Yes Yes Estonia Yes Finland Yes Yes Yes France Yes Yes Yes Germany Yes Yes Yes Greece Yes Hungary Yes Yes Yes Ireland Yes Yes Yes Italy Yes Yes Yes Latvia Yes Yes Yes Malta Yes Yes Yes Moldova Yes Netherlands Yes Yes Yes Norway Yes Yes Yes Portugal Yes Romania Yes Yes Yes Russia Yes Serbia Yes Slovak Republic Yes Yes Yes Slovenia Yes Yes Yes Sweden Yes Yes Yes Switzerland Yes Yes Yes Türkiye Yes Yes Yes United Kingdom Yes Yes Yes Total 26 26 22 ETSI ETSI TR 104 142 V1.1.1 (2026-02) 32 Annex B: Country Split Table B.1: Vendor statistics country split ITU-R Region Country Spectrum Regional Association Aggregated Region Aggregated Macro Region Africa Angola ATU Sub-Saharan Africa Africa Africa Benin ATU Sub-Saharan Africa Africa Africa Botswana ATU Sub-Saharan Africa Africa Africa Burkina Faso ATU Sub-Saharan Africa Africa Africa Burundi ATU Sub-Saharan Africa Africa Africa Cape Verde ATU Sub-Saharan Africa Africa Africa Cameroon ATU Sub-Saharan Africa Africa Africa Central African Republic ATU Sub-Saharan Africa Africa Africa Chad ATU Sub-Saharan Africa Africa Africa Congo ATU Sub-Saharan Africa Africa Africa Côte d'Ivoire ATU Sub-Saharan Africa Africa Africa Democratic Republic of the Congo ATU Sub-Saharan Africa Africa Africa Equatorial Guinea ATU Sub-Saharan Africa Africa Africa Eritrea Sub-Saharan Africa Africa Africa Eswatini ATU Sub-Saharan Africa Africa Africa Ethiopia ATU Sub-Saharan Africa Africa Africa Gabon ATU Sub-Saharan Africa Africa Africa Gambia ATU Sub-Saharan Africa Africa Africa Ghana ATU Sub-Saharan Africa Africa Africa Guinea ATU Sub-Saharan Africa Africa Africa Guinea-Bissau ATU Sub-Saharan Africa Africa Africa Kenya ATU Sub-Saharan Africa Africa Africa Lesotho ATU Sub-Saharan Africa Africa Africa Liberia ATU Sub-Saharan Africa Africa Africa Madagascar ATU Sub-Saharan Africa Africa Africa Malawi ATU Sub-Saharan Africa Africa Africa Mali ATU Sub-Saharan Africa Africa Africa Mauritius ATU Sub-Saharan Africa Africa Africa Mozambique ATU Sub-Saharan Africa Africa Africa Namibia ATU Sub-Saharan Africa Africa Africa Niger ATU Sub-Saharan Africa Africa Africa Nigeria ATU Sub-Saharan Africa Africa Africa Rwanda ATU Sub-Saharan Africa Africa Africa Sao Tome and Principe ATU Sub-Saharan Africa Africa Africa Senegal ATU Sub-Saharan Africa Africa Africa Seychelles Sub-Saharan Africa Africa Africa Sierra Leone ATU Sub-Saharan Africa Africa Africa South Africa ATU Sub-Saharan Africa Africa Africa South Sudan ATU Sub-Saharan Africa Africa Africa Tanzania ATU Sub-Saharan Africa Africa Africa Togo ATU Sub-Saharan Africa Africa Africa Uganda ATU Sub-Saharan Africa Africa Africa Zambia ATU Sub-Saharan Africa Africa Africa Zimbabwe ATU Sub-Saharan Africa Africa ETSI ETSI TR 104 142 V1.1.1 (2026-02) 33 Table B.2 ITU-R Region Country Spectrum Regional Association Proposed Region Aggregated Macro Region Americas Antigua and Barbuda CITEL Latina America (LATAM) Americas Americas Argentina CITEL Latina America (LATAM) Americas Americas Bahamas CITEL Latina America (LATAM) Americas Americas Barbados CITEL Latina America (LATAM) Americas Americas Belize CITEL Latina America (LATAM) Americas Americas Bolivia CITEL Latina America (LATAM) Americas Americas Brazil CITEL Latina America (LATAM) Americas Americas Canada CITEL North America (NAM) Americas Americas Chile CITEL Latina America (LATAM) Americas Americas Colombia CITEL Latina America (LATAM) Americas Americas Costa Rica CITEL Latina America (LATAM) Americas Americas Cuba CITEL Latina America (LATAM) Americas Americas Dominica CITEL Latina America (LATAM) Americas Americas Dominican Republic CITEL Latina America (LATAM) Americas Americas Ecuador CITEL Latina America (LATAM) Americas Americas El Salvador CITEL Latina America (LATAM) Americas Americas Grenada CITEL Latina America (LATAM) Americas Americas Guatemala CITEL Latina America (LATAM) Americas Americas Guyana CITEL Latina America (LATAM) Americas Americas Haiti CITEL Latina America (LATAM) Americas Americas Honduras CITEL Latina America (LATAM) Americas Americas Jamaica CITEL Latina America (LATAM) Americas Americas Mexico CITEL Latina America (LATAM) Americas Americas Nicaragua CITEL Latina America (LATAM) Americas Americas Panama CITEL Latina America (LATAM) Americas Americas Paraguay CITEL Latina America (LATAM) Americas Americas Peru CITEL Latina America (LATAM) Americas Americas Saint Kitts and Nevis CITEL Latina America (LATAM) Americas Americas Saint Lucia CITEL Latina America (LATAM) Americas Americas Saint Vincent and the Grenadines CITEL Latina America (LATAM) Americas Americas Suriname CITEL Latina America (LATAM) Americas Americas Trinidad and Tobago CITEL Latina America (LATAM) Americas Americas United States of America CITEL North America (NAM) Americas Americas Uruguay CITEL Latina America (LATAM) Americas Americas Venezuela CITEL Latina America (LATAM) Americas ETSI ETSI TR 104 142 V1.1.1 (2026-02) 34 Table B.3 ITU-R Region Country Spectrum Regional Association Proposed Region Aggregated Macro Region Arab States Algeria ASMG/ATU North Africa Africa Arab States Comoros ASMG/ATU North Africa Africa Arab States Djibouti ASMG/ATU North Africa Africa Arab States Egypt ASMG/ATU North Africa Africa Arab States Libya ASMG/ATU North Africa Africa Arab States Mauritania ASMG/ATU North Africa Africa Arab States Morocco ASMG/ATU North Africa Africa Arab States Somalia ASMG/ATU North Africa Africa Arab States Sudan ASMG/ATU North Africa Africa Arab States Tunisia ASMG/ATU North Africa Africa Arab States Bahrain ASMG Middle East Arab States Arab States Iraq ASMG Middle East Arab States Arab States Jordan ASMG Middle East Arab States Arab States Kuwait ASMG Middle East Arab States Arab States Lebanon ASMG Middle East Arab States Arab States Oman ASMG Middle East Arab States Arab States Qatar ASMG Middle East Arab States Arab States Saudi Arabia ASMG Middle East Arab States Arab States Syria ASMG Middle East Arab States Arab States United Arab Emirates ASMG Middle East Arab States Arab States Yemen ASMG Middle East Arab States Table B.4 ITU-R Region Country Spectrum Regional Association Proposed Region Aggregated Macro Region Asia and Pacific Afghanistan APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Australia APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Bangladesh APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Bhutan APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Brunei APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Cambodia APT Asia Pacific Asia Pacific (APAC) Asia and Pacific China APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Democratic People's Republic of Korea APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Fiji APT Asia Pacific Asia Pacific (APAC) Asia and Pacific India APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Indonesia APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Iran APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Japan APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Kiribati APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Korea APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Laos APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Malaysia APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Maldives APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Marshall Islands APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Micronesia APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Mongolia APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Myanmar APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Nauru APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Nepal APT Asia Pacific Asia Pacific (APAC) Asia and Pacific New Zealand APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Pakistan APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Palau APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Papua New Guinea APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Philippines APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Samoa APT Asia Pacific Asia Pacific (APAC) ETSI ETSI TR 104 142 V1.1.1 (2026-02) 35 ITU-R Region Country Spectrum Regional Association Proposed Region Aggregated Macro Region Asia and Pacific Singapore APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Solomon Islands APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Sri Lanka APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Timor-Leste Asia Pacific Asia Pacific (APAC) Asia and Pacific Thailand APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Tonga APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Tuvalu APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Vanuatu APT Asia Pacific Asia Pacific (APAC) Asia and Pacific Vietnam APT Asia Pacific Asia Pacific (APAC) Table B.5 ITU-R Region Country Spectrum Regional Association Proposed Region Aggregated Macro Region Europe Albania CEPT Europe Europe Europe Andorra CEPT Europe Europe Europe Austria CEPT Europe Europe Europe Belgium CEPT Europe Europe Europe Bosnia and Herzegovina CEPT Europe Europe Europe Bulgaria CEPT Europe Europe Europe Croatia CEPT Europe Europe Europe Cyprus CEPT Europe Europe Europe Czech Republic CEPT Europe Europe Europe Denmark CEPT Europe Europe Europe Estonia CEPT Europe Europe Europe Finland CEPT Europe Europe Europe France CEPT Europe Europe Europe Georgia CEPT Europe Europe Europe Germany CEPT Europe Europe Europe Greece CEPT Europe Europe Europe Holy See CEPT Europe Europe Europe Hungary CEPT Europe Europe Europe Iceland CEPT Europe Europe Europe Ireland CEPT Europe Europe Europe Israel Europe Europe Europe Italy CEPT Europe Europe Europe Latvia CEPT Europe Europe Europe Liechtenstein CEPT Europe Europe Europe Lithuania CEPT Europe Europe Europe Luxembourg CEPT Europe Europe Europe Malta CEPT Europe Europe Europe Moldova CEPT Europe Europe Europe Monaco CEPT Europe Europe Europe Montenegro CEPT Europe Europe Europe Netherlands CEPT Europe Europe Europe North Macedonia CEPT Europe Europe Europe Norway CEPT Europe Europe Europe Poland CEPT Europe Europe Europe Portugal CEPT Europe Europe Europe Romania CEPT Europe Europe Europe San Marino CEPT Europe Europe Europe Serbia CEPT Europe Europe Europe Slovak Republic CEPT Europe Europe Europe Slovenia CEPT Europe Europe Europe Spain CEPT Europe Europe Europe Sweden CEPT Europe Europe Europe Switzerland CEPT Europe Europe Europe Türkiye CEPT Europe Europe Europe Ukraine CEPT Europe Europe ETSI ETSI TR 104 142 V1.1.1 (2026-02) 36 ITU-R Region Country Spectrum Regional Association Proposed Region Aggregated Macro Region Europe United Kingdom CEPT Europe Europe Table B.6 ITU-R Region Country Spectrum Regional Association Proposed Region Aggregated Macro Region Commonwealth of Independent States Armenia RCC Commonwealth of Independent States (CIS) Commonwealth of Independent States (CIS) Commonwealth of Independent States Azerbaijan RCC Commonwealth of Independent States (CIS) Commonwealth of Independent States (CIS) Commonwealth of Independent States Belarus RCC Commonwealth of Independent States (CIS) Commonwealth of Independent States (CIS) Commonwealth of Independent States Kazakhstan RCC Commonwealth of Independent States (CIS) Commonwealth of Independent States (CIS) Commonwealth of Independent States Kyrgyzstan RCC Commonwealth of Independent States (CIS) Commonwealth of Independent States (CIS) Commonwealth of Independent States Russian Federation RCC Commonwealth of Independent States (CIS) Commonwealth of Independent States (CIS) Commonwealth of Independent States Tajikistan RCC Commonwealth of Independent States (CIS) Commonwealth of Independent States (CIS) Commonwealth of Independent States Turkmenistan RCC Commonwealth of Independent States (CIS) Commonwealth of Independent States (CIS) Commonwealth of Independent States Uzbekistan RCC Commonwealth of Independent States (CIS) Commonwealth of Independent States (CIS) ETSI ETSI TR 104 142 V1.1.1 (2026-02) 37 Annex C: Change history Date Version Information about changes October 2024 V0.0.1 Draft Skeleton May 2025 V0.1.0 Stable Draft July 2025 V0.2.0 Final Draft August 2025 V0.2.2 Final Draft first revision September 2025 V0.2.3 Final Draft editorial revision November 2025 V0.2.4 Final Draft second editorial revision January 2026 V0.2.5 Final Draft third editorial revision ETSI ETSI TR 104 142 V1.1.1 (2026-02) 38 History Version Date Status V1.1.1 February 2026 Publication |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 1 Scope | The present document specifies a protocol for allowing an EUDI Wallet to request a Personal Identification Data (PID hereinafter) Provider, the issuance of a PID, and to request an Electronic Attestation of Attributes (EAA hereinafter) Provider, the issuance of EAA. The protocol specified builds on OpenID4VC-HAIP [1], which defines a profile of OpenID4VCI [2]. In addition to that, the protocol extends OpenID4VC-HAIP [1], for meeting requirements imposed by the EUDI Wallet ecosystem as specified in EUDI Wallet ARF [i.1], by EUDI Wallet TS03 [i.2], and by EAA formats, categories, and profiles specified in ETSI TS 119 472-1 [3]. More specifically, the present document defines requirements for: 1) Inclusion of the access certificates issued to PID/EAA Provider in the Issuer Metadata. 2) Inclusion of the registration certificates issued to PID/EAA Provider in the Issuer Metadata. 3) Inclusion of Embedded Disclosure Policy details in the Issuer Metadata. 4) Inclusion of details on the PID/EAA Provider preferences on the method to limit the number of times that a PID/EAA may be presented, in the Issuer Metadata. 5) Sending the Wallet Instance Attestation (WIA hereinafter) to the Pushed Authorisation Endpoint, and the Token Endpoint. 6) Sending the Wallet Unit Attestation (WUA hereinafter) to the Credential Endpoint. 7) Proofing possession of the private key associated to the public key in the WUA. 8) Proofing possession of the private key(s) associated to the public key(s) to be bound to the PID/EAA(s) to be issued. 9) Proofing that the same WSCA/WSCD possesses the private key associated to the public key in the WUA and the private key(s) associated to the public key(s) to be bound to the PID/EAA(s) to be issued. 10) Sending the details of the format(s) of the PID/EAA requested to the Authorisation Endpoint, and the Credential Endpoint. 11) Issuance of EAA in formats that are not covered by OpenID4VCI [2], as EAA built on X.509 Attribute certificates, for instance (X509-AC EAA specified in clause 8 of ETSI TS 119 472-1[3]). 12) Claims path for X509-AC EAA format, not covered by OpenID4VCI [2]. NOTE: Some of the specifications used by the present document are not yet final. Should breaking changes occur in some of the mentioned drafts, they should not be taken into account unless a new version of the present document is generated referencing the updated drafts or final versions. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 7 |
1806d1da064da1cf756176d3a87e14f9 | 119 472-3 | 2 References | |
1806d1da064da1cf756176d3a87e14f9 | 119 472-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 referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] OpenID4VC-HAIP (24 December 2025): "OpenID4VC High Assurance Interoperability Profile 1.0". [2] OpenID4VCI (16 September 2025): "OpenID for Verifiable Credential Issuance 1.0". [3] ETSI TS 119 472-1: "Electronic Signatures and Trust Infrastructures (ESI); Profiles for Electronic Attestation of Attributes; Part 1: General requirements". [4] ETSI TS 119 475: "Electronic Signatures and Trust Infrastructures (ESI); Relying party attributes supporting EUDI Wallet user's authorization decisions". [5] IETF draft-ietf-oauth-attestation-based-client-auth-07 (September 2025): "OAuth 2.0 Attestation- Based Client Authentication". [6] IETF RFC 4514 (June 2006): "Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names". [7] IETF RFC 4648 (October 2006): "The Base16, Base32, and Base64 Data Encodings". [8] IETF RFC 7515 (May 2015): "JSON Web Signature (JWS)". [9] OpenID4 VP (9 July 2025): "OpenID for Verifiable Presentations 1.0". [10] NIST SP 800.38D (November 2007): "Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC". [11] W3C® Recommendation 15 May 2025: "Securing Verifiable Credentials using JOSE and COSE". |
1806d1da064da1cf756176d3a87e14f9 | 119 472-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 referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] EUDI Wallet ARF: "Architecture and Reference Framework version 2.4.0". [i.2] EUDI Wallet TS03: "Specification of Wallet Unit Attestations (WUA) used in issuance of PID and Attestations". ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 8 [i.3] Commission Implementing Regulation (EU) 2024/2979 of 28 November 2024 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the integrity and core functionalities of European Digital Identity Wallets. [i.4] EUDI Wallet TS05: "Specification of common formats and API for Relying Party Registration information". [i.5] ETSI TS 119 471: "Electronic Signatures and Trust Infrastructures (ESI); Policy and Security requirements for Providers of Electronic Attestation of Attributes Services". [i.6] IETF RFC 7519 (May 2015): "JSON Web Token (JWT)". [i.7] ETSI TS 119 472-2: "Electronic Signatures and Trust Infrastructures (ESI); Profiles for Electronic Attestation of Attributes; Part 2: Profiles for EAA/PID Presentations to Relying Party". |
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 Digital Identity Wallets Wallet Instance Attestation (WIA): JWT signed by the Wallet Provider that attests the integrity of the app NOTE 1: Based on clause 2 of EUDI Wallet TS03 [i.2]. NOTE 2: The WIA allows PID/EAA Providers to protect their endpoints by only communicating with Wallet Applications which integrity are ensured by the Wallet Providers. NOTE 3: The contents of the WIA are as specified in EUDI Wallet TS03 [i.2]. NOTE 4: JWT is specified in IETF RFC 7519 [i.6]. Wallet Unit Attestation (WUA): JWT signed by the Wallet Provider that describes the components of the Wallet Unit or allows authentication and validation of those components NOTE 1: The WUA allows PID/EAA Providers to ensure that they only issue PID/EAA that are cryptographically bound to keys that are properly protected (i.e. in a WSCD with sufficiently high attack resistance), as well as to revoke their credentials in case a Wallet Provider revokes a Wallet Unit (EUDI Wallet TS03 [i.2]). NOTE 2: The contents of the WUA are as specified in EUDI Wallet TS03 [i.2]. |
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 119 472-3 V1.1.1 (2026-03) 9 PID Personal Identification Data PID/EAA Provider PID or EAA Provider X509-AC X.509 Attribute Certificate WIA Wallet Instance Attestation WSCA Wallet Secure Cryptographic Application WSCD Wallet Secure Cryptographic Device WU Wallet Unit WUA Wallet Unit Attestation |
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 clause the number will start in 01 and it will increase in one unity for each requirement. The following topic identifiers are used: 1) GEN-REQ for general requirements on the issuance flows. 2) ISS-MDATA for general requirements on Issuer Metadata. 3) ISS-MDATA-ACC_CERT for requirements on provision of access certificates in Issuer Metadata. 4) ISS-MDATA-REG_CERT for requirements on provision of registration certificates in Issuer Metadata. 5) ISS-MDATA-EAA-REUSE-POL for requirements for PID/EAA reuse policy. 6) ISS-MDATA-EBD for requirements on provision of Embedded Disclosure Policies. 7) ISS-CRED-OFFER for requirements on the Credential Offer. 8) AUTH-REQ for requirements on the Pushed Authorisation Request. 9) AUTH-REQ-PROC for requirements on processing of the Pushed Authorisation Request. 10) TOKEN-REQ for requirements on the Token Request. 11) TOKEN-REQ-PROC for requirements on processing of the Token Request. 12) CRED-REQ for requirements on the Credential Request. 13) CRED-REQ-PROC for requirements on processing of the Credential Request. 14) CRED-RESP for requirements on Credential Response. 15) NOT-REQ for requirements on Notification Request. 16) CRYPTO for requirements on crypto suites. 17) SEC for security considerations. 18) ISS-MDATA-X509-AC EAA for requirements on paths for identifying attributes in X509-AC EAAs in Issuer Metadata. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 10 |
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 issuing PIDs and EAAs into the EUDI Wallet, they shall implement the protocol defined in OpenID4VCI [2], specified by the requirements defined for the Issuer in OpenID4VC-HAIP [1], clause 4 and its subclauses, unless specified otherwise in the present document. GEN-REQ-4.1-03: The EUDI Wallet shall support the following flows: the Authorisation Code Flow as specified in clause 3.4 of OpenID4VCI [2], and the Pre-Authorised Code Flow as specified in clause 3.5 of OpenID4VCI [2]. GEN-REQ-4.1-04: PID/EAA Providers implementing the protocol defined in clause 4 and its subclauses of the present document, shall implement at least one of the following flows: the Authorisation Code Flow as specified in clause 3.4 of OpenID4VCI [2], or the Pre-Authorised Code Flow as specified in clause 3.5 of OpenID4VCI [2]. GEN-REQ-4.1-05: PID Providers implementing the Pre-Authorised Code Flow shall perform user authorisation with the physical presence. NOTE: As described in OpenID4VCI [2], Pre-Authorised Code Flow does not provide sufficient security against hijacking attacks for remote scenarios and therefore online issuance requiring user authentication with Level of Assurance HIGH is discarded for the Pre-Authorised Code Flow. GEN-REQ-4.1-06: The custom URL scheme "eu-eaa-offer://" shall be used to invoke the EUDI Wallet. 4.2 Requirements for Issuer Metadata (PID/EAA Provider Metadata) |
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 Provider. ISS-MDATA-4.2.1-03: The set of possible values for the format parameter of credential_configurations_supported parameter of the Issuer Metadata shall include one or more of the values defined for the Credential Format Identifier in Annex A of OpenID4VCI [2]. |
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 PID/EAA Provider, which shall also be the signing certificate. ISS-MDATA-ACC_CERT-4.2.2-03: The x5c header parameter should contain the base64 (IETF RFC 4648 [7]) encoding of the DER-encoded certificates in the signing certificate's path until the trust anchor, but excluding it. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 11 4.2.3 Provision of registration certificates of PID/EAA Provider to EUDI Wallet ISS-MDATA-REG_CERT-4.2.3-01: The Issuer Metadata shall contain the issuer_info metadata parameter. ISS-MDATA-REG_CERT-4.2.3-02: The issuer_info parameter shall be placed at the top level of the Signed JWT payload used for retrieving the Issuer Metadata. ISS-MDATA-REG_CERT-4.2.3-03: The issuer_info parameter shall have the same structure as the verifier_info parameter specified in clause 5.1 of OpenID4 VP [9]. ISS-MDATA-REG_CERT-4.2.3-04: One of the elements in the issuer_info array parameter may contain the PID/EAA Provider's registration certificate. ISS-MDATA-REG_CERT-4.2.3-05: The value of the format member of the element in the issuer_info array parameter that contains the PID/EAA Provider's registration certificate shall be "registration_cert". NOTE 1: This value of the format member of the element identifies this element as the container of the PID/EAA Provider's registration certificate. ISS-MDATA-REG_CERT-4.2.3-06: The value of the data member of the element in the issuer_info array parameter that contains the PID/EAA Provider's registration certificate shall be the registration certificate of the PID/EAA Provider. ISS-MDATA-REG_CERT-4.2.3-07: One of the elements of issuer_info shall contain the PID/EAA Provider's registration information provided by the PID/EAA Provider's Registrar. ISS-MDATA-REG_CERT-4.2.3-08: The value of the format member of the element in the issuer_info array parameter that contains the PID/EAA Provider's registration information shall be "registrar_dataset". NOTE 2: This value of the format member of the element identifies this element as the container of the PID/EAA Provider's registration information provided by the PID/EAA Provider's Registrar. ISS-MDATA-REG_CERT-4.2.3-09: The value of the data member of the element in the issuer_info array parameter that contains the PID/EAA Provider's registration information shall be a non-empty JSON Object. The data member of the element in the issuer_info array parameter that contains the PID/EAA Provider's registration information: • ISS-MDATA-REG_CERT-4.2.3-10: Shall contain the identifier member specified in clause B.2.2 of ETSI TS 119 475 [4], whose value shall be the PID/EAA Provider's identifier. • ISS-MDATA-REG_CERT-4.2.3-11: Shall contain the srvDescription member specified in clause B.2.2 of ETSI TS 119 475 [4], which shall be an array of JSON MultiLangString objects (defined in clause B.2.6 of ETSI TS 119 475 [4]), whose contents shall be registered user-friendly descriptions of the PID/EAA Provider's service. • ISS-MDATA-REG_CERT-4.2.3-12: Shall contain the registryURI member specified in clause B.2.1 of ETSI TS 119 475 [4], whose value shall be the URI of the PID/EAA Provider's Registrar. • ISS-MDATA-REG_CERT-4.2.3-13: Shall contain the providesAttestations member, which contains information of the attestation types that the PID/EAA Provider intends to issue for Wallet Units. NOTE 3: For avoidance of confusion on issuance intentions, this element is typically expected to contain same attestation or attestations, or a superset of the attestation types that are communicated to the Wallet Unit in the related Credential Offer message of OpenID4VCI and its credential_configuration_ids parameter, if/as a credential offer is used as part of the issuance flow (issuance can also be executed without an offer phase, if desired attestation type is known e.g. out-of-band). The providesAttestations tells the Wallet Unit what credentials the issuer is registered for in its national Registrar and can thus always be used for verification of the issuer's registered attestation types, whereas the credential_configuration_ids in Credential Issuer Metadata tells the Wallet Unit what credentials are under active offer by the issuer for a given use case. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 12 NOTE 4: See clause 2.1 of EUDI Wallet TS05 [i.4] for the specifications of providesAttestations member. NOTE 5: This information is required by the Wallet Unit to be able to verify the PID/EAA Provider's registration information upon issuance and present this information to the User. Note that in case the PID/EAA Provider uses the services of an intermediary, the identifier of requirement ISS-MDATA- REG_CERT-4.2.3-10 will be different from the identifier of the intermediary as included in the intermediary's access certificate. |
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 may contain the parameter credential_reuse_policy, with the details on the preferences of the PID/EAA Provider on the policy that it shall use to limit the number of times that a Wallet Unit may present the PID/EAA. ISS-MDATA-EAA-REUSE-POL-4.2.4.1-02: Absence of the credential_reuse_policy parameter shall be understood as that the PID/EAA Provider does not limit the number of times that a Wallet Unit may present the PID/EAA. ISS-MDATA-EAA-REUSE-POL-4.2.4.1-03: The credential_reuse_policy parameter shall be a JSON Object. ISS-MDATA-EAA-REUSE-POL-4.2.4.1-04: The credential_reuse_policy parameter shall have the id member, identifying the PID/EAA reuse policy. ISS-MDATA-EAA-REUSE-POL-4.2.4.1-05: The id member shall be a JSON string. ISS-MDATA-EAA-REUSE-POL-4.2.4.1-06: The credential_reuse_policy parameter may have the options member for providing specific details of the reuse policy identified by the id member. ISS-MDATA-EAA-REUSE-POL-4.2.4.1-07: The options member shall be a JSON Array of objects, whose contents shall depend on the specific reuse policy. ISS-MDATA-EAA-REUSE-POL-4.2.4.1-08: If the id member has the value "arf_annex_ii" then the PID/EAA reuse policy shall be as specified in clause 4.2.4.2 of the present document. |
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 present. ISS-MDATA-EAA-REUSE-POL-4.2.4.2-02: If the id member has the value "arf_annex_ii" the element within the options member shall contain the member of label "details" mapped to an array of strings. ISS-MDATA-EAA-REUSE-POL-4.2.4.2-03: If the id member has the value "arf_annex_ii" the array mapped to the label "details" shall contain either "once_only" or "limited_time". ISS-MDATA-EAA-REUSE-POL-4.2.4.2-04: If the id member has the value "arf_annex_ii" the array mapped to the label "details" may contain either "rotating-batch" or "per-relying-party", or both of them. NOTE 2: The "once_only" value is used to indicate that the Wallet Unit meets the requirements ISSU_43 to ISSU_47 of Annex 2 of EUDI Wallet ARF [i.1]. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 13 NOTE 3: The "limited-time" value is used to indicate that the Wallet Unit meets the requirements ISSU_48 to ISSU_50 of Annex 2 of EUDI Wallet ARF [i.1]. NOTE 4: The "rotating-batch" value is used to indicate that the Wallet Unit meets the requirements ISSU_51 to ISSU_54 of Annex 2 of EUDI Wallet ARF [i.1]. NOTE 5: The "per-relying-party" value is used to indicate that the Wallet Unit meets the requirements ISSU_55 to ISSU_57 of Annex 2 of EUDI Wallet ARF [i.1]. ISS-MDATA-EAA-REUSE-POL-4.2.4.2-05: If the id member has the value "arf_annex_ii" and the array mapped to the label "details" contains only one element, the Wallet Unit shall behave as specified by the string contained in this element. NOTE 6: In this case the value of the element is as specified by requirement ISS-MDATA-EAA-REUSE- POL-4.2.4.2-05 in the present clause. ISS-MDATA-EAA-REUSE-POL-4.2.4.2-06: If the id member has the value "arf_annex_ii" and the array mapped to the label "details" contains more than one string, the Wallet Unit should follow the method whose string first appears in the mentioned array and the Wallet Unit supports. EXAMPLE 1: If the array mapped to the label "details" contains ["per-relying-party", "rotating-batch", "once_only"], and the Wallet Unit supports "rotating-batch" and "once_only" then the Wallet Unit would use method "rotating-batch". ISS-MDATA-EAA-REUSE-POL-4.2.4.2-07: If the id member has the value "arf_annex_ii" and the array mapped to the label "details" contains any of the following values: "once_only", "rotating-batch", or "per-relying-party", then the JSON Object that contains this array mapped to the label "details" shall also contain a JSON number mapped to the label "batch_size". ISS-MDATA-EAA-REUSE-POL-4.2.4.2-08: The JSON number mapped to the label "batch_size" shall specify the maximum array size for the proofs parameter in a Credential Request and shall be 2 or greater. ISS-MDATA-EAA-REUSE-POL-4.2.4.2-09: If the id member has the value "arf_annex_ii" and the array mapped to the label "details" contains the value "once_only", then the JSON Object that contains this array mapped to the label "details" shall also contain a JSON number mapped to the label "reissue_trigger_unused". ISS-MDATA-EAA-REUSE-POL-4.2.4.2-10: The JSON number mapped to the label "reissue_trigger_unused" shall specify the lower limit for the number of unused PIDs/EAAs held by the Wallet Unit. ISS-MDATA-EAA-REUSE-POL-4.2.4.2-11: The JSON number mapped to the label "reissue_trigger_unused" shall be lower than the value of the JSON Number mapped to the label "batch_size". NOTE 7: According to Annex 2 of EUDI Wallet ARF [i.1], once the Wallet Unit reaches this lower limit, it requests the issuance of a new batch of PIDs/EAAs. ISS-MDATA-EAA-REUSE-POL-4.2.4.2-12: If the id member has the value "arf_annex_ii" and the array mapped to the label "details" contains any of the following values: "limited-time", "rotating-batch", or "per-relying-party", then the JSON Object that contains this array mapped to the label "details" shall also contain a JSON number mapped to the label "reissue_trigger_lifetime_left". ISS-MDATA-EAA-REUSE-POL-4.2.4.2-13: The JSON number mapped to the label "reissue_trigger_lifetime_left" shall specify the number of seconds before the expiration of the PID/EAA. NOTE 8: According to Annex 2 of EUDI Wallet ARF [i.1], once the instant indicated by the mentioned number of seconds before the expiration of the PID/EAA arrives, the Wallet Unit requests a new issuance of a new PID/EAA. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 14 EXAMPLE 2: Below follows a non-normative example for the type "once_only". { "credential_reuse_policy" : { "id": "arf_annex_ii", "options": [ { "details": ["once_only"], "batch_size": 10, "reissue_trigger_unused": 2 } ] } } EXAMPLE 3: Below follows a non-normative example for the type "limited-time". { "credential_reuse_policy" : { "id": "arf_annex_ii", "options": [ { "details": ["limited-time"], "reissue_trigger_lifetime_left": 86400 } ] } } EXAMPLE 4: Below follows a non-normative example for the type "rotating-batch". { "credential_reuse_policy" : { "id": "arf_annex_ii", "options": [ { "details": [rotating-batch"], "batch_size": 50, "reissue_trigger_lifetime_left": 86400 } ] } } EXAMPLE 5: Below follows a non-normative example for the type "per-relying-party". { "credential_reuse_policy" : { "id": "arf_annex_ii", "options": [ { "details": ["per-relying-party"], "batch_size": 10, "reissue_trigger_lifetime_left": 86400 } ] } } ISS-MDATA-EAA-REUSE-POL-4.2.4.2-14: If both the batch_credential_issuance (specified in OpenID4VCI [2]) and the credential_reuse_policy are present, then the batch_credential_issuance shall be ignored. |
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 [i.3] it is required that: 1) Wallet providers ensure that electronic attestations of attributes with common embedded disclosure policies set out in Annex III of [i.3] can be processed by the wallet units that they provide. 2) Wallet instances are able to process and present such embedded disclosure policies referred to in paragraph 1 (above) in conjunction with data received from the requesting wallet-relying party. 3) Wallet instances verify whether the wallet-relying party complies with the requirements of the embedded disclosure policy and inform the wallet user of the result. An embedded disclosure policy is meta data associated with an EAA when issued to a wallet holder either by including the content of the policy itself or by retrieving the policy from a pre-loaded policy definition. The embedded disclosure policy is applied by wallet to control the disclosure of an EAA including selective disclosure of attributes within an EAA. This policy may be loaded into a wallet using the EAA issuer protocol as specified in the present document. The embedded disclosure policy is not revealed to the relying party through the relying party presentation protocol as specified in ETSI TS 119 472-2 [i.7]. NOTE: The EAA rule book informs the relying part of any access restrictions in place. When accessing a particular EAA it is expected that the relying party takes this into account. Any further access control policy management controls are outside the scope of the present document. |
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 provider shall either include the Embedded Disclosure Policy identifier with the data set for the Embedded Disclosure Policy or just provide the identifier if the policy data set has already been pre-loaded into the Wallet Unit. ISS-MDATA-EBD-4.2.5.2-04: The Embedded Disclosure Policy may include a description of the applicability of an embedded disclosure to a particular community and/or class of application with common security requirements. ISS-MDATA-EBD-4.2.5.2-05: The Embedded Disclosure Policy may include an identifier of the authority responsible for the policy. ISS-MDATA-EBD-4.2.5.2-06: The Embedded Disclosure Policy may indicate that no policy restrictions apply for the associated EAA. ISS-MDATA-EBD-4.2.5.2-07: The Embedded Disclosure Policy may contain a list of authorised relying parties for the associated EAA: a) as identified by their subject distinguished name as held in the wallet-relying party access certificate in the form of LDAP string as specified in IETF RFC 4514 [6]; and/or NOTE 1: The LDAP representation of the LDAP string represents those elements of the identification attributes as listed in ETSI TS 119 475 [4], clauses 5.1.2 and 5.1.4 that are in the X.509 subject distinguished name as required to distinguish a specific relying party. For legal person this is commonName, organizationName, organizationIdentifier, countryName. For natural person this is commonName, givenName, surname, serialNumber, countryName. NOTE 2: organizationIdentifier attribute type is represented by the LDAP string "ORGID". serialNumber attribute type is represented by the LDAP string "SN". b) as indicated by the URI encoded entitlements required of relying parties as specified in ETSI TS 119 475 [4], and held in the wallet relying party registration certificate. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 16 NOTE 3: Other equivalent forms of URI encoded authorisations can be provided in the wallet-relying party access certificate but this may be ignored by the Wallet Unit. ISS-MDATA-EBD-4.2.5.2-08: The Embedded Disclosure Policy may define a specific list of roots of trust, to indicate that EUDI Wallet users should only disclose specific EAAs to Relying Parties in possession of access certificates derived from one of these roots or intermediate certificates. ISS-MDATA-EBD-4.2.5.2-09: Each element of the list of roots of trust, as specified in ISS-MDATA-EBD-4.2.5.2-08 above, shall include the issuer's distinguished name in the form of LDAP string as specified in IETF RFC 4514 [6] and the issuer's certificate serial number. ISS-MDATA-EBD-4.2.5.2-10: Other information may be included in an Embedded Disclosure Policy Extension which may be ignored by the wallet. ISS-MDATA-EBD-4.2.5.2-11: Wallet Units should still be able to cope with extensions being present even if they are ignored. ISS-MDATA-EBD-4.2.5.2-12: An Embedded Disclosure Policy Extension may be defined which contains alternative policy rules (no policy as in ISS-MDATA-EBD-4.2.5.2-05, authorised relying party only as in ISS-MDATA- EBD-4.2.5.2-06 or specific roots of trust as in ISS-MDATA-EBD-4.2.5.2-07) to be applied to specified attributes within the EAA which are allowed to be disclosed using selective disclosure. ISS-MDATA-EBD-4.2.5.2-13: The Embedded Disclosure Policy should contain a link to a website of the Attestation Provider explaining the disclosure policy in layman's terms for display by the Wallet Unit to the User and to allow the User to navigate to the website. |
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 of EUDI Wallet TS03 [i.2]. AUTH-REQ-4.4.2-02: The Pushed Authorisation Request shall include a Proof-of-Possession of the public key included within the cnf claim, as specified in Appendix E of OpenID4VCI [2], and IETF draft-ietf-oauth-attestation- based-client-auth-07 [5]. NOTE 2: According to EUDI Wallet TS03 [i.2], WIAs are expected to have a time-to-live of less than 24 hours; i.e. the difference between expiration time and the time of issuance is expected to be less than 24 hours. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 17 |
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. AUTH-REQ-PROC-4.4.3-03: When a PID/EAA Provider receives a WIA with a Proof-of-Possession, then it shall check that the signature of the Proof-of-Possession verifies under the public key present in the cnf claim of the WIA. |
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 TS03 [i.2]. TOKEN-REQ-4.5.1-02: The Token Request shall include a Proof-of-Possession of the public key included within the cnf claim, as specified in Appendix E of OpenID4VCI [2], and IETF draft-ietf-oauth-attestation-based-client-auth-07 [5]. |
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 expired. TOKEN-REQ-PROC-4.5.2-03: When a PID/EAA Provider receives a WIA with a Proof-of-Possession, then it shall check that the signature of the Proof-of-Possession verifies under the public key present in the cnf claim of the WIA. TOKEN-REQ-PROC-4.5.2-04: Refresh tokens for credential refresh may be supported. NOTE: When PID/EAA Providers choose to issue refresh tokens that can be used to generate new credentials, they need to carefully assess the associated security implications. This assessment is expected to consider factors such as the type of credentials being issued and the sensitivity of the attributes within. Providers also need to take into account that they cannot make assumptions about how or where the EUDI Wallet stores the refresh tokens. |
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 private key(s) corresponding to public key(s) that the PID/EAA will be bound to in the Credential Request. NOTE 2: Using proofs->attestation, the WU sends attestation(s) of public key(s) that the PID/EAA will be bound to in the Credential Request, without proof of possession of the corresponding private key(s). ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 18 |
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 key_attestation parameter in the Protected Header. CRED-REQ-4.6.1.2-04: The key_attestation parameter of the element in the jwt array member shall be the WUA, signed by the Wallet Provider. CRED-REQ-4.6.1.2-05: The WUA shall be a key attestation in JWT format as specified in clause D.1 of OpenID4VCI [2]. NOTE 1: The contents of the WUA are specified in section 2.3.4 of EUDI Wallet TS03 [i.2]. CRED-REQ-4.6.1.2-06: The attested_keys claim in the key_attestation parameter of the element in the jwt array, shall contain one or more public keys owned by the WU. CRED-REQ-4.6.1.2-07: The element in the jwt array member shall be signed by the Wallet Unit using the private key corresponding to the public key present in the first element of the attested_keys claim in the key_attestation parameter (the WUA). NOTE 2: Taken from the method of transport for the WUA in EUDI Wallet TS03 [i.2]. NOTE 3: Meeting the former requirements, the WU proves possession of the private key corresponding to the first public key in the attested_keys array claim in the WUA, attested by the Walled Provider. |
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 shall be the WUA. NOTE: The element in the attestation array member does not prove possession of the private keys corresponding to the attested public keys. |
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 that the signature of the element of the jwt array member verifies under the public key contained in the first position of the attested_keys array within the key_attestation parameter. CRED-REQ-PROC-4.6.2.1-03: The PID/EAA Provider shall verify that the element of the jwt array member includes the nonce claim in its JWT Body with a valid nonce value from its Nonce endpoint. CRED-REQ-PROC-4.6.2.1-04: The PID/EAA Provider shall generate as many PIDs/EAAs as elements present in the attested_keys array within the key_attestation parameter. CRED-REQ-PROC-4.6.2.1-05: Each PID/EAA shall be bound to one of the public keys present in the attested_keys array within the key_attestation parameter. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 19 CRED-REQ-PROC-4.6.2.1-06: There shall not be two PIDs/EAAs bound to the same public key. |
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 elements present in the attested_keys array within the element of the attestation array member. CRED-REQ-PROC-4.6.2.2-03: Each PID/EAA shall be bound to one of the public keys present in the attested_keys array within the element of the attestation array member. CRED-REQ-PROC-4.6.2.2-04: There shall not be two PIDs/EAAs bound to the same public key. |
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 requirements for issuing X509-AC EAAs, which have been specified in clause 8 of ETSI TS 119 472-1 [3]. A.2 Requirements for Issuer Metadata ISS-MDATA-A.2-01: If the PID/EAA Provider is able to issue X509-AC EAAs, then the set of possible values for the format parameter of credential_configurations_supported parameter of the Issuer Metadata shall include the value "x509_attr", which shall be used for identifying a X509-AC EAA as specified in ETSI TS 119 472-1 [3]. A.3 Rules for path in Issuer Metadata for X509-AC EAAs The present annex specifies rules for building paths for identifying attributes in X509-AC EAAs in Issuer Metadata. ISS-MDATA-X509-AC EAA-A-01: For X509-AC EAAs, the attributes in the EAA shall be identified by the path member within the claims member of the credential_metadata member. ISS-MDATA-X509-AC EAA-A-02: The path member shall be an array of 2 or 3 strings, where: 1) The first one shall identify the type of EAA. 2) The second one shall contain the OID of the attribute, represented as a sequence of integer numbers separated by the '.' character. 3) The third one, if present, shall contain the name of the attribute. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 21 Annex B (normative): Requirements for issuance of JSON-LD W3C-VC EAAs secured with enveloping proofs B.1 Introduction The present annex defines specific requirements for issuing JSON-LD W3C-VC EAA secured with enveloping proofs, which have been specified in clauses 3.1.1 and 3.2.1 of W3C VC_JOSE_COSE [11], and further profiled in clause 7 of ETSI TS 119 472-1 [3]. B.2 Requirements for Issuer Metadata ISS-MDATA-B.2-01: If the PID/EAA Provider is able to issue JSON-LD W3C VC JOSE EAAs, defined in clause 3.1.1 of W3C VC_JOSE_COSE [11] and further profiled in ETSI TS 119 472-1 [3], then the set of possible values for the format parameter of credential_configurations_supported parameter of the Issuer Metadata shall include the value "vc+jwt". NOTE 1: For more details on the specific profiles, see clause 7.6.4.2 of ETSI TS 119 472-1 [3]. ISS-MDATA-B.2-02: If the PID/EAA Provider is able to issue JSON-LD W3C VC SD-JWT EAAs, defined in clause 3.2.1 of W3C VC_JOSE_COSE [11] and further profiled in ETSI TS 119 472-1 [3], then the set of possible values for the format parameter of credential_configurations_supported parameter of the Issuer Metadata shall include the value "vc+sd-jwt". NOTE 2: For more details on the specific profiles, see clause 7.6.4.3 of ETSI TS 119 472-1 [3]. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 22 Annex C (informative): Change history Date Version Information about changes 8/9/2025 V0.0.1 First complete version 6/10/2025 V0.0.2 Submission of WIA and WUA to their respective Endpoints redefined. 17/10/2025 V0.0.3 Dispositions to comments raised to v0.0.2 implemented. Among others: - Registration certificate in issuer_info (same structure as verifier_info in OpenID4 VP) - Rework of transport of WIA for better alignment to TS-03 - Rework of transport of WUA - Allowing of pre-Authorised code flow - Requirement for refresh tokens: may instead should of HAIP 30/10/2025 V0.0.4 Last agreements reached implemented. Among others: - Two proofs methods: jwt and attestation. - proofs->jwt: first element WUA. Other elements signed with private keys corresponding to public keys in WUA. - New structure for supporting PID/EAA reuse. Profile of this structure for policy specified in Annex II of ARF. - Ephemeral WIA dropped from Authorisation End point and Token End point. - Dropped credential_format_id. - Dropped clause on requirements on EDP in Credential Response 3/11/2025 V0.0.5 Implemented editorial changes as a result of comments by Technical Officer to v0.0.4 25/11/2025 V0.0.6 Implemented dispositions to comments arrived from BDR, IDNow, CHTL, and EC. 10/12/2025 V0.0.7 Implemented some missing agreements with EC (comments arrived in two rounds and the agreements for the comments in the second round were not included in v0-0.6): - Do not restrict user authorisation in pre-authorised code flow to physical presence. The comment said: "Note that OpenId4VCI allows the use of OTP (one-time-password) in case of Pre-Authorised Code flow, delivered via a separate channel, to further protect such scenarios. It was agreed to also allow authentication with a Level of Assurance HIGH. - Drop the mandatory requirement that the PoP of WIA has the challenge parameter: this is not a mandatory requirement in TS3. According to TS3 "it's up to the Credential Issuer to require challenge by providing a challenge end point or not. Implemented agreements reached in adhoc call of 9/12/2025 on comments by Idakto. 1) Drop former GEN-REQ-4.1-06 (duplication of OIDF4VCI). 2) Reworded ISS-MDATA-4.2.1-03 as detailed in the dispositions of comments. 3) Reworded ISS-MDATA-REG_CERT-4.2.3-02 for clarifying where the issuer_info element is placed when the Issuer Metadata is transferred using a signed JWT. 4) ISS-MDATA-REG_CERT-4.2.3-08: reworded, and a new ISS-MDATA- REG_CERT-4.2.3-09 is added so that the issuer_info either contains the PID/EAA Provider's registration certificate or an element containing the PID PID/EAA Provider's registration information. 5) Added definition of PID/EAA Provider's Registrar in clause 3.1. 6) Replace the old ISS-MDATA-REG_CERT-4.2.3-15 (ISS-MDATA-REG_CERT- 4.2.3-16 in v0.0.7 because the insertion of a new requirement as detailed in bullet 4 above) by a requirement that requires the presence of providesAttestations member as specified in EUDIW TS05. 7) Dropped allow element in credential_reuse_policy element. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 23 Date Version Information about changes 15/12/2025 V0.0.8 a) Implemented agreement that there is only ONE element in jwt array, which contains the WUA in the credential request. This agreement was not implemented in v0.0.7 by mistake. This has implied deletion of the clause specifying elements of jwt array different than the first one, and also deletion of the clause specifying the processing of such elements. b) Implemented a fix for a last-moment gap identified by EC team in a message received on 11/12/2025. The gap affected PID/EAA reuse policy as specified in Annex 2 of ARF (clause 4.2.4.2 of the present document), and was as follows: 1) When the policy is "once_only" an indication is needed of, a lower limit for the number of unused PIDs/EAAs held by the WU, because once reached this limit, the WU requests the issuance of a new batch of PIDs/EAAs. This indication is a JSON Number mapped to the label "reissue_trigger_unused". 2) When the policy is "limited-time", "rotating-batch", or "per-relying-party", then an indication is needed of the number of seconds before the expiration of the PID/EAA because, once arrived this moment, the WU requests the issuance of a new PID/EAA. c) Reverted an agreement reached at the ad hoc call, because of a review of ARF annex 2. The agreement was that the issuer_info in the Issuer Metadata would contain EITHER the Registration Certificate OR the registration information from the Registrar. EC team claims that after a new reading of the HLRs of ARF Annex 2, the Registration information has to be always present regardless the presence of a Registration Certificate. d) Fixing two editorial issues: wrong numbering of notes in clause 4.2.3, and fixing the wording of Note 2 in clause 4.2.5.2. 16/12/2025 V0.0.9 Added requirement that "the data member of the element in the issuer_info array parameter that contains the PID/EAA Provider's registration information shall contain the entitlement member, which contains the entitlements of the RP" in clause 4.2.3 17/12/2025 V0.0.10 Implemented the following changes due to the agreements reached at ESI#88 plenary: 1) Remove the option of perform user authorisation on-line with authentication with LoA HIGH in the Pre-Authorised Code flow (Requirement GEN-REQ-4.1- 05), and add a note on this. 2) Remove the entitlement member in issuer_info element's data member. 3) Remove the trade_name member in issuer_info element's data member 17/12/2025 V0.0.11 NOTE on Pre-Authorised Code Flow reworded to highlight hijacking risk of online authorisations. All the references to Annex 2 of EUDI Wallet ARF [i.1] have been moved to NOTES (as it is an informative reference). 15/1/2026 V0.0.12 Implemented dispositions for all the comments reached to v0.0.11 during the RC ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 24 History Version Date Status V1.1.1 March 2026 Publication |
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, MCVideo Server- SIP Core, etc. scenarios which involve interfaces which implementation may widely vary. In particular the present specification contains: • the overall test structure; • the test configurations; • the conformance requirement and reference to the core specifications; • the test purposes; and • a brief description of the test procedure, the specific test requirements and short message exchange table. The present document is valid for MCVideo Servers implemented according to 3GPP releases starting from Release 14 up to the Release indicated on the cover page of the present document. The following information relevant to testing specified in the present document could be found in accompanying specifications: • default setting of the test parameters ETSI TS 136 579-1 [1] (3GPP TS 36.579-1); • Implementation Conformance Statement (ICS) ETSI TS 136 579-4 [2] (3GPP TS 36.579-4) and Implementation extra Information for Testing (IXIT) ETSI TS 136 579-5 [i.3] (3GPP TS 36.579-5); • the applicability of each test case ETSI TS 136 579-4 [2] (3GPP TS 36.579-4). The present document does not specify the protocol conformance testing for the EPS (LTE) bearers which carry the MCVideo data sent or received by the MCVideo Server. The specification of such testing is out of the scope of RAN5. |
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 are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 136 579-1: "LTE; Mission Critical (MC) services over LTE; Part 1: Common test environment (3GPP TS 36.579-1)". [2] ETSI TS 136 579-4: "LTE; Mission Critical (MC) services over LTE; Part 4: Test Applicability and Implementation Conformance Statement (ICS) proforma specification (3GPP TS 36.579-4)". [3] ETSI TS 124 379: "LTE; Mission Critical Push To Talk (MCPTT) call control; Protocol specification (3GPP TS 24.379)". ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 13 [4] ETSI TS 136 509: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Special conformance testing functions for User Equipment (UE) (3GPP TS 36.509)". [5] ETSI TS 136 508: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing (3GPP TS 36.508)". [6] ETSI TS 133 310: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Network Domain Security (NDS); Authentication Framework (AF) (3GPP TS 33.310)". [7] ETSI TS 133 180: "LTE; Security of the Mission Critical (MC) service (3GPP TS 33.180)". [8] ETSI TS 124 281: "LTE; Mission Critical Video (MCVideo) signalling control; Protocol specification (3GPP TS 24.281)". [9] ETSI TS 124 581: "LTE; Mission Critical Video (MCVideo) media plane control; Protocol specification (3GPP TS 24.581)". [10] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol". [11] IETF RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)". [12] IETF RFC 2854 (June 2000): "The 'text/html' Media Type". [13] W3C® Recommendation 24 December 1999: "HTML 4.01 Specification". [14] IETF RFC 6665 (July 2012): "SIP-Specific Event Notification". [15] ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction (3GPP TS 26.114)". [16] IETF RFC 486 (April 2007): "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". [17] IETF RFC 6335 (August 2011): "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry". [18] IETF RFC 3556 (July 2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". [19] IETF RFC 4412 (February 2006): "Communications Resource Priority for the Session Initiation Protocol (SIP)". [20] IETF RFC 8101 (March 2017): "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk service". [21] IETF RFC 7134 (March 2014): "The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"". [22] IETF RFC 5621 (September 2009): "Message Body Handling in the Session Initiation Protocol (SIP)". [23] IETF RFC 3903 (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication". [24] IETF RFC 6184 (May 2011): "RTP Payload Format for H.264 Video". [25] IETF RFC 3550 (July 2003): "RTP: A Transport Protocol for Real-Time Applications". [26] ETSI TS 123 003: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Numbering, addressing and identification (3GPP TS 23.003)". [27] ETSI TS 124 482: "LTE; Mission Critical Services (MCS) identity management; Protocol specification (3GPP TS 24.482)". ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 14 [28] ETSI TS 124 484: "LTE; Mission Critical Services (MCS) configuration management; Protocol specification (3GPP TS 24.484)". [29] ETSI TS 124 481: "LTE; Mission Critical Services (MCS) group management; Protocol specification (3GPP TS 24.481)". [30] ETSI TS 124 282: "LTE; Mission Critical Data (MCData) signalling control; Protocol specification (3GPP TS 24.282)". |
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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Vocabulary for 3GPP Specifications (3GPP TR 21.905)". [i.2] ETSI TS 136 579-3: "LTE; Mission Critical (MC) services over LTE; Part 3: Mission Critical Push To Talk (MCPTT) Server Application conformance specification (3GPP TS 36.579-3)". [i.3] ETSI TS 136 579-5: "LTE; Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS) (3GPP TS 36.579-5)". [i.4] ETSI TS 136 579-2: "LTE; Mission Critical (MC) services over LTE; Part 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specification (3GPP TS 36.579-2)". [i.5] ETSI TS 136 579-6: "LTE; Mission Critical (MC) services over LTE; Part 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specification (3GPP TS 36.579-6)". [i.6] ETSI TS 136 579-7: "LTE; Mission Critical (MC) services over LTE; Part 7: Mission Critical Data (MCData) User Equipment (UE) Protocol conformance specification (3GPP TS 36.579-7)". [i.7] 3GPP TS 36.579-9: "Mission Critical (MC) services over LTE; Part 9: Mission Critical Data (MCData) Server Application conformance specification". [i.8] 3GPP TS 36.579-8: "Mission Critical (MC) services over LTE; Part 8: Mission Critical Video (MCVideo) Server Application conformance specification". |
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 For the purpose of the present document, the following terms and definitions given in ETSI TS 124 281 [8] (3GPP TS 24.281) apply: • An MCVideo user is affiliated to an MCVideo group • An MCVideo user is affiliated to an MCVideo group at an MCVideo client • Affiliation status • Group identity • MCVideo client ID • MCVideo emergency alert state • MCVideo emergency group state • MCVideo emergency group call state • MCVideo emergency private call • MCVideo emergency private call state • MCVideo emergency private priority state • MCVideo imminent peril group call state • MCVideo imminent peril group state • MCVideo private call • MCVideo private emergency alert state • MCVideo video media • Media-transmission control entity • Private call • Remote change of an MCVideo user's selected group • Temporary MCVideo group identity • Trusted mutual aid • Untrusted mutual aid For the purpose of the present document, the following terms given in ETSI TS 133 180 [7] (3GPP TS 33.180) apply: • Client Server Key (CSK) • Private Call Key (PCK) • Signalling Protection Key (SPK) • XML Protection Key (XPK) |
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 Key ECGI E-UTRAN Cell Global Identification E-UTRA Evolved UMTS Terrestrial Radio Access FEC Forward Error Correction GKTP Group Key Transport Payload GMK Group Management Key GMOP Group Management OPeration ICS Implementation Conformance Statement IMPU IMS Public User Identity IUT Implementation Under Test IXIT Implementation eXtra Information for Testing MBMS Multimedia Broadcast and Multicast Service MC Mission Critical MCData Mission Critical Data MCPTT Mission Critical Push To Talk MCS Mission Critical Service MCVideo group ID MCVideo group Identity MCVideo Mission Critical Video MIME Multipurpose Internet Mail Extensions MKI Master Key identifier MVEA MCVideo Emergency Alert MVEG MCVideo Emergency Group MVEGC MCVideo Emergency Group Call MVIG MCVideo Imminent peril Group MVIGC MCVideo Imminent peril Group Call NAT Network Address Translation OIDC OpenID Connect PCK Private Call Key PIDF Presence Information Data Format PLMN Public Land Mobile Network QCI QoS Class Identifier RTP Real-time Transport Protocol SDP Session Description Protocol SIP Session Initiation Protocol SPK Signalling Protection Key SS System Simulator SSRC Synchronization SouRCe TGI Temporary MCVideo Group Identity TMGI Temporary Mobile Group Identity TP Test Purpose TP Transmission Point UE User Equipment URI Uniform Resource Identifier XCAP XML Access Configuration Protocol XDMC XML Document Management Client XPK XML Protection Key XUI XCAP Unique Identifier ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 17 |
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 an optional function/procedure has been implemented. |
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 test case are explicitly copy-pasted from relevant core specifications in the especially dedicated for this clause of each test with the title 'Conformance requirements'. NOTE: When in the copy/pasted text there are references to other specifications the reference numbers will not match the reference numbers used in the present document. This approach has been taken in order to allow easy copy and then search for conformance requirements in those specifications. When differences between conformance requirements in different releases of the cores specifications have impact on the Pre-test conditions, Test procedure sequence or/and the Specific message contents, the Conformance requirements related to different releases are specified separately with clear indication of the Release of the spec from which they were copied. When there is no Release indicated for a conformance requirement text, this should be understood either as the Conformance requirements in the latest version of the spec with release = the TC Applicability release (which can be found in ETSI TS 136 579-4 [2] (3GPP TS 36.579-4), Table 4-1: Applicability of tests and additional information for testing, column 'Release'), or, as the Conformance requirements in the latest version of the spec of the release when the feature was introduced to the core specs. |
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 specified otherwise the condition MCVIDEO applies for all message contents. |
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 refresh token to the successfully authenticated user} } (2) with { IUT (MCVideo Server) having authenticated the SS-UE1 (MCVideo Client) } ensure that { when { the SS-UE1 (MCVideo Client) initiates key management authorization } then { IUT (MCVideo Server) provides identity management key material } } (3) with { IUT (MCVideo Server) having provided identity management key material } ensure that { when { the SS-UE1 (MCVideo Client) requests user service authorization } then { IUT (MCVideo Server) responds to the SS-UE1 (MCVideo Client) with SIP 200 (OK) messages } } (4) with { IUT (MCVideo Server) having provided service authorization } ensure that { when { the SS-UE1 (MCVideo Client) requests configuration management authorization} then { IUT (MCVideo Server) responds to the SIP SUBSCRIBE message with a SIP 200 (OK) message and sends a SIP NOTIFY message containing the XCAP-URI of the documents and sends the MCVideo UE Configuration Document and MCVideo User Profile Configuration Document MCVideo Service Configuration Document via HTTP 200 (OK) messages in response to HTTP GET requests } } (5) with { IUT (MCVideo Server) having provided user configuration data } ensure that { when { the SS-UE1 (MCVideo Client) requests group management authorization } then { IUT (MCVideo Server) responds to the SS-UE1 (MCVideo Client) with SIP 200 (OK) messages and sends the XCAP-URI of the Group documents via a SIP NOTIFY message and sends the Group Document MCVideo UE Configuration document' via a HTTP 200 (OK) message in response to a HTTP GET request and sends the group key transport payloads (GKTP) document via a SIP NOTIFY message } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 19 (6) with { IUT (MCVideo Server) having provided all required configuration data } ensure that { when { the SS-UE1 (MCVideo Client) requests to refresh its service settings } then { IUT (MCVideo Server) responds to the SS-UE1 (MCVideo Client) with a SIP 200 (OK) message } } |
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, 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 7.3.1, 7.3.1A, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6.1, 7.3.6.2, and ETSI TS 133 180 [7] (3GPP TS 33.180), clauses 5.1.1, 5.1.3.1, 5.2.2, 5.3.5, 5.3.6, 5.8.1, 9.2.1. Unless otherwise stated these are Rel-14 requirements. [ETSI TS 124 482 [27] (3GPP TS 24.482), clause 6.3.1] "Upon receipt of an OIDC Authentication Request message as specified in the OpenID Connect 1.0 [6] and IETF RFC 6749 [5] via a secure TLS tunnel between the identity management client and the authorisation endpoint of the IdM server, the IdM server: 1) shall validate the received OIDC Authentication Request message as specified in the OpenID Connect 1.0 [6] and IETF RFC 6749 [5]; 2) shall generate an HTTP 200 (OK) response according to IETF RFC 2616 [4] including form data to prompt the MC service user for their username and password credentials; and NOTE 1: The username will be the MC service user's MC ID. 3) shall send the HTTP 200 (OK) response towards the IdM client. Upon receipt of an HTTP POST request method from the IdM client containing the MC service user's username and password, the IdM server authenticates the MC service user and: NOTE 2: Other methods of authentication can be used by the MC service provider and are not defined by the OIDC specifications. 3GPP TS 33.180 [17] has defined username and password as a mandatory authentication method to be supported for MC services, hence a procedure to realize that method is included here. 1) shall generate an OIDC Authentication Response message as specified in OpenID Connect 1.0 [6] and IETF RFC 6749 [5] with the following clarifications: a) shall generate an HTTP 302 (FOUND) response according to IETF RFC 2616 [4]; and b) shall include the required parameters including the authorization_code as specified in 3GPP TS 33.180 [17] in the query component of the redirection URI contained in the Location header field of the HTTP FOUND request method using the "application/x-www-form-urlencoded" format as specified in W3C.REC-html401-19991224 [7]; and 2) shall send the HTTP 302 (FOUND) response towards the IdM client. Upon receipt of an OIDC Token Request message via a secure TLS tunnel established between the identity management client and the token endpoint of the IdM server, the IdM server: 1) shall validate the OIDC Token Request message and if valid shall generate an OIDC Token Response message as specified in OpenID Connect 1.0 [6] and IETF RFC 6749 [5] with the following clarifications: a) shall generate an HTTP 200 (OK) response according to IETF RFC 2616 [4]; b) shall based on the received MC ID obtained from the received user authentication credentials, determine the MC service ID of the MC service user; c) shall include an id_token, access_token and refresh_token and MC service ID as specified in 3GPP TS 33.180 [17]; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 20 d) shall include the other required parameters as specified in OpenID Connect 1.0 [6] and IETF RFC 6749 [5]; and 2) shall send the HTTP 200 (OK) response towards the IdM client." [ETSI TS 124 482 [27] (3GPP TS 24.482), clause A.2.1.3] "The HTTP client in the network entity is configured with the following parameters: 1) a home HTTP proxy FQDN; and 2) a home HTTP proxy port. The HTTP client in the network entity shall send and receive all HTTP messages via the home HTTP proxy. The HTTP client in the network entity shall insert an X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.109 [15] in the HTTP request and shall set X-3GPP-Asserted-Identity header field to the identity of the HTTP client in the network entity. The identity of the HTTP client in the network entity can be a public service identity, an MC service group ID, or an MC service ID." [ETSI TS 124 482 [27] (3GPP TS 24.482), Annex A.2.3] "The HTTP server shall support the server role of IETF RFC 2616 [4]. Upon reception of an HTTP request: 1) if the received HTTP request does not contain an Authorization header field with the "Bearer" authentication scheme and a bearer access token as specified in IETF RFC 6750 [14] and the received HTTP request does not contain an X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.109 [15], the HTTP server shall reject the request with HTTP 403 (Forbidden) response; 2) if the received HTTP request contains an Authorization header field with the "Bearer" authentication scheme and a bearer access token as specified in IETF RFC 6750 [14]; a) the HTTP server shall validate the bearer access token as specified in IETF RFC 6750 [14]; and b) the HTTP server shall consider the MC service ID derived from the bearer access token as the identity of the sender of the HTTP request; and 3) if the received HTTP request does not contain an Authorization header field with the "Bearer" authentication scheme and a bearer access token as specified in IETF RFC 6750 [14] and the received HTTP request contains an X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.109 [15], the HTTP server shall consider the URI in the X-3GPP-Asserted-Identity header field as the identity of the sender of the HTTP request." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 4.3.1] "The MCS server obtains the appropriate MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. The MCS server obtains the MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. The MCS server subscribes to the MCS service configuration document for each mission critical organisation that is provisioned that is supported by the MCS server using the procedure specified in subclause 6.3.13.2.3. How the MCS server is provisioned with the identities of the mission critical organisations is out of scope of the present document. If the MCS service configuration document has been updated since the current version stored at the MCS server, then the MCS server will receive a SIP NOTIFY request containing an HTTPS URI of the MCS service configuration document. Retrieval by the MCS server, using the notified HTTPS URI, of the MCS service configuration document is performed as specified in subclause 6.3.3.2.3. NOTE: The MCS server can be notified of changes to the MCS service management configuration document at any time while operating the MCS." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 21 [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 4.3.3] "The format of the MCData service configuration document downloaded to the MCData server is defined in subclause 9.4." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 4.4] "The following applies to the configuration management server used for online configuration. The configuration management server needs to convert the MCS UE initial configuration document received from an MCS administrator into an appropriate format for configuration of the MCS UE initial configuration MO. If the MCS UE initial configuration MO contains a <default-user-profile> element that identifies an MCS user profile configuration document, the configuration management server needs to convert the identified MCS user profile configuration document received from an MCS administrator into an appropriate format for configuration of the MCS user profile configuration MO. Once an MCS User Profile configuration document has been created or updated by the MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to store MCS user profile configuration document as the user profile in the MC service user database. In order to download the MCS user profile configuration document to an MCS UE or to support an MCS UE updating the MCS user profile configuration document, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to obtain the MCS user profile from the MC service user database. In order to be notified of changes to an MCS user profile configuration document(s) that have been subscribed to by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to be notified of changes to the MCS user profile stored in the MC service user database. In order to delete the MCS user profile when requested by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to delete the MCS user profile from the MC service user database. NOTE: The configuration management server and group management server functionality for offline configuration is out of scope of the present document." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 6.2.3] "The MCS server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.482 [6]." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 6.2.4.1] "The CMS shall handle the HTTP request as specified for the HTTP server in annex A of 3GPP TS 24.482 [6]. The CMS shall be configured with an authorized MCS server list, containing public service identities of MCS servers of the MCS provider of the CMS. When handling an HTTP request, the CMS shall determine the identity of the sender of the HTTP request as specified in 3GPP TS 24.482 [6], and shall use the identity of the sender of the HTTP request as an authenticated identity when performing the authorization. The CMS shall handle SIP requests and SIP responses as specified in 3GPP TS 24.229 [22]." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 6.3.1.2] "A CMS shall support subclause 6.2.1 "Document Management", and subclause 6.2.4 "Access Permissions" of OMA OMA-TS-XDM_Core-V2_1 [2] and subclause 6.3.13.3 for accepting subscriptions to configuration management documents." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 6.3.2.3] "A CMS shall support receiving XML documents of the application usages according to procedures specified in IETF RFC 4825 [14] "PUT Handling" where the Request-URI of the HTTP PUT request identifies an XML document and include the "auid" as per the appropriate application usage in clause 7." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 22 [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 6.3.13.3.2.2] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI set to own public service identity for performing subscription proxy function of the CMS; c) with a P-Asserted-Identity header field not containing an identity listed in the authorized MCPTT server list specified in subclause 6.2.4; d) with an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-access-token> element; e) with an application/resource-lists+xml MIME body; and f) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [23]; the CMS: a) if an <EncryptedData> XML tag is included in the application/vnd.3gpp.mcptt-info+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/vnd.3gpp.mcptt-info+xml MIME body; b) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; c) shall identify the originating MCPTT ID from <mcptt-access-token> element received in the application/vnd.3gpp.mcpttinfo+xml MIME body and shall use the originating MCPTT ID as an authenticated identity when performing the authorization; d) if the authenticated identity is not authorized to subscribe to notification of changes of any resource in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; e) act as a notifier according to IETF RFC 5875 [11]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the initial SIP SUBSCRIBE request contains an "auid" parameter set to an application usage identifying a configuration management document as described in clause 7; shall return the XCAP URI identifying the configuration management document in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request. Upon sending a SIP NOTIFY request associated with a subscription created as result of the received initial SIP SUBSCRIBE request, if the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, the CMS shall perform the confidentiality protection procedures and integrity protection procedures defined in 3GPP TS 24.379 [9] for MCPTT server. Upon reception of a SIP re-SUBSCRIBE request: a) with the Event header field set to xcap-diff; and b) with an application/resource-lists+xml MIME body; the CMS: a) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body of the received SIP re-SUBSCRIBE request and the CSK was received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 23 b) act as a notifier according to IETF RFC 5875 [11]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the SIP re-SUBSCRIBE request contains an "auid" parameter set to an application usage identifying a configuration management document as described in clause 7: and for which there is no related subscription established according to the subclause 6.3.13.3.2.3, shall return the XCAP URI identifying the configuration management document in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 6.3.13.3.2.3] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI having the base URI equal to the XCAP root URI of the CMS; c) with a P-Asserted-Identity header field containing an identity listed in the authorized MCS server list specified in subclause 6.2.4; and d) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [23]; the CMS shall act as a notifier according to IETF RFC 5875 [11]. Upon reception of a SIP re-SUBSCRIBE request with the Event header field set to xcap-diff, the CMS: a) if the <mcptt-calling-user-id> element is included in the application/vnd.3gpp.mcptt-info+xml MIME body: 1) shall use the <mcptt-calling-user-id> element value as an authenticated identity when performing the authorization; and 2) if the authenticated identity is not authorized to subscribe to notification of changes of any document, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; b) if the authenticated identity is not authorized to subscribe to notification of changes of any document, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; and c) shall act as a notifier according to IETF RFC 5875 [11]." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 9.2.1] "The MCVideo UE configuration document is specified in this subclause. The MCVideo UE configuration document content is based on requirements of Annex A.2 of 3GPP TS 23.281 [27], in accordance with OMA OMA-TS- XDM_Core-V2_1-20120403-A [2]. The usage of an MCVideo UE configuration document in the MCVideo service is described in 3GPP TS 24.281 [28] and 3GPP TS 24.581 [29]. The schema definition is provided in subclause 9.2.2.3. An MCVideo UE configuration document may apply to all MCVideo UEs of a mission critical organization or apply to specific MCVideo UEs identified in the <mcvideo-UE-id> element. If there is no <mcvideo-UE-id> element in the MCVideo UE configuration document, then by default the MCVideo UE configuration document applies to all MCVideo UEs of the mission critical organization that are not specifically identified in the <mcvideo-UE-id> element of another MCVideo UE configuration document of the mission critical organization. Each MCVideo UE of a mission critical organization is configured with an MCVideo UE configuration document that is identified by the instance ID of the MCVideo UE. MCVideo UE configuration documents of a MCVideo user are contained as "XDM collections" in the user's directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCVideo ID, as the user has been already authenticated. A MCVideo UE configuration document corresponding to a specific MCVideo UE the MCVideo user has used to authenticate and is authorised to use the MCVideo service with is placed in the user directory of the MCVideo user. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 24 The MCVideo UE configuration document acts as a template for the CMS to generate UE configuration documents that are downloaded to specific MCVideo UEs. The MCVideo UE configuration document that acts as a template is referred to as a "master MCVideo UE configuration document". The master MCVideo UE configuration document is stored in the users tree of that MCVideo system administrator. The master MCVideo UE configuration document does not directly apply to a specific MCVideo UE, but instead acts as template that the CMS uses to populate the MCVideo UE configuration documents of MCVideo UEs identified by elements of the <MCVideo-UE-id> element. For MCVideo UE configuration documents that correspond to a specific MCVideo UE, the name of the MCVideo UE configuration document is created from a value defined by the corresponding element that identifies the MCVideo UE within the <MCVideo-UE-id> element. For a master MCVideo UE configuration documents that does not contain a <MCVideo- UE-id> element, the name of the MCVideo UE configuration document stored in the user directory is "DEFAULT- MCVideo-UE.xml"." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 9.2.1A] "The MCVideo UE configuration document is accessed using the same XCAP URI, regardless of whether the MCVideo UE has a specific MCVideo UE configuration document configured or the master MCVideo UE configuration document applies. The CMS shall generate the UE's MCVideo UE configuration document from the master MCVideo UE configuration document if the MCVideo administrator did not provision a specific MCVideo UE configuration document. In this generated document, the <MCVideo-UE-id> element shall be set to the MCVideo client's UE ID. The UE's MCVideo UE configuration document shall always be stored with the filename corresponding to the UE's MCVideo UE ID under the user's directory in the users tree. The XCAP URI used by the MCVideo client to access the UE's MCVideo UE configuration document shall be: CMSXCAPROOTURI/org.3gpp.mcvideo.ue-config/users/sip:MCVIDEOID/MCSUEID." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 9.3.1] "The MCVideo user profile configuration document is specified in this subclause. The MCVideo user profile configuration document content is based on requirements of Annex A.3 of 3GPP TS 23.281 [27], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCVideo ID, as the user has been already authenticated. The usage of an MCVideo user profile in the MCVideo service is described in 3GPP TS 24.281 [28]. The schema definition is provided in subclause 9.3.2. MCVideo user profile documents are "XDM collections" in the user's directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The name of the MCVideo user profile document matches the value of the <ProfileName> element in the MCVideo user profile document." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 9.3.1A] "The XCAP URI used by the MCVideo client to access the MCVideo user's MCVideo user profile documents shall be: CMSXCAPROOTURI/org.3gpp.mcvideo.user-profile/users/sip:MCVIDEOID/mcvideo-user-profile-INDEX.xml Where INDEX is the index of the MCVideo user profile as defined in subclause 9.3.2.8." [ETSI TS 124 484 [28] (3GPP TS 24.484), clause 9.4.1] "The MCVideo service configuration document is specified in this subclause. The MCVideo service configuration document content is based on requirements of Annex A.5 of 3GPP TS 23.281 [27], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCVideo service configuration in the MCVideo service is described in 3GPP TS 24.281 [28] and 3GPP TS 24.581 [29]. The schema definition is provided in subclause 9.4.2.3. Each mission critical organization is configured with an MCVideo service configuration document." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 5.4] "To be compliant with the procedures in the present document, an MCVideo server shall support role of an MCS server as specified in subclause 5.2A." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 25 [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 5.2A] "To be compliant with the procedures in the present document, an MCS server: - shall support the role of XCAP client as specified in IETF RFC 4825 [22]; - shall support the role of XDMC as specified in OMA OMA-TS-XDM_Group-V1_1_1 [3]; - shall support the procedure in subclause 6.2.4; - shall support the procedure in subclause 6.3.3.2.3; and - shall support the procedure in subclause 6.3.13.2.2." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.2.4] "The MCS server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.482 [10]. The MCS server shall perform the procedures in subclause 6.2.2 specified for GC." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.3.3.3] "A GMS shall support handling an HTTP GET request from a GMC according to procedures specified in IETF RFC 4825 [22] "GET Handling" where the Request-URI of the HTTP GET request identifies an XML document of the application usage specified in subclause 7.2." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.3.13.3.2.2] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI set to own public service identity for performing subscription proxy function of the GMS; c) with a P-Asserted-Identity header field not containing an identity listed in the authorized MCS server list specified in subclause 6.2.5.1 and not containing an identity listed in the authorized GMS list as specified in subclause 6.2.5.1; d) with an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-access-token> element; e) with an application/resource-lists+xml MIME body; and f) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; the GMS: a) if an <EncryptedData> XML tag is included in the application/vnd.3gpp.mcptt-info+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/vnd.3gpp.mcptt-info+xml MIME body; b) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; c) shall identify the originating MCS ID from <mcptt-access-token> element received in the application/vnd.3gpp.mcptt-info+xml MIME body and shall use the originating MCS ID as an authenticated identity when performing the authorization; d) if the authenticated identity is not authorized to subscribe to notification of changes of any resource in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 26 e) act as a notifier according to IETF RFC 5875 [13]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the initial SIP SUBSCRIBE request identifies: 1) a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is an MCS group ID owned by an MCS provider other than the MCS provider of the GMS; or 2) a element of an MCS GKTP document as described in subclause 7.7.10 where the group ID is an MCS group ID owned by an MCS provider other than the MCS provider of GMS; shall perform the procedure in subclause 6.3.13.3.2.4 for each such MCS group ID and shall interwork information of received SIP NOTIFY requests in subclause 6.3.13.3.2.4 in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request. Upon sending a SIP NOTIFY request associated with a subscription created as result of the received initial SIP SUBSCRIBE request, if the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, the GMS shall perform the confidentiality protection procedures and integrity protection procedures defined in 3GPP TS 24.379 [5] for MCS server. Upon reception of a SIP re-SUBSCRIBE request: a) with the Event header field set to xcap-diff; and b) with an application/resource-lists+xml MIME body; the GMS: a) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body of the received SIP re-SUBSCRIBE request and the CSK was received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; and b) act as a notifier according to IETF RFC 5875 [13]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the SIP re-SUBSCRIBE request identifies: 1) a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is an MCS group ID owned by an MCS provider other than the MCS provider of the GMS; or 2) a element of an MCS GKTP document as described in subclause 7.7.10 where the group ID is an MCS group ID owned by an MCS provider other than the MCS provider of GMS; and for which there is no related subscription established according to the subclause 6.3.13.3.2.4, shall perform the procedure in subclause 6.3.13.3.2.4 for each such MCS group ID and shall interwork information of received SIP NOTIFY requests in subclause 6.3.13.3.2.4 in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.3.13.3.3] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI set to own public service identity for accessing documents; c) with a P-Asserted-Identity header field containing an identity listed in the authorized GMS list as specified in subclause 6.2.5.1; d) with an application/resource-lists+xml MIME body; e) with an application/vnd.3gpp.mcptt-info+xml MIME body; and f) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 27 the GMS: a) if the <mcptt-calling-user-id> element is included in the application/vnd.3gpp.mcptt-info+xml MIME body: 1) shall use the <mcptt-calling-user-id> element value as an authenticated identity when performing the authorization; and 2) if the authenticated identity is not authorized to subscribe to notification of changes of any document or element in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; b) if the <mcptt-calling-group-id> element is included in the application/vnd.3gpp.mcptt-info+xml MIME body: 1) when performing the authorization, shall use URI of the P-Asserted-Identity header field as an authenticated identity and shall determine that the subscription is on behalf of the identity in the <mcptt- calling-group-id> element; 2) if the authenticated identity is not authorized to subscribe to notification of changes of any document or element in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; and 3) if the MCS group ID indicated in the <mcptt-calling-group-id> element is a constituent MCS group of a temporary MCS group and the documents or elements indicated in the application/resource-lists+xml MIME body are not associated with the temporary MCS group ID, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; and c) shall act as a notifier according to IETF RFC 5875 [13]." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 7.2.12.1] "Authorization policies are described in the OMA OMA-TS-XDM_Group-V1_1_1 [3] "Authorization policies". An authenticated identity is authorized to read the <group> element of an MCS group document. An authenticated identity is authorized to read a <list-service> element of the <group> element of the MCS group document and any descendant elements of the <list-service> element: a) except a <list> element of the <list-service> element; and b) except descendant elements of the <list> element of the <list-service> element; if the authenticated identity is a member of an MCS group defined by the <list-service> element. An authenticated identity is authorized to read a <list> element of a <list-service> element of the <group> element of an MCS group document and any descendant elements of the <list> element if: a) the authenticated identity is a member of MCS group defined by the <list-service> element; and b) the MCS group document contains a <rule> element: 1) with the <conditions> element evaluating to true for the authenticated identity or without the <conditions> element; and 2) with the <actions> element containing the <on-network-allow-getting-member-list> element. An authenticated identity is authorized to read an <entry> element of a <list> element of a <list-service> element of the <group> element of the MCS group document and any descendant elements of the <entry> element if: a) the "uri" attribute of the <entry> element contains the authenticated identity; b) the "uri" attribute of the <mcvideo-mcvideo-id> element of the <entry> element contains the authenticated identity; or c) the "uri" attribute of the <mcdata-mcdata-id> element of the <entry> element contains the authenticated identity. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 28 An authenticated identity is authorized to read an MCS group document if the authenticated identity is listed in the authorized MCS server list specified in subclause 6.2.5.1. An authenticated identity is authorized to create, read, modify and delete an MCS group document if the MCS group document is stored: a) in users tree of the XUI equal to the authenticated identity; or b) in users tree of the another XUI, subject to MCS service provider policy. The MCS service provider policy can specified e.g. using an appropriate access permissions document specified in OMA OMA-TS-XDM_Core- V2_1 [2], stored in the user's tree of the other XUI; and unless precluded by other statement of this subclause. None is authorized to create, delete, and modify a <on-network-temporary> element of a <list-service> element of the <group> element of an existing MCS group document. None is authorized to delete a group document containing a <on-network-regrouped> element of a <list-service> element of the <group> element of an MCS group document. An authenticated identity is authorized to create and delete a <on-network-regrouped> element in the <list-service> element of the <group> element of an existing MCS group document if the authenticated identity is in authorized GMS list specified in subclause 6.2.5.1. An authenticated identity is authorized to subscribe to notification of changes of an MCS group document if: 1) the authenticated identity is a member of an MCS group defined by a <list-service> element of the <group> element of the MCS group document; 2) the authenticated identity is listed in the authorized MCS server list specified in subclause 6.2.5.1; or 3) the authenticated identity is listed in the authorized GMS list specified in subclause 6.2.5.1 and the subscription is on behalf of a constituent MCS group of the MCS group defined by the MCS group document." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.1] "The MCVideo server obtains information that it needs to implement service authorization specific requirements from: a) any received third-party SIP REGISTER request (e.g. including information contained in the body of the third- party SIP REGISTER request) as specified in 3GPP TS 24.229 [11]. The body will carry the SIP REGISTER request as sent by the MCVideo client and may contain information needed for service authorization; or b) any received SIP PUBLISH request for MCVideo server settings containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters. The body of the SIP PUBLISH request will contain information needed for service authorization." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.1A] "When the MCVideo server receives a SIP REGISTER request sent from the MCVideo client contained within a message/sip MIME body of a received third-party SIP REGISTER request or a SIP PUBLISH request, it first determines whether XML MIME bodies included in the request are integrity protected. If XML MIME bodies are integrity protected the MCVideo server validates the signature of each of the XML MIME bodies. If the integrity protection check(s) pass or the XML MIME bodies are not integrity protected, the MCVideo server then determines whether the content in specific XML elements is confidentiality protected. If XML content is confidentiality protected, the MCVideo server decrypts the protected content. Upon receiving: - a SIP REGISTER request containing an application/vnd.3gpp.mcvideo-info+xml MIME body within a message/sip MIME body of the SIP REGISTER request sent from the MCVideo client; or - a SIP PUBLISH request containing an application/vnd.3gpp.mcvideo-info+xml MIME body and an application/poc-settings+xml MIME body; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 29 the MCVideo server: 1) shall determine if integrity protection has been applied to XML MIME bodies in the SIP request by following the procedures in clause 6.6.3.4.1 for each XML MIME body; 2) if integrity protection has been applied, shall use the keying data described in clause 6.6.3.2 and the procedures described in clause 6.6.3.4.2 to verify the integrity of each of the XML MIME bodies; and 3) if all integrity protection checks succeed, shall continue with the remaining steps of this clause. Upon receiving: - a SIP REGISTER request containing an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-access-token> element and an <mcvideo-client-id> element within a message/sip MIME body of the SIP REGISTER request sent from the MCVideo client; or - a SIP PUBLISH request containing an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-access-token> element and an <mcvideo-client-id> element, and an application/poc-settings+xml MIME body; the MCVideo server: 1) shall determine if confidentiality protection has been applied to the <mcvideo-access-token> element and the <mcvideo-client-id> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, by following the procedures in clause 6.6.2.4.1; 2) if confidentiality protection has been applied to the <mcvideo-access-token> element and <mcvideo-client- id> element: a) shall use the keying information received in the MIKEY-SAKKE I_MESSAGE as specified in 3GPP TS 33.180 [8], along with the procedures described in clause 6.6.2.4.2 to: i) decrypt the received access token in the <mcvideo-access-token> element in the application/vnd.3gpp.mcvideo-info+xml MIME body; and ii) decrypt the received MCVideo client ID in the <mcvideo-client-id> element in the application/vnd.3gpp.mcvideo-info+xml MIME body; b) if the decryption procedure succeeds, shall identify the MCVideo ID and the MCVideo client ID from the decrypted values; and c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful; 3) if confidentiality protection has been applied to only one of the <mcvideo-access-token> element or the <mcvideo-client-id> element: a) shall determine that confidentiality protection has not been successful; 4) if confidentiality protection has not been applied: a) shall identify the MCVideo ID from <mcvideo-access-token> element received in the application/vnd.3gpp.mcvideo-info+xml MIME body; and b) shall identify the MCVideo client ID from the <mcvideo-client-id> element received in the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receiving a SIP PUBLISH request containing an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-request-uri> element, an <mcvideo-client-id> element, and an application/poc-settings+xml MIME body, the MCVideo server: 1) shall determine if confidentiality protection has been applied to the <mcvideo-request-uri> element and the <mcvideo-client-id> element in the application/vnd.3gpp.mcvideo-info+xml MIME body by following the procedures in clause 6.6.2.4.1; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 30 2) if confidentiality protection has been applied to the <mcvideo-request-uri> element and the <mcvideo-client- id> element: a) shall use the keying information described in clause 6.6.2.2 along with the procedures described in clause 6.6.2.4.2 to: i) decrypt the received encrypted MCVideo ID in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body; and ii) decrypt the received encrypted MCVideo client ID in the <mcvideo-client-id> element in the application/vnd.3gpp.mcvideo-info+xml MIME body; b) if all decryption procedures succeed, shall identify the MCVideo ID and MCVideo client ID from the decrypted values; and c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful; 3) if confidentiality protection has been applied to only one of the <mcvideo-request-uri> element or <mcvideo- client-id> element: a) shall determine that confidentiality protection has not been successful; 4) if confidentiality protection has not been applied: a) shall identify the MCVideo ID from the contents of the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body; and b) shall identify the MCVideo client ID from the <mcvideo-client-id> element received in the application/vnd.3gpp.mcvideo-info+xml MIME body." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.2] "The MCVideo server shall support obtaining service authorization specific information from the SIP REGISTER request sent from the MCVideo client and included in the body of a third-party SIP REGISTER request. NOTE 1: 3GPP TS 24.229 [11] defines how based on initial filter criteria the SIP REGISTER request sent from the UE is included in the body of the third-party SIP REGISTER request. Upon receiving a third party SIP REGISTER request with a message/sip MIME body containing the SIP REGISTER request sent from the MCVideo client containing an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-access-token> element and an <mcvideo-client-id> element within a message/sip MIME body of the SIP REGISTER request sent from the MCVideo client, the MCVideo server: 1) shall identify the IMS public user identity from the third-party SIP REGISTER request; 2) shall identify the MCVideo ID from the SIP REGISTER request sent from the MCVideo client and included in the message/sip MIME body of the third-party SIP REGISTER request by following the procedures in clause 7.3.1A; 2a) shall check if the number of maximum simultaneous authorizations supported for the MCVideo user as specified in the <max-simultaneous-authorizations> element of the <anyExt> element contained in the <OnNetwork> element of the MCVideo service configuration document (see the service configuration document in 3GPP TS 24.484 [25]) has been reached. If the number of maximum simultaneous authorizations has been reached, the MCVideo server shall not continue with the rest of the steps in this clause; 3) shall perform service authorization for the identified MCVideo ID as described in 3GPP TS 33.180 [8]; 4) if service authorization was successful, shall bind the MCVideo ID and the MCVideo client ID to the IMS public user identity; 4a) if service authorization was successful and if, the service authorization request was from an MCVideo user who is previously MCVideo service authorized on another MCVideo client (as determined by a comparison of the received MCVideo client ID with the MCVideo client ID of existing bindings), keep the current bindings and create a new binding between the MCVideo ID, MCVideo client ID and the IMS public user identity; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 31 NOTE 2: The MCVideo server will store the binding MCVideo ID, MCVideo client ID, IMS public user identity and an identifier addressing the MCVideo server in an external database. 5) if a Resource-Share header field with the value "supported" is contained in the "message/sip" MIME body of the third-party REGISTER request, shall bind the MCVideo ID and the MCVideo client ID to the identity of the MCVideo UE contained in the "+g.3gpp.registration-token" header field parameter in the Contact header field of the incoming third-party REGISTER request; and 6) if more than one binding exists for the MCVideo ID, shall include in the SIP 200 (OK) response an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in annex F.1 with an <multiple-devices-ind> element set to a value of "true"." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.3] "For MCVideo server settings. Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; 2) an application/poc-settings+xml MIME body; and 3) an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <mcvideo-access-token> element and an <mcvideo-client-id> element; the MCVideo server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall perform the procedures in clause 7.3.1A; … 3a) shall check if the number of maximum simultaneous authorizations supported for the MCVideo user as specified in the <max-simultaneous-authorizations> element of the <anyExt> element contained in the <OnNetwork> element of the MCVideo service configuration document (see the service configuration document in 3GPP TS 24.484 [25]) has been reached… 4) shall perform service authorization for the identified MCVideo ID as described in 3GPP TS 33.180 [8]; 5) if service authorization was successful: a) shall bind the MCVideo ID and MCVideo client ID to the IMS public user identity; b) if the service authorization request was from an MCVideo user who is previously MCVideo service authorized on another MCVideo client (as determined by a comparison of the received MCVideo client ID with the MCVideo client ID of existing bindings), keep the current bindings and create a new binding between the MCVideo ID, MCVideo client ID and the IMS public user identity; and c) if a Resource-Share header field with the value "supported" was included in the "message/sip" MIME body of the third-party REGISTER request, shall bind the MCVideo ID to the identity of the MCVideo UE contained in the "+g.3gpp.registration-token" header field parameter in the Contact header field of the third-party REGISTER request that contained this IMS public user identity; NOTE 1: The MCVideo server will store the binding MCVideo ID, MCVideo client ID, IMS public user identity and an identifier addressing the MCVideo server in an external database. 6) if service authorization was not successful, shall send a SIP 403 (Forbidden) response towards the MCVideo client with the warning text set to: "101 service authorisation failed" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause; 7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [12] and if processing of the SIP request was not successful, do not continue with the rest of the steps; 8) shall cache the received MCVideo service settings until the MCVideo service settings expiration timer expires; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 32 9) shall send aSIP 200 (OK) response according to 3GPP TS 24.229 [11] with: a) if more than one binding exists for the MCVideo ID, an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in annex F.1 with an <multiple-devices-ind> element set to the value "true"; 10) shall use the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package as the current Answer-Mode Indication of the MCVideo client. 11) shall download the MCVideo user profile from the MCVideo user database as defined in 3GPP TS 29.283 [54] if not already stored at the MCVideo server and use the <selected-user-profile-index> element of the poc- settings event package if included to identify the active MCVideo user profile for the MCVideo client; NOTE 2: If the <selected-user-profile-index> element of the poc-settings event package is included then only that MCVideo user profile is needed to be downloaded from the MCVideo user database. 12) if there is no <selected-user-profile-index> element included in the poc-settings event package then if multiple MCVideo user profiles are stored at the MCVideo server or downloaded for the MCVideo user from the MCVideo user database, shall determine the pre-selected MCVideo user profile to be used as the active MCVideo user profile by identifying the MCVideo user profile (see the MCVideo user profile document in 3GPP TS 24.484 [25]) in the collection of MCVideo user profiles that contains a <Pre-selected-indication> element; and NOTE 3: If only one MCVideo user profile is stored at the MCVideo server or only one MCVideo user profile is downloaded from the MCVideo user database, then by default this MCVideo user profile is the pre- selected MCVideo user profile. 13) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCVideo user profile document with one or more <entry> elements containing an MCVideo group ID (see the MCVideo user profile document in 3GPP TS 24.484 [25]) for the served MCVideo ID, shall perform implicit affiliation as specified in clause 8.2.2.2.15." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.4] "Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; 2) an application/poc-settings+xml MIME body; and 3) an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <mcvideo-request-uri> element and an <mcvideo-client-id> element; The MCVideo server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall perform the procedures in clause 7.3.1A; … 4) shall verify that a binding between the IMS public user identity in the Request-URI and the MCVideo ID in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml exists at the MCVideo server; 5) if a binding exists between the IMS public user identity and the MCVideo ID in the request and the validity period of the binding has not expired shall download the MCVideo user profile from the MCVideo user database as defined in 3GPP TS 29.283 [54] if not already stored at the MCVideo server; … 7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [12] and if processing of the SIP request was not successful, do not continue with the rest of the steps; 8) shall cache the received MCVideo service settings until the MCVideo service settings expiration timer expires; 9) shall send a SIP 200 (OK) response according 3GPP TS 24.229 [11]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 33 10) shall use the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package as the current Answer-Mode Indication of the MCVideo client. 11) shall download the MCVideo user profile from the MCVideo user database as defined in 3GPP TS 29.283 [54] if not already stored at the MCVideo server and use the <selected-user-profile-index> element of the poc- settings event package if included to identify the active MCVideo user profile for the MCVideo client; NOTE 1: If the <selected-user-profile-index> element of the poc-settings event package is included then only that MCVideo user profile is needed to be downloaded from the MCVideo user database. 12) if there is no <selected-user-profile-index> element included in the poc-settings event package then if multiple MCVideo user profiles are stored at the MCVideo server or downloaded for the MCVideo user from the MCVideo user database, shall determine the pre-selected MCVideo user profile to be used as the active MCVideo user profile by identifying the MCVideo user profile (see the MCVideo user profile document in 3GPP TS 24.484 [25]) in the collection of MCVideo user profiles that contains a <Pre-selected-indication> element; and NOTE 2: If only one MCVideo user profile is stored at the MCVideo server or only one MCVideo user profile is downloaded from the MCVideo user database, then by default this MCVideo user profile is the pre- selected MCVideo user profile. 13) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCVideo user profile document with one or more <entry> elements containing an MCVideo group ID (see the MCVideo user profile document in 3GPP TS 24.484 [25]) for the served MCVideo ID, shall perform implicit affiliation as specified in clause 8.2.2.2.15." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.5] "Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; and 2) an Expires header field set to 0; the MCVideo server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [12] and if processing of the SIP request was successful, continue with the rest of the steps; 3) shall remove the MCVideo service settings; 4) shall remove the binding between the MCVideo ID and public user identity; and 5) shall send a SIP 200 (OK) response according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.6.1] "Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCVideo function of the served MCVideo user; 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body containing the<mcvideo-request-uri> element which identifies an MCVideo ID served by the MCVideo server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; and 3) the Event header field of the SIP SUBSCRIBE request contains the 'poc-settings' event type. the MCVideo server: 1) shall identify the served MCVideo ID in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP SUBSCRIBE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 34 2) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCVideo function serving the MCVideo user, shall identify the originating MCVideo ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request; 3) if the originating MCVideo ID is different than the served MCVideo ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; and 4) shall generate a 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 6665 [16] and IETF RFC 4354 [53]. For the duration of the subscription, the MCVideo server shall notify subscriber about changes of the MCVideo service settings of the subscribed MCVideo user, as described in clause 7.3.6.2." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.6.2] "In order to notify the subscriber about changes of the MCVideo service settings of the subscribed MCVideo client of the subscribed MCVideo user, the MCVideo server: 1) shall generate an application/poc-settings+xml MIME body as defined in 3GPP TS 24.379 [40] containing: a) the <am-settings> element of the poc-settings event package set to the current answer mode setting of the MCVideo client according to IETF RFC 4354 [53]; and b) the <selected-user-profile-index> element as defined in clause 7.4.1.2 identifying the active MCVideo user profile; and 2) send a SIP NOTIFY request according to 3GPP TS 24.229 [11], IETF RFC 6665 [16] and IETF RFC 4354 [53] with the constructed application/poc-settings+xml MIME body." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 5.1.1] "The generic steps for MCX user authentication and authorisation is shown in figure 5.1.1-1. MCX UE SIP Core MCX Domain LTE & EPC ID Management server LTE Attach procedure B-1. SIP Registration and Authentication B-2. Third Party Registration C. MCX User Service Authorisation A. MCX User Authentication Figure 5.1.1-1: MCX authentication and authorisation At UE power-on, the MCX UE performs LTE authentication as specified in TS 33.401 [14]. The MCX UE then performs the following steps to complete authentication of the user, authorisation of the user, MCX service registration, and identity binding between signalling layer identities and the MC service ID(s). - A: MCX user authentication. - B: SIP Registration and Authentication. - C: MCX Service Authorization. These procedures are described in more detail in subsequent clauses. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 35 Steps A and B may be performed in either order or in parallel. For scenarios where this order has an impact on the identity bindings between signalling layer identities and the MC service ID(s), a re-registration (Step B) to the SIP Core may be performed to update the registered signalling layer identity. If an MCX UE completes SIP registration in Step B prior to performing MCX user authentication in Step A and MCX user service authorization as part of Step C, the MCX UE shall be able to enter a 'limited service' state. In this limited state, where the MCX user is not yet authorized with the MCX service, the MCX UE shall be able to use limited MCX services (e.g. an anonymous MCX emergency communication). The MCX Server is informed of the registration of the MC UE with the SIP core though Step B-2. Additionally, an HTTP-1 authentication mechanism is used. NOTE: Mechanisms for confidentiality and integrity protection (not defined in this clause) may be combined only with certain authentication procedures." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 5.1.3.1] "This clause expands on the MCX user service authorization step shown in figure 5.1.1-1 step C. MCX User Service Authorization is the function that validates whether or not a MCX user has the authority to access certain MCX services. In order to gain access to MCX services, the MCX client in the UE presents an access token (acquired during user authentication as described in subclause 5.1.2) to each service of interest (i.e. Key Management, MCX server, Configuration Management, Group Management, etc.). If the access token is valid, then the user is granted the use of that service. Figure 5.1.3.1-1 shows the flow for user authorization which covers key management authorization, MCX user service authorization, configuration management authorization, and group management authorization. NOTE: All HTTP traffic between the UE and HTTP proxy, and all HTTP traffic between the UE and KMS (if not going through the HTTP proxy) is protected using HTTPS. For key management authorization, the KM client in the UE presents an access token to the KMS over HTTP. The access token shall be scoped for key management services as defined in annex B.4.2.2. The KMS validates the access token and if successful, provides one or more sets of user specific key material back to the UE KM client based on the MC service ID(s) present in the access token (MCPTT ID, MCVideo ID and/or MCData ID). User specific key material includes identity based key information for media and signalling protection. If an interworking key management record (InterKMRec) exists and is associated to the requesting MC service ID (see clause 11.2.3), the KMS shall also provide the InterKMRec. This key management authorisation may be repeated for each KM service the user is authorised to use (MCPTT, MCVideo, MCData). In order to secure the transfer of user specific key material from the KMS to the KM client when using the TrK and InK, the KM client includes the TrK-ID and the InK-ID in the key management authorization request. … For MCVideo service authorization, the MCVideo client in the UE presents an access token to the MCVideo server over SIP. The access token shall be scoped for MCVideo services as defined in annex B.4.2.2. The MCVideo server validates the access token and if successful, authorizes the user for full MCVideo services and sends an acknowledgement back to the MCVideo client. The MCVideo server then maps and maintains the IMPU to MCVideo ID association. The MCVideo ID to IMPU association shall only be known to the application layer. The SIP message used to convey the access token from the MCVideo client to the MCVideo server may be either a SIP REGISTER or SIP PUBLISH message. … The UE can now perform configuration management authorization and download the user profile for the service(s) (MCPTT, MCVideo, MCData). Following the flow described in subclause 10.1.4.3 of 3GPP TS 23.280 [36] "MC service user obtains the MC service user profile(s) from the network", the Configuration Management (CM) client in the UE sends an access token in the user profile query to the Configuration Management server over HTTP. The access token shall be scoped for configuration management services as defined in annex B.4.2.2. The CM server receives the request and validates the access token, and if valid, the CM server uses the identity from the access token (MCPTT ID, MCVideo ID, MCData ID) to obtain the user profile from the MCX user database. The CM server then sends the user profile back to the CM client over HTTP. This configuration management authorisation may be repeated for each CM service the user is authorised to use (MCPTT, MCVideo, MCData). ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 36 Upon receiving each user profile, the Group Management (GM) client in the UE can now perform group management authorization. The GM client obtains the user's group membership information from the user profile, and following the flow shown in clause 10.1.5.2 of 3GPP TS 23.280 [36] "Retrieve group configurations at the group management client", the Group Management (GM) client in the UE sends an access token in the Get group configuration request to the host GM server of the group membership over HTTP. The access token shall be scoped for group management services as defined in annex B.4.2.2. The GM server validates the access token, and if valid, completes the flow. As part of group management authorization, group key information is provided as per subclause 5.7 of the present document. This group management authorisation may be repeated for each GM service the user is authorised to use (MCPTT, MCVideo, MCData). For MC UEs that support mission critical location services, authorization is accomplished by including an access token in each location message (i.e. location information report, location reporting trigger, etc.) sent by the location management client to the location management server. The access token shall be scoped for location management services as defined in annex B.4.2.2. The location management server validates the access token and (if successful) processes the message (e.g. accepts and stores the location information report). If an access token cannot be validated, local policy may dictate an action to be taken within the location management server with regards to the received location message (e.g. the local policy may require storage of the location information report as an emergency provision). MCX UE KM Server(s) C-1a: Establish a secure tunnel MCX Server(s) GM Server(s) MCX proxy C-5: Group Management Authorisation C-4: Configuration Management Authorisation C-3: User Service Authorisation CM Server(s) C-1b: Establish a secure tunnel (optional) Figure 5.1.3.1-1: MCX user service authorization The user authorization procedure in Step C of Figure 5.1.1-1 is further detailed into 5 sub steps that comprise the MCX user service authorization process: Step C-1a: If not already done, establish a secure HTTP tunnel using HTTPS between the MCX UE and MCX proxy server. Subsequent HTTP messaging makes use of this tunnel . Step C-1b: When required by the MCX system, establish a secure HTTP tunnel using HTTPS between the MCX KM client and the KMS. When supported, subsequent HTTP messaging between the MCX KM client and the KMS makes use of this tunnel in lieu of the tunnel set up in Step C-1a. Step C-2: The KM client in the MCX UE presents an access token to the KMS over HTTP. The KMS authorizes the user for key management services based upon the MC service ID(s) provided and replies to the client with identity specific key information. This step may be repeated to authorise the user with additional KM services (MCPTT, MCVideo, MCData) as necessary. Step C-3: The MCX client in the UE presents an access token to the MCX server over SIP as defined in clause 5.1.3.2 of the present document. This step may be repeated to authorise the user with additional MCX services (MCPTT, MCVideo, MCData) as necessary. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 37 Step C-4: The CM client in the UE follows the "MCX user obtains the user profile (UE initiated)" flow from clause 10.1.4.3 of 3GPP TS 23.280 [36], presenting an access token in the Get MCX user profile request over HTTP. If the token is valid, then the CM server authorizes the user for configuration management services. Completion of this step results in the CM server providing the user's profile to the CM client. This step may be repeated as necessary to obtain the user profile for additional services (MCPTT, MCVideo, or MCData). Step C-5: The GM client in the UE follows the "Retrieve group configurations at the group management client" flow as shown in clause 10.1.5.2 of 3GPP TS 23.280 [36], presenting an access token in the Get group configuration request over HTTP. If the token is valid, the GMS authorizes the user for group management services. Completion of this step results in the GMS sending the user's group policy information and group key information to the GM client. This step may be repeated to authorise the user for additional group services (MCPTT, MCVideo, MCData) as necessary." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 5.2.2] "The security mechanism described in this clause allows a key, K, to be distributed from an initiating party to a receiving party. It provides confidentiality of the key, and integrity and authenticity of the payload. It is used within a number of different security procedures in this specification. The key, K, is distributed encrypted specifically to the receiving entity and signed by the initiating entity. Prior to call commencement, both MCX UEs shall be provisioned by the KMS with time-limited key material associated with the MCX entity's URI. The key is distributed with a 32-bit Key Identifier (K-ID). This payload is a MIKEY-SAKKE I_MESSAGE, as defined in IETF RFC 6509 [11], which ensures the confidentiality of the key, plus integrity and authenticity of the payload. The key is encrypted to the user identity (UID) associated to the receiving MCX entity using the security domain parameters provided in the public values in the certificate received from the KMS. The UID used to encrypt the data is derived from the receiving entity's URI (e.g. sip:user.002@mcptt.example.org) and a time-related parameter (e.g. the current year and month). The terminating entity's URI is added to the recipient field (IDRr) of the message. The payload includes the encrypted key and the key identifier (K-ID). The key is unique within the MC domain. On creating the key, the initiator generates a 32-bit key identifier (K-ID). The 4 most significant bits of the K-ID shall indicate the purpose of the key, the other 28-bits shall be randomly generated. The key identifier (K-ID) is stored in the CSB-ID field of the MIKEY I_MESSAGE. The payload is signed using (the KMS-provisioned key associated to) the identity of the initiating entity. The UID used to sign the data is derived from the initiating entity's URI (e.g. sip:user.001@mcptt.example.org) and a time-related parameter (e.g. the current year and month). The initiating entity's URI is added to the initiator field (IDRi) of the message. NOTE: This solution is for the end-to-end protection of keys and does not protect the identities transmitted. Identities may be masked by transmitting the UID within the MIKEY ID fields as described in Annex E.7. The security processes are summarized in figure 5.2.2-1. … Via this mechanism, the key distribution is confidentiality protected, authenticated and integrity protected. It is possible that the key has been distributed using an unacceptable KMS, either for the initiator's KMS or for the receiver's KMS. This is particularly likely for communications being sent across multiple MC Systems (where KMS information may not have been shared prior to beginning the key distribution procedure). In this case, a KMS Redirect Response (KRR) may be sent back to the initiator. The KRR provides the initiator with information about which KMS may be acceptable. KRR procedures are described in clause 5.2.8. Assuming that acceptable KMS(s) have been used, the I_MESSAGE will be processed by the receiving entity. The initiating entity's URI is extracted from the initiator field (IDRi) of the message. This is converted to a UID and used to check the signature on the MIKEY-SAKKE I_MESSAGE. If valid, the UE extracts and decrypts the encapsulated key, K, using the (KMS-provisioned) entity's UID key. The MCX entity also extracts the K-ID. This process is shown in figure 5.2.2-2. … ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 38 With the key successfully shared between the two MCX entities, the entities are able to use the shared security context to protect communications." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 5.3.5] "A KMS Certificate is defined in Annex D.3.2. A KMS Certificate contains the following: - A Role of 'Home' or 'External', depending on whether the certificate is the issuing KMS's or is provided by another external KMS. - The KMS Public Authentication Key (KPAK in IETF RFC 6507 [9]). - The KMS Public Confidentiality Key (Z_T in IETF RFC 6508 [10]). - The UID conversion (as described below). - Choice of cryptographic domain parameters (such as those listed in IETF RFC 6509 [8]). - The time period for which this information is valid. Certificates are identified by the KMS (KMSUri) and a unique identifier (CertUri). A (logical) KMS should only have a single KMS certificate active at any one time (based upon the KMSUri). Certificates may be updated using the CertURI. Should a client receive a certificate with a CertURI of an existing certificate, the client shall replace this existing certificate with the newly provisioned certificate. The UID conversion mechanism defines how UIDs are generated. Using this information a MC client can take a user identifier (e.g. an MCPTT ID), and the current time, (e.g. the year and month) and convert these to a UID. EXAMPLE: UID = Hash (MCPTT ID, KMS URI, validity period info). As a consequence, there is a one-to-one correspondence between MC Service IDs and UIDs during each time period." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 5.3.6] "KMSKeySet(s) are defined in Annex D.3.3.2 and contain the following: - A user signing key for each UID for the current time period (SSK and PVT in IETF RFC 6507 [9]). - A user decryption key for each UID for the current time period (RSK in IETF RFC 6508 [10]). - The key period number associated with the current keys. - Optionally, the time period, for which the user key material is valid (e.g. month)." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 5.8.1] "The 'key download' procedure is used to send keys from the MCX server to the MC client. It is used to distribute Multicast Signalling Keys (MuSiKs) to the MC clients, and it is used to update both the CSKs and MuSiKs. Within the 'key download' procedure, keys (CSK or MuSiKs) are encrypted specifically to the MC user and signed using an identity representing the MC Server. Prior to group key distribution, each MC client shall be provisioned by the KMS with time-limited key material associated with the MC User as described clause 5.3. The MC Server shall also be provisioned by the MC KMS with key material for an identity which is authorised to act as an MCX Server. The key (CSK or MuSiK) is distributed from the MCX Server to a MC client using the security mechanism described in clause 5.2.2, transported over the SIP bearer. End-point diversity is not required as end-points do not encrypt data, hence the extension in clause 5.2.3 is not applied. Additional parameters may be included as defined in clause 5.2.4. The SAKKE-to-self extension may be included as defined in clause 5.2.5. Identity hiding may be supported as defined in clause 5.2.6. The initiating entity shall be the initiating MCX Server and the receiving entity shall be the terminating MC user. The initiating entity URI shall be the FQDN of the MCX Server (e.g. MDSI of the MC Domain) and the receiving entity URI shall be the MC Service ID of the terminating user. The distributed key, K, shall be the CSK or MuSiK and the key identifier K-ID shall be the CSK-ID or MuSiK-ID (respectively). As a result of this 'key download' mechanism, the MC clients receive a new signalling key, CSK or MuSiK, identified by the 4 most significant bits of the key ID. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 39 The MCData Service server may use the Key Download procedure to indicate or modify the algorithm used to protect the MCData signalling fields (i.e. MCData signaling parameters, Data signaling payload and End to end security parameters) by including a 'signalling algorithm' parameter. The 'signalling algorithm' parameter is described in clause 8.5.4.1. The available algorithms shall be as defined in clause 8.5.4.2." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 9.2.1.1] "A Client-Server Key is required to protect unicast RTCP signalling between the MC client and the MCX Server. The use of the CSK in this context is defined in clause 9.4. Additionally, the MC Service provider may require that MC identities, access tokens and other sensitive information transferred between clients and MC domain on the SIP-1 and SIP-2 interfaces be protected at the application layer from any viewing, including protection from viewing at the SIP signalling layer. Symmetric key based protection of SIP payload using CSK may be used to satisfy this requirement. The use of CSK in this context is defined in clause 9.3. The uses of the CSK are shown in Figure 9.2.1-1 …" [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 9.2.1.2] "The 128-bit CSK is initially generated by the client and provided encrypted to the server through the SIP interface along with the CSK-ID identifying the CSK. The key remains in use until: a new CSK is required, the SIP session is torn down, the MC user logs off, or some other indication. If during the active SIP session an update of the CSK is required, the server generates a CSK and provides it to the client using the mechanism defined in clause 5.8." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 9.2.1] "The CSK is initially distributed via the 'CSK upload' procedure as defined in clause 5.4. The 'CSK upload' procedure creates a security association between the MC client and the MCX Server and occurs during the client's initial connection with the MC Server. The following steps describe how the client obtains the user specific key material and securely transfers the CSK to a server within the MC domain. Prior to beginning of this procedure, the client would have obtained user-specific key material from the KMS. 1) The client randomly generates the CSK and encapsulates the CSK as described in clause 5.4. 2) The client includes the encapsulated CSK in its initial SIP REGISTER or in a SIP PUBLISH message that is used to perform the MC user authorization procedure, and sends the SIP message addressed to the PSI of the server. An illustration is provided below as an example of how this message in included in the body of the SIP REGISTER message. The MIME media type "application/mikey" IETF RFC 3830 [22] is used in this example to insert a MIKEY I_MESSAGE in the SIP payload: … The following steps describe how the MCX Server retrieves the CSK from the SIP message: 1) The server receives the SIP message and decrypts the encapsulated the CSK as described in clause 5.4. 2) Once the CSK has been extracted, MC user specific information (e.g. the access token) protected in the SIP message as defined in clause 9.3.4, may be decrypted." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 40 |
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.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo Server) consists of all sub-systems of the Common Services Core, including the Group Management Server, the Configuration Management Server, the Key Management Server, the Identity Management Server, the HTTP Server, and the SIP AS. The IUT (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1. - The IUT (MCVideo Server) is connected to the SS-UE1 (MCVideo Client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCVideo". |
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) including the initial UE configuration document? <-- HTTP 200 (OK) 1 P 0C The SS-UE1 (MCVideo Client) establishes a secure TLS tunnel as specified by ETSI TS 133 310 [6] (3GPP TS 33.310) to the authorisation endpoint of the IdM server as specified in ETSI TS 133 180 [7] (3GPP TS 33.180) using the configured URL of the authorisation endpoint of the IdM server as specified in the "<x>/OnNetwork/AppServerInfo/IDMSAuthEndpoint" leaf node, Table 5.5.8.1-1, ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). - - - - 1 The SS-UE1 (MCVideo Client) sends an OpenID Connect Authentication Request using HTTP POST --> HTTP POST (Authorization) - - 2 Check: Does the IUT (MCVideo Server) respond by sending an HTTP 200 (OK) including the HTML form requesting username and password? <-- HTTP 200 (OK) 1 P 3 The SS-UE1 (MCVideo Client) sends an HTTP POST Request message to the IUT (MCVideo Server) containing username and password --> HTTP POST - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 41 St Procedure Message Sequence TP Verdict U - S Message 4 Check: Does the IUT (MCVideo Server) send an HTTP 302 (Found) as the OpenID Connect Authentication Response? <-- HTTP 302 (Found) 1 P 5 The SS-UE1 (MCVideo Client) establishes a secure TLS tunnel as specified by ETSI TS 133 310 [6] (3GPP TS 33.310) to the token endpoint of the IdM server as specified in ETSI TS 133 180 [7] (3GPP TS 33.180) using the configured URL of the token endpoint of the IdM server as specified in the "/<x>/OnNetwork/AppServerInfo/IDMSTokenEndpoint" leaf node, Table 5.5.8.1-1, ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) - - - - 6 The SS-UE1 (MCVideo Client) sends an HTTP POST Request message to the IUT (MCVideo Server) over the TLS connection established to the IdM token endpoint (OIDC Token Request message) passing the authorization code sent in step 4. --> HTTP POST - - 7 Check: Does the IUT (MCVideo Server) send an HTTP 200 (OK) providing id_token, access_token and refresh token? <-- HTTP 200 (OK) 1 P 7A The SS-UE1 (MCVideo Client) establishes a secure TLS tunnel as specified by ETSI TS 133 310 [6] (3GPP TS 33.310) to the HTTP Proxy as specified in ETSI TS 133 180 [7] (3GPP TS 33.180) using the configured URL of the HTTP Proxy as specified in the "/<x>/OnNetwork/AppServerInfo/HTTPproxy" leaf node, Table 5.5.8.1-1, ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) - - - - 8 The SS-UE1 (MCVideo Client) sends an HTTP POST message presenting an access token sent in step 7 for Key Management Initialisation. --> HTTP POST - - 9 Check: Does the IUT (MCVideo Server) respond by sending identity-specific key information? <-- HTTP 200 (OK) 2 P 10 The SS-UE1 (MCVideo Client) sends an HTTP POST message presenting an access token for Key Material Request --> HTTP POST - - 11 Check: Does the IUT (MCVideo Server) respond by sending identity-specific key information? <-- HTTP 200 (OK) 2 P 12 The SS-UE1 (MCVideo Client) sends a SIP REGISTER request for service authorisation --> SIP REGISTER - - 13 Check: Does the IUT (MCVideo Server) respond by sending an SIP 200 (OK) message? <-- SIP 200 (OK) 3 P 14 The SS-UE1 (MCVideo Client) sends a SIP SUBSCRIBE - subscription to multiple documents simultaneously - containing the access token and a resource list mime body containing a list of the following documents: MCVideo UE Configuration document, MCVideo User Profile Configuration Document, and the MCVideo Service configuration document. The base URI of each list entry is set to the CMS XCAP-ROOT-URI --> SIP SUBSCRIBE - - 15 Check: Does the IUT (MCVideo Server) respond by sending an SIP 200 (OK) message? <-- SIP 200 (OK) 4 P 16 Check: Does the IUT (MCVideo Server) send a SIP NOTIFY message containing the XCAP-URI of the documents? <-- SIP NOTIFY 4 P 17 The SS-UE1 (MCVideo Client) responds with a SIP 200 (OK) message --> SIP 200 (OK) - - 18 The SS-UE1 (MCVideo Client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the MCVideo UE Configuration document --> HTTP GET - - 19 Check: Does the IUT (MCVideo Server) send the HTTP 200 (OK) message including the MCVideo UE Configuration Document? <-- HTTP 200 (OK) 4 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 42 St Procedure Message Sequence TP Verdict U - S Message 20 The SS-UE1 (MCVideo Client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the MCVideo User Profile Configuration Document --> HTTP GET - - 21 Check: Does the IUT (MCVideo Server) send the HTTP 200 (OK) message including the MCVideo User Profile Configuration Document? <-- HTTP 200 (OK) 4 P 22 The SS-UE1 (MCVideo Client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the MCVideo Service Configuration Document --> HTTP GET - - 23 Check: Does the IUT (MCVideo Server) send the HTTP 200 (OK) message including the MCVideo Service Configuration Document? <-- HTTP 200 (OK) 4 P 24 The SS-UE1 (MCVideo Client) sends a SIP SUBSCRIBE containing the access token and a resource list mime body and a list of the Groups to be obtained. The base URI of each list entry is set to the GMS XCAP-ROOT-URI, and the MCVideo group ID identifies a group document --> SIP SUBSCRIBE - - 25 Check: Does the IUT (MCVideo Server) respond with a HTTP 200 (OK) message <-- SIP 200 (OK) 5 P 26 Check: Does the IUT (MCVideo Server) send a SIP NOTIFY message to the UE that contains the XCAP- URI of the Group documents? <-- SIP NOTIFY 5 P 27 The SS-UE1 (MCVideo Client) sends a SIP 200 (OK) message --> SIP 200 (OK) - - 28 The SS-UE1 (MCVideo Client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the Group Configuration document --> HTTP GET - - 29 Check: Does the IUT (MCVideo Server) send an HTTP 200 (OK) message including the Group Document 'MCVideo UE Configuration document'? <-- HTTP 200 (OK) 5 P 29A Check: Does the IUT (MCVideo Server) send a SIP NOTIFY message to the UE that contains the group key transport payloads (GKTP) document. <-- SIP NOTIFY 5 P 29B The SS-UE1 (MCVideo Client) sends a SIP 200 (OK) message --> SIP 200 (OK) - - 30 The SS-UE1 (MCVideo Client) sends a SIP PUBLISH request for update of PoC-settings. NOTE: The PoC-settings document contains the user profile index of the selected user profile. --> SIP PUBLISH - - 31 Check: Does the IUT (MCVideo Server) send a SIP 200 (OK)? <-- SIP 200 (OK) 6 P |
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 (Step 6, 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 TOKEN ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 43 Table 5.1.3.3-4: HTTP POST (Step 8, 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 KMSINIT. Table 5.1.3.3-5: HTTP POST (Step 10, 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 KMSKEY. Table 5.1.3.3-5A: HTTP 200 (OK) (Step 0B, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition UEINITIALCONFIG Table 5.1.3.3-6: HTTP 200 (OK) (Step 2, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1 Information Element Value/remark Comment Reference Condition Content-Type media-type "text/html" IETF RFC 2854 [12] Message-body HTML form <!DOCTYPE html> <html> <body> <form action="/idms/userauth" method="post"> Username: <input type="text" name="user"><br> Password: <input type="password" name="password"><button type="submit">Login</button> </form> </body> </html> "/idms/userauth" given by tsc_MCX_IdMS_user auth_UriPath is the URI to be used by the UE as request URI in the HTTP POST request for user authentication HTML 4.01 Specification [13] Table 5.1.3.3-7: HTTP 200 (OK) (Step 7, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition TOKEN Table 5.1.3.3-8: HTTP 200 (OK) (Step 9, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition KMSINIT. Table 5.1.3.3-9: HTTP 200 (OK) (Step 11, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition KMSKEY. Table 5.1.3.3-10: HTTP 200 (OK) (Step 19, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, conditions MCVIDEO and UECONFIG. Table 5.1.3.3-11: HTTP 200 (OK) (Step 21, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, conditions MCVIDEO and UEUSERPROF. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 44 Table 5.1.3.3-12: HTTP 200 (OK) (Step 23, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, conditions MCVIDEO and UESERVCONFIG. Table 5.1.3.3-13: HTTP 200 (OK) (Step 29, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition GROUPCONFIG. Table 5.1.3.3-14: HTTP 302 (Found) (Step 4, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.8-1, condition AUTH. Table 5.1.3.3-14A: HTTP GET (Step 0A, Table 5.1.3.2-1) Derivation Path: Table 5.5.4.2-1, condition UEINITIALCONFIG Table 5.1.3.3-15: HTTP GET (Step 18, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.2-1, conditions MCVIDEO and UECONFIG. Table 5.1.3.3-16: HTTP GET (Step 20, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.2-1, conditions MCVIDEO and UEUSERPROF. Table 5.1.3.3-17: HTTP GET (Step 22, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.2-1, conditions MCVIDEO and UESERVCONFIG. Table 5.1.3.3-18: HTTP GET (Step 28, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.2-1, condition GROUPCONFIG Table 5.1.3.3-19: SIP REGISTER (Step 12, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.13-1, condition SIP_REGISTER_INITIAL, CONFIG Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCVideo_PublicSer viceId_B SIP URI of the home domain name Table 5.1.3.3-20: SIP SUBSCRIBE (Step 14, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1, condition CONFIG ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 45 Table 5.1.3.3-20A: SIP SUBSCRIBE (Step 24, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1, condition GROUPCONFIG Information Element Value/remark Comment Reference Condition Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 5.1.3.3-20B Table 5.1.3.3-20B: Resource-lists in SIP SUBSCRIBE (Table 5.1.3.3-20A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1A-1, condition GROUPCONFIG Table 5.1.3.3-21: SIP NOTIFY (Step 16, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, condition CONFIG Information Element Value/remark Comment Reference Condition Contact addr-spec user-info and host tsc_MCVideo_PublicServiceId_B Table 5.1.3.3-21A: SIP NOTIFY (Step 26, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, condition GROUPCONFIG Information Element Value/remark Comment Reference Condition Contact addr-spec user-info and host tsc_MCVideo_PublicServiceId_B Table 5.1.3.3-21B: SIP NOTIFY (Step 29A, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, condition GROUPCONFIG Information Element Value/remark Comment Reference Condition Contact addr-spec user-info and host tsc_MCVideo_PublicServiceId_ B Message-body xcap-diff document xcap-diff document as described in Table 5.1.3.3-21C Table 5.1.3.3-21C: Xcap-Diff Document (Table 5.1.3.3-21B) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.12-2, condition GROUPKEY Table 5.1.3.3-22: SIP PUBLISH (Step 30, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.11-1, conditions MCVIDEO and POC- SETTINGS-EVENT Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCVideo_PublicServi ceId_B The public service identity identifying the originating participating MCVideo function serving the MCVideo user ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 46 Table 5.1.3.3-23: SIP 200 (OK) (Steps 13, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 condition REGISTER-RSP Information Element Value/remark Comment Reference Condition Table 5.1.3.3-24: SIP 200 (OK) (Steps 15, 25, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 condition SUBSCRIBE-RSP Information Element Value/remark Comment Reference Condition Contact addr-spec user-info and host tsc_MCVideo_PublicServiceId_B Table 5.1.3.3-25: SIP 200 (OK) (Step 31, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 condition PUBLISH-RSP Information Element Value/remark Comment Reference Condition 5.2 MCVIDEO Server - MCVIDEO Client / Configuration / Group Creation / Group Regroup Creation / Group Regroup Teardown |
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 { IUT (MCVideo Server) having establish terminated group } ensure that { when { the SS-UE1 (MCVideo Client) initiates creation of the terminated temporary group by sending a HTTP POST request } then { IUT (MCVideo Server) responds with a HTTP 200 (OK) containing the GMOP group-regroup- creation-response } } (3) with { IUT (MCVideo Server) having establish a temporary group } ensure that { when { the SS-UE1 (MCVideo Client) initiates tear down of the temporary group by sending a HTTP DELETE request } then { IUT (MCVideo Server) responds to the UE (MCVideo Client) with HTTP 200 (OK) message } } |
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 these are Rel-14 requirements. [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 5.4] "To be compliant with the procedures in the present document, an MCVideo server shall support role of an MCS server as specified in subclause 5.2A." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 47 [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 5.2A] "To be compliant with the procedures in the present document, an MCS server: - shall support the role of XCAP client as specified in IETF RFC 4825 [22]; - shall support the role of XDMC as specified in OMA OMA-TS-XDM_Group-V1_1_1 [3]; - shall support the procedure in subclause 6.2.4; - shall support the procedure in subclause 6.3.3.2.3; and - shall support the procedure in subclause 6.3.13.2.2." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.2.4] "The MCS server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.482 [10]. The MCS server shall perform the procedures in subclause 6.2.2 specified for GC." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.3.3.3] "A GMS shall support handling an HTTP GET request from a GMC according to procedures specified in IETF RFC 4825 [22] "GET Handling" where the Request-URI of the HTTP GET request identifies an XML document of the application usage specified in subclause 7.2." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.3.13.3.2.2] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI set to own public service identity for performing subscription proxy function of the GMS; c) with a P-Asserted-Identity header field not containing an identity listed in the authorized MCS server list specified in subclause 6.2.5.1 and not containing an identity listed in the authorized GMS list as specified in subclause 6.2.5.1; d) with an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-access-token> element; e) with an application/resource-lists+xml MIME body; and f) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; the GMS: a) if an <EncryptedData> XML tag is included in the application/vnd.3gpp.mcptt-info+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/vnd.3gpp.mcptt-info+xml MIME body; b) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; c) shall identify the originating MCS ID from <mcptt-access-token> element received in the application/vnd.3gpp.mcptt-info+xml MIME body and shall use the originating MCS ID as an authenticated identity when performing the authorization; d) if the authenticated identity is not authorized to subscribe to notification of changes of any resource in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 48 e) act as a notifier according to IETF RFC 5875 [13]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the initial SIP SUBSCRIBE request identifies: 1) a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is an MCS group ID owned by an MCS provider other than the MCS provider of the GMS; or 2) a element of an MCS GKTP document as described in subclause 7.7.10 where the group ID is an MCS group ID owned by an MCS provider other than the MCS provider of GMS; shall perform the procedure in subclause 6.3.13.3.2.4 for each such MCS group ID and shall interwork information of received SIP NOTIFY requests in subclause 6.3.13.3.2.4 in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request. Upon sending a SIP NOTIFY request associated with a subscription created as result of the received initial SIP SUBSCRIBE request, if the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, the GMS shall perform the confidentiality protection procedures and integrity protection procedures defined in 3GPP TS 24.379 [5] for MCS server. Upon reception of a SIP re-SUBSCRIBE request: a) with the Event header field set to xcap-diff; and b) with an application/resource-lists+xml MIME body; the GMS: a) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body of the received SIP re-SUBSCRIBE request and the CSK was received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; and b) act as a notifier according to IETF RFC 5875 [13]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the SIP re-SUBSCRIBE request identifies: 1) a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is an MCS group ID owned by an MCS provider other than the MCS provider of the GMS; or 2) a element of an MCS GKTP document as described in subclause 7.7.10 where the group ID is an MCS group ID owned by an MCS provider other than the MCS provider of GMS; and for which there is no related subscription established according to the subclause 6.3.13.3.2.4, shall perform the procedure in subclause 6.3.13.3.2.4 for each such MCS group ID and shall interwork information of received SIP NOTIFY requests in subclause 6.3.13.3.2.4 in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.3.13.3.3] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI set to own public service identity for accessing documents; c) with a P-Asserted-Identity header field containing an identity listed in the authorized GMS list as specified in subclause 6.2.5.1; d) with an application/resource-lists+xml MIME body; e) with an application/vnd.3gpp.mcptt-info+xml MIME body; and f) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 49 the GMS: a) if the <mcptt-calling-user-id> element is included in the application/vnd.3gpp.mcptt-info+xml MIME body: 1) shall use the <mcptt-calling-user-id> element value as an authenticated identity when performing the authorization; and 2) if the authenticated identity is not authorized to subscribe to notification of changes of any document or element in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; b) if the <mcptt-calling-group-id> element is included in the application/vnd.3gpp.mcptt-info+xml MIME body: 1) when performing the authorization, shall use URI of the P-Asserted-Identity header field as an authenticated identity and shall determine that the subscription is on behalf of the identity in the <mcptt- calling-group-id> element; 2) if the authenticated identity is not authorized to subscribe to notification of changes of any document or element in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; and 3) if the MCS group ID indicated in the <mcptt-calling-group-id> element is a constituent MCS group of a temporary MCS group and the documents or elements indicated in the application/resource-lists+xml MIME body are not associated with the temporary MCS group ID, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; and c) shall act as a notifier according to IETF RFC 5875 [13]." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 7.2.12.1] "Authorization policies are described in the OMA OMA-TS-XDM_Group-V1_1_1 [3] "Authorization policies". An authenticated identity is authorized to read the <group> element of an MCS group document. An authenticated identity is authorized to read a <list-service> element of the <group> element of the MCS group document and any descendant elements of the <list-service> element: a) except a <list> element of the <list-service> element; and b) except descendant elements of the <list> element of the <list-service> element; if the authenticated identity is a member of an MCS group defined by the <list-service> element. An authenticated identity is authorized to read a <list> element of a <list-service> element of the <group> element of an MCS group document and any descendant elements of the <list> element if: a) the authenticated identity is a member of MCS group defined by the <list-service> element; and b) the MCS group document contains a <rule> element: 1) with the <conditions> element evaluating to true for the authenticated identity or without the <conditions> element; and 2) with the <actions> element containing the <on-network-allow-getting-member-list> element. An authenticated identity is authorized to read an <entry> element of a <list> element of a <list-service> element of the <group> element of the MCS group document and any descendant elements of the <entry> element if: a) the "uri" attribute of the <entry> element contains the authenticated identity; b) the "uri" attribute of the <mcvideo-mcvideo-id> element of the <entry> element contains the authenticated identity; or c) the "uri" attribute of the <mcdata-mcdata-id> element of the <entry> element contains the authenticated identity. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 50 An authenticated identity is authorized to read an MCS group document if the authenticated identity is listed in the authorized MCS server list specified in subclause 6.2.5.1. An authenticated identity is authorized to create, read, modify and delete an MCS group document if the MCS group document is stored: a) in users tree of the XUI equal to the authenticated identity; or b) in users tree of the another XUI, subject to MCS service provider policy. The MCS service provider policy can specified e.g. using an appropriate access permissions document specified in OMA OMA-TS-XDM_Core- V2_1 [2], stored in the user's tree of the other XUI; and unless precluded by other statement of this subclause. None is authorized to create, delete, and modify a <on-network-temporary> element of a <list-service> element of the <group> element of an existing MCS group document. None is authorized to delete a group document containing a <on-network-regrouped> element of a <list-service> element of the <group> element of an MCS group document. An authenticated identity is authorized to create and delete a <on-network-regrouped> element in the <list-service> element of the <group> element of an existing MCS group document if the authenticated identity is in authorized GMS list specified in subclause 6.2.5.1. An authenticated identity is authorized to subscribe to notification of changes of an MCS group document if: 1) the authenticated identity is a member of an MCS group defined by a <list-service> element of the <group> element of the MCS group document; 2) the authenticated identity is listed in the authorized MCS server list specified in subclause 6.2.5.1; or 3) the authenticated identity is listed in the authorized GMS list specified in subclause 6.2.5.1 and the subscription is on behalf of a constituent MCS group of the MCS group defined by the MCS group document." [ETSI TS 124 481 [29] (3GPP TS 24.481) clause 6.3.2.3] "Upon reception of an HTTP PUT request where the Request-URI of the HTTP PUT request identifies an XML document of the application usage specified in subclause 7.2 then the GMS: a) shall determine the identity of the sender of the received HTTP PUT request as specified in subclause 6.2.5; b) if the identity of the sender of the received HTTP PUT request is not authorized to initiate group creation, shall respond with a HTTP 403 (Forbidden) response to the HTTP PUT request and shall not continue with rest of the steps; c) if value of the "uri" attribute of the <list-service> element of the <group> element of the XML document specified in subclause 7.2.1 of the received HTTP PUT request does not conform to local policy, shall respond with an HTTP 409 (Conflict) response to the HTTP PUT request. The <uniqueness-failure> error element shall identify the error condition. The GMS shall include at least one <alt-value> element in the <uniqueness- failure> error element, whereby each <alt-value> element contains an MCS Group ID acceptable for the GMS. The GMS shall not continue with rest of the steps; and d) shall support receiving an XML document of the application usage specified in subclause 7.2.1 according to procedures specified in IETF RFC 4825 [22] "PUT Handling" where the Request-URI of the HTTP PUT request identifies an XML document of the application usage specified in subclause 7.2." [ETSI TS 124 481 [29] (3GPP TS 24.481) clause 6.3.14.3.1] "Upon reception of an HTTP POST request: a) with a Request-URI with an XCAP URI identifying a non-existing group document; and b) with an application/vnd.3gpp.GMOP+xml MIME body containing a GMOP document requesting group regroup creation specified in subclause 7.3.4.3; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 51 then the GMS: a) shall determine the identity of the sender of the received HTTP POST request as specified in subclause 6.2.5; … d) for each MCS group ID of an MCS group to be combined indicated in content of a <constituent-MCPTT- group-ID> element of the <constituent-MCPTT-group-IDs> element of the <on-network-temporary> element of the group document of the <group> element of the GMOP document requesting group regroup creation specified in subclause 7.3.4.3 of the received HTTP POST request: 1) shall send a HTTP POST request according to procedures specified in IETF RFC 2616 [21] and subclause 6.2.5. In the HTTP POST request, the GMS: A) shall set the Request-URI to an XCAP URI: i) with the document selector identifying a group document addressed by a group ID as specified in subclause 7.2.10.2, where the group ID is set to the MCS group ID of the MCS group to be combined; ii) with the node selector identifying a <on-network-regrouped> element of the constituent MCS group such that the <on-network-regrouped> element has the "temporary-MCPTT-group- ID" attribute set to the content of the "uri" attribute of the <list-service> element of the group document included in the received HTTP POST request; iii) if the MCS group ID of the MCS group to be combined is owned by the MCS provider of the GMS, with the XCAP root URI of the MCS provider of the GMS; and iv) if the MCS group ID of the MCS group to be combined is owned by an MCS provider other than the MCS provider of the GMS, with XCAP root URI derived using the group ID routing database as specified in subclause 6.2.5.2 and the MCS group ID of the MCS group to be combined; B) shall set the X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.482 [10] to a public service identity of the GMS; and C) shall include an application/vnd.3gpp.GMOP+xml MIME body containing a GMOP document requesting group regroup check specified in subclause 7.3.4.4 with a <on-network-regrouped> element. In the <on-network-regrouped> element, the GMS: i) shall set the "temporary-MCPTT-group-ID" attribute to the content of the "uri" attribute of the <list-service> element of the group document included in the received HTTP POST request; ii) shall set the "temporary-MCPTT-group-requestor" attribute to the identity of the sender of the received HTTP POST request; iii) shall include the <constituent-MCPTT-group-IDs> element set to content of the <constituent-MCPTT-group-IDs> element of <on-network-temporary> element of the <list- service> element of the group document of the MCS group included in the received HTTP POST request; iv) if an <on-network-group-priority> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <on- network-group-priority> element set to content of the <on-network-group-priority> element of the <list-service> element of the group document included in the received HTTP POST request; v) if a <protect-media> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <protect-media> element set to content of the <protect-media> element of the <list-service> element of the group document included in the received HTTP POST request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 52 vi) if a <protect-floor-control-signalling> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <protect- floor-control-signalling> element set to content of the <protect-floor-control-signalling> element of the <list-service> element of the group document included in the received HTTP POST request; and vii) if a <require-multicast-floor-control-signalling> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <require-multicast-floor-control-signalling> element. … Upon reception of HTTP 2xx responses to all sent HTTP POST requests, the GMS: a) for each MCS group ID of an MCS group to be combined indicated in content of a <constituent-MCPTT- group-ID> element of the <constituent-MCPTT-group-IDs> element of the <on-network-temporary> element of the <group> element of the GMOP document requesting group regroup creation specified in subclause 7.3.4.3 of the received HTTP POST request: 1) shall send an HTTP POST request according to procedures specified in IETF RFC 2616 [21] and subclause 6.2.5. In the HTTP POST request, the GMS: A) shall set the Request-URI to an XCAP URI: i) with the document selector identifying a group document addressed by a group ID as specified in subclause 7.2.10.2, where the group ID is set to the MCS group ID of the MCS group to be combined; ii) with the node selector identifying a <on-network-regrouped> element of the constituent MCS group such that the <on-network-regrouped> element has the "temporary-MCPTT-group- ID" attribute set to the content of the "uri" attribute of the <list-service> element of the group document included in the received HTTP POST request; iii) if the MCS group ID of the MCS group to be combined is owned by the MCS provider of the GMS, with the XCAP root URI of the MCS provider of the GMS; and iv) if the MCS group ID of the MCS group to be combined is owned by an MCS provider other than the MCS provider of the GMS, with XCAP root URI derived using the group ID routing database as specified in subclause 6.2.5.2 and the MCS group ID of the MCS group to be combined; B) shall set the X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.482 [10] to a public service identity of the GMS; and C) shall include an application/vnd.3gpp.GMOP+xml MIME body with a GMOP document requesting group regroup notification specified in subclause 7.3.4.5. In the GMOP document requesting group regroup notification, the GMS: i) shall include a <on-network-regrouped> element. In the <on-network-regrouped> element, the GMS: - shall set the "temporary-MCPTT-group-ID" attribute to the content of the "uri" attribute of the <list-service> element of the group document included in the received HTTP POST request; - shall set the "temporary-MCPTT-group-requestor" attribute to the identity of the sender of the received HTTP POST request; - shall include the <constituent-MCPTT-group-IDs> element set to content of the <constituent-MCPTT-group-IDs> element of <on-network-temporary> element of the <list-service> element of the group document of the MCS group included in the received HTTP POST request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 53 - if an <on-network-group-priority> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <on-network-group-priority> element set to content of the <on-network-group- priority> element of the <list-service> element of the group document included in the received HTTP POST request; - if a <protect-media> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <protect- media> element set to content of the <protect-media> element of the <list-service> element of the group document included in the received HTTP POST request; - if a <protect-floor-control-signalling> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <protect-floor-control-signalling> element set to content of the <protect-floor-control- signalling> element of the <list-service> element of the group document included in the received HTTP POST request; and - if a <require-multicast-floor-control-signalling> element is included in the <list- service> element of the group document included in the received HTTP POST request, shall include the <require-multicast-floor-control-signalling> element. NOTE: GMK is not included in the GMOP document requesting group regroup notification as GMK is provided only using SIP. Upon reception of HTTP 2xx responses to all sent HTTP POST requests, the GMS shall create the group document of the temporary MCS group at the location specified by the Request-URI of the received HTTP POST request and shall send an HTTP 2xx response to the received HTTP request. In the HTTP 2xx response, the GMS shall include an application/vnd.3gpp.GMOP+xml MIME body containing a GMOP document with group regroup creation response specified in subclause 7.3.4.6 with a <temporary-group-document-ETag> element set to the current value of the entity tag for the created group document of the temporary MCS group." [ETSI TS 124 481 [29] (3GPP TS 24.481) clause 6.3.15.3.1] "Upon reception of an HTTP DELETE request with Request-URI with an XCAP URI identifying a group document of a temporary MCS group, the GMS: a) for each constituent MCS group indicated in the group document indicated by Request-URI: 1) shall send an HTTP DELETE request. In the HTTP DELETE request, the GMS: A) shall set the Request-URI to an XCAP URI: i) with the document selector identifying a group document addressed by a group ID as specified in subclause 7.2.10.2, where the group ID is set to the MCS group ID of the constituent MCS group; ii) with the node selector identifying a <on-network-regrouped> element of the constituent MCS group, such that the "temporary-MCPTT-group-ID" attribute of the <on-network- regrouped> element contains the temporary MCS group ID of the temporary MCS group; iii) if the MCS group ID of the constituent MCS group is owned by the MCS provider of the GMS, with the XCAP root URI of the MCS provider of the GMS; and iv) if the MCS group ID of the constituent MCS group is owned by an MCS provider other than the MCS provider of the GMS, with XCAP root URI derived using the group ID routing database as specified in subclause 6.2.5.2 and the MCS group ID of the constituent MCS group; and B) shall set the X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.482 [10] to a public service identity of the GMS. Upon reception of an HTTP response to all sent HTTP DELETE requests, the GMS shall remove the group document of the temporary MCS group and shall send an HTTP 2xx response to the received HTTP request." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 54 |
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.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo Server) consists of all sub-systems of the Common Services Core, including the Group Management Server, the Configuration Management Server, the Key Management Server, the Identity Management Server, the HTTP Server, and the SIP AS. The IUT (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Group Management Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The IUT (MCVideo Server) is connected to the SS-UE1 (MCVideo Client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCVideo". - The SS-UE1 (MCVideo Client) performs the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in subclause 5.1. - The SS-UE1 (MCVideo Client) is member of group A. |
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 procedure 'MCX Server Terminated Temporary Group Creation' as described in Annex A, Table A.2.5.3-1 to create temporary group T? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Server Originated notifications regarding temporary group creation or tear down' as described in Annex A, Table A.2.3.3-1 to update the group document of group A and retrieve the GMK for the temporary group T? - - 2 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 55 St Procedure Message Sequence TP Verdict U - S Message 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Server Terminated Temporary Group Tear Down' as described in Annex A, Table A.2.6.3-1 to delete temporary group T? - - 3 P 5 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Server Originated notifications regarding temporary group creation or tear down' as described in Annex A, Table A.2.3.3-1 to update the group document and the GKTP document of group A? - - 3 P |
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 Affiliation / Remote change / De- affiliation / Home MCVIDEO system |
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 subscribe to affiliation status changes for the MCVideo User with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (2) 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 to de-affiliate user A from an MCVideo group with SIP PUBLISH } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (3) 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 to affiliate user A to an MCVideo group with SIP PUBLISH message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 56 (4) 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-UE2 (MCVideo Client) requests to de-affiliate user B from an MCVideo group with SIP PUBLISH message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (5) 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 allowed to make affiliation changes for another user with the specified group } ensure that { when { the SS-UE1 (MCVideo client ) requests to affiliate status changes of targeted user with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (6) 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 allowed to make affiliation changes for another user with the specified group } ensure that { when { the SS-UE1 (MCVideo Client) requests to affiliate targeted user B to an MCVideo group via mandatory mode with SIP PUBLISH message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (7) 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 allowed to make affiliation changes for another user with the specified group } ensure that { when { the SS-UE1 (MCVideo Client) requests to de-affiliate targeted user from an MCVideo group via mandatory mode with SIP PUBLISH message } then { IUT (MCVideo Server) responds to the SS-UE1 (MCVideo Client) with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (8) 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 allowed to make affiliation changes for another user with the specified group } ensure that { when { SS-UE1 (MCVideo Client) requests that a target user B be affiliated to an MCVideo group via negotiated mode by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } (9) with { MCVideo Client already affiliated to the MCVideo group } ensure that { when { the SS-UE1 (MCVideo Client) requests to affiliate targeted user to a group via negotiated mode } then { IUT (MCVideo Server) informs user B about a remote request by sending a SIP MESSAGE message to the SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 57 (10) 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-UE2 (MCVideo Client) requests to affiliate user B to an MCVideo group with SIP PUBLISH message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (11) 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 allowed to make affiliation changes for another user with the specified group } ensure that { when { SS-UE1 (MCVideo Client) requests that a target user B be de-affiliated to an MCVideo group via negotiated mode by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } (12) with { MCVideo Client already de-affiliated from the MCVideo group } ensure that { when { the SS-UE1 (MCVideo Client) requests to de-affiliate targeted user to a group via negotiated mode } then { IUT (MCVideo Server) informs user B about a remote request by sending a SIP MESSAGE message to the SS-UE2 (MCVideo Client) } } (13) 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 to de-subscribe from affiliation status changes for the MCVideo User with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } |
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 stated these are Rel-14 requirements. [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 5.4] "To be compliant with the procedures in the present document, an MCVideo server shall support role of an MCS server as specified in subclause 5.2A." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 5.2A] "To be compliant with the procedures in the present document, an MCS server: - shall support the role of XCAP client as specified in IETF RFC 4825 [22]; - shall support the role of XDMC as specified in OMA OMA-TS-XDM_Group-V1_1_1 [3]; - shall support the procedure in subclause 6.2.4; - shall support the procedure in subclause 6.3.3.2.3; and - shall support the procedure in subclause 6.3.13.2.2." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 58 [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.2.4] "The MCPTT server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.382 [10]. The MCPTT server shall perform the procedures in subclause 6.2.2 specified for GC." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.3.3.3] "A GMS shall support handling an HTTP GET request from a GMC according to procedures specified in IETF RFC 4825 [22] "GET Handling" where the Request-URI of the HTTP GET request identifies an XML document of the application usage specified in subclause 7.2." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.3.13.3.2.2] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI set to own public service identity for performing subscription proxy function of the GMS; c) with a P-Asserted-Identity header field not containing an identity listed in the authorized MCPTT server list specified in subclause 6.2.5.1 and not containing an identity listed in the authorized GMS list as specified in subclause 6.2.5.1; d) with an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-access-token> element; e) with an application/resource-lists+xml MIME body; and f) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; the GMS: a) if an <EncryptedData> XML tag is included in the application/vnd.3gpp.mcptt-info+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/vnd.3gpp.mcptt-info+xml MIME body; b) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; c) shall identify the originating MCPTT ID from <mcptt-access-token> element received in the application/vnd.3gpp.mcptt-info+xml MIME body and shall use the originating MCPTT ID as an authenticated identity when performing the authorization; d) if the authenticated identity is not authorized to subscribe to notification of changes of any resource in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; e) act as a notifier according to IETF RFC 5875 [13]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the initial SIP SUBSCRIBE request identifies: 1) a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is an MCPTT group ID owned by an MCPTT provider other than the MCPTT provider of the GMS; or 2) a element of an MCPTT GKTP document as described in subclause 7.7.10 where the group ID is an MCPTT group ID owned by an MCPTT provider other than the MCPTT provider of GMS; shall perform the procedure in subclause 6.3.13.3.2.4 for each such MCPTT group ID and shall interwork information of received SIP NOTIFY requests in subclause 6.3.13.3.2.4 in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 59 Upon sending a SIP NOTIFY request associated with a subscription created as result of the received initial SIP SUBSCRIBE request, if the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, the GMS shall perform the confidentiality protection procedures and integrity protection procedures defined in 3GPP TS 24.379 [5] for MCPTT server. Upon reception of a SIP re-SUBSCRIBE request: a) with the Event header field set to xcap-diff; and b) with an application/resource-lists+xml MIME body; the GMS: a) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body of the received SIP re-SUBSCRIBE request and the CSK was received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; and b) act as a notifier according to IETF RFC 5875 [13]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the SIP re-SUBSCRIBE request identifies: 1) a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is an MCPTT group ID owned by an MCPTT provider other than the MCPTT provider of the GMS; or 2) a element of an MCPTT GKTP document as described in subclause 7.7.10 where the group ID is an MCPTT group ID owned by an MCPTT provider other than the MCPTT provider of GMS; and for which there is no related subscription established according to the subclause 6.3.13.3.2.4, shall perform the procedure in subclause 6.3.13.3.2.4 for each such MCPTT group ID and shall interwork information of received SIP NOTIFY requests in subclause 6.3.13.3.2.4 in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 6.3.13.3.3] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI set to own public service identity for accessing documents; c) with a P-Asserted-Identity header field containing an identity listed in the authorized GMS list as specified in subclause 6.2.5.1; d) with an application/resource-lists+xml MIME body; e) with an application/vnd.3gpp.mcptt-info+xml MIME body; and f) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; the GMS: a) if the <mcptt-calling-user-id> element is included in the application/vnd.3gpp.mcptt-info+xml MIME body: 1) shall use the <mcptt-calling-user-id> element value as an authenticated identity when performing the authorization; and 2) if the authenticated identity is not authorized to subscribe to notification of changes of any document or element in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; b) if the <mcptt-calling-group-id> element is included in the application/vnd.3gpp.mcptt-info+xml MIME body: 1) when performing the authorization, shall use URI of the P-Asserted-Identity header field as an authenticated identity and shall determine that the subscription is on behalf of the identity in the <mcptt- calling-group-id> element; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 60 2) if the authenticated identity is not authorized to subscribe to notification of changes of any document or element in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; and 3) if the MCS group ID indicated in the <mcptt-calling-group-id> element is a constituent MCS group of a temporary MCS group and the documents or elements indicated in the application/resource-lists+xml MIME body are not associated with the temporary MCS group ID, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; and c) shall act as a notifier according to IETF RFC 5875 [13]." [ETSI TS 124 481 [29] (3GPP TS 24.481), clause 7.2.12.1] "Authorization policies are described in the OMA OMA-TS-XDM_Group-V1_1_1 [3] "Authorization policies". An authenticated identity is authorized to read the <group> element of an MCS group document. An authenticated identity is authorized to read a <list-service> element of the <group> element of the MCS group document and any descendant elements of the <list-service> element: a) except a <list> element of the <list-service> element; and b) except descendant elements of the <list> element of the <list-service> element; if the authenticated identity is a member of an MCS group defined by the <list-service> element. An authenticated identity is authorized to read a <list> element of a <list-service> element of the <group> element of an MCS group document and any descendant elements of the <list> element if: a) the authenticated identity is a member of MCS group defined by the <list-service> element; and b) the MCS group document contains a <rule> element: 1) with the <conditions> element evaluating to true for the authenticated identity or without the <conditions> element; and 2) with the <actions> element containing the <on-network-allow-getting-member-list> element. An authenticated identity is authorized to read an <entry> element of a <list> element of a <list-service> element of the <group> element of the MCS group document and any descendant elements of the <entry> element if: a) the "uri" attribute of the <entry> element contains the authenticated identity; b) the "uri" attribute of the <mcvideo-mcvideo-id> element of the <entry> element contains the authenticated identity; or c) the "uri" attribute of the <mcdata-mcdata-id> element of the <entry> element contains the authenticated identity. An authenticated identity is authorized to read an MCS group document if the authenticated identity is listed in the authorized MCS server list specified in subclause 6.2.5.1. An authenticated identity is authorized to create, read, modify and delete an MCS group document if the MCS group document is stored: a) in users tree of the XUI equal to the authenticated identity; or b) in users tree of the another XUI, subject to MCS service provider policy. The MCS service provider policy can specified e.g. using an appropriate access permissions document specified in OMA OMA-TS-XDM_Core- V2_1 [2], stored in the user's tree of the other XUI; and unless precluded by other statement of this subclause. None is authorized to create, delete, and modify a <on-network-temporary> element of a <list-service> element of the <group> element of an existing MCS group document. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 61 None is authorized to delete a group document containing a <on-network-regrouped> element of a <list-service> element of the <group> element of an MCS group document. An authenticated identity is authorized to create and delete a <on-network-regrouped> element in the <list-service> element of the <group> element of an existing MCS group document if the authenticated identity is in authorized GMS list specified in subclause 6.2.5.1. An authenticated identity is authorized to subscribe to notification of changes of an MCS group document if: 1) the authenticated identity is a member of an MCS group defined by a <list-service> element of the <group> element of the MCS group document; 2) the authenticated identity is listed in the authorized MCS server list specified in subclause 6.2.5.1; or 3) the authenticated identity is listed in the authorized GMS list specified in subclause 6.2.5.1 and the subscription is on behalf of a constituent MCS group of the MCS group defined by the MCS group document." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 8.2.2.2.3] "Upon receiving a SIP PUBLISH request such that: 1) Request-URI of the SIP PUBLISH request contains either the public service identity identifying the originating participating MCVideo function serving the MCVideo user, or the public service identity identifying the terminating participating MCVideo function serving the MCVideo user; 2) the SIP PUBLISH request contains an application/vnd.3gpp.mcvideo-info+xml MIME body containing the<mcvideo-request-uri> element which identifies an MCVideo ID served by the MCVideo server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; 4) the Event header field of the SIP PUBLISH request contains the "presence" event type; and 5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-user affiliation information according to clause 8.3.1; then the MCVideo server: 1) shall identify the served MCVideo ID in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP PUBLISH request; 2) if the Request-URI of the SIP PUBLISH request contains the public service identity identifying the originating participating MCVideo function serving the MCVideo user, shall identify the originating MCVideo ID from public user identity in the P-Asserted-Identity header field of the SIP PUBLISH request; 3) if the Request-URI of the SIP PUBLISH request contains the public service identity identifying the terminating participating MCVideo function serving the MCVideo user, shall identify the originating MCVideo ID in the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP PUBLISH request; 4) if the originating MCVideo ID is different than the served MCVideo ID and the originating MCVideo ID is not authorized to modify affiliation status of the served MCVideo ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; 5) if the Expires header field of the SIP PUBLISH request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP PUBLISH request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps; 6) if the Expires header field of the SIP PUBLISH request has nonzero value, shall determine the candidate expiration interval to according to IETF RFC 3903 [12]; 7) if the Expires header field of the SIP PUBLISH request has zero value, shall set the candidate expiration interval to zero; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 62 8) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 3GPP TS 24.229 [11], IETF RFC 3903 [12]. In the SIP 200 (OK) response, the MCVideo server: a) shall set the Expires header field according to IETF RFC 3903 [12], to the candidate expiration time; 9) if the "entity" attribute of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request is different than the served MCVideo ID, shall not continue with the rest of the steps; 10) shall identify the served MCVideo client ID in the "id" attribute of the <tuple> element of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request; 11) shall consider an MCVideo user information entry such that: a) the MCVideo user information entry is in the list of MCVideo user information entries described in clause 8.2.2.2.2; and b) the MCVideo ID of the MCVideo user information entry is equal to the served MCVideo ID; as the served MCVideo user information entry; 12) shall consider an MCVideo client information entry such that: a) the MCVideo client information entry is in the list of MCVideo client information entries of the served MCVideo user information entry; and b) the MCVideo client ID of the MCVideo client information entry is equal to the served MCVideo client ID; as the served MCVideo client information entry; 13) shall consider a copy of the list of the MCVideo group information entries of the served MCVideo client information entry as the served list of the MCVideo group information entries; 14) if the candidate expiration interval is nonzero: a) shall construct the candidate list of the MCVideo group information entries as follows: i) for each MCVideo group ID which has an MCVideo group information entry in the served list of the MCVideo group information entries, such that the expiration time of the MCVideo group information entry has not expired yet, and which is indicated in a "group" attribute of an <affiliation> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request: A) shall copy the MCVideo group information entry into a new MCVideo group information entry of the candidate list of the MCVideo group information entries; B) if the affiliation status of the MCVideo group information entry is "deaffiliating" or "deaffiliated", shall set the affiliation status of the new MCVideo group information entry to the "affiliating" state and shall reset the affiliating p-id of the new MCVideo group information entry; and C) shall set the expiration time of the new MCVideo group information entry to the current time increased with the candidate expiration interval; ii) for each MCVideo group ID which has an MCVideo group information entry in the served list of the MCVideo group information entries, such that the expiration time of the MCVideo group information entry has not expired yet, and which is not indicated in any "group" attribute of the <affiliation> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request: A) shall copy the MCVideo group information entry into a new MCVideo group information entry of the candidate list of the MCVideo group information entries; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 63 B) if the affiliation status of the MCVideo group information entry is "affiliated" or "affiliating": - shall set the affiliation status of the new MCVideo group information entry to the "de- affiliating" state; and - shall set the expiration time of the new MCVideo group information entry to the current time increased with twice the value of timer F; and iii) for each MCVideo group ID: A) which does not have an MCVideo group information entry in the served list of the MCVideo group information entries; or B) which has an MCVideo group information entry in the served list of the MCVideo group information entries, such that the expiration time of the MCVideo group information entry has already expired; and which is indicated in a "group" element of the <affiliation> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request: A) shall add a new MCVideo group information entry in the candidate list of the MCVideo group information list for the MCVideo group ID; B) shall set the affiliation status of the new MCVideo group information entry to the "affiliating" state; C) shall set the expiration time of the new MCVideo group information entry to the current time increased with the candidate expiration interval; and D) shall reset the affiliating p-id of the new MCVideo group information entry; b) determine the candidate number of MCVideo group IDs as number of different MCVideo group IDs which have an MCVideo group information entry: i) in the candidate list of the MCVideo group information entries; or ii) in the list of the MCVideo group information entries of an MCVideo client information entry such that: A) the MCVideo client information entry is in the list of the MCVideo client information entries of the served MCVideo user information entry; and B) the MCVideo client ID of the MCVideo client information entry is not equal to the served MCVideo client ID; with the affiliation status set to the "affiliating" state or the "affiliated" state and with the expiration time which has not expired yet; and c) if the candidate number of MCVideo group IDs is bigger than N2 value of the served MCVideo ID, shall based on MCVideo service provider policy reduce the candidate MCVideo group IDs to that equal to N2; NOTE: The MCVideo service provider policy can determine to remove an MCVideo group ID based on the order it appeared in the PUBLISH request or based on the importance or priority of the MCVideo group or some other policy to determine which MCVideo groups are preferred. 15) if the candidate expiration interval is zero, constructs the candidate list of the MCVideo group information entries as follows: a) for each MCVideo group ID which has an entry in the served list of the MCVideo group information entries: i) shall copy the MCVideo group entry of the served list of the MCVideo group information into a new MCVideo group information entry of the candidate list of the MCVideo group information entries; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 64 ii) shall set the affiliation status of the new MCVideo group information entry to the "de-affiliating" state; and iii) shall set the expiration time of the new MCVideo group information entry to the current time increased with twice the value of timer F; 16) shall replace the list of the MCVideo group information entries stored in the served MCVideo client information entry with the candidate list of the MCVideo group information entries; 17) shall perform the procedures specified in clause 8.2.2.2.6 for the served MCVideo ID and each MCVideo group ID: a) which does not have an MCVideo group information entry in the served list of the MCVideo group information entries and which has an MCVideo group information entry in the candidate list of the MCVideo group information entries with the affiliation status set to the "affiliating" state; b) which has an MCVideo group information entry in the served list of the MCVideo group information entries with the expiration time already expired, and which has an MCVideo group information entry in the candidate list of the MCVideo group information entries with the affiliation status set to the "affiliating" state; c) which has an MCVideo group information entry in the served list of the MCVideo group information entries with the affiliation status set to the "deaffiliating" state or the "deaffiliated" state and with the expiration time not expired yet, and which has an MCVideo group information entry in the candidate list of the MCVideo group information entries with the affiliation status set to the "affiliating" state; or d) which has an MCVideo group information entry in the served list of the MCVideo group information entries with the affiliation status set to the "affiliated" state and with the expiration time not expired yet, and which has an MCVideo group information entry in the candidate list of the MCVideo group information entries with the affiliation status set to the "de-affiliating" state; 18) shall identify the handled p-id in the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and 19) shall perform the procedures specified in clause 8.2.2.2.5 for the served MCVideo ID." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 8.2.2.2.4] "Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains either the public service identity identifying the originating participating MCVideo function serving the MCVideo user, or the public service identity identifying the terminating participating MCVideo function serving the MCVideo user; 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body containing the<mcvideo-request-uri> element which identifies an MCVideo ID served by the MCVideo server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; and 4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; the MCVideo server: 1) shall identify the served MCVideo ID in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP PUBLISH request; 2) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCVideo function serving the MCVideo user, shall identify the originating MCVideo ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request; 3) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the terminating participating MCVideo function serving the MCVideo user, shall identify the originating MCVideo ID in the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP SUBSCRIBE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 65 4) if the originating MCVideo ID is different than the served MCVideo ID and the originating MCVideo ID is not authorized to modify affiliation status of the served MCVideo ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; and 5) shall generate a 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 6665 [16]. For the duration of the subscription, the MCVideo server shall notify the subscriber about changes of the information of the served MCVideo ID, as described in clause 8.2.2.2.5." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 8.2.2.2.5] "In order to notify the subscriber about changes of the served MCVideo ID, the MCVideo server: 1) shall consider an MCVideo user information entry such that: a) the MCVideo user information entry is in the list of MCVideo user information entries described in clause 8.2.2.2.2; and b) the MCVideo ID of the MCVideo user information entry is equal to the served MCVideo ID; as the served MCVideo user information entry; 2) shall consider the list of the MCVideo client information entries of the served MCVideo user information entry as the served list of the MCVideo client information entries; 3) shall generate an application/pidf+xml MIME body indicating per-user affiliation information according to clause 9.3.1 and the served list of the MCVideo client information entries with the following clarifications: a) the MCVideo server shall not include information from an MCVideo group information entry with the expiration time already expired; b) the MCVideo server shall not include information from an MCVideo group information entry with the affiliation status set to the "deaffiliated" state; c) if the SIP SUBSCRIBE request creating the subscription of this notification contains an application/simple-filter+xml MIME body according to clause 8.3.2, the MCVideo server shall restrict the application/pidf+xml MIME body according to the application/simple-filter+xml MIME body; and d) if this procedures is invoked by procedure in clause 8.2.2.2.3 where the handled p-id value was identified, the MCVideo server shall set the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id value; and 4) send a SIP NOTIFY request according to 3GPP TS 24.229 [11], and IETF RFC 6665 [16] with the MIME body. In the SIP NOTIFY request, the MCVideo server shall include the generated application/pidf+xml MIME body indicating per-user affiliation information." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 8.2.2.2.8] "Upon receiving a SIP MESSAGE request such that: 1) Request-URI of the SIP MESSAGE request contains the public service identity identifying the terminating participating MCVideo function serving the MCVideo user; 2) the SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body containing the<mcvideo-request-uri> element and the <mcvideo-calling-user-id> element; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; and 4) the SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-affiliation-command+xml MIME body; then the MCVideo server: 1) shall identify the served MCVideo ID in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP MESSAGE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 66 2) shall identify the originating MCVideo ID in the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP MESSAGE request; 3) if the originating MCVideo ID is not authorized to send an affiliation status change request in negotiated mode to the served MCVideo ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; 4) shall set the Request-URI of the SIP MESSAGE request to the public user identity bound to the served MCVideo ID in the MCVideo server; and 5) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; before forwarding the SIP MESSAGE request further." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 8.2.2.2.15] "This clause is referenced from other procedures. If the participating MCVideo function has successfully performed service authorisation for the MCVideo ID identified in the service authorisation procedure, the participating MCVideo function: 1) shall identify the MCVideo ID included in the SIP request received for service authorisation procedure as the served MCVideo ID; 2) shall identify the MCVideo client ID from the <mcvideo-client-id> element contained in the application/vnd.3gpp.mcvideo-info+xml MIME body included in the SIP request received for service authorisation as the served MCVideo client ID; 3) shall download the MCVideo user profile from the MCVideo user database if not already stored at the participating MCVideo function; 4) if no <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) for the served MCVideo ID or the <ImplicitAffiliations> element contains no <entry> elements containing an MCVideo group ID, shall skip the remaining steps; 5) shall consider an MCVideo user information entry such that: a) the MCVideo user information entry is in the list of MCVideo user information entries described in clause 8.2.2.2.2; and b) the MCVideo ID of the MCVideo user information entry is equal to the served MCVideo ID; as the served MCVideo user information entry; 6) shall consider an MCVideo client information entry such that: a) the MCVideo client information entry is in the list of MCVideo client information entries of the served MCVideo user information entry; and b) the MCVideo client ID of the MCVideo client information entry is equal to the served MCVideo client ID; as the served MCVideo client information entry; 7) shall consider a copy of the list of the MCVideo group information entries of the served MCVideo client information entry as the served list of the MCVideo group information entries; 8) shall construct the candidate list of the MCVideo group information entries as follows: a) for each MCVideo group ID which has an MCVideo group information entry in the served list of the MCVideo group information entries shall copy the MCVideo group information entry into a new MCVideo group information entry of the candidate list of the MCVideo group information entries; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 67 b) for each MCVideo group ID contained in an <entry> element of the <ImplicitAffiliations> element in the <OnNetwork> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) for the served MCVideo ID that does not have an MCVideo group information entry in the served list of the MCVideo group information entries or has an MCVideo group information entry in the served list of the MCVideo group information entries such that the expiration time of the MCVideo group information entry has already expired: i) shall add a new MCVideo group information entry in the candidate list of the MCVideo group information list for the MCVideo group ID; ii) shall set the affiliation status of the new MCVideo group information entry to the "affiliating" state; and iii) shall set the expiration time of the new MCVideo group information entry to the current time increased with the candidate expiration interval; c) if in step b) above, no new MCVideo group information entries were added to the candidate list of the MCVideo group information list for the MCVideo group ID: i) shall discard the candidate list; and ii) shall skip the remaining steps; 9) determine the candidate number of MCVideo group IDs as the number of different MCVideo group IDs which have an MCVideo group information entry: a) in the candidate list of the MCVideo group information entries; or b) in the list of the MCVideo group information entries of an MCVideo client information entry such that: i) the MCVideo client information entry is in the list of the MCVideo client information entries of the served MCVideo user information entry; and ii) the MCVideo client ID of the MCVideo client information entry is not equal to the served MCVideo client ID; with the affiliation status set to the "affiliating" state or the "affiliated" state and with the expiration time which has not expired yet; and c) if the candidate number of MCVideo group IDs is bigger than the N2 value of the served MCVideo ID, shall based on MCVideo service provider policy reduce the candidate MCVideo group IDs to that equal to N2; NOTE 1: The MCVideo service provider policy can determine to remove an MCVideo group ID based on the importance or priority of other MCVideo groups, received SIP requests containing an authorised request for originating a priority call or other policy to determine which MCVideo groups are preferred. 10) shall replace the list of the MCVideo group information entries stored in the served MCVideo client information entry with the candidate list of the MCVideo group information entries; and 11) for each MCVideo group ID contained in an <entry> element of the <ImplicitAffiliations> element in the <OnNetwork> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) for the served MCVideo ID and which has an MCVideo group information entry in the candidate list of the MCVideo group information entries with an affiliation status of "affiliating", shall perform the procedures specified in clause 8.2.2.2.6 for the served MCVideo ID and each MCVideo group ID. NOTE 2: To learn of the MCVideo groups successfully affiliated to, the MCVideo client can subscribe to that information by the procedures specified in clause 8.2.1.3." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 68 |
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 defined in ETSI TS 136 508 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo Server) consists of all sub-systems of the Common Services Core, including the Group Management Server, the Configuration Management Server, the Key Management Server, the Identity Management Server, the HTTP Server, and the SIP AS. The IUT (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The IUT (MCVideo Server) is connected to the SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCVideo". - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in subclause 5.1. |
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 status changes for user A? (See note) - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to de-affiliate user A from group A using the SS-UE1 (MCVideo Client)? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to affiliate user A to group A using the SS-UE1 (MCVideo Client)? - - 3 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 69 St Procedure Message Sequence TP Verdict U - S Message 4 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-UE2 (MCVideo Client) to own affiliation status changes for user B? (See note) - - 1 P 5 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to de-affiliate user B from group A using the SS-UE2 (MCVideo Client)? - - 4 P 6 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 affiliation status changes of targeted user B? - - 5 P 7 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to request from the SS-UE1 (MCVideo Client) to affiliate targeted user B to group A (mandatory mode)? - - 6 P 8 Check: Does the IUT (MCVideo Server) correctly perform steps 3-6 of procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to inform user B in the SS-UE2 (MCVideo Client) that is being remotely affiliated to group A? - - 6 P 9 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to request from the SS-UE1 (MCVideo Client) to de- affiliate targeted user B from group A (mandatory mode)? - - 7 P 10 Check: Does the IUT (MCVideo Server) correctly perform steps 3-6 of procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to inform user B in the SS-UE2 (MCVideo Client) that is being remotely de-affiliated from group A? - - 7 P 11 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to request from the SS-UE1 (MCVideo Client) to affiliate targeted user B to group A via negotiated mode? - - 8 P 12 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 inform user B in the SS-UE2 (MCVideo Client) about a remote request to affiliate to group A via negotiated mode? - - 9 P 13 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to affiliate user B to group A using the SS-UE2 (MCVideo Client)? - - 10 P 14 Check: Does the IUT (MCVideo Server) correctly perform steps 3-6 of procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to inform user A in the SS-UE1 (MCVideo Client), that user B is being affiliated to group A? - - 10 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 70 St Procedure Message Sequence TP Verdict U - S Message 15 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to request from the SS-UE1 (MCVideo Client) to de- affiliate targeted user B to group A via negotiated mode? - - 11 P 16 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 inform user B in the SS-UE2 (MCVideo Client) about a remote request to de-affiliate to group A via negotiated mode - - 11 P 17 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to de-affiliate user B to group A using the SS-UE2 (MCVideo Client)? - - 4 P 18 Check: Does the IUT (MCVideo Server) correctly perform steps 3-6 of procedure 'MCVideo Group Affiliation status change' as described in Annex A, Table A.3.6.3-1 to inform user A in the SS-UE1 (MCVideo Client), that user B is being de-affiliated from group A? - - 4 P 19 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 de-subscribe the SS-UE1 (MCVideo Client) from affiliation status changes for targeted user B? - - 13 P NOTE: Affiliation status change triggered by implicit 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 Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Annex A, Table A.2.7.4-3 MIME body part SIMPLE-FILTER MIME-part-body Simple-Filter as described in Table 5.3.3.3-2 Table 5.3.3.3-2: Simple-Filter in SIP SUBSCRIBE (Table 5.3.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.6-1, condition MCVIDEO and PER-CLIENT ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 71 Table 5.3.3.3-3: SIP SUBSCRIBE from the SS-UE2 (Step 4, 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 Element Value/remark Comment Reference Condition From IETF RFC 3261 [10] addr-spec user-info and host Default public user id (px_MCX_SIP_PublicUserId_B) Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-4 MIME body part SIMPLE-FILTER MIME-part-body Simple-Filter as described in Table 5.3.3.3-2 Table 5.3.3.3-4: MCVideo-Info in SIP SUBSCRIBE (Table 5.3.3.3-3) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri Encrypted (note) <mcvideo- request-uri> with mcvideoURI set to px_MCVideo_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2A. Table 5.3.3.3-5: SIP SUBSCRIBE from the SS-UE1 (Step 6, 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 Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-4 Table 5.3.3.3-6: SIP SUBSCRIBE from the SS-UE1 (Step 19, 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, condition re-SUBSCRIBE Information Element Value/remark Comment Reference Condition Expires delta-seconds "0" Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-4 Table 5.3.3.3-7: SIP PUBLISH from the SS-UE1 (Step 2, Table 5.3.3.2-1; Step 1, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.6.4-1 Information Element Value/remark Comment Reference Condition Expires delta-seconds "0" ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 72 Table 5.3.3.3-8: SIP PUBLISH from the SS-UE1 (Step 3, Table 5.3.3.2-1; Step 1, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.6.4-1 Table 5.3.3.3-9: SIP PUBLISH from the SS-UE2 (Steps 5 and 17, Table 5.3.3.2-1; Step 1, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.6.4-1 Information Element Value/remark Comment Reference Condition From IETF RFC 3261 [10] addr-spec user-info and host Default public user id (px_MCX_SIP_PublicUserId_B) Expires delta-seconds "0" Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-10 MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-11 Table 5.3.3.3-10: MCVideo-Info in SIP PUBLISH (Table 5.3.3.3-9) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri Encrypted (note) <mcvideo- request-uri> with mcvideoURI set to px_MCVideo_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2A. Table 5.3.3.3-11: PIDF in SIP PUBLISH (Table 5.3.3.3-9) Derivation Path: Annex A, Table A.3.6.4-2 Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCVideo_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status not present ..p-id any allowed value p-id shall be present acc. to ETSI TS 124 281 [8] (3GPP TS 24.281) clause 8.2.1.2 NOTE: Encrypted attribute as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.13.3-1. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 73 Table 5.3.3.3-12: SIP PUBLISH from the SS-UE1 (Step 7, Table 5.3.3.2-1; Step 1, Annex A, Table A.3.5.3-1) Derivation Path: Annex A, Table A.3.6.4-1 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-13 MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-14 Table 5.3.3.3-13: MCVideo-Info in SIP PUBLISH (Table 5.3.3.3-12) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri Encrypted (note) <mcvideo- request-uri> with mcvideoURI set to px_MCVideo_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2A. Table 5.3.3.3-14: PIDF in SIP PUBLISH (Table 5.3.3.3-12) Derivation Path: Annex A, Table A.3.6.4-2 Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCVideo_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status not present ..p-id any allowed value p-id shall be present acc. to ETSI TS 124 281 [8] (3GPP TS 24.281) clause 8.2.1.2 NOTE: Encrypted attribute as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.13.3-1. Table 5.3.3.3-15: SIP PUBLISH from the SS-UE1 (Step 9, Table 5.3.3.2-1; Step 1, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.6.4-1 Information Element Value/remark Comment Reference Condition Expires delta-seconds "0" Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-13 MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-14 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 74 Table 5.3.3.3-16: SIP PUBLISH from the SS-UE2 (Step 13, Table 5.3.3.2-1; Step 1, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.6.4-1 Information Element Value/remark Comment Reference Condition From addr-spec user-info and host Default public user id (px_MCX_SIP_PublicUserId_B) Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-10 MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-11 Table 5.3.3.3-17: SIP NOTIFY from the IUT (MCVideo Server) (Step 1, Table 5.3.3.2-1; Step 3, Annex A, Table A.3.5.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-18 Table 5.3.3.3-18: PIDF in SIP NOTIFY (Table 5.3.3.3-17) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "affiliated" Table 5.3.3.3-19: SIP NOTIFY from the IUT (MCVideo Server) (Step 3, Table 5.3.3.2-1; Step 5, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-20 Table 5.3.3.3-20: PIDF in SIP NOTIFY (Table 5.3.3.3-19) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "affiliated" ..p-id same value as received in corresponding SIP PUBLISH (Step 3) ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 75 Table 5.3.3.3-21: SIP NOTIFY from the IUT (MCVideo Server) (Step 3, Table 5.3.3.2-1; Step 3, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-22 Table 5.3.3.3-22: PIDF in SIP NOTIFY (Table 5.3.3.3-21) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "affiliating" ..p-id same value as received in corresponding SIP PUBLISH (Step 3) Table 5.3.3.3-23: SIP NOTIFY from the IUT (MCVideo Server) (Step 2, Table 5.3.3.2-1; Step 3, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-24 Table 5.3.3.3-24: PIDF in SIP NOTIFY (Table 5.3.3.3-23) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "deaffiliating" ..p-id same value as received in corresponding SIP PUBLISH (Step 2) Table 5.3.3.3-25: SIP NOTIFY from the IUT (MCVideo Server) (Step 2, Table 5.3.3.2-1; Step 5, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-26 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 76 Table 5.3.3.3-26: PIDF in SIP NOTIFY (Table 5.3.3.3-25) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status not present Table 5.3.3.3-27: SIP NOTIFY from the IUT (MCVideo Server) (Step 4, Table 5.3.3.2-1; Step 3, Annex A, Table A.3.5.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-28 Table 5.3.3.3-28: PIDF in SIP NOTIFY (Table 5.3.3.3-27) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCVideo_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status affiliation status "affiliated" NOTE: Encrypted attribute as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.13.3-1. Table 5.3.3.3-29: SIP NOTIFY from the IUT (MCVideo Server) (Steps 7, 8, 13 and 14, Table 5.3.3.2-1; Step 5, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-30 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 77 Table 5.3.3.3-30: PIDF in SIP NOTIFY (Table 5.3.3.3-29) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCVideo_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status affiliation status "affiliated" ..p-id same value as received in corresponding SIP PUBLISH NOTE: Encrypted attribute as described in Table 5.5.13.3-1. Table 5.3.3.3-31: SIP NOTIFY from the IUT (MCVideo Server) (Steps 7, 8, 13 and 14, Table 5.3.3.2-1; Step 3, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-32 Table 5.3.3.3-32: PIDF in SIP NOTIFY (Table 5.3.3.3-31) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCVideo_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status affiliation status "affiliating" ..p-id same value as received in corresponding SIP PUBLISH NOTE: Encrypted attribute as described in Table 5.5.13.3-1. Table 5.3.3.3-33: SIP NOTIFY from the IUT (MCVideo Server) (Steps 5, 9, 10, 17 and 18, Table 5.3.3.2-1; Step 3, Annex A, Table A.3.6.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-34 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 78 Table 5.3.3.3-34: PIDF in SIP NOTIFY (Table 5.3.3.3-33) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCVideo_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status affiliation status "deaffiliating" ..p-id same value as received in corresponding SIP PUBLISH (Steps 5, 9 and 17) NOTE: Encrypted attribute as described in Table 5.5.13.3-1. Table 5.3.3.3-35: SIP NOTIFY from the IUT (MCVideo Server) (Steps 5, 6, 9, 10, 17 and 18, Table 5.3.3.2-1; Step 5, Annex A, Table A.3.6.3-1; Step 3, Annex A, Table A.3.5.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-35A Table 5.3.3.3-35A: PIDF in SIP NOTIFY (Table 5.3.3.3-35) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCVideo_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status not present NOTE: Encrypted attribute as described in Table 5.5.13.3-1. Table 5.3.3.3-36: SIP NOTIFY from the IUT (MCVideo Server) (Step 19, Table 5.3.3.2-1; Step 3, Annex A, Table A.3.5.3-1) Derivation Path: Annex A, Table A.3.5.4-2 Information Element Value/remark Comment Reference Condition Subscription-State IETF RFC 6665 [14] substate-value "terminated" expires not present Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-35A ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 79 Table 5.3.3.3-37: SIP MESSAGE from the SS-UE1 (Step 11, Table 5.3.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, conditions MCVIDEO and AFFILIATION Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-38 Table 5.3.3.3-38: MCVideo-Info in SIP MESSAGE (Table 5.3.3.3-37) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri Encrypted (note) <mcvideo- request-uri> with mcvideoURI set to px_MCVideo_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2A. Table 5.3.3.3-39: SIP MESSAGE from the IUT (MCVideo Server) (Step 12, Table 5.3.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, conditions MCVIDEO and AFFILIATION Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-40 Table 5.3.3.3-40: MCVideo-Info in SIP MESSAGE (Table 5.3.3.3-39) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri Encrypted (note) <mcvideo- request-uri> with mcvideoURI set to px_MCVideo_ID_User_B mcvideo-calling-user-id not present NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. Table 5.3.3.3-41: SIP MESSAGE from the SS-UE1 (Step 15, Table 5.3.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, conditions MCVIDEO and AFFILIATION Information Element Value/remark Comment Reference Condition Message-body MIME body part Affiliation-Command MIME-part-body Affiliation-Command as described in Table 5.3.3.3-43 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-42 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 80 Table 5.3.3.3-42: MCVideo-Info in SIP MESSAGE (Table 5.3.3.3-41) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri Encrypted (note) <mcvideo- request-uri> with mcvideoURI set to px_MCVideo_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2A. Table 5.3.3.3-43: Affiliation-Command in SIP MESSAGE (Table 5.3.3.3-41) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.7-2 Information Element Value/remark Comment Reference Condition command-list affiliate not present de-affiliate group[1] px_MCVideo_Group_A_ID MCVideo group name Table 5.3.3.3-44: SIP MESSAGE from the IUT (MCVideo Server) (Step 16, Table 5.3.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, conditions MCVIDEO and AFFILIATION Information Element Value/remark Comment Reference Condition Message-body MIME body part Affiliation-Command MIME-part-body Affiliation-Command as described in Table 5.3.3.3-46 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.3.3-45 Table 5.3.3.3-45: MCVideo-Info in SIP MESSAGE (Table 5.3.3.3-44) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri Encrypted (note) <mcvideo- request-uri> with mcvideoURI set to px_MCVideo_ID_User_B mcvideo-calling-user-id not present NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. Table 5.3.3.3-46: Affiliation-Command in SIP MESSAGE (Table 5.3.3.3-44) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.7-2 Information Element Value/remark Comment Reference Condition command-list affiliate not present de-affiliate group[1] px_MCVideo_Group_A_ID MCVideo group name ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 81 5.4 MCVIDEO Server - MCVIDEO Client / Configuration / Determination of MCVIDEO Service Settings / Current Active MCVIDEO Settings / De-subscribe |
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 (MCVideo Server) having determined MCVideo service settings} ensure that { when { the SS-UE1 (MCVideo client ) requests to re-subscribe to MCVideo service settings with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (3) with { IUT (MCVideo Server) having determined MCVideo service settings } ensure that { when { the SS-UE1 (MCVideo client ) requests to de-subscribe from MCVideo service settings with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } |
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 describes the procedures for SIP registration and MCVideo service authorization for the MCVideo client and the MCVideo service. The MCVideo UE can use SIP REGISTER or SIP PUBLISH for MCVideo service settings to perform service authorization for MCVideo. The decision which method to use is based on implementation and on availability of an access-token received as outcome of the user authentication procedure as described in 3GPP TS 24.482 [52]. If another MC service client (e.g. MCPTT, MCData) is operating at the same time on the same MC UE as the MCVideo client, then the MCVideo client shares the same SIP registration as the other MC service clients. The SIP REGISTER procedures in this clause are combined with the SIP REGISTER procedures for the other operating MC service clients to create a single SIP REGISTER request. If other MC service clients are already operating when the MCVideo client registers, then a re-registration is performed containing the parameters for the other operating MC services. Although the access-token can be the same for the MCVideo service as for other MC services when performing service authorization for MCVideo along with other MC services using SIP REGISTER multipart MIME bodies for each MC service are included in the SIP REGISTER request. The MCVideo server can therefore receive multipart MIME bodies in the SIP REGISTER request. Multiple contact addresses (one per MC service client) can be included in a SIP REGISTER request provided they all contain the same IP address and port number (see 3GPP TS 24.229 [4] for further details of including multiple contact addresses in a single SIP REGISTER request). ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 82 If the MCVideo client logs off from the MCVideo service but other MC service clients are to remain registered the MC UE performs a re-registration as specified in 3GPP TS 24.229 [4] without the g.3gpp.mcvideo media feature tag and the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" in the Contact header field of the SIP REGISTER request but with the parameters for the remaining operating MC service clients." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.2.4] "In order to discover MCVideo service settings of another MCVideo client of the same MCVideo user or to verify the currently active MCVideo service settings of this MCVideo client, the MCVideo client shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 6665 [16], and IETF RFC 4354 [53]. In the SIP SUBSCRIBE request, the MCVideo client: 1) shall set the Request-URI to the public service identity identifying the originating participating MCVideo function serving the MCVideo user; 2) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body. In the application/vnd.3gpp.mcvideo- info+xml MIME body, the MCVideo client shall include the <mcvideo-request-uri> element set to the MCVideo ID of the MCVideo user; 3) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Preferred-Service header field according to IETF RFC 6050 [14]; 4) shall set the Event header field to the 'poc-settings' value; 5) shall include an Accept header field containing the "application/poc-settings+xml" MIME type; 6) if the MCVideo client wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [16], to 4294967295; and NOTE 1: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [15]. 7) if the MCVideo client wants to fetch the current state only, shall set the Expires header field according to IETF RFC 6665 [16], to zero. In order to re-subscribe or de-subscribe, the MCVideo client shall generate an in-dialog SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 6665 [16], IETF RFC 4354 [53]. In the SIP SUBSCRIBE request, the MCVideo client: 1) shall set the Event header field to the 'poc-settings' value; 2) shall include an Accept header field containing the "application/poc-settings+xml" MIME type; 3) if the MCVideo client wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [16], to 4294967295; and NOTE 2: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [15]. 4) if the MCVideo client wants to de-subscribe, shall set the Expires header field according to IETF RFC 6665 [16], to zero. Upon receiving a SIP NOTIFY request according to 3GPP TS 24.229 [11], IETF RFC 6665 [16] and IETF RFC 4354 [53], that contains an application/poc-settings+xml MIME body the MCVideo client shall cache: 1) the <am-settings> element of the poc-settings+xml MIME body for each MCVideo client identified by the "id" attribute according to IETF RFC 4354 [53] as the current Answer-mode indication of that MPCTT client; and 2) the <selected-user-profile-index> element of the poc-settings+xml MIME body for each MCVideo client identified by the "id" attribute according to IETF RFC 4354 [53] as the active MCVideo user profile of that MCVideo client." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 83 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.3] "The MCVideo server shall support obtaining service authorization specific information from a SIP PUBLISH request for MCVideo server settings. Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; 2) an application/poc-settings+xml MIME body; and 3) an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <mcvideo-access-token> element and an <mcvideo-client-id> element; the MCVideo server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall perform the procedures in clause 7.3.1A; … 3a) shall check if the number of maximum simultaneous authorizations supported for the MCVideo user as specified in the <max-simultaneous-authorizations> element of the <anyExt> element contained in the <OnNetwork> element of the MCVideo service configuration document (see the service configuration document in 3GPP TS 24.484 [25]) has been reached … 4) shall perform service authorization for the identified MCVideo ID as described in 3GPP TS 33.180 [8]; 5) if service authorization was successful: a) shall bind the MCVideo ID and MCVideo client ID to the IMS public user identity; b) if the service authorization request was from an MCVideo user who is previously MCVideo service authorized on another MCVideo client (as determined by a comparison of the received MCVideo client ID with the MCVideo client ID of existing bindings), keep the current bindings and create a new binding between the MCVideo ID, MCVideo client ID and the IMS public user identity; and c) if a Resource-Share header field with the value "supported" was included in the "message/sip" MIME body of the third-party REGISTER request, shall bind the MCVideo ID to the identity of the MCVideo UE contained in the "+g.3gpp.registration-token" header field parameter in the Contact header field of the third-party REGISTER request that contained this IMS public user identity; NOTE 1: The MCVideo server will store the binding MCVideo ID, MCVideo client ID, IMS public user identity and an identifier addressing the MCVideo server in an external database. … 7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [12] and if processing of the SIP request was not successful, do not continue with the rest of the steps; 8) shall cache the received MCVideo service settings until the MCVideo service settings expiration timer expires; 9) shall send aSIP 200 (OK) response according to 3GPP TS 24.229 [11] with: a) if more than one binding exists for the MCVideo ID, an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in annex F.1 with an <multiple-devices-ind> element set to the value "true"; 10) shall use the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package as the current Answer-Mode Indication of the MCVideo client. 11) shall download the MCVideo user profile from the MCVideo user database as defined in 3GPP TS 29.283 [54] if not already stored at the MCVideo server and use the <selected-user-profile-index> element of the poc- settings event package if included to identify the active MCVideo user profile for the MCVideo client; NOTE 2: If the <selected-user-profile-index> element of the poc-settings event package is included then only that MCVideo user profile is needed to be downloaded from the MCVideo user database. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 84 12) if there is no <selected-user-profile-index> element included in the poc-settings event package then if multiple MCVideo user profiles are stored at the MCVideo server or downloaded for the MCVideo user from the MCVideo user database, shall determine the pre-selected MCVideo user profile to be used as the active MCVideo user profile by identifying the MCVideo user profile (see the MCVideo user profile document in 3GPP TS 24.484 [25]) in the collection of MCVideo user profiles that contains a <Pre-selected-indication> element; and NOTE 3: If only one MCVideo user profile is stored at the MCVideo server or only one MCVideo user profile is downloaded from the MCVideo user database, then by default this MCVideo user profile is the pre- selected MCVideo user profile. 13) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCVideo user profile document with one or more <entry> elements containing an MCVideo group ID (see the MCVideo user profile document in 3GPP TS 24.484 [25]) for the served MCVideo ID, shall perform implicit affiliation as specified in clause 8.2.2.2.15." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.4] "Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; 2) an application/poc-settings+xml MIME body; and 3) an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <mcvideo-request-uri> element and an <mcvideo-client-id> element; The MCVideo server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall perform the procedures in clause 7.3.1A; … 4) shall verify that a binding between the IMS public user identity in the Request-URI and the MCVideo ID in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml exists at the MCVideo server; 5) if a binding exists between the IMS public user identity and the MCVideo ID in the request and the validity period of the binding has not expired shall download the MCVideo user profile from the MCVideo user database as defined in 3GPP TS 29.283 [54] if not already stored at the MCVideo server; … 7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [12] and if processing of the SIP request was not successful, do not continue with the rest of the steps; 8) shall cache the received MCVideo service settings until the MCVideo service settings expiration timer expires; 9) shall send a SIP 200 (OK) response according 3GPP TS 24.229 [11]; 10) shall use the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package as the current Answer-Mode Indication of the MCVideo client. 11) shall download the MCVideo user profile from the MCVideo user database as defined in 3GPP TS 29.283 [54] if not already stored at the MCVideo server and use the <selected-user-profile-index> element of the poc- settings event package if included to identify the active MCVideo user profile for the MCVideo client; NOTE 1: If the <selected-user-profile-index> element of the poc-settings event package is included then only that MCVideo user profile is needed to be downloaded from the MCVideo user database. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 85 12) if there is no <selected-user-profile-index> element included in the poc-settings event package then if multiple MCVideo user profiles are stored at the MCVideo server or downloaded for the MCVideo user from the MCVideo user database, shall determine the pre-selected MCVideo user profile to be used as the active MCVideo user profile by identifying the MCVideo user profile (see the MCVideo user profile document in 3GPP TS 24.484 [25]) in the collection of MCVideo user profiles that contains a <Pre-selected-indication> element; and NOTE 2: If only one MCVideo user profile is stored at the MCVideo server or only one MCVideo user profile is downloaded from the MCVideo user database, then by default this MCVideo user profile is the pre- selected MCVideo user profile. 13) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCVideo user profile document with one or more <entry> elements containing an MCVideo group ID (see the MCVideo user profile document in 3GPP TS 24.484 [25]) for the served MCVideo ID, shall perform implicit affiliation as specified in clause 8.2.2.2.15." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.5] "Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; and 2) an Expires header field set to 0; the MCVideo server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [12] and if processing of the SIP request was successful, continue with the rest of the steps; 3) shall remove the MCVideo service settings; 4) shall remove the binding between the MCVideo ID and public user identity; and 5) shall send a SIP 200 (OK) response according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.1A] "When the MCVideo server receives a SIP REGISTER request sent from the MCVideo client contained within a message/sip MIME body of a received third-party SIP REGISTER request or a SIP PUBLISH request, it first determines whether XML MIME bodies included in the request are integrity protected. If XML MIME bodies are integrity protected the MCVideo server validates the signature of each of the XML MIME bodies. If the integrity protection check(s) pass or the XML MIME bodies are not integrity protected, the MCVideo server then determines whether the content in specific XML elements is confidentiality protected. If XML content is confidentiality protected, the MCVideo server decrypts the protected content. Upon receiving: - a SIP REGISTER request containing an application/vnd.3gpp.mcvideo-info+xml MIME body within a message/sip MIME body of the SIP REGISTER request sent from the MCVideo client; or - a SIP PUBLISH request containing an application/vnd.3gpp.mcvideo-info+xml MIME body and an application/poc-settings+xml MIME body; the MCVideo server: 1) shall determine if integrity protection has been applied to XML MIME bodies in the SIP request by following the procedures in clause 6.6.3.4.1 for each XML MIME body; 2) if integrity protection has been applied, shall use the keying data described in clause 6.6.3.2 and the procedures described in clause 6.6.3.4.2 to verify the integrity of each of the XML MIME bodies; and 3) if all integrity protection checks succeed, shall continue with the remaining steps of this clause. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 86 Upon receiving: - a SIP REGISTER request containing an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-access-token> element and an <mcvideo-client-id> element within a message/sip MIME body of the SIP REGISTER request sent from the MCVideo client; or - a SIP PUBLISH request containing an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-access-token> element and an <mcvideo-client-id> element, and an application/poc-settings+xml MIME body; the MCVideo server: 1) shall determine if confidentiality protection has been applied to the <mcvideo-access-token> element and the <mcvideo-client-id> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, by following the procedures in clause 6.6.2.4.1; 2) if confidentiality protection has been applied to the <mcvideo-access-token> element and <mcvideo-client- id> element: a) shall use the keying information received in the MIKEY-SAKKE I_MESSAGE as specified in 3GPP TS 33.180 [8], along with the procedures described in clause 6.6.2.4.2 to: i) decrypt the received access token in the <mcvideo-access-token> element in the application/vnd.3gpp.mcvideo-info+xml MIME body; and ii) decrypt the received MCVideo client ID in the <mcvideo-client-id> element in the application/vnd.3gpp.mcvideo-info+xml MIME body; b) if the decryption procedure succeeds, shall identify the MCVideo ID and the MCVideo client ID from the decrypted values; and c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful; 3) if confidentiality protection has been applied to only one of the <mcvideo-access-token> element or the <mcvideo-client-id> element: a) shall determine that confidentiality protection has not been successful; 4) if confidentiality protection has not been applied: a) shall identify the MCVideo ID from <mcvideo-access-token> element received in the application/vnd.3gpp.mcvideo-info+xml MIME body; and b) shall identify the MCVideo client ID from the <mcvideo-client-id> element received in the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receiving a SIP PUBLISH request containing an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-request-uri> element, an <mcvideo-client-id> element, and an application/poc-settings+xml MIME body, the MCVideo server: 1) shall determine if confidentiality protection has been applied to the <mcvideo-request-uri> element and the <mcvideo-client-id> element in the application/vnd.3gpp.mcvideo-info+xml MIME body by following the procedures in clause 6.6.2.4.1; 2) if confidentiality protection has been applied to the <mcvideo-request-uri> element and the <mcvideo-client- id> element: a) shall use the keying information described in clause 6.6.2.2 along with the procedures described in clause 6.6.2.4.2 to: i) decrypt the received encrypted MCVideo ID in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 87 ii) decrypt the received encrypted MCVideo client ID in the <mcvideo-client-id> element in the application/vnd.3gpp.mcvideo-info+xml MIME body; b) if all decryption procedures succeed, shall identify the MCVideo ID and MCVideo client ID from the decrypted values; and c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful; 3) if confidentiality protection has been applied to only one of the <mcvideo-request-uri> element or <mcvideo- client-id> element: a) shall determine that confidentiality protection has not been successful; 4) if confidentiality protection has not been applied: a) shall identify the MCVideo ID from the contents of the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body;and b) shall identify the MCVideo client ID from the <mcvideo-client-id> element received in the application/vnd.3gpp.mcvideo-info+xml MIME body." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.6.1] "Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCVideo function of the served MCVideo user; 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body containing the<mcvideo-request-uri> element which identifies an MCVideo ID served by the MCVideo server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; and 3) the Event header field of the SIP SUBSCRIBE request contains the 'poc-settings' event type. the MCVideo server: 1) shall identify the served MCVideo ID in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP SUBSCRIBE request; 2) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCVideo function serving the MCVideo user, shall identify the originating MCVideo ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request; 3) if the originating MCVideo ID is different than the served MCVideo ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; and 4) shall generate a 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 6665 [16] and IETF RFC 4354 [53]. For the duration of the subscription, the MCVideo server shall notify subscriber about changes of the MCVideo service settings of the subscribed MCVideo user, as described in clause 7.3.6.2." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.6.2] "In order to notify the subscriber about changes of the MCVideo service settings of the subscribed MCVideo client of the subscribed MCVideo user, the MCVideo server: 1) shall generate an application/poc-settings+xml MIME body as defined in 3GPP TS 24.379 [40] containing: a) the <am-settings> element of the poc-settings event package set to the current answer mode setting of the MCVideo client according to IETF RFC 4354 [53]; and b) the <selected-user-profile-index> element as defined in clause 7.4.1.2 identifying the active MCVideo user profile; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 88 2) send a SIP NOTIFY request according to 3GPP TS 24.229 [11], IETF RFC 6665 [16] and IETF RFC 4354 [53] with the constructed application/poc-settings+xml MIME body." |
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.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo Server) consists of all sub-systems of the Common Services Core, including the Group Management Server, the Configuration Management Server, the Key Management Server, the Identity Management Server, the HTTP Server, and the SIP AS. The IUT (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The IUT (MCVideo Server) is connected to the SS-UE1 (MCVideo Client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCVideo". - The SS-UE1 (MCVideo Client) performs the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. |
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)? - - 1 P 2 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 re- subscribe to MCVideo service settings and to receive later notifications? - - 2 P 3 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 de- subscribe from MCVideo service settings? - - 3 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 89 |
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-1), Table 5.5.2.14-1, condition POC-SETTINGS-EVENT Information Element Value/remark Comment Reference Condition Expires ETSI TS 124 281 [8] (3GPP TS 24.281) clause 7.2.4 value "4294967295" Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.4.3.3-2 Table 5.4.3.3-2: MCVideo-Info in SIP SUBSCRIBE (Table 5.4.3.3-1, Table 5.4.3.3-4 and Table 5.4.3.3-5) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2, condition POC-SETTINGS-EVENT Table 5.4.3.3-3: SIP 200 (OK) from the MCVideo Server (Steps 1, 2 and 3, Table 5.4.3.2-1; Step 2, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1, conditions SUBSCRIBE-RSP Table 5.4.3.3-4: SIP SUBSCRIBE from the SS-UE1 (Step 2, 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-1), Table 5.5.2.14-1, condition POC-SETTINGS-EVENT, re_SUBSCRIBE Information Element Value/remark Comment Reference Condition Expires ETSI TS 124 281 [8] (3GPP TS 24.281) clause 7.2.4 value "4294967295" Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.4.3.3-2 Table 5.4.3.3-5: SIP SUBSCRIBE from the SS-UE1 (Step 3, 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-1), Table 5.5.2.14-1, condition POC-SETTINGS-EVENT, re_SUBSCRIBE Information Element Value/remark Comment Reference Condition Expires ETSI TS 124 281 [8] (3GPP TS 24.281) clause 7.2.4 value "0" Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.4.3.3-2 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 90 Table 5.4.3.3-6: SIP NOTIFY from the MCVideo Server (Steps 1 and 2, Table 5.4.3.2-1; Step 3, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, conditions POC-SETTINGS-EVENT Information Element Value/remark Comment Reference Condition Message-body MIME body part PoC-Settings MIME-part-body PoC-Settings as described in Table 5.4.3.3-7 Table 5.4.3.3-7: PoC-Settings in SIP NOTIFY (Table 5.4.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.11.2-1 Table 5.4.3.3-8: SIP NOTIFY from the MCVideo Server (Step 3, Table 5.4.3.2-1; Step 3, Annex A, Table A.2.7.3-1) Derivation Path: Table 5.4.3.3-6 Information Element Value/remark Comment Reference Condition Subscription-State IETF RFC 6665 [14] substate-value "terminated" expires not present 5.5 MCVIDEO Server - MCVIDEO Client / Configuration / Download CSK |
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 (MCVideo Client) initiates an E2E group call establishment 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 the call with all registered users of the group and enforces transmission control } } (3) with { IUT (MCVideo Server) having established an MCVideo E2E group call with Manual Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) ends the E2E group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the other participants } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 91 |
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 these are Rel-14 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 7.3.7] "If confidentiality protection is enabled as specified in clause 6.6.2.3.1, and if the participating MCVideo function received a Client Server Key (CSK) within a SIP REGISTER request for service authorisation or SIP PUBLISH request for service authorisation, the participating MCVideo function may decide to update the CSK. In this case, the participating MCVideo function shall perform a key download procedure for the CSK. The participating MCVideo function: 1) shall generate an SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]; 2) shall set the Request-URI to the URI received in the To header field in a third-party SIP REGISTER request; 3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with parameters "require" and "explicit" according to IETF RFC 3841 [20]; 4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 5) shall include an application/mikey MIME body containing the CSK-ID and the CSK encrypted within a MIKEY message to the MC client as specified in clause 9.2.1 of 3GPP TS 33.180 [8] in the body of the SIP MESSAGE request; 6) shall send the SIP MESSAGE request towards the MCVideo client according to 3GPP TS 24.229 [11]." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 9.2.1.1] "A Client-Server Key is required to protect unicast RTCP signalling between the MC client and the MCX Server. The use of the CSK in this context is defined in clause 9.4. Additionally, the MC Service provider may require that MC identities, access tokens and other sensitive information transferred between clients and MC domain on the SIP-1 and SIP-2 interfaces be protected at the application layer from any viewing, including protection from viewing at the SIP signalling layer. Symmetric key based protection of SIP payload using CSK may be used to satisfy this requirement. The use of CSK in this context is defined in clause 9.3. The uses of the CSK are shown in Figure 9.2.1-1. …" [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 9.2.1.2] "The 128-bit CSK is initially generated by the client and provided encrypted to the server through the SIP interface along with the CSK-ID identifying the CSK. The key remains in use until: a new CSK is required, the SIP session is torn down, the MC user logs off, or some other indication. If during the active SIP session an update of the CSK is required, the server generates a CSK and provides it to the client using the mechanism defined in clause 5.8." [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 9.2.1.4] "The MCX Server may decide to update an existing CSK at any time. This may be due to CSK revocation or expiry. The CSK shall be updated by the MCX Server using the 'key download' procedure, defined in clause 5.8. Upon receipt of a CSK via a 'key download' procedure, the MC client shall identify the type of key as a CSK via the 4 most significant bits of the CSK-ID. The MC client shall: - discard any previous CSKs associated with the MC Server FQDN, and - use the new CSK for uplink signaling with the MC Server." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 92 [ETSI TS 133 180 [7] (3GPP TS 33.180), clause 5.8.1] "The 'key download' procedure is used to send keys from the MCX server to the MC client. It is used to distribute Multicast Signalling Keys (MuSiKs) to the MC clients, and it is used to update both the CSKs and MuSiKs. Within the 'key download' procedure, keys (CSK or MuSiKs) are encrypted specifically to the MC user and signed using an identity representing the MC Server. Prior to group key distribution, each MC client shall be provisioned by the KMS with time-limited key material associated with the MC User as described clause 5.3. The MC Server shall also be provisioned by the MC KMS with key material for an identity which is authorised to act as an MCX Server. The key (CSK or MuSiK) is distributed from the MCX Server to a MC client using the security mechanism described in clause 5.2.2, transported over the SIP bearer. End-point diversity is not required as end-points do not encrypt data, hence the extension in clause 5.2.3 is not applied. Additional parameters may be included as defined in clause 5.2.4. The SAKKE-to-self extension may be included as defined in clause 5.2.5. Identity hiding may be supported as defined in clause 5.2.6. The initiating entity shall be the initiating MCX Server and the receiving entity shall be the terminating MC user. The initiating entity URI shall be the FQDN of the MCX Server (e.g. MDSI of the MC Domain) and the receiving entity URI shall be the MC Service ID of the terminating user. The distributed key, K, shall be the CSK or MuSiK and the key identifier K-ID shall be the CSK-ID or MuSiK-ID (respectively). As a result of this 'key download' mechanism, the MC clients receive a new signalling key, CSK or MuSiK, identified by the 4 most significant bits of the key ID. The MCData Service server may use the Key Download procedure to indicate or modify the algorithm used to protect the MCData signalling fields (i.e. MCData signaling parameters, Data signaling payload and End to end security parameters) by including a 'signalling algorithm' parameter. The 'signalling algorithm' parameter is described in clause 8.5.4.1. The available algorithms shall be as defined in clause 8.5.4.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 13.1] "Media plane security provides integrity and confidentiality protection of individual media streams and media plane control messages in MCVideo sessions. The media plane security is based on 3GPP MCVideo security solution including key management and end-to-end media and transmission control and reception control messages protection as defined in 3GPP TS 33.180 [8]. Various keys and associated key identifiers protect: 1. RTP transported media; 2. RTCP transported media control messages (i.e. RTCP SR packets, RTCP RR packets, RTCP SDES packets); and 3. RTCP APP transported transmission control and reception control messages. In an on-network group call of an MCVideo group which is not a constituent MCVideo group of a temporary MCVideo … 2. if protection of transmission control and reception control messages sent using unicast between the MCVideo client and the participating MCVideo function serving the the MCVideo client is negotiated, the CSK and the CSK-ID protect the transmission control messages sent and received using unicast by the MCVideo client and by a participating MCVideo function; … 5. if protection of media control messages sent using unicast between the MCVideo client and the participating MCVideo function serving the the MCVideo client is negotiated, the CSK and the CSK-ID protect the media control messages sent and received using unicast by the MCVideo client and by a participating MCVideo function; and … ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 93 In an on-network private call: … 2. if protection of transmission control and reception control messages sent using unicast between the MCVideo client and the participating MCVideo function serving the the MCVideo client is negotiated, the CSK and the CSK-ID protect the transmission control and reception control messages sent and received by the MCVideo client and by the participating MCVideo function; … 4. if protection of media control messages sent using unicast between the MCVideo client and the participating MCVideo function serving the the MCVideo client is negotiated, the CSK and the CSK-ID protect the media control messages sent and received using unicast by the MCVideo client and by a participating MCVideo function; and … The CSK and the CSK-ID are generated by the MCVideo client and provided to the participating MCVideo function serving the MCVideo client using SIP signalling according to 3GPP TS 24.281 [2]. …" [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 13.2] "Each key (i.e. CSK, GMK, MKFC, PCK, SPK, MSCCK) and its associated key identifier (i.e. CSK-ID, GMK-ID, MKFC-ID, PCK-ID, SPK-ID, MSCCK-ID) described in clause 13.1 are used to derive SRTP-MK, SRTP-MS and SRTP- MKI. SRTP-MK, SRTP-MS and SRTP-MKI are used in encryption of media or transmission control and reception control messages in SRTP as specified in IETF RFC 3711 [4] and 3GPP TS 33.180 [8]." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 13.3.2] "The participating MCVideo function: 1. if protection of media is negotiated, shall be transparent to RTP media streams and shall forward encrypted RTP media streams without decrypting the payload; 2. if protection of transmission control and reception control messages sent using unicast between the participating MCVideo function and the MCVideo client is negotiated and the CSK and the CSK-ID were received from the MCVideo client using SIP signalling according to 3GPP TS 24.281 [2]: A) shall encrypt transmission control and reception control messages sent using unicast to the served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; and B) shall decrypt transmission control and reception control messages received using unicast from the served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; … 5. if protection of pre-established session call control messages between the participating MCVideo function and the MCVideo client is negotiated and the CSK and the CSK-ID were received from the MCVideo client using SIP signalling according to 3GPP TS 24.281 [2]: A) shall encrypt pre-established session call control messages sent to the served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; and B) shall decrypt pre-established session call control messages received from served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 94 6. if protection of media control messages sent using unicast between the participating MCVideo function and the MCVideo client is negotiated between the participating MCVideo function and the MCVideo client and the CSK and the CSK-ID were received from the MCVideo client using SIP signalling according to 3GPP TS 24.281 [2]; A) shall encrypt media control messages sent using unicast to the served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; and B) shall decrypt media control messages received using unicast from the served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; …" |
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 defined in ETSI TS 136 508 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo Server) consists of all sub-systems of the Common Services Core, including the Group Management Server, the Configuration Management Server, the Key Management Server, the Identity Management Server, the HTTP Server, and the SIP AS. The IUT (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The IUT (MCVideo Server) is connected to the SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCVideo". - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 95 |
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)? - - 1 P 2 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 implicit transmission request but without implicit granted; and using the updated CSK to unprotect the SIP INVITE message received from SS-UE1 (MCVideo Client), with Option b.ii of note on Table A.3.2.3-1? - - 2 P 3 Check: Does the IUT (MCVideo server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1, to release the call? - - 3 P |
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] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCVIDEO Information Element Value/remark Comment Reference Condition P-Asserted-Service ETSI TS 124 281 [8] (3GPP TS 24.281) clause 7.3.7 Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcvideo" Content-Type media-type "application/mikey" Message-body MIKEY message base64 encoded MIKEY message as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.9.1-1A MIKEY message, containing the updated CSK ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 96 5.6 MCVIDEO Server - MCVIDEO Client / Configuration / Subscription to group dynamic data / De-subscribe |
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 the call with all registered users of the group } } (2) with { IUT (MCVideo Server) having established an E2E group call with manual commencement mode } ensure that { when { the SS-UE1 (MCVideo client ) requests to subscribe to group dynamic data for group call ongoing information with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (3) with { IUT (MCVideo Server) having determined MCVideo subscription to group dynamic data } ensure that { when { the SS-UE1 (MCVideo client ) requests to de-subscribe from MCVideo group dynamic data for group call ongoing information with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (4) with { IUT (MCVideo Server) having established an MCVideo E2E group call with Manual Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) ends the E2E group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the other participants } } |
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 request such that: 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCVideo function serving the MCVideo user; 2) the SIP SUBCRIBE request contains an application/vnd.3gpp.mcvideo-info MIME body containing the<mcvideo-request-uri> element which identifies an MCVideo group ID not served by the MCVideo server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service header field according to IETF RFC 6050 [9]; and 4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; then the MCVideo server: 1) shall identify the target MCVideo group ID in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info MIME body of the SIP SUBSCRIBE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 97 2) shall identify the originating MCVideo ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request; 3) shall if the originating MCVideo ID is not authorized for this subscription reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps; 4) shall generate a SIP SUBSCRIBE request from the received SIP SUBSCRIBE request. In the generated SIP SUBSCRIBE request, the MCVideo server: a) shall set the Request-URI to the public service identity identifying the controlling MCVideo function serving the target MCVideo group ID; b) shall include a P-Asserted-Identity header field containing the public service identity identifying the originating participating MCVideo function serving the MCVideo user; c) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body. In the application/vnd.3gpp.mcvideo-info+xml MIME body, the MCVideo server: A) shall include the <mcvideo-request-uri> element set to the target MCVideo group ID; and B) shall include the <mcvideo-calling-user-id> element set to the originating MCVideo ID; and d) shall include other signalling elements from the received SIP SUBSCRIBE request; and 4) shall send the generated SIP SUBSCRIBE request according to 3GPP TS 24.229 [11]. The MCVideo server shall forward any received SIP responses to the SIP SUBSCRIBE request, any received SIP NOTIFY requests and any received SIP responses to the SIP NOTIFY request." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 8.2.2.3.9] "Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity of the controlling MCVideo function associated with the served MCVideo group; 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body containing the<mcvideo-request-uri> element and the <mcvideo-calling-user-id> element; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service header field according to IETF RFC 6050 [9]; 4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; and 5) the SIP SUBSCRIBE request contains an application/simple-filter+xml MIME body indicating per-group dynamic data of presence event package notification information according to clause 8.3.2 indicating the same MCVideo group ID as in the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the SIP SUBSCRIBE request; then the MCVideo server: 1) shall identify the served MCVideo group ID in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP SUBSCRIBE request; 2) shall identify the handled MCVideo ID in the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP SUBSCRIBE request; 3) if the Expires header field of the SIP SUBSCRIBE request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP SUBSCRIBE request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 98 4) if an MCVideo group for the served MCVideo group ID does not exist in the group management server according to 3GPP TS 24.481 [31], shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps; 5) if the handled MCVideo ID is not authorized to subscribe to group dynamic data of the MCVideo group identified by the served MCVideo group ID, shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps; and 6) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 6665 [26]. For the duration of the subscription, the MCVideo server shall notify subscriber about changes of the information of the served MCVideo ID, as described in clause 8.2.2.3.10." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 8.2.2.3.10] "In order to notify the subscriber identified by the handled MCVideo ID about changes of the per-group dynamic data of the served MCVideo group ID, the MCVideo server: 1) shall consider an MCVideo group information entry such that: a) the MCVideo group information entry is in the list of MCVideo group information entries described in clause 8.2.2.3.2; and b) the MCVideo group ID of the MCVideo group information entry is equal to the served MCVideo group ID; 2) shall generate an application/pidf+xml MIME body indicating per-group dynamic data according to clause 8.3.1 with the following clarifications: a) the MCVideo server shall include the "expires" attribute in the <affiliation> element; and 3) shall send a SIP NOTIFY request according to 3GPP TS 24.229 [11], and IETF RFC 6665 [26] for the subscription created in clause 8.2.2.3.9. In the SIP NOTIFY request, the MCVideo server shall include the generated application/pidf+xml MIME body indicating per-group dynamic data." |
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 defined in ETSI TS 136 508 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo Server) consists of all sub-systems of the Common Services Core, including the Group Management Server, the Configuration Management Server, the Key Management Server, the Identity Management Server, the HTTP Server, and the SIP AS. The IUT (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 99 Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The IUT (MCVideo Server) is connected to the SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4. - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.