hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.1 IMZ basic service in the ITS architecture | All authorized ITS-S: authorized roadside ITS-S, authorized vehicle ITS-S and authorized personal ITS-S (for example, an OBE in a train or a portable device in an emergency vehicle), shall be capable of sending IMZMs. As illustrated in Figure 1, the IMZ basic service shall have the following interfaces: • the NF-SAP wi... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.2 IMZ basic service functional architecture | The IMZ basic service is part of the Application Support domain of the Facilities Layer according to ETSI TS 102 894-1 [i.5]. Figure 2 shows the functional block diagram with the functional blocks of the IMZ basic service and interfaces to other entities and layers. The IMZ basic service interacts with other Facilities... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.3 Interfaces of the IMZ basic service | |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.3.1 Interface to ITS applications | An ITS application is an application layer entity that implements the logic for fulfilling one or more ITS use cases. For example, ITS Release 1 applications are defined in ETSI TS 101 539-1 [i.7], ETSI TS 101 539-2 [i.8] and ETSI TS 101 539-3 [i.9]. ITS applications can provide the trigger to transmit IMZM. For the pr... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.3.2 Interface to data provisioning facilities | For the generation of IMZMs, the IMZ basic service interacts with other facilities layer entities in order to obtain the required data. This set of facilities that provides data for IMZM generation is referred to as data provisioning facilities. Data are exchanged between the data provisioning facilities and the IMZ ba... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.3.3 Interface to the networking & transport layer | The IMZ basic service exchanges information with ITS networking & transport layer via the interface IF.NF (Figure 2). A specification of the interface IF.NF as NF-SAP (Figure 1) is provided in ETSI TS 102 723-11 [i.11]. At the originating ITS-S, the IMZ basic service shall provide the IMZM embedded in a Facility-Layer ... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.3.4 Interfaces to the protocol stacks of the networking & transport layer | |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.3.4.1 Interface to the GeoNetworking/BTP stack | A IMZM may rely on the services provided by the GeoNetworking/BTP stack. If this stack is used, the GN packet transport type Single-Hop Broadcasting (SHB) shall be used. In this scenario, only nodes in direct communication range may receive the IMZM. PCI being passed from IMZ basic service to the GeoNetworking/BTP stac... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.3.4.2 Interface to the IPv6 stack and the combined IPv6/GeoNetworking stack | A IMZM may use the IPv6 stack (and possibly GeoNetworking over IPv6) or the combined IPv6/GeoNetworking stack for IMZM dissemination as specified in ETSI EN 302 636-3 [1]. NOTE: When the IMZM dissemination makes use of the combined IPv6/GeoNetworking stack, the interface between the IMZ basic service and the combined I... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.3.5 Interface to the Management entity | The IMZ basic service may exchange primitives with the management entity of the ITS-S via the MF-SAP interface (Figure 1). At receiving ITS-S and when relevant, the IMZ basic service may transfer the received mitigation information to the Management entity. In the case of the ITS-G5 access layer, the IMZ basic service ... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 5.3.6 Interface to the Security entity | The IMZ basic service may exchange primitives with the Security entity of the ITS-S via the SF-SAP interface (Figure 1) using the IF.SF interface provided by the Security entity (Figure 2). The IMZ basic service shall align with the CA basic service to determine whether to subscribe or not to the identity change servic... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6 IMZM dissemination | |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.1 IMZM dissemination concept | |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.1.1 IMZM dissemination requirements | Point-to-multipoint communication, specified in ETSI EN 302 636-3 [1], shall be used for transmitting IMZMs. The IMZM shall be transmitted only from the originating ITS-S in a single hop to the receiving ITS-Ss located in the direct communication range of the originating ITS-S. As specified for the interface to the pro... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.1.2 IMZ basic service activation and termination | For vehicle and personal ITS-S, the IMZ basic service shall be activated with the ITS-S activation of the platform hosting the facilities layer (e.g. swich ON the ITS-S). The IMZ basic service shall be terminated when the ITS-S is deactivated. |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.1.3 IMZM generation frequency management | The IMZM generation frequency is managed by the IMZ basic service. The time interval between two consecutive IMZM generations shall be greater than or equal to T_genImzmMin [1 000 ms] and shall not be superior to T_genImzmMax [5 000 ms]. This corresponds to an IMZM generation rate of 0,2 Hz to 1 Hz. |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.1.4 IMZM generation time requirement | In order to ensure proper interpretation of received IMZMs, each IMZM shall be time-stamped. The time required for generating an IMZM shall be less than 50 ms. The time required for generating an IMZM refers to the time difference between the time at which an IMZM generation is triggered and the time at which the IMZM ... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.1.5 IMZM triggering conditions | As long as the IMZ basic service is active in infrastructure ITS-S, the IMZM generation shall be triggered and managed by the IMZ basic service or by a relevant application. The IMZM generation can be triggered in different ways, as set in the IMZM configuration: • Continuous generation, e.g. continuous generation and ... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.2 IMZM dissemination constraints | |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.2.1 Security constraints | |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.2.1.1 Introduction | A security analysis of IMZ use cases is provided in annex B. ETSI ETSI TS 103 724 V2.1.1 (2021-08) 18 IMZMs that are transmitted over links that cannot be fully trusted (see clause 7 of ETSI TS 102 941 [i.6]), such as radio links, shall be signed using ITS certificates as specified in ETSI TS 103 097 [4]. In particular... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.2.1.2 Authorization Ticket requirements and Service Specific Permissions (SSP) | The Authorization Ticket that is contained in the component signer of SignedData shall have the component appPermissions of type SequenceOfPsidSsp containing the ITS-AID and SSPs for the Interference Management Zone Service. The SSP shall be a BitmapSsp as specified in ETSI TS 103 097 [4]. The SSP for the IMZM is defin... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.2.1.3 Message security requirements | The Authorization Ticket associated to the private key used to sign the IMZM shall be attached to every IMZM, in the component signer of SignedData. The generic security profile as defined in ETSI TS 103 097 [4] shall be applied. Additional HeaderField types are not allowed. |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 6.2.2 General priority constraints | The priority constraint is given by the Traffic Class as specified in ETSI EN 302 636-4-1 [i.4]. |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 7 IMZM Format Specification | |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 7.1 General Structure of a IMZM PDU | An IMZM is composed of: • a common ITS PDU header; • a generation delta time; • a basic container; • an IMZM container; • The IMZM is extensible, but no extensions are defined in the present document. An illustration of the IMZM structure is provided in Figure 4. Detailed data presentation rules shall be as specified i... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 7.2 ITS PDU header | The ITS PDU header shall be as specified in ETSI TS 102 894-2 [2]. Detailed data presentation rules of the ITS PDU header in the context of IMZM shall be as specified in annex A. |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 7.3 Generation Delta Time | The generation time in the IMZM shall be a GenerationDeltaTime as used in ETSI EN 302 637-2 [5] for the CAM. This is a measure of the number of milliseconds elapsed since the ITS epoch, modulo 216 (i.e. 65 536). |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 7.4 Basic container | The basic container provides basic information of the originating ITS-S: • type of the originating ITS-S (e.g. roadSideUnit(15)); • the latest geographic position of the originating ITS-S as obtained by the IMZ basic service at the IMZM generation. The basic container shall be present in each IMZM generated by ITS-Ss i... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 7.5 IMZM container | IMZM generated by infrastructure ITS-S shall include the IMZM container. The IMZM container shall include a sequence of interference management communication zones, as specified in annex A. For each interference management communication zone (DF_InterferenceManagementZone), it shall contain a sequence of the zone defin... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 7.6 IMZM format and coding rules | |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 7.6.1 Common data dictionary | The IMZM format shall make use of the common data dictionary as defined in ETSI TS 102 894-2 [2]. Where relevant, it shall also make use of additional DEs and DFs defined in ETSI EN 302 637-2 [5] and ETSI TS 103 300-3 [6]. Where applicable, DEs and DFs that are not defined in the present document shall be imported from... |
f9547882ee2f363fd382500f81fd5160 | 103 724 | 7.6.2 IMZM data presentation | The IMZM format is presented in ASN.1. Unaligned Packed Encoding Rules (UPER) as defined in Recommendation ITU-T X.691/ISO/IEC 8825-2 [3] shall be used for IMZM encoding and decoding. The ASN.1 representation of IMZM shall be as specified in the annex A of the present document. ETSI ETSI TS 103 724 V2.1.1 (2021-08) 24 ... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 1 Scope | The scope of the present document is to identify a common set of standards and specify configuration parameter values and references required for the implementation of direct communication between ITS stations, to achieve interoperable deployment of ITS services via V2V and V2I links. The scope is limited to communicat... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 2 References | |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 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... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 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... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 3 Definition of terms, symbols and abbreviations | |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 3.1 Terms | For the purposes of the present document, the terms given in C2C-CC BSP [8], C-ROADS RSP [13], C-ROADS MSP [14] and the following apply: C-ITS basic system: cooperative ITS system employing radio communication technologies to exchange messages between ITS stations hybrid system: system combining direct communication ov... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 3.2 Symbols | Void. ETSI ETSI TS 103 723 V1.2.1 (2020-11) 9 |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in C2C-CC Glossary [i.3] and the following apply: 3GPP 3rd Generation Partnership Project 5GAA 5G Automotive Association AM Item identifier prefix for amendments provided in the present document BSP Basic System Profile C2C-CC Car-2-Car Communication Con... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 4 General Requirements | |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 4.1 Introduction | The present document contains individual requirement items which are assigned with unambiguous references starting with "AM_BSP_", and "AM_RSP_", and "AM_MSP_" as prefix for OBU and, RSU and Mobile-RSU requirements, respectively. The unique identifier is useful as a reference for any comments/questions instead of refer... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 4.2 AM_BSP_010 | If not otherwise stated in the present document, the requirements from C2C-CC BSP [8], C2C-CC Feat [9], C2C-CC Trig [10], C2C-CC HSM [11], C-ROADS RSP [13], C-ROADS MSP [14], C-ROADS Func [16], C-ROADS Hyb [17], and C-ROADS Serv [15] shall be adopted for LTE-V2X systems. Version numbers of references given in C2C-CC [1... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5 Requirement Specifications for OBUs | |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1 Applicable Items | |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.1 General requirements | The following requirements shall be applied for an LTE-V2X Basic System and shall amend C2C-CC BSP [8]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.2 AM_BSP_012 | AM_BSP_012 replaces RS_BSP_434 of C2C-CC BSP [8]. The LTE-V2X Basic System's access layer shall be conformant with ETSI EN 303 613 [1] and make use of the Hybrid Automatic Repeat Request (HARQ) mechanism according to ETSI TS 136 321 [19] with parameter setting allowedRetxNumberPSSCH=n1 for one retransmission, as long a... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.3 AM_BSP_014 | AM_BSP_014 replaces RS_BSP_235 of C2C-CC BSP [8]. For "Day 1" applications, the LTE-V2X Basic System shall support the mapping of Traffic Classes (TC) to PPPP levels as defined in table B.7 of ETSI EN 303 613 [1]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.4 AM_BSP_015 | AM_BSP_015 replaces RS_BSP_436 of C2C-CC BSP [8]. The congestion control mechanism of a LTE-V2X Basic System shall be conformant with ETSI TS 103 574 [4]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.5 AM_BSP_016 | AM_BSP_016 replaces RS_BSP_238 of C2C-CC BSP [8]. The LTE-V2X Basic System shall use the parameters as defined in table 1 of ETSI TS 103 574 [4] for the congestion control mechanism in the access layer. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.6 AM_BSP_017 | AM_BSP_017 replaces RS_BSP_240 of C2C-CC BSP [8]. LTE-V2X Basic System shall perform CBR measurements as defined in clause 5.1.30 of ETSI TS 136 214 [18]. ETSI ETSI TS 103 723 V1.2.1 (2020-11) 11 |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.7 AM_BSP_020 | AM_BSP_020 replaces RS_BSP_246 of C2C-CC BSP [8]. When the LTE-V2X Basic System enters a protected communication zone, the LTE-V2X Basic System shall set its power Pregulatory,c according to ETSI TS 136 101 [6] and apply the mitigation techniques as described in RS_BSP_458 or RS_BSP_459 without changing any other conge... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.8 AM_BSP_022 | AM_BSP_022 replaces RS_BSP_267 of C2C-CC BSP [8]. When forwarding packets, the LTE-V2X Basic System shall use the PPPP level as profiled in AM_BSP_014. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.9 AM_BSP_023 | AM_BSP_023 replaces RS_BSP_270 of C2C-CC BSP [8]. All GeoNetworking frames sent by the LTE-V2X Basic System shall use the packet header fields as given in clause D.2 of ETSI EN 303 613 [1]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.10 AM_BSP_027 | AM_BSP_027 replaces RS_BSP_225 of C2C-CC BSP [8]. A LTE-V2X Basic System shall use a sub-band dedicated for C-ITS according to ETSI EN 302 571 [7] for all messages. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.11 AM_BSP_028 | AM_BSP_028 replaces RS_BSP_245 of C2C-CC BSP [8]. Transmission power control shall be applied as specified in ETSI TS 103 574 [4]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.1.12 AM_BSP_029 | AM_BSP_029 amends RS_BSP_443 of C2C-CC BSP [8]. For LTE-V2X Basic System, parameters of RS_BSP_443 shall be adopted, unless otherwise specified in this item. Parameter pGnInterfaceType shall be set to "LTE-V2X". For LTE-V2X Basic System, HARQ retransmission shall be set according to AM_BSP_012 and congestion control pa... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 5.2 Non-Applicable Items | The following items from C2C-CC BSP [8] are not applicable to LTE-V2X Basic System or are covered by appropriate other items: • RS_BSP_228, RS_BSP_397, RS_BSP_293, RS_BSP_435 ETSI ETSI TS 103 723 V1.2.1 (2020-11) 12 |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6 Requirement Specifications for RSUs | |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1 Applicable Items | |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1.1 General requirements | The following requirements shall be applied for a LTE-V2X Basic System. They amend C-ROADS RSP [13] and C-ROADS MSP [14]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1.2 AM_RSP_014 | AM_RSP_014 replaces Sections 3.1.1 and 3.1.2 of C-ROADS RSP [13] and C-ROADS MSP [14]. The access layer of a LTE-V2X Basic System shall comprise of a message protocol stack, which includes Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers according... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1.3 AM_RSP_015 | AM_RSP_015 replaces section 3.1.4 of C-ROADS RSP [13]. The LTE-V2X Basic System's access layer shall conform to AM_BSP_012 and employ congestion control according to AM_BSP_015. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1.4 AM_RSP_016 | AM_RSP_016 replaces RS_RSP_011 of C-ROADS RSP [13]. A LTE-V2X Basic System shall use a sub-band dedicated for C-ITS according to ETSI EN 302 571 [7] for all messages. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1.5 AM_RSP_017 | AM_RSP_017 replaces RS_RSP_072 of C-ROADS RSP [13]. The LTE-V2X Basic System's access layer shall be compliant to the ETSI EN 302 571 [7]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1.6 AM_RSP_018 | AM_RSP_018 replaces sections 3.1.6 and 3.1.7 of C-ROADS RSP [13]. The congestion control mechanism of a LTE-V2X Basic System shall be compliant to ETSI TS 103 574 [4]. The LTE-V2X Basic System shall support the mapping of Traffic Classes (TC) to PPPP levels as defined in table B.7 of ETSI EN 303 613 [1]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1.7 AM_RSP_019 | AM_RSP_019 replaces section 3.2.1 of C-ROADS RSP [13] and C-ROADS MSP [14]. For LTE-V2X Basic System, the network and transport layer shall comply with the specifications ETSI EN 302 636-4-1 [2] and ETSI EN 302 636-5-1 [3], covering the media-independent functionality and the basic transport protocols, respectively. ET... |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1.8 AM_RSP_021 | AM_RSP_021 replaces RS_RSP_035 of C-ROADS RSP [13]. The GeoNetworking (GN) parameter itsGnIfType shall be set to "LTE-V2X" according to ETSI EN 302 636-4-1 [2]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.1.9 AM_RSP_022 | AM_RSP_022 replaces RS_RSP_050 of C-ROADS RSP [13]. All GeoNetworking frames sent by the LTE-V2X Basic System shall use the packet header fields as given in clause D.2 of ETSI EN 303 613 [1]. |
6fb6ea4ca5d726bb2a4439420b241255 | 103 723 | 6.2 Non-Applicable Items | The following items from C-ROADS RSP [13] and C-ROADS MSP [14] are not applicable to LTE-V2X Basic System and are excluded from the LTE-V2X Profile: • RS_RSP_018, RS_RSP_027, RS_RSP_070, RS_RSP_094 ETSI ETSI TS 103 723 V1.2.1 (2020-11) 14 Annex A (informative): Change History Date Version Information about changes 2019... |
179c56242535c70e283548bec0bde828 | 103 720 | 1 Scope | The present document introduces the 5G Broadcast System along with the associated features of such a system. A concrete instantiation of a 5G Broadcast System is specified, referred to as LTE-based 5G Broadcast. LTE-based 5G Broadcast is a profile of existing 3GPP specifications that addresses all requirements of a 5G ... |
179c56242535c70e283548bec0bde828 | 103 720 | 2 References | |
179c56242535c70e283548bec0bde828 | 103 720 | 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... |
179c56242535c70e283548bec0bde828 | 103 720 | 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... |
179c56242535c70e283548bec0bde828 | 103 720 | 3 Definition of terms, symbols and abbreviations | |
179c56242535c70e283548bec0bde828 | 103 720 | 3.1 Terms | For the purposes of the present document, the following terms apply: 5G Broadcast Client API: Application Programming Interface that enable a 5G Broadcast TV/Radio Service Application to communicate with a 5G Broadcast Receiver 5G Broadcast Receiver: entity implementing the receiver requirements of a 5G Broadcast Syste... |
179c56242535c70e283548bec0bde828 | 103 720 | 3.2 Symbols | Void. |
179c56242535c70e283548bec0bde828 | 103 720 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 5GMS 5G Media Streaming ABR Adaptive Bit Rate ADPD Associated Delivery Procedure Document AF Application Function API Application Programming Interface APN Access Point Name ARP Allocation and Retention Priority AV Audio-Visual BCCH Broadcast ... |
179c56242535c70e283548bec0bde828 | 103 720 | 4 General | |
179c56242535c70e283548bec0bde828 | 103 720 | 4.1 Background and history (informative) | While Multimedia Broadcast Multicast Services (MBMS) had been part of 3GPP specifications since Release 6 in 2005 based on UTRAN, and since Release 9 based on LTE (the evolution to LTE is also referred to as "eMBMS"), the dedicated requirements of broadcast service providers were only taken into account in Release 14 s... |
179c56242535c70e283548bec0bde828 | 103 720 | 4.2 Basic features of a 5G Broadcast System | |
179c56242535c70e283548bec0bde828 | 103 720 | 4.2.1 General | Based on the collected use cases and requirements in clause 4.1, a 5G Broadcast System for linear television and radio services as defined in the present document addresses the following features and functionalities: - Support of Free-to-Air (FTA) service. - Broadcast-only service for UEs without an MNO broadcast subsc... |
179c56242535c70e283548bec0bde828 | 103 720 | 4.2.2 Reference architecture | The general architecture for a 5G Broadcast System is provided in figure 4.2.2-1. The principal actors in the system are as follows: - A 5G Broadcast TV/Radio Content Service Provider runs a head-end providing linear television and radio services. - A 5G Broadcast TV/Radio Service Application runs on devices that inclu... |
179c56242535c70e283548bec0bde828 | 103 720 | 4.2.3 Services | The 5G Broadcast System is based on a service concept. A 5G Broadcast Service is offered by the 5G Broadcast System and provides a transport-level service, delivered by a broadcast bearer service across a Radio Access Network (RAN). Such 5G Broadcast Services are announced and can be discovered. Different types of serv... |
179c56242535c70e283548bec0bde828 | 103 720 | 4.2.4 TV/Radio Content Provider and Application requirements | A Content Provider wanting to make use of a 5G Broadcast System needs to provision the 5G Broadcast Services and publish content using the Network API for 5G Broadcast. In addition, a device capable of receiving 5G Broadcast Services needs to integrate a 5G Broadcast TV/Radio Service Application (for example provisione... |
179c56242535c70e283548bec0bde828 | 103 720 | 4.2.5 Public Warning System | ETSI TR 122 968 [i.5] is the output of a 3GPP feasibility study for a Public Warning System (PWS) service capable of sending emergency alerts and public warning messages via the 5G System to a UE-hosted message reception function. The EMTEL specification ETSI TS 102 182 [i.6], ETSI TR 102 444 [i.7], requirements from J... |
179c56242535c70e283548bec0bde828 | 103 720 | 4.3 5G Broadcast Systems | |
179c56242535c70e283548bec0bde828 | 103 720 | 4.3.1 General | A 5G Broadcast System for linear television and radio services shall address the requirements and use cases in clause 4.1, as well as the feature list summarized in clause 4.2.1, the reference architecture described in clause 4.2.2 and the service model documented in clause 4.2.3. |
179c56242535c70e283548bec0bde828 | 103 720 | 4.3.2 LTE-based 5G Broadcast System | The LTE-based 5G Broadcast System is an instantiation of a 5G Broadcast System addressing the basic features documented in clause 4.2 that is based on a profile of 3GPP specifications available in Release 17. As a background, in order to address the identified key issues and requirements, 3GPP developed service layer s... |
179c56242535c70e283548bec0bde828 | 103 720 | 5 LTE-based 5G Broadcast System | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.1 Introduction | According to the introduction in clause 4, and in particular clause 4.3.2, the remainder of the present document defines a 5G Broadcast System based on a continuous evolution of MBMS to meet the use cases and requirements for a dedicated broadcast system for linear television and radio broadcast services, referred to a... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.2 Architecture | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.2.1 Reference architecture | Figure 5.2.1-1 depicts the reference architecture for the LTE-based 5G Broadcast System as defined in the present document. This architecture is a simplified version of the EPS architecture for E-UTRAN only, as defined in ETSI TS 123 246 [5]. ETSI ETSI TS 103 720 V1.2.1 (2023-06) 20 5G Broadcast System 5G Broadcast Rec... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.2.2 Deployment models (informative) | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.2.2.0 Introduction | This clause introduces a non-exhaustive list of deployment models based on the logical reference architecture presented in clause 5.2.1. |
179c56242535c70e283548bec0bde828 | 103 720 | 5.2.2.1 Deployment with separated Core and RAN functions | In a typical deployment of an LTE-based 5G Broadcast System, the core functions of the MBMS GW, MME and BM-SC may be integrated into a single physical device that manages all the 5G Broadcast Services of a 5G Broadcast System. In this case, only a restricted set of 5G Broadcast Transmitter interfaces are of relevance, ... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.2.2.2 Deployment with self-contained 5G Broadcast Transmitter | If a deployment of the 5G Broadcast System requires only one eNodeB, or if Single Frequency Network operation is not required, the eNodeB may be integrated into the same physical entity as the core functions. In this case, only interfaces xMB and Uu are exposed externally by the 5G Broadcast Transmitter, as shown in fi... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.3 5G Broadcast Services | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.3.1 Definition | LTE-based 5G Broadcast, as defined in the present document, instantiates 5G Broadcast Services with MBMS User Services as defined in ETSI TS 123 246 [5] and with the constraints and requirements in the present document in order to carry linear television and radio broadcast services. MBMS User Services are uniquely ide... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.