Method and apparatus for split rendering embedded in media streaming architecture of 5G network

Abstract

The method includes determining that a split management session is provisioned through a first split rendering interface, the first split rendering interface being an extension of an M1 interface; receiving a request to split the one or more client media functions of the UE through a second split rendering interface, the second split rendering interface being an extension of an M4 interface; and negotiating a segmentation of the one or more media functions between a segmentation rendering client of the UE and a segmentation rendering function of the 5GMS AS over the second segmentation rendering interface, where the negotiation is based on (i) one or more client media capabilities of the UE determined using a third segmentation rendering interface, where the one or more client media capabilities of the UE are different from the first segmentation rendering interface. The third split rendering interface is between the split rendering client and a function on the UE indicating one or more client media capabilities, and (ii) the one or more network capabilities of the 5GMS AS determined using a fourth split rendering interface, the fourth split rendering interface is between the split rendering function and a function on the 5GMS AS indicating one or more network capabilities.

Description

Cross-references

[0001] This application claims priority to U.S. Provisional Application No. 63 / 445,659 filed in the U.S. Patent and Trademark Office on February 14, 2023; U.S. Provisional Application No. 63 / 445,656 filed on February 14, 2023; U.S. Provisional Application No. 63 / 445,652 filed on February 14, 2023; and U.S. Application No. 18 / 440,374 filed on February 13, 2024. The disclosure of each of these applications is incorporated herein by reference in its entirety. Technical Field

[0002] The present disclosure generally relates to 5th generation media streaming (5GMS, 5 th The present invention relates to a management process in generation media streaming, and specifically to a method and apparatus for segmented rendering embedded in a media streaming transmission architecture of a 5G network. Background Art

[0003] The 3rd Generation Partnership Project (3GPP) defines a work item on split rendering of media delivery services, in which the client media functions are split between the device and the network edge. Therefore, as a result of the split, the client runs lighter and less demanding processes and can receive more complex applications and services. In addition, the edge network decodes and partially renders the received media into a simpler form, so that the client can run lighter processes. 5G augmented reality devices need to have intensive processing, including multiple parallel media decoding and media encoding, scene synthesis, and augmented reality rendering. Summary of the invention

[0004] According to one or more embodiments, a method for managing the splitting of one or more media functions of a client of a user equipment (UE) and a 5G media streaming (5GMS) application server (AS) executed by at least a processor includes: determining that a split management session is provisioned, wherein the split management session is provisioned through a first split rendering interface, and the first split rendering interface is an extension of an M1 interface; receiving a request to split the one or more client media functions of the UE through a second split rendering interface, and the second split rendering interface is an extension of an M4 interface; and negotiating the splitting of the one or more media functions between a split rendering client of the UE and a split rendering function of the 5GMS AS through the second split rendering interface, wherein the negotiation is based on (i) one or more client media capabilities of the UE determined using a third split rendering interface, wherein the third split rendering interface is between the split rendering client and a function indicating one or more client media capabilities on the UE, and (ii) one or more network capabilities of the 5GMS AS determined using a fourth split rendering interface, wherein the fourth split rendering interface is between the split rendering function and a function indicating one or more network capabilities on the 5GMS AS.

[0005] According to one or more embodiments, an apparatus for managing the splitting of one or more media functions includes: 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, wherein the program code includes: determining code configured to cause the at least one processor to determine that a split management session is provided, wherein the split management session is provided through a first split rendering interface, and the first split rendering interface is an extension of an M1 interface; receiving code configured to cause the at least one processor to receive a request to split the one or more client media functions of the UE through a second split rendering interface, and the second split rendering interface is an extension of an M4 interface; negotiating code configured to cause the at least one processor to negotiate the splitting of the one or more media functions between a split rendering client of the UE and a split rendering function of the 5GMS AS through the second split rendering interface, wherein the negotiation is based on (i) one or more client media capabilities of the UE determined using a third split rendering interface, wherein the third split rendering interface is between the split rendering client and a function indicating one or more client media capabilities on the UE, and (ii) the 5GMS AS determined using a fourth split rendering interface. The one or more network capabilities of the AS, wherein the fourth split rendering interface is between the split rendering function and a function indicating one or more network capabilities on the 5GMS AS.

[0006] According to one or more embodiments, a non-volatile computer-readable storage medium storing instructions, when the instructions are executed by a processor, causes the processor to execute a method for managing the splitting of one or more media functions of a client of a user equipment (UE) and a 5G media streaming (5GMS) application server (AS), the method comprising: determining that a split management session is provisioned, wherein the split management session is provisioned through a first split rendering interface, the first split rendering interface being an extension of an M1 interface; receiving a request to split the one or more client media functions of the UE through a second split rendering interface, the second split rendering interface being an extension of an M4 interface; and negotiating the splitting of the one or more media functions between a split rendering client of the UE and a split rendering function of the 5GMS AS through the second split rendering interface, wherein the negotiation is based on (i) one or more client media capabilities of the UE determined using a third split rendering interface, wherein the third split rendering interface is between the split rendering client and a function indicating one or more client media capabilities on the UE, and (ii) one or more network capabilities of the 5GMS AS determined using a fourth split rendering interface, wherein the fourth split rendering interface is between the split rendering function and a function indicating one or more network capabilities on the 5GMS AS. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Other features, properties and various advantages of the disclosed subject matter will become further apparent from the following detailed description and accompanying drawings, in which:

[0008] Figure 1 is a diagram of an environment in which the methods, apparatuses, and systems described herein may be implemented according to an embodiment.

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

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

[0011] Figure 4A and Figure 4B It is a schematic diagram of the architecture of a 5G standalone edge-related AR (5G_STAR EDGAR, 5G StandaloneEDGe-Dependent AR) UE according to an embodiment.

[0012] Figure 5 is a schematic diagram of a media architecture for media streaming according to an embodiment.

[0013] Figure 6 is a schematic diagram of a partition management architecture according to an embodiment.

[0014] Figure 7 is an operational flow chart of a client-driven segmentation management process according to an embodiment.

[0015] Figure 8 is an operational flow diagram of a network driven segmentation management process according to an embodiment.

[0016] Fig. 9 is a flow diagram of an example process for using a partition management architecture, according to an embodiment. DETAILED DESCRIPTION

[0017] The following detailed description of example embodiments refers to the accompanying drawings.The same reference numbers in different drawings may identify the same or similar elements.

[0018] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementation to the precise form disclosed. According to the above disclosure, modifications and variations are possible, or modifications and variations can be obtained from the practice of the implementation. In addition, one or more features or components of an embodiment may be incorporated into another embodiment (or one or more features of another embodiment) or combined with another embodiment (or one or more features of another embodiment). In addition, in the flowcharts and descriptions of the operations provided below, it should be understood that one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least partially), and the order of one or more operations may be switched.

[0019] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the implementation. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code - it should be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0020] Even though particular 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 implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with all other claims in the claim set.

[0021] The elements, actions or instructions used herein should not be interpreted as critical or necessary unless explicitly described as such. In addition, as used herein, the articles "a" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In the case of only one item, the term "one" or similar language is used. In addition, as used herein, the terms "has", "have", "having", "include", "including", etc. are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part", unless otherwise explicitly stated. In addition, statements such as "at least one of [A] and [B]" or "at least one of [A] or [B]" should be understood to include only A, only B, or both A and B.

[0022] Reference throughout this specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the illustrated embodiment is included in at least one embodiment of the present solution. Thus, the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0023] In addition, the features, advantages and characteristics of the present disclosure may be combined in any suitable manner in one or more embodiments. Based on the description herein, those skilled in the relevant art will recognize that the present disclosure may be practiced without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages that may not be present in all embodiments of the present disclosure may be recognized in certain embodiments.

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

[0025] The user device 110 includes one or more devices that can receive, generate, store, process, and / or provide information related to the platform 120. For example, the user device 110 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smart phone, a wireless phone, etc.), a wearable device (e.g., smart glasses or a smart watch), or a similar device. In some embodiments, the user device 110 can receive information from the platform 120 and / or send information to the platform 120.

[0026] The platform 120 includes one or more devices as described elsewhere herein. In some embodiments, the platform 120 may include a cloud server or a cloud server group. In some embodiments, the platform 120 may be designed to be modular so that software components can be swapped in or out according to specific needs. In this way, the platform 120 can be easily and / or quickly reconfigured to have different uses.

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

[0028] Cloud computing environment 122 includes an environment hosting platform 120. Cloud computing environment 122 may provide computing, software, data access, storage, and other services that do not require end users (e.g., user devices 110) to be aware of the physical location and configuration of the systems and / or devices hosting platform 120. As shown, cloud computing environment 122 may include a set of computing resources 124 (collectively, “computing resources 124” and individually, “computing resource 124”).

[0029] The computing resources 124 include one or more personal computers, workstation computers, server devices, or other types of computing and / or communication devices. In some embodiments, the computing resources 124 can host the platform 120. Cloud resources can include computing instances executed in the computing resources 124, storage devices provided in the computing resources 124, data transmission devices provided by the computing resources 124, etc. In some embodiments, the computing resources 124 can communicate with other computing resources 124 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0030] Further Figure 1 As shown, the computing resources 124 include a set of cloud resources, such as one or more application programs ("APP") 124-1, one or more virtual machines ("VM") 124-2, virtualized storage ("VS") 124-3, one or more hypervisors ("HYP") 124-4, and the like.

[0031] The applications 124-1 include one or more software applications that can be provided to or accessed by the user device 110 and / or the platform 120. The applications 124-1 do not require the software applications to be installed and executed on the user device 110. For example, the applications 124-1 may include software associated with the platform 120, and / or any other software that can be provided through the cloud computing environment 122. In some embodiments, one application 124-1 can send / receive information to or from one or more other applications 124-1 through the virtual machine 124-2.

[0032] Virtual machine 124-2 includes a software implementation of a machine (e.g., a computer) that executes programs, similar to a physical machine. Virtual machine 124-2 can be a system virtual machine or a process virtual machine, depending on the use and correspondence of virtual machine 124-2 to any real machine. System virtual machines can provide a complete system platform that supports the execution of a complete operating system ("OS"'). Process virtual machines can execute a single program and can support a single process. In some embodiments, 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, synchronization, or long-term data transfer.

[0033] Virtualized storage 124-3 includes one or more storage systems and / or one or more devices that use virtualization technology within the storage system or device of the computing resource 124. In some embodiments, within the context of the storage system, the types of virtualization may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of logical storage from physical storage so that the storage system can be accessed without considering the physical storage or heterogeneous structure. Separation may allow administrators of the storage system to flexibly manage the storage of end users. File virtualization may eliminate the dependency between data accessed at the file level and the location of the physical storage file. This may optimize the performance of storage usage, server consolidation, and / or non-disruptive file migration.

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

[0035] The network 130 includes one or more wired and / or wireless networks. For example, the network 130 may include a cellular network (e.g., a fifth generation (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber-based network, etc., and / or a combination of these or other types of networks.

[0036] Figure 1 The number and arrangement of devices and networks shown are provided as examples. Figure 1 There may be more devices and / or networks, fewer devices and / or networks, different devices and / or networks, or different arrangements of devices and / or networks than those shown. Figure 1 Two or more of the devices shown may be implemented in a single device, or Figure 1 The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, one set of devices (eg, one or more devices) of environment 100 may perform one or more functions described as being performed by another set of devices of environment 100.

[0037] Figure 2 yes Figure 1 Device 200 may correspond to user device 110 and / or platform 120. Figure 2 As shown, device 200 may include a bus 210 , a processor 220 , a memory 230 , a storage component 240 , an input component 250 , an output component 260 , and a communication interface 270 .

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

[0039] Storage component 240 stores information and / or software related to the operation and use of device 200. For example, storage component 240 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cassette, a magnetic tape, and / or another type of non-volatile computer-readable medium, and a corresponding drive.

[0040] Input components 250 include components that allow device 200 to receive information, such as through user input, such as a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone. Additionally or alternatively, input components 250 may include sensors for sensing information (e.g., global positioning system (GPS) components, accelerometers, gyroscopes, and / or actuators). Output components 260 include components that provide output information from device 200, such as a display, a speaker, and / or one or more light emitting diodes (LEDs).

[0041] The communication interface 270 includes a transceiver-like component (e.g., a transceiver and / or a separate receiver and transmitter) that enables the device 200 to communicate with other devices, for example, via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface 270 can allow the device 200 to receive information from another device and / or provide information to another device. For example, the communication interface 270 can 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.

[0042] Device 200 can perform one or more processes described herein. Device 200 can perform these processes in response to processor 220 executing software instructions stored by non-volatile computer-readable media (e.g., memory 230 and / or storage component 240). Computer-readable media is defined herein as non-volatile memory devices. Memory devices include storage space within a single physical storage device or storage space distributed on multiple physical storage devices.

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

[0044] Figure 2 The number and arrangement of components shown are provided as examples. Figure 2 The device 200 may include more components, fewer components, different components, or components arranged differently than the components shown. Additionally or alternatively, a set of components (e.g., one or more components) of the device 200 may perform one or more functions described as being performed by another set of components of the device 200.

[0045] The 5G media streaming (5GMS) system may be an assembly of application functions, application servers and interfaces from the 5G media streaming architecture that supports downlink media streaming services, or supports uplink media streaming services, or supports both. A 5GMS application provider may include a party that interacts with the functions of the 5GMS system and provides a 5GMS-aware application that interacts with the functions of the 5GMS system. A 5GMS-aware application may refer to an application in a user equipment (UE) provided by a 5GMS application provider, which contains the service logic of the 5GMS application service and interacts with other 5GMS clients and network functions via interfaces and application programming interfaces (APIs) defined in the 5GMS architecture. A 5GMS client may refer to a UE function, which may be a 5GMS downlink (5GMSd) client, a 5GMS uplink (5GMS uplink, 5GMSu) client, or both.

[0046] 5GMSd client may refer to a UE function that includes at least a 5G media streaming player and a media session handler for downlink streaming and can be accessed through a well-defined interface / API. 5GMSu client may refer to the initiator of a 5GMSu service that can be accessed through a well-defined interface / API. 5GMSu media streamer may refer to a UE function that enables uplink streaming media content to the Application Server (AS) function of the 5GMS application provider and interacts with a 5GMSu aware application for media capture and subsequent streaming and a media session handler for media session control.

[0047] Dynamic policy may refer to dynamic policy and charging control (PCC) rules for uplink or downlink application flows during a media session. An EgestSession may refer to an uplink media streaming session from a 5GMS AS to a 5G MSu application provider. An ingest session may refer to a session for uploading media content to a 5GMSd AS. A policy template may refer to a set of (semi-static) policy or control function (PCF) / network exposure function (NEF) API parameters that are specific to 5GMS application providers and the resulting PCC rules. A policy template ID may identify the desired policy template, which is used by the 5GMSd application function (AF) to select the appropriate PCF / NEF API for the 5G system so that the PCF can compile the desired PCC rules. A Media Player Entry may refer to a document or a pointer to a document that defines a media presentation (e.g., a Media Presentation Description (MPD) of DASH or a Uniform Resource Locator (URL) of a video clip file). A Media Streamer Entry may refer to a pointer (e.g., in the form of a URL) that defines an entry point for an uplink media streaming session. A presentation entry may refer to a document or a pointer to a document that defines an application presentation (e.g., an HTML5 document).

[0048] A provisioning session may refer to a data structure provided at an interface (M1d) by a 5GMSd application provider that configures 5GMSd features associated with a set of 5GMSd-aware applications. A 5GMSd media player may refer to a UE function that enables playback and rendering of a media presentation based on a media play entry and exposes some basic controls, such as play, pause, search, stop, to 5GMSd-aware applications. Server access information may refer to a set of parameters and addresses (including 5GMSd AF and 5GMSd AS addresses) required to activate a receive streaming session. Service and content discovery may refer to functions and procedures provided by a 5GMSd application provider to a 5GMS-aware application that enables an end user to discover available streaming services and content offerings and select a specific service or content item for access. A service announcement may refer to a procedure performed between a 5GMS-aware application and a 5GMS application provider, so that the 5GMS-aware application can obtain 5GMS service access information directly or in the form of a reference to the information.

[0049] A third party player may refer to a portion of an application that uses the API to exercise selected 5GMSd functions to play back media content. A third party uplink streamer may refer to a portion of an application that uses the API to exercise selected 5GMSd functions to capture and stream media content.

[0050] Figure 3 3 is a schematic diagram of the architecture of an augmented reality (AR) UE 300 according to one or more embodiments. The AR UE 300 may be a 5G UE with 5G connectivity provided by an embedded 5G modem and 5G system components. The AR UE 300 may include several components and user controls for an AR experience, including but not limited to a sensor 320A, a camera 320B, a microphone 320C, an eye buffer display 320D, and a speaker 320E.

[0051] The AR UE 300 may include an AR / MR application 302 configured to communicate with various device resources to provide an AR experience to a user. In one or more examples, the AR / MR application 302 communicates with the AR runtime 304 via an AR runtime API 312A, communicates with the media access function (MAF) via a MAF-API 312B, and communicates with the AR scene manager 308 via an AR scene manager API 312C. These APIs enable the AR / MR application 302 to discover and query media capabilities in terms of support and available resources at runtime.

[0052] In one or more examples, while the AR / MR application 302 is running, downlink media flows from the 5G system 310 to the MAF 306 in compressed form, and then flows from the MAF 306 in decoded form to the AR scene manager 308. The MAF 306 may also provide a scene description to the AR scene manager 308. In one or more examples, in parallel, the AR UE 300 is configured to establish an uplink data flow from the AR runtime 304 to the MAF 306, where the raw media and sensor data may be in uncompressed form, and then from the MAF 306 to the 5G system 310, where the MAF 306 may have compressed the data for intended delivery over the network.

[0053] When the application and / or application service provider decides to run the client media function in split rendering mode, the function is replaced by two new modules: an edge-related lightweight media service client, and a media processing application running on the 5GMS AS. In one or more examples, the client media function can be an application or one or more tasks to be performed by a client device such as a UE. Figure 4A and Figure 4B An example of a media delivery architecture with a 5G EDGAR UE 400 and a cloud / edge 402 for implementing segmentation is illustrated. However, 3GPP SR_MSE does not specify an architecture or process for performing segmentation rendering.

[0054] Figure 55GMS application provider 501 can use 5GMS for streaming services. In one or more examples, the streaming service can be a live video streaming session using a social media platform. 5GMS application provider 501 can be implemented as a server. 5GMS application provider 501 can provide 5GMS-aware applications 502 on UE 303 to utilize 5GMS clients 504 and network functions using interfaces and APIs defined in 5GMS. 5GMS application server (AS) 505 can be an AS dedicated to 5G media streaming. 5GMS client 504 can be an internal function of UE 503 dedicated to 5G media streaming.

[0055] 5GMS Application Function (AF) 506 and 5GMS AS 505 may be data network (DN) 507 functions. 5GMS AF 506 may be implemented as a server. Functions in a trusted DN may be trusted by the operator network. Therefore, the AF in a trusted DN may communicate directly with some or all 5G core functions. Functions in an external DN may communicate with the 5G core functions via a network exposure function (NEF) 508 using only link 520. NEF 508 facilitates secure access to public network services and capabilities of the 5G network.

[0056] The media architecture 500 can connect the UE 503 internal functions and related network functions for 5G media streaming. Therefore, the media architecture 500 can include multiple functions. For example, the 5GMS client 504 on the UE 503 can be the initiator of the 5GMS service that can be accessed through the interface / API. The 5GMS client 504 can include two sub-functions, a media session handler 509 and a media streaming processor 510. The media session handler 509 can communicate with the 5GMS AF 506 to establish, control and support the distribution of media sessions. The media session handler 509 can expose an API that can be used by the 5GMS-aware application 502. The media streamer 510 can communicate with the 5GMS AS 505 to stream media content and provide services to the 5GMS-aware application 502 for media capture and streaming, and provide services to the media session handler 509 for media session control. The 5GMS-aware application 502 can control the 5GMS client 504 by implementing external application or content service provider specific logic and enabling the establishment of media sessions. For example, the 5GMS AS 505 can host the 5G media functions and can be implemented as a content delivery network (CDN). The 5GMS application provider 501 can be an external application or content-specific media functions (e.g., media storage, consumption, transcoding, and redistribution) that streams media from the 5GMS-aware application 502 using 5GMS. The 5GMS AF 506 can provide various control functions to the media session handler 509 on the UE 503 and / or the 5GMS application provider 501. The 5GMS AF 506 can relay or initiate requests for different policy control functions (PCFs) 511 processing or interact with other network functions.

[0057] The media architecture 500 may include multiple different interfaces. For example, link 521 may involve M1, which may be a 5GMS provisioning API exposed by 5GMS AF 506 to supply the use of the media architecture 500 and obtain feedback. Link 522 may involve M2, which may be a 5GMS publishing API exposed by 5GMS AS 505 and used when selecting a 5GMS AS 505 in a trusted DN such as DN 507 to receive content for streaming services. Link 523 may involve M3, which may be an internal API for exchanging information about content hosted on 5GMS AS 505 within a trusted DN such as DN 507. Link 524 may involve M4, which may be a media streaming API exposed by 5GMS AS 505 to media streamer 510 for streaming media content. Link 525 may involve M5, which may be a media session handling API exposed by the 5GMS AF 505 to the media session handler for media session handling, control and assistance, which may also include appropriate security mechanisms (e.g., authorization and authentication). Link 526 may involve M6, which may be a UE 503 media session handling API exposed by the media session handler 509 to the 5GMS-aware application 502 to utilize 5GMS functions. Link 527 may involve M7, which may be a UE media streamer API exposed by the media streamer 510 to the 5GMS-aware application 502 and the media session handler 509 to utilize the media streamer 510. Link 528 may involve M8, which may be an application API for information exchange between the 5GMS-aware application 502 and the 5GMS application provider 501, such as providing service access information to the 5GMS-aware application 502. The UE 503 may also be implemented in a standalone manner such that interfaces M6 526 and M7 527 are not exposed. Figure 5 The architecture shown does not include split rendering functionality.

[0058] The embodiments of the present disclosure relate to Figure 6 The illustrated segmentation management architecture embedded in the 5G media streaming architecture. In order to manage segmentation, several entities in the device and the network need to interact with each other.

[0059] Figure 6 An exemplary 5G media streaming architecture in which a segmentation management architecture is embedded is illustrated.

[0060] According to one or more embodiments, a split-rendering client (SRC) 510A is added to the media stream processor 510. The SRC may be configured to obtain UE media capabilities and negotiate with the 5GMS AS 505 to agree on a split-rendering process at the 5GMS AS 505.

[0061] In one or more examples, a device media function (DMF) 510B is added to the media stream processor 510. The DMF 510 may include one or more media processing functions running on the UE 503.

[0062] According to one or more embodiments, a split-rendering function (SRF) 505A is added to the 5GMS AS 505. The SRF 505A may be configured to obtain the 5GMS AS processing capability and negotiate with the UE 503 to configure the split-rendering process at the 5GMS AS 505.

[0063] In one or more examples, an application server function (ASF) 505B is added to the 5GMS AS 505. The ASF 505B may include one or more functions to run the segmentation rendering process on the 5GMS AS 505. The ASF 505B may provide its processing capabilities to the SRF.

[0064] The above entities can communicate with each other using the following disclosed interfaces. In one or more examples, the interaction between the above functions and other functions in the 5GMS architecture can be internal to the device or server, or defined as part of the 5GMS interface.

[0065] In one or more examples, communication between SRC 510A and SRF 505A can be supported as part of an extended M4 interface. The extension to this interface can be referred to as SR-4.

[0066] In one or more examples, communication between the SRF 505A and the 5GMS-aware application 502 can be supported as part of an extended M7 interface. The extension to this interface can be referred to as SR-7.

[0067] In one or more examples, the 5GMS application provider 501 can supply split rendering through an extended M1 interface, and the 5GMS AF 506 passes the supply to the SRF 505B through an extended M3 interface. The extensions to the M1 and M3 interfaces for split rendering can be referred to as SR-1 and SR-3, respectively.

[0068] In one or more examples, the interface between the SRF 505A and the ASF 505B may be referred to as SR-9 and may be used by the SRF 505A to retrieve the capabilities of the ASF 505B.

[0069] In one or more examples, the interface between the SRC 510A and the DMF 510B can be referred to as SR-10 and can be used by the SRC 510A to retrieve the media capabilities of the UE 503.

[0070] In one or more examples, one of two different deployment scenarios for the start of the split negotiation can be utilized. In one or more examples, the split negotiation can be client-initiated. In the client-initiated split negotiation, the 5GMS-aware application 502 can request the SRC 510A to initiate the split negotiation. The SRC 510A can negotiate with the SRF 505A to find the best or optimal split. In one or more examples, the best or optimal split can be the split of the application that minimizes the resource utilization of the UE 503 and the 5GMS AS505. Due to changes in the available resources of the client, the 5GMS-aware application 502 can also authorize the SRC 510A to renegotiate the split during the media delivery session.

[0071] In one or more examples, the split negotiation may be network initiated. In a network initiated split, the 5GMS application provider 501 may request the SRF 505A to initiate a split negotiation. The SRF 505A may present the possibilities to the SRC 510A and start a negotiation to find the best split. The 5GMS application provider 501 may also authorize the SRF 505A to renegotiate the split during the session due to changes in the available resources of the 5GMS AS 505.

[0072] According to one or more embodiments, segmentation management can be static or dynamic. In one or more examples, static segmentation management can be performed, where the segmentation management framework runs before starting a media delivery session or when a non-segmented rendering media delivery session is determined to be segmented. In static segmentation management, segmentation of client media functions occurs only once before or during a media delivery session.

[0073] In one or more examples, dynamic segmentation management can be performed, where the segmentation management architecture runs in parallel with the media delivery session. In dynamic segmentation management, the performance of the client and the 5GMS AS 505 can be monitored during the media delivery session, and new segmentation can be performed based on the status of the client and / or the 5GMS AS 505. In one or more examples, the performance of the client can be determined based on the workload of the client exceeding a workload threshold or the processing speed of the client decreasing below a processing speed threshold. In one or more examples, the performance of the 5GMS AS 505 can be determined based on the workload of the 5GMS AS 505 exceeding a workload threshold or the processing speed of the 5GMS AS 505 decreasing below a processing speed threshold.

[0074] The segmentation management architecture has several advantages. For example, segmentation management is separated from media delivery and edge management, where segmentation management can be run in parallel using the SR interface discussed above.

[0075] Embodiments of the present disclosure provide interfaces for provisioning segmentation management sessions, interactions between clients and networks, applications and clients, and network segmentation functions and network application servers. These APIs (e.g., interfaces) provide simple interaction and independence with other architectures (e.g., media delivery and edge management), and simplify the parallel existence of these architectures.

[0076] Embodiments of the present disclosure provide an architecture combined with a 5G media streaming architecture. Thus, a new interface can be embedded in an existing 5G media streaming architecture. For example, an SR-1 interface can be embedded in an M1 interface, an SR-3 interface can be embedded in an M3 interface, and an SR-4 interface can be embedded in an M4 interface.

[0077] The embodiments of the present disclosure also define two new interfaces: SR-9 and SR-10, which are unique to split rendering.

[0078] Embodiments of the present disclosure provide a control plane architecture. Entities in the control plane architecture interact only in the control plane, and therefore, they remain separate from the media panel.

[0079] Embodiments of the present disclosure provide for segmentation management to be initiated by the client or by the network, where either entity can initiate the negotiation for segmentation.

[0080] Embodiments of the present disclosure provide static and dynamic segmentation with a single architecture. The same solution can be used for both cases.

[0081] Figure 7The diagram illustrates a schematic diagram of an operation flow 700 for establishing split rendering by a client. The operation flow 700 may be performed between a 5GMS-aware application 702, a 5GMS client 704 having a DMF 704A and an SRC 704B, a 5GMS AS 706 having an SRF 706A and an ASF 706B, and a 5GMS application provider 710. The 5GMS-aware application 702 may correspond to the 5GMS-aware application 502 ( Figure 6 ). The 5GMS client 704 may correspond to the 5GMS client 504 ( Figure 6 ). DMF 704A may correspond to DMF510B ( Figure 6 ). SRC 704B may correspond to SRC 510A ( Figure 6 ). The 5GMS AS 706 may correspond to the 5GMS AF 506 ( Figure 6 ). SRF 706A may correspond to SRF 505A. ASF 706B may correspond to ASF 505B. 5GMS application provider 710 may correspond to application provider 510 ( Figure 6 ).

[0082] Operational flow 700 may begin at operation 712, where the 5GMS application provider 710 requests the SRF 706A to provision a split management session. This operation may be performed using the SR-1 and SR-3 interfaces. For example, the 5GMS application provider 710 may provision a split management session via the SR-1 interface, and the 5GMS AF 708 may pass the provision to the SRF 706A via the SR-3 interface.

[0083] In operation 714, the split management session is announced to the 5GMS aware application 702 as part of the service access information. The announcement can be performed through the M8u interface.

[0084] In operation 716, the 5GMS-aware application 702 requests the SRC 704B for splitting of the client media function. The request in operation 716 may be performed through the SR-7 interface.

[0085] In operation 718, SRC 704B queries DMF 704A to discover the media capabilities of the client. For example, SRC 704B may send a request to DMF 704A, where DMF 704A responds with a message indicating one or more device capabilities of the client. The message of operation 718 may be sent via an SR-10 interface.

[0086] In operation 720, SRC 704B may request the SRF 706A for splitting of the client media function. The request may be sent via the SR-4 interface.

[0087] In operation 722, SRF 706A may query ASF 706B regarding the capabilities of ASF 706. SRF 706A may send a message to ASF 706B, where ASF 706B responds with a message indicating the capabilities of ASF 706B. The message of operation 722 may be sent over an SR-9 interface.

[0088] In operation 724, the SRC 704B and the SRF 706B negotiate acceptable capabilities of the device and agree on a split option. The negotiation between the SRC 704B and the SRF 706B may be based on the client capabilities discovered in operation 718 and the capabilities of the 5GMS AS 706 discovered in operation 722. The negotiation may be performed over the SR-4 interface. In one or more examples, if the application to be executed includes tasks A, B, C, D, and E, the tasks may be split between the client and the network based on the negotiation, where the client performs tasks A and B, and the network may perform tasks C, D, and E.

[0089] In operation 726, the SRC confirms to the 5GMS aware application 702 that segmentation rendering on the network is running. The confirmation can be sent over the SR-7 interface.

[0090] Figure 8 A schematic diagram of an operational flow 800 for establishing split rendering over a network is illustrated.

[0091] The operation flow 800 may be performed between a 5GMS-aware application 802, a 5GMS client 804 having a DMF 804A and an SRC 804B, a 5GMS AS 806 having an SRF 806A and an ASF 806B, and a 5GMS application provider 810. The 5GMS-aware application 802 may correspond to the 5GMS-aware application 502 ( Figure 6 ). The 5GMS client 804 may correspond to the 5GMS client 504 ( Figure 6 ). DMF 804A may correspond to DMF 510B ( Figure 6 ). SRC 804B may correspond to SRC 510A ( Figure 6 ). 5GMS AS 806 may correspond to 5GMS AF 506 ( Figure 6 ). SRF 806A may correspond to SRF 505A. ASF 806B may correspond to ASF 505B. 5GMS application provider 810 may correspond to application provider 510 ( Figure 6 ).

[0092] Operational flow 800 may begin at operation 812, where the 5GMS application provider 810 requests the SRF 806A to provision a split management session. This operation may be performed using the SR-1 and SR-3 interfaces. For example, the 5GMS application provider 810 may provision a split management session via the SR-1 interface, and the 5GMS AF 808 may pass the provision to the SRF 806A via the SR-3 interface.

[0093] In operation 814, the split management session is announced to the 5GMS-aware application 802 as part of the service access information. The announcement can be performed through the M8u interface.

[0094] In operation 816, the SRF 806A may query the ASF 806B for the capabilities of the 5GMS AS 806. The SRF 806A may transmit a message to the ASF 806B, where the ASF 806B responds with a message indicating the capabilities of the 5GMS AS 806. The message of operation 816 may be sent over the SR-9 interface.

[0095] In operation 818, SRF 806A requests the SRC 804B for the splitting of the client media functions. The request may be sent via the SR-4 interface.

[0096] In operation 820, SRC 804B queries DMF 804A to discover the media capabilities of the client. For example, SRC 804B may send a request to DMF 804A, where DMF 804A responds with a message indicating one or more device capabilities of the client. The message of operation 820 may be sent via SR-10.

[0097] In operation 822, SRC 804B and SRF 806A negotiate acceptable capabilities of the device and agree on a split option. The negotiation between SRC 804B and SRF 806A may be based on the client capabilities discovered in operation 820 and the capabilities of 5GMS AS 806 discovered in operation 816. The negotiation may be performed over the SR-4 interface.

[0098] In operation 824, the SRC 804B confirms to the 5GMS aware application 802 that the segmentation rendering on the edge is running. The confirmation can be sent over the SR-7 interface.

[0099] Embodiments of the present disclosure provide a simple negotiation scheme between SRC 510A and SRF 505A for split rendering configuration. In a simple split rendering negotiation, SRF 505A provides the capabilities of the device to SRC 510A, and if SRC 510A is able to accommodate split rendering processing for the addressed device, the configuration is confirmed. Based on these embodiments, no back-and-forth negotiation occurs, and in one or more examples, SRC 510A may be responsible for making decisions regarding confirmation.

[0100] In one or more examples, split rendering includes (1) the 5GMS application provider 501 supplies a mobile network operation (MNO) to perform split rendering (SR-1), (2) providing the address of the SRF 505A to the UE 503 via M8 or M5, (3) the SRC 510A provides the UE's capabilities to the SRF 505A via the SR-4 interface, and (4) if confirmed, the SRC 510A responds to the SRF 505A with an updated media item; otherwise, the SRC 510A rejects the request.

[0101] In one or more examples, the split rendering provisioning process may rely on one or more RESTful APIs, including one or more split rendering provisioning programs and one or more split rendering provisioning APIs.

[0102] In one or more examples, the program used by the 5GMS application provider 501 and the 5GMS AF 506 to supply the split rendering process can be executed on the M1 interface.

[0103] In one or more examples, the provisioning of the split rendering process includes creating a split rendering configuration program. The 5GMS application provider 501 can use the program to create a new split rendering configuration. The 5GMS application provider can use the HTTP POST method for this, and the request message body can include a SplitRenderingConfiguration resource. If the program is successful, the 5GMS AF 506 can generate a resource identifier representing the new split rendering configuration. In this case, the 5GMS AF can respond with a 201 (Created) HTTP response message and can provide a URL to the newly created resource in the location header field. The response message body may include a SplitRenderingConfiguration resource representing the current state of the split rendering configuration, including any fields set by the 5GMS AF 506. If the program is unsuccessful, the 5GMS AF 506 should provide an error code.

[0104] In one or more examples, the provisioning of the split rendering process includes a read split rendering configuration property procedure. The 5GMS application provider can use the procedure to obtain the properties of the existing split rendering resources from the 5GMS AF 506. The HTTP GET method can be used for this purpose. If the procedure is successful, the 5GMS AF 506 can respond with a 200 (OK) response message, which includes the SplitRenderingConfiguration resource in the response message body. If the procedure is unsuccessful, the 5GMS AF 506 can provide an error code.

[0105] In one or more examples, the provisioning of the split rendering process includes a procedure for updating split rendering configuration properties. The update operation can be called by the 5GMS application provider 501 to modify the properties of an existing SplitRenderingConfiguration resource. In one or more examples, all writable properties except domainNameAlias ​​can be updated. HTTPPATCH or HTTP PUT methods can be used for update operations. If the procedure is successful, the 5GMS AF 506 can respond with 200 (OK) and provide the content of the resource in the response, thereby confirming the successful update operation. If the procedure is unsuccessful, the 5GMSd AF should provide an error code.

[0106] In one or more examples, the provisioning of the split rendering process includes destroying the split rendering configuration program. The 5GMS application provider 501 can use this operation to destroy the split rendering configuration resources and terminate the related distribution. The HTTP DELETE method can be used for this purpose. As a result, the 5GMS AF 506 can release any associated network resources, clear any cached contents, and delete any corresponding configuration. If the procedure is successful, the 5GMS AF responds with a 200 (OK) response message. If the procedure is unsuccessful, the 5GMS AF 506 can provide an error code.

[0107] In one or more examples, the split rendering provider may use one or more split rendering provisioning APIs. These providers may specify an API used by the 5GMS application provider 501 at interface M1 to provision and manage the 5GMS AS split rendering functionality by interacting with the 5GMS AF 506. Each configuration may be represented by a SplitRenderingConfiguration. The data model is specified below. The RESTful resources for managing split rendering configurations are also specified below.

[0108] In one or more examples, the split rendering provisioning API may be accessed via the following URL base path: {apiRoot} / 3gpp-m1 / {apiVersion} / provisioning-sessions / {provisioningSessionId} /

[0109] Table 1 below shows exemplary operations and corresponding HTTP methods supported by this API. In each case, the provisioning session identifier may be replaced with {provisioningSessionId} in the above URL template, and the sub-resource path specified in the second column will be appended to the URL base path. Table 1: Operations supported by the split rendering provisioning API

[0110] An exemplary data model for a SplitRenderingConfiguration resource is specified in Table 2. Table 2: Definition of SplitRenderingConfiguration resource

[0111] In one or more examples, a data model is specified for split rendering in service access information. The data model can be used for the SR-5 interface. In one or more examples, an attribute can be included in the ServiceAccessInformation resource to signal the availability of the split rendering service in the 5GMS AS 506. The attribute can indicate the protocol and address of the SRF 505A, as illustrated in Table 3. Table 3: Split rendering attributes in the ServiceAccessInformation resource

[0112] In one or more examples, when the UE receives the split rendering configuration, the UE uses the information to contact the 5GMS ASSRF 505A to establish split rendering. The UE SRC 510A uses splitRenderingConfiguraturation to send the UE's media capabilities to the SRF505A. If the SRF 505A can initialize a split rendering process that can adapt to the UE's capabilities, the SRF505A confirms the new media entry point. These procedures can be performed over the SR-4 interface.

[0113] In one or more examples, HTTP POST may be used as the default protocol for initiating a split rendering request. In this case, SRC 510A may include the media capabilities of the UE in the HTTP POST body. The default format of the body may be JSON as defined in MeCAR. If the procedure is successful, SRF 510A may respond with a 200 (OK) response message and include the media entry point in the body of the message. If the procedure is unsuccessful, SRF 510 should provide a response code indicating a rejection of the negotiation.

[0114] Fig. 9 is a flow chart of an example process 900 performed by an SRC or SRF. The process may be performed by an SRC 510A ( Figure 6 )、SRC 704B( Figure 7 )、SRF 505A( Figure 6 ) or SRF 806A( Figure 8 )implement.

[0115] The process may begin at operation S902, where it is determined that a split management session is provisioned. The provisioning of the split management session may be performed according to operation 712 ( Figure 7 ) or operation 812( Figure 8 ) to execute.

[0116] The process proceeds to operation S904, where a request to split one or more client media functions is received. The request may be based on operation 716 ( Figure 7 ) or operation 818( Figure 8 ) to execute.

[0117] The process proceeds to operation S906, where the segmentation of one or more client media functions is performed between the SRC and the SRF. Figure 7 ) or operation 822( Figure 8 ) to perform negotiation. The negotiation may be based on the determined client media capabilities (e.g., operation 718 or 820) and the determined capabilities of the 5GMS AS (e.g., operation 722 or 816).

[0118] According to one or more embodiments, a method for managing the splitting of a client's media functions between a device and a network edge computing resource, wherein the functions are embedded in a 5G media streaming architecture, wherein the functions extend the 5G media streaming architecture API to include interfaces required for split rendering configuration, wherein interfaces are defined for retrieving device capabilities, network computing capabilities, and interfaces for provisioning split management sessions, and the process is directed and managed by an application on the client or by an application service provider on the network, or the responsibility is delegated to corresponding entities on the device and the network, wherein static and dynamic split management can be performed as needed for the media delivery session.

[0119] According to one or more embodiments, a procedure for managing the splitting of a client's media functions between a device and a network edge computing resource in a 5G media streaming architecture driven by a client on the device, after seeing the offered split management session, an application requests the client to start splitting. The split rendering client of the device negotiates with the split rendering function on the network to determine the best implementation of split rendering. After reaching an agreement, the split rendering function starts the media split rendering process on the network and notifies the client how to access the split rendering process on the network, wherein the client starts media delivery by requesting media from the split rendering on the network, and continues media delivery.

[0120] According to one or more embodiments, a procedure for splitting the media functions of a client between a device and a network edge computing resource in a network-driven management 5G media streaming architecture, after seeing the provisioned split management session, the split rendering function discovers the media capabilities of the network application server on the network. Then, it contacts the split rendering client on the device's split rendering client and negotiates the best implementation of splitting the client functions into two parts (network and device). After reaching an agreement, the split rendering function starts the media split rendering process on the network and notifies the client how to access the split rendering process on the network, wherein the client starts media delivery by requesting media from the split rendering on the network, and continues media delivery.

[0121] According to one or more embodiments, procedures and data structures for a split rendering provisioning API are defined so that an application service provider can request to establish split rendering for any 5G media streaming application through an M1 interface, wherein creation, updating, retrieval, and deletion of resources are provided.

[0122] According to one or more embodiments, a program and data structure for providing split rendering instantiation information through service access information is provided by the innovation, wherein the protocol, format and address of the application service split rendering function are added to the service access information, wherein the client can use such information to instantiate the split rendering function in the application server.

[0123] According to one or more embodiments, a simple negotiation procedure for instantiating a split rendering function is provided, wherein a client provides its capabilities via a default HTTP POST API using a JSON object that describes the client's media capabilities, and the split rendering function of an application server decides whether it can accommodate such client's split rendering, and if so, confirms the service by providing a media service entry.

[0124] Further, the proposed method can be implemented by a processing circuit (eg, one or more processors or one or more integrated circuits). In one example, one or more processors execute a program stored in a non-transitory computer readable medium to perform one or more of the proposed methods.

[0125] The techniques described above may be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media.

[0126] The embodiments of the present disclosure may be used alone or in combination in any order. In addition, each embodiment (and method thereof) may be implemented by a processing 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.

[0127] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

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

[0129] Although combinations of features are referenced in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features can be combined in ways not specifically referenced in the claims and / or disclosed in the specification. Although each of the dependent claims listed below may be directly dependent on only one claim, the disclosure of possible implementations includes each dependent claim in combination with all other claims in the claim set.

[0130] Elements, actions or instructions used herein should not be interpreted as critical or essential unless explicitly described as such. In addition, as used herein, the articles "a" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and can be used interchangeably with "one or more". When only one item is intended to be referred to, the term "one" or similar language is used. In addition, as used herein, the terms "has", "have", "having", etc. are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated.

[0131] The above disclosure also includes the following embodiments:

[0132] (1) A method for managing the splitting of one or more media functions of a client of a user equipment (UE) and a 5G media streaming (5GMS) application server (AS) executed by at least a processor, characterized in that the method includes: determining that a split management session is provisioned, wherein the split management session is provisioned via a first split rendering interface, wherein the first split rendering interface is an extension of an M1 interface; receiving a request to split the one or more client media functions of the UE via a second split rendering interface, wherein the second split rendering interface is an extension of an M4 interface; and negotiating the splitting of the one or more media functions between a split rendering client of the UE and a split rendering function of the 5GMS AS via the second split rendering interface, wherein the negotiation is based on (i) one or more client media capabilities of the UE determined using a third split rendering interface, wherein the third split rendering interface is between the split rendering client and a function indicating one or more client media capabilities on the UE, and (ii) one or more network capabilities of the 5GMS AS determined using a fourth split rendering interface, wherein the fourth split rendering interface is between the split rendering function and a function indicating one or more network capabilities on the 5GMS AS.

[0133] (2) A method according to feature (1), wherein the provision of the split management session is included in service access information of a 5GMS-aware application provided to the UE by a 5GMS application provider.

[0134] (3) The method according to feature (2), further comprising: the split rendering client receiving a request to split the one or more media functions from the 5GMS-aware application through a fifth split rendering interface, wherein the fifth split rendering interface is an extension of the M7 interface.

[0135] (4) A method according to feature (3), wherein the negotiation is initiated by the split rendering client, and wherein the request to split the one or more client media functions received through the second split rendering interface is sent from the split rendering client to the split rendering function based on the request received through the fifth split rendering interface.

[0136] (5) A method according to feature (4), further comprising: after the negotiation, sending a confirmation of the negotiation that the one or more client media functions have been executed from the split rendering client to the 5GMS-aware application through the fifth split rendering interface.

[0137] (6) A method according to features (1)-(5), wherein the provision of the split management session is passed between a 5GMS application function (AF) and the 5GMS AS via a sixth split rendering interface, wherein the sixth split rendering interface is an extension of the M3 interface.

[0138] (7) A method according to feature (6), wherein the one or more network capabilities of the 5GMSAS determined using the fourth split rendering interface are performed based on the delivery of the provisioning of the split management session through the sixth split rendering interface.

[0139] (8) A method according to features (6) or (7), wherein the negotiation is initiated by the network, and wherein the request to split the one or more client media functions received through the second split rendering interface is transmitted from the split rendering function to the split rendering client based on the delivery of the provision of the split management session through the sixth split rendering interface.

[0140] (9) A method according to any one of features (1) to (8), wherein the negotiated split of the one or more client media functions is a static split, and the static split is not updated after performing the negotiated split.

[0141] (10) A method according to any one of features (1) to (9), wherein the negotiated split of the one or more client media functions is a dynamic split, and the dynamic split is updated after performing the negotiated split.

[0142] (11) A method according to feature (2), wherein the provisioning of the split management session further includes creating a new split rendering configuration between the 5GMS application provider and a 5GMS application function (AF).

[0143] (12) A method according to feature (11), wherein upon successful creation of the split rendering configuration, the 5GMS application provider retrieves the split management session from the 5GMS AF.

[0144] (13) A method according to feature (11) or (12), wherein after creating the split rendering configuration, the 5GMS application provider initiates an update procedure with the 5GMS AF to update the split rendering configuration.

[0145] (14) The method according to features (11) to (13), wherein after creating the split rendering configuration, the 5GMS application provider initiates a deletion procedure with the 5GMS AF to delete the split rendering configuration.

[0146] (15) A method according to features (2)-(14), wherein the service access information specifies one or more of a protocol, a format, and an address of the split rendering function to instantiate the split rendering function in the 5GMS AS.

[0147] (16) A method according to feature (15), wherein the segmented rendering function is instantiated via an HTTP POST API using one or more JavaScript Object Notation (JSON) objects, wherein the JSON objects describe the one or more client media capabilities of the UE.

[0148] (17) A method according to feature (16), wherein when it is determined that the splitting of the one or more client media functions can be accommodated, the split rendering client receives a media service entry point from the split rendering function.

[0149] (18) A method according to feature (17), wherein a media delivery session using the media service entry point begins after negotiating the splitting of the one or more client media capabilities.

[0150] (19) An apparatus for managing the splitting of one or more media functions, comprising: 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, wherein the program code comprises: determining code configured to cause the at least one processor to determine that a split management session is provisioned, wherein the split management session is provisioned via a first split rendering interface, wherein the first split rendering interface is an extension of an M1 interface; receiving code configured to cause the at least one processor to receive a request to split the one or more client media functions of the UE via a second split rendering interface, wherein the second split rendering interface is an extension of an M4 interface; negotiating code configured to cause the at least one processor to negotiate the splitting of the one or more media functions between a split rendering client of the UE and a split rendering function of the 5GMS AS via the second split rendering interface, wherein the negotiation is based on (i) one or more client media capabilities of the UE determined using a third split rendering interface, wherein the third split rendering interface is between the split rendering client and a function indicating one or more client media capabilities on the UE, and (ii) the 5GMS AS determined using a fourth split rendering interface. The one or more network capabilities of the AS, wherein the fourth split rendering interface is between the split rendering function and a function indicating one or more network capabilities on the 5GMS AS.

[0151] (20) A non-volatile computer-readable storage medium storing instructions, which, when executed by a processor, cause the processor to perform a method for managing the splitting of one or more media functions of a client of a user equipment (UE) and a 5G media streaming (5GMS) application server (AS), the method comprising: determining that a split management session is provisioned, wherein the split management session is provisioned via a first split rendering interface, the first split rendering interface being an extension of an M1 interface; receiving a request to split the one or more client media functions of the UE via a second split rendering interface, the second split rendering interface being an extension of an M4 interface; and negotiating the splitting of the one or more media functions between a split rendering client of the UE and a split rendering function of the 5GMS AS via the second split rendering interface, wherein the negotiation is based on (i) one or more client media capabilities of the UE determined using a third split rendering interface, wherein the third split rendering interface is between the split rendering client and a function indicating one or more client media capabilities on the UE, and (ii) one or more network capabilities of the 5GMS AS determined using a fourth split rendering interface, wherein the fourth split rendering interface is between the split rendering function and the 5GMS AS. Between functions on an AS indicating one or more network capabilities.

Claims

1. A method for managing the segmentation of one or more media functions of a client of a user equipment (UE) and a 5G media streaming (5GMS) application server (AS) performed by at least a processor, characterized in that The method comprises: Determining that a split management session is provisioned, wherein the split management session is provisioned through a first split rendering interface, the first split rendering interface being an extension of an M1 interface; receiving a request to split the one or more client media functions of the UE through a second split rendering interface, where the second split rendering interface is an extension of the M4 interface; and The splitting of the one or more media functions is negotiated between the split rendering client of the UE and the split rendering function of the 5GMS AS through the second split rendering interface, wherein the negotiation is based on (i) one or more client media capabilities of the UE determined using a third split rendering interface, wherein the third split rendering interface is between the split rendering client and a function indicating one or more client media capabilities on the UE, and (ii) one or more network capabilities of the 5GMS AS determined using a fourth split rendering interface, wherein the fourth split rendering interface is between the split rendering function and a function indicating one or more network capabilities on the 5GMS AS.

2. The method according to claim 1, characterized in that The provision of the split management session is included in service access information of the 5GMS-aware application provided by a 5GMS application provider to the UE.

3. The method according to claim 2, characterized in that Further including: The split rendering client receives a request to split the one or more media functions from the 5GMS-aware application through a fifth split rendering interface, where the fifth split rendering interface is an extension of the M7 interface.

4. The method according to claim 3, characterized in that The negotiation is initiated by the split rendering client, wherein the request to split the one or more client media functions received through the second split rendering interface is sent from the split rendering client to the split rendering function based on the request received through the fifth split rendering interface.

5. The method according to claim 4, characterized in that Further including: After the negotiation, a confirmation of the negotiation that the one or more client media functions have been performed is sent from the split rendering client to the 5GMS-aware application via the fifth split rendering interface.

6. The method according to claim 1, characterized in that The provision of the split management session is communicated between a 5GMS application function (AF) and the 5GMS AS via a sixth split rendering interface, wherein the sixth split rendering interface is an extension of the M3 interface.

7. The method according to claim 6, characterized in that The one or more network capabilities of the 5GMS AS determined using the fourth split rendering interface is performed based on the delivery of the provisioning of the split management session through the sixth split rendering interface.

8. The method according to claim 6, characterized in that The negotiation is initiated by the network, wherein the request to split the one or more client media functions received through the second split rendering interface is transmitted from the split rendering function to the split rendering client based on the passing of the provision of the split management session through the sixth split rendering interface.

9. The method according to claim 1, characterized in that: The negotiated split of the one or more client media functions is a static split that is not updated after performing the negotiated split.

10. The method according to claim 1, characterized in that The negotiated split of the one or more client media functions is a dynamic split that is updated after performing the negotiated split.

11. The method according to claim 2, characterized in that The provisioning of the split management session further includes creating a new split rendering configuration between the 5GMS application provider and a 5GMS application function (AF).

12. The method according to claim 11, characterized in that Upon successful creation of the split rendering configuration, the 5GMS application provider retrieves the split management session from the 5GMS AF.

13. The method according to claim 11, characterized in that After creating the segmented rendering configuration, the 5GMS application provider initiates an update procedure with the 5GMS AF to update the segmented rendering configuration.

14. The method according to claim 11, characterized in that After creating the split rendering configuration, the 5GMS application provider initiates a deletion procedure with the 5GMS AF to delete the split rendering configuration.

15. The method according to claim 2, characterized in that The service access information specifies one or more of a protocol, a format, and an address of the split rendering function to instantiate the split rendering function in the 5GMS AS.

16. The method according to claim 15, characterized in that The segmented rendering function is instantiated via an HTTP POST API using one or more javascript object notation (JSON) objects, the JSON objects describing the one or more client media capabilities of the UE.

17. The method according to claim 16, characterized in that When it is determined that the segmentation of the one or more client media functions can be accommodated, the segmented rendering client receives a media service entry point from the segmented rendering function.

18. The method according to claim 17, characterized in that A media delivery session using the media service entry point begins after negotiating the splitting of the one or more client media capabilities.

19. An apparatus for managing segmentation of one or more media functions, comprising: at least one memory configured to store program code; as well as At least one processor is configured to read a program code and operate according to instructions of the program code, wherein the program code includes: determining code configured to cause the at least one processor to determine that a split management session is provisioned, wherein the split management session is provisioned through a first split rendering interface, the first split rendering interface being an extension of an M1 interface; Receiving code, configured to cause the at least one processor to receive a request to split the one or more client media functions of the UE through a second split rendering interface, where the second split rendering interface is an extension of the M4 interface; The negotiation code is configured to cause the at least one processor to negotiate the splitting of the one or more media functions between the split rendering client of the UE and the split rendering function of the 5GMS AS through the second split rendering interface, wherein the negotiation is based on (i) one or more client media capabilities of the UE determined using a third split rendering interface, wherein the third split rendering interface is between the split rendering client and a function indicating one or more client media capabilities on the UE, and (ii) one or more network capabilities of the 5GMS AS determined using a fourth split rendering interface, wherein the fourth split rendering interface is between the split rendering function and a function indicating one or more network capabilities on the 5GMS AS.

20. A non-volatile computer-readable storage medium storing instructions, which, when executed by a processor, causes the processor to perform a method for managing the segmentation of one or more media functions of a client of a user equipment (UE) and a 5G media streaming (5GMS) application server (AS), the method comprising: Determining that a split management session is provisioned, wherein the split management session is provisioned through a first split rendering interface, the first split rendering interface being an extension of an M1 interface; receiving a request to split the one or more client media functions of the UE through a second split rendering interface, where the second split rendering interface is an extension of the M4 interface; and The splitting of the one or more media functions is negotiated between the split rendering client of the UE and the split rendering function of the 5GMS AS through the second split rendering interface, wherein the negotiation is based on (i) one or more client media capabilities of the UE determined using a third split rendering interface, wherein the third split rendering interface is between the split rendering client and a function indicating one or more client media capabilities on the UE, and (ii) one or more network capabilities of the 5GMS AS determined using a fourth split rendering interface, wherein the fourth split rendering interface is between the split rendering function and a function indicating one or more network capabilities on the 5GMS AS.

Images