Method, device and medium for fifth generation media streaming uplink 5GMSu application function AF

By defining and implementing the creation and allocation mechanism of content discharge templates in 5G uplink streaming, the problem of lack of standardized content resource management in the prior art is solved, and the efficiency and reliability of the streaming process are improved.

CN115462021BActive Publication Date: 2024-11-12TENCENT AMERICA LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202180030901.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-10-08
Filing Date
2021-10-13
Publication Date
2024-11-12
Estimated Expiration
2041-10-13

AI Technical Summary

Technical Problem

The existing 5G uplink streaming architecture does not define the discharge protocol or discharge configuration, resulting in a lack of standardized content resource allocation and management mechanisms during media streaming.

Method used

Provided is a method and device to receive a request to create a content discharge template through a 5GMSu application provider, create a content discharge template, send an allocation request to the 5GMSu application server, and send a confirmation to the provider to realize the allocation and management of content resources.

Benefits of technology

It realizes the effective allocation and management of content resources in 5G uplink streaming, improves the efficiency and reliability of the streaming process, and ensures the correct configuration and use of content resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115462021B_ABST
    Figure CN115462021B_ABST
Patent Text Reader

Abstract

The present disclosure provides a method, device and medium for a fifth generation media streaming uplink 5GMSu application function AF. The method includes: receiving a first request to create a content discharge template CET from a 5GMSu application provider; creating the CET based on the first request received from the 5GMSu application provider; sending a second request to a 5GMSu application server AS to allocate content resources for discharge based on the created CET; and sending a confirmation of the creation of the CET to the 5GMSu application provider.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 168,956 filed with the U.S. Patent and Trademark Office on March 31, 2021 and U.S. Application No. 17 / 497,009 filed with the U.S. Patent and Trademark Office on October 8, 2021, the disclosures of which are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure generally relates to the fifth generation (5 th The present invention relates to 5G uplink streaming transmission, and more particularly to a method and apparatus for defining and signaling an egest configuration and an egest protocol in 5G uplink streaming transmission. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) TS26.512 defines the concept of uplink streaming, where content is streamed from a device to an external service provider. However, the existing streaming architecture only defines a general architecture for uplink and downlink media streaming. No draining protocol or draining configuration is defined. Summary of the invention

[0005] According to one aspect of the present disclosure, a method of a fifth generation media streaming uplink 5GMSu application function AF is provided. The method may include: receiving a first request to create a content discharge template CET from a 5GMSu application provider; creating the CET based on the first request received from the 5GMSu application provider; sending a second request to a 5GMSu application server AS to allocate content resources for discharge based on the created CET; and sending a confirmation of the creation of the CET to the 5GMSu application provider.

[0006] According to one aspect of the present disclosure, a device is provided. The device may include: at least one memory for storing program codes; and at least one processor for reading the program codes and operating according to the instructions of the program codes, wherein the program codes include: a first receiving code for causing the at least one processor to receive a first request for creating a content discharge template CET at the fifth generation media streaming uplink 5GMSu application function AF and from a 5GMSu application provider; a first creating code for causing the at least one processor to create the CET based on the first request received from the 5GMSu application provider; a first sending code for causing the at least one processor to send a second request to the 5GMSu application server AS, thereby allocating content resources for discharge based on the created CET; and a second sending code for causing the at least one processor to send a confirmation of the creation of the CET to the 5GMSu application provider.

[0007] According to one aspect of the present disclosure, a non-volatile computer-readable storage medium is provided. The non-volatile computer-readable medium may store instructions, the instructions including: one or more instructions, when executed by one or more processors of a device, enable the one or more processors to: at the fifth generation media streaming uplink 5GMSu application function AF, receive a first request to create a content discharge template CET from a 5GMSu application provider; create the CET based on the first request received from the 5GMSu application provider; send a second request to the 5GMSu application server AS, thereby allocating content resources for discharge based on the created CET; and send a confirmation of the creation of the CET to the 5GMSu application provider. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] 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:

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

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

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

[0012] Figure 4 is a diagram of a media architecture for content preparation after uplink ingest streaming, according to an embodiment.

[0013] Figure 5A and Figure 5B is an operational flow chart of content preparation after uplink access streaming according to an embodiment.

[0014] Figure 6 is a flow chart of a content preparation process after uplink access streaming according to an embodiment. DETAILED DESCRIPTION

[0015] 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.

[0016] 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.

[0017] 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.

[0018] 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.

[0019] 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”).

[0020] 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.

[0021] 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, etc.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] 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.

[0028] 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 .

[0029] 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.

[0030] 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.

[0031] 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).

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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).

[0039] 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.

[0040] 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.

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

[0042] 5GMSu AF 306 and 5GMSu AS 305 may be Data Network (DN) 307 functions. Functions in trusted DNs may be trusted by the operator's network. Therefore, AFs in trusted DNs may communicate directly with all 5G core functions. Functions in external DNs may communicate with 5G core functions via NEF 308 using only link 320.

[0043] The media architecture 300 can connect UE 303 internal functions and related network functions for 5G media uplink streaming. Accordingly, the media architecture 300 can include multiple functions. For example, the 5GMSu client 304 on the UE 303 can be the initiator of the 5GMSu service that can be accessed through the interface / API. The 5GMSu client 304 can include two sub-functions, a media session handler 309 and a media streamer 310. The media session handler 309 can communicate with the 5GMSu AF 306 to establish, control and support the delivery of a media session. The media session handler 309 can expose an API that can be used by the 5GMSu-aware application 302. The streaming player 310 can communicate with the 5GMSu AS 305 to stream media content, and provide services for media capture and streaming to the 5GMSu-aware application 302, and provide media session control services to the media session handler 309. The 5GMSu-aware application 302 can control the 5GMSu client 304 by implementing external applications, 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 be an external application or content specific media functionality, such as media storage, consumption, transcoding and redistribution of media streamed from the 5GMSu-aware application 302 using 5GMSu. The 5GMSu AF 306 can provide various control functions to the media session processor 309 of the UE 303, and / or the 5GMSu application provider 301. The 5GMSu AF 306 can relay or initiate requests for processing by different PCFs 311 or interact with other network functions.

[0044] The media architecture 300 may include a number of different interfaces. For example, link 321 may be associated with M1u, which may be a 5GMSu provisioning API exposed by the 5GMSu AF 306 to provision the use of the media architecture 300 and obtain feedback. Link 322 may be associated with M2u, which may be a 5GMSu publishing API exposed by the 5GMSu AS 305 and used when a 5GMSu AS 305 in a trusted DN (such as DN 307) is selected to receive content for a streaming service. Link 323 may be associated with M3u, which may be an internal API for exchanging information about 5GMSu AS 305 hosted content within a trusted DN such as DN 307. Link 324 may be associated with M4u, which may be a Media Uplink Streaming API exposed by the 5GMSu AS 323 to the streaming media player 310 to stream media content. Link 325 may be related to M5u, which may be a Media Session Handling API exposed by the 5GMSu AF 305 to the Media Session Processor for media session handling, control and assistance, which may also include appropriate security mechanisms, such as authorization and authentication. Link 326 may be related to M6u, which may be a UE 303 Media Session Handling API exposed by the Media Session Processor 309 to the 5GMSu-aware application 302 to use the 5GMSu functions. Link 327 may involve M7u, which may be a UE streaming player API exposed by the streaming player 310 to the 5GMSu-aware application 302 and the Media Session Processor 309 to use the streaming player 310. Link 328 may be related to M8u, which may be an application API for information exchange between the 5GMSu-aware application 302 and the 5GMSu application provider 301, for example, providing service access information to the 5GMSu-aware application 302. The UE 303 may also be implemented in a standalone manner such that the interfaces M6u 326 and M7u 327 are not exposed.

[0045] Figure 44 is a schematic diagram of a media architecture 400 for content preparation after uplink ingest streaming according to an embodiment. The media architecture 400 includes a UE 403, an external DN 407, and a trusted DN 408. The UE 403 includes a 5GMSu aware application 402 and a 5GMSu client 404. The external DN 407 includes a 5GMSu application provider 401. The trusted DN 408 includes a 5GMSu AS 405 and a 5GMSu AF 406. The 5GMSu AF 406 can relay or initiate requests for processing by different PCFs 411, or interact with other network functions via an N5 link 420.

[0046] Figure 4 A scenario is depicted where a 5GMSu application provider 401, or a 5GMSu aware application 402, requests that content be prepared for an uplink access flow and delivered to the 5GMSu application provider 401. As such, the 5GMSu application provider 401 may interface with the 5GMSu AF 406 via an M1u link 421, may interface with the 5GMSu AS 405 via an M2u link 422, and may interface with the 5GMSu aware application 402 via an M8u link 428. In addition, the 5GMSu client 404 may interface with the 5GMSu AS 405 via an M4u link 424, and may interface with the 5GMSu AF 406 via an M5u link 425. The 5GMSu AS 405 may interface with the 5GMSu AF 406 via an M3u link 430. The M3u link 430 may include an internal API between the 5GMSu AF 406 and the 5GMSu AS 405 for exchanging information of content hosted on the 5GMSu AS 405 within the trusted DN 408. The 5GMSu AS 405 may include an application server dedicated to 5G uplink media streaming.

[0047] According to an embodiment, the 5GMSu application provider 401 may create a provisioning session with the 5GMSu AF 406 using, for example, an M1u link 421. The 5GMSu application provider 401 may request the 5GMSu AF 406 to create a content egress template (CET), which defines instructions for content egress use using, for example, an M1u link 421. Based on the received request to create a CET, the 5GMSu AF 406 may request the 5GMSu AS 405 to allocate content resources for egress use using, for example, an M3u link 430. The 5GMSu AF 406 may confirm to the 5GMSu application provider 401 the successful creation of the CET using, using, for example, an M1u link 421. The 5GMSu application provider 401 may then notify the 5GMSu awareness application 402 of the availability of the service. In response to the request to create a CET, the CET is added as a new resource. The CET includes information for setting up draining using the M2u link 422, as described below in operation 544.

[0048] Figure 5A and Figure 5B is an operational flow chart of content preparation after uplink access streaming according to an embodiment. The operational flow uses, for example, 5GMSu Aware Application 502, 5GMSu Client 504, 5GMSu AF 506, 5GMSu AS 508, and 5GMSu Application Provider 510.

[0049] In operation 520, the 5GMSu application provider 510 creates a provisioning session with the 5GMSu AF 506 using interface M1u. In operation 522, the 5GMSu application provider 510 sends a request to create a CET to the 5GMSu AF 506 using interface M1u. In operation 524, the 5GMSu AF 506 discovers and requests resources allocated for drainage from the 5GMSu AS 508 using the M3u interface. In operation 526, the 5GMSu AF 506 sends a confirmation to the 5GMSu application provider 510 that the CET has been created using the M1u interface. In operation 528, the 5GMSu application provider 510 provides a service announcement indicating the availability of the service to the 5GMSu aware application 502. In operation 534, the 5GMSu AF 506 discovers and requests updated resources allocated for drainage from the 5GMSu AS 508 using the M3u interface.

[0050] In operation 530, the 5GMSu Aware Application 502 sends a request to start the service to the 5GMSu Application Provider 510 using the M8u interface. In operation 532, the 5GMSu Application Provider 510 sends a request to update the CET to the 5GMSu AF 506 using the M1u interface. In operation 536, the 5GMSu AF 506 sends a confirmation that the CET has been updated to the 5GMSu Application Provider 510 using the M1u interface. In operation 538, the 5GMSu Application Provider 510 confirms the service to the 5GMSu Aware Application 502 using the M8u interface.

[0051] In operation 540, the UE API is used from the 5GMSu client 504. In operation 542, the 5GMSu AF 506 performs service access information acquisition from the 5GMSu client 504. In operation 544, the 5GMSu client 504 sends a media session request to the 5GMSu AF 506 using the M5u interface. In operation 546, the 5GMSu AF 506 sends a request to start a content preparation process to the 5GMSu AS 508 using the M3u interface. In operation 548, the 5GMSu AS 508 performs an instantiation of the content preparation process. In operation 550, the 5GMSu AS 508 sends a confirmation indicating the start of the content preparation process to the 5GMSu AF 506 using the M3u link. In operation 552, media streaming is performed between the 5GMSu AS 508 and the 5GMSu client 504 using the M4u interface. In operation 554 , 5GMS egest is performed between the 5GMSu application provider 510 and the 5GMSu AS 508 using the M2u interface.

[0052] For content egest protocols, a content ingest protocol based on hyper-text transfer protocol (HTTP) pull and a content ingest protocol based on DASH-IF push are added for egestion. Table 1 shows supported egest content protocols.

[0053] Table 1

[0054]

[0055] When using HTTP pull-based content access protocol, since the 5GMSu application provider pulls content from the 5GMSu's AS, the relative address of the media content can be provided through the M8u interface (i.e., the 5GMSu-aware application provides the 5GMSu application provider with a list of relative content resource URLs).

[0056] For the content egest configuration API, an API is defined for creation, update, access and removal of CET resources, as shown in Table 2. Table 2 shows the operations supported by the content egest configuration API.

[0057] Table 2

[0058]

[0059] Content drain configuration may be defined based on CET. For CET, the data model shown in Table 3 may be used.

[0060]

[0061]

[0062] Figure 6 6 is a flow chart of a process 600 for content preparation after uplink access streaming according to an embodiment. In operation 602, the 5GMSu AF receives a first request to create a CET from the 5GMSu application provider. In operation 604, the 5GMSu AF creates the CET based on the first request received from the 5GMSu application provider. In operation 606, the 5GMSu AF sends a second request to the 5GMSu AS to allocate content resources for draining based on the created CET. In operation 608, the 5GMSu AF sends a confirmation to the 5GMSu application provider that the CET was created.

[0063] Although Figure 6 Example blocks of process 600 are shown, but in some implementations, process 600 may include Figure 6 The blocks of process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in process 600. Additionally or alternatively, two or more blocks of process 600 may be performed in parallel.

[0064] 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.

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

[0066] 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.

[0067] 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.

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

[0069] 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.

[0070] 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 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 intended to refer to an item, 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.

Claims

1. A method for fifth generation media streaming uplink 5GMSu application function AF, characterized in that: The method comprises: receiving a first request to create a content ejection template CET from a 5GMSu application provider; creating the CET based on the first request received from the 5GMSu application provider; Sending a second request to the 5GMSu application server AS, thereby allocating content resources for draining based on the created CET, creating a content draining configuration based on the created CET, the content draining configuration including a draining protocol at the interface M2u, the draining protocol including a content access protocol based on a hypertext transfer protocol HTTP pull and a content access protocol based on a DASH-IF push; and, A confirmation of creation of the CET is sent to the 5GMSu application provider.

2. The method according to claim 1, characterized in that The content drain configuration includes at least one of a drain path, a drain pull, a drain protocol, or a drain entry point.

3. The method according to claim 1, characterized in that Said sending a second request to allocate a content resource is performed using an interface between said 5GMSu AS and said 5GMSu AF.

4. The method according to claim 1, characterized in that: The CET defines at least one application programming interface for creating, updating, accessing, and removing the CET.

5. The method according to any one of claims 1 to 4, characterized in that: Further including: receiving a third request to update the CET from the 5GMSu application provider; as well as, Based on the received third request to update the CET, the CET is updated.

6. A device, characterized in that: include: A first receiving module is used to receive, at a fifth generation media streaming uplink 5GMSu application function AF, a first request to create a content ejection template CET from a 5GMSu application provider; A first creation module, configured to create the CET based on the first request received from the 5GMSu application provider; A first sending module is used to send a second request to the 5GMSu application server AS, so as to allocate content resources for discharge based on the created CET, and create a content discharge configuration based on the created CET, wherein the content discharge configuration includes a discharge protocol at the interface M2u, and the discharge protocol includes a content access protocol based on a hypertext transfer protocol HTTP pull and a content access protocol based on a DASH-IF push; as well as, The second sending module is used to send a confirmation of creating the CET to the 5GMSu application provider.

7. The device according to claim 6, characterized in that The content drain configuration includes at least one of a drain path, a drain pull, a drain protocol, or a drain entry point.

8. The device according to claim 6, characterized in that The sending of the second request for allocating content resources by the first sending module is performed using an interface between the 5GMSu AS and the 5GMSu AF.

9. The device according to claim 6, characterized in that The CET defines at least one application programming interface for creating, updating, accessing, and removing the CET.

10. The device according to any one of claims 6 to 9, characterized in that The device further comprises: A second receiving module is configured to receive a third request for updating the CET from the 5GMSu application provider; and The third receiving module is used to update the CET based on the received third request for updating the CET.

11. A device, characterized in that: include: one or more non-volatile computer readable media for storing computer program code; as well as, One or more computer processors, configured to access the computer program code and operate according to instructions of the computer program code to execute the method according to any one of claims 1 to 5.

12. A non-volatile computer-readable medium storing instructions, characterized in that: The instructions include: one or more instructions, which, when executed by one or more processors of a device, enable the one or more processors to perform the method according to any one of claims 1 to 5.