Content for  TR 21.917  Word version:  17.0.1

Summary based on the input provided by b<>com in SP-220652. This WI aims at defining 5G communication services requirements for critical medical applications, e.g. medical applications targeting the delivery of serious care to patients, such as:

• Image Assisted Surgery inside hybrid operating rooms equipped with high quality and augmented imaging systems
• Robotic Aided Surgery inside hybrid operating rooms or in remote medical facilities
• Tele-diagnosis and patient vital-signal monitoring in ambulances, hospitals, or remote healthcare facilities

The generated requirements cover network dependability, performances, medical data confidentiality and integrity, network auditability (to demonstrate to regulators that patient safety and privacy is maintained), and more generally specific 5G functionalities. During the work, it has been detected that due to the very specific nature of the targeted vertical, several performance requirements look out of reach for current technology. For example, surgeons pay a lot of attention to video quality (very high resolution, frame rates, …) and repeatedly ask for non-compressed video streams to avoid artifacts and to lower application latencies during non-invasive surgery. This led to very stringent data rate requirements (several dozen or higher Gbps in some identified use cases). Interestingly, it has been noted that some of the requirements covered as part of CMED are similar to those generated by VIAPA (video, imaging, and audio for professional applications) and this has led to a joint specification for the two work items. For VIAPA, see section "Enhanced support of Non-Public Networks". Beside SA1, no specific stage 2 nor stage 3 work could be carried out in 3GPP downstream groups as key performance requirements (bitrate, latency, …) were felt too stringent for current technology generation.

Summary based on the input provided by BBC in xP-22xxxx. AVPROD looks at applications for Programme Making and Special Events (PMSE) and use cases for media production. It looks specifically at PMSE use cases and VIAPA (Video Imaging and Audio for Professional Applications expands this to include areas such as medical and gaming. The documents introduce requirements related to professional video, imaging and audio services. Unlike other consumer multimedia applications envisioned for 3GPP systems, the applications in which this document focuses have more demanding performance targets and includes user devices that are managed in different workflows when compared to typical UEs. This can be divided into two main categories: contribution and production.

• Contribution links are heavily compressed and have lower latency requirements and are used for newsgathering and other programme items. They are currently serviced by satellite or bonded cellular and use the PLMNs
• Production links have higher bandwidth, due to less compression, and challenging latency requirements as well as strict Quality of Service metrics to ensure reliability.

The key parameters for these applications are: System latency: Bandwidth: Quality of Service: VIAPA also highlights service aspects for Non-Public networks, clock synchronization, Network exposure, service continuity and multi-network connectivity. Performance requirements are defined for all applications. There are no specific Stage 2/3 works needed after the Stage 1 requirements, but work has continued in SA4 with the study item on NPNs for media production. Summary based on the input provided by Ericsson in SP-220650. The media production industry uses its own set of codecs, protocols and procedures for IP-based media production. These protocols are (often) targeting dedicated networks installed at a production facility or at a temporary location, which allow transmission of either uncompressed or compressed video at high quality. For the orchestration and configuration of an IP-based media production setup, different solutions are defined. There are cases for which the Media Producer may own their own 5G Network. There are other cases for which the media producer collaborates with a 5G Network operator to support media production events and services. Different collaboration scenarios require different means to establish 5G-based media production connectivity. In deployments, 5G Systems including NPNs may have to be tailored to the needs of each industry vertical and the target use-case in question. The Media Production vertical may want to use the 5G System for different purposes, primarily for sending video and audio from remote locations to a central production studio, but also for return video, tally, talkback, remote device control (connectivity configuration, but also operational control of specialist UE). One aim of the study would be to identify how (in technical terms) media production can beneficially use 5G systems for media production. TR 26.805 documents the findings of the Study on Media Production over 5G NPNs. The document contains an elaborative description on different protocols and workflows used in media production at the time of writing. Several different standardization and industry fora are defining Ethernet- and IP-based protocols for media production purposes. While the study has not identified an urgent technical area for standardisation at this point in time, a number of practical guidelines for implementers are identified and documented in the Technical Report. Those are intended to support media production device manufactures and media producers to leverage different 3GPP features for their purposes. These guidelines may be further promoted and expanded, and more specific aspects are likely worthwhile to be defined. Communication with external organizations such as 5G-MAG is recommended in order to identify if they would follow up on those guidelines to support media production device manufactures and media producers to leverage different 3GPP features for their purposes.

Summary based on the input provided by TELUS in SP-220646. This Study is about potential architecture enhancement to enable 5G multicast-broadcast media streaming. It further provides recommendations for normative specification work on a generic 5G MBS User Service Architecture. The following key issues are studied in this work item:

• Support of Multicast ABR in 5G Media Streaming Architecture
• Nmb2 Design Considerations
• Collaboration and Deployment Scenarios
• Reuse of MBMS Service Layer
• Client Architecture Options
• Hybrid Services
• 5GMS via eMBMS

This study concludes that functional entities for a generic 5G MBS User Service Architecture are determined to be defined in normative specification TS 26.502 to support 5G Multicast-Broadcast applications. It presents a complete service offering to an end-user, via a set of APIs that allows the MBS Client to activate or deactivate reception of the service. The 5MBS User Service architecture is independent of 5G Media Streaming (5GMS) and may or may not be used by 5GMS. 5G Multicast ABR media streaming service could be a User Service where the MBS User Services allow streaming of DASH content as defined in TS 26.501, and it also includes the use of an MBS session to deliver the DASH segments in multicast. When delivering content to a MBS Client, the MBSTF uses one or more MBS Delivery Methods.

Summary based on the input provided by TELUS in SP-221269. This Work Item has resulted in a new specification TS 26.502 entitled "5G multicast-broadcast services, User Service architecture" and in CRs to TS 26.501, to support 5G Media Streaming (5GMS) via eMBMS. TS 26.502 defines the stage 2 5G multicast-broadcast User Services architecture as follows:

1. An MBS User Services network architecture that defines how MBS-related entities are involved in providing MBS User Services delivery and control.
2. An MBS User Services reference architecture model that describes roles of the principal network and UE functions involved.
3. New reference points in order to support MBS User Services, including MBS 4 MC, MBS 4 UC, MBS 5, MBS 6, MBS 7, and MBS 8 beyond the existing reference points defined in TS 23.247.
4. Two distribution methods for multicast/broadcast transport of objects and packets respectively.
5. User Services domain model and dynamic model with relevant parameters for reception reporting, ingestion and announcement.
6. Procedures for 5G Multicast-Broadcast User Services, including baseline procedures, and procedures for user services provisioning, advertisement/discovery, data transfer and data repair.
7. Network function services exposed by MBSF and MBSTF.
8. Informative annexes that documents deployment and collaboration models, Nmb8 User Plane ingest examples, and data model examples.

TS 26.501 further specifies the architecture to allow 5GMS-based downlink media streaming to be deployed as an MBMS-Aware Application on top of eMBMS as defined in TS 23.246, TS 26.346, TS 26.347 and TS 26.348. The procedures for the following uses cases when 5GMS uses eMBMS for delivery are defined:

1. 5GMS content delivered exclusively via eMBMS.
2. 5GMS consumption reporting for eMBMS.
3. 5GMS metrics reporting procedures for eMBMS.
4. Procedures for hybrid 5GMS content delivery via 5G systems and eMBMS.
5. Procedures for dynamic provisioning of 5GMS content delivery via eMBMS.

Collaboration models for 5GMS via eMBMS are documented in an informative annex in TS 26.501. Stage 3 is covered by TS 26.517, TS 26.512, TS 26.346, TS 26.347 and TS 26.348.

For Frequency bands for broadcast, see the section "New bands and bandwidth allocation for 5G terrestrial broadcast - part 1" Other specific broadcasting aspects appear in the sections on "V2V" and on "MC". For Other Media production, professional video aspects, see section on User Plane.