Method and apparatus for mapping DASH to WebRTC transmissions

By mapping DASH content to WebRTC transmission sessions, the problem that WebRTC does not support large-scale DASH content distribution is solved, and fast delivery and efficient DASH content distribution is achieved, reducing processing overhead and improving user experience.

CN119072915AActive Publication Date: 2024-12-03QUALCOMM INC
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202380031994.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-04-25
Filing Date
2023-04-26
Publication Date
2024-12-03
Estimated Expiration
2043-04-26

AI Technical Summary

Technical Problem

WebRTC currently does not support large-scale content distribution, especially in the large-scale distribution of DASH content to endpoint computing devices, without defining how to set up and provide adaptive bit rate adaptation based on DASH sessions on WebRTC.

Method used

By mapping DASH content to WebRTC transport sessions, large-scale content distribution is supported, and DASH sessions that include rate adaptation based on adaptive bit rate encoding are provided and established from a server providing DASH content to an endpoint computing device that provides DASH content with a server providing DASH content to a terminal computing device using WebRTC sessions Let DASH sessions be provided and set up through WebRTC, and DASH content is delivered to the endpoint computing device using WebRTC sessions.

Benefits of technology

It reduces the end-to-end waiting time when DASH content is distributed, realizes the reuse of encryption context, reduces the processing overhead when delivering DASH content, and improves the operation efficiency and user experience of the communication network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072915A_ABST
    Figure CN119072915A_ABST
Patent Text Reader

Abstract

Various embodiments include systems and methods for delivering dynamic adaptive streaming (DASH) content based on a hypertext transfer protocol over web real-time communication (WebRTC). Various embodiments may enable mapping of DASH content onto a WebRTC transmission session. Various embodiments may enable reuse of encrypted context.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related Applications

[0002] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 363,707, filed on April 27, 2022, entitled “MANAGING REORDERING TIMERS,” the entire contents of which are incorporated herein by reference for all purposes. Background Art

[0003] Long Term Evolution (LTE), 5G New Radio (NR) (5GNR), and other recently developed communication technologies allow wireless devices to communicate information at data rates (e.g., in gigabits per second, etc.) that are orders of magnitude greater than those available just a few years ago.

[0004] Today's communications networks are also more secure, resilient to multipath fading, allow for lower network traffic latency, and provide better communications efficiency (e.g., in bits per second used per unit of bandwidth, etc.). These and other recent improvements have enabled the emergence of the Internet of Things (IoT), massive machine-to-machine (M2M) communication systems, autonomous vehicles, and other technologies that rely on continuous and secure communications. Summary of the invention

[0005] Various aspects include systems and methods for delivering Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content via Web Real-Time Communication (WebRTC). Various aspects may enable mapping of DASH content onto WebRTC transport sessions. Various aspects may enable reuse of encryption contexts.

[0006] Various aspects may include methods executed by a processor of an endpoint computing device to receive Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content via Web Real-Time Communication (WebRTC), the methods comprising: sending a request for a manifest file for the DASH content to a server; and receiving a reply to the request from the server, the reply including the manifest file for the DASH content and an indication that WebRTC can be used to deliver the DASH content.

[0007] Some aspects may further include: determining one or more DASH content components of the DASH content to be consumed based at least in part on parsing the manifest file; selecting WebRTC to receive one or more DASH content components of the DASH content based at least in part on an indication that WebRTC can be used to deliver the DASH content; and sending a proposal to the server to establish a WebRTC session, the proposal including an indication of one or more DASH content components of the DASH content. Some aspects may further include: receiving an acceptance message from the server to establish the WebRTC session, wherein the acceptance message may include an object indicating a mapping between each corresponding media stream of the WebRTC session and a DASH component of the one or more DASH components of the DASH content assigned to the corresponding media stream. Some aspects may further include: receiving the DASH content from the server via at least one corresponding media stream of the WebRTC session.

[0008] In some aspects, the proposal to establish the WebRTC session may further include an indication of one or more streaming attributes. In some aspects, the one or more streaming attributes are one or more of bandwidth, width, height, frame rate, codec, and file type.

[0009] In some aspects, the indication that WebRTC can be used to deliver the DASH content may include an indication that the server has WebRTC capabilities and an indication of a signaling endpoint for use in a WebRTC session. In some aspects, the indication that WebRTC can be used to deliver the DASH content may further include an indication of a signaling protocol for use in establishing the WebRTC session.

[0010] In some aspects, the one or more DASH content components of the DASH content are one or more adaptation sets of the DASH content.In some aspects, the manifest file of the DASH content may be a media presentation description.

[0011] Some aspects may further include: receiving an indication from the server that an encryption context between a common encryption and a Datagram Transport Layer Security (DTLS) (DTLS-SRTP) of a Secure Real Time Protocol (SRTP) can be reused in the WebRTC session; obtaining a key for the DASH content from an encryption server in response to receiving an indication from the server that an encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session; and using the obtained key to decrypt the SRTP packet payload of the DASH content received in the WebRTC session.

[0012] Further aspects include a wireless device having a processor configured with processor-executable instructions for performing the operations of any of the methods outlined above. Further aspects include a wireless device having means for performing the functions of any of the methods outlined above. Further aspects include a non-transitory processor-readable medium having processor-executable instructions stored thereon, the processor-executable instructions configured to cause the processor of the wireless device to perform the operations of any of the methods outlined above.

[0013] Some aspects include a method performed by a processor of a server to deliver dynamic adaptive streaming over hypertext transfer protocol (DASH) content via web real-time communication (WebRTC), the method comprising: sending a reply to a request for a manifest file of DASH content from an endpoint computing device, wherein the reply may include the manifest file of the DASH content and an indication that WebRTC can be used to deliver the DASH content. In some aspects, the indication that WebRTC can be used to deliver the DASH content may include an indication that the server has WebRTC capabilities and an indication of a signaling endpoint for use in a WebRTC session. In some aspects, the indication that WebRTC can be used to deliver the DASH content may further include an indication of a signaling protocol for use in establishing the WebRTC session.

[0014] Some aspects may further include: receiving a proposal to establish a WebRTC session from the endpoint computing device, the proposal including an indication of one or more DASH content components of the DASH content; establishing the WebRTC session, the WebRTC session including a corresponding media stream for each of the indicated one or more DASH components of the DASH content; generating an object indicating a mapping between each corresponding media stream of the WebRTC session and the DASH component assigned to the corresponding media stream in the DASH content; and sending an acceptance message to the endpoint computing device to establish the WebRTC session, wherein the acceptance message may include an object indicating the mapping. Some aspects may further include: delivering the DASH content to the endpoint computing device using at least one corresponding media stream of the WebRTC session. In some aspects, the proposal from the endpoint computing device to establish the WebRTC session may further include an indication of one or more streaming attributes. In some aspects, the one or more streaming attributes are one or more of bandwidth, width, height, frame rate, codec, and file type.

[0015] In some aspects, the one or more DASH content components of the DASH content are one or more adaptation sets of the DASH content.In some aspects, the manifest file of the DASH content may be a media presentation description.

[0016] Some aspects may further include: determining whether an encryption context between a common encryption and a Datagram Transport Layer Security (DTLS) (DTLS-SRTP) of a Secure Real Time Protocol (SRTP) can be reused in the WebRTC session; and in response to determining that the encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session: sending an indication to the endpoint computing device that the encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session; and delivering the DASH content to the endpoint computing device without applying further encryption.

[0017] Further aspects may include a server having a processor configured to perform one or more operations of any of the methods outlined above. Further aspects include a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a network server to perform the operations of any of the methods outlined above. Further aspects include a server having means for performing the functions of any of the methods outlined above. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the claims and, together with the general description given above and the detailed description given below, serve to explain features of the claims.

[0020] Figure 1A is a system block diagram illustrating an example communication system suitable for implementing any of the various embodiments.

[0021] Figure 1B is a system block diagram illustrating an example decomposed base station architecture of a wireless communication system suitable for implementing any of the various embodiments.

[0022] Figure 2 is a component block diagram illustrating an example computing and wireless modem system suitable for implementing any of the various embodiments.

[0023] Figure 3 is a component block diagram illustrating a software architecture including a radio protocol stack for a user plane and a control plane in wireless communications suitable for implementing any of the various embodiments.

[0024] Figure 4 is a system block diagram of an example content delivery network (CDN) in accordance with various embodiments.

[0025] Figure 5is a process flow diagram illustrating a method that may be performed by a processor of an endpoint computing device to receive Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content over Web Real-Time Communications (WebRTC) in accordance with various embodiments.

[0026] Figure 6 is a process flow diagram illustrating a method that may be performed by a processor of a server to deliver DASH content over WebRTC in accordance with various embodiments.

[0027] Figure 7 is a process flow diagram illustrating a method that may be performed by a processor of a server to deliver DASH content over WebRTC in accordance with various embodiments.

[0028] Figure 8 is a process flow diagram illustrating a method that may be performed by a processor of an endpoint computing device to receive DASH content over WebRTC in accordance with various embodiments.

[0029] Fig. 9 is a call flow diagram illustrating a method that may be performed by a processor of a server and a processor of an endpoint computing device to receive DASH content over WebRTC in accordance with various embodiments.

[0030] Fig.10 is a component block diagram of a network computing device suitable for use with various embodiments.

[0031] Fig.11 is a component block diagram of a computing device suitable for use with various embodiments.

[0032] Detailed Description

[0033] Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts. References to specific examples and embodiments are for illustrative purposes and are not intended to limit the scope of the claims.

[0034] Various embodiments include systems and methods for delivering Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content via Web Real-Time Communication (WebRTC). Various aspects may enable mapping of DASH content onto WebRTC transport sessions. DASH may support large-scale content distribution, such as content distributed by a content delivery network (CDN), and WebRTC may support media streaming at near real-time latency. Mapping DASH content onto WebRTC transport sessions according to various embodiments may reduce (such as minimize) end-to-end latency when distributing DASH content, such as live and real-time content. Various embodiments may further enable reuse of encryption contexts, thereby reducing processing overhead when delivering DASH content.

[0035] The terms "wireless device," "user equipment," and "UE" are used herein to refer to any or all of the following: endpoints or user devices, including wireless devices, wireless router devices, wireless appliances, cellular phones, smart phones, portable computing devices, personal or mobile multimedia players, laptop computers, tablet computers, smartbooks, ultrabooks, handheld computers, wireless email receivers, Internet-enabled multimedia cellular phones, medical devices and equipment, biosensors / devices, wearable devices (including smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings and smart bracelets)), entertainment devices (e.g., wireless game controllers, music and video players, satellite radios, etc.), wireless network-enabled Internet of Things (IoT) devices (including smart meters / sensors, industrial manufacturing equipment, large and small machines and appliances for home or business use), wireless communication elements within autonomous and semi-autonomous vehicles, UEs attached to or incorporated into various mobile platforms, global positioning system devices, and similar electronic devices that include memory, wireless communication components, and programmable processors.

[0036] The term "radio resources" is used herein to refer to hardware, such as modems, radios, processors, transceivers, transmitters, receivers, timers, voltage regulators, oscillators, amplifiers, filters, antennas, circuits, encoders, decoders, etc., and / or software that operate individually or in any combination to send and / or receive electromagnetic radiation to provide wireless communication services (such as cellular and mobile communication services).

[0037] The term "system on chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip that includes multiple resources and / or processors integrated on a single substrate. A single SOC may include circuit systems for digital, analog, mixed signal, and radio frequency functions. A single SOC may also include any number of general and / or special processors (digital signal processors, modem processors, video processors, etc.), memory blocks (e.g., ROM, RAM, flash memory, etc.), and resources (e.g., timers, voltage regulators, oscillators, etc.). Each SOC may also include software for controlling the integrated resources and processors, and for controlling peripheral devices.

[0038] The term "system-in-package" (SIP) may be used herein to refer to a single module or package that includes multiple resources, computing units, cores and / or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unified substrate. A SIP may also include multiple independent SOCs that are coupled together via high-speed communication circuitry and packaged together in close proximity (such as on a single motherboard or in a single wireless device). The proximity of the SOCs facilitates high-speed communication and sharing of memory and resources.

[0039] Various embodiments are described herein using the term "server" to refer to any computing device capable of being used as a server (such as a primary exchange server, a web server, a mail server, a document server, a content server, or any other type of server). A server can be a dedicated computing device or a computing device that includes a server module (e.g., running an application that enables the computing device to operate as a server). A server module (e.g., a server application) can be a full-featured server module, or a light server module or sub-server module (e.g., a light server application or sub-server application) configured to provide synchronization services between dynamic databases on a receiver device. A light server or sub-server can be a streamlined version of server-type functionality that can be implemented on a receiver device so that the receiver device can be used as an Internet server (e.g., a corporate email server) only to the extent necessary to provide the functionality described herein.

[0040] As used herein, the terms "network", "system", "wireless network", "cellular network" and "wireless communication network" may interchangeably refer to a portion or all of an operator's wireless network associated with a wireless device and / or a subscription on a wireless device. The techniques described herein may be used in various wireless communication networks, such as code division multiple access (CDMA), time division multiple access (TDMA), FDMA, orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), and other networks. In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support at least one radio access technology that may operate on one or more frequencies or frequency ranges. For example, a CDMA network may implement Universal Terrestrial Radio Access (UTRA) (including Wideband Code Division Multiple Access (WCDMA) standards), CDMA2000 (including IS-2000, IS-95 and / or IS-856 standards), and the like. In another example, a TDMA network may implement GSM Enhanced Data Rates for GSM Evolution (EDGE). In another example, an OFDMA network may implement Evolved DURA (E-DURA) (including LTE standards), IEEE 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20, Etc. References may be made to wireless networks using the LTE standard, and thus the terms "Evolved Universal Terrestrial Radio Access," "E-UTRAN," and "eNodeB" may also be used interchangeably herein to refer to wireless networks. However, such references are provided merely as examples and are not intended to exclude wireless networks using other communication standards.

[0041] LTE is a mobile network standard for 4G wireless communications for high-speed data developed by 3GPP (3rd Generation Partnership Project) and specified in its Release 8 document series. In contrast to the circuit switching (CS) model of cellular network standards, LTE has been designed to support only packet switching (PS) services. Data services in LTE can be provided over the Internet, while multimedia services can be supported by the Internet Multimedia Subsystem (IMS) framework. The LTE standard is based on the evolution of the Universal Mobile Telecommunications System (UMTS) radio access to the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN together with the Evolved Packet Core (EPC) network (LTE-friendly core network) constitutes the Evolved Packet System (EPS). The access network in UMTS simulates circuit switching connections for real-time services and packet switching connections for data communication services, while the Evolved Packet System (EPS) is purely based on the Internet Protocol (IP), and both real-time services and data communication services are carried by the IP protocol.

[0042] The 5G system is an advanced technology developed from 4G LTE and provides a new radio access technology (RAT) through the evolution of the existing mobile communication network structure. The 5G system can support, for example, extended LTE (eLTE) and non-3GPP access (eg, WLAN).

[0043] One implementation option for using advanced networks such as 5G New Radio (NR) (5GNR) networks, future generations of system networks (e.g., sixth generation (6G) or higher generation networks), etc. is a 5G SA network, in which a 5G radio access network (RAN) and a 5G core network provide 5G services in a geographic area such as a country. In this way, the 5G SA network may overlap with LTE network coverage in a geographic area such as a country. The 5G SA network may exclusively include NR base stations such as next generation Node Bs (gNodeBs or gNBs).

[0044] Another implementation option currently employing an advanced system or network (e.g., a 5G system or network, a 6G system or network, a higher generation system or network, etc.) is a 5G NSA network, in which a RAN (e.g., a RAN including both LTE base stations (such as LTE evolved Node B (eNodeB or eNB)) and NR base stations (such as next generation Node B (gNodeB or gNB)) that provides both LTE (also known as 4G) and New Radio (NR) (also known as 5G) support is connected to an LTE core network (e.g., an evolved packet core (EPC) network). A wireless device (sometimes referred to as user equipment (UE)) in such a 5G NSA network that can support both LTE and NR communications can signal the 5G NSA to notify the UE that it supports dual connectivity with New Radio (DCNR).

[0045] Web Real-Time Communication (WebRTC) is a protocol that supports real-time peer-to-peer communication between devices. WebRTC uses the Real-Time Transport Protocol (RTP) to transmit media. WebRTC enables the establishment of WebRTC sessions between computing devices (such as between endpoint wireless devices and servers (e.g., servers of CDN networks, game servers, conference servers, etc.)), where multiple streams can be supported for data transmission between devices in WebRTC sessions (such as multiple RTP streams multiplexed through a single IP address and port). In WebRTC, the session establishment protocol may not be defined, although several implementations rely on the Session Initiation Protocol (SIP) session establishment and Session Description Protocol (SDP) signaling to establish WebRTC sessions between devices.

[0046] Hypertext Transfer Protocol (HTTP) streaming is a popular method of delivering content over the Internet. Content is gradually available in segments. Segment availability follows a timeline indicating when each coherent segment becomes available on an HTTP server. Content can be streamed according to a streaming format such as Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) or HTTP Live Streaming (HLS). Streaming formats generally consider two types of main formats, a manifest that provides instructions about where and when to access the segments, and a segment format that contains the actual media content in a downloadable and timed manner. While the following focuses on DASH and the term Media Presentation Description (MPD) is used for the manifest, the same concept may apply to other streaming formats including manifests and segment formats. As an example, another manifest format may include Common Media Application Format (CMAF).

[0047] DASH is a standard for implementing HTTP streaming. DASH announces segment availability in a manifest file called a Media Presentation Description (MPD). MPD is a segment availability timeline that announces the location of the segment (usually a Uniform Resource Locator (URL) to an HTTP server), the time when the segment is available, and possibly the size of the segment. A DASH client running on a processor of a computing device (such as a DASH client that provides content to an adaptive bit rate (ABR) player) uses MPD to request and receive segments of a service (such as segments of a media streaming service provided by a CDN server) from a server. The segments of a service described by an MPD may be referred to as a presentation, and as such, the term presentation may generally refer to DASH content to be and / or actually supplied to an endpoint computing device.

[0048] Although WebRTC can support peer-to-peer communications, WebRTC currently does not support large-scale content distribution, such as large-scale distribution of DASH content delivery to endpoint computing devices in various types of content distribution services, such as broadcast services, cloud-based game streaming services, online game spectator mode services, in-venue interactive services, etc. Specifically, WebRTC currently does not define how to set up and provide rate adaptation based on adaptive bitrate encoding of DASH sessions over WebRTC.

[0049] Various embodiments may include systems and methods for delivering DASH content via WebRTC. Various embodiments may enable mapping of DASH content onto a WebRTC transport session. In various embodiments, DASH content may be mapped onto a WebRTC transport session to support large-scale content distribution, such as large-scale distribution of DASH content delivery to endpoint computing devices in various types of content distribution services (such as broadcast services, cloud-based game streaming services, online game spectator mode services, in-venue interactive services, etc.). In various embodiments, signaling from a server providing content to an endpoint computing device is provided and established via WebRTC, for example, a DASH session including rate adaptation based on adaptive bitrate encoding may be provided and established via WebRTC using a WebRTC session between a server providing DASH content and an endpoint computing device (e.g., a wireless device).

[0050] In various embodiments, a server providing DASH content (such as a CDN edge node server) may signal an endpoint computing device that the server is capable of serving DASH content using WebRTC. In various embodiments, a server providing DASH content (such as a CDN edge node server) may receive a request for a manifest of DASH content (e.g., a request for an MPD) from an endpoint computing device. A server providing DASH content (such as a CDN edge node server) may obtain the requested manifest file (e.g., the requested MPD). The requested manifest file (e.g., the requested MPD) may be obtained from a memory available to the server or downloaded from another computing device (such as an origin server providing DASH content to the CDN).

[0051] In various embodiments, a server providing DASH content (such as a CDN edge node server) may signal to a requester endpoint computing device that WebRTC can be used to deliver DASH content, and that the server is capable of supplying DASH content described by a requested manifest (e.g., capable of supplying DASH content presented by a requested MPD description). The signal issued to the requester endpoint computing device that WebRTC can be used to deliver DASH content may include an indication that the server has WebRTC capabilities and an indication of a signaling endpoint (e.g., an IP address and a port) to be used in a WebRTC session. As an example, the server may respond to a request for a manifest file with a response including the requested manifest file, an indication that the server has WebRTC capabilities, and an indication of a signaling endpoint (e.g., an IP address and a port). The signal issued to the requester endpoint computing device that WebRTC can be used to deliver DASH content may include an indication that the server has WebRTC capabilities, an indication of a signaling endpoint (e.g., an IP address and a port) to be used in a WebRTC session, and an indication of a signaling protocol (e.g., SDP or other suitable protocol) for establishing a WebRTC session.

[0052] As an example, a server may respond to a request for a manifest file with a response that includes the requested manifest file, an indication that the server is WebRTC-capable, an indication of a signaling endpoint (e.g., an IP address and port), and an indication of a signaling protocol (e.g., SDP or other suitable protocol) for use in establishing a WebRTC session. As an example, a server providing DASH content (such as a CDN edge node server) may respond to an HTTP GET message for an MPD from a requesting endpoint computing device with an HTTP 200 / OK response message that includes the requested MPD, an indication that the server is WebRTC-capable (e.g., an element in the HTTP response indicating "WebRTC available"), an indication of a signaling endpoint (e.g., an element in the HTTP response listing an IP address and port for use in a WebRTC session), and an indication of a signaling protocol (e.g., an element in the HTTP response indicating "SDP") for use in establishing a WebRTC session.

[0053] In various embodiments, an endpoint computing device that receives a signal from a server providing DASH content (such as a CDN edge node server) that WebRTC can be used to deliver DASH content may determine to switch to or use WebRTC to receive DASH content. In various embodiments, an endpoint computing device that selects WebRTC to receive DASH content may parse the received manifest file (e.g., parse the received MPD) to determine the DASH content components of the service that will be consumed. For example, an endpoint computing device that selects WebRTC to receive DASH content may parse the received MPD to determine the content components of the service that will be consumed and the corresponding time periods and adaptation sets (AdaptationSet) of these content components.

[0054] In various embodiments, an endpoint computing device that selects WebRTC to receive DASH content may determine streaming attributes associated with a DASH content component to be consumed by a service. For example, the streaming attributes may include one or more operating points that the endpoint computing device can support for the content component, such as bandwidth (e.g., maximum bandwidth), width / height (e.g., maximum width and / or height), frame rate (e.g., maximum frame rate), etc. For example, the streaming attributes may include codecs and / or file types for use with the content component. As an example, an endpoint computing device that selects WebRTC to receive DASH content may determine the streaming attributes associated with the DASH content component to be consumed for each selected adaptation set of the service based on the maximum attributes (e.g., @max attributes) indicated in the MPD for each corresponding selected adaptation set. In addition, the endpoint computing device may evaluate its own capabilities to determine the maximum operating point (e.g., maximum bandwidth, maximum width, maximum height, maximum frame rate, etc.) that the endpoint computing device can support for each corresponding selected adaptation set, as well as the codecs (e.g., @codecs) and file types (e.g., @mimeTypes) for each selected adaptation set.

[0055] In various embodiments, an endpoint computing device that selects WebRTC to receive DASH content may send a proposal to establish a WebRTC session to a signaling endpoint (e.g., an IP address and port), such as the signaling endpoint indicated by a server providing the DASH content when providing a manifest file (e.g., an MPD) for the DASH content. The proposal to establish a WebRTC session may be sent using a signaling protocol (e.g., SDP) indicated by the server for use in establishing a WebRTC session. In various embodiments, the proposal to establish a WebRTC session may include an indication of a DASH content component selected by the endpoint computing device to be consumed by the service and streaming attributes associated with the DASH content component determined by the endpoint computing device. For example, the proposal to establish a WebRTC session may include one media line per content component, where the maximum capabilities correspond to the streaming attributes determined by the endpoint computing device. For example, a proposal to establish a WebRTC session may include a media line for each selected adaptation set and a determined maximum operating point (e.g., maximum bandwidth, maximum width, maximum height, maximum frame rate, etc.) that the endpoint computing device can support for each corresponding selected adaptation set, the codecs (e.g., @codecs), and file types (e.g., @mimeTypes) for each selected adaptation set.

[0056] In various embodiments, the media streams for the selected DASH content component may be indicated as receive-only media streams in the proposal to establish a WebRTC session. For example, each media stream in the proposal to establish a WebRTC session may be indicated as "recvonly".

[0057] In various embodiments, a server providing DASH content (such as a CDN edge node server) may receive a proposal to establish a WebRTC session from an endpoint computing device that selects WebRTC to receive DASH content at a signaling endpoint (e.g., an IP address and port), the server being capable of using WebRTC to supply the DASH content described by the requested manifest (e.g., capable of supplying the DASH content presented as described by the requested MPD). In various embodiments, based at least in part on the proposal to establish a WebRTC session, the server providing DASH content (such as a CDN edge node server) may convert segments of the DASH content into an RTP stream of RTP packets and send the RTP stream to the endpoint computing device. In various embodiments, the server providing DASH content (such as a CDN edge node server) may obtain DASH content (e.g., DASH segments) from a cache and / or a DASH content source, convert the DASH content (e.g., DASH segments) into RTP packets, and send the RTP packets to the endpoint computing device. In various embodiments, an RTP stream may be assigned for each content component (e.g., each adaptation set) indicated in a proposal received from the endpoint computing device to establish a WebRTC session. Additionally, in various embodiments, a CMAF track and segment format may be mapped to an RTP stream (such as an RTP hint track). In various embodiments, a manifest file (such as an MPD) may be used to establish Real-time Transport Control Protocol (RTCP) synchronization between media streams of different content versions (such as between media streams of different DASH representations). In various embodiments, a security context may be established for a WebRTC session.

[0058] In various embodiments, once a server providing DASH content (such as a CDN edge node server) establishes a media stream for a WebRTC session—the server is capable of using WebRTC to supply the DASH content described by the requested manifest (e.g., capable of supplying the DASH content presented by the requested MPD description), the server may establish a mapping between the content components of the DASH content selected by the endpoint computing device and the actual media streams used to deliver the DASH content in the WebRTC session. For example, a mapping may be established between the selected presentation of each content component and the actual media streams of the WebRTC session. For example, a tag attribute of the SDP may be associated with an @id or tag of the selected representation to map the content components of the DASH content selected by the endpoint computing device and the actual media streams used to deliver the DASH content in the WebRTC session.

[0059] In various embodiments, a mapping between a content component of the DASH content selected by an endpoint computing device and an actual media stream used to deliver the DASH content in a WebRTC session may be established by generating a mapping object that indicates an assignment of a corresponding content component of the DASH content selected by an endpoint computing device to an actual media stream used to deliver the DASH content in a WebRTC session. As an example, a JavaScript Object Notation (JSON) mapping object may include an indication of an association between a tag attribute of an SDP and an @id or tag of a selected representation to map a content component of the DASH content selected by an endpoint computing device to an actual media stream used to deliver the DASH content in a WebRTC session. Such example JSON mapping objects may be exchanged between a server and an endpoint computing device to establish and / or update a mapping of a content component of the DASH content selected by an endpoint computing device to an actual media stream used in a WebRTC session for the server to deliver the DASH content.

[0060] The mapping (such as a JSON mapping object) may be sent to the endpoint computing device as part of an initial control message to establish a WebRTC session. For example, the mapping (such as a JSON mapping object) may be sent to the endpoint computing device in an accept message confirming the WebRTC session. The accept message confirming the WebRTC session may be a response to the proposal to establish a WebRTC session.

[0061] Various embodiments may enable reuse of encryption contexts. In various embodiments, a server providing DASH content (such as a CDN edge node server) may determine whether a selected representation of the DASH content is content-protected, and the server is capable of supplying the DASH content described by the requested manifest using WebRTC (e.g., capable of supplying DASH content presented by the requested MPD description). In response to determining that the selected representation of the DASH content is content-protected, a server providing DASH content (such as a CDN edge node server) may determine whether an encryption context between a shared encryption and Datagram Transport Layer Security (DTLS) (DTLS-SRTP) of a secure real-time protocol (SRTP) may be reused, and the server is capable of supplying the DASH content described by the requested manifest using WebRTC (e.g., capable of supplying DASH content presented by the requested MPD description). For example, when a data rights management (DRM) server encrypts DASH content before a server providing DASH content (such as a CDN edge node server) obtains the content, the encryption context between the common encryption and DTLS-SRTP can be reused, and the server providing DASH content can use WebRTC to supply the DASH content described by the requested manifest (for example, can supply DASH content presented as described by the requested MPD).

[0062] In response to determining that the encryption context between the common encryption and DTLS-SRTP can be reused, the context reuse can be signaled to the endpoint computing device, and the initialization vector can be reused as an element of encryption for the WebRTC session. The endpoint computing device can obtain a key from an encryption server (such as a DRM server) and use the key to decrypt the SRTP packet payload. A server (such as a CDN edge node server) that provides DASH content can use the encryption context with the common encryption and DTLS-SRTP to send the DASH content in the WebRTC session, because the DASH content was originally obtained without re-encrypting the DASH content (e.g., using the common encryption and DTLS-SRTP to perform the re-encryption), the server can use WebRTC to supply the DASH content described by the requested manifest (e.g., can supply the DASH content of the presentation described by the requested MPD). In this way, packets in the DASH content that have been encrypted (such as encrypted using the common encryption and DTLS-SRTP) may not be re-encrypted by the server before being sent to the endpoint computing device.

[0063] Various embodiments improve the operation and efficiency of communication networks and improve the user experience of some applications and services. Mapping DASH content onto a WebRTC transport session according to various embodiments can reduce or minimize end-to-end latency when distributing DASH content (such as live and real-time content) to an endpoint computing device (e.g., UE). Reducing (such as minimizing) end-to-end latency when distributing DASH content according to various embodiments can be beneficial to various services that utilize DASH content delivery to users of endpoint computing devices, such as broadcast services, cloud-based game streaming services, online game spectator mode services, in-venue interactive services, etc. Various embodiments can further enable reuse of encryption contexts, which can eliminate encryption operations performed by servers (such as CDN edge servers), thereby reducing processing overhead when delivering DASH content to endpoint computing devices. Reducing processing overhead when delivering DASH content according to various embodiments can be beneficial to various services that utilize DASH content delivery to end users, such as broadcast services, cloud-based game streaming services, online game spectator mode services, in-venue interactive services, etc.

[0064] Figure 1A 1 is a system block diagram illustrating an example communication system 100. The communication system 100 may be a 5G New Radio (NR) network, or any other suitable network, such as a Long Term Evolution (LTE) network. Figure 1A A 5G network is illustrated, but later generations of networks may include the same or similar elements. Therefore, references to a 5G network and 5G network elements in the following description are for illustrative purposes and are not intended to be limiting.

[0065] The communication system 100 may include a heterogeneous network architecture including a core network 140 and various UEs (in Figure 1A120a-120e). The communication system 100 may also include various network devices 143, such as various servers of a content delivery network (CDN) 142, etc. The communication system 100 may also include several base stations (illustrated as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station is an entity that communicates with a UE, and may also be referred to as a B node, an LTE evolved B node (eNodeB or eNB), an access point (AP), a radio head, a transmit receive point (TRP), a new radio base station (NR BS), a 5G B node (NB), a next generation B node (gNodeB or gNB), and the like. Each base station may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a base station, a base station subsystem serving the coverage area, or a combination thereof, depending on the context in which the term is used. The core network 140 may be any type of core network, such as an LTE core network (e.g., an evolved packet core (EPC) network), a 5G core network, etc.

[0066] The base stations 110a-110d may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A base station for a macro cell may be referred to as a macro BS. A base station for a pico cell may be referred to as a pico BS. A base station for a femto cell may be referred to as a femto BS or a home BS. In Figure 1A In the example illustrated in , base station 110a may be a macro BS for macro cell 102a, base station 110b may be a pico BS for pico cell 102b, and base station 110c may be a femto BS for femto cell 102c. Base stations 110a-110d may support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “B node,” “5G NB,” and “cell” may be used interchangeably herein.

[0067] In some examples, the cell may not be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile base station. In some examples, the base stations 110a-110d may be interconnected to each other and to one or more other base stations or network nodes (not illustrated) in the communication system 100 via various types of backhaul interfaces (such as direct physical connections, virtual networks, or combinations thereof) using any suitable transport network.

[0068] The base stations 110a-110d may communicate with the core network 140 over a wired or wireless communication link 126. The UEs 120a-120e may communicate with the base stations 110a-110d over a wireless communication link 122.

[0069] The wired communication link 126 may use various wired networks (such as Ethernet, TV cable, telephone, fiber optic, and other forms of physical network connections) that may use one or more wired communication protocols, such as Ethernet, Point-to-Point Protocol, High-Level Data Link Control (HDLC), Advanced Data Communications Control Protocol (ADCCP), and Transmission Control Protocol / Internet Protocol (TCP / IP).

[0070] The communication system 100 may also include a relay station (such as relay BS 110d). A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station or UE) and send transmissions of the data to a downstream station (e.g., a UE or base station). A relay station may also be a wireless device (e.g., a UE) that can relay transmissions for other UEs. Figure 1A In the example illustrated in , a relay station 110d may communicate with a macro base station 110a and a UE 120d to facilitate communication between the base station 110a and the UE 120d. A relay station may also be referred to as a relay base station, a relay base station, a relay, or the like.

[0071] The communication system 100 may be a heterogeneous network including different types of base stations (e.g., macro base stations, pico base stations, femto base stations, relay base stations, etc.). These different types of base stations may have different transmit power levels, different coverage areas, and different impacts on interference in the communication system 100. For example, a macro base station may have a high transmit power level (e.g., 5 to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0072] A network controller 130 may be coupled to a set of base stations and may provide coordination and control for these base stations. The network controller 130 may communicate with the base stations via a backhaul. The base stations may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0073] UEs 120a, 120b, 120c may be dispersed throughout the communication system 100, and each UE may be stationary or mobile.UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, wireless device, etc.

[0074] The macro base station 110a may communicate with the communication network 140 over a wired or wireless communication link 126. The UEs 120a, 120b, 120c may communicate over a wireless communication link 122 with the base stations 110a-110d.

[0075] The wireless communication links 122 and 124 may include multiple carrier signals, frequencies, or frequency bands, each of which may include multiple logical channels. The wireless communication links 122 and 124 may utilize one or more radio access technologies (RATs). Examples of RATs that may be used in the wireless communication links include: 3GPP LTE, 3G, 4G, 5G (such as NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Time Division Multiple Access (TDMA), and other mobile phone communication technology cellular RATs. Other examples of RATs that may be used in one or more of the various wireless communication links within the communication system 100 include medium-range protocols (such as Wi-Fi, LTE-U, LTE-Direct, LAA, MuLTEfire) and relatively short-range RATs (such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE)).

[0076] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (referred to as a "resource block") can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may be further divided into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0077] Although the description of some implementations may use terms and examples associated with LTE technology, some implementations may be applicable to other wireless communication systems (such as new radio (NR) or 5G networks). NR may utilize OFDM with a cyclic prefix (CP) on the uplink (UL) and downlink (DL), and include support for half-duplex operation using time division duplex (TDD). A single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span 12 subcarriers with a subcarrier bandwidth of 75 kHz over a duration of 0.1 milliseconds (ms). Each radio frame may include 50 subframes with a length of 10 ms. Therefore, each subframe may have a length of 0.2 ms. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission, and the link direction of each subframe may be dynamically switched. Each subframe may include DL / UL data and DL / UL control data. Beamforming may be supported and the beam direction may be dynamically configured. Multiple-input multiple-output (MIMO) transmission with precoding may also be supported. MIMO configuration in DL can support up to 8 transmit antennas (with multi-layer DL transmission of up to 8 streams) and up to 2 streams per UE. Multi-layer transmission of up to 2 streams per UE can be supported.

[0078] Up to 8 serving cells may be used to support aggregation of multiple cells. Alternatively, NR may support different air interfaces other than OFDM-based air interfaces.

[0079] Some UEs may be considered as machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (e.g., a remote device), or some other entity. The wireless computing platform may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband Internet of Things) devices. UE 120a-120e may be included inside a housing that houses components of UE 120a-120e, such as processor components, memory components, similar components, or a combination thereof.

[0080] In general, any number of communication systems and any number of wireless networks may be deployed in a given geographic area. Each communication system and wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between communication systems of different RATs. In some cases, 4G / LTE and / or 5G / NR RAT networks may be deployed. For example, a 5G non-self-sustaining (NSA) network may use 4G / LTE RAT on the 4G / LTE RAN side of a 5G NSA network, and simultaneously use 5G / NR RAT on the 5G / NR RAN side of a 5G NSA network. Both 4G / LTE RAN and 5G / NR RAN may be connected to each other and to a 4G / LTE core network (e.g., an evolved packet core (EPC) network) in a 5G NSA network. Other example network configurations may include a 5G self-sustaining (SA) network, in which 5G / NRRAN is connected to a 5G core network in a 5G SA network.

[0081] In some implementations, two or more UEs (e.g., illustrated as UE 120a and UE 120e) may communicate directly (e.g., without using base stations 110a-d as an intermediary to communicate with each other) using one or more sidelink channels. For example, UEs 120a-120e may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or similar protocols), mesh networks, or similar networks, or a combination thereof. In this case, UEs 120a-120e may perform scheduling operations, resource selection operations, and other operations described elsewhere herein as being performed by base stations 110a-110d.

[0082] In some implementations, the CDN 142 may provide content (such as DASH content) to one or more of the UEs 120a-120e. The content (such as DASH content) may be delivered to the UEs 120a-120e from one or more servers 143 of the CDN 142 via the core network 140 and the connections 122, 126. The one or more servers 143 of the CDN 142 may be node servers. A server 143 in the CDN 142 may be referred to as an origin server, which originates content (such as DASH content) and provides it to other servers 143 of the CDN 142. The content (such as DASH content) may be delivered using various protocols (such as HTTP (e.g., HTTP / 1.1, etc.), WebRTC, etc.). The server 143 in the CDN 142 that provides content (such as DASH content) to the core network 140 may be referred to as an edge node server of the CDN 142. The UEs 120a-120e that receive content (such as DASH content) from the CDN 142 may be endpoint computing devices. As an example, the CDN 142 may support delivery of DASH content to endpoint computing devices (e.g., UEs 120a-120e), thereby provisioning various services for the endpoint computing devices, such as live video services, broadcast services, cloud-based game streaming services, online game spectator mode services, in-venue interactive services, etc.

[0083] Figure 1B is a system block diagram illustrating an example decomposed base station 160 architecture that may be part of a V2X and / or 5G network suitable for communicating V2X messages and misbehavior condition information. Figure 1A and 1B , the decomposed base station 160 architecture may include one or more central units (CU) 162, which may communicate directly with the core network 180 via a backhaul link, or indirectly with the core network 180 through one or more decomposed base station units (such as a near real-time (Near-RT) RAN intelligent controller (RIC) 164 via an E2 link, or a non-real-time (Non-RT) RIC 168 associated with a service management and orchestration (SMO) framework 166, or both). The CU 162 may communicate with one or more distributed units (DU) 170 via corresponding mid-haul links (such as an F1 interface). The DU 170 may communicate with one or more radio units (RU) 172 via corresponding forward links. The RU 172 may communicate with a corresponding UE 120 via one or more radio frequency (RF) access links. In some implementations, a UE may be served by multiple RUs 172 simultaneously.

[0084] Each of these units (i.e., CU 162, DU 170, RU 172), as well as near-RT RIC 164, non-RT RIC 168, and SMO framework 166 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or transmit signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or transmit signals, or both, to one or more of the other units on a wireless transmission medium.

[0085] In some aspects, CU 162 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 162. CU 162 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 162 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 162 may be implemented to communicate with DU 170 for network control and signaling.

[0086] DU 170 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RU 172. In some aspects, DU 170 may host one or more of a radio link control (RLC) layer, a media access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional partition, such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 170 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 170 or with control functions hosted by CU 162.

[0087] The lower layer functionality may be implemented by one or more RUs 172. In some deployments, the RUs 172 controlled by the DUs 170 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional partitioning (such as functional partitioning of the lower layers). In such an architecture, the RUs 172 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RUs 172 may be controlled by the corresponding DUs 170. In some scenarios, this configuration may enable the DUs 170 and CUs 162 to be implemented in a cloud-based radio access network (RAN) architecture (such as a vRAN architecture).

[0088] The SMO framework 166 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 166 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 166 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 176) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 162, DU 170, RU 172, and near-RT RIC 164. In some implementations, the SMO framework 166 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 174) via the O1 interface. Additionally, in some implementations, the SMO framework 166 may communicate directly with one or more RUs 172 via the O1 interface. The SMO framework 166 may also include a non-RT RIC 168 configured to support the functionality of the SMO framework 166 .

[0089] The non-RT RIC 168 may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 164. The non-RT RIC 168 may be coupled to or in communication with the near-RT RIC 164 (such as via an A1 interface). The near-RT RIC 164 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 162, one or more DUs 170, or both, and O-eNBs with the near-RT RIC 164.

[0090] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 164, the non-RT RIC 168 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 164 and may be received from a non-network data source or from a network function at the SMO framework 166 or the non-RT RIC 168. In some examples, the non-RT RIC 168 or the near-RT RIC 164 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 168 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 166 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0091] Figure 2 is a component block diagram illustrating an example computing and wireless modem system 200 suitable for implementing any of the various embodiments. The various embodiments may be implemented on a number of single-processor and multi-processor computer systems, including systems on a chip (SOC) or systems in packages (SIP).

[0092] Reference Figure 1A-2, the illustrated example computing system 200 (which may be a SIP in some embodiments) includes two SOCs 202, 204 coupled to a clock 206, a voltage regulator 208, and a wireless transceiver 266, which is configured to send and receive wireless communications to / from a UE (such as a base station 110a) via an antenna (not shown). In some implementations, the first SOC 202 may operate as a central processing unit (CPU) of the UE, which executes the instructions of the software application by performing arithmetic, logic, control, and input / output (I / O) operations specified by the instructions of the software application. In some implementations, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a dedicated 5G processing unit responsible for managing high-capacity, high-speed (such as 5Gbps, etc.), or ultra-high-frequency short-wavelength (such as 28GHz mmWave spectrum, etc.) communications.

[0093] The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an application processor 216, one or more coprocessors 218 (such as a vector coprocessor) connected to one or more of these processors, memory 220, custom circuitry 222, system components and resources 224, an interconnect / bus module 226, one or more temperature sensors 230, a thermal management unit 232, and a thermal power envelope (TPE) component 234. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect / bus module 264, a plurality of millimeter wave transceivers 256, a memory 258, and various additional processors 260 (such as an application processor, a packet processor, etc.).

[0094] Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor / core may perform operations independently of other processors / cores. For example, the first SOC 202 may include a processor that executes a first type of operating system (such as FreeBSD, LINUX, OS X, etc.) and a processor that executes a second type of operating system (such as MICROSOFT WINDOWS10). In addition, any or all of the processors 210, 212, 214, 216, 218, 252, 260 may be included as part of a processor cluster architecture (such as a synchronous processor cluster architecture, an asynchronous or heterogeneous processor cluster architecture, etc.).

[0095] The first and second SOCs 202, 204 may include various system components, resources, and custom circuit systems for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other dedicated operations (such as decoding data packets and processing encoded audio and video signals for display in a web browser). For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components used to support processors and software clients running on UEs. The system components and resources 224 or custom circuit systems 222 may also include circuit systems for docking with peripheral devices (such as cameras, electronic displays, wireless communication devices, external memory chips, etc.).

[0096] The first and second SOCs 202, 204 may communicate via an interconnect / bus module 250. The various processors 210, 212, 214, 216, 218 may be interconnected to one or more memory elements 220, system components and resources 224, and custom circuitry 222, and a thermal management unit 232 via an interconnect / bus module 226. Similarly, the processor 252 may be interconnected to a power management unit 254, a millimeter wave transceiver 256, a memory 258, and various additional processors 260 via an interconnect / bus module 264. The interconnect / bus modules 226, 250, 264 may include an array of reconfigurable logic gates or implement a bus architecture such as CoreConnect, AMBA, etc. Communications may be provided by an advanced interconnect such as a high-performance network on chip (NoC).

[0097] The first or second SOC 202, 204 may further include an input / output module (not illustrated) for communicating with resources external to the SOC, such as clock 206 and voltage regulator 208. Resources external to the SOC, such as clock 206, voltage regulator 208, may be shared by two or more internal SOC processors / cores.

[0098] In addition to the example SIP 200 discussed above, some implementations may be implemented in a variety of computing systems that may include a single processor, multiple processors, multi-core processors, or any combination thereof.

[0099] Figure 3 3 is a component block diagram illustrating a software architecture 300 including a radio protocol stack for a user plane and a control plane in wireless communications suitable for implementing any of the various embodiments. Figure 1A-3, UE 320 may implement software architecture 300 to facilitate communication between UE 320 (e.g., UE 120a-120e, 200) and network device 350 (e.g., network device 142a) of a communication system (e.g., 100). In various embodiments, the layers in software architecture 300 may form logical connections with corresponding layers in software of network device 350. Software architecture 300 may be distributed between one or more processors (e.g., processors 212, 214, 216, 218, 252, 260). Although explained with respect to one radio protocol stack, in a multi-SIM (subscriber identity module) UE, software architecture 300 may include multiple protocol stacks, each of which may be associated with a different subscriber identity module (SIM) (e.g., in a dual SIM wireless communication device, two protocol stacks are associated with two SIMs, respectively). Although described below with reference to LTE communication layers, software architecture 300 may support any of a variety of standards and protocols for wireless communication, and / or may include additional protocol stacks that support any of a variety of standards and protocols for wireless communication.

[0100] Software architecture 300 may include a non-access stratum (NAS) 302 and an access stratum (AS) 304. NAS 302 may include functions and protocols to support packet filtering, security management, mobility control, session management, and traffic and signaling between a UE's SIM(s) (such as SIM(s) 204) and its core network 140. AS 304 may include functions and protocols to support communications between a SIM (such as SIM(s) 204) and entities (such as base stations) of a supported access network. Specifically, AS 304 may include at least three layers (Layer 1, Layer 2, and Layer 3), each of which may include various sublayers.

[0101] In the user plane and control plane, layer 1 (L1) of AS 304 may be a physical layer (PHY) 306, which may oversee functions for transmission or reception over an air interface via a wireless transceiver (e.g., 266). Examples of such physical layer 306 functions may include cyclic redundancy check (CRC) attachment, decoding blocks, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. The physical layer may include various logical channels, including a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH).

[0102] In the user plane and the control plane, Layer 2 (L2) of AS 304 may be responsible for the link between UE 320 and network device 350 on physical layer 306. In some implementations, Layer 2 may include a medium access control (MAC) sublayer 308, a radio link control (RLC) sublayer 310, and a packet data convergence protocol (PDCP) 312 sublayer, and a service data adaptation protocol (SDAP) 317 sublayer, each of which forms a logical connection terminated at network device 350.

[0103] In the control plane, layer 3 (L3) of AS 304 may include a radio resource control (RRC) sublayer 3. Although not shown, software architecture 300 may include additional layer 3 sublayers, as well as various upper layers above layer 3. In some implementations, RRC sublayer 313 may provide functionality including broadcasting system information, paging, and establishing and releasing RRC signaling connections between UE 320 and network device 350.

[0104] In various embodiments, the SDAP sublayer 317 may provide mapping between quality of service (QoS) flows and data radio bearers (DRBs). In some implementations, the PDCP sublayer 312 may provide uplink functions including multiplexing between different radio bearers and logical channels, sequence number addition, handover data handling, integrity protection, ciphering, and header compression. In the downlink, the PDCP sublayer 312 may provide functions including in-sequence delivery of data packets, duplicate data packet detection, integrity verification, cipher decryption, and header decompression.

[0105] In the uplink, the RLC sublayer 310 may provide segmentation and concatenation of upper layer data packets, retransmission of lost data packets, and automatic repeat request (ARQ). In the downlink, the RLC sublayer 310 functions may include reordering of data packets to compensate for out-of-order reception, reassembly of upper layer data packets, and ARQ.

[0106] In the uplink, the MAC sublayer 308 may provide functions including multiplexing between logical and transport channels, random access procedures, logical channel priorities, and hybrid ARQ (HARQ) operations. In the downlink, MAC layer functions may include channel mapping within a cell, demultiplexing, discontinuous reception (DRX), and HARQ operations.

[0107] While the software architecture 300 may provide functionality for transferring data over a physical medium, the software architecture 300 may further include at least one host layer 314 to provide data transfer services to various applications in the UE 320. In some implementations, the application-specific functionality provided by the at least one host layer 314 may provide an interface between the software architecture and the general processor 206.

[0108] In other implementations, the software architecture 300 may include one or more higher logical layers (such as transport, session, presentation, application, etc.) that provide host layer functionality. For example, in some implementations, the software architecture 300 may include a network layer (such as an Internet Protocol (IP) layer) where the logical connection terminates at a packet data network (PDN) gateway (PGW). In some implementations, the software architecture 300 may include an application layer where the logical connection terminates at another device (such as an end-user device, a server, etc.). In some implementations, the software architecture 300 may further include a hardware interface 316 between the physical layer 306 and communication hardware (such as one or more radio frequency (RF) transceivers) in the AS 304.

[0109] Figure 4 is a system block diagram of an example CDN 400 (eg, CDN 142) according to various embodiments. Figure 1A-4 , CDN 400 can deliver DASH content from origin server 403 through node servers 404a-b and 405a-405c (e.g., server 143). DASH content can be cached at each node server 404a-404b and 405a-405c. Origin server 403 can provide DASH content to intermediate node servers 404a-404b via HTTP communication (such as HTTP / 1.1 communication). Intermediate node servers 404a-404b can provide DASH content to edge node servers 405a-405c via HTTP communication (such as HTTP / 1.1 communication). Edge node servers 405a-405c can be servers that provide point-to-point communication of DASH content from CDN 400 to endpoint computing devices 406 (e.g., UE 120a-120e, 200, 300). The endpoint computing device 406 may also be referred to as a client device, and may include a media client application (such as a DASH client application) running on a processor that can consume DASH content received from the CDN 400. As an example, the CDN 400 may support delivery of DASH content to the endpoint computing device 406, thereby provisioning various services for the endpoint computing device 406, such as live video services, broadcast services, cloud-based game streaming services, online game spectator mode services, in-venue interactive services, etc.

[0110] In various embodiments, the edge node server 405b may support delivery of DASH content to the endpoint computing device 406 using WebRTC. In this way, the edge node server 405b may use WebRTC to deliver DASH content, rather than delivering DASH content to the endpoint computing device 406 via HTTP communication (such as HTTP / 1.1 communication). In some embodiments, the edge node server 405b may indicate support for WebRTC to the endpoint computing device 406. In some embodiments, the endpoint computing device 406 may trigger an update to WebRTC. In some embodiments, the edge node server 405b with WebRTC capabilities may convert segments of DASH content into RTP streams based on the endpoint computing device's selection of WebRTC for DASH content delivery. In addition, in some embodiments, CMAF tracking and segment formats may be mapped to an RTP stream (such as RTP hint tracking). In some embodiments, MPD may be used to establish real-time transport control protocol (RTCP) synchronization between media streams of different content versions (such as establishing synchronization between media streams of different DASH representations). In some embodiments, a security context may be established for a WebRTC session.

[0111] Figure 5 is a process flow diagram illustrating a method 500 that may be performed by a processor of an endpoint computing device to receive DASH content via WebRTC in accordance with various embodiments. Figure 1A-5 , the method 500 may be implemented by one or more processors (eg, 210, 212, 214, 216, 218, 252, 260, 426) of an endpoint computing device (eg, 120a-120e, 200, 300, 406).

[0112] In block 502, the processor may perform operations including sending a request for a manifest file of DASH content to a server. As an example, the request for the manifest file of the DASH content may be an HTTP GET request for an MPD of the DASH content. The means for performing the functions of the operations in block 502 may be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, and / or wireless transceiver 266) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0113] In block 504, the processor may perform operations including receiving a reply to the request from the server, the reply including a manifest file for the DASH content and an indication that WebRTC can be used to deliver the DASH content. In various embodiments, a server providing DASH content (such as a CDN edge node server) may signal to the requesting endpoint computing device that WebRTC can be used to deliver the DASH content, and that the server is capable of supplying the DASH content described by the requested manifest (e.g., capable of supplying the DASH content presented as described by the requested MPD). As an example, a server providing DASH content (such as a CDN edge node server) may respond to an HTTP GET message for an MPD from a requesting endpoint computing device with an HTTP 200 / OK response message, the HTTP 200 / OK response message including the requested MPD and an indication that the server has WebRTC capabilities (e.g., an element in the HTTP response indicating "WebRTC is available"). In some embodiments, the reply may include additional indications, such as an indication of a signaling endpoint (e.g., an IP address and port) to be used in the WebRTC session and / or an indication of a signaling protocol (e.g., SDP or other suitable protocol) to be used to establish the WebRTC session. As an example, a server providing DASH content (such as a CDN edge node server) may respond to an HTTP GET message for an MPD from a requesting endpoint computing device with an HTTP 200 / OK response message that includes the requested MPD, an indication that the server has WebRTC capabilities (e.g., an element in the HTTP response indicating "WebRTC available"), an indication of a signaling endpoint (e.g., an element in the HTTP response listing an IP address and port to be used in the WebRTC session), and an indication of a signaling protocol to be used to establish the WebRTC session (e.g., an element in the HTTP response indicating "SDP"). The means for performing the functions of the operation in block 504 may be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, and / or wireless transceiver 266) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0114] In box 506, the processor may perform operations including determining one or more DASH content components to be consumed of the DASH content based at least in part on parsing the manifest file. In various embodiments, the endpoint computing device may parse the received manifest file (e.g., parse the received MPD) to determine the DASH content components to be consumed for the service. For example, the endpoint computing device may parse the received MPD to determine the content components to be consumed for the service and the corresponding time periods and adaptation sets of these content components. The means for performing the functions of the operations in box 506 can be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, etc.) of the endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0115] In block 508, the processor may perform operations including selecting WebRTC to receive one or more DASH content components of the DASH content based at least in part on an indication that WebRTC may be used to deliver the DASH content. For example, the endpoint computing device may determine to switch to or use WebRTC to receive the DASH content. The means for performing the functions of the operations in block 508 may be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, etc.) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0116] In block 510, the processor may perform operations including sending a proposal to establish a WebRTC session to the server, the proposal including an indication of one or more DASH content components of the DASH content. In various embodiments, an endpoint computing device that selects WebRTC to receive DASH content may send a proposal to establish a WebRTC session to a signaling endpoint (e.g., an IP address and port), such as a signaling endpoint indicated by a server providing DASH content when providing a manifest file (e.g., an MPD) for the DASH content. The proposal to establish a WebRTC session may be sent using a signaling protocol (e.g., SDP) indicated by the server for use in establishing a WebRTC session. The means for performing the functions of the operations in block 510 may be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, and / or a wireless transceiver 266) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0117] In some embodiments, the offer to establish a WebRTC session may additionally include an indication of streaming properties associated with the DASH content component determined by the endpoint computing device. In some embodiments, an endpoint computing device selecting WebRTC to receive DASH content may determine streaming properties associated with a DASH content component of a service to be consumed. For example, the streaming properties may include one or more operating points that the endpoint computing device may support for the content component, such as bandwidth (e.g., maximum bandwidth), width / height (e.g., maximum width and / or height), frame rate (e.g., maximum frame rate), etc. For example, the streaming properties may include a codec and / or file type to be used for the content component.

[0118] As an example, an endpoint computing device that selects WebRTC to receive DASH content may determine streaming attributes associated with the DASH content component of each selected adaptation set to be consumed by the service based on the maximum attributes (e.g., @max attributes) indicated in the MPD for each corresponding selected adaptation set and the capabilities of the endpoint computing device itself to determine the maximum operating point (e.g., maximum bandwidth, maximum width, maximum height, maximum frame rate, etc.) that the endpoint computing device can support for each corresponding selected adaptation set, as well as the codecs (e.g., @codecs) and file types (e.g., @mimeTypes) for each selected adaptation set. For example, an offer to establish a WebRTC session may include one media line per content component, where the maximum capabilities correspond to the streaming attributes determined by the endpoint computing device. For example, an offer to establish a WebRTC session may include one media line per selected adaptation set and the determined maximum operating point (e.g., maximum bandwidth, maximum width, maximum height, maximum frame rate, etc.) that the endpoint computing device can support for each corresponding selected adaptation set, the codecs (e.g., @codecs) and file types (e.g., @mimeTypes) for each selected adaptation set.

[0119] In some embodiments, the media streams for the selected DASH content component may be indicated as receive-only media streams in the proposal to establish a WebRTC session. For example, each media stream in the proposal to establish a WebRTC session may be indicated as "receive-only".

[0120] In block 512, the processor may perform operations including receiving an acceptance message from the server to establish a WebRTC session, wherein the acceptance message includes an object indicating a mapping between each corresponding media stream of the WebRTC session and a DASH component assigned to the corresponding media stream in one or more DASH components of the DASH content. In various embodiments, once the server establishes the media streams of the WebRTC session, the server may establish a mapping between the content components of the DASH content selected by the endpoint computing device and the actual media streams used to deliver the DASH content in the WebRTC session. For example, a mapping may be established between the selected presentation of each content component and the actual media stream of the WebRTC session. For example, a tag attribute of the SDP may be associated with an @id or tag of the selected representation to map the content components of the DASH content selected by the endpoint computing device to the actual media streams used to deliver the DASH content in the WebRTC session. As an example, a JavaScript Object Notation (JSON) mapping object may include an indication of an association between a tag attribute of the SDP and an @id or tag of the selected representation to map the content components of the DASH content selected by the endpoint computing device to the actual media streams used to deliver the DASH content in the WebRTC session. Such example JSON mapping objects may be exchanged between a server and an endpoint computing device to establish and / or update a mapping of content components of DASH content selected by an endpoint computing device to actual media streams used in a WebRTC session for the server to deliver the DASH content. A mapping (such as a JSON mapping object) may be sent to an endpoint computing device as part of an initial control message to establish a WebRTC session. For example, a mapping (such as a JSON mapping object) may be sent to an endpoint computing device in an accept message confirming a WebRTC session. The accept message confirming a WebRTC session may be a response to a proposal to establish a WebRTC session. The means for performing the functions of the operations in block 512 may be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, and / or a wireless transceiver 266) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0121] At block 514, the processor may perform operations including receiving the DASH content from the server via at least one corresponding media stream of the WebRTC session. In various embodiments, a server providing DASH content may obtain DASH content (e.g., DASH segments) from a cache and / or a DASH content source, convert the DASH content (e.g., DASH segments) into RTP packets, and send the RTP packets to the endpoint computing device. In some embodiments, an RTP stream may be assigned for each content component (e.g., each adaptation set) indicated in a proposal to establish a WebRTC session received from the endpoint computing device. Additionally, in some embodiments, a CMAF track and segment format may be mapped to an RTP stream (such as an RTP hint track). In some embodiments, a manifest file (such as an MPD) may be used to establish real-time transport control protocol (RTCP) synchronization between media streams of different content versions (such as establishing synchronization between media streams of different DASH representations). In some embodiments, a security context may be established for a WebRTC session. The means for performing the functions of the operation in block 514 may be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, and / or wireless transceiver 266) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0122] Figure 6 6 is a process flow diagram illustrating a method 600 that may be performed by a processor of a server to deliver DASH content via WebRTC in accordance with various embodiments. Figure 1A-6 , the method 600 may be implemented by one or more processors of a server (eg, 143, 405b, etc.). In various embodiments, the operations of the method 600 may be performed in conjunction with the operations of the method 500.

[0123] In block 602, the processor may perform operations including receiving a request for a manifest file of DASH content from an endpoint computing device (e.g., 120a-120e, 200, 300, 406). As an example, the request for the manifest file of the DASH content may be an HTTP GET request for an MPD of the DASH content. The means for performing the functions of the operations in block 602 may be one or more processors of a server (e.g., 143, 405b, etc.).

[0124] In block 604, the processor may perform operations including obtaining the manifest file or the DASH content. The requested manifest file (e.g., the requested MPD) may be obtained from a memory available to the server or downloaded from another computing device (such as an origin server that provides DASH content to the CDN). The means for performing the functions of the operations in block 604 may be one or more processors of a server (e.g., 143, 405b, etc.).

[0125] In block 606, the processor may perform operations including sending a reply to a request for a manifest file for DASH content from an endpoint computing device, wherein the reply includes a manifest file for the DASH content and an indication that WebRTC can be used to deliver the DASH content. The means for performing the functions of the operations in block 606 may be one or more processors of a server (e.g., 143, 405b, etc.).

[0126] As an example of the operations in block 606, a server providing DASH content (such as a CDN edge node server) may respond to an HTTP GET message for an MPD from a requesting endpoint computing device with an HTTP 200 / OK response message that includes the requested MPD and an indication that the server has WebRTC capabilities (e.g., an element in the HTTP response indicating “WebRTC is available”). As another example, the server may respond to a request for a manifest file with a response that includes the requested manifest file, an indication that the server has WebRTC capabilities, and an indication of a signaling endpoint (e.g., an IP address and port).

[0127] In some embodiments, the signal sent by the server to the requesting endpoint computing device that WebRTC is available for delivery of the DASH content in block 606 may include an indication that the server is WebRTC-capable, an indication of a signaling endpoint (e.g., an IP address and port) to be used in the WebRTC session, and an indication of a signaling protocol (e.g., SDP or other suitable protocol) to be used to establish the WebRTC session. As an example, a server providing DASH content (such as a CDN edge node server) may respond to an HTTP GET message for an MPD from the requesting endpoint computing device with an HTTP 200 / OK response message that includes the requested MPD, an indication that the server is WebRTC-capable (e.g., an element in the HTTP response indicating "WebRTC available"), an indication of a signaling endpoint (e.g., an element in the HTTP response listing an IP address and port to be used in the WebRTC session), and an indication of a signaling protocol (e.g., an element in the HTTP response indicating "SDP") to be used to establish the WebRTC session.

[0128] In block 608, the processor may perform operations including receiving from the endpoint computing device a proposal to establish a WebRTC session, the proposal including an indication of one or more DASH content components of the DASH content. In some embodiments, an endpoint computing device that selects WebRTC to receive DASH content may send a proposal to establish a WebRTC session to a signaling endpoint (e.g., an IP address and port). The proposal to establish a WebRTC session may be sent using a signaling protocol (e.g., SDP) indicated by the server for use in establishing a WebRTC session. In some embodiments, the proposal to establish a WebRTC session may include an indication of a DASH content component selected by the endpoint computing device to be consumed by a service and streaming attributes associated with the DASH content component determined by the endpoint computing device. For example, the proposal to establish a WebRTC session may include one media line per content component, where the maximum capability corresponds to the streaming attributes determined by the endpoint computing device. For example, the proposal to establish a WebRTC session may include a media row for each selected adaptation set and a determined maximum operating point (e.g., maximum bandwidth, maximum width, maximum height, maximum frame rate, etc.) that the endpoint computing device can support for each corresponding selected adaptation set, a codec (e.g., @codecs), and a file type (e.g., @mimeTypes) for each selected adaptation set. In some embodiments, the media streams for the selected DASH content component may be indicated as receive-only media streams in the proposal to establish a WebRTC session. For example, each media stream in the proposal to establish a WebRTC session may be indicated as "receive-only". The means for performing the functions of the operations in block 608 may be one or more processors of a server (e.g., 143, 405b, etc.).

[0129] In block 610, the processor may perform operations including establishing a WebRTC session including a respective media stream for each of the indicated one or more DASH components of the DASH content. In various embodiments, establishing the WebRTC session may include assigning a media stream to each DASH component of the DASH content indicated as selected by the endpoint computing device. The means for performing the functions of the operations in block 610 may be one or more processors of a server (e.g., 143, 405b, etc.).

[0130] In box 612, the processor may perform operations including generating an object indicating a mapping between each corresponding media stream of the WebRTC session and the DASH component assigned to the corresponding media stream in the DASH content. In various embodiments, once the media streams of the WebRTC session are established, the server may establish a mapping between the content components of the DASH content selected by the endpoint computing device and the actual media streams used to deliver the DASH content in the WebRTC session. For example, a mapping may be established between the selected presentation of each content component and the actual media stream of the WebRTC session. For example, a tag attribute of the SDP may be associated with an @id or tag of the selected representation to map the content components of the DASH content selected by the endpoint computing device to the actual media streams used to deliver the DASH content in the WebRTC session. The means for performing the functions of the operations in box 612 may be one or more processors of a server (e.g., 143, 405b, etc.).

[0131] In some embodiments, a mapping between content components of the DASH content selected by the endpoint computing device and actual media streams used to deliver the DASH content in the WebRTC session may be established in block 612 by generating a mapping object that indicates an assignment of corresponding content components of the DASH content selected by the endpoint computing device to actual media streams used to deliver the DASH content in the WebRTC session. As an example, a JavaScript Object Notation (JSON) mapping object may include an indication of an association between a tag attribute of the SDP and an @id or tag of a selected representation to map content components of the DASH content selected by the endpoint computing device to actual media streams used to deliver the DASH content in the WebRTC session. Such example JSON mapping objects may be exchanged between a server and an endpoint computing device to establish and / or update a mapping of content components of the DASH content selected by the endpoint computing device to actual media streams used in the WebRTC session for the server to deliver the DASH content.

[0132] In block 614, the processor may perform operations including sending an accept message to the endpoint computing device to establish the WebRTC session, wherein the accept message includes an object indicating the mapping. The mapping (such as a JSON mapping object) may be sent to the endpoint computing device as part of an initial control message to establish a WebRTC session. For example, the mapping (such as a JSON mapping object) may be sent to the endpoint computing device in an accept message confirming the WebRTC session. The accept message confirming the WebRTC session may be a response to the proposal to establish the WebRTC session. The means for performing the functions of the operations in block 614 may be one or more processors of a server (e.g., 143, 405b, etc.).

[0133] At block 616, the processor may perform operations including delivering the DASH content to the endpoint computing device using at least one corresponding media stream of the WebRTC session. In various embodiments, the server may convert the segments of the DASH content into an RTP stream of RTP packets and send the RTP stream to the endpoint computing device. In some embodiments, the server may obtain DASH content (e.g., DASH segments) from a cache and / or a DASH content source, convert the DASH content (e.g., DASH segments) into RTP packets, and send the RTP packets to the endpoint computing device. In some embodiments, an RTP stream may be assigned to each content component (e.g., each adaptation set) indicated in a proposal to establish a WebRTC session received from the endpoint computing device. In addition, in some embodiments, a CMAF track and a segment format may be mapped to an RTP stream, such as an RTP hint track. In various embodiments, a manifest file (such as an MPD) may be used to establish real-time transport control protocol (RTCP) synchronization between media streams of different content versions (such as establishing synchronization between media streams of different DASH representations). In various embodiments, a security context may be established for a WebRTC session. The means for performing the functions of the operation in block 616 may be one or more processors of a server (eg, 143, 405b, etc.).

[0134] Figure 7 700 is a process flow diagram illustrating a method 700 that may be performed by a processor of a server to deliver DASH content via WebRTC in accordance with various embodiments. Figure 1A-7 , method 700 may be implemented by one or more processors of a server (e.g., 143, 405b, etc.). In various embodiments, the operations of method 700 may be performed in conjunction with the operations of methods 500 and / or 600. As an example, the operations of method 700 may be performed as part of the operations of delivering DASH content to an endpoint computing device in block 616 of method 600.

[0135] In response to sending an acceptance message to establish the WebRTC session in block 614, the processor may perform operations including determining in determination block 702 whether an encryption context between common encryption and DTLS-SRTP may be reused in the WebRTC session. For example, when a data rights management (DRM) server encrypts DASH content before the server retrieves the content, the encryption context between common encryption and DTLS-SRTP may be reused. The means for performing the functions of the operations in block 702 may be one or more processors of a server (e.g., 143, 405b, etc.).

[0136] In response to determining that the encryption context between common encryption and DTLS-SRTP may not be reused in a WebRTC session (ie, determination block 702 = "No"), the processor may perform the operations in block 614 of method 600, as described.

[0137] In response to determining that the encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session (i.e., determination block 702 = "Yes"), the processor may perform operations including sending an indication to the endpoint computing device in block 704 that the encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session. For example, the context reuse may be signaled to the endpoint computing device, and the initialization vector may be reused as an element for encryption on the WebRTC session. The means for performing the functions of the operations in block 704 may be one or more processors of a server (e.g., 143, 405b, etc.).

[0138] In box 706, the processor may perform operations including delivering the DASH content to the endpoint computing device without applying further encryption. For example, the processor may perform operations including delivering the DASH content to the endpoint computing device without applying further encryption context between common encryption and DTLS-SRTP. The server may use an encryption context with common encryption and DTLS-SRTP to send the DASH content in a WebRTC session because the DASH content was originally obtained without re-encrypting the DASH content (e.g., using separate common encryption and DTLS-SRTP). In this way, packets in the DASH content that have been encrypted (such as using common encryption and DTLS-SRTP or other suitable encryption) may not be re-encrypted by the server before being sent to the endpoint computing device. The means for performing the functions of the operations in box 706 can be one or more processors of a server (e.g., 143, 405b, etc.).

[0139] Figure 8 8 is a process flow diagram illustrating a method 800 that may be performed by a processor of an endpoint computing device to receive DASH content via WebRTC in accordance with various embodiments. Figure 1A-5 , method 500 may be implemented by one or more processors (e.g., 210, 212, 214, 216, 218, 252, 260, 426) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406). In various embodiments, the operations of method 800 may be performed in conjunction with the operations of methods 500, 600, and / or 700. As an example, the operations of method 800 may be performed in response to receiving an acceptance message in block 512 of method 500.

[0140] In block 802, the processor may perform operations including receiving an indication from a server that an encryption context between a common encryption and DTLS-SRTP may be reused in a WebRTC session. For example, context reuse may be signaled to the endpoint computing device, and an initialization vector may be reused as an element for encryption on the WebRTC session. The means for performing the functions of the operations in block 802 may be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, and / or wireless transceiver 266) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0141] In block 804, the processor may perform operations including obtaining a key for the DASH content from an encryption server in response to receiving an indication from the server that an encryption context between common encryption and DTLS-SRTP may be reused in a WebRTC session. The endpoint computing device may obtain the key from an encryption server (such as a DRM server) and use the key to decrypt the SRTP packet payload. The means for performing the functions of the operations in block 804 may be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, and / or wireless transceiver 266) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0142] At block 514 , the processor may perform operations for receiving DASH content, as discussed with reference to method 500 .

[0143] In block 806, the processor may perform operations including decrypting the SRTP packet payload of the DASH content received in the WebRTC session using the obtained key. In this way, the packets of the DASH content may be decrypted using the obtained key without having to use a separate key from a server sending the DASH content in the WebRTC session. The means for performing the functions of the operations in block 806 may be one or more processors (such as one or more processors 210, 212, 214, 216, 218, 252, 260, 426, and / or wireless transceiver 266) of an endpoint computing device (e.g., 120a-120e, 200, 300, 406).

[0144] Fig. 9 is an illustration of a method that can be performed by an endpoint computing device 902 (eg, 120a-120e, 200, 300, 406) (in Fig. 9A call flow diagram of a method executed by a processor (labeled as "client") to receive DASH content via WebRTC. Figure 1A-9 , Fig. 9 The call flow shows a CDN edge node server 903 (eg, 143, 405b) delivering DASH content via WebRTC (in Fig. 9 ), endpoint computing device 902, and origin server 904 (eg, 403) (in Fig. 9 Example interactions between (labeled as “source” in ). Fig. 9 The example interactions may be example operations performed according to one or more of methods 500 , 600 , 700 , and / or 800 .

[0145] In communication 1, the endpoint computing device 902 may send an HTTP GET request for the MPD of the DASH content to the CDN edge node server 903. The CDN edge node server 903 may reply with an HTTP response 200 / OK with the MPD in communication 2. The HTTP response 200 / OK may include an indication that the CDN edge node server 903 has WebRTC capabilities and indicates a control endpoint (e.g., an endpoint IP address and port). In communication 3, the endpoint computing device 902 may establish a WebRTC session by sending an SDP offer with a mapping of the DASH content components requested to be streamed from the CDN edge node server 903. In communication 4, the CDN edge node server 903 may send an accept message for the WebRTC session as a response to the endpoint computing device 902. The acceptance may include an object indicating a mapping between each corresponding media stream of the WebRTC session and the DASH component assigned to the corresponding media stream in the DASH content.

[0146] In communication 5, the CDN edge node server 903 may determine a reusable encryption context. In communication 6, the CDN edge node server 903 may signal the endpoint computing device 902 to reuse the encryption context. In communication 7, the endpoint computing device 902 may obtain an encryption key from the origin server (e.g., the DRM server provides the key as part of the DASH content license). In communication 8, the endpoint computing device 902 and the CDN edge node server 903 may establish a DTLS-SRTP encryption context. In communication 9, the CDN edge node server 903 may obtain the DASH segments from the cache or the origin server 904. In communication 10, the CDN edge node server 903 may convert the DASH segments into RTP packets. In communication 11, the CDN edge node server 903 may send the RTP packets to the endpoint computing device 902.

[0147] Fig.10 is a component block diagram of a network computing device 1000 (such as a server) suitable for use in various embodiments. Figure 1A-10 , various embodiments may be implemented on various network computing devices 1000 (e.g., base stations 110a-e, 350, server 143, CDN edge node servers 405a-405c, CDN node servers 404a-404b, origin servers 403, 904, etc.), examples of which are described in Fig.10 This type of network computing device may include at least Fig.10 . The network computing device 1000 may include: a processor 1001 coupled to a volatile memory 1002 and a large capacity non-volatile memory (such as a disk drive 1008). The network computing device 1000 may also include: a peripheral memory access device (such as a floppy disk drive, a compact disc (CD) or a digital video disc (DVD) drive 1006) coupled to the processor 1001. The network computing device 1000 may also include: a network access port 1004 (or interface) coupled to the processor 1001 for establishing a data connection with a network (such as the Internet and / or a local area network coupled to other system computers and servers). The network computing device 1000 may include: one or more antennas 1007 for sending and receiving electromagnetic radiation, which one or more antennas 1007 may be connected to a wireless communication link. The network computing device 1000 may include: additional access ports for coupling to peripheral devices, external memory or other devices, such as USB, Firewire, Thunderbolt, etc.

[0148] Fig.11 is a component block diagram of a computing device, such as an endpoint computing device, suitable for use with various embodiments. Figure 1A-11 , various embodiments may be implemented on various computing devices (such as endpoint computing devices (e.g., UE 120a-120e, wireless devices 200, 320, endpoint computing devices 406, 902, etc.)), examples of which are described in Fig.111100 is used for illustration. The wireless device 1100 may include: a first SOC 202 (e.g., SOC-CPU), which is coupled to a second SOC 204 (e.g., a SOC with 5G capabilities). The first and second SOCs 202, 204 may be coupled to an internal memory 1116, a display 1112, and a speaker 1114. In addition, the wireless device 1100 may include: an antenna 1104 for sending and receiving electromagnetic radiation, which may be connected to a wireless transceiver 266, which is coupled to one or more processors in the first and / or second SOCs 202, 204. The wireless device 1100 may also include: a menu selection button or rocker switch 1120 for receiving user input.

[0149] The wireless device 1100 also includes a sound coding / decoding (CODEC) circuit 1110 that digitizes the sound received from the microphone into a data packet suitable for wireless transmission and decodes the received sound data packet to generate an analog signal provided to the speaker to produce sound. In addition, one or more of the processors in the first and second SOCs 202, 204, the wireless transceiver 266, and the CODEC 1110 may include a digital signal processor (DSP) circuit (not shown separately).

[0150] The processors of the network computing device 1000 and the wireless device 1100 may be any programmable microprocessor, microcomputer, or one or more multi-processor chips that can be configured by software instructions (applications) to perform various functions including the functions of the various embodiments described below. In some mobile devices, multiple processors may be provided (such as one processor dedicated to wireless communication functions within the SOC 204 and one processor dedicated to running other applications within the SOC 202). Software applications may be stored in memory and then accessed and loaded into the processor. The processor may include internal memory sufficient to store application software instructions.

[0151] As used in this application, the terms "component", "module", "system" and similar terms are intended to include computer-related entities, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution that is configured to perform a specific operation or function. For example, a component can be, but is not limited to, a process, a processor, an object, an executable, a thread of execution, a program, and / or a computer running on a processor. As an illustration, both an application running on a wireless device and a wireless device can be referred to as a component. One or more components may reside within a process and / or a thread of execution, and a component may be localized on a processor or core and / or distributed between two or more processors or cores. In addition, these components may be executed from various non-transient computer-readable media having various instructions and / or data structures stored thereon. Each component may communicate via local and / or remote processes, function or procedure calls, electronic signals, data packets, memory read / writes, and other known networks, computers, processors, and / or communication methodologies associated with processes.

[0152] Several different cellular and mobile communication services and standards are available and are contemplated in the future, all of which can be implemented and benefit from various embodiments. Such services and standards include, for example, the Third Generation Partnership Project (3GPP), LTE systems, third generation wireless mobile communication technology (3G), fourth generation wireless mobile communication technology (4G), fifth generation wireless mobile communication technology (5G) and subsequent 3GPP technologies, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) systems (e.g., cdmaOne, CDMA1020TM), Enhanced Data Rates for GSM Evolution (EDGE), Advanced Mobile Phone System (AMPS), Digital AMPS (IS-136 / TDMA), Evolution Data Optimized (EV-DO), Digital Enhanced Cordless Telecommunications (DECT), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Local Area Network (WLAN), Wi-Fi Protected Access I and II (WPA, WPA2), and Integrated Digital Enhanced Network (iDEN). Each of these technologies involves, for example, the transmission and reception of voice, data, signaling and / or content messages. It should be understood that any reference to terminology and / or technical details related to individual telecommunication standards or technologies is for illustrative purposes only and is not intended to limit the scope of the claims to a particular communication system or technology unless specifically stated in the claim language.

[0153] The various embodiments illustrated and described are provided merely as examples of various features of the claims. However, the features shown and described for any given embodiment are not necessarily limited to the associated embodiment, and may be used or combined with other embodiments shown and described. In addition, the claims are not intended to be limited to any one example embodiment. For example, one or more operations of methods 500, 600, 700, and / or 800 may replace or be combined with one or more operations of methods 500, 600, 700, and / or 800.

[0154] Various implementation examples are described in the following paragraphs. Although some of the following implementation examples are described in the form of example methods, further example implementations may include: example methods discussed in the following paragraphs implemented by a computing device, the computing device including a processor configured to perform the operations of these example methods; example methods discussed in the following paragraphs implemented by a computing device, the computing device including means for performing the functions of these example methods; and example methods discussed in the following paragraphs implemented as a non-transitory processor-readable storage medium storing processor-executable instructions, the processor-executable instructions being configured to cause a processor of a computing device to perform the operations of these example methods.

[0155] Example 1. A method executed by a processor of an endpoint computing device to receive Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content via Web Real-Time Communication (WebRTC), comprising: sending a request for a manifest file of DASH content to a server; and receiving a reply to the request from the server, the reply including the manifest file of the DASH content and an indication that WebRTC can be used to deliver the DASH content.

[0156] Example 2. The method of Example 1 further includes: determining one or more DASH content components of the DASH content to be consumed based at least in part on parsing the manifest file; selecting WebRTC to receive one or more DASH content components of the DASH content based at least in part on an indication that WebRTC can be used to deliver the DASH content; and sending a proposal to the server to establish a WebRTC session, the proposal including an indication of one or more DASH content components of the DASH content.

[0157] Example 3. The method of Example 2 further includes: receiving an acceptance message from the server to establish the WebRTC session, wherein the acceptance message includes an object indicating a mapping between each corresponding media stream of the WebRTC session and a DASH component assigned to the corresponding media stream in one or more DASH components of the DASH content.

[0158] Example 4. The method of Example 3, further comprising: receiving the DASH content from the server via at least one corresponding media stream of the WebRTC session.

[0159] Example 5. The method of any of Examples 1-4, wherein the proposal to establish the WebRTC session further comprises an indication of one or more streaming properties.

[0160] Example 6. The method of Example 5, wherein the one or more streaming properties are one or more of bandwidth, width, height, frame rate, codec, and file type.

[0161] Example 7. The method of any of Examples 1-6, wherein the indication that WebRTC can be used to deliver the DASH content includes an indication that the server has WebRTC capabilities and an indication of a signaling endpoint for use in a WebRTC session.

[0162] Example 8. The method of Example 7, wherein: the indication that WebRTC can be used to deliver the DASH content further includes an indication of a signaling protocol for use in establishing the WebRTC session.

[0163] Example 9. The method of any of Examples 1-8, wherein the one or more DASH content components of the DASH content are one or more adaptation sets of the DASH content.

[0164] Example 10. The method of any of Examples 1-9, wherein the manifest file for the DASH content is a media presentation description.

[0165] Example 11. A method as in any of Examples 1-10, further comprising: receiving an indication from the server that an encryption context between a common encryption and a Datagram Transport Layer Security (DTLS) (DTLS-SRTP) of a Secure Real Time Protocol (SRTP) can be reused in the WebRTC session; obtaining a key for the DASH content from an encryption server in response to receiving an indication from the server that the encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session; and using the obtained key to decrypt the SRTP packet payload of the DASH content received in the WebRTC session.

[0166] Example 12. A method executed by a processor of a server to deliver Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content via Web Real-Time Communication (WebRTC), comprising: sending a reply to a request for a manifest file for DASH content from an endpoint computing device, wherein the reply includes the manifest file for the DASH content and an indication that WebRTC can be used to deliver the DASH content.

[0167] Example 13. The method of Example 12, wherein: the indication that WebRTC can be used to deliver the DASH content includes an indication that the server has WebRTC capabilities and an indication of a signaling endpoint for use in a WebRTC session.

[0168] Example 14. The method of Example 13, wherein: the indication that WebRTC can be used to deliver the DASH content further includes an indication of a signaling protocol for use in establishing the WebRTC session.

[0169] Example 15. A method as in any of Examples 12-14, further comprising: receiving a proposal to establish a WebRTC session from the endpoint computing device, the proposal comprising an indication of one or more DASH content components of the DASH content; establishing the WebRTC session, the WebRTC session comprising a corresponding media stream for each of the indicated one or more DASH components of the DASH content; generating an object indicating a mapping between each corresponding media stream of the WebRTC session and the DASH component in the DASH content assigned to the corresponding media stream; and sending an acceptance message to the endpoint computing device to establish the WebRTC session, wherein the acceptance message comprises an object indicating the mapping.

[0170] Example 16. The method of Example 15, further comprising: delivering the DASH content to the endpoint computing device using at least one corresponding media stream of the WebRTC session.

[0171] Example 17. The method of any of Examples 15-16, wherein the proposal from the endpoint computing device to establish the WebRTC session further includes an indication of one or more streaming attributes.

[0172] Example 18. The method of Example 17, wherein: the one or more streaming properties are one or more of bandwidth, width, height, frame rate, codec, and file type.

[0173] Example 19. The method of any of Examples 15-18, wherein the one or more DASH content components of the DASH content are one or more adaptation sets of the DASH content.

[0174] Example 20. The method of any of Examples 12-19, wherein the manifest file for the DASH content is a media presentation description.

[0175] Example 21. A method as in any of Examples 12-20, further comprising: determining whether an encryption context between a common encryption and a Datagram Transport Layer Security (DTLS) (DTLS-SRTP) of a Secure Real Time Protocol (SRTP) can be reused in the WebRTC session; and in response to determining that the encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session: sending an indication to the endpoint computing device that the encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session; and delivering the DASH content to the endpoint computing device without applying further encryption.

[0176] The foregoing method descriptions and process flow diagrams are provided only as illustrative examples and are not intended to require or imply that the operations of the various embodiments must be performed in the order given. As will be appreciated by those skilled in the art, the order of operations in the foregoing embodiments may be performed in any order. Phrases such as "thereafter," "subsequently," and "next" are not intended to limit the order of operations; these phrases are used to guide the reader through the description of the method. Further, any reference to a claim element in the singular form (e.g., a reference using the article "a," "a," or "the") should not be interpreted as limiting the element to the singular.

[0177] The various illustrative logic blocks, modules, components, circuits, and algorithmic operations described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and operations are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in different ways for each specific application, but such embodiment decisions should not be interpreted as causing a departure from the scope of the claims.

[0178] The hardware used to implement the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device designed to perform the functions described herein, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of receiver smart objects, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by a circuit system dedicated to a given function.

[0179] In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions may be stored as one or more instructions or codes on a non-transient computer-readable storage medium or a non-transient processor-readable storage medium. The operation of the method or algorithm disclosed herein may be implemented in a processor-executable software module or a processor-executable instruction, which may reside on a non-transient computer-readable or processor-readable storage medium. A non-transient computer-readable or processor-readable storage medium may be any storage medium that can be accessed by a computer or processor. As an example and not limitation, such non-transient computer-readable or processor-readable storage media may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage, disk storage or other magnetic storage smart objects, or any other medium that can be used to store desired program codes in the form of instructions or data structures and can be accessed by a computer. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disk often reproduces data magnetically and disc reproduces data optically with lasers. Combinations of the above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and / or instructions on a non-transitory processor-readable storage medium and / or computer-readable storage medium that may be incorporated into a computer program product.

[0180] The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present claims. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Thus, the present disclosure is not intended to be limited to the embodiments shown herein, but should be accorded the broadest scope consistent with the appended claims and the principles and novel features disclosed herein.

Claims

1. A method executed by a processor of an endpoint computing device to receive Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content via Web Real-Time Communication (WebRTC), include: Send a request for the manifest file of the DASH content to the server; as well as A reply to the request is received from the server, the reply including the manifest file for the DASH content and an indication that WebRTC may be used to deliver the DASH content.

2. The method of claim 1, further comprising: include: determining one or more DASH content components of the DASH content to be consumed based at least in part on parsing the manifest file; selecting WebRTC to receive the one or more DASH content components of the DASH content based at least in part on the indication that WebRTC can be used to deliver the DASH content; as well as A proposal to establish a WebRTC session is sent to the server, the proposal including an indication of the one or more DASH content components of the DASH content.

3. The method of claim 2, further comprising: include: An accept message is received from the server to establish the WebRTC session, wherein the accept message includes an object indicating a mapping between each corresponding media stream of the WebRTC session and a DASH content component of the one or more DASH content components of the DASH content assigned to the corresponding media stream.

4. The method of claim 3, further comprising: include: The DASH content is received from the server via at least one corresponding media stream of the WebRTC session.

5. The method of claim 2, wherein the proposal to establish the WebRTC session further comprises an indication of one or more streaming attributes.

6. The method of claim 5, wherein the one or more streaming properties include one or more of bandwidth, width, height, frame rate, codec, and file type.

7. The method of claim 1, wherein the indication that WebRTC can be used to deliver the DASH content includes an indication that the server has WebRTC capabilities and an indication of a signaling endpoint for use in a WebRTC session.

8. The method of claim 7, wherein the indication that WebRTC can be used to deliver the DASH content further comprises an indication of a signaling protocol for use in establishing the WebRTC session.

9. The method of claim 2, wherein the one or more DASH content components of the DASH content include one or more adaptation sets of the DASH content.

10. The method of claim 1, wherein the manifest file of the DASH content is a media presentation description.

11. The method of claim 1, further comprising: include: receiving an indication from the server that a cryptographic context between a Datagram Transport Layer Security (DTLS) (DTLS-SRTP) and a Secure Real Time Protocol (SRTP) common cryptographic context can be reused in a WebRTC session; obtaining a key for the DASH content from an encryption server in response to receiving an indication from the server that an encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session; as well as The obtained key is used to decrypt the SRTP packet payload of the DASH content received in the WebRTC session.

12. A method executed by a processor of a server to deliver Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content via Web Real-Time Communication (WebRTC), include: A reply is sent to a request for a manifest file for DASH content from an endpoint computing device, wherein the reply includes the manifest file for the DASH content and an indication that WebRTC may be used to deliver the DASH content.

13. The method of claim 12, wherein the indication that WebRTC can be used to deliver the DASH content includes an indication that the server has WebRTC capabilities and an indication of a signaling endpoint for use in a WebRTC session.

14. The method of claim 13, wherein the indication that WebRTC can be used to deliver the DASH content further comprises an indication of a signaling protocol for use in establishing the WebRTC session.

15. The method of claim 12, further comprising: include: receiving, from the endpoint computing device, a proposal to establish a WebRTC session, the proposal comprising an indication of one or more DASH content components of the DASH content; establishing the WebRTC session, the WebRTC session comprising a respective media stream for each of the indicated one or more DASH content components of the DASH content; generating an object indicating a mapping between each respective media stream of the WebRTC session and an indicated DASH content component of the respective media stream in the DASH content; as well as An accept message is sent to the endpoint computing device to establish the WebRTC session, wherein the accept message includes the object indicating the mapping.

16. The method of claim 15, further comprising: include: The DASH content is delivered to the endpoint computing device using at least one corresponding media stream of the WebRTC session.

17. The method of claim 15, wherein the proposal from the endpoint computing device to establish the WebRTC session further comprises an indication of one or more streaming attributes.

18. The method of claim 17, wherein the one or more streaming properties include one or more of bandwidth, width, height, frame rate, codec, and file type.

19. The method of claim 15, wherein the one or more DASH content components of the DASH content include one or more adaptation sets of the DASH content.

20. The method of claim 12, wherein the manifest file of the DASH content is a media presentation description.

21. The method of claim 12, further comprising: include: Determine whether the cryptographic context between the Datagram Transport Layer Security (DTLS) with the Secure Real Time Protocol (SRTP) (DTLS-SRTP) can be reused in a WebRTC session; as well as In response to determining that the encryption context between the common encryption and DTLS-SRTP can be reused in the WebRTC session: sending an indication to the endpoint computing device that a cryptographic context between the common crypto and DTLS-SRTP can be reused in the WebRTC session; as well as The DASH content is delivered to the endpoint computing device without applying further encryption.

22. An endpoint computing device, include: A processor configured with processor-executable instructions for: Sending a request for a manifest file of Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content to a server; as well as A reply to the request is received from the server, the reply including the manifest file for the DASH content and an indication that Web Real-Time Communications (WebRTC) may be used to deliver the DASH content.

23. The endpoint computing device of claim 22, wherein the processor is further configured with processor-executable instructions to: determining one or more DASH content components of the DASH content to be consumed based at least in part on parsing the manifest file; selecting WebRTC to receive the one or more DASH content components of the DASH content based at least in part on the indication that WebRTC can be used to deliver the DASH content; and A proposal to establish a WebRTC session is sent to the server, the proposal including an indication of the one or more DASH content components of the DASH content.

24. The endpoint computing device of claim 23, wherein the processor is further configured with processor-executable instructions to: An accept message is received from the server to establish the WebRTC session, wherein the accept message includes an object indicating a mapping between each corresponding media stream of the WebRTC session and a DASH content component of the one or more DASH content components of the DASH content assigned to the corresponding media stream.

25. The endpoint computing device of claim 24, wherein the processor is further configured with processor-executable instructions to: The DASH content is received from the server via at least one corresponding media stream of the WebRTC session.

26. A server, include: A processor configured with processor-executable instructions for: A reply is sent to a request for a manifest file of Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) content from an endpoint computing device, wherein the reply includes the manifest file of the DASH content and an indication that Web Real-Time Communication (WebRTC) can be used to deliver the DASH content.

27. The server of claim 26, wherein the processor is further configured with processor-executable instructions such that: the indication that WebRTC can be used to deliver the DASH content includes an indication that the server has WebRTC capabilities and an indication of a signaling endpoint for use in a WebRTC session.

28. The server of claim 27, wherein the processor is further configured with processor-executable instructions such that: the indication that WebRTC can be used to deliver the DASH content further includes an indication of a signaling protocol for use in establishing the WebRTC session.

29. The server of claim 26, wherein the processor is further configured with processor-executable instructions for: receiving, from the endpoint computing device, a proposal to establish a WebRTC session, the proposal comprising an indication of one or more DASH content components of the DASH content; establishing the WebRTC session, the WebRTC session comprising a respective media stream for each of the indicated one or more DASH content components of the DASH content; generating an object indicating a mapping between each corresponding media stream of the WebRTC session and a DASH component in the DASH content assigned to the corresponding media stream; as well as An accept message is sent to the endpoint computing device to establish the WebRTC session, wherein the accept message includes the object indicating the mapping.

30. The server of claim 29, wherein the processor is further configured with processor-executable instructions for: The DASH content is delivered to the endpoint computing device using at least one corresponding media stream of the WebRTC session.

Citation Information

Patent Citations

  • Method and system for adaptive virtual broadcasting of digital content

    CN107223325A

  • WebRTC media gateway based on Docker container technology and an interworking method thereof

    CN109257344A

  • Communication device connection method, communication device connection system, and communication device connection program

    JP2019145916A

  • Method and apparatus for playing media stream on web-browser

    KR1020170114219A

  • Video Conferencing Over IP Networks

    US20180152669A1