Methods, apparatuses, devices, and media for streaming

Abstract

Methods, apparatuses, devices, and non-transitory computer-readable storage media for streaming are provided. The method includes sending, by a 5th generation media streaming (5GMS) application provider to a 5GMS downlink application function (AF), a first request to create a first content hosting configuration template; receiving, at the 5GMS application provider from the 5GMS downlink AF, the first content hosting configuration template; sending, by the 5GMS application provider to a 5GMS uplink AF, a second request to create a second content hosting configuration template, the second request including protocol information; and receiving, at the 5GMS application provider from the 5GMS uplink AF, a confirmation that the second content hosting configuration template was created. The present invention enables uplink and downlink stitched streaming.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 168,962, filed March 31, 2021, and U.S. Application No. 17 / 497,027, filed October 8, 2021, the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to the 5th generation (5 th 5G (5G) media streaming th The invention relates to generation media streaming (5GMS), and particularly to methods, apparatus, devices, and media for establishing connections between 5GMS application servers for uplink and downlink streaming. Background Technology

[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, existing streaming architectures do not provide or define how to establish a session that streams content from one user to another by connecting uplink and downlink streaming. Summary of the Invention

[0005] According to one aspect of this disclosure, a method may include: sending a first request to a 5GMS downlink application function (AF) via a 5th-generation media streaming (5GMS) application provider to create a first content hosting configuration template; receiving the first content hosting configuration template from the 5GMS downlink AF at the 5GMS application provider; sending a second request to a 5GMS uplink AF via the 5GMS application provider to create a second content hosting configuration template, the second request including protocol information; and receiving confirmation from the 5GMS uplink AF at the 5GMS application provider regarding the creation of the second content hosting configuration template.

[0006] According to one aspect of this disclosure, an apparatus may include: at least one memory configured to store program code; and at least one processor configured to read the program code and operate according to the instructions of the program code, the program code including: a first transmission code configured to cause the at least one processor to send a first request to a 5GMS downlink AF via a 5GMS application provider to create a first content hosting configuration template; a first reception code configured to cause the at least one processor to receive the first content hosting configuration template from the 5GMS downlink AF at the 5GMS application provider; a second transmission code configured to cause the at least one processor to send a second request to a 5GMS uplink AF via a 5GMS application provider to create a second content hosting configuration template, the second request including protocol information; and a second reception code configured to cause the at least one processor to receive confirmation from the 5GMS uplink AF at the 5GMS application provider regarding the creation of the second content hosting configuration template.

[0007] According to one aspect of this disclosure, a non-transitory computer-readable medium may store instructions including, when executed by one or more processors of a device, causing one or more processors to: send a first request to a 5GMS downlink AF via a 5GMS application provider to create a first content hosting configuration template; receive the first content hosting configuration template from the 5GMS downlink AF at the 5GMS application provider; send a second request to a 5GMS uplink AF via the 5GMS application provider to create a second content hosting configuration template, the second request including protocol information; and receive confirmation from the 5GMS uplink AF at the 5GMS application provider regarding the creation of the second content hosting configuration template.

[0008] Given that existing streaming architectures do not provide or define how to establish a session for streaming content from one user to other users by connecting uplink and downlink streaming, this application provides a streaming method, apparatus, device, and medium for connecting uplink and downlink. Content is streamed from one user and distributed to other users via streaming, which is possible after content preparation. Uplink and downlink 5GAS can be established, enabling streaming media via a direct connection between the uplink and downlink 5GAS, wherein a content hosting configuration template is used to set the configuration. Through this invention, streaming with connected uplink and downlink is achieved. Attached Figure Description

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

[0010] Figure 1 The diagram shows an environment in which the methods, apparatus and systems described herein can be implemented according to an embodiment.

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

[0012] Figure 3 This is a diagram of a media architecture for media uplink streaming according to an implementation method.

[0013] Figure 4 This is a diagram of a media architecture for media downlink streaming according to an implementation method.

[0014] Figure 5 This is a diagram of a media system for uplink-to-downlink streaming according to an implementation method.

[0015] Figure 6 This is a flowchart illustrating the operation of uplink and downlink streaming in a 5G network according to an implementation method.

[0016] Figure 7 This is a diagram illustrating the operational flow of uplink and downlink streaming transmission in a 5G network according to an implementation method.

[0017] Figure 8 This is a diagram illustrating the process of uplink and downlink streaming according to an implementation method. Detailed Implementation

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

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

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

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

[0022] The cloud computing environment 122 includes the environment of the hosting platform 120. The cloud computing environment 122 can provide services such as computing, software, data access, and storage, which do not require the end user (e.g., user device 110) to know the physical location and configuration of the systems and / or devices of the hosting platform 120. As shown, the cloud computing environment 122 may include a set of computing resources 124 (collectively referred to as "computing resources 124" and individually referred to as "computingresource 124").

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

[0024] For example, further Figure 1 As shown, computing resources 124 include a set of cloud resources, such as one or more applications (APP) 124-1, one or more virtual machines (VMs) 124-2, virtualized storage devices (VS) 124-3, one or more hypervisors (HYPs) 124-4, etc.

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

[0026] Virtual machine 124-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 124-2 can be a system virtual machine or a process virtual machine, depending on the extent to which virtual machine 124-2 uses and corresponds to any real machine. A system virtual machine can be a complete system platform that supports the execution of a full operating system (OS). A process virtual machine can execute a single program and can support a single process. In some implementations, virtual machine 124-2 can execute on behalf of a user (e.g., user device 110) and can manage the infrastructure of the cloud computing environment 122, such as data management, synchronization, or long-duration data transfer.

[0027] Virtualized storage device 124-3 includes one or more storage systems and / or one or more devices that utilize virtualization technology within the storage system or device of computing resource 124. In some implementations, within the context of the storage system, the type of virtualization may include block virtualization and file virtualization. Block virtualization can refer to extracting (or separating) logical storage from physical storage, enabling access to the storage system regardless of physical storage or heterogeneous architecture. Separation allows storage system administrators flexibility in how they manage storage for end users. File virtualization eliminates the dependency between data accessed at the file level and the location where the file is physically stored. This enables performance optimization for storage space usage, server consolidation, and / or non-disruptive file migration.

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

[0029] Network 130 includes one or more wired and / or wireless networks. For example, network 130 may include cellular networks (e.g., fifth-generation (5G) networks, Long-Term Evolution (LTE) networks, third-generation (3G) networks, code division multiple access (CDMA) networks, etc.), Public Land Mobile Networks (PLMNs), Local Area Networks (LANs), Wide Area Networks (WANs), Metropolitan Area Networks (MANs), telephone networks (e.g., Public Switched Telephone Networks (PSTNs)), private networks, self-organizing networks, intranets, the Internet, fiber-optic networks, etc., and / or combinations of these or other types of networks.

[0030] Figure 1 The number and layout of devices and networks shown are provided as an example. In reality, with... Figure 1 Compared to the equipment and / or network shown, there may be additional equipment and / or networks, fewer equipment and / or networks, different equipment and / or networks, or equipment and / or networks with different arrangements. Furthermore, Figure 1 The two or more devices shown can be implemented within a single device, or Figure 1 The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, a group of devices in environment 100 (e.g., one or more devices) can perform one or more functions described as being performed by another group of devices in environment 100.

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

[0032] Bus 210 includes components that allow communication between parts of device 200. Processor 220 is implemented in hardware, firmware, or a combination of hardware and software. Processor 220 is a Central Processing Unit (CPU), Graphics Processing Unit (GPU), Accelerated Processing Unit (APU), microprocessor, microcontroller, Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), Application-Specific Integrated Circuit (ASIC), or another type of processing unit. In some implementations, processor 220 includes one or more processors that can be programmed to perform functions. Memory 230 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by processor 220.

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

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

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

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

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

[0038] Figure 2 The number and arrangement of the components shown are provided as an example. In reality, with... Figure 2 Compared to the components shown, device 200 may include more components, fewer components, different components, or components arranged differently. Additionally or alternatively, a group of components of device 200 (e.g., one or more components) may perform one or more functions described as being performed by another group of components of device 200.

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

[0040] The term "5GMSd client" can refer to the following UE function: This UE function includes at least a media session processor and a 5G media streaming player for downlink streaming, and can be accessed through a clearly defined interface / API. The term "5GMSu client" can refer to the initiator of a 5GMSu service that can be accessed through a clearly defined interface / API. The term "5GMSu media streamer" can refer to the following UE function: This UE function enables uplink delivery of streaming media content to the application server (AS) function of the 5GMS application provider, and interacts with both the 5GMSu-aware application for media capture and subsequent streaming, and the media session processor for media session control.

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

[0042] A configuration session can refer to a data structure provided by a 5GMSd application provider at the interface (M1d), whose configuration is associated with a set of 5GMSd features related to 5GMSd-aware applications. A 5GMSd media player can refer to a UE function that enables playback and presentation of media based on media playback items and exposes basic controls such as play, pause, search, and stop to 5GMSd-aware applications. Server access information can refer to a set of parameters and addresses (including 5GMSd AF and 5GMSd AS addresses) required to activate reception of a streaming session. Service and content discovery can refer to the functions and procedures provided by the 5GMSd application provider to the 5GMSd-aware application, enabling end users to discover available streaming services and content products and select specific services or content items for access. Service announcements can refer to procedures executed between the 5GMSd-aware application and the 5GMSd application provider that enable the 5GMSd-aware application to directly obtain 5GMS service access information or obtain 5GMS service access information by referencing such information.

[0043] Third-party player can refer to the following part of the application: this part uses the API to utilize selected 5GMSd functions to play back media content. Third-party uplink streamer can refer to the following part of the application: this part uses the API to utilize selected 5GMSu functions to capture and stream media content.

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

[0045] 5GMSu AF 306 and 5GMSu AS 305 can be Data Network (DN) functions 307. Functions in a Trusted DN can be trusted by the operator's network. Therefore, an AF in a Trusted DN can communicate directly with all 5G core functions. Functions in an External DN can only communicate with 5G core functions via Link 320 through NEF 308.

[0046] Media architecture 300 can connect the internal functions of UE 303 and related network functions for 5G media uplink streaming. Therefore, media architecture 300 can include many functions. For example, the 5GMSu client 304 on UE 303 can be the initiator of 5GMSu services accessible via an interface / API. 5GMSu client 304 can include two sub-functions: a media session processor 309 and a media streamer 310. The media session processor 309 can communicate with the 5GMSu AF 306 to establish, control, and support the delivery of media sessions. The media session processor 309 can expose APIs that can be used by the 5GMSu-aware application 302. The media streamer 310 can communicate with the 5GMSu AS 305 to stream media content and provide services to the 5GMSu-aware application 302 for media capture and streaming, as well as provide services to the media session processor 309 for media session control. The 5GMSu-aware application 302 can control the 5GMSu client 304 by implementing external application or content service provider-specific logic and enabling the establishment of media sessions. For example, the 5GMSu AS 305 can host 5G media functions and can be implemented as a content delivery network (CDN). The 5GMSu application provider 301 can be an external application or content-specific media function that uses 5GMSu to stream media from the 5GMSu-aware application 302, such as media storage, consumption, transcoding, and redistribution. The 5GMSu AF 306 can provide various control functions to the media session processor 309 on the UE 303 and / or to 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.

[0047] Media architecture 300 may include many different interfaces. For example, link 321 may be associated with M1u, which may be a 5GMSu provisioning API opened by 5GMSu AF 306 to configure the use of media architecture 300 and obtain feedback. Link 322 may be associated with M2u, which may be a 5GMSu publishing API opened by 5GMSu AS 305 and used when a 5GMSu AS 305 in a trusted DN (e.g., DN 307) is selected to receive content for streaming services. Link 323 may be associated with M3u, which may be an internal API for exchanging information about content hosted on a 5GMSu AS 305 in a trusted DN such as DN 307. Link 324 may be associated with M4u, which may be a media uplink streaming API opened by 5GMSu AS 323 to media streamer 310 for streaming media content. Link 325 may be associated with M5u, which may be a media session processing API exposed by 5GMSu AF 305 to the media session processor for media session processing, control, and assistance—including appropriate security mechanisms such as authorization and authentication. Link 326 may be associated with M6u, which may be a UE 303 media session processing API exposed by media session processor 309 to 5GMSu-aware application 302 to utilize 5GMSu functionality. Link 327 may be associated with M7u, which may be a UE media streamer API exposed by media streamer 310 to 5GMSu-aware application 302 and media session processor 309 to utilize media streamer 310. Link 328 may be associated with M8u, which may be an application API used for exchanging information between 5GMSu-aware application 302 and 5GMSu application provider 301 to, for example, provide service access information to 5GMSu-aware application 302. UE 303 can also be implemented in a self-contained manner, making interfaces M6u 326 and M7u 327 closed.

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

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

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

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

[0052] Figure 5 This is a diagram of a media system 500 for uplink-to-downlink streaming according to an embodiment. System 500 includes a first UE 502, a second UE 508, a trusted DN 516, and an external DN 528. The first UE 502 includes a 5GMSu client 504 and a 5GMSu-aware application 506. The second UE 508 includes a 5GMSd client 510 and a 5GMSd-aware application 512. The trusted DN 516 includes 5GMSd AF 518, 5GMSd 520, 5GMSu 522, and 5GMSu AF 524. The external DN 528 includes a 5GMS application provider 530.

[0053] 5GMSu client 504 connects to 5GMSu AF 524 via M5u interface 550 and to 5GMSu AS 522 via M4u interface 522. 5GMSu sensing application 506 connects to 5GMS application provider 530 via M8u interface 558. 5GMSd client 510 connects to 5GMSd AS 520 via M4d interface 554 and to 5GMSd AF 518 via M5d interface 556. 5GMSd sensing application 512 connects to 5GMS application provider 530 via M8d interface 560.

[0054] The 5GMSd AF 518 connects to the 5GMSd AS 520 via the M3d interface 562, to the 5GMSuAF 524 via the I1 interface 570, to the PCF 526 via the N5 interface 567, and to the 5GMS application provider 530 via the M1d interface 572. The 5GMSd AS 520 connects to the 5GMSu AS 522 via the I2 interface 564. The 5GMSu AS 522 connects to the 5GMSu AF 524 via the M3u interface 566. The 5GMSu AF 524 connects to the PCF 526 via the N5 interface 568 and to the 5GMS application provider 530 via the M1u interface 574. The 5GMS application provider 530 can connect via... Figure 5 The diagram shows how uplink and downlink streaming connections are used to establish a session for streaming content from one user to other users.

[0055] Figure 6 This is a diagram illustrating the operational flow for uplink and downlink streaming in a 5G network according to an implementation method. This operational flow utilizes, for example, 5GMSu AF 602, 5GMSu AS 604, 5GMSd AF 606, 5GMSd AS 608, and 5GMS application provider 610.

[0056] In operation 620, the 5GMS application provider 610 uses, for example, interface M1d to send a request to 5GMSd AF 606 to create a content hosting configuration template. This request may include requests for I2 addresses and supported protocols.

[0057] In operation 622, 5GMSd AF 606 uses, for example, interface M3d to request resources from 5GMSd AS 608.

[0058] In operation 624, the 5GMS application provider 610 receives an acknowledgment including a content hosting configuration template sent from 5GMSd AF 606. The content hosting configuration template may include information about I2 addresses and protocols in its ingest configuration fields.

[0059] In operation 626, other configuration calls can be executed.

[0060] In operation 628, the 5GMS application provider 610 uses, for example, the M1u interface to send a request to the 5GMS AF 602 to create a second content hosting configuration template. This request includes the I2 address and supported protocols. The I2 address and supported protocols can be included in the downlink ingestion configuration field.

[0061] In operation 630, 5GMSu AF 602 uses, for example, the M3u interface to request resources from 5GMSu AS 604 and provides I2 information to 5GMSu AS 604.

[0062] In operation 632, the 5GMS application provider 610 receives confirmation from 5GMSu AF 602 regarding the creation of a content hosting configuration template.

[0063] like Figure 6 As shown, downlink content hosting configuration tables are created in operations 620, 622, and 624, and uplink content hosting configuration tables are created in operations 628, 630, and 632. The order of these operations can be interchanged based on connectivity requirements. For example, operations 628, 630, and 632 can be performed first, followed by operations 620, 622, and 624.

[0064] In the disclosed method of connecting a 5GMSu AS to a 5GMSd AS as a virtual application provider, the 5GMSu AS can be considered the application provider for the 5GMSd AS, and vice versa. Therefore, the protocols and addresses between the two ASs can be exchanged through the application provider.

[0065] In the first example, a pull is performed by 5GMSd AS 608 from 5GMSu AS 604. In this example, operations 628, 630, and 632 can be performed first, where application provider 610 does not request protocol information. Instead, 5GMS application provider 610 requests the Uniform Resource Locator (URL) address of 5GMSu AS 604 from which to pull content. Then, operations 620, 622, and 624 are performed, where 5GMS application provider 610 uses the protocol to request 5GMSd AS 608 to pull content from 5GMSu AS 604 using the URL address.

[0066] In the second example, a push is performed from 5GMSu AS 604 to 5GMSd AS 608. In this example, operations 620, 622, and 624 can be performed first, where application provider 610 does not request protocol information. Instead, 5GMS application provider 610 requests the URL address of 5GMSd AS 608 to which content is to be pushed. Then, operations 628, 630, and 632 are performed, where 5GMS application provider 610 uses the protocol to request 5GMSd AS 608 to push content from 5GMSu AS 604 using the URL address.

[0067] Table 1 provides an example of the usage of the IngestConfiguration field without protocol information.

[0068] Table 1

[0069]

[0070]

[0071] Table 2 provides an example of the usage of the EgestConfiguration field without protocol information.

[0072] Table 2

[0073]

[0074] The addressed AS URL can be made available to the application provider. Therefore, the URL address can be encrypted before being provided to the application provider. Then, the 5GMSu AS and 5GMSd AS can have a mechanism for exchanging decryption keys. Alternatively, a unique identifier can be provided to the application provider instead of the URL address. Then, the 5GMSu AS and 5GMSd AS can identify the internal address of the AS from the unique identifier or have a method to find the internal address of the AS from the unique identifier.

[0075] Using proprietary 5G network protocols can also lack flexibility. To send proprietary 5G network signaling via signals, a Uniform Resource Identifier (URI) string can be used. This URI string is unique to the specific protocol used by the 5G network and can only be detected by trusted network entities (such as 5GMS AS). Since the protocol may require additional configuration parameters, a resource URL describing the protocol-specific configuration parameters can be provided.

[0076] Table 3 shows additional example usage of the IngestConfiguration field.

[0077] Table 3

[0078]

[0079]

[0080] Table 4 shows additional example usage of the EgestConfiguration field.

[0081] Table 4

[0082]

[0083] Figure 7 This is a diagram illustrating the operational flow for uplink and downlink streaming in a 5G network according to an implementation method. The operational flow uses, for example, 5GMSu AF 702, 5GMSu AS 704, 5GMSd AF 706, 5GMSd AS 708, and 5GMS application provider 710. In one example, because the content hosting configuration template resource has a unique address and is defined by the provisioning session ID, the following operation can be used instead... Figure 6 The operations within.

[0084] In operation 720, the 5GMS application provider 710 uses, for example, interface M1d to send a request to 5GMSd AF 706 to create a managed configuration template. This request may include requests for I2 addresses and supported protocols.

[0085] In operation 722, 5GMSd AF 706 uses, for example, interface M3d to request resources from 5GMSd AS 708.

[0086] In operation 724, the 5GMS application provider 710 receives an acknowledgment from 5GMSd AF 706 that includes a content hosting configuration template.

[0087] In operation 726, other configuration calls can be executed.

[0088] In operation 728, the 5GMS application provider 710 uses, for example, the M1u interface to send a request to the 5GMSu AF 702 to create a second content hosting configuration template. This request includes a downlink provisioningSessionID. The I2 address and supported protocols can be included in the downlink ingestion configuration field.

[0089] In operation 730, 5GMSu AF 702 uses, for example, the M3u interface to request resources from 5GMSu AS 704 and provides the provisioningSessionID to 5GMSu AS 704.

[0090] In operation 732, the 5GMS application provider 710 receives confirmation from 5GMSu AF 702 regarding the creation of a content hosting configuration template.

[0091] exist Figure 7 In this example, 5GMSu AF 702 can access the downlink content hosting configuration template using the provisioningSessionID and configure 5GMSu AS 704 accordingly. Operations 728 and 730 can be performed before operations 720, 722, and 724. In this example, the uplink provisioningSessionID is provided to 5GMSd AF 706 in operation 722.

[0092] exist Figure 7 In this configuration, the I2 address and protocol are not exposed to application service providers because the internal ingestion configuration of the content hosting configuration template source makes it inaccessible to application service providers. As shown in Table 5, additional fields can be added to the ingestion and exhaust configurations.

[0093] Table 5

[0094]

[0095] In some examples, only the ID of the connected AS is sent, and the protocol is negotiated between the two ASs, as shown in Table 6.

[0096] Table 6

[0097]

[0098] Figure 8This is a diagram of process 800 for uplink and downlink streaming according to an implementation. In operation 802, the system sends a first request to the 5GMS downlink AF via the 5GMS application provider to create a first content hosting configuration template. In operation 804, the system receives the first content hosting configuration template from the 5GMS downlink AF at the 5GMS application provider. In operation 806, the system uses the 5GMS application provider to send a second request to the 5GMS uplink AF to create a second content hosting configuration template, the second request including protocol information. In operation 808, the system receives confirmation from the 5GMS uplink AF at the 5GMS application provider regarding the creation of the second content hosting configuration template.

[0099] although Figure 8 An example block of process 800 is shown, but in some implementations, it differs from... Figure 8 Compared to the blocks depicted, process 800 may include additional blocks, fewer blocks, different blocks, or blocks with different arrangements. Alternatively or concurrently, two or more blocks of process 800 may be executed in parallel.

[0100] Example implementations may include methods for establishing uplink-to-downlink (or downlink-to-uplink) streaming in a 5G network, wherein content is streamed from one user and distributed to other users via streaming, which is possible after content preparation. Uplink and downlink 5G ASs can be established to enable streaming media via a direct connection between the uplink and downlink 5G ASs, wherein this configuration is set using a content preparation template and a content hosting configuration template.

[0101] Application providers can decide how to configure push or pull protocols and provide the addresses of other ASs to push / pull ASs via content hosting configuration templates. Various methods for hiding AS URL addresses from application providers include encryption or using unique IDs. The URL of the AS's ingest / exhaust protocol profile can be provided by the application provider to indicate the protocol and its configuration to other entities that allow 5G network providers to connect to their ASs using their protocols.

[0102] Application providers can provide a downlink configuration ID to the 5GMSd AF server, enabling access to the downlink managed configuration template and the corresponding configuration of the 5GMSd AS. Application providers can exchange an AS ID with another AS, and the two servers can negotiate to determine the protocol and other connectivity information.

[0103] Furthermore, the proposed methods can be implemented by processing circuitry (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-transitory computer-readable medium to perform one or more of the proposed methods.

[0104] The above-mentioned techniques can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media.

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

[0106] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the implementation to the exact forms disclosed. Modifications and variations are possible in light of the foregoing disclosure, or modifications and variations can be derived from practical implementation methods.

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

[0108] Even if combinations of features are defined 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 stated in the claims and / or not disclosed in the specification. Although each dependent claim listed below may directly refer to only one claim, the disclosure of possible implementations includes every dependent claim combined with every other claim in the group of claims.

[0109] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the term “group” is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with “one or more.” The term “one” or similar language is used where only one item is intended. Moreover, as used herein, the terms “have,” “possess,” “contain,” etc., are intended to be open-ended terms. Furthermore, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.”

Claims

1. A method for streaming transmission, characterized in that, The method includes: The 5GMS application provider sends a first request to the 5GMS downlink application function AF to create a first content hosting configuration template. The first content hosting configuration template is received from the 5GMS downlink AF at the 5GMS application provider. The first content hosting configuration template contains the Uniform Resource Locator URL address of the 5GMS downlink application server AS and does not contain protocol information. The 5GMS application provider sends a second request to the 5GMS uplink AF to create a second content hosting configuration template, the second request including the URL address of the 5GMS downlink application server AS; and The 5GMS application provider receives confirmation from the 5GMS uplink AF regarding the creation of the second content hosting configuration template; The content hosting configuration template includes configuration parameters for the output and / or input of media content in the 5G network.

2. The method according to claim 1, characterized in that, The method further includes requesting resources from the 5GMS application server via the 5GMS downlink AF, based on the first request to create the first content hosting configuration template.

3. The method according to claim 1, characterized in that, The method further includes requesting resources from the 5GMS uplink application server via the 5GMS uplink AF, the second request based on creating the second content hosting configuration template, and the protocol information.

4. The method according to claim 1, characterized in that, The protocol information includes the address information of the 5GMS uplink application server.

5. The method according to claim 4, characterized in that, The address information includes an encrypted Uniform Resource Locator (URL) address, which describes protocol-specific configuration parameters.

6. The method according to claim 1, characterized in that, The protocol information includes the downlink configuration session ID.

7. The method according to claim 1, characterized in that, The protocol information includes a Uniform Resource Identifier (URI) string that is unique to the specific protocol used in the 5G network.

8. A device for streaming, comprising: At least one memory is configured to store program code; as well as At least one processor is configured to read the program code and operate according to the instructions of the program code to implement the method as described in any one of claims 1-7.

9. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a device, cause the one or more processors to perform the method as described in any one of claims 1-7.

10. An apparatus for streaming transmission, characterized in that, The device includes: The first request sending module is used to send a first request to the 5GMS downlink application function AF to create a first content hosting configuration template via the 5GMS application provider. A configuration template receiving module is configured to receive the first content hosting configuration template from the 5GMS downlink AF at the 5GMS application provider. The first content hosting configuration template contains the Uniform Resource Locator (URL) address of the 5GMS downlink application server AS and does not contain protocol information. The second request sending module sends a second request to the 5GMS uplink AF to create a second content hosting configuration template through the 5GMS application provider. The second request includes the URL address of the 5GMS downlink application server AS. The confirmation receiving module is used to receive confirmation from the 5GMS uplink AF at the 5GMS application provider regarding the creation of the second content hosting configuration template; The content hosting configuration template includes configuration parameters for the output and / or input of media content in the 5G network.

11. The apparatus according to claim 10, characterized in that, The device further includes a resource request module, used to request resources from the 5GMS application server through the 5GMS downlink AF and based on the first request to create the first content hosting configuration template.

12. The apparatus according to claim 10, characterized in that, The device further includes a resource request module, used to request resources from the 5GMS uplink application server through the 5GMS uplink AF, the second request based on creating the second content hosting configuration template, and the protocol information.

13. The apparatus according to claim 10, characterized in that, The protocol information includes the address information of the 5GMS uplink application server.

14. The apparatus according to claim 13, characterized in that, The address information includes an encrypted Uniform Resource Locator (URL) address, which describes protocol-specific configuration parameters.

15. The apparatus according to claim 10, characterized in that, The protocol information includes the downlink configuration session ID.

16. The apparatus according to claim 10, characterized in that, The protocol information includes a Uniform Resource Identifier (URI) string that is unique to the specific protocol used in the 5G network.

Images