hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
179c56242535c70e283548bec0bde828 | 103 720 | 5.3.2 Service types | The following of types of 5G Broadcast Service are defined: 1) A 5G Broadcast SA Service: A 5G Broadcast Service that provides Service Announcement and originates in the BM-SC (or in the 5G Broadcast Transmitter) and terminates in the MBMS Client (or in the 5G Broadcast Receiver). 2) 5G Broadcast User Service: A 5G Bro... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.3.3 Service provisioning, configuration, announcement and selection | A 5G Broadcast TV/Radio Content Service Provider using a 5G Broadcast System shall support all relevant service provisioning and ingest procedures as defined in clause 5.5.2. 5G Broadcast User Services shall be announced in at least one 5G Broadcast SA Service. To facilitate the discovery of 5G Broadcast Services, in p... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.4 Operation modes | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.4.1 General | For the LTE-based 5G Broadcast System, the BROADCAST MODE as defined in ETSI TS 123 246 [5], clause 5.4.3 shall apply. The phases of MBMS broadcast service provision include: - Service Announcement, for details see clause 5.4.2. - Session Start, for details see clause 5.4.3. - MBMS Notification, for details see clause ... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.4.2 Service announcement and discovery | In order to access a 5G Broadcast Service, the service and its associated parameters need to be properly announced. The MBMS User Service announcement/discovery mechanisms allow receivers to be informed about the MBMS User Services available. Service Announcement is used to distribute to 5G Broadcast Receivers informat... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.4.3 Session Start | Session Start is the point at which the BM-SC is ready to send data. For details, see ETSI TS 123 246 [5], clause 4.4.3.2. |
179c56242535c70e283548bec0bde828 | 103 720 | 5.4.4 MBMS notification | See ETSI TS 123 246 [5], clause 4.4.3.3. |
179c56242535c70e283548bec0bde828 | 103 720 | 5.4.5 Data transfer | See ETSI TS 123 246 [5], clause 4.4.3.4. |
179c56242535c70e283548bec0bde828 | 103 720 | 5.4.6 Session Stop | See ETSI TS 123 246 [5], clause 4.4.3.5. |
179c56242535c70e283548bec0bde828 | 103 720 | 5.4.7 Session Update | Session Update is aligned with ETSI TS 123 246 [5], clause 4.4.3.6, but the following constraints apply: 1) Session Update is used to update specific parameters of an ongoing MBMS Broadcast session. The only parameter which can be updated is the MBMS Service Area. 2) Session Update due to QoS (ARP parameter only) is no... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.4.8 Receive-Only Mode (ROM) | LTE-based 5G Broadcast Services shall be Receive-Only Mode (ROM), i.e. they are intended for consumption on 5G Broadcast Receivers operating in Receive-Only Mode (ROM). According to ETSI TS 123 246 [5], Receive-Only Mode (ROM) is defined as a UE configuration option that allows a UE to receive an eMBMS broadcast servic... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.5 Reference points and protocols | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.5.1 General | According to figure 5.2.1-1, this clause defines the reference points and protocols for the LTE-based 5G Broadcast System instantiation, namely: - For the northbound Network API for 5G Broadcast, a profile of xMB is defined in clause 5.5.2. - For the User Service for 5G Broadcast, a profile of the MBMS User Service is ... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.5.2 xMB profile for 5G Broadcast | The Application Programming Interfaces (APIs) for Multimedia Broadcast/Multicast Service (MBMS) at reference point xMB are defined in ETSI TS 126 348 [10] and ETSI TS 129 116 [11]. The xMB reference point provides the ability for the Content Provider to: - Authenticate and authorize BM-SC(s). - Create, modify and termi... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.5.3 MBMS User Service profile | MBMS User Service protocols and codecs are documented in ETSI TS 126 346 [8] and that specification defines the reference point between the BM-SC (the origin of an MBMS User Service) and the MBMS Client. Only a subset of the MBMS User Service protocols and functionalities are applicable to 5G Broadcast Services. The Us... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.5.4 E-UTRAN Uu profile for 5G Broadcast | The E-UTRAN Uu for 5G Broadcast relies on two main principles: 1) A radio network comprising only MBMS-dedicated cells (as defined in ETSI TS 136 300 [18]) as transmitters; MBMS-dedicated cells support only MBMS transmission and do not support uplink transmission. 2) Receive-Only-Mode (ROM) devices (as defined in ETSI ... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.5.5 Client APIs for 5G Broadcast | For the Client API for 5G Broadcast, the MBMS Application Programming Interfaces (MBMS-APIs) are specified in ETSI TS 126 347 [9] and define the application service interfaces between the MBMS Client and the MBMS-Aware Application. For 5G Broadcast Services, the following MBMS-APIs shall apply: 1) For File Delivery Use... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.6 5G Broadcast procedures | The following MBMS procedures specified in ETSI TS 123 246 [5] shall be supported for LTE-based 5G Broadcast: - MBMS Session Start Procedure for E-UTRAN and UTRAN for EPS. - MBMS Session Stop Procedure for E-UTRAN and UTRAN for EPS. - MBMS Broadcast Service Activation. - MBMS Broadcast Service De-activation. - BM-SC-in... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.7 Security | For 5G Broadcast, the following security considerations apply: - A ROM device does not support signalling procedures, including registration with a PLMN. - A ROM device is not equipped with a USIM. Therefore, security procedures with a PLMN are not supported. If security is required for 5G Broadcast, it shall be implem... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.8 Charging | For 5G Broadcast, the following charging considerations apply: - A ROM device does not support signalling procedures, including registration with a PLMN. - A ROM device is not equipped with a USIM. Therefore, charging by a PLMN is not supported. If charging is required for 5G Broadcast, charging can be implemented usin... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.9 Roaming | Roaming does not apply. |
179c56242535c70e283548bec0bde828 | 103 720 | 5.10 TV Service Configuration Management Object | If the Service Announcement is further supported by an application to MBMS Client communication through the MBMS-API, then the receiver configuration procedure for a 5G Broadcast Receiver can be achieved by the application providing relevant information obtained from a TV Service Configuration MO to the MBMS Client. Th... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.11 Temporary Mobile Group Identity | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.11.1 Introduction | 5. |
179c56242535c70e283548bec0bde828 | 103 720 | 11.1 Introduction | The Temporary Mobile Group Identity (TMGI) is used for MBMS notification purposes to uniquely identify MBMS bearer services. The BM-SC allocates a globally unique TMGI per MBMS bearer service. The structure of the TMGI is defined in clause 15.2 of ETSI TS 123 003 [3], but also shown in figure 5.11.1-1. The TMGI is a ra... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.11.2 TMGIs for 5G Broadcast Services | An LTE-based 5G Broadcast Service is a Receive-Only Mode (ROM) service as well as a broadcast TV service. According to clause 6.3 of ETSI TS 124 116 [6], for the TMGI in the case of Receive-Only Mode, the first hexadecimal digit (i.e. the four most significant bits) of the MBMS Service ID is used to signal the type of ... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.11.3 TMGI Management for 5G Broadcast Services | Two different types of 5G Broadcast Service provider exist: 1) A 5G Broadcast Service provider may use TMGIs from the reserved range on the globally assigned PLMN ID 901 56. However, note that MBMS Service IDs are not globally unique in the sense that two service providers may use the same TMGI from the reserved range ... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.12 Discovering 5G Broadcast Services | For discovering all available 5G Broadcast Services, a 5G Broadcast Receiver shall identify all PLMNs that carry 5G Broadcast Services. NOTE: PLMNs may be identified by RAN parameters as defined in clause 5.3.3. Then, for each identified PLMN carrying at least one 5G Broadcast Service, a 5G Broadcast Receiver shall fin... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.13 RAN configuration options (informative) | Two important features for the radio access network documented in clause 4.2 are the support for: - Single Frequency Network (SFN) deployments with Inter-Site Distance (ISD) significantly larger than a typical ISD associated with typical cellular deployments with ISD > 100 km to support receivers with high-gain rooftop... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.14 5G Broadcast TV/Radio Service Application requirements | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.14.1 Introduction | This clause documents the requirements for a 5G Broadcast TV/Radio Application to interface and make use of the LTE-based 5G Broadcast System to set up and consume 5G Broadcast Services. |
179c56242535c70e283548bec0bde828 | 103 720 | 5.14.2 Supported content formats | A 5G Broadcast TV/Radio Service Application can make of use of different 5G Broadcast User Services as defined in clause 5.3: - UDP Proxy. - IP Packet Routing. - File Delivery. - Segment Streaming. The User Services and content formats supported by a 5G Broadcast TV/Radio Service Application using 5G Broadcast Services... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.14.3 Application Programming Interface conformance | The 5G Broadcast TV/Radio Service Application shall be an MBMS-Aware application that supports the Application Programming Interfaces of the MBMS-APIs as profiled in clause 5.5.5. |
179c56242535c70e283548bec0bde828 | 103 720 | 5.14.4 Application-based Service Announcement | The 5G Broadcast TV/Radio Service Application may support service discovery by providing either the Service Announcement generated by the BM-SC or the TV Service Configuration MO to the 5G Broadcast Receiver using the Application Programming Interfaces of the MBMS-APIs as profiled in clause 5.5.5. |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15 Public Warning System support | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.1 Reference architecture | This clause extends the basic reference architecture in clause 5.2, adding the Cell Broadcast Service to support the Public Warning System (PWS) introduced in clause 4.2.5. Figure 5.15.1-1 depicts the extended reference architecture for the LTE-based 5G Broadcast System including Public Warning System. This architectur... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.2 Warning message delivery procedures | Following the description in clause 9.1.3.4 of ETSI TS 123 041 [35], the warning message to be broadcast is delivered via MMEs to multiple eNodeB instances. The eNodeB instance(s) are responsible for scheduling the broadcast of the new message and the repetitions in each cell. The warning message delivery procedure is ... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.3 Reference points and protocols for Public Warning System | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.3.1 General | According to figure 5.15.2-1, this clause defines the reference points and protocols for the LTE-based 5G Broadcast System instantiation of the Public Warning System, namely: • For the CBE-CBC interface, a profile of CAP is defined in clause 5.15.3.2. • For the 5G Broadcast RAN, a profile of E-UTRAN Uu is defined in cl... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.3.2 CBE-CBC interface | Version 1.2 of the Common Alerting Protocol (CAP), as defined in [38] shall be supported at the CBE-CBC interface, together with a common set of Internet protocols. The use of this profile allows a Public Warning Service (PWS) provider acting as a CBE to connect to the CBC in the 5G Broadcast Transmitter. The protocol ... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.3.3 E-UTRAN Uu usage in Public Warning System for 5G Broadcast | PWS warning messages shall be sent in the 5G Broadcast System via the Commercial Mobile Alert Service (CMAS) as described in this clause. The alerts are delivered via the E-UTRAN Uu downlink within broadcast messages, called System Information Block (SIB) messages. A 5G Broadcast Transmitter (i.e. an eNodeB) broadcasts... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.4 CBC operation: Mapping from CBE-CBC to E-UTRAN-Uu | The functional requirements for the Cell Broadcast Centre (CBC) are described in clause 5 of ETSI TS 123 041 [35] and shall apply when a CBC is instantiated in a 5G Broadcast Transmitter. In summary, the following functions shall be supported in order to manage the Cell Broadcast System (CBS) messages that are used to ... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.5 5G Broadcast Receiver support for Public Warning System | |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.5.1 General UE functionality | A 5G Broadcast Receiver implementing a PWS Client shall process SIB12 messages received on the E-UTRAN Uu downlink within broadcast messages according to the recommendations in clause 8.1 of ETSI TS 123 041 [35]. A summary of PWS Client functionality is provided below: - Discard corrupt CMAS messages received on the ra... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.5.2 Presentation of warning messages by PWS Client | The PWS Client in the 5G Broadcast Receiver provides a CMAS-capable User Interface, as defined in clause 6.2 of ETSI TS 122 268 [i.8]. According to clause 8.1 of ETSI TS 123 041 [35], the precise method of display of PWS warning messages is outside the scope of 3GPP specifications. Aligning with the requirements in cla... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.5.3 Duplication detection | For the detection and handling of duplicated messages, refer to clause 8.2 of ETSI TS 123 041 [35]. 5.15.6 Scenarios for UEs receiving PWS warning messages from 5G Broadcast Typically, it is assumed that MNO PLMNs distribute the same emergency alerts in a region where emergency alerts are also distributed through 5G Br... |
179c56242535c70e283548bec0bde828 | 103 720 | 5.15.7 Emergency media services delivered via 5G Broadcast | Special purpose radio or TV services may be provisioned as 5G Broadcast User Services in emergency situations using the service establishment procedures defined in clause 5.3. Service announcement for such 5G Broadcast User Services may be transmitted by the 5G Broadcast Transmitter on a regular basis. However, in orde... |
179c56242535c70e283548bec0bde828 | 103 720 | 6.1 Introduction | This clause provides requirements for the transmitter of an LTE-based 5G Broadcast System as defined in clause 5. This function is referred to as 5G Broadcast Transmitter. |
179c56242535c70e283548bec0bde828 | 103 720 | 6.2 Broadcast-Multicast Service Centre (BM-SC) | The 5G Broadcast Transmitter shall include a BM-SC function with the following functions: - Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point are defined in ETSI TS 126 348 [10] with the constraints described in clause 5.5.2. - MBMS User Serv... |
179c56242535c70e283548bec0bde828 | 103 720 | 6.3 MBMS GW | The 5G Broadcast Transmitter shall include an MBMS GW function. The functions of an MBMS GW in the 5G Broadcast System are specified in ETSI TS 123 246 [5]. |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4 E-UTRAN | |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4.1 General | The 5G Broadcast Transmitter shall include an eNodeB function with all functionalities defined in the rest of this clause 6.4. |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4.2 MBMS-dedicated cells | The E-UTRAN part of a 5G Broadcast Transmitter shall consist of MBMS-dedicated cells only, as defined in ETSI TS 136 300 [18]. According to [18], MBMS-dedicated cells support strictly (downlink) MBMS transmission and do not support uplink transmission. MBSFN subframes of a MBMS-dedicated cell do not have a control regi... |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4.3 Architecture, protocol stack and E-UTRAN interfaces | The E-UTRAN architecture of a 5G Broadcast System shall adhere to the MBMS architecture in ETSI TS 136 300 [18], clause 15.1.1. The E-UTRAN user plane and control plane protocol stacks architecture shall adhere to the description in ETSI TS 136 300 [18], clause 15.1.2 and clause 15.1.3, respectively. The E-UTRAN interf... |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4.4 Frame structure and numerologies | The following applies on frame structures and numerologies: - Only frame structure type 1 shall be used. - All numerologies specified in ETSI TS 136 211 [16] shall be supported. For subframes using Df other than 0,370 kHz, the frame structure shall be according to figure 6.4.4-1. For transmissions using Df = 0,370 kHz,... |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4.5 MBMS transmission | MBMS transmission shall be performed according to ETSI TS 136 300 [18], clause 15.3.3. MCCH configuration and scheduling shall be performed according to [18], clause 15.3.5 and ETSI TS 136 331 [21], clause 5.8.1, except that the MBMS Service Counting procedure is not supported. MCCH information acquisition shall be per... |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4.6 Physical channels and signals | The E-UTRAN shall support downlink physical channels only. The general structure of downlink physical channels is specified in ETSI TS 136 211 [16]. Only the following physical channels are supported according to [16]: - PMCH; - PDSCH; CAS #1 #2 #3 ………… #13 One 1m subframe One 3ms slot, one symbol per slot Four radio f... |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4.7 MAC layer | The MAC layer signal shall be compatible with the 5G Broadcast Receiver requirements as defined in clause 7.3.4. |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4.8 RLC layer | The BCCH shall use the RLC-TM mode. MTCH and MCCH shall use the RLC-UM mode. RLC operation for MTCH and MCCH shall be used as described in ETSI TS 136 300 [18], clause 15.3.3. |
179c56242535c70e283548bec0bde828 | 103 720 | 6.4.9 RRC layer | The RRC layer shall be compatible with a 5G Broadcast Receiver requirements as defined in clause 7.3.6. |
179c56242535c70e283548bec0bde828 | 103 720 | 6.5 System Information | A 5G Broadcast Transmitter shall implement System Information (SI) as specified in ETSI TS 136 321 [20], clause 5.2. In an MBMS-dedicated cell, non-MBSFN subframes are used for providing MasterInformationBlock-MBMS (MIB-MBMS) and SystemInformationBlockType1-MBMS. SIBs other than SystemInformationBlockType1-MBMS are car... |
179c56242535c70e283548bec0bde828 | 103 720 | 6.6 Cell Broadcast Centre and MME for Public Warning System | The 5G Broadcast Transmitter may include a Cell Broadcast Centre (CBC) for Public Warning System services. In this case, the 5G Broadcast transmitter shall: - Support a CBE-CBC interface according to the requirements specified in clause 5.15.3.2. - Generate emergency alerts and public warning messages as specified in c... |
179c56242535c70e283548bec0bde828 | 103 720 | 7 Receiver Requirements for LTE-based 5G Broadcast | |
179c56242535c70e283548bec0bde828 | 103 720 | 7.1 Introduction | This clause provides requirements for the receiver of an LTE-based 5G Broadcast System as introduced in clause 5. This function is referred to as 5G Broadcast Receiver. |
179c56242535c70e283548bec0bde828 | 103 720 | 7.2 General | A 5G Broadcast Receiver shall support Receive-Only Mode (ROM) device functionalities with further constraints defined in this clause. As examples, ROM devices support MBMS transmission but do not support uplink transmission. ROM devices may not have USIM. As such, ROM devices do not support two-way signalling procedure... |
179c56242535c70e283548bec0bde828 | 103 720 | 7.3 Access Stratum | |
179c56242535c70e283548bec0bde828 | 103 720 | 7.3.1 General | Since a ROM device does not support uplink transmission or two-way signalling procedures, and does not include a USIM, it cannot and does not need to support all the physical layer procedures of a conventional UE. By the same token, only a subset of idle mode procedures and RRM requirements applicable to a conventional... |
179c56242535c70e283548bec0bde828 | 103 720 | 7.3.2 Physical layer procedures | A 5G Broadcast Receiver shall support the following physical layer procedures specified in ETSI TS 136 213 [17]: - Cell search; - Timing synchronization; - PDSCH procedures; - PDCCH assignment procedure; and - PMCH procedures. The system shall be bootstrapped with the Cell Acquisition Subframe (CAS) transmitted using a... |
179c56242535c70e283548bec0bde828 | 103 720 | 7.3.3 Idle mode procedures | A 5G Broadcast Receiver shall support the following idle mode procedures specified in ETSI TS 136 304 [19]: - Cell selection; and - Cell reselection. PLMN prioritization for cell reselection as specified in ETSI TS 136 304 [19], clause 5.2.4.1 shall be supported with the following exception: - NAS layer PLMN selection ... |
179c56242535c70e283548bec0bde828 | 103 720 | 7.3.4 MAC layer | The MAC layer of a 5G Broadcast Receiver shall support: - BCH reception for BCCH; - DL-SCH reception for BCCH; and - MCH reception for MCCH/MTCH. BCH reception and DL-SCH reception in the MAC layer of a 5G Broadcast Receiver shall use transparent MAC according to ETSI TS 136 321 [20], i.e. single a MAC PDU per TTI with... |
179c56242535c70e283548bec0bde828 | 103 720 | 7.3.5 RLC layer | For the RLC layer of the 5G Broadcast Receiver the following applies: - The BCCH shall support the RLC-TM mode. - RLC operation for MTCH and MCCH shall be used as described in ETSI TS 136 300 [18], clause 15.3.3. |
179c56242535c70e283548bec0bde828 | 103 720 | 7.3.6 RRC layer | The RRC layer of the 5G Broadcast Receiver shall support: - System Information reception including SIB and MIB (see ETSI TS 136 331 [21], clause 5.2) in an MBMS- dedicated cell; and - MBMS reception (see ETSI TS 136 331 [21], clause 5.8) in an MBMS-dedicated cell. For System Information reception, the following shall a... |
179c56242535c70e283548bec0bde828 | 103 720 | 7.3.7 RRM requirements | 5G Broadcast Receivers shall support the following requirements specified in ETSI TS 136 133 [15]: - Cell selection; and - Cell reselection, except for: - IRAT reselection; - paging-related requirements; and - CSG cell-related requirements. |
179c56242535c70e283548bec0bde828 | 103 720 | 7.3.8 Demodulation requirements | 5G Broadcast Receivers shall support, for the supported features, the demodulation requirements in ETSI TS 136 101 [14], clauses 10.3.3 and 10.4. In particular, this includes: - Minimum performance requirements for MBMS-dedicated cells. - Support for dual antenna reception for numerologies other than 0,37 kHz SCS. |
179c56242535c70e283548bec0bde828 | 103 720 | 7.4 MBMS Client | An MBMS Client for a 5G Broadcast Receiver shall support UE behaviour in Receive-Only Mode as defined in annex E of ETSI TS 123 246 [5]. A 5G Broadcast Receiver shall support: - MBMS User Services with the constraints from clause 5.5.3. - The MBMS-APIs with the constraints from clause 5.5.5. - The discovery of 5G Broad... |
179c56242535c70e283548bec0bde828 | 103 720 | 7.5 Codec and format requirements | In order to provide consistency for media consumption, a 5G Broadcast Receiver should support the 5GMS Television (TV) profile as defined in clause 5.4 of ETSI TS 126 511 [30]. The 5GMS TV Profile includes, among others: - Requirements and recommendations on audio and video codecs, as well as subtitling. - Requirements... |
179c56242535c70e283548bec0bde828 | 103 720 | 7.6 Public Warning System support | A 5G Broadcast Receiver should support receiver functionalities for emergency alerts and public warnings as specified in clause 5.15.5. 5G Broadcast Receivers that are unable to access system information from any network other than the 5G Broadcast network should monitor the 5G Broadcast network for CMAS warning messag... |
179c56242535c70e283548bec0bde828 | 103 720 | 8 Spectrum and Frequency Bands (informative) | The supported bandwidth for LTE-based 5G Broadcast in units of MHz are 1,4; 3; 5; 6; 7; 8; 10; 15 and 20. No additional spectrum or frequency band configurations are considered in this version of the present document. NOTE: At the time of completion of the present document, 3GPP has ongoing work to support specific fre... |
179c56242535c70e283548bec0bde828 | 103 720 | 9.1 General (informative) | 5G Broadcast Services impose no requirements on the support of a unicast connection. However, a UE may choose to support unicast in addition to 5G Broadcast Services. As one example of such an architecture, a UE may include an independent unicast modem and stack as illustrated in ETSI TS 123 246 [5], figure E-1. The fi... |
179c56242535c70e283548bec0bde828 | 103 720 | 9.2 Hybrid 5G Broadcast operation (informative) | The 5G Broadcast TV/Radio service content provider may provider a richer and more advanced application service to a UE that also supports unicast. This is shown in figure 9.2-1. UE 5G Broadcast Transmitter 5G Broadcast TV/Radio Service Content Provider 5G Broadcast Receiver 5G Broadcast TV/Radio Service Application App... |
179c56242535c70e283548bec0bde828 | 103 720 | 9.3 5GMS via LTE-based 5G Broadcast | |
179c56242535c70e283548bec0bde828 | 103 720 | 9.3.1 Overview | The 5G Media Streaming (5GMS) architecture defined in ETSI TS 126 501 [29] may be deployed on top of LTE-based 5G Broadcast using MBMS User Services as defined in ETSI TS 126 501 [29], clauses 4.6 and 5.10. This arrangement allows 5GMS-based downlink media streaming to be deployed as an MBMS-Aware Application on top of... |
179c56242535c70e283548bec0bde828 | 103 720 | 9.3.2 Procedures | Based on the architecture described in clause 9.3.1, the procedures defined in ETSI TS 126 501 [29], clause 5.10 shall be re-used in the context of 5G Broadcast in particular to support the following scenarios: - 5GMS content delivered exclusively via 5G Broadcast based on the procedures in ETSI TS 126 501 [29], clause... |
179c56242535c70e283548bec0bde828 | 103 720 | 9.3.3 Protocols | In order to support 5G Media Streaming via 5G Broadcast and the scenarios and procedures described in clause 9.3.2, a system implementing 5G Media Streaming over LTE-based 5G Broadcast shall support the following protocols based on ETSI TS 126 501 [29], clause 4.6.2 and clause 4.6.3, as well ETSI TS 126 512 [31], claus... |
179c56242535c70e283548bec0bde828 | 103 720 | 9.3.4 5GMS profiles, codecs and formats | In order to support 5G Media Streaming via 5G Broadcast and the scenarios and procedures defined in clause 9.3.2, a system shall support the Television (TV) profile as specified in ETSI TS 126 511 [30], clause 5.4. |
179c56242535c70e283548bec0bde828 | 103 720 | 9.3.5 MBMS User Service signalling | In order to signal that the application service conforms to 5G Media Streaming formats, the 5G Broadcast Transmitter should signal the MBMS features to the 5G Broadcast Receiver as specified in clause 11.9 of ETSI TS 126 346 [8], indicating that the service is a 5GMSd service (i.e. using the feature value 29). ETSI ETS... |
179c56242535c70e283548bec0bde828 | 103 720 | 9.3.6 Receiver requirements | A 5G Broadcast Receiver supporting 5GMS via 5G Broadcast shall support: - The procedures in clause 9.3.2. - The protocols and reference points in clause 9.3.3. - The 5GMS profiles, codecs and formats in clause 9.3.4. - The reception of services with MBMS feature value 29 as introduced in clause 9.3.5. |
179c56242535c70e283548bec0bde828 | 103 720 | 10 5G Broadcast Receiver Categories | |
179c56242535c70e283548bec0bde828 | 103 720 | 10.1 Introduction | The present document defines receiver categories in order to support various deployment scenarios. MBMS features as defined in ETSI TS 126 346 [8] enable the BM-SC to signal to the UE the set of capabilities that are required for the consumption of the MBMS user service. The MBMS features with the respective MBMS Featu... |
179c56242535c70e283548bec0bde828 | 103 720 | 10.2 LTE-based 5G Broadcast Base Receiver | Devices implementing the LTE-based 5G Broadcast Base Receiver shall support: - All requirements in clause 7 for an LTE-based 5G Broadcast Receiver. - The reception of signals with sub-carrier spacing of 1,25 kHz. Other sub-carrier spacings from table 6.4.4-1 may also be supported. The requirements for the support of LT... |
179c56242535c70e283548bec0bde828 | 103 720 | 10.3 LTE-based 5G Broadcast Main Receiver | Devices implementing the LTE-based 5G Broadcast Main Receiver category shall support: - All requirements in clause 7 for an LTE-based 5G Broadcast Receiver. - The reception of signals with all the sub-carrier spacings defined in table 6.4.4-1. The requirements for the support of LTE-based 5G Broadcast Main Receiver fun... |
179c56242535c70e283548bec0bde828 | 103 720 | 10.4 5GMS via LTE-based 5G Broadcast Receiver | Devices implementing the 5GMS via LTE-based 5G Broadcast Receiver category shall support: - All requirements in clause 7 for an LTE-based 5G Broadcast Receiver. - All requirements in clause 9.3.5 for a 5GMS via 5G Broadcast Receiver. The requirements for the support of LTE-based 5G Broadcast Main Receiver functionaliti... |
179c56242535c70e283548bec0bde828 | 103 720 | 10.5 LTE-based 5G Broadcast Emergency Alerts Receiver | Devices implementing the LTE-based 5G Broadcast Emergency Alerts Receiver shall support: - The requirements in clause 7 for an LTE-based 5G Broadcast Receiver to at least receive system acquisition signals PSS/SSS and physical channels PBCH, PDCCH and PDSCH. - All requirements in clause 7.6. More detailed implementatio... |
179c56242535c70e283548bec0bde828 | 103 720 | 11.2 BM-SC, MME and MBMS GW | As BM-SC, MME and MBMS GW functionalities are significantly down-scoped by the present document, the functionalities may be provided in a single physical entity. |
179c56242535c70e283548bec0bde828 | 103 720 | 11.3 E-UTRAN | |
179c56242535c70e283548bec0bde828 | 103 720 | 11.3.1 Examples of capacity for the physical layer | Tables 11.3.1-1 and 11.3.1-2 show the physical layer capacity for the supported numerologies for MBMS transmission over PMCH as summarized in table 6.4.4-1 for a bandwidth of 8 MHz (PMCH bandwidth of 40 PRBs). For both table 11.3.1-1 and table 11.3.1-2, it is assumed that the UE is configured by higher layers to decode... |
179c56242535c70e283548bec0bde828 | 103 720 | 12.1 Introduction | This clause provides selected implementation guidelines for 5G Broadcast Receivers. |
179c56242535c70e283548bec0bde828 | 103 720 | 12.2 UE Access Stratum | |
179c56242535c70e283548bec0bde828 | 103 720 | 12.2.1 Idle mode measurements | Requirements for measurements in idle mode in ETSI TS 136 133 [15] are expressed in terms of DRX cycle length. A ROM device does not support the DRX cycle and E-UTRAN in the 5G Broadcast System does not support it. Therefore, it is not to be expected that the E-UTRAN will broadcast the DRX cycle length in the System In... |
179c56242535c70e283548bec0bde828 | 103 720 | 12.2.2 Idle mode states | Neither the 5G Broadcast System nor ROM devices support paging. Therefore, idle mode states described in the cell selection and re-selection procedure in ETSI TS 136 304 [19] are not applicable in the form in which they are specified. In particular, the Camped Normally state and the Camped on Any Cell state mandate tha... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.