A media streaming method, device, and storage medium

Abstract

This application provides a media streaming method, device, and storage medium. The method includes: selecting media content, the media content including a scene; creating an augmented reality (AR) / mixed reality (MR) session for streaming the media content in an outer session loop; rendering the media content in an inner session loop within the outer session loop; and updating the scene with the new scene in the outer session loop by providing the new scene to the inner session loop while the inner session loop is rendering the media content.

Description

[0001] Cross-referencing

[0002] This application claims priority to U.S. Provisional Application No. 63 / 275,358, filed November 3, 2021, with the United States Patent and Trademark Office, the disclosure of which is incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to 5th generation Augmented Reality (AR) / Mixed Reality (MR), and more particularly to a method and apparatus for providing AR / MR content to a 5G device in which the scene is dynamically updated. Background Technology

[0004] The 3rd Generation Partnership Project (3GPP) TS26.501 defines the media streaming architecture for 5G networks. 3GPP initiated a technical report on supporting augmented reality (AR) / mixed reality (MR) applications. 3GPP TR 26.998 defines support for glass-type AR / MR devices in 5G networks. Two device categories are considered: devices fully capable of decoding and playing complex AR / MR content (i.e., standalone AR (STAR)), and devices with smaller computing resources and / or smaller physical size (i.e., smaller batteries). Both device categories can only run such applications if a significant portion of the computation is performed on a 5G edge server, network, or cloud rather than on the device (edge-related AR (EDGAR)). However, call flows for STAR devices cannot update scene descriptions. Summary of the Invention

[0005] According to one aspect of this disclosure, a method may include: selecting media content, the media content including a scene; creating an augmented reality (AR) / mixed reality (MR) session for streaming the media content in an outer session loop; rendering the media content in an inner session loop within the outer session loop; and updating the scene with the new scene in the outer session loop by providing the new scene to the inner session loop while the inner session loop is rendering the media content.

[0006] According to one aspect of this disclosure, an apparatus may include: at least one memory configured to store program code; and at least one processor configured to read the program code and operate according to the instructions of the program code. The program code includes: first selection code configured to cause the at least one processor to select media content, the media content including a scene; first creation code configured to cause the at least one processor to create an AR / MR session for streaming the media content in an external session loop; first rendering code configured to cause the at least one processor to render the media content in an internal session loop within the external session loop; and first update code configured to cause the at least one processor to update the scene with the new scene in the external session loop by providing a new scene to the internal session loop while the internal session loop is rendering the media content.

[0007] According to one aspect of this disclosure, a non-volatile computer-readable medium storable instruction includes: one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to: select media content, the media content including a scene; create an AR / MR session for streaming the media content in an external session loop; render the media content in an internal session loop within the external session loop; and update the scene with the new scene in the external session loop by providing the new scene to the internal session loop while the internal session loop is rendering the media content. Attached Figure Description

[0008] Other features, properties, and various advantages of the disclosed subject matter will become more apparent from the following detailed description and accompanying drawings, wherein:

[0009] Figure 1 A diagram illustrating the environment in which the methods, apparatus, and systems described herein according to embodiments may be implemented.

[0010] Figure 2 for Figure 1 A block diagram of example components of one or more devices.

[0011] Figure 3 This is a diagram of a media architecture for media uplink streaming according to an embodiment.

[0012] Figure 4 This is a diagram of a media architecture for media downlink streaming according to an embodiment.

[0013] Figure 5This is a diagram of the 5th Generation Media Streaming Downlink (5GMSd) download architecture for standalone augmented reality (AR) (STAR) according to an embodiment.

[0014] Figure 6A , Figure 6B and Figure 6C This is a diagram illustrating the operational flow of STAR-based 5G downlink streaming according to an embodiment.

[0015] Figure 7 This is a flowchart of a STAR-based 5G downlink streaming method according to an embodiment. Detailed Implementation

[0016] Figure 1 This is a schematic diagram of an environment 100 in which the methods, apparatus, and systems described herein can be implemented according to an embodiment. Figure 1 As shown, environment 100 may include user equipment 110, platform 120, and network 130. The devices in environment 100 can be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0017] User equipment 110 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information associated with platform 120. For example, user equipment 110 may include computing devices (e.g., desktop computers, laptop computers, tablet computers, handheld computers, smart speakers, servers, etc.), mobile phones (e.g., smartphones, cordless phones, etc.), wearable devices (e.g., a pair of smart glasses or a smartwatch), or similar devices. In some embodiments, user equipment 110 may receive information from and / or send information to platform 120.

[0018] Platform 120 includes one or more devices as described elsewhere herein. In some embodiments, platform 120 may include a cloud server or a group of cloud servers. In some embodiments, platform 120 may be designed to be modular, allowing software components to be swapped in or out as needed. This allows platform 120 to be easily and / or quickly reconfigured for different purposes.

[0019] In some implementations, as shown in the figure, platform 120 may be hosted in a cloud computing environment 122. It is worth noting that while the implementations described herein depict platform 120 as being hosted in a cloud computing environment 122, in some implementations, platform 120 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0020] The cloud computing environment 122 includes the environment of the hosting platform 120. The cloud computing environment 122 can provide services such as computing, software, data access, and storage, without requiring end users (e.g., user equipment 110) to know the physical location and configuration of one or more systems and / or one or more devices used to host the aforementioned platform 120. As shown in the figure, the cloud computing environment 122 may include a set of computing resources 124 (collectively referred to as "computing resources 124" and individually as "computing resources 124").

[0021] Computing resource 124 includes one or more personal computers, workstations, server devices, or other types of computing and / or communication devices. In some embodiments, computing resource 124 may host the aforementioned platform 120. Cloud resources may include computing instances executing in computing resource 124, storage devices provided in computing resource 124, data transmission devices provided by computing resource 124, etc. In some embodiments, computing resource 124 may communicate with other computing resources 124 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0022] like Figure 1 As further shown, computing resources 124 include a set of cloud resources, such as one or more applications (“APP”) 124-1, one or more virtual machines (“VM”) 124-2, virtualized storage (“VS”) 124-3, one or more hypervisors (“HYP”) 124-4, etc.

[0023] Application 124-1 includes one or more software applications that can be provided to or accessed by user equipment 110 and / or platform 120. Application 124-1 can eliminate the need to install and execute software applications on user equipment 110. For example, application 124-1 may include software associated with platform 120 and / or any other software that can be provided through cloud computing environment 122. In some implementations, an application 124-1 may send / receive information to / from one or more other applications 124-1 via virtual machine 124-2.

[0024] Virtual machine 124-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Depending on its use and degree of correspondence with any real machine, virtual machine 124-2 can be a system virtual machine or a process virtual machine. A system virtual machine can provide a complete system platform supporting the execution of a full operating system (“OS”). A process virtual machine can execute a single program and can support a single process. In some implementations, virtual machine 124-2 can execute on behalf of a user (e.g., user device 110) and can manage the infrastructure of cloud computing environment 122, such as data management, synchronous or long-duration data transfers.

[0025] Virtualized storage 124-3 includes one or more storage systems and / or one or more devices that utilize virtualization technology within the storage systems or devices of computing resource 124. In some embodiments, within the context of the storage system, the type of virtualization may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of logical storage from physical storage, enabling access to the storage system without considering physical storage or heterogeneous architecture. This separation allows storage system administrators flexibility in how to manage storage for end users. File virtualization eliminates the dependency between data accessed at the file level and the physical location where files are stored. This can optimize the performance of storage usage, server consolidation, and / or non-destructive file migration.

[0026] Hypervisor 124-4 can provide hardware virtualization technology that allows multiple operating systems (e.g., "guest operating systems") to execute concurrently on a host (such as computing resource 124). Hypervisor 124-4 can present a virtual operating platform to the guest operating system and manage the execution of the guest operating system. Multiple instances of various operating systems can share virtualized hardware resources.

[0027] Network 130 includes one or more wired and / or wireless networks. For example, network 130 may include cellular networks (e.g., fifth-generation (5G), long-term evolution (LTE), third-generation (3G), code division multiple access (CDMA), etc.), public land mobile networks (PLMNs), local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), telephone networks (e.g., public switched telephone networks (PSTNs)), private networks, self-organizing networks, intranets, the Internet, fiber-optic networks, etc., and / or combinations of these or other types of networks.

[0028] Figure 1 The number and arrangement of devices and networks shown are provided as examples. In reality, additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or networks may exist. Figure 1 The devices and / or networks shown are arranged differently. Furthermore, Figure 1 The two or more devices shown can be implemented within a single device, or can be... Figure 1 The single device shown is implemented as multiple distributed devices. Additionally or alternatively, a group of devices in environment 100 (e.g., one or more devices) may perform one or more functions, which are described as being performed by another group of devices in environment 100.

[0029] Figure 2 yes Figure 1 A block diagram of example components of one or more devices. Device 200 may correspond to user device 110 and / or platform 120. Figure 2 As shown, device 200 may include bus 210, processor 220, memory 230, storage unit 240, input unit 250, output unit 260 and communication interface 270.

[0030] Bus 210 includes components that allow communication between parts of device 200. Processor 220 is implemented in hardware, firmware, or a combination of hardware and software. Processor 220 is a central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), microprocessor, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), or another type of processing unit. In some embodiments, processor 220 includes one or more processors that can be programmed to perform functions. Memory 230 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) for storing information and / or instructions for use by processor 220.

[0031] Storage component 240 stores information and / or software related to the operation and use of device 200. For example, storage component 240 may include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, and / or solid-state disks), compact discs (CDs), digital versatile discs (DVDs), floppy disks, cassette tapes, magnetic tapes, and / or another type of non-volatile computer-readable media, and corresponding drives.

[0032] Input component 250 includes components that allow device 200 to receive information via user input (e.g., touchscreen display, keyboard, keypad, mouse, buttons, switches, and / or microphone). Additionally or optionally, input component 250 may include sensors for sensing information (e.g., a global positioning system (GPS) component, accelerometer, gyroscope, and / or actuator). Output component 260 includes components that provide output information from device 200 (e.g., a display, speaker, and / or one or more light-emitting diodes (LEDs)).

[0033] Communication interface 270 includes transceiver components (e.g., transceivers and / or separate receivers and transmitters) that enable device 200 to communicate with other devices via, for example, wired connections, wireless connections, or a combination of wired and wireless connections. Communication interface 270 can allow device 200 to receive information from and / or provide information to another device. For example, communication interface 270 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0034] Device 200 can perform one or more of the processes described herein. Device 200 can perform these processes in response to processor 220 executing software instructions stored on a non-volatile computer-readable medium such as memory 230 and / or storage unit 240. Computer-readable medium is defined herein as a non-volatile storage device. Storage devices include storage space within a single physical storage device or storage space distributed across multiple physical storage devices.

[0035] Software instructions can be read from another computer-readable medium or from another device via communication interface 270 into memory 230 and / or storage unit 240. When executed, the software instructions stored in memory 230 and / or storage unit 240 can cause processor 220 to perform one or more processes described herein. Additionally or alternatively, hardware circuitry may be used in place of or in combination with the software instructions to perform one or more processes described herein. Therefore, the embodiments described herein are not limited to any particular combination of hardware circuitry and software.

[0036] Figure 2 The number and arrangement of components shown are provided as an example. In practice, device 200 may include additional components, fewer components, different components, or components related to... Figure 2 The components shown are arranged differently. Additionally or optionally, a set of components of device 200 (e.g., one or more components) may perform one or more functions, which are described as being performed by another set of components of device 200.

[0037] A 5G Media Streaming (5GMS) system can be a component of an application function, application server, and interface from a 5G media streaming architecture that supports downlink media streaming services, uplink media streaming services, or both. A 5GMS application provider can be a party that interacts functionally with the 5GMS system and provides a 5GMS-aware application that interacts functionally with the 5GMS system. A 5GMS-aware application can refer to an application in a User Equipment (UE) provided by a 5GMS application provider, which contains the service logic of 5GMS application services and interacts with other 5GMS clients and network functions via interfaces and application programming interfaces (APIs) defined in the 5GMS architecture. A 5GMS client can refer to a UE function that is a 5GMS downlink (5GMSd) client, a 5GMS uplink (5GMSu) client, or both.

[0038] A 5GMSd client can refer to a UE function that includes at least a 5G media streaming player and a media session processor for downlink streaming, and that is accessible through a well-defined interface / API. A 5GMSu client can refer to an initiator of a 5GMSu service that is accessible through a well-defined interface / API. A 5GMSu media streaming player can refer to a UE function that can deliver streaming content uplink to the application server (AS) function of a 5GMS application provider, and can interact with 5GMSu-aware applications for media acquisition and subsequent streaming, as well as a media session processor for media session control.

[0039] Dynamic policies refer to dynamic policies and charging control (PCC) rules used for uplink or downlink application processes during a media session. An Egest Session refers to an uplink media streaming session from a 5GMS AS to a 5GMS Application Provider. An Ingest Session refers to a session that uploads media content to a 5GMSd AS. A policy template refers to a set of (semi-static) Policy or Control Function (PCF) / Network Exposure Function (NEF) API parameters, which are specific to the 5GMS Application Provider and are the resulting PCC rules. A Policy Template ID identifies the desired policy template, which is used by the 5GMSd Application Function (AF) to select the appropriate PCF / NEF API from the 5G system, enabling the PCF to compile the desired PCC rules. Media player entries can refer to a document or a pointer to a document that defines a media presentation (e.g., a media presentation description (MPD) for DASH or a uniform resource locator (URL) for a video clip file). Media streaming player entries can refer to a pointer to the entry point that defines an uplink media streaming session (e.g., in the form of a URL). Presentation entries can refer to a document or a pointer to a document that defines an application presentation, such as an HTML5 document.

[0040] A provisioning session can refer to a data structure provided at the interface (M1d) by a 5GMSd application provider configured with 5GMSd features associated with a set of 5GMSd-aware applications. A 5GMSd media player can refer to a UE function capable of replaying and rendering media presentations based on media playback entries, and providing basic controls such as play, pause, search, and stop to the 5GMSd-aware application. Server access information can refer to a set of parameters and addresses (including the 5GMSd AF address and 5GMSd AS address) required to activate a streaming session. Service and content discovery can refer to the functions and procedures provided by the 5GMSd application provider to the 5GMS-aware application, enabling end users to discover available streaming services and content provisioning and select specific services or content items for access. Service announcements can refer to the process between the 5GMS-aware application and the 5GMS application provider, enabling the 5GMS-aware application to obtain 5GMS service access information directly or by referencing this information.

[0041] A third-party player can refer to a part of an application that uses an API to perform selected 5GMSd functions for media content playback. A third-party uplink streamer can refer to a part of an application that uses an API to perform selected 5GMSu functions for media content capture and streaming.

[0042] Figure 3 This is a diagram of a media architecture 300 for media uplink streaming according to an embodiment. A 5GMSu application provider 301 can use 5GMSu to perform uplink streaming services. The 5GMSu application provider 301 can provide a 5GMSu-aware application 302 on the UE 303 to utilize the 5GMSu client 304 and network functions by using interfaces and APIs defined in 5GMSu. The 5GMSu AS can be an AS dedicated to 5G media uplink streaming. The 5GMSu client 304 can be an internal function of the UE 303 dedicated to 5G media uplink streaming.

[0043] 5GMSu AF 306 and 5GMSu AS 305 can provide data network (DN) 307 functionality. Functions in a trusted DN can be trusted by the operator's network. Therefore, an AF in a trusted DN can communicate directly with all 5G core functions. Functions in an external DN can only communicate with 5G core functions via link 320 through NEF 308.

[0044] Media architecture 300 can connect the internal functions and related network functions of UE 303 for 5G media uplink streaming. Therefore, media architecture 300 can include multiple functions. For example, the 5GMSu client 304 on UE 303 is the initiator of 5GMSu services accessible via an interface / API. 5GMSu client 304 can include two sub-functions: a media session processor 309 and a media streaming player 310. The media session processor 309 can communicate with 5GMSu AF 306 to establish, control, and support the delivery of media sessions. The media session processor 309 can display APIs that can be used by the 5GMSu-aware application 302. The media streaming player 310 can communicate with 5GMSu AS 305 to stream media content, provide services to the 5GMSu-aware application 302 for media acquisition and streaming, and provide services to the media session processor 309 for media session control. The 5GMSu-aware application 302 can control the 5GMSu client 304 by implementing external application or content service provider-specific logic and enabling the establishment of media sessions. For example, the 5GMSu AS 305 can host 5G media functions and can be implemented as a content delivery network (CDN). The 5GMSu application provider 301 can use 5GMSu to stream media from the 5GMSu-aware application 302 for external application or content-specific media functions, such as media storage, consumption, transcoding, and redistribution. The 5GMSu AF 306 can provide various control functions to the media session processor 309 on the UE 303 and / or the 5GMSu application provider 301. The 5GMSu AF 306 can relay or initiate requests for different PCF 311 processes or interact with other network functions.

[0045] Media architecture 300 may include several different interfaces. For example, link 321 may involve M1u, which may be a 5GMSu supply API presented by 5GMSuAF 306 to provide usage of media architecture 300 and obtain feedback. Link 322 may be associated with M2u, which may be a 5GMSu publishing API presented by 5GMSu AS 305 and used when 5GMSu AS 305 in a trusted DN (such as DN 307) is selected to receive content for streaming services. Link 323 may be associated with M3u, which may be an internal API used to exchange content hosting information on 5GMSu AS 305 in a trusted DN (such as DN 307). Link 324 may be associated with M4u, which may be a media uplink streaming API presented by 5GMSu AS 323 to media streaming player 310 for streaming media content. Link 325 may be associated with M5u, which may be a media session processing API presented by 5GMSu AF 305 to the media session processor for media session processing, control, and assistance, including appropriate security mechanisms such as authorization and authentication. Link 326 may be associated with M6u, which may be a UE 303 media session processing API presented by media session processor 309 to 5GMSu awareness application 302 to utilize 5GMSu functionality. Link 327 may be associated with M7u, which may be a UE media stream player API presented by media stream player 310 to 5GMSu awareness application 302 and media session processor 309 to utilize media stream player 310. Link 328 may be associated with M8u, which may be an application API for exchanging information between 5GMSu awareness application 302 and 5GMSu application provider 301, such as providing service access information to 5GMSu awareness application 302. UE 303 can also be implemented independently, so that interfaces M6u 326 and M7u 327 are not exposed.

[0046] Figure 4 This is a diagram of a media architecture 400 for media downlink streaming according to an embodiment. A 5GMSd application provider 401 can use 5GMSd to perform downlink streaming services. The 5GMSd application provider 401 can provide a 5GMSd-aware application 402 on the UE 403 to utilize the 5GMSd client 404 and network functions by using the interfaces and APIs defined in 5GMSd. The 5GMSd AS can be an AS dedicated to 5G media downlink streaming. The 5GMSd client 404 can be an internal function of the UE 403 dedicated to 5G media downlink streaming.

[0047] 5GMSd AF 406 and 5GMSd AS 405 are functionalities of DN 407. Functions in a trusted DN can be trusted by the operator's network. Therefore, an AF in a trusted DN can communicate directly with all 5G core functions. Functions in an external DN can only communicate with 5G core functions via Link 420 through NEF 408.

[0048] Media architecture 400 can connect the internal functions and related network functions of UE 403 for 5G media downlink streaming. Therefore, media architecture 400 can include multiple functions. For example, the 5GMSd client 404 on UE 403 is a receiver for 5GMSd services accessible via an interface / API. 5GMSd client 404 can include two sub-functions: a media session processor 409 and a media player 410. The media session processor 409 can communicate with the 5GMSd AS 406 to establish, control, and support the delivery of media sessions. The media session processor 409 can expose APIs used by the 5GMSd-aware application 402. The media player 410 can communicate with the 5GMSd AS 405 to stream media content, provide services to the 5GMSd-aware application 402 for media playback, and provide services to the media session processor 409 for media session control. The 5GMSd-aware application 402 can control the 5GMSd client 404 by implementing external application or content service provider-specific logic and enabling the establishment of media sessions. The 5GMSd AS 405 can host 5G media functions. The 5GMSd application provider 401 can provide external application or content-specific media functions, such as media creation, encoding, and formatting, which use 5GMSd to stream media to the 5GMSd-aware application 402. The 5GMSd AF 406 can provide various control functions to the media session processor 409 on the UE 403 and / or the 5GMSd application provider 401. The 5GMSd AF 406 can relay or initiate requests for different PCF 411 processing or interact with other network functions.

[0049] Media architecture 400 may include several different interfaces. For example, link 421 may be associated with M1d, which may be a 5GMSd supply API exposed by 5GMSd AF 406 to provide access to and feedback from media architecture 400. Link 422 may be associated with M2d, which may be a 5GMSd outgoing API exposed by 5GMSd AS 405 and is used when a trusted DN (such as DN 407) is selected to receive content for streaming services. Link 423 may be associated with M3d, which may be an internal API used to exchange content hosting information on 5GMSd AS 405 in a trusted DN (such as DN 407). Link 424 may be associated with M4d, which may be a media downlink streaming API exposed by 5GMSd AS 423 to media player 410 for streaming media content. Link 425 may be associated with M5d, which may be a media session processing API presented by the 5GMSd AF 405 to the media session processor for media session processing, control, and assistance, including appropriate security mechanisms such as authorization and authentication. Link 426 may be associated with M6d, which may be a UE 403 media session processing API presented by the media session processor 409 to the 5GMSd-aware application 402 to utilize 5GMSd functionality. Link 427 may be associated with M7d, which may be a UE media player API presented by the media player 410 to both the 5GMSd-aware application 402 and the media session processor 409 to utilize the media player 410. Link 428 may be associated with M8d, which may be an application API used for exchanging information between the 5GMSd-aware application 402 and the 5GMSd application provider 401, such as providing service access information to the 5GMSd-aware application 402.

[0050] Figure 5A diagram of a 5GMSd (5th Generation Media Streaming Downlink) download architecture 500 for standalone augmented reality (AR) (STAR) according to an embodiment. The AR STAR 5GMSd architecture 500 can also be applied to mixed reality (MR). Architecture 500 includes a 5G STARUE 502, a 5G system 504 (i.e., a 5G server and computing), and an AR / MR application provider 506. The 5G STAR UE 502 includes an AR runtime 508, an AR scene manager 510, media access functionality 512, and an AR / MR application 514. The AR runtime 508 includes an extended reality (XR) computing module 516, a posture correction module 518, and a sound field mapping module 520. The AR scene manager 510 includes a scene graph handler (SGH) 521, a synthesizer 522, an immersive visual renderer 523, and an immersive audio renderer 524. Media access function 512 includes a media session processor 526 and a media client 528. Media client 528 includes a two-dimensional (2D) codec 530, an immersive media decoder 532, a scene description delivery module 534, a content delivery module 536, and an XR spatial description delivery module 538. 5G STAR UE 502 includes a 5G system (Uu) 540, which communicates with the 5G node (gNb) 542 of the 5G system 504.

[0051] The 5G system 504 includes a media AF 544 and a media AS 546. The AR / MR application provider 506 includes an AR function 548 and an AR scene module 550. The media client 528 communicates with the media AS 546 via an M4 interface 582. The media session processor 526 communicates with the media AF 544 via an M5 interface 586. The AR / MR application 514 communicates with the AR / MR application provider 506 via an M8 interface 588. The AR / MR application 514 can receive user input 591 and AR runtime API data from the AR runtime 508. The AR runtime 508 can receive data from a camera 592 and a sensor 593, and can output the data to a display 594 and a speaker 595.

[0052] Embodiments of this disclosure provide a call flow comprising two loops: a streaming scenario and a scenario update as the outer loop, and a streaming media object for each scenario as the inner loop.

[0053] Figure 6A , Figure 6B and Figure 6C This is a diagram illustrating the operational flow of STAR-based 5G downlink streaming according to an embodiment. The system executing the operational flow of Figure 6 may include an AR / MR application 606, an AR runtime 608, an AR / MR scene manager 610, a media client 612, and a media session processor 614, which may be part of a STAR UE 602 (furthermore, the media client 612 and media session processor 614 may be part of a media access function). The system also includes a 5GMSd AF 616 and a 5GMSd AS 618. The system may also include an AR / MR application provider 620. The application provider 620 may refer to a scene server.

[0054] In operation 630, scene content is captured by 5GMSd AS 618. In operation 632, service announcements and content delivery are triggered by AR / MR application 606. Service access information includes media client entries or references to service access information provided via the M8d interface. In operation 634, media content / scene is selected. In operation 636, service access information is acquired or updated as needed (i.e., operation 636 is optional). In operation 638, AR / MR application 606 initializes scene manager 610 using the entry point (i.e., complete scene description) URL. In operation 640, media client 612 establishes a transport session for receiving the entry point.

[0055] In operations 641 to 672, a scene session loop is established, in which the system requests and renders the scene and updates the scene.

[0056] In operation 641, media client 612 requests and receives an entry point or an update to the scene description. In operation 642, the entry point is processed. In operation 644, AR / MR scene manager 610 requests the creation of a new AR / MR session from AR runtime 608. In operation 646, AR runtime 608 creates a new AR / MR session. In operation 648, a streaming session is created. Media client 612 and / or AR / MR scene manager 610 may provide necessary Quality of Service (QoS) information to media session processor 614. In operation 650, one or more streaming sessions are configured. In some embodiments, media session processor 614 may share information with 5GMSd AF 616, including desired QoS information. Based on the existing provision of AR / MR application provider 620, 5GMSd AF 616 may request QoS modifications for protocol data unit (PDU) sessions.

[0057] In operations 652 through 656, a media session is established for each media stream object. In operation 652, a transport session is established for the delivery manifest. For the required media content, media client 612 establishes a transport session to obtain the delivery manifest information. In operation 654, media client 612 requests and receives the delivery manifest from 5GMSd AS 618. In operation 656, media client 612 processes the delivery manifest. For example, media client 612 determines the number of transport sessions required to obtain the media. Media client 612 is configured to use the delivery manifest information to initialize the media pipeline for each media stream.

[0058] In operation 658, the AR / MR scene manager 610 and media client 612 configure the rendering and delivery of the media pipeline. In operation 660, media client 612 establishes a transport session to retrieve media content.

[0059] In operations 662 to 672, a media session loop (i.e., an inner session loop) is established within the scene session loop (i.e., the outer session loop). While the outer loop establishes a session and receives updates to the media content, the media session loop can run rendering and displaying the media content. Updates can be sent from the outer session loop to the inner session loop while the inner session loop is rendering content.

[0060] In operation 662, the latest pose information (e.g., updated scene or content) is acquired by the AR / MR scene manager 610 and shared with the media client 612. In operation 664, the media client 612 requests immersive media data based on a processed delivery list. The media client 612 may consider pose information (e.g., viewport-dependent streaming). In operation 666, the media client 612 receives the immersive data and triggers one or more media rendering pipelines accordingly, including registering AR content to the real world. In operation 668, the media client 612 decodes and processes the media data. For encrypted media data, the media client 612 may also decrypt it. In operation 670, the media client 612 passes the media data to the AR / MR scene manager 610. In operation 672, the AR / MR scene manager 610 renders the media and passes it to the AR runtime 608. The AR runtime 608 may perform further processing, such as registering AR content to the real world, pose correction, etc.

[0061] AR / MR scenes can be dynamically updated during streaming to the STAR device, and therefore, scenes can be completely changed during a streaming session. Scene updates for the STAR device are achieved through a dual-loop call flow, where media objects for the scene are streamed in the inner loop, while the scene is updated or changed in the outer loop. With the embodiments disclosed herein, whenever the scene is changed and updated, the inner loop is interrupted, and the previous media objects are replaced with new media objects relevant to the new scene, thus avoiding wasted streaming bandwidth for media objects that are no longer relevant in the new scene.

[0062] Figure 7 This is a flowchart of a STAR-based 5G downlink streaming method according to an embodiment. In operation 702, the system selects media content, which includes a scene. In operation 704, the system creates an AR / MR session for streaming the media content in an outer session loop. In operation 706, the system renders the media content in an inner session loop within the outer session loop. In operation 708, while the inner session loop is rendering the media content, the system updates the scene with the new scene by providing a new scene to the inner session loop in the outer session loop.

[0063] although Figure 7 An example block of process 700 is shown. In some embodiments, process 700 may include additional blocks, fewer blocks, different blocks, or blocks similar to those in the example. Figure 7 The blocks shown are arranged differently. Alternatively, two or more blocks of process 700 can be executed in parallel.

[0064] Furthermore, the proposed methods can be implemented by processing a circuit (e.g., one or more processors or one or more integrated circuits). In one example, one or more processors execute a program stored in a non-volatile computer-readable medium to perform one or more of the proposed methods.

[0065] The above-described technology can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media.

[0066] The embodiments of this disclosure can be used individually or in any combination in any order. Furthermore, the embodiments (and their methods) can be implemented by processing a circuit (e.g., one or more processors or one or more integrated circuits). In one example, one or more processors execute a program stored in a non-volatile computer-readable medium.

[0067] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Modifications and variations are possible based on the foregoing disclosure, or may be obtained from practice of the embodiments.

[0068] As used in this article, the term component is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software.

[0069] Even if combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible embodiments. In fact, many of these features can be combined in ways not specifically recited in the claims and / or disclosed in the specification. While each dependent claim listed below may directly depend on only one claim, the disclosure of possible embodiments includes every dependent claim in combination with all other claims in the claim set.

[0070] Elements, actions, or instructions used herein should not be construed as critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Additionally, as used herein, the term “group” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and is used interchangeably with “one or more.” The term “one” or similar language is used when referring to only one item. Furthermore, as used herein, the terms “has / have / having” are intended to be understood as open-ended terms. Additionally, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise.

Claims

1. A media streaming transmission method, characterized in that, include: The augmented reality (AR) application on the standalone augmented reality (STAR) user equipment (UE) selects media content supported by the STAR UE, the media content supported by the STAR UE including a complete scene description; Augmented Reality (AR) / Mixed Reality (MR) sessions are created from the AR runtime on the STAR UE for streaming media content supported by the STAR UE; The AR scene manager on the STAR UE configures the rendering and transmission of the media pipeline with the media client. In AR / MR sessions, streaming media content supported by the STAR UE employs a dual-loop call process. This dual-loop call process includes an external scene session loop and an internal media session loop, with the internal media session loop nested within the external scene session loop. The internal media session loop is configured to stream one or more media objects based on the complete scene description. The external scene session loop is configured to receive one or more updates from a scene, the updates containing at least one media object from the new scene, and to provide the at least one media object from the new scene to the internal media session loop while streaming one or more media objects to the STAR UE in the internal media session loop.

2. The method according to claim 1, characterized in that, Updating the scene includes updating the pose information.

3. The method according to claim 2, characterized in that, The updated scenario further includes: requesting immersive media based on the updated gesture information during the internal media session loop.

4. The method according to claim 3, characterized in that, The updated scenario further includes: In the internal media session loop, the immersive media is received; and In the internal media session loop, the AR content of the immersive media is registered to the real world.

5. The method according to claim 4, characterized in that, The update of the scenario further includes: decoding and processing the immersive media in the internal media session loop.

6. The method according to claim 1, characterized in that, Further includes: In the external scenario session loop, the number of transmission sessions required to acquire media is determined based on the media content supported by the STAR UE.

7. The method according to claim 6, characterized in that, The required number of transport sessions is determined based on the delivery manifest information.

8. A media streaming transmission device, characterized in that, include: At least one memory is configured to store program code; as well as At least one processor is configured to read the program code and operate according to the instructions of the program code, the program code comprising: A first selection code is configured to cause the at least one processor to select media content supported by the STAR UE, the media content including a complete scene description; The first creation code is configured to enable the at least one processor to create an augmented reality (AR) / mixed reality (MR) session for streaming media content supported by the STAR UE; The AR scene manager on the STAR UE configures the rendering and transmission of the media pipeline with the media client. In AR / MR sessions, streaming media content supported by the STAR UE employs a dual-loop call process. This dual-loop call process includes an external scene session loop and an internal media session loop, with the internal media session loop nested within the external scene session loop. The internal media session loop is configured to stream one or more media objects based on the complete scene description. The external scene session loop is configured to receive one or more updates from a scene, the updates containing at least one media object from the new scene, and to provide the at least one media object from the new scene to the internal media session loop while streaming one or more media objects to the STAR UE in the internal media session loop.

9. The device according to claim 8, characterized in that, The program code also includes first update code, which is configured to cause the at least one processor to update the pose information.

10. The device according to claim 9, characterized in that, The first update code further causes the at least one processor to request immersive media based on the updated gesture information in the internal media session loop.

11. The device according to claim 10, characterized in that, The first update code further enables the at least one processor to: In the internal media session loop, the immersive media is received; and In the internal media session loop, the AR content of the immersive media is registered to the real world.

12. The device according to claim 11, characterized in that, The first update code further enables the at least one processor to decode and process the immersive media in the internal media session loop.

13. The device according to claim 8, characterized in that, The program code further includes first determining code, which is configured to cause the at least one processor to determine, in the external scene session loop, the number of transmission sessions required to acquire the media based on the media content.

14. The device according to claim 13, characterized in that, The required number of transport sessions is determined based on the delivery manifest information.

15. A non-volatile computer-readable medium storing instructions, characterized in that, The instructions include: one or more instructions that, when executed by one or more processors of the device, cause the one or more processors to perform the method as described in any one of claims 1 to 7.

16. A device, characterized in that, It includes a processor and a memory; the memory stores a computer program that, when executed by the processor, causes the processor to perform the method as described in any one of claims 1 to 7.

Images