Page 370 - 5G Basics - Core Network Aspects
P. 370

1                                                Core network aspects


            2)      MC-Streaming is recommended to support different media types (e.g., audio and video) as well as
                    formats (e.g., [ITU-T G.722]) to be delivered from a single source to one or multiple destinations/UE.
            3)      MC-Streaming is recommended to support the delivery of multimedia content throughout different
                    connections simultaneously, especially when multi-connection capability is supported by underlying
                    network elements and accesses.

            4)      MC-Streaming  can  optionally  support  multiple  kinds  of  coding  resolutions  and  aspects  ratios
                    (e.g., ITU-T H.264 video compression).

            5)      MC-Streaming can optionally support live and/or video on-demand (VoD) content offering.
            6)      MC-Streaming can optionally support content or programme selection.
            7)      MC-Streaming  can  optionally  support  integration  with  other  telecommunication  services
                    (e.g., instant message, presence, telephony, etc.).
            8)      Multimedia content can optionally be transmitted to a single destination (e.g., VoD), or to multiple
                    destinations simultaneously (e.g., broadcasting service).

            6.2.2   Interaction requirement
            1)      User interaction is recommended to be supported. Service provider and subscriber of MC-Streaming
                    can  share  interesting  information  within  or  between  them,  including  programme  information,
                    image, data, text, audio, etc.
            2)      MC-Streaming  can  optionally  support  interactive  capabilities  such  as  educational  applications,
                    entertainment applications (e.g., games), communication services (e.g., mail, chat and messaging),
                    and information services (e.g., stock and weather services).
            3)      MC-Streaming can optionally support user generated content to be uploaded and shared to other
                    subscribers.
            4)      MC-Streaming can optionally support download of user generated content.
            5)      MC-Streaming can optionally support mechanisms for users to send user preferences to the server
                    during a streaming session, so that the service providers may offer personalized content markers to
                    the users.
            6)      MC-Streaming can optionally enable a subscriber to share content marker(s) with other subscribers
                    in accordance to legal aspects and operator policies.
            7)      MC-Streaming can optionally support content pushing by the service provider to the UE, which can
                    be requested or not requested by subscriber.
            8)      MC-Streaming can optionally support content filtering mechanisms so that a subscriber can filter
                    unwanted content.


            6.3     QoS/QoE requirements
            The requirements of quality of service (QoS) and quality of experience (QoE) are listed below:
            1)      MC-Streaming is recommended to support a subscriber's required level of QoS/QoE, security and
                    reliability.
            2)      MC-Streaming is recommended to support service continuity (i.e., seamless connection handover).
            3)      MC-Streaming is recommended to support service control to provide a quality at least as good as
                    the quality of any individual access technology under its control.
            4)      MC-Streaming is recommended to allow the delivery of MC-Streaming services with a subscriber's
                    defined quality of experience (QoE).
            5)      MC-Streaming can optionally support mechanisms to monitor audio and video quality.
            6)      MC-Streaming can optionally support consistent QoS.
            7)      MC-Streaming can optionally support mechanisms for QoE/QoS parameters adjustment due to the
                    changes of content characteristics in a connection.



            360
   365   366   367   368   369   370   371   372   373   374   375