hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.3.3 Specific message contents | Table 6.1.1.3.3-1: SIP MESSAGE from the SS-UE1 (Step 1, Table 6.1.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.1.3.3-1 Table 6.1.1.3.3-2: SIP MESSAGE from the MCData Server (IUT) to SS-UE2 (Step 1, Table 6.1.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) De... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData Client) initiates establishment of a group standalone SDS } then { IUT (MCData Server) accepts the call from the initiator and establishes the call with SS- UE2 (MCData Client) and responds/forwards empty MSRP messages } } (2) w... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 9.2.3.3.3, 9.2.3.3.4, 9.2.3.3.1, 9.2.3.3.2, 9.2.3.4.3, 9.2.3.4.4, 9.2.3.4.1, 9.2.3.4.2, ETSI TS 124 582 [40] (3GPP TS 24.582), clauses 6.2.1.4.1, 6.2.1.4.2, 6.2.1.4.3, 6.2.1.5.1, 6.2.1.5.2... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.3.2 Test procedure sequence | Table 6.1.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Establishment' as described in Annex A, Table A.4.3.3-1 to establish a media plane connection for a group? - - 1 P 2 Check: Does the MCData Server (... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.3.3 Specific message contents | Table 6.1.2.3.3-1: SIP INVITE from the SS-UE1 (Step 1, Table 6.1.2.3.2-1; Step 1, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.7.3.3-1 Information Element Value/remark Comment Reference Condition Session-Expires generic-param "1800" The recommended initial value is 1 80... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData Client) initiates establishment of a one-to-one SDS session } then { IUT (MCData Server) accepts the call from the initiator and establishes the call with SS- UE2 (MCData Client) and responds/forwards empty MSRP messages } } (2)... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 9.2.4.3.3, 9.2.4.3.4, 9.2.4.3.1, 9.2.4.3.2, 9.2.4.4.3, 9.2.4.4.4, 9.2.4.4.1, 9.2.4.4.2, ETSI TS 124 582 [40] (3GPP TS 24.582), clauses 6.2.2.4.1, 6.2.2.4.2, 6.2.2.4.3, 6.2.2.5.1, 6.2.2.5.2... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.3.2 Test procedure sequence | Table 6.1.3.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Establishment' as described in Annex A, Table A.4.3.3-1 to establish a media plane connection between SS-UE1 (MCData Client) and SS-UE2 (MCData Clie... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.3.3 Specific message contents | Table 6.1.3.3.3-1: SIP INVITE from the SS-UE1 (Step 1, Table 6.1.3.3.2-1; Step 1, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-1 Information Element Value/remark Comment Reference Condition Session-Expires generic-param "1800" The recommended initial value is 1 80... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 and having established a pre-established session with the clients} ensure that { when { the SS-UE1 (MCData Client) requests the call establishment using a pre-established session with SIP REFER message } then { IUT (MCData Server) responds with a SIP 200 (OK) and establ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 18.3.2.2, 18.3.3.1.2, 18.3.3.2.2, 9.2.5.2.2.1, 9.2.5.2.2.2, 9.2.5.4.2.1, 9.2.5.4.2.2, 9.2.5.1.1, 9.2.5.1.2, 9.2.5.1.3, ETSI TS 124 582 [40] (3GPP TS 24.582), clauses 12.2, 6.2.1.4.1, 6.2.1... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.3.2 Test procedure sequence | Table 6.1.4.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Establishment using pre-established session' as described in Annex A, Table A.4.6.3-1 to establish a media plane connection between SS-UE1 (MCData C... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.3.3 Specific message contents | Table 6.1.4.3.3-1: SIP REFER from the SS-UE1 (Step 1, Table 6.1.4.3.2-1; Step 1, Annex A, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-1 Information Element Value/remark Comment Reference Condition Message-body MIME body part Resource list MIME-part-body Resource-lists as d... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2 File Distribution | 6.2.1 MCDATA Server - MCDATA Client / File Distribution (FD) / FD Using HTTP / One-to-one Standalone FD / Non-Mandatory Download / FILE DOWNLOAD REQUEST ACCEPTED / FILE DOWNLOAD COMPLETED / FILE DOWNLOAD REQUEST REJECTED / FILE DOWNLOAD DEFERRED |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests discovery of the absolute URI by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 200 (Ok) to UE1 (MCData Client) } } ETSI ETSI TS... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 10.2.4.1, 10.2.4.3.1, 10.2.4.3.2, 10.2.4.4.1, 10.2.4.4.2, 10.2.4.2.1, 10.2.1.2.3, 11.2, 6.2.3.2, 12.2.2.1, 15.2.6. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.3.2 Test procedure sequence | Table 6.2.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'Discovery of the absolute URI of the media storage function' as described in Annex A, Table A.4.10.3-1? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perf... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.3.3 Specific message contents | Table 6.2.1.3.3-1: HTTP POST from the SS-UE1 (Step 2 and 6, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.1.3.3-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 203 Table 6.2.1.3.3-2: HTTP 201 Created from the MCData Server (IUT) to the SS-UE1 (Step 2... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests discovery of the absolute URI by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 200 (Ok) to UE1 (MCData Client) } } (2) with { I... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 10.2.4.1, 10.2.4.3.1, 10.2.4.3.2, 10.2.4.4.1, 10.2.4.4.2, 10.2.4.2.1, 10.2.1.2.2, 6.2.2.2, 11.2, 6.2.3.2, 15.2.16. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.3.2 Test procedure sequence | Table 6.2.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'Discovery of the absolute URI of the media storage function' as described in Annex A, Table A.4.10.3-1? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perf... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.3.3 Specific message contents | Table 6.2.2.3.3-1: HTTP POST from the SS-UE1 (Step 2, Table 6.2.2.3.2-1; Step 1, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.7.3.3-7 Table 6.2.2.3.3-2: HTTP 201 Created from the MCData Server (IUT) to the SS-UE1 (Step 2, Table 6.2.2.3.2-1; Step 3, Annex A, Table A.4.8.... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData Client) initiates establishment of a media plane FD session } then { IUT (MCData Server) accepts the call from the initiator and establishes the call with SS- UE2 (MCData Client) and responds/forwards empty MSRP messages } } (2)... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 10.2.5.3.3, 10.2.5.3.4, 10.2.5.3.1, 10.2.5.3.2, 10.2.5.4.3, 10.2.5.4.4, 10.2.5.4.1, 10.2.5.4.2, ETSI TS 124 582 [40] (3GPP TS 24.582), clauses 7.2.4.1, 7.2.4.2, 7.2.4.3, 7.2.5.1, 7.2.5.2, ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.3.2 Test procedure sequence | Table 6.2.3.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Establishment' as described in Annex A, Table A.4.3.3-1 to establish a media plane connection between SS-UE1 (MCData Client) and SS-UE2 (MCData Clie... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.3.3 Specific message contents | Table 6.2.3.3.3-1: SIP INVITE from the SS-UE1 (Step 1, Table 6.2.3.3.2-1; Step 1, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-1 Information Element Value/remark Comment Reference Condition Session-Expires generic-param "1800" The recommended initial value is 1800... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests discovery of the absolute URI by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 200 (Ok) to UE1 (MCData Client) } } ETSI ETSI TS... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 11.3.1, 11.3.3.1, 11.3.3.2, 6.3.2.1, 15.1.12.1, 11.3.2.1, 6.2.4.1, 15.1.11.1. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 11.3.1]... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.3.2 Test procedure sequence | Table 6.2.4.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'Discovery of the absolute URI of the media storage function' as described in Annex A, Table A.4.10.3-1? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perf... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.3.3 Specific message contents | Table 6.2.4.3.3-1: HTTP POST from the SS-UE1 (Step 2, Table 6.2.4.3.2-1; Step 1, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.13.3.3-7 Table 6.2.4.3.3-2: HTTP 201 Created from the MCData Server (IUT) to the SS-UE1 (Step 2, Table 6.2.4.3.2-1; Step 3, Annex A, Table A.4.8... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3 Enhanced Status (ES) | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1 MCDATA Server - MCDATA Client / Enhanced Status (ES) | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests one-to-one Standalone SDS by sending a SIP MESSAGE message with disposition request "DELIVERY" and an enhanced status payload with id = 0} then { IUT (MCData Server) sends a SIP MESSAGE message to UE2 (MCData Client... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 14.2.2.1, 14.2.2.2, 14.2.3.1, 14.2.3.2, 9.2.2.3.1, 9.2.2.3.2, 9.2.2.4.1, 9.2.2.4.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 1... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as def... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.3.2 Test procedure sequence | Table 6.3.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward an Enhanced Status from SS-UE1 (MCData client) to SS-UE2 ... |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.3.3 Specific message contents | Table 6.3.1.3.3-1: SIP MESSAGE from the SS-UE1 (Step 1, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.3.1.3.3-1 Table 6.3.1.3.3-2: SIP MESSAGE from the MCData Server (IUT) to SS-UE2 (Step 1, Table 6.3.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) De... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 1 Scope | The present document assesses the importance of low frequency bands in wireless backhaul networks collecting information on current use by Fixed Services of the bands lower than 10 GHz, expected use on medium term and reporting technical considerations on why bands below 10 GHz are necessary to deploy long haul links, ... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 2 References | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 2.1 Normative references | Normative references are not applicable in the present document. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 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... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 3 Definition of terms, symbols and abbreviations | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 3.1 Terms | For the purposes of the present document, the following terms apply: access link: last mile connection to site (fixed or mobile) dense urban: location in highly populated areas (malls, business districts, city centres) very close to fibre PoP: distances less than 1 km and very high capacity, up to 50 Gbps NOTE: Usually... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: p0 Multipath occurrence factor R0.01 Rainfall intensity exceeded for 0,01 % of an average year (mm/h) dN1 Point refractivity gradient in the lowest 65 m of the atmosphere not exceeded for 1 % of an average year sa Area terrain roughness as defined i... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 4G 4th Generation Mobile Networks 5G 5th Generation Mobile Networks AI Action Item APAC Asia-Pacific APT Asia-Pacific Telecommunity ASMG Arab Spectrum Management Group ATU African Telecommunications Union BCA Band and Carrier Aggregation CCDP ... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 4 Spectrum Considerations | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 4.1 Available Microwave Spectrum | Frequency bands used in modern Wireless Backhaul Networks range from 4 GHz to 86 GHz and studies for going beyond 90 GHz are in an advanced stage with prototypes showcased in W-Band (92 GHz to 114,25 GHz) and D-Band (130 GHz to 174,8 GHz). Figure 3: Microwave Spectrum Frequency band choice takes into account different ... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 4.2 Spectrum Requirements | In past years, evolution of MW application from medium-long distance infrastructure network to Wireless Backhaul of thousands mobile sites and wider fibre availability, shifted major requirements from low bands to high bands: higher spectrum amount allows to serve multiple sites minimizing the interferences and achieve... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5 Spectrum Segmentation in Wireless Backhaul | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.1 Wireless Backhaul Trends | The study in on evolution of wireless backhaul published by ABI Research for GSMA in 2021 [i.7] touched multiple aspects, from technology innovation to spectrum availability, allocation and pricing, including capacity analysis and link forecasts. According to this study there will be 17,2 million backhaul links to coll... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.2 Low Bands Application Scenarios | Frequency band segmentation is related to region/country specific reasons related to applications and propagation conditions: • Long haul high capacity backbone. Countries lacking nationwide fibre infrastructure rely on MW technology deploying multichannel links to carry 5-10 Gbps. These links are in the uppermost laye... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3 Bands below 10 GHz Statistics | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.1 Worldwide wireless backhaul statistics | Starting from ABI Research for GSMA study [i.7] snapshot of technologies used for mobile backhaul in 2021, it is possible to extrapolate traditional band segmentation: out of 5,1 million links installed in 2021, about 2 million are deployed in low bands (< 13 GHz) representing more than 30 % of the overall installed MW... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.2 CEPT Countries - ECC Report 173 and ECC Report 365 | CEPT has analysed Fixed Service use and trends several times since 1997 asking Administrations to answer to questionnaires: ECC Report 3 was issued in 1997 and revised in 2001, ECC Report 173 was issued in 2012 and revised in 2018 and 2022. Latest ECC Report 173 [i.8] collected the feedbacks of 26 administrations: depl... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.3 Real Networks - Tier 1 Operators | Bands segmentation of links deployed by Tier-1 Operators with affiliates across Europe and MEA countries is reported in Figure 12. About 3 600 links are deployed in Europe and more than 11 000 in MEA leading to two considerations: 1) In Europe, where fibre has a deeper penetration, links in bands below 10 GHz are deplo... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.4 USA statistics | Basic licenses attributes of MW point-to-point link installed in USA can be retrieved searching FCC Universal Licensing Scheme database. Six bands are included in the analysis: 6 GHz, 11 GHz, 18 GHz, 23 GHz and 38 GHz. U4 GHz, 7 GHz and 8 GHz are not available for fixed service. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 18... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.5 Vendors statistics | Vendors delivery statistics from 2019 to 2024 have been collected to define the band distribution across different regions: Europe, Commonwealth of Independent States, Asia Pacific, Middle East, Africa, North and Latin America. Country split is reported in Annex B. Notwithstanding country split may not completely overl... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.4 Bands < 10 GHz Trends | Focusing on wireless backhaul links forecast reported in ABI Research for GSMA report [i.7], bands up to 13 GHz will represent almost one fourth of the overall installed links (Figure 17), increasing from 2,1 million links (2021) to more than 2,2 million links in 2027 and confirming that medium-long haul applications w... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6 Planning Considerations and Link Lengths Statistics | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1 Microwave Planning Basic Concepts | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.1 Overview | Prediction methods required for Line-Of-Sight MW link design are described in Recommendation ITU-R P.530-19 [i.10] and takes into account both clear-air and rainfall conditions. Propagation loss includes different contributions: • Attenuation due to atmospheric gases: attenuation due to oxygen and water vapour ais alwa... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2 Multipath fading | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.1 Multipath fading highlights | In case of atmosphere stratification (refractivity gradient varying with altitude), the MW signal may be divided in different rays along the path. These rays arrive on the receiver antenna with different delays due to the length of their paths and are combined together causing attenuation (down-fading) or enhancement (... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.2 Outage due to non-selective fading | The graph in Figure 18 shows the relation between the fade depth A (dB) on the X axis and the percentage of time in which this fade depth is exceeded (on the Y axis) according to the values of a parameter named p0. Link will be in outage when the fade depth is bigger or equal to the fade margin of the link. p0 depends ... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.3 Outage due to selective fading | Selective fading can cause an in-band distortion that may not be recovered by the system equalizer therefore causing an outage of the link. Calculation of the outage cause by selective fading is based on the p0 parameter and on the signature of the modem that gives the system capability of recovering the distortion. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.4 Space Diversity improvement | Space diversity is the most used technique to counteract multipath fading, in particular for long haul links. SD is based on the use of two antennas on the receiver side and on the combination/switching of the signal coming from the two antennas to improve the Rx signal quality. Recommendation ITU-R P.530-17 [i.2] defi... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.5 Total outage caused by multipath | Total outage caused by multipath is given by the combination of the contributions of Pns (outage due to non-selective fading) and Ps (outage due to selective fading). ETSI ETSI TR 104 142 V1.1.1 (2026-02) 22 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.3 Rain attenuation | Recommendation ITU-R P.837-8 [i.11] provides the rainfall statistics required for rain attenuation prediction described in Recommendation ITU-R P.530-17 [i.2]. Notwithstanding ITU-R has updated the rainfall database reported in in past years (latest update in 2017) and common planning tools utilize it as option for pre... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.4 Availability prediction | The total bi-directional outage of the link is usually given by the sum of the outage due to rain plus two times the outage given by multipath fading. The rain outage is considered correlated in two directions (attenuation in the two direction is the same at the same time), but is considered un-correlated for the multi... |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.2 Low Bands Performances Comparison | |
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 dN... |
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 ar... |
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 am... |
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... |
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 us... |
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 ... |
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 allo... |
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 an... |
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 distribu... |
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... |
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], ... |
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 a... |
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 i... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.