WO2021225765A1 - Methods for discovery of media capabilities of 5g edge - Google Patents
Methods for discovery of media capabilities of 5g edge Download PDFInfo
- Publication number
- WO2021225765A1 WO2021225765A1 PCT/US2021/027431 US2021027431W WO2021225765A1 WO 2021225765 A1 WO2021225765 A1 WO 2021225765A1 US 2021027431 W US2021027431 W US 2021027431W WO 2021225765 A1 WO2021225765 A1 WO 2021225765A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- media
- 5gms
- media streaming
- edge
- capabilities
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 103
- 238000012545 processing Methods 0.000 claims abstract description 86
- 230000004044 response Effects 0.000 claims abstract description 33
- 230000006870 function Effects 0.000 claims description 103
- 230000007613 environmental effect Effects 0.000 claims description 6
- 230000008569 process Effects 0.000 description 59
- 239000008186 active pharmaceutical agent Substances 0.000 description 38
- 238000010586 diagram Methods 0.000 description 27
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical group CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 19
- 238000004891 communication Methods 0.000 description 11
- 230000003993 interaction Effects 0.000 description 9
- 238000012546 transfer Methods 0.000 description 4
- 238000000605 extraction Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000002156 mixing Methods 0.000 description 2
- 238000000926 separation method Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 238000007596 consolidation process Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000012805 post-processing Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1059—End-user terminal functionalities specially adapted for real-time communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/75—Media network packet handling
- H04L65/752—Media network packet handling adapting media to network capabilities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1063—Application servers providing network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/21—Server components or server architectures
- H04N21/222—Secondary servers, e.g. proxy server, cable television Head-end
- H04N21/2225—Local VOD servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/633—Control signals issued by server directed to the network components or client
- H04N21/6338—Control signals issued by server directed to the network components or client directed to network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
- H04N21/64723—Monitoring of network processes or resources, e.g. monitoring of network load
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5066—Algorithms for mapping a plurality of inter-dependent sub-tasks onto a plurality of physical CPUs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5072—Grid computing
Definitions
- Embodiments of this disclosure are directed to media processing and streaming methods and systems, more particularly to discovery of network processing capabilities of 5G edge networks by external application servers, which allows the external application servers to learn about the current capabilities of the 5G network before requesting to set up any network-based processing.
- Network and cloud platforms are used to run various applications. However, there is no standard based solution to describe the characteristics of a network or cloud platform or its elements.
- 3rd Generation Partnership Project (3GPP) TS26.501 defines the workflow for external application servers to establish network processing in 5G networks for uplink and downlink streaming applications.
- European Telecommunications Standards Institute (ETSI) Multi-access Edge Computing (MEC) standard defines an architecture for instantiation, running, and managing applications on cloud platforms.
- the current 5G Edge architecture defined in 3GPP TS23.558 only defines the general architecture and discovery of edge server hardware capabilities. It does not address the discovery of edge sever capabilities for media processing, which is more than raw hardware capabilities. It also does not address the environmental characteristics of the edge server.
- the NBMP Source is the entity providing the workflow description to Workflow Manager to create, run, manage and monitor a media workflow. The interaction between NBMP Source and Workflow Manager is through a set of NBMP Operation APIs.
- the source device of media streams establishes an uplink session with an application function/application server (AF/AS) pairs in the network.
- a receiving device also establishes a downlink session with AF/AS to stream/download content from the network.
- AF/AS application function/application server
- edge computing architecture in 5GMSA that allows the deployment of network and edge processing or the split rendering of media streaming using the edge and network resources.
- a method of managing capabilities of a media streaming network using at least one processor includes receiving a capability request for media streaming capabilities of an edge data network (EDN); determining the media streaming capabilities of the EDN; transmitting a capability response based on the determined media streaming capabilities; receiving a media processing workflow request based on the capability response; establishing a media streaming session according to the media processing workflow request; and streaming media content based on the media streaming session.
- EDN edge data network
- a device for managing capabilities of a media streaming network includes at least one memory configured to store program code; and at least one processor configured to read the program code and operate as instructed by the program code, the program code including: first receiving code configured to cause the at least one processor to receive a capability request for media streaming capabilities of an edge data network (EDN); determining code configured to cause the at least one processor to determine the media streaming capabilities of the EDN; first transmitting code configured to cause the at least one processor to transmit a capability response based on the determined media streaming capabilities; second receiving code configured to cause the at least one processor to receive a media processing workflow request based on the capability response; establishing code configured to cause the at least one processor to establish a media streaming session according to the media processing workflow request; and streaming code configured to cause the at least one processor to stream media content based on the media streaming session.
- EDN edge data network
- a non-transitory computer-readable medium storing instructions, the instructions including: one or more instructions that, when executed by one or more processors of a device for managing capabilities of a media streaming network, cause the one or more processors to: receive a capability request for media streaming capabilities of an edge data network (EDN); determine the media streaming capabilities of the EDN; transmit a capability response based on the determined media streaming capabilities; receive a media processing workflow request based on the capability response; establish a media streaming session according to the media processing workflow request; and stream media content based on the media streaming session.
- EDN edge data network
- FIG. 1 is a diagram of an environment in which methods, apparatuses, and systems described herein may be implemented, according to embodiments.
- FIG. 2 is a block diagram of example components of one or more devices of
- FIG. 3 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 4 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 5 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 6 is a block diagram illustrating an example process for network capability discovery, according to embodiments.
- FIG. 7 is a block diagram illustrating an example process for network capability discovery, according to embodiments.
- FIG. 8 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 9 is a block diagram illustrating an example process for network capability discovery, according to embodiments.
- FIG. 10 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 11 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 12 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 13 is a block diagram illustrating an example process for network capability discovery, according to embodiments.
- FIG. 14 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 15 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 16 is a block diagram illustrating an example process for network capability discovery, according to embodiments.
- FIG. 17 is a block diagram illustrating an example process for network capability discovery, according to embodiments.
- FIG. 18 is a block diagram illustrating an example process for network capability discovery, according to embodiments.
- FIG. 19 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 20 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 21 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 22 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 23 is a block diagram of a network architecture for media streaming, according to embodiments.
- FIG. 24 is a flowchart of an example process for managing capabilities of a media streaming network, according to embodiments.
- FIG. 1 is a diagram of an environment 100 in which methods, apparatuses, and systems described herein may be implemented, according to embodiments.
- the environment 100 may include a user device 110, a platform 120, and a network 130.
- Devices of the environment 100 may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.
- the user device 110 includes one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with platform 120.
- 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 radiotelephone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device.
- the user device 110 may receive information from and/or transmit information to the platform 120.
- the platform 120 includes one or more devices as described elsewhere herein.
- the platform 120 may include a cloud server or a group of cloud servers.
- the platform 120 may be designed to be modular such that software components may be swapped in or out depending on a particular need. As such, the platform 120 may be easily and/or quickly reconfigured for different uses.
- the platform 120 may be hosted in a cloud computing environment 122.
- the platform 120 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.
- the cloud computing environment 122 includes an environment that hosts the platform 120.
- the cloud computing environment 122 may provide computation, software, data access, storage, etc. services that do not require end-user (e.g. the user device 110) knowledge of a physical location and configuration of system(s) and/or device(s) that hosts the platform 120.
- the cloud computing environment 122 may include a group of computing resources 124 (referred to collectively as “computing resources 124” and individually as “computing resource 124”).
- the computing resource 124 includes one or more personal computers, workstation computers, server devices, or other types of computation and/or communication devices. In some implementations, the computing resource 124 may host the platform 120.
- the cloud resources may include compute instances executing in the computing resource 124, storage devices provided in the computing resource 124, data transfer devices provided by the computing resource 124, etc. In some implementations, the computing resource 124 may communicate with other computing resources 124 via wired connections, wireless connections, or a combination of wired and wireless connections.
- the computing resource 124 includes a group of cloud resources, such as one or more applications (“APPs”) 124-1, one or more virtual machines (“VMs”) 124-2, virtualized storage (“VSs”) 124-3, one or more hypervisors (“HYPs”) 124-4, or the like.
- APPs applications
- VMs virtual machines
- VSs virtualized storage
- HOPs hypervisors
- the application 124-1 includes one or more software applications that may be provided to or accessed by the user device 110 and/or the platform 120.
- the application 124- 1 may eliminate a need to install and execute the software applications on the user device 110.
- the application 124-1 may include software associated with the platform 120 and/or any other software capable of being provided via the cloud computing environment 122.
- one application 124-1 may send/receive information to/from one or more other applications 124-1, via the virtual machine 124-2.
- the virtual machine 124-2 includes a software implementation of a machine
- the virtual machine 124-2 may be either a system virtual machine or a process virtual machine, depending upon use and degree of correspondence to any real machine by the virtual machine 124-2.
- a system virtual machine may provide a complete system platform that supports execution of a complete operating system (“OS”).
- a process virtual machine may execute a single program, and may support a single process.
- the virtual machine 124-2 may execute on behalf of a user (e.g. the user device 110), and may manage infrastructure of the cloud computing environment 122, such as data management, synchronization, or long-duration data transfers.
- the virtualized storage 124-3 includes one or more storage systems and/or one or more devices that use virtualization techniques within the storage systems or devices of the computing resource 124.
- types of virtualizations may include block virtualization and file virtualization.
- Block virtualization may refer to abstraction (or separation) of logical storage from physical storage so that the storage system may be accessed without regard to physical storage or heterogeneous structure. The separation may permit administrators of the storage system flexibility in how the administrators manage storage for end users.
- File virtualization may eliminate dependencies between data accessed at a file level and a location where files are physically stored. This may enable optimization of storage use, server consolidation, and/or performance of non-disruptive file migrations.
- the hypervisor 124-4 may provide hardware virtualization techniques that allow multiple operating systems (e.g. “guest operating systems”) to execute concurrently on a host computer, such as the computing resource 124.
- the hypervisor 124-4 may present a virtual operating platform to the guest operating systems, and may manage the execution of the guest operating systems. Multiple instances of a variety of operating systems may share virtualized hardware resources.
- the network 130 includes one or more wired and/or wireless networks.
- 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. the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, and/or a combination of these or other types of networks.
- 5G fifth generation
- LTE long-term evolution
- 3G third generation
- CDMA code division multiple access
- PLMN public land mobile network
- LAN local area network
- WAN wide area network
- MAN metropolitan area network
- PSTN Public Switched Telephone Network
- private network e.
- FIG. 1 The number and arrangement of devices and networks shown in FIG. 1 are provided as an example. In practice, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown in FIG. 1. Furthermore, two or more devices shown in FIG. 1 may be implemented within a single device, or a single device shown in FIG. 1 may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g. one or more devices) of the environment 100 may perform one or more functions described as being performed by another set of devices of the environment 100. [0051] FIG. 2 is a block diagram of example components of one or more devices of
- the device 200 may correspond to the user device 110 and/or the platform 120. As shown in FIG. 2, the 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.
- the bus 210 includes a component that permits communication among the 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.
- the processor 220 includes one or more processors capable of being programmed to perform a function.
- 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. a flash memory, a magnetic memory, and/or an optical memory) that stores information and/or instructions for use by the processor 220.
- RAM random access memory
- ROM read only memory
- optical memory e.g. a flash memory, a magnetic memory, and/or
- the storage component 240 stores information and/or software related to the operation and use of the device 200.
- the storage component 240 may include a hard disk (e.g. a magnetic disk, an optical disk, a magneto-optic disk, and/or a solid state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable medium, along with a corresponding drive.
- the input component 250 includes a component that permits the device 200 to receive information, such as via user input (e.g. a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and/or a microphone). Additionally, or alternatively, the input component 250 may include a sensor for sensing information (e.g. a global positioning system (GPS) component, an accelerometer, a gyroscope, and/or an actuator).
- the output component 260 includes a component that provides output information from the device 200 (e.g. a display, a speaker, and/or one or more light-emitting diodes (LEDs)).
- LEDs light-emitting diodes
- 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, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections.
- the communication interface 270 may permit the device 200 to receive information from another device and/or provide information to another device.
- the 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, or the like.
- the device 200 may perform one or more processes described herein. The device 200 may perform these processes in response to the processor 220 executing software instructions stored by a non-transitory computer-readable medium, such as the memory 230 and/or the storage component 240.
- a computer-readable medium is defined herein as a non- transitory memory device.
- a memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.
- Software instructions may be read into the memory 230 and/or the storage component 240 from another computer-readable medium or from another device via the communication interface 270.
- software instructions stored in the memory 230 and/or the storage component 240 may cause the processor 220 to perform one or more processes described herein.
- hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein.
- implementations described herein are not limited to any specific combination of hardware circuitry and software.
- the device 200 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 2. 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.
- FIG. 3 is a diagram of a media architecture 300 for media streaming.
- media architecture 300 may be used for uplink streaming or downlink streaming.
- a 5G media streaming uplink (5GMS) Application Provider 301 may use 5GMS for streaming services.
- 5GMS Application provider 301 may provide a 5GMS Aware Application 302 on the UE 303 to make use of 5GMS Client 304 and network functions using interfaces and APIs defined in 5GMS.
- 5GMS Application Server (AS) may be an AS dedicated to 5G Media Streaming.
- 5GMS Client 304 may be a UE 303 internal function dedicated to 5G Media Streaming.
- 5GMS Application Function (AF) 306 and 5GMS 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 directly communicate with all 5G Core functions.
- Functions in external DNs may only communicate with 5G Core functions via the Network Exposure Function (NEF) 308 using link 320.
- NEF Network Exposure Function
- the media architecture 300 may connect UE 303 internal functions and related network functions for 5G Media Uplink Streaming. Accordingly, media architecture 300 may include a number of functions.
- 5GMS Client 304 on UE 303 may be an originator of 5GMS service that may be accessed through interfaces/ APIs.
- 5GMS Client 304 may include two sub-functions, media session handler (MSH) 309 and media streamer 310.
- MSH 309 may communicate with the 5GMS AF 306 in order to establish, control and support the delivery of a media session.
- the MSH 309 may expose APIs that can be used by the 5GMS Aware Application 302.
- Media Streamer 310 may communicate with 5GMS AS 305 in order to stream the media content and provide a service to the 5GMS Aware Application 302 for media capturing and streaming, and the MSH 309 for media session control.
- 5GMS Aware Application 302 may control 5GMS Client 303 by implementing external application or content service provider specific logic and enabling the establishment of a media session.
- 5GMS AS 305 may host 5G media functions.
- 5GMS Application Provider 301 may be an external application or content specific media functionality, e.g., media storage, consumption, transcoding and redistribution that uses 5GMS to stream media from 5GMS Aware Application 302.
- 5GMS AF 306 may provide various control functions to the MSH 309 on the UE 303 and/or to 5GMS Application Provider 301. 5GMS AF 306 may relay or initiate a request for different Policy or Charging Function (PCF) 311 treatment or interact with other network functions.
- PCF Policy or Charging Function
- Media architecture 300 may include a number of different interfaces.
- link M1 may be a 5GMS Provisioning API exposed by 5GMS AF 306 to provision usage of media architecture 300 and to obtain feedback.
- Link M2 may be a 5GMS Publish API exposed by 5GMS AS 305 and used when 5GMS AS 305 in trusted DN, such as DN 307, is selected to receive content for streaming service.
- Link M3 may be an internal API used to exchange information for content hosting on 5GMS AS 305 within a trusted DN such as DN 307.
- Link M4 may be a Media Uplink Streaming API exposed by 5GMS AS 323 to Media Streamer 310 to stream media content.
- Link M5 may be a Media Session Handling API exposed by 5GMS AF 305 to Media Session Handler for media session handling, control and assistance that also include appropriate security mechanisms e.g. authorization and authentication.
- Link M6 may be a UE 303 Media Session Handling API exposed by MSH 309 to 5GMS Aware Application 302 to make use of 5GMS functions.
- Link M7 may be a UE Media Streamer API exposed by Media Streamer 310 to 5GMS Aware Application 302 and MSH 309 to make use of Media Streamer 310.
- Link M8 may be an Application API which is used for information exchange between 5GMS Aware Application 302 and 5GMS Application Provider 301, for example to provide service access information to the 5GMS Aware Application 302.
- FIG. 4 is a diagram of a 5G edge network architecture 400, according to embodiments.
- Edge Data Network (EDN) 401 is a local Data Network.
- Edge Application Server (EAS) 402 and Edge Enabler Server (EES) 403 are contained within the EDN 401.
- Edge Configuration Server (ECS) 404 provides configurations related to EES 403, including details of EDN 401 hosting EES 403.
- User Equipment (UE) 405 contains Application Client (AC) 406 and Edge Enabler Client (EEC) 407.
- EAS 402, EES 403 and ECS 404 may interact with the 3GPP Core Network 408.
- EES 403 provides supporting functions needed for EAS 402 and EEC 407.
- Functionalities of EES 403 may include: provisioning of configuration information to EEC 407, enabling exchange of application data traffic with EAS; supporting the functionalities of API invoker and API exposing function, for example as specified in 3GPP TS 23.222; interacting with 3GPP Core Network 408 for accessing the capabilities of network functions either directly (e.g. via PCF) or indirectly (e.g.
- SCEF Service Capability Exposure Function
- NEF+NEF Service Capability Exposure Function
- supporting the functionalities of application context transfer supporting external exposure of 3GPP network and service capabilities to EASs 402 over link EDGE-3; supporting the functionalities of registration (i.e., registration, update, and de- registration) for EEC 407 and EAS 402; and supporting the functionalities of triggering EAS 402 instantiation on demand.
- EEC 407 provides supporting functions needed for AC 406. Functionalities of EEC 407 may include: retrieval and provisioning of configuration information to enable the exchange of Application Data Traffic with EAS 402; and discovery of EASs 402 available in the EDN 401.
- ECS 404 provides supporting functions needed for the EEC 407 to connect with an EES 403.
- Functionalities of ECS 404 are: provisioning of Edge configuration information to the EEC 407, for example the information for the EEC 407 to connect to the EES 403 (e.g. service area information applicable to LADN); and the information for establishing a connection with EESs 403 (such as URI); supporting the functionalities of registration (i.e., registration, update, and de-registration) for the EES 403; supporting the functionalities of API invoker and API exposing function as specified in 3GPP TS 23.222; and interacting with 3GPP Core Network 408 for accessing the capabilities of network functions either directly (e.g. PCF) or indirectly (e.g. via SCEF/NEF/SCEF+NEF).
- AC 406 is the application resident in the UE 405 performing the client function.
- EAS 402 is the application server resident in the EDN 401, performing the server functions.
- the AC 406 connects to EAS 402 in order to avail the services of the application with the benefits of Edge Computing. It is possible that the server functions of an application are available only as an EAS 402. However, it is also possible that certain server functions are available both at the edge and in the cloud, as an EAS 402 and an Application Server resident in the cloud respectively.
- the server functions offered by an EAS 402 and its cloud Application Server counterpart may be the same or may differ; if they differ, the Application Data Traffic exchanged with the AC may also be different.
- EAS 402 may consume the 3 GPP Core Network 408 capabilities in different ways, such as: it may invoke 3GPP Core Network 408 function APIs directly, if it is an entity trusted by the 3GPP Core Network 408; it may invoke 3GPP Core Network 408 capabilities through EES 403; and it may invoke the 3GPP Core Network 408 capability through the capability exposure functions i.e. SCEF or NEF.
- Architecture 400 may include a number of different interfaces for enabling edge applications, which may be referred to as reference points.
- link EDGE-1 may be a reference point which enables interactions between the EES 403 and the EEC 407.
- Link EDGE-2 may be a reference point which enables interactions between EES 403 and the 3GPP Core Network 408. It supports: access to 3GPP Core Network 408 functions and APIs for retrieval of network capability information, e.g. via SCEF and NEF APIs as defined in 3 GPP TS 23.501, 3 GPP TS 23.502, 3 GPP TS 29.522, 3 GPP TS 23.682,
- Link EDGE-2 may reuse 3GPP reference points or interfaces of EPS or 5GS considering different deployment models.
- Link EDGE-3 may be a reference point which enables interactions between EES 403 and EASs 402. It supports: registration of EASs 402 with availability information (e.g. time constraints, location constraints); de-registration of EASs 402 from EES 403; discovery of target EAS 402 information to support application context transfer; providing access to network capability information (e.g. location information, Quality of Service (QoS) related information); and requesting the setup of a data session between AC 406 and EAS 402 with a specific QoS.
- availability information e.g. time constraints, location constraints
- de-registration of EASs 402 from EES 403 e.g. discovery of target EAS 402 information to support application context transfer
- providing access to network capability information e.g. location information, Quality of Service (QoS) related information
- QoS Quality of Service
- Link EDGE-4 may be a reference point which enables interactions between ECS 404 and EEC 407. It supports: provisioning of Edge configuration information to the EEC 407.
- Link EDGE-5 may be a reference point which enables interactions between AC and EEC 407.
- Link EDGE-6 may be a reference point which enables interactions between ECS 404 and EES 403. It supports: registration of EES 403 information to ECS 404.
- Link EDGE-7 may be a reference point which enables interactions between EAS 402 and the 3GPP Core Network 408. It supports: access to 3GPP Core Network 408 functions and APIs for retrieval of network capability information, e.g. via SCEF and NEF APIs as defined in 3 GPP TS 23.501, 3 GPP TS 23.502, 3 GPP TS 29.522, 3 GPP TS 23.682,
- Link EDGE-7 may reuse 3 GPP reference points or interfaces of EPS or 5GS considering different deployment models.
- Link EDGE-8 may be a reference point which enables interactions between the ECS 404 and the 3GPP Core Network 408. It supports: a) access to 3GPP Core Network 408 functions and APIs for retrieval of network capability information, e.g. via SCEF and NEF APIs as defined in 3 GPP TS 23.501, 3 GPP TS 23.502, 3 GPP TS 29.522, 3 GPP TS 23.682, 3GPP TS 29.122; and with the ECS 404 deployed within the MNO trust domain (see 3GPP TS 23.501 clause 5.13, 3GPP TS 23.682).
- Link EDGE-8 may reuse 3GPP reference points or interfaces of EPS or 5GS considering different deployment models.
- Embodiments corresponding to FIGS. 5-7 relate to workflows and procedures to discover the capabilities of the 5G network by the external entities in two stages, for example,
- the environmental characteristics including the operating system (OS), version of OS and other parameters
- FIG. 5 illustrates an architecture 500 in which elements from architecture 400 of FIG. 4 are combined with elements from architecture 300 of FIG. 3. In order to avoid unnecessary duplication, redundant description has been omitted.
- media streamer 310 and MSH 309 are included in AC 406, and 5GMS AS 305 and 5GMS 306 are included in EAS 402.
- MSH 309 may communicate with AC 406 through link U1
- 5GMS AS 305 may communicate with 5GMS AF 306 through link N2
- 5GMS AF 306 may communicate with EAS 402 through link N1.
- FIG. 6 illustrates a process 600 which may relate to a call flow for discovering edge data network capabilities.
- Process 600 may be performed using architecture 500, or any other architecture as desired.
- Process 600 may extend the TS23.558 APIs to enable the discovery of media capabilities of the edge data networks (EDNs).
- EDNs edge data networks
- the capabilities discovery is performed by requesting and responding through link U1, link EDGE-7, link N1, and link N2 APIs, and in reverse.
- MSH 309 may send a request for processing capabilities to AC 406 using link U1.
- AC 406 may send a request for processing capabilities to EAS 402 using link EDGE-7.
- EAS 402 may send a request for processing capabilities to 5GMS AF 306 using link N1.
- 5GMS AF 306 may send a request for processing capabilities to 5GMS AS 305 using link N2.
- 5GMS AS 305 may send a response including the processing capabilities to 5GMS AF 306 using linkN2.
- 5GMS AF 306 may send a response including the processing capabilities to EAS 402 using link N1.
- EAS 402 may send a response including the processing capabilities to AC 406 using link EDGE-7.
- AC 406 may send a response including the processing capabilities to MSH 309 using link U1.
- Link EDGE-7 API is defined by TS23.558. To support the capability discovery shown herein, the link EDGE-7 API may be extended. Link U1, link N1, and link N2 may be internal APIs.
- FIG. 7 illustrates a process 700 which may relate to a call flow for discovering edge data network capabilities.
- Process 700 may be performed using architecture 500, or any other architecture as desired.
- Process 700 may use the TS23.558 APIs to discover the hardware capabilities of the edge data network, but use the direct API to discover media-specific capabilities.
- the capabilities discovery is performed by requesting and responding through U1, EDGE-7 at one stage (operations 7010-7040), and through M5, and N2 APIs in the second stage (operations 7050-7080).
- MSH 309 may send a request for processing capabilities to AC 406 using link U1.
- AC 406 may send a request for processing capabilities to EAS 402 using link EDGE-7.
- EAS 402 may send a response including the processing capabilities to AC 406 using link EDGE-7.
- AC 406 may send a response including the processing capabilities to MSH 309 using link U1.
- MSH 309 may send a request for processing capabilities to 5GMS AF 306 using link M5.
- 5GMS AF 306 may send a request for processing capabilities to 5GMS AS 305 using link N2.
- 5GMS AS 305 may send a response including the processing capabilities to 5GMS AF 306 using link N2.
- 5GMS AF 306 may send a response including the processing capabilities to MSH 309 using link M5.
- Link EDGE-7 API is defined by TS23.558, and link M5 is defined in TS26.501. To support the capability discovery shown herein, the link EDGE-7 and link M5 APIs may be extended.
- MSH 309 may discover the hardware capabilities through link U1 and link EDGE-7 APIs, and the media-specific capabilities through link M5 API.
- Table 1 shows extensions for link EDGE-7 API to support media discovery functions according to FIGS. 5-7.
- Table 1 Edge-7 extensions [0097]
- Table 2 shows embodiments of example data extension for link M5 API to support media discovery functions according to FIGS. 5-7.
- Tables 3-6 describe parameters added to link EDGE-7 and link M5 APIs in accordance with FIGS. 5-7.
- Each repository includes a list of supported functions.
- embodiments may provide a method for discovering the 5G network capabilities by the application through 3GPP Edge APIs and a call flow wherein the 5G device gathers the currently available resources from application server including media capabilities, wherein the 3GPP Edge APIs are extended to provide media capabilities of the edge network to the application.
- Embodiments may provide a method for discovering the 5G network capabilities by the application in two stages through 3GPP Edge APIs and then through 3GPP 5GMSA APIs, and a call flow wherein the 5G device gathers the currently available resources from application server including media capabilities, wherein the 3GPP Edge and 5GMSA APIs are extended to provide media capabilities of the edge network to the application.
- Embodiments may provide a method of discovering 5G application server environment parameters, wherein the application can discover information about the 5G Application Server operation system, environment parameters, and related information to run 1st and 3rd party applications, libraries, and functions on the 5G Application Server.
- Embodiments corresponding to FIGS. 8-10 may extend the 5G edge architectures discussed above to allow the following:
- FIG. 8 illustrates an architecture 800 in which elements from architecture 400 of FIG. 4 are combined with elements from architecture 300 of FIG. 3. In order to avoid unnecessary duplication, redundant description has been omitted.
- link EDGE-9 allows communication between EAS 402 and 5GMS AP 301
- link EDGE-10 allows communication between EES 403 and 5GMS AP 301
- link EDGE-11 allows communication between ECS 404 and 5GMS AP 301.
- FIG. 9 illustrates a process 900 which may relate to a call flow for discovering Edge Data Network 401 capabilities.
- Process 900 may be performed using architecture 800, architecture 1000 discussed below, or any other architecture as desired.
- Process 900 may extend the TS23.558 APIs to enable the discovery of media capabilities of the edge data networks by the 5GMS AP 301.
- 5GMS AP 301 may send a request for provisioning to ECS 404 using link EDGE-11.
- ECS 404 provisions and provides a list of EESs 403 to 5GMS AP 301 using link EDGE-11.
- 5GMS AP 301 requests registration from an EES 403 included in the list of EESs 403 using link EDGE- 10.
- EES 403 registers and provides a list and locations of EASs 402 to 5GMS AP 301 using link EDGE-10.
- 5GMS AP 301 may request a service from an EAS 402 included in the list of EASs 402 using link EDGE-9.
- EAS 402 starts running the service and confirms the service to 5GMS AP 301 using link EDGE-9, and 5GMS AP 301 connects to EAS 402 and uses the service [0110]
- FIG. 10 illustrates an architecture 1000 in which elements from architecture 400 of FIG. 4 are combined with elements from architecture 300 of FIG. 3. In order to avoid unnecessary duplication, redundant description has been omitted.
- 5GMS AS 305 and 5GMS AF 306 as well as ECS 404 and EES 403 may be logical entities. All or some of them may be combined when implemented.
- EASs 402 may be multiple entities. From the point of view of 5GMS AS 305, all EAS 402 entities are part of the 5GMS AP 301.
- Link M2 provides the media flow between 5GMS AS 305 and 5GMS AP 301. Because some or all of the application may be run on an EAS 402, 5GMS AS 305 may be connected to the EAS 402 through 5GMS AP 301.
- 5GMS AP 301 may discover the list and location of the EASs 402 directly.
- 5GMS AP 301 may discover the capabilities of EASs 402.
- 5GMS AP 301 may request service(s) from EAS 402 directly and instantiate and use those services.
- 5GMS AP 301 may perform any above functions without going through UE 303.
- architecture 300 may be combined with architecture 400, providing a mechanism to set up media services on edge servers and providing a media flow between 5GMS AS 305 and EAS 402.
- embodiments may provide a method for discovering the EDN 401 capabilities by the 5GMS AP 301 through new APIs and a call flow wherein the 5GMS AS 305 can discover the list of available edge servers, provision for a subset of them, discover the location and capabilities of the provisioned one, discover more details about a specific EAS 402, and then request a service from that server, wherein the currently standardized resources can be used to perform the above operations.
- Embodiments may provide a method of combining 5G edge data network and 5G media data network where the two architectures are combined and control and data flow are arranged such that part of the media application may be run on an EAS 402 and the session can be established using the standard processes of 5G edge networks and 5G media streaming architecture.
- Embodiments corresponding to FIGS. 11-13 may extend the 5G edge architectures discussed above to allow the following:
- FIGS. 11-12 illustrate architecture 1100 and architecture 1200 in which elements from architecture 400 of FIG. 4 are combined with elements from architecture 300 of FIG. 3, and additional elements are added. In order to avoid unnecessary duplication, redundant description has been omitted.
- Edge Discovery Function (EDF) 1101 enables 5GMS AP 301 to discover EASs 402 and their capabilities.
- EDF 1101 is used as the EDF 1101.
- EDGE- 10, EDGE- 11 and EDGE- 12 are EDGE-1, EDGE-4 and EDGE-5 respectively.
- Edge Orchestrator (EO) 1102 may be an orchestration service for requesting running specific apps on the EAS 402.
- EO 1101 may be provided by 5G Network Operator.
- 5GMS AP 301 Provider may include an EO service function.
- Edge Host (EH) 1103 may be a service that manages running specific apps on the EAS 402.
- FIG. 12 shows architecture 1200, which may be an example of architecture 1100 implemented using MEC.
- EDF 1101 is implemented using EEC functionality and link EDGE-1 is used for discovery.
- a MEC System Manager 1203 is used as EO 1101.
- MEC System manager 1203 can be implemented by 5G network operator, or by the 5GMS AP 301.
- the link M1 interface is used as link EDGE-9.
- a MEC Host 1202 is used as EH 1103.
- FIG. 13 illustrates a process 1300 which may relate to a call flow for discovering Edge Data Network capabilities.
- Process 1300 may be performed using architecture 1200, architecture 1300, or any other architecture as desired.
- 5GMS AP 301 may send a request for provisioning to ECS 404 using EDF 1101 and link EDGE-1.
- ECS 404 provisions and provides a list of EESs 403 to 5GMS AP 301 using link EDGE-1.
- 5GMS AP 301 requests registration from an EES 403 included in the list of EESs 403 using link EDGE-4.
- EES 403 registers and provides a list and locations of EASs 402 to 5GMS AP 301 through EDF 1101 using link EDGE-4.
- 5GMS AP 301 may request a service from an EAS 402 included in the list of EASs 402 using EO 1101 and link EDGE-9.
- EAS 402 starts running the service and confirms the service to 5GMS AP 301 using link EDGE-9, and 5GMS AP 301 connects to EAS 402 and uses the service.
- EAS 402 starts an instance of 5GMS AF 306 and 5GMS AS 305, MSH 309 and 5GMS AF 306 and 5GMS AS 305 may set up the media session, and the media streaming may start.
- 5GMS AP 301 may discover the list, location, and capabilities of the EASs 402 directly using the existing edge standard.
- 5GMS AP 301 may discover the EAS 402 capabilities directly using the existing edge standard.
- 5GMS AP 301 may request service(s) from EAS 402 directly and instantiate and use those services using standards such as MEC.
- 5GMS AP 301 may perform any above functions without going through UE 303.
- the appropriate EAS 402 instantiates a single 5GMS AF 306 and 5GMS AS 305 and therefore the media will flow through this EAS 402.
- the same resources that UE 303 uses to communicate with the EDN 401 can be used by the 5GMS AP 301 and no new resources are needed.
- architecture 300 may be combined with architecture 400, providing a mechanism to set up media services on edge servers and providing a media flow between 5GMS AS 305 and EAS 402.
- embodiments may provide a method for discovering the 5G edge data network capabilities by the 5GMS AP 301 through existing APIs using a pseudo client in the application and a call flow wherein the 5GMS AP 301 can discover the list of available edge servers, provision for a subset of them, discover the location and capabilities of the provisioned one, discover more details about a specific edge application server, and then request a service from that server using a standard orchestration solution, wherein the currently standardized resources can be used to perform the above operations.
- Embodiments may provide a method of combining 5G edge data network, 5G media data network, and MEC architecture, where the three architectures are combined and control and data flow are arranged such that part of the media application may be run on an EAS 402 and the session can be established using the standard processes of 5G edge networks and 5G media streaming architecture.
- Embodiments corresponding to FIGS. 14-18 may extend the 5G edge architectures discussed above to include 5G discovery server (DS) 1401 which may include the list of 5GMS AS 305 and, in embodiments, their capabilities.
- Embodiments relating to FIGS. 14-18 may relate to workflows and procedures to discover the associated 5GMS AF 306 locations and the capabilities of their corresponding 5GMS AS 305 by the 5GMS AP301 in two stages:
- FIG. 14 illustrates an architecture 1400 which includes some elements from architecture 300 of FIG. 3, along with an additional element, DS 1401. In order to avoid unnecessary duplication, redundant description has been omitted.
- DS 1401 may be used for the discovery of available 5GMS ASs 305.
- MSH 309 may communicate with discovery server 1401 using link M10
- 5GMS AP 301 may communicate with DS 1401 using link M9.
- the 5GMS AP 301 or an external application server may use the DS 1401 to obtain a list of 5GMS AS 305.
- Each entry in the DS 1401 may include some or all of the following information:
- FIG. 15 illustrates an architecture 1500 which includes some elements from architecture 300 of FIG. 3, along with DS 1401. In order to avoid unnecessary duplication, redundant description has been omitted
- FIGs. 16-18 illustrates processes 1600, 1700, and 1800 which may relate to call flows for discovering network capabilities.
- Process 1600, 1700, and 1800 may be performed using architecture 1400, architecture 1500, or any other architecture as desired.
- Processes 1600, 1700, and 1800 may extend the TS26.501 APIs to enable the discovery of 5G application servers.
- Process 1600 relates to a call flow in which 5GMS AP 301 may discover network capabilities.
- 5GMS AP 301 may send a request for a list of AFs to DS 1401 using link M9.
- DS 1401 may provide the list of available AFs to 5GMS AP 301 using link M9.
- 5GMS AP 301 may send a request for capabilities to 5GMS AF 306 using link M1.
- 5GMS AF 306 may send a request for capabilities to 5GMS AS 305 using link M3.
- 5GMS AS 305 may send a response including the capabilities to 5GMS AF 306 using link M3.
- 5GMS AF 306 may send a response including the capabilities to 5GMS AP 301 using link M1.
- 5GMS Aware Application (AA) 302 included on the UE 303 may discover the network capabilities through 5GMS AP 301, as shown for example in process 1700 of FIG. 17, and through MSH 309, as shown for example in process 1800 of FIG. 18.
- 5GMS AA 302 may send may send a request for a list of AFs to 5GMS AP 301 using link M8.
- 5GMS AP 301 may send a request for a list of AFs to DS 1401 using link M9.
- DS 1401 may provide the list of available AFs to 5GMS AP 301 using link M9.
- 5GMS AP 301 may provide the list of available AFs to 5GMS AA 302 using link M8.
- 5GMS AA 302 may send a request for capabilities to 5GMS AP 301 using link M8.
- 5GMS AP 301 may send a request for capabilities to 5GMS AF 306 using link M8.
- 5GMS AF 306 may send a request for capabilities to 5GMS AS 305 using link M3.
- 5GMS AS 305 may send a response including the capabilities to 5GMS AF 306 using link M3.
- 5GMS AF 306 may send a response including the capabilities to 5GMS AP 301 using link M1.
- 5GMS AP 301 may send a response including the capabilities to 5GMS AA 302 using link M8.
- 5GMS AA 302 may send a request for a list of AFs to MSH 309 using link M6.
- MSH 309 may send a request for a list of AFs to DS 1401 using link M10.
- DS 1401 may provide the list of available AFs to MSH 309 using link M10.
- MSH 309 may provide the list of available AFs to 5GMS AA 302 using link M6.
- 5GMS AA 302 may send a request for capabilities to MSH 309 using link M8.
- MSH 309 may send a request for capabilities to 5GMS AF 306 using link M5.
- 5GMS AF 306 may send a request for capabilities to 5GMS AS 305 using link M3.
- 5GMS AS 305 may send a response including the capabilities to 5GMS AF 306 using link M3.
- 5GMS AF 306 may send a response including the capabilities to MSH 309 using link M5.
- MSH 309 may send a response including the capabilities to 5GMS AA 302 using link M6.
- Table 7 shows information for entries in the DS 1401, according to embodiments:
- Table 8 shows information for application server capabilities, according to embodiments:
- embodiments may provide a method for discovering 5GMS AS 305 by the 5GMS AP 301 through a DS 1401 by which the URL of the 5GMS AF 306 and additional information, including capabilities of the corresponding application servers, may be listed.
- Embodiments may provide a method for discovering the 5GMS AS 305 by 5GMS AA 302 through the 5GMS AS 305 by which the 5GMS AA 302 can discover the available the 5GMS ASs 305 and their capabilities.
- Embodiments may provide a method for discovering the 5GMS AS 305 by 5GMS AA 302 through the MSH 309 by which the 5GMS AA 302 can discover the available 5GMS ASs 305 and their capabilities.
- Embodiments may provide a method of conveying the application server and application function information in the DS 1401, wherein the URL and other information of 5GMS ASs 305 are listed in the DS 1401.
- Embodiments may provide a method of discovering 5GMS AS 305 environment parameters, as well as built-in functions and supported repositories wherein information about the 5GMS AS 305 operation system, environment parameters, and related information to run 1st and 3rd party applications, libraries, and functions on the 5GMS AS 305 can be discovered.
- Embodiments corresponding to FIGS. 19-23 relate to various possible deployment scenarios to use the network and edge processing in 5GMS architecture.
- the use of NBMP standard as a specific case of network and edge processing is also addressed.
- an NBMP system 1900 includes an NBMP source 1910, an NBMP workflow manager 1920, a function repository 1930, one or more media processing entities 1950, a media source 1960, and a media sink 1970.
- the NBMP source 1910 may receive instructions from a third party entity, may communicate with the NBMP workflow manager 1920 via an NBMP workflow API 1992, and may communicate with the function repository 1930 via a function discovery API 1991.
- the NBMP source 1910 may send a workflow description document(s) (WDD) to the NBMP workflow manager 1920, and may read the function description of functions stored in the function repository 1930, the functions being media processing functions stored in memory of the function repository 1930 such as, for example, functions of media decoding, feature point extraction, camera parameter extraction, projection method, seam information extraction, blending, post-processing, and encoding.
- the NBMP source 1910 may include or be implemented by at least one processor and memory that stores code configured to cause the at least processor to perform the functions of the NBMP source 1910.
- the NBMP source 1910 may request the NBMP workflow manager 1920 to create workflow including tasks 1952 to be performed by the one or more media processing entities 1950 by sending the workflow description document, which may include several descriptors, each of which may have several parameters.
- the NBMP source 1910 may select functions stored in the function repository 1930 and send the workflow description document to the NBMP workflow manager 1920 that includes a variety of descriptors for description details such as input and output data, required functions, and requirements for the workflow.
- the workflow description document may include a set of task descriptions and a connection map of inputs and outputs of tasks 1952 to be performed by one or more of the media processing entities 1950.
- the NBMP workflow manager 1920 may create the workflow by instantiating the tasks based on function names and connecting the tasks in accordance with the connection map.
- the NBMP source 1910 may request the NBMP workflow manager 1920 to create workflow by using a set of keywords. For example,
- NBMP source 1910 may send the NBMP workflow manager 1920 the workflow description document that may include a set of keywords that the NBMP workflow manager 1920 may use to find appropriate functions stored in the function repository 1930.
- the NBMP workflow manager 1920 may create the workflow by searching for appropriate functions using the keywords that may be specified in a Processing Descriptor of the workflow description document, and use the other descriptors in the workflow description document to provision tasks and connect them to create the workflow.
- the NBMP workflow manager 1920 may communicate with the function repository 1930 via a function discovery API 1993, which may be a same or different API from the function discovery API 1991, and may communicate with one or more of the media processing entities 1950 via an API 1994 (e.g. an NBMP task API).
- the NBMP workflow manager 1920 may include or be implemented by at least one processor and memory that stores code configured to cause the at least processor to perform the functions of the NBMP workflow manager 1920.
- the NBMP workflow manager 1920 may use the API 1994 to setup, configure, manage, and monitor one or more tasks 1952 of a workflow that is performable by the one or more media processing entities 1950.
- the NBMP workflow manager 1920 may use the API 1994 to update and destroy the tasks 1952.
- the NBMP workflow manager 1920 may send messages, such as requests, to one or more of the media processing entities 1950, wherein each message may have several descriptors, each of which have several parameters.
- the tasks 1952 may each include media processing functions 1954 and configurations 1953 for the media processing functions 1954.
- the NBMP workflow manager 1920 may select the tasks based on the descriptions of the tasks in the workflow description document to search the function repository 1930, via the function discovery API 1993, to find the appropriate functions to run as tasks 1952 for a current workflow. For example, the NBMP workflow manager 1920 may select the tasks based on keywords provided in the workflow description document. After the appropriate functions are identified by using the keywords or the set of task descriptions that is provided by the NBMP source 1910, the NBMP workflow manager 1920 may configure the selected tasks in the workflow by using the API 1994. For example, the NBMP workflow manager 1920 may extract configuration data from information received from the NBMP source, and configure the tasks 1952 based on the configuration data.
- the one or more media processing entities 1950 may be configured to receive media content from the media source 1960, process the media content in accordance with the workflow, that includes tasks 1952, created by the NBMP workflow manager 1920, and output the processed media content to the media sink 1970.
- the one or more media processing entities 1950 may each include or be implemented by at least one processor and memory that stores code configured to cause the at least processor to perform the functions of the media processing entities 1950.
- the media source 1960 may include memory that stores media and may be integrated with or separate from the NBMP source 1910.
- the NBMP workflow manager 1920 may notify the NBMP source 1910 when a workflow is prepared and the media source 1960 may transmit media content to the one or more of the media processing entities 1950 based on the notification that the workflow is prepared.
- the media sink 1970 may include or be implemented by at least one processor and at least one display that is configured to display the media that is processed by the one or more media processing entities 1950.
- messages from the NBMP Source 1910 e.g. a workflow description document for requesting creation of a workflow
- messages from the NBMP workflow manager 1920 to the one or more media processing entities 1950 may include several descriptors, each of which may have several parameters.
- communication between any of the components of the NBMP system 1900 using an API may include several descriptors, each of which may have several parameters.
- FIGS. 20-23 illustrate architectures 2000, 2100, 2200, and 2300 elements from architecture 300 of FIG. 3 are combined with elements from system 1900, and additional elements are added. In order to avoid unnecessary duplication, redundant description has been omitted.
- FIG. 20 illustrates architecture 2000, in which network processing is included in the application server.
- NMBP source 1910, NBMP workflow manager 1920, and one or more media processing entities (MPE) 1950 are located in the 5GMS AP 301.
- MPE media processing entities
- a process for establishing, operation, and tearing down a session may include: 1. 5GMS AA 302 makes a request through M8 to NMBP source 1910.
- NMBP source 1910 builds the Workflow Description (WD) and requests the NMBP source 1910 to instantiate the Workflow.
- NMBP workflow manager 1920 discovers various MPEs 1950 and finds enough number of MPEs 1950 to run the workflow
- NMBP workflow manager 1920 instantiates the workflow.
- NMBP workflow manager 1920 responds to NMBP source 1910 with updated WD.
- NMBP source 1910 responds to 5GMS AA 302 with 5GMS AF 306 and 5GMS AS 305 information.
- 5GMS AA 302 requests MSH 309 to establish the session.
- MSH 309 establishes the session and acknowledges 5GMS AA 302 .
- 5GMS AA 302 start ingesting the content.
- 5GMS AA 302 requests NMBP source 1910 to end the session.
- NMBP source 1910 request NMBP workflow manager 1920 to end the Workflow.
- NMBP workflow manager 1920 acknowledges the stopping of the Workflow.
- NMBP source 1910 acknowledges 5GMS AA 302 the stopping of the workflow.
- 5GMS AA 302 requests MSH 309 to stop the session.
- Table 9 shows the required standard interfaces in this scenario:
- FIG. 21 illustrates architecture 2100, in which NMBP source 1910 and NMBP workflow manager 1920 are included in 5GMS AP 301.
- NMBP source 1910 and NMBP workflow manager 1920 are located in the 5GMS AP 301
- MPEs 1950 are located in 5GMS AS 305.
- a process for establishing, operation, and tearing down a session may include: 1. 5GMS AA 302 makes a request through M8 to Workflow Source (NMBP source 1910).
- NMBP source 1910 builds the Workflow Description (WD) and requests the NMBP workflow manager 1920 to instantiate the Workflow.
- NMBP workflow manager 1920 discovers 5GMS AS 305 with enough number of MPEs 1950 to run the workflow
- NMBP workflow manager 1920 instantiates the workflow through 5GMS AS 305.
- NMBP workflow manager 1920 responds to NMBP source 1910 with updated WD.
- NMBP source 1910 responds to 5GMS AA 302 with 5GMS AF 306 and 5GMS AS 305 information.
- 5GMS AA 302 requests MSH 309 to establish the session.
- MSH 309 establishes the session and acknowledges 5GMS AA 302.
- 5GMS AA 302 start ingesting the content.
- 5GMS AA 302 requests NMBP source 1910 to end the session.
- NMBP source 1910 request NMBP workflow manager 1920 to end the Workflow.
- NMBP workflow manager 1920 request 5GMS AS 305 to stop MPEs 1950.
- NMBP workflow manager 1920 acknowledges the stopping of the Workflow.
- NMBP source 1910 acknowledges 5GMS AA 302 the stopping of the workflow.
- 5GMS AA 302 requests MSH 309 to stop the session.
- Table 10 shows the required standard interfaces in this scenario:
- N2 may be a closed API implemented by the AP-operator agreement.
- FIG. 22 illustrates architecture 2200, in which NMBP workflow manager 1920 and
- MPE 1950 are included in 5GMS AS 305
- 5GMS AA 302 makes a request through M8 to Workflow Source (NMBP source 1910).
- NMBP source 1910 builds the Workflow Description (WD) and discovers 5GMS AS 305 which can perform the media.
- NMBP source 1910 requests the appropriate 5GMS ASs 305 NMBP workflow manager 1920 to instantiate the Workflow.
- NMBP workflow manager 1920 instantiates the workflow inside 5GMS AS 305.
- NMBP workflow manager 1920 responds to NMBP source 1910 with updated WD.
- NMBP source 1910 responds to 5GMS AA 302 with 5GMS AF 306 and 5GMS AS 305 information.
- 5GMS AA 302 requests MSH 309 to establish the session.
- MSH 309 establishes the session and acknowledges 5GMS AA 302.
- 5GMS AA 302 start ingesting the content.
- 5GMS AA 302 requests NMBP source 1910 to end the session.
- NMBP source 1910 request NMBP workflow manager 1920 of 5GMS AS 305 to end the Workflow.
- NMBP workflow manager 1920 acknowledges the stopping of the Workflow.
- NMBP source 1910 acknowledges 5GMS AA 302 the stopping of the workflow.
- 5GMS AA 302 requests MSH 309 to stop the session.
- Table 11 shows the required standard interfaces in this scenario:
- FIG. 23 illustrates architecture 2300, in which NMBP source 1910 is included in MSH 309, and NMBP workflow manager 1920 and MPE 1950 are included in in 5GMS AS 305.
- a process for establishing, operation, and tearing down a session may include: 1. 5GMS AA 302 requests MSH 309 through M6 to start a session
- NMBP source 1910 builds the Workflow Description (WD) and discovers 5GMS AS 305 which can perform the media through M5 or other means.
- MSH 309 s NMBP source 1910 requests the NMBP workflow manager 1920 of the appropriate 5GMS AS 305 to instantiate the Workflow.
- NMBP workflow manager 1920 instantiates the workflow inside 5GMS AS 305.
- NMBP workflow manager 1920 responds to MSH 309 with updated WD.
- MSH 309 responds to 5GMS AA 302 .
- 5GMS AA 302 requests MSH 309 to establish the session.
- MSH 309 establishes the session and acknowledges 5GMS AA 302 .
- 5GMS AA 302 start ingesting the content.
- 5GMS AA 302 requests MSH 309 to end the session.
- MSH 309 s NMBP source 1910 request NMBP workflow manager 1920 of 5GMS AS 305 to end the Workflow.
- NMBP workflow manager 1920 acknowledges the stopping of the Workflow.
- MSH 309 acknowledges 5GMS AA 302 the stopping of the workflow.
- Table 12 shows the required standard interfaces in this scenario:
- Table 12 Workflow Source in MSH 309, NMBP workflow manager 1920, and MPE 1950 in 5GMS AS 305
- N2 may be a closed API implemented by the AP-operator agreement.
- M5 is with the support of NBMP Workflow Manager APIs.
- NMBP workflow manager 1920 and MPE 1950 can be supported in 5GMS AS 305 with the
- NMBP source 1910 is supported in 5GMS AA 302, or all NMBP source 1910, NMBP workflow manager 1920 and MPE 1950 are supported in 5GMS AS 305.
- 5GMS AS 305 pair may exist.
- NMBP source 1910 and/or NMBP workflow manager 1920 must discover the capabilities of multiple 5GMS AF 306 and 5GMS AS 305 pairs for running the network media workflow on the most suitable 5GMS AS 305.
- embodiments may provide a method for deployment of any network or edge-based media processing such as NBMP workflow management in 5GSMA environment wherein 4 different scenarios is considered, including implementing a) Entire network processing modules in Application Server, b) media processing services in 5GMS AS 305 c) workflow manager and media processing services in 5GMS AS 305 , and d) NBMP source 1910 in MSH 309, and both NBMP workflow manager 1920 and MPE 1950 are in 5GMS AS 305.
- any network or edge-based media processing such as NBMP workflow management in 5GSMA environment wherein 4 different scenarios is considered, including implementing a) Entire network processing modules in Application Server, b) media processing services in 5GMS AS 305 c) workflow manager and media processing services in 5GMS AS 305 , and d) NBMP source 1910 in MSH 309, and both NBMP workflow manager 1920 and MPE 1950 are in 5GMS AS 305.
- workflow processing modules may be implemented in a different module of the 5GSM architecture, wherein for each scenario the APIs between network processing and 5GMSA are defined, where APIs are divided to the APIs according to the 3GPP 3GSMA standards, the internal APIs for each module and the private APIs between the service provider and the operator.
- Embodiments may provide methods including separate call flow for the establishment, management, and tears down of Workflow processing and 5GMSAjoint session for each of the four scenarios of method 1, wherein each case’s call flow, a workflow session, and a FLUS session are set up, where appropriate information is exchanged through the APIs defined in method 1 to establish and manage a joint session where the content is up- streamed from the device to the network using 5GMSA and then it is processed in a cloud or edge service using the network workflow processing.
- Embodiments may provide methods for implementing the NBMP standard as the network workflow processing, for deployment with 5GMSA.
- FIG. 24 is a flowchart is an example process 2400 for managing capabilities of a media streaming network. In some implementations, one or more process blocks of FIG.
- 2400 may be performed by one or more elements of any of the systems or architectures discussed above.
- process 2400 may include receiving a capability request for media streaming capabilities of an edge data network (EDN) (block 2402).
- EDN edge data network
- the EDN may correspond to EDN 401 discussed above.
- process 2400 may include determining the media streaming capabilities of the EDN (block 2404). [0188] As further shown in FIG. 24, process 2400 may include transmitting a capability response based on the determined media streaming capabilities (block 2406).
- process 2400 may include receiving a media processing workflow request based on the capability response (block 2408).
- process 2400 may include establishing a media streaming session according to the media processing workflow request (block 2410).
- process 2400 may include streaming media content based on the media streaming session (block 2412).
- the media streaming capabilities relate to at least one of available hardware resources, environmental characteristics of the EDN, a current throughput of an edge server associated with the EDN, an current delay range of the edge server, available media processing function libraries, functional descriptions of one or more functions, and characteristics of the one or more functions.
- the receiving of the capability request may include receiving, by an edge application server (EAS), a first capability request from a media streaming handler of a client device, and the determining of the media streaming capabilities may include transmitting, by the EAS, a second capability request to at least one of a media streaming application function or a media streaming application server included in the EAS.
- EAS edge application server
- the EAS may correspond to EAS 402 discussed above.
- the first capability request may be transmitted using an edge application programming interface (API), and the second capability request is transmitted using a media streaming API.
- API edge application programming interface
- the capability request may be received by an edge configuration server (ECS) from a media streaming application provider (AP).
- ECS edge configuration server
- AP media streaming application provider
- the AP may correspond to 5GMS AP 301 discussed above
- the ECS may correspond to ECS 404 discussed above.
- the determining of the media streaming capabilities may include transmitting, from the ECS to the AP, a list of a plurality of edge enabler servers (EES); receiving, by the ECS from the AP, a registration request for an EES from among the plurality of EESs; and transmitting, from the EES to the AP, a list of a plurality of EASs including the media streaming capabilities.
- EES edge enabler servers
- the EES may correspond to EES 403 discussed above.
- the media processing workflow request may be transmitted from the AP to an EAS from among the plurality of EASs based on the list of the plurality of EASs.
- the list of the plurality of EASs may be transmitted to the AP through an edge discovery function (EDF).
- EDF edge discovery function
- the EDG may correspond to EDF 1101 discussed above.
- the EDF may be included in the AP.
- process 2400 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 24. Additionally, or alternatively, two or more of the blocks of process 2400 may be performed in parallel.
- the example methods according to embodiments of the instant application may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits).
- the one or more processors execute a program that is stored in a non-transitory computer-readable medium to perform one or more of the example methods.
- the techniques described above can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media.
- Embodiments of the present disclosure may be used separately or combined in any order. Further, each of the embodiments (and methods thereof) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program that is stored in a non-transitory computer-readable medium.
- processing circuitry e.g., one or more processors or one or more integrated circuits.
- the one or more processors execute a program that is stored in a non-transitory computer-readable medium.
- the term component is intended to be broadly construed as hardware, firmware, or a combination of hardware and software.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202180005539.4A CN114503091A (en) | 2020-05-07 | 2021-04-15 | Method for discovering 5G edge media ability |
JP2022523298A JP7455204B2 (en) | 2020-05-07 | 2021-04-15 | Method for 5G Edge Media Capability Detection |
EP21799671.9A EP4018332A4 (en) | 2020-05-07 | 2021-04-15 | Methods for discovery of media capabilities of 5g edge |
KR1020227012879A KR20220065822A (en) | 2020-05-07 | 2021-04-15 | Methods for discovery of media capabilities at the 5G edge |
Applications Claiming Priority (12)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202063021411P | 2020-05-07 | 2020-05-07 | |
US63/021,411 | 2020-05-07 | ||
US202063026432P | 2020-05-18 | 2020-05-18 | |
US63/026,432 | 2020-05-18 | ||
US202063052104P | 2020-07-15 | 2020-07-15 | |
US63/052,104 | 2020-07-15 | ||
US202063066692P | 2020-08-17 | 2020-08-17 | |
US63/066,692 | 2020-08-17 | ||
US202063075461P | 2020-09-08 | 2020-09-08 | |
US63/075,461 | 2020-09-08 | ||
US17/213,679 US11902337B2 (en) | 2020-05-07 | 2021-03-26 | Methods for discovery of media capabilities of 5G edge |
US17/213,679 | 2021-03-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021225765A1 true WO2021225765A1 (en) | 2021-11-11 |
Family
ID=78413520
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2021/027431 WO2021225765A1 (en) | 2020-05-07 | 2021-04-15 | Methods for discovery of media capabilities of 5g edge |
Country Status (6)
Country | Link |
---|---|
US (1) | US11902337B2 (en) |
EP (1) | EP4018332A4 (en) |
JP (1) | JP7455204B2 (en) |
KR (1) | KR20220065822A (en) |
CN (1) | CN114503091A (en) |
WO (1) | WO2021225765A1 (en) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11388067B2 (en) * | 2020-03-30 | 2022-07-12 | Tencent America LLC | Systems and methods for network-based media processing (NBMP) for describing capabilities |
CN114747244A (en) * | 2020-10-05 | 2022-07-12 | 三星电子株式会社 | Method and apparatus for providing service to Edge Application Servers (EAS) in an Edge Data Network (EDN) |
US20220109722A1 (en) * | 2020-10-07 | 2022-04-07 | Nokia Technologies Oy | Method and apparatus for dynamic workflow task management |
US11792249B2 (en) * | 2022-02-07 | 2023-10-17 | Tencent America LLC | Event-driven provisioning of new edge servers in 5G media streaming architecture |
US20230353643A1 (en) * | 2022-03-30 | 2023-11-02 | Tencent America LLC | Edge application server discovery and identification of activated edge application servers and associated profiles |
US20230319118A1 (en) * | 2022-03-30 | 2023-10-05 | Tencent America LLC | Method for network-side and client side activation of the edge servers in 5g media streaming architecture |
KR20240004621A (en) * | 2022-03-30 | 2024-01-11 | 텐센트 아메리카 엘엘씨 | Triggering of edge server discovery and instantiation by 5GMS-aware applications |
KR20230155740A (en) * | 2022-05-04 | 2023-11-13 | 삼성전자주식회사 | Method and apparatus for split rendering architecture to support real-time media delivery in a mobile communication system |
US20230362257A1 (en) * | 2022-05-05 | 2023-11-09 | Tencent America LLC | Procedure for discovery of capabilities and performance of 5g edgar devices |
KR20240021529A (en) * | 2022-08-10 | 2024-02-19 | 삼성전자주식회사 | Apparatus and method for provisioning device capavility-based ar content service in wireless system |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080270610A1 (en) * | 2002-07-24 | 2008-10-30 | Kasenna, Inc. | System and metehod for highly scalable real-time and time-based data delivery using server clusters |
US20100198977A1 (en) * | 2006-09-27 | 2010-08-05 | Adobe Systems Incorporated | Automatic live stream trees |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3902011B2 (en) | 2002-01-11 | 2007-04-04 | Kddi株式会社 | Routing method and system |
US8732854B2 (en) * | 2006-11-01 | 2014-05-20 | Time Warner Cable Enterprises Llc | Methods and apparatus for premises content distribution |
US7954131B2 (en) * | 2007-06-13 | 2011-05-31 | Time Warner Cable Inc. | Premises gateway apparatus and methods for use in a content-based network |
US8396055B2 (en) * | 2009-10-20 | 2013-03-12 | Time Warner Cable Inc. | Methods and apparatus for enabling media functionality in a content-based network |
US10419533B2 (en) * | 2010-03-01 | 2019-09-17 | Genghiscomm Holdings, LLC | Edge server selection for device-specific network topologies |
US8806031B1 (en) * | 2010-12-15 | 2014-08-12 | Juniper Networks, Inc. | Systems and methods for automatically detecting network elements |
US9407944B1 (en) * | 2015-05-08 | 2016-08-02 | Istreamplanet Co. | Resource allocation optimization for cloud-based video processing |
US11444850B2 (en) * | 2016-05-02 | 2022-09-13 | Huawei Technologies Co., Ltd. | Method and apparatus for communication network quality of service capability exposure |
CN109451793B (en) * | 2017-06-30 | 2021-11-23 | 北京小米移动软件有限公司 | Method and device for realizing network edge calculation |
US10834198B2 (en) * | 2017-09-28 | 2020-11-10 | International Business Machines Corporation | Edge side dynamic response with context propagation for IoT |
EP3750335A4 (en) * | 2018-06-01 | 2021-08-11 | Samsung Electronics Co., Ltd. | Systems and methods for better resource utilization in 5g networks using enablement layer |
US20210219268A1 (en) * | 2018-08-09 | 2021-07-15 | Convida Wireless, Llc | Resource management for 5g ev2x |
US11683393B2 (en) * | 2019-09-11 | 2023-06-20 | Intel Corporation | Framework for computing in radio access network (RAN) |
WO2021060937A1 (en) * | 2019-09-25 | 2021-04-01 | Samsung Electronics Co., Ltd. | Method and system for distributed discovery and notification for edge computing |
US11563828B2 (en) * | 2019-10-31 | 2023-01-24 | Qualcomm Incorporated | Edge computing platform capability discovery |
US20210136178A1 (en) * | 2019-11-06 | 2021-05-06 | Centurylink Intellectual Property Llc | Predictive resource allocation in an edge computing network utilizing geolocation for orchestration |
KR20210098724A (en) * | 2020-02-03 | 2021-08-11 | 삼성전자주식회사 | Method and apparatus for providing edge computing service |
EP4104425A4 (en) * | 2020-04-01 | 2023-07-12 | Samsung Electronics Co., Ltd. | Electronic device for performing edge computing service and method for the same |
-
2021
- 2021-03-26 US US17/213,679 patent/US11902337B2/en active Active
- 2021-04-15 KR KR1020227012879A patent/KR20220065822A/en not_active Application Discontinuation
- 2021-04-15 EP EP21799671.9A patent/EP4018332A4/en active Pending
- 2021-04-15 JP JP2022523298A patent/JP7455204B2/en active Active
- 2021-04-15 WO PCT/US2021/027431 patent/WO2021225765A1/en unknown
- 2021-04-15 CN CN202180005539.4A patent/CN114503091A/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080270610A1 (en) * | 2002-07-24 | 2008-10-30 | Kasenna, Inc. | System and metehod for highly scalable real-time and time-based data delivery using server clusters |
US20100198977A1 (en) * | 2006-09-27 | 2010-08-05 | Adobe Systems Incorporated | Automatic live stream trees |
Non-Patent Citations (1)
Title |
---|
See also references of EP4018332A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN114503091A (en) | 2022-05-13 |
JP7455204B2 (en) | 2024-03-25 |
EP4018332A4 (en) | 2022-10-19 |
US20210352113A1 (en) | 2021-11-11 |
KR20220065822A (en) | 2022-05-20 |
JP2022553275A (en) | 2022-12-22 |
US11902337B2 (en) | 2024-02-13 |
EP4018332A1 (en) | 2022-06-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11902337B2 (en) | Methods for discovery of media capabilities of 5G edge | |
US11743512B2 (en) | Methods for NBMP deployments through 5G FLUS control | |
US11451869B2 (en) | 5G media streaming network capability discovery and expression | |
CN113542208A (en) | Methods, apparatus and media for media processing and streaming | |
US11956281B2 (en) | Method and apparatus for edge application server discovery or instantiation by application provider to run media streaming and services on 5G networks | |
US20240137393A1 (en) | Methods for discovery of media capabilities of 5g edge | |
CN116250221A (en) | Method and apparatus for contribution reporting for uplink streaming in 5G networks | |
JP2024069394A (en) | Method for detecting media capabilities at 5G edge | |
US20230135864A1 (en) | Method for application context transfer between edge servers in 5g networks | |
CN113472732B (en) | Method, apparatus and storage medium for managing capabilities of a media streaming network | |
US20220369073A1 (en) | Methods for implementing various uplink streaming deployment scenarios in 5g networks | |
US11799937B2 (en) | CMAF content preparation template using NBMP workflow description document format in 5G networks | |
CN115715461A (en) | Method for discovering media service portals for uplink and downlink streaming in 5G networks | |
WO2022211850A1 (en) | Method and apparatus for defining egest configuration and protocols in 5g uplink streaming | |
KR20230162805A (en) | Event-driven provisioning of new edge servers in 5G media streaming architecture |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21799671 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2021799671 Country of ref document: EP Effective date: 20220325 |
|
ENP | Entry into the national phase |
Ref document number: 20227012879 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2022523298 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |