hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f034bffddd3013f74d8544c8dd9a379e | 103 572 | 3.2.2 Relational operators | For the purposes of the present document, the following relational operators apply: > Greater than >= Greater than or equal to < Less than <= Less than or equal to == Equal to ETSI ETSI TS 103 572 V1.3.1 (2021-08) 8 != Not equal to |
f034bffddd3013f74d8544c8dd9a379e | 103 572 | 3.2.3 Assignment operators | For the purposes of the present document, the following assignment operators apply: = Assignment operator ++ Increment, i.e. x is equivalent to x = x + 1; when used in an array index, evaluates to the value of the variable prior to the increment operation -- Decrement, i.e. x- - is equivalent to x = x - 1; when used in... |
f034bffddd3013f74d8544c8dd9a379e | 103 572 | 3.2.4 Mathematical functions | For the purposes of the present document, the following mathematical functions apply: Abs(x) = ; ≥0 − ; < 0 Clip3(x, y, z) = ; < ; > ; ℎ Floor(x) the largest integer less than or equal to x. Round(x)=Sign(x)*Floor(Abs(x)+0,5) Sign(x) = 1 ; x > 0 0 ; = 0 −1 ; < 0 |
f034bffddd3013f74d8544c8dd9a379e | 103 572 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CVS Coded Video Sequence EN European Standard HDR High Dynamic Range HEVC High Efficiency Video Coding ITU-R International Telecommunications Union - Radiocommunications standardization sector ITU-T International Telecommunications Union - Tel... |
f034bffddd3013f74d8544c8dd9a379e | 103 572 | 4 ST2094-10_data() structure definition | |
f034bffddd3013f74d8544c8dd9a379e | 103 572 | 4.1 Introduction | This clause specifies the syntax and semantics of ST2094-10_data() structure. Clause 4.2 defines the syntax of the ST2094-10_data() structure. Clause 4.3 defines the semantics of the ST2094-10_data() structure. The metadata elements of the ST2094-10_data() structure are defined according to the SMPTE ST 2086 [2], SMPTE... |
f034bffddd3013f74d8544c8dd9a379e | 103 572 | 4.2 ST2094-10_data() structure syntax | The parsing process of each syntax element by the descriptor u(n) is described in Recommendation ITU-T H.265 [5] for HEVC and VSEI [11] for VVC. Table 1: ST2094-data() syntax ST2094-10_data () { Descriptor app_identifier ue(v) app_version ue(v) metadata_refresh_flag u(1) if( metadata_refresh_flag ) { num_ext_blocks ue(... |
f034bffddd3013f74d8544c8dd9a379e | 103 572 | 4.3 ST2094-10_data() structure semantics | app_identifier identifies an application and shall be set equal to 1 according to constraints of the section 5 of SMPTE ST 2094-10 [4]. app_version specifies the application version in the application and shall be set equal to 0 according to constraints of the section 5 of SMPTE ST 2094-10 [4]. metadata_refresh_flag wh... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 1 Scope | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, whi... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 2 References | |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 3 Definition of terms, symbols and abbreviations | |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 3.1 Terms | Void. |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 3.2 Symbols | Void. |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: HUD Heads-Up Display ICD Instrument Cluster Display SBP Service Binary Protocol UTC Coordinated Universal Time |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 4 Data Service Definition | |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 4.1 Navigation Meta Data Service Version 1.0 | /** The present document defines data objects for the Navigation Meta * data service to be carried over the SBP. By receiving this data, * the MirrorLink Client (i.e. car) can provide variety navigation * information to driver and passenger through instrument cluster * display panel, HUD, etc. * The service is based on... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 5 SBP Binding | The Navigation Meta Data Services uses the following objects and their access capabilities, as defined in [1]. Table 1 Object Name Access Type Subscription Type Min Interval Time Max Interval Time NavigationInfo READABLE ON_CHANGE N/A N/A NavigationConfig WRITEABLE NONE N/A N/A NavigationNextMan euver READABLE ON_CHANG... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 6 Theory of Operation | |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 6.1 Maneuver Description | The following icons illustrate the different maneuvers, as defined in ManeuverDirection. Table 2 Description Example Description Example Description Example Description Example No Symbol No Info Follow Street Turn Straight Turn Slight Right Turn Slight Left Turn Right Turn Left Turn Sharp Right Turn Sharp Left U-Turn R... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 6.2 Representation of Angle | Angles are represented clock-wise from 0 to 360 degree, as shown in the following Figure 1. Figure 1: representation of angles |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 6.3 Getting Turn-by-Turn Navigation Info | Figure 2 shows how a navigation data sink retrieves meta data about the currently running navigation data source and displays turn-by-turn guidance e.g. on the Instrument Cluster Display (ICD). ETSI ETSI TS 103 544-25 V1.3.1 (2019-10) 17 SBP Server (Media Source) SBP Server (Media Source) SBP Client (Media Sink) SBP Cl... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 6.4 Definition of Time | The Service Binary Protocol (SBP) [2] defines TIME as a 64-bit signed integer (LONG) with the meaning of time in milliseconds since 1970-01-01-00:00 in UTC or relative time in milliseconds depending on how it is defined in each service. The present specification defines the TIME value in the NavigationNextDistance obje... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 6.5 Navigation Lane Guidance | The NavigationLaneGuidance object informs the data sink about available lanes. Each lane is described within a 32-Bit integer value, containing information about: • Line Type (termination marking at the left of the lane). • Lane Type (used for special purpose lanes). • Directional markings on the lane. Lane information... |
c0188f8c5f020f30fddff028c269c744 | 103 544-25 | 6.6 Next Side Streets | The NavigationNextManeuver objects contains 3 arrays, nextSideStreetAngles_{1,2,3}, which represent angle values of side streets leaving from the point at next turn and prior to it: • nextSideStreet_1 array contains side street angles at the point of the next maneuver. • nextSideStreet_2 array contains side street angl... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 1 Scope | The present document specifies interoperability tests with the purpose of supporting the Mission Critical Push To Talk (MCPTT) PlugtestsTM events. |
691c466e3e00944b16122d9a64d5601b | 103 564 | 2 References | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 3 Definition of terms, symbols and abbreviations | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 3.1 Terms | Void. |
691c466e3e00944b16122d9a64d5601b | 103 564 | 3.2 Symbols | Void. |
691c466e3e00944b16122d9a64d5601b | 103 564 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA Authentication Authorization Accounting AFFIL AFFILiation AMR Adaptative Multi-Rate audio codec AMR-WB Adaptative Multi-Rate audio codec Wideband APN Access Point Name APP APPlication ARP Address Resolution Protocol AS Application Server A... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 4 Conventions | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 4.1 Test Description Proforma | A Test Description (TD) is a detailed description of the process that needs to be followed to test one or more interoperable functionalities between two or more vendor implementations. A TD should include as a minimum the following elements. The following different types are defined. Table 1 Interoperability Test Descr... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 4.2 Interoperable Functions Statement | The "Interoperable Functions Statement" (IFS) identifies the standardized functions of a DUT. These functions can be mandatory, optional or conditional (depending on other functions), and depend on the role played by the DUT. The IFS can also be used as a proforma by a vendor to identify the functions that its DUT will... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 4.3 Test Overview | The following objectives shall be considered: • MCPTT Private/Group Calls (unicast) • MCPTT Group Call (eMBMS) • MCPTT Emergency Group Call • MCPTT Floor Control • MCPTT Registration and service authorization • MCPTT Affiliation • MCPTT Location • MCPTT Security • MCData Services • Specific selection of MCVideo Call Ty... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 5 Configurations | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 5.1 Common remarks | The tests may be executed several times by permuting the role that each device plays. This depends on the support of the DUT of the Functional Connectivity Modes defined in clause 5.3.2 of ETSI TS 124 379 [9]. The following roles are possible: a) Functions of the MCPTT server in the primary MCPTT system. b) The non-con... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 5.2 CFG_ONN_OTT-1 | CFG_ONN_OTT-1 is shown in figure 8. MCPTT Client A Originating Participating MCPTT Function Controlling MCPTT Function Terminating Participating MCPTT Function MCPTT Client B Primary MCPTT System MCPTT Client A Originating Participating MCPTT Function Controlling MCPTT Function Terminating Participating MCPTT Function ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 5.3 CFG_ONN_UNI-MC-LTE-1 | In this configuration LTE will have PCC capabilities and therefore will enforce QoS policies in terms of prioritization and pre-emptiveness in unicast bearers including new Public Safety QCI 65/69 (but still no Release 13 eMBMS capabilities). Therefore, a Rx interface will be exposed and related reference points and si... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 5.4 CFG_ONN_MULTI-MC-LTE-1 | In this configuration LTE shall have full MCPTT supporting capabilities (i.e. Release 13 LTE-A Pro eMBMS + needed interfaces + needed MCPTT Release 14 related interfaces). Figure 12: CFG_ONN_MULTI-MC-LTE-1 Application plane interfaces MCPTT-3 MCPTT-1 MCPTT-3 MCPTT-1 Participating MCPTT Server Controlling MCPTT Server P... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6 Interoperable Functions Statement (IFS) | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.1 Entities | Table 2: Entities Item Which entity is supported? Status Support 1 UE 2 MCPTT Client 3 MCData Client 4 MCVideo Client 5 IMS 6 MCPTT Participating AS 7 MCPTT Controlling AS 8 joint MCPTT Participating & Controlling AS 9 MCData Participating AS 10 MCData Controlling AS 11 joint MCData Participating & Controlling AS 12 MC... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.2 UE Features | Table 3: UE features Item Feature ID Ref Status Support 1 Does the UE support Mission Critical APNs and QCIs? UE_MC-APN [4] 2 Does the UE support EMBMS? UE_EMBMS [19] ETSI ETSI TS 103 564 V1.4.1 (2021-01) 37 |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.3 MCPTT Client Features | Table 4: MCPTT Client features Item Feature ID Ref Status Support 1 Does MCPTT-Client support Authentication and ID retrieval from IDMS? MCPTT-Client_IDMS [12] 2 Does MCPTT-Client support PUBLISH Based Registration? MCPTT-Client_PUBREG [9] 3 Does MCPTT-Client support REGISTER Based Registration? MCPTT-Client_REGREG [9]... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.4 MCData Client Features | Table 5: IMS features Item Feature ID Ref Status Support 1 Does MCData-Client support Authentication and ID retrieval from IDMS? MCData-Client_IDMS [12] 2 Does MCData-Client support PUBLISH Based Registration? MCData-Client_PUBREG [9] 3 Does MCData-Client support REGISTER Based Registration? MCData-Client_REGREG [9] 4 ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.5 MCVideo Client Features | Table 6: MCVideo Client features Item Feature ID Ref Status Support 1 Does MCVideo-Client support Authentication and ID retrieval from IDMS? MCVideo-Client_IDMS [12] 2 Does MCVideo-Client support PUBLISH Based Registration? MCVideo-Client_PUBREG [9] 3 Does MCVideo-Client support REGISTER Based Registration? MCVideo-Cli... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.6 IMS Features | Table 7: IMS features Item Feature ID Ref Status Support 1 Does the IMS support 3rd Party REGISTER? IMS_3RDPARTYREG [9] 2 Does the IMS support MCPTT compatible Rx Interface in the PCSCF? IMS_RX [21] ETSI ETSI TS 103 564 V1.4.1 (2021-01) 39 |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.7 MCPTT-Participating AS Features | Table 8: MCPTT-Participating AS features Item Feature ID Ref Status Support 1 Does the MCPTT-Part support REGISTER+PUBLISH Based Service Authorization? MCPTT-Part_PUBAUTH [9] 2 Does the MCPTT-Part support REGISTER Based Authorization? MCPTT-Part_REGAUTH [9] 3 Does the MCPTT-Part support On-Network MCPTT private and gro... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.8 MCPTT-Controlling AS Features | Table 9: MCPTT-Controlling AS features Item Feature ID Ref Status Support 1 Does the MCPTT-Ctrl support On-Network MCPTT private and group calling? MCPTT-Ctrl_ONN-MCPTT-CALL [9] 2 Does the MCPTT-Ctrl support Release 14 specific MCPTT call types? MCPTT-Ctrl_ONN-MCPTT-Rel14 [9] 3 Does the MCPTT-Ctrl support On-Network MC... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.9 MCData-Participating AS Features | Table 10: MCData-Participating AS features Item Feature ID Ref Status Support 1 Does the MCData-Part support REGISTER+PUBLISH Based Service Authorization? MCData-Part_PUBAUTH [9] 2 Does the MCData-Part support REGISTER Based Authorization? MCData-Part_REGAUTH [9] 3 Does the MCData-Part support On-Network MCData SDS ove... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.10 MCData-Controlling AS Features | Table 11: MCData-Controlling AS features Item Feature ID Ref Status Support 1 Does the MCData-Ctrl support On-Network MCData SDS over signalling plane? MCData-Ctrl_ONN-MCData-SDS-SP [8] 2 Does the MCData-Ctrl support On-Network MCData SDS over media plane? MCData-Ctrl_ONN-MCData-SDS-MP [17] 3 Does the MCData-Ctrl suppo... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.11 MCVideo-Participating AS Features | Table 12: MCVideo-Participating AS features Item Feature ID Ref Status Support 1 Does the MCVideo-Part support REGISTER+PUBLISH Based Service Authorization? MCVideo-Part_PUBAUTH [9] 2 Does the MCVideo-Part support REGISTER Based Authorization? MCVideo-Part_REGAUTH [9] 3 Does the MCVideo-Part support On-Network MCVideo ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.12 MCVideo-Controlling AS Features | Table 13: MCVideo-Controlling AS features Item Feature ID Ref Status Support 1 Does the MCVideo-Ctrl support On-Network MCVideo private and group calling? MCVideo-Ctrl_ONN-MCVideo-CALL [7] 2 Does the MCVideo-Ctrl support On-Network MCVideo transmission controlling? MCVideo-Ctrl_ONN-MCVideo-TC [15] 3 Does the MCVideo-Ct... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.13 BM-SC Features | Table 14: BM-SC features Item Feature ID Ref Status Support 1 Does the BM-SC support MB2-C and MB2-U interfaces? BM-SC_GCSE [23] |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.14 EPS Features | Table 15: EPS (LTE eUTRAN + EPC) features Item Feature ID Ref Status Support 1 Does the EPS support Mission Critical APNs and QCIs? EPS_MC-APN [4] 2 Does the EPS support Mission Critical compatible Gx interface with the PCRF? EPS_GX [20] 3 Does the EPS support EMBMS capable EUTRAN+EPC? EPS_EMBMS [19] ETSI ETSI TS 103 5... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 6.15 PCRF Features | Table 16: PCRF features Item Feature ID Ref Status Support 1 Does the PCRF support Mission Critical compatible Rx interface? PCRF_RX [21] 43 ETSI TS 103 564 V1.4.1 (2021-01) ETSI |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7 Test Descriptions | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.1 Common Remarks | Initially the interactions with the support servers may be analysed in separated tests and not necessarily in every e2e call procedure. Similarly, unless otherwise specified, no security mechanism should be applied (including interaction with KMS and ciphering of different parts of both signalling and media streams), a... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.2 Connectivity (CONN) | 7.2.1 MCPTT User initiates an on-demand prearranged MCPTT Group Call [CONN-MCPTT/ONN/GROUP/PREA/ONDEM/NFC/01] This test comprises the establishment of an on-demand prearranged Group Call. Initially, pure SIP signalling shall be evaluated (then, no floor control -NFC- mechanisms shall be specifically considered apart fr... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.2.53 Network triggered FD notifications [CONN-MCDATA/NET/FD/01] | When a user uploads a file to be distributed using HTTP protocol as described in clauses 7.2.45 or 7.2.46, the MCData client will set a file-availability timer as part of the file metadata in the FD signalling part of the SIP MESSAGE. When this timer expires the controlling MCData server is responsible for notifying th... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.3 Floor Controlling (FC) | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.3.1 Basic FC functionality [FC/BASIC/01] | This test shall verify the basic Floor Controlling functionality as defined by ETSI TS 124 380 [10]. In order to do so, after a successful establishment of a prearranged on-demand Group Call different users shall request the Token and Floor Control server capabilities on the controlling server shall be tested. For the ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.3.2 Basic FC functionality. Effect of Priorities [FC/BASIC/02] | This test case extends the previous basic on in clause 7.3.1 by showing the preemptiveness capabilities in the Floor Control when a user with higher priority requests the Token already granted to another lower-priority one. In fact as defined in clause 4.1.1.2 in ETSI TS 124 380 [10] whenever a new request with higher ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.4 Registration and Service Authorization (RegAuth) | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.4.1 MCPTT User authenticates to the IdMS [REGAUTH/IDMSAUTH/01] | MCPTT User gets authenticated in the IdMS using OpenID Connect Core 1.0 as specified in ETSI TS 124 482 [12]. Web-based user and password mechanism shall be used so that the MCPTT Client receives the access and identity tokens that shall be later used for all the service authorization mechanisms. NOTE: MCData and MCVid... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.5 Policing (PCC) | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.5.0 General | Although in the 3GPP Release 14 the MCPTT-Pre-emption feature and enhanced shared resources have been introduced in the 2nd Plugtests the basic mechanisms will be evaluated. Originally on-demand private call was used as an example of a call type responsible for triggering the PCC procedures. Later, Pre-Established Sess... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.6 eMBMS (EMBMS) | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.6.1 Void | 308 ETSI TS 103 564 V1.4.1 (2021-01) ETSI 7.6.2 Use of dynamically established MBMS bearers in prearranged MCPTT group calls with pre-allocated TMGIs [EMBMS/ACTIVATEBEARER/WPRETMGI/01] In an on-going prearranged MCPTT group call the MCPTT Participating server uses the MB2-C interface to the BM-SC to allocate a TMGI usi... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.7 Affiliation (AFFIL) | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.7.1 MCPTT User subscribes to its own affiliation [AFFIL/DET/01] | A registered MCPTT User subscribes to its affiliation by following clauses 9.2.1.3 and 9.2.2.2.4 in ETSI TS 124 379 [9]. Regardless it is its own or other user's affiliation the procedure is rather equivalent. The MCPTT Client sends a SIP SUBSCRIBE message setting as Request-URI the public service identity identifying ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.8 Location (LOC) | 7.8.1 MCPTT Client Configuration upon 3rd party register [LOC/3PRTYREG/CONFIG/01] Upon a successful IMS registration and 3rd party REGISTER arriving at the Participating a new Location Reporting Configuration message shall be created following the procedures in clause 13.2.2 in ETSI TS 124 379 [9]. 347 ETSI TS 103 564 ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.9 OAM procedures (CSC) | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.9.0 General | ETSI TS 124 484 [14] defines the mechanism for online and offline configuration. Since the offline configuration specific mechanism is out of scope of 3GPP in the 2nd Plugtests online mechanisms online will be considered. Although there are several OMA XDM based document operations defined, those ones that are crucial ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.10 Security mechanisms (SEC) | 7.10.1 Key material download from KMS to MCPTT client (CSC-8) with proxy [SEC/KEYMDOWNLOAD/WPROXY/01] In order to derive the keys that will be used for RTP, RTCP, floor control, MBMS control and XML encryption and to be able to decode the MIKEY-SAKKE messages sent by other clients (PCK distribution), GMS (GMK distribut... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.11 MCVideo Transmission Control (TC) | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.11.1 Basic TC functionality [TC/BASIC/01] | This test shall verify the basic transmission control functionality as defined by ETSI TS 124 581 [15]. In order to do so, after a successful establishment of a prearranged on-demand MCVideo Group Call different users shall request the transmission and/or the reception of media and the transmission control server capab... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.12 Server-to-Server communications (S2S) | 7.12.1 On-demand prearranged MCPTT Group Call to temporary group in trusted mode [S2S/ONN/GROUP/PREA/ONDEM/TEMP/01] The test cases in this clause and in the following try to illustrate the controlling and non-controlling capabilities of the MCPTT server for managing on-demand pre-arranged group calls to temporary group... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.13 Functional Alias (FA) | 7.13.1 MCPTT user requests to activate one or more functional aliases [FA/CHANGE/01] Note that, according to clause 9A.2.1.1 in ETSI TS 124 379 [9] the MCPTT client needs to initiate the Functional Alias (FA) status determination procedure for the MCPTT user before starting the functional alias status change procedure ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 7.14 Interoperability Scenarios (IOP) | 7.14.1 Effect of (de)affiliating another user during an ongoing group call [IOP/01] During an ongoing (on-demand prearranged) group call among Users A, C and D, an MCPTT user -User A from vendor A- acting as operator affiliates a new user -MCPTT user B from vendor B- to that group in mandatory mode (refer to [AFFIL/CHA... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 8 eMBMS complementary test cases (informative) | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 8.1 Introduction (disclaimer) | During the preparation of the test cases for the 2nd Plugtests the convenience of extensively testing eMBMS related interfaces and procedures was agreed. Such additional testing would however go beyond the overall approach followed for the rest of MCS features (even further than those test cases purely considered in 3G... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 8.2 Extended eMBMS test cases | 8.2.1 TMGI allocation management [EMBMS-ADDITIONAL/MB2C/FUNCT/ALLOCTMGI/01] TMGI allocation management: • TMGI/TMGI range allocation • TMGI expiration time renewal (free or in use) 8.2.2 TMGI deallocation management [EMBMS-ADDITIONAL/MB2C/FUNCT/DEALLOCTMGI-/01] TMGI deallocation management: • No TMGI IE in request -> a... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9 Observers scenarios | |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.1 Introduction | The so called "Observers scenarios" were introduced during the 4th MCX Plugtest so that relevant stakeholders (mostly governments/public safety network operators) registered as observers could provide feedback about more complex test cases, closer to daily operations and reflecting the demands from real users. Most of ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.2 Common remarks | During the discussions towards the definition of the base set of scenarios there was a consensus among the observers regarding the need to show an operation as realistic as possible. That would mean avoiding Over-the-Top configuration (CFG_ONN_OTT-1) and using always MCX clients running on LTE UEs connected to a live M... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.3 Emergency call [OS1] | The scenario comprises the following steps: • User initiates emergency private call in manual commencement mode • Call is answered by another user • Call terminated Message Sequence Diagram Figure 123: OS1 Message Sequence |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.4 Emergency call handling [OS2] | The scenario comprises the following steps: • Ongoing MCPTT group call • While one participant is talking, another group participant initiates emergency call • Emergency alert being sent • Group call converted to emergency call and emergency user gets the Floor MCPTT Client A MCS Part/Ctrl AS MCPTT Client B (1) Emergen... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.5 Encrypted private call [OS3] | The scenario comprises the following steps: • User initiates private call in automatic commencement mode • Call is received by another user • Call terminated based on hang timer MCPTT Client A MCS Part/Ctrl AS MCPTT Client B MCPTT Client C (1) audio (2) audio (3) audio Ongoing group call (Client B talking) (4) Emergenc... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.6 eMBMS MCPTT [OS4.1] | The scenario considers a ciphered MCPTT group call using eMBMS (therefore CFG_ONN_MULTI-MC-LTE-1 is to be used). MCPTT Client A MCS Part/Ctrl AS KMS MCPTT Client B 1 Retrieve KMS certificate 2 Retrieve Client's key material 3 Retrieve KMS certificate 4 Retrieve Client's key material (1) Initiate encrypted private call ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.7 eMBMS MCVideo [OS4.2] | The scenario considers a ciphered MCVideo group call using eMBMS (therefore CFG_ONN_MULTI-MC-LTE-1 is to be used). MCPTT Client A MCS Part/Ctrl AS KMS BM-SC MCPTT Client B MCPTT Client C 1 Retrieve certificate/key information 2 Retrieve certificate/key information 3 Retrieve certificate/key information 4 Retrieve certi... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.8 Switching on [OS5] | The scenario comprises the following steps: • LTE Registration - Authentication - Location update • MC Service user authentication and authorization • Update of user profile and group configuration (Selection of user profile) • Affiliation MCVIDEO Client A MCS Part/Ctrl AS KMS BM-SC MCVIDEO Client B MCVIDEO Client C 1 ... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.9 Encrypted MCPTT group call [OS6] | The scenario comprises the following steps: • Group Call set-up: - Pre-arranged Group Call - Chat Group Call • Floor Control with speech duration of several seconds between multiple (up to 30) participants • MCS solution uses the standardized MC-QCIs • During call an extra participant affiliates to the group using late... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.10 Enhanced status [OS7.1] | This scenario is FFS since no Stage 3 protocol specifications were available for the considered 3GPP Release. |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.11 MCDATA SDS [OS7.2] | This scenario comprises transmitting a SDS message from one user to another (see clause 7.2.39). Message Sequence Diagram Figure 130: OS7.2 Message Sequence |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.12 Encrypted MCVideo Group Call [OS8] | The scenario comprises the following steps (over Unicast MC LTE): • Video group call set-up by one user • The stream is received by multiple user • MCS solution uses the standardized MC-QCIs MCPTT Client A MCS Part/Ctrl AS PCRF LTE Core MCPTT Client B MCPTT Client C (1) audio (2) audio Ongoing prearranged group call (C... |
691c466e3e00944b16122d9a64d5601b | 103 564 | 9.13 Parallel MCPTT and MCVIDEO [OS9] | The scenario comprises the following steps (over Unicast MC LTE): • Setup MCPTT group call • Floor Control with speech duration of several seconds between multiple participants • Video group call set-up by one user • The stream is received by multiple users • MCPTT and MCVIDEO calls in parallel • Manual call terminatio... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.