Media streaming method, edge resource processing method, storage medium and device

Abstract

Embodiments of the present application disclose a media streaming method, an edge resource processing method, a storage medium and equipment, the method is applied to a user equipment, comprising: determining an identification target edge application server (EAS) for a 5th generation media stream (5GMS) streaming session and a 5GMS aware application of the user equipment; sending a discovery request to identify at least one available EAS for the streaming session, wherein the discovery request comprises at least one discovery filter, and the at least one discovery filter comprises at least one of the following: a service key performance indicator (KPI), a service area, a service availability plan or a service continuity scenario; receiving a discovery request response, the discovery request response indicating the at least one available EAS satisfying the discovery request; selecting a target EAS from the at least one available EAS; and carrying out media stream communication with the target EAS during the streaming session.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. non-provisional application No. 18 / 127,996, filed March 29, 2023; U.S. provisional application No. 63 / 325,508, filed March 30, 2022; and U.S. provisional application No. 63 / 325,512, filed March 30, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of media streaming, and more particularly to a media streaming method, an edge resource processing method, a storage medium, and a device. Background Technology

[0004] For 5GMS architecture, edge processing is beneficial due to its advantages in terms of latency, response time, bandwidth, and proximity to the user equipment (UE). Therefore, the design needs to address various ways in which clients provide edge services and / or obtain information about edge application servers. Summary of the Invention

[0005] This application provides a media streaming transmission method, an edge resource processing method, a storage medium, and a device, enabling user devices to obtain information about edge application servers and activate and control streaming media sessions.

[0006] On one hand, embodiments of this application provide a media streaming transmission method, which is applied to a user equipment and includes:

[0007] For 5GMS streaming sessions of 5th generation media streams and 5GMS-aware applications of the user equipment, identify the Edge Application Server (EAS).

[0008] Send a discovery request to identify at least one available EAS for the streaming session, wherein the discovery request includes at least one discovery filter, the at least one discovery filter including at least one of the following: service key performance indicators (KPIs), service region, service availability plan, or service continuity scenario;

[0009] Receive a discovery request response, the discovery request response indicating at least one available EAS that satisfies the discovery request;

[0010] Select a target EAS from the at least one available EAS; and,

[0011] Media streaming communication is performed with the target EAS during the streaming session.

[0012] On the other hand, embodiments of this application provide a media streaming transmission method, the method being applied to the 5GMS Application Function (AF) of the 5th generation media streaming network, including:

[0013] Receive edge resource information, wherein the edge resource information is received from the 5GMS application provider via the M1 interface, and create an edge resource configuration for provisioning at least one Edge Application Server (EAS); and

[0014] In response to receiving the edge resource information, service access information is sent to the user equipment via the M5 interface. The service access information indicates the availability of edge resources and includes an EAS discovery template for discovering target EAS for 5GMS streaming sessions.

[0015] On the other hand, embodiments of this application provide an edge resource processing method, which is applied to a 5GMS application provider for 5G media streaming in a data network, including:

[0016] Determine the acquisition list, which includes a list of at least one active Edge Application Server (EAS);

[0017] Send an activated EAS request to the 5GMS Application Function (AF) of the edge data network to request the list; and,

[0018] Receive the list from the 5GMS AF.

[0019] On the other hand, embodiments of this application also provide a non-volatile computer-readable storage medium storing instructions thereon, which, when a computer performs media streaming and edge resource processing, cause the computer to execute the method described in any of the above implementations.

[0020] On the other hand, embodiments of this application provide a computer device including a processor and a memory, wherein the memory stores at least one instruction, which is loaded and executed by the processor to implement the above-described method.

[0021] On the other hand, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the described method.

[0022] As can be seen from the above technical solutions, according to the method provided in the embodiments of this application, in the 5GMS architecture, the user equipment can obtain information about the edge application server (EAS), thereby activating and controlling the streaming media session, making full use of the advantages of edge processing in terms of latency, response time, bandwidth, and proximity processing, and improving the efficiency of 5GMS streaming media transmission. Attached Figure Description

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

[0024] Figure 1 A block diagram of an example configuration of an edge-enabled fifth-generation media streaming (5GMS) system is shown.

[0025] Figure 2 A flowchart of a sample media streaming method executed by a user device is shown.

[0026] Figure 3 A flowchart of an example method for media streaming executed by an edge network is shown.

[0027] Figure 4 A flowchart of another example media streaming method executed by an edge network is shown.

[0028] Figure 5 A flowchart is shown of an example method for edge resource processing performed by a 5GMS application provider.

[0029] Figure 6 A flowchart is shown of an example method for edge resource processing performed by 5GMS Application Function (AF).

[0030] Figure 7 A flowchart is shown for another example method of edge resource processing performed by a 5GMS application provider.

[0031] Figure 8 A flowchart of another example method for edge resource processing performed by 5GMS AF is shown.

[0032] Figure 9 A block diagram of an example computer device is shown. Detailed Implementation

[0033] Figure 1This is a block diagram of an example configuration of an edge-enabled fifth-generation media streaming (5GMS) system 100. A 5GMS system is a collection or component including at least one application function (AF), at least one application server (AS), and interfaces from a 5GMS architecture that supports or is configured to perform downlink media streaming services for mobile network operators (MNOs) and third parties, as well as uplink media streaming services for MNOs and third parties. An edge-enabled 5GMS system has the functionality and architecture of a 5GMS system and further supports or is configured to perform edge processing (e.g., media processing in an edge data network (DN)). The term "edge" refers to a location at or relatively close to the user. Accordingly, edge processing (or edge computing) refers to computer processing performed by at least one computing device considered to be located at or near the user equipment.

[0034] exist Figure 1 In the example configuration, the edge-enabled 5GMS system 100 includes user equipment 102, data network (DN) 104, and edge DN 106. A user equipment or device, or multiple (e.g., a network) electronic devices or devices, are capable of communicating over the network. User equipment may include, or be referred to as, a user terminal, user terminal equipment, or user equipment (UE). Additionally, user equipment may be, or includes, mobile devices (such as mobile phones, smartphones, smartwatches, tablets, laptops, vehicles, or other vessels (human-, motor-, or engine-driven, such as cars, airplanes, trains, ships, or bicycles as non-limiting examples) or fixed or stationary devices (such as desktop computers or other computing devices that are typically stationary for extended periods, such as electrical appliances, other relatively heavy devices including those for the Internet of Things (IoT), or computing devices used in commercial or industrial environments as non-limiting examples).

[0035] Additionally, DN 104 and edge DN 106 may each include one or more computing devices configured to communicate with user equipment 102 via signaling. At least some of the signaling used in the communication may be characterized as downlink or uplink. As used in embodiments of this application, the term downlink refers to the direction of transmission from the network (e.g., DN or edge DN) to the user equipment. Accordingly, the network is the source of information or content (e.g., media) transmitted and / or included in the transmission, and the user equipment is the consumer of the information or content, or acts as a consumer device. In this context, the network transmits and the user equipment receives downlink transmissions. Furthermore, as used in embodiments of this application, the term uplink refers to the direction of transmission from the user equipment to the network (e.g., DN or edge DN). Accordingly, the user equipment is the source of information or content (e.g., media) transmitted and / or included in the transmission, and the network is the consumer of the information or content, or acts as a consumer device. In this context, the user equipment transmits and the network receives uplink transmissions.

[0036] for Figure 1 In an edge-enabled 5GMS system 100, user equipment 102, DN 104, and edge DN 106 can be configured to establish at least one media session and stream media during that at least one media session. For at least some configurations, user equipment 102, DN 104, and edge DN 106 can perform media streaming and associated functions to establish media streams and media according to at least one 5GMS technical specification, standard, and / or protocol (e.g., 3GPP Technical Specification (TS) 26.501).

[0037] Alternatively or additionally, each of user equipment 102, DN 104, and edge DN 106 may include at least one component or module to enable communication of media streams and / or the establishment of media streams and media sessions, such as according to the 5GMS specification. Such components are collectively referred to as 5GMS components in this embodiment. Figure 1 The configuration shown includes 5GMS components such as a 5GMS application provider 108, a 5GMS-aware application 110, a 5GMS client 112, a media session processor 114, a media stream processor 116, a 5GMS application function (AF) 118, and a 5GMS application server (AS) 120. In other configurations, 5GMS components may include... Figure 1The number of components may be more or less as shown. Furthermore, as described in further detail below, the 5GMS components can be configured to communicate with each other via or through at least one interface M. Unless otherwise explicitly stated, each of the 5GMS components can be configured to communicate in both the uplink and downlink directions, and each of the interfaces M can handle communication in both the uplink and downlink directions. For at least some configurations, at least one of the 5GMS components and / or at least one of the interfaces M can be divided into a downlink portion handling downlink functionality and an uplink portion handling uplink functionality. For simplicity, the separate downlink and uplink portions are not shown in the diagram. Figure 1 It is specified separately or mentioned separately in the embodiments of this application.

[0038] The 5GMS application provider 108 is a module of DN 104 that uses 5GMS for streaming media services and supplies or provides the 5GMS-aware application 110 to the user equipment 106. The 5GMS application provider 108 can execute, initiate, and / or establish a provisioning session to configure 5GMS features for the 5GMS-aware application 110. Alternatively or additionally, the 5GMS application provider 108 can provide functions and / or procedures used by the 5GMS-aware application 110, enabling the user equipment 106 to discover available streaming media services and content products and select specific services or content items for access. Alternatively or additionally, the 5GMS application provider 108 can execute service announcements that enable the 5GMS-aware application 110 to obtain 5GMS service access information. Alternatively or additionally, the 5GMS application provider 108 uses 5GMS downlink (5GMSd) and / or 5GMS uplink (5GMSu) functions for downlink streaming media services and / or uplink streaming media services, respectively. Alternatively or alternatively, the 5GMS application provider 108 has content-specific media functions, such as media creation, encoding, and formatting, which use the 5GM5 interface to stream media to and / or stream media from the 5GMS sensing application 110.

[0039] The 5GMS sensing application 110 is a module of the user equipment 102, which includes service logic for at least one 5GMS application service and participates in the delivery of downlink and / or uplink 5GMS services.

[0040] The 5GMS client 112 is a module dedicated to the user equipment 102 for 5GMS, providing interfaces and / or application programming interfaces (APIs) to modules within the user equipment 102 to communicate with each other and / or with modules or other components outside the user equipment 102 according to 5GMS. For example... Figure 1In some configurations shown, the 5GMS client 112 may include a media session processor 114 and a media stream processor 116, although other configurations where one or both of the media session processor 114 or the media stream processor 116 are separate from the 5GMS client 112 are also possible. In other configurations, the user equipment 102 may include the media session processor 114 and the media stream processor 116 without necessarily having a 5GMS client 112.

[0041] The media session processor 114 is a module of the user equipment 102 that communicates with the 5GMS Application Function (AF) to establish, control, and / or support media communication and / or delivery during a media session. For at least some configurations, the media session processor 114 may perform additional functions such as consumption and quality of experience (QoE) metric collection and reporting. Furthermore, the media session processor 114 may provide network assistance, such as for downlink streaming transmission and / or by providing bitrate recommendations and / or estimates. Additionally or optionally, for at least some configurations, the media session processor 114 may expose at least one API used by the 5GMS-aware application 110.

[0042] Media stream processor 116 is a module of user equipment 102 that communicates with a 5GMS application server (AS) to execute downlink and / or uplink streaming of media content. Media stream processor 116 may also provide services for media capture and uplink streaming to 5GMS-aware application 110, and services for media session control to media session processor 114. Furthermore, for at least some configurations, media stream processor 116 may be configured with a media player that processes media content streaming, and / or may provide at least one API to 5GMS-aware application 110 for media playback, and / or provide at least one API to media session processor 114 for media session control.

[0043] Edge DN 104 is a local data network including at least one computing device that supports and / or includes an architecture configured to enable edge applications and / or perform edge computing or processing. Edge DN 106 may include at least one 5GMS Application Function (AF) 118 and / or at least one Application Server (AS) 120. Figure 1 In the example configuration, the edge DN 106 includes one 5GMS AF 118 and two AS 120(1), 120(2). Other configurations with at least one 5GMS AF 118 and / or at least one 5GMS AS 120 are also possible.

[0044] The 5GMS AF 118 is a module that provides control functions to the media session processor 114 of the user equipment 102 and / or the 5GMS application provider 108 of the data network 102. For at least some configurations, the 5GMS AF 118 can relay or initiate requests for different policy or charging function (PCF) processing.

[0045] Furthermore, the 5GMS AS 120 is an application server dedicated to 5G media streaming and hosts 5G media functions. The 5GMS AS 120 can communicate with the media stream processor 116 to stream media content. Alternatively, the 5GMS AS 120 can perform content hosting, including but not limited to fetching media content from the 5GMS application provider 108 and caching the media content to reduce duplicate content fetching.

[0046] Furthermore, the edge-enabled 5GMS system 100 may include multiple interfaces or APIs used by 5GMS components to communicate with each other. For example... Figure 1 As shown, each Mi (where i is an integer) can be used between two corresponding Mis in the 5GMS component.

[0047] M1 is used to provide data structures during provisioning sessions from 5GMS application provider 108 to 5GMS AF, whereby the 5GMS AF is used to configure the characteristics of 5GMS-aware application 110. The M1 interface enables 5GMS application provider 108 to provision the use of edge-enabled 5GMS system 100 for downlink and uplink media streams and to obtain feedback. Alternatively, 5GMS application provider 108 can use the M1 interface to provide resources in edge DN 106 for 5GMS-aware application 110, for example, by configuring edge processing resource templates. For at least some configurations, 5GMS application provider 108 can configure the following via the M1 interface: at least one condition for activating edge processing, such as a service descriptor, application identifier, or geographic location of user equipment 102; selection of client-driven or AF-driven management; EAS profile information for each EAS 124 serving an application, such as service key performance indicators (KPIs), geographic location, and service continuity support; and / or application context relocation tolerances and requirements.

[0048] The M2 interface is the interface between 5GMS 108 and 5GMS AS 120. 5GMS AS 120 uses this interface to retrieve media content from 5GMS application provider 108.

[0049] The M3 interface is the interface between the 5GMS AF 118 and the 5GMS AS 120, which exchange information about the content hosted on the 5GMS AS 120. The M3 interface can also be used to allow the selection of one of several 5GMS AS 120s for a media session.

[0050] The M4 interface is the interface between the 5GMS AS 120 and the media stream processor 116. The M4 interface is used to communicate at least one media stream of media content (in the uplink and / or downlink direction) between the 5GMS AS 120 and the media stream processor 116.

[0051] The M5 interface is the interface between the 5GMS AF 118 and the media session processor 114, used to exchange information for processing, controlling, reporting, and assisting media sessions. The 5GMS AF 118 and the media session processor 114 can also use the M5 interface to implement at least one security, authorization, and / or authentication mechanism for media sessions, and / or report QoE metrics. Alternatively, the 5GMS AF 118 can transmit service access information to the media session processor 114 via the M5 interface to share configuration information regarding edge processing. Alternatively, the 5GMS AF 118 can use the M5 interface to transmit consumption report and / or metric report configuration information, which is provided via the M1 interface and passed by the 5GMS AF 118 to the 5GMS client 112.

[0052] The M6 ​​interface is an interface between the media session processor 114 and the media stream processor 116, and / or between the media session processor 114 and the 5GMS-aware application 110, for communication between two or more of the 5GMS-aware application 110, the media session processor 114, and the media stream processor 116. The media session processor 114 and / or the media stream processor 116 can use the M6 ​​interface to configure the 5GMS-enabled 5GMS-aware application 110, or to enable the 5GMS-aware application 110 to utilize 5GMS functionality. Alternatively, the M6 ​​interface can be used to configure 5GMS-related data reporting for the 5GMS-aware application 110.

[0053] The M7 interface is the interface between the media session processor 114 and the media stream processor 116, and between the media stream processor 116 and the 5GMS-aware application 110. The M7 interface allows the media session processor 114 and / or the 5GMS-aware application 110 to utilize the media player of the media stream processor 116, and / or to configure the QoE metrics and / or the set of metric measurement logs to be measured and recorded by the user equipment 106. Additionally or alternatively, the M7 interface can be used to configure, activate, and / or deactivate media capture, media encoding, and / or media upstream client functions.

[0054] The M8 interface is the interface between the 5GMS application provider 108 and the 5GMS awareness application 110. In any of the various configurations, as a non-limiting example, the 5GMS application provider 108 can use the M8 interface to directly provide various information to the 5GMS awareness application 110, including service access information, remote control commands, and service announcement information.

[0055] In addition, as mentioned above, Figure 1 The 5GMS system 100 is edge-enabled and / or capable of performing edge processing to execute 5G media streams. The 5GMS system 100 can support the edge by being configured with edge components that provide edge computing or processing capabilities to at least one of the 5GMS components. In this respect, each of the 5GMS AF 118 and 5GMS AS 120 can be an edge-enabled component and / or configured to perform edge processing, as indicated as part of the edge DN 106. Additionally, the user equipment 102 can be edge-enabled, at least by being able to communicate with the edge-enabled 5GMS 118 and the edge-enabled 5GMS AS 120 for media streaming. The 5GMS AF 118 can be an edge-enabled component at least by including a first type of edge component called an Edge Enabled Server (EES) 122. Furthermore, each 5GMS AS 120 can be an edge-enabled component by including a second type of edge component called an Edge Application Server (EAS) 124. Additionally, user equipment 102 can be an edge-enabled component by including third and fourth types of edge components, referred to as edge-enabled client (EEC) 126 and / or application client 128, respectively. The edge components may also include an edge configuration server (ECS) 130. The edge components can communicate with each other according to at least one specification, standard, and / or protocol (e.g., 3GPP TS 23.558).

[0056] The EES 122 supports or is configured to perform functions supporting the operation of at least one EAS 124 and EEC 126, including supplying configuration information to the EEC 126 and / or allowing the exchange of application data services with at least one EAS 124. Furthermore, for at least some embodiments, the EES 122 may perform additional functions, such as communication with the core network (…). Figure 1 The ability to interact with (not shown) EEC 126 to access network functions, perform context passing with EEC 126, support the external exposure of network and service capabilities to at least one EAS, and register functions (including registration, update, and deregistration of EEC 126 and EAS 124, and / or trigger EAS instantiation on demand, as a non-limiting example. EES 122 may also perform other functions.

[0057] Additionally, EAS 124 is configured to connect to User Equipment 102 to utilize services from 5GMS-aware applications with edge computing capabilities. Furthermore, EAS 124 can consume core network capabilities, for example, by directly invoking core network function APIs via the edge enable layer, via EES 122, and / or by invoking core network capabilities through capability exposure functions. Alternatively, EAS 124 can expose its service APIs to other EAS 124s, such as by providing domain functions through API support. Alternatively, EAS 124 can consume EAS service APIs exposed by other EASs, such as by supporting API caller functions. EAS 124 can also perform other functions or actions.

[0058] Additionally, EEC 126 is a module of user equipment 102, configured to retrieve configuration information to enable the exchange of application data services with EAS 124. Furthermore, EEC 126 can be configured to discover available EAS 124s in edge DN 106. Alternatively or additionally, EEC 126 can be configured to detect mobility events of user equipment 106. For example... Figure 1 In at least some of the configurations shown, the EEC 126 may be part of or a component of the media session processor 114 of the user equipment 102, although other configurations in which the EEC 126 is a component separate from the media session processor 114 are also possible.

[0059] Additionally, the application client (AC) 128 is a module that locates and / or connects to at least one user equipment 102 of EAS 124. For example, AC 128 can determine the connection to EAS 124 and determine the most suitable needs for serving the 5GMS-aware application 110. For example... Figure 1As shown in at least some of the configurations, AC 128 may be part of or a component of the 5GMS Sensing Application 110, although other configurations in which AC 128 is a component separate from the 5GMS Sensing Application 110 are also possible.

[0060] Additionally, ECS 130 is a module that provides support functions for EEC 126 to connect to EES 122. For example, ECS 130 can provide edge configuration information to EEC 126. For at least some configurations, the edge configuration information may include at least one of the following: information that allows EEC 126 to distinguish multiple EES 126s or information that establishes a connection with at least one EES 122. In some configurations, ECS 130 may also support the registration, updating, and / or deregistration of EES 122s, and / or the ability to interact with the core network to access network functions. Other functions of ECS 130 are also possible. For example... Figure 1 In at least some of the configurations shown, ECS 130 is a separate component from each of User Equipment 102, DN 104, and Edge DN 106, although other configurations in which ECS 130 is a component of User Equipment 102, DN 104, or Edge DN 106 are also possible.

[0061] Additionally, similar to the "M" interface used by 5GMS components, edge components can communicate with each other via multiple edge interfaces or APIs. For example... Figure 1 As shown, each edge interface is designated as EDGE-j, where j is an integer.

[0062] EDGE-1 is the interface between EES 122 and EEC 126. EES 122 and EEC 126 can use EDGE-1 to transmit information related to EEC 126 registration and deregistration to EES 122, retrieve and provision EAS configuration information, discover EAS 124 available in edge DN106, and / or service continuity procedures.

[0063] EDGE-3 is the interface between EES 122 and EAS 124. EES 122 and EAS 124 can use EDGE-3 to register EAS 124 with EES 122 (which may include registration availability information such as time constraints and / or location constraints); deregister EAS 124 from ESS; perform target EAS (T-EAS) information discovery to support Application Context Transfer (ACT); provide access to network capability information (such as location information); and / or request the establishment of a data session between AC 128 and EAS 124, including QoS information communication. EDGE-3 can also be used to transmit other information and / or perform other functions.

[0064] EDGE-4 is the interface between EEC 126 and ECS 130. ECS 130 can use EDGE-4 to provide edge configuration information to EEC 126.

[0065] EDGE-5 is the interface between EEC 126 and application client 128.

[0066] EDGE-6 is the interface between EES 122 and ECS 130. EES 122 and ECS 130 can use EDGE-6 to register EES 122 with ECS 130; deregister EES 122 from ECS 130; and / or retrieve target ESS information from ECS 130.

[0067] EDGE-9 is the interface between two EES 122s. The two EES 122s can use EDGE-9 to discover target EAS information to support Application Context Relocation (ACR); perform EEC context relocation procedures; and / or manage the transparent transfer of application context during ACR by the Edge Enable Layer (EEL).

[0068] Other edge interfaces, including Figure 1 The interface between the edge components and the core network, not shown, can be part of the edge-enabled 5GMS system 100 or used in various other example configurations.

[0069] Additionally, as used in embodiments of this application, service access information is a set of at least one parameter and / or address used by user equipment 102 (such as 5GMS client 112) to activate and control streaming media sessions. For at least some example configurations, service access information may also include at least one parameter and / or address used for reporting service, content, and / or QoE metrics. In some configurations, user equipment 102 may receive service access information directly from DN 104. In other configurations, user equipment 102 may receive service access information from 5GMS AF 118 at edge DN 106. With edge enable, the media session processor 114 of user equipment 102 may be configured to use the service access information to determine whether a media streaming session meets the eligibility criteria for requesting edge resources.

[0070] As described above, during provisioning, the 5GMS application provider 108 can request the deployment of edge resources and / or configure information regarding its edge processing requirements for media streaming sessions. During the provisioning session, the 5GMS application provider 108 can use the M1 interface to configure information regarding its edge processing requirements. As part of provisioning, the 5GMS application provider 108 can provision at least one new EAS 124 using the M1 interface. Using the M1 interface, the 5GMS application provider 108 can create, update, and / or retrieve edge resource configuration information. Furthermore, the 5GMS AF 118 can share configuration information regarding edge processing with the media session processor 114. This configuration information can be included as part of the service access information provided by the 5GMS AF 118 to the media session processor 114 via the M5 interface. When the media session processor 114 receives the service access information from the 5GMS AF 118, the EEC 126 can process the configuration information and, consequently, request edge processing for the streaming session from the EES 122 of the 5GMS AF 118 using EDGE-1. Table 1 below lists several parameters (also known as attributes, some or all of which may be included in the service access information provided to the media session processor by 5GMS AF 118).

[0071] Table 1: Example Attributes of Service Access Information

[0072]

[0073]

[0074]

[0075]

[0076]

[0077]

[0078] As shown in the second-to-last row of Table 1, service access information may include an EAS discovery template (easDiscoveryTemplate), which can be a template used for an EAS discovery filter. The EEC 126 uses the EAS discovery filter to discover and select a target EAS 124 from at least one available EAS 124 to serve the user equipment 102 during the media streaming session. Table 2 below lists several parameters or attributes, some or all of which may be included in the EAS discovery template provided by the 5GMS AF 118 to the media session processor 114.

[0079] Table 2: Example Attributes of EAS Discovery Templates

[0080]

[0081]

[0082] In some example configurations, when user equipment 102 determines, for example via its media session processor 114, to conduct media streaming communication during a streaming session, EEC 126 sends an EAS discovery request to EES 122 via an EDGE-1 interface to obtain information about available EAS 124. In response to the EAS discovery request, EEC 126 may receive an EAS discovery request response from EES 122 indicating at least one available EAS 124 and its associated services. EEC 126 may identify or select a target EAS 124 from the EAS discovery request response to enter the streaming session.

[0083] The discovery request sent by EEC 126 may include at least one EAS discovery filter. The EAS discovery filter is a feature that User Equipment 102 expects EAS 124 to have for media streaming sessions. In some configurations, at least one EAS discovery filter may be included in the discovery request as at least one Information Element (IE). For at least some configurations, at least one discovery filter included by EEC 126 in the EAS discovery request may match at least one of the parameters, or at least one discovery filter included by EEC 126 in the EAS discovery request may respond to or depend on EAS discovery template attributes included in the EAS discovery template. Additionally, EEC 126 may populate at least one discovery filter with at least one discovery filter value.

[0084] In response to receiving an EAS discovery request, EES 122 may seek to identify at least one available EAS 124 that satisfies at least one discovery filter included in the EAS discovery template. To determine at least one available EAS 124, EES 122 may perform a discovery filter value matching process, wherein EES 122 attempts to match at least one discovery filter value with the capabilities of at least one registered or candidate EAS 124 known to EES 122. As used in embodiments of this application, a candidate EAS 124 is an EAS 124 that EES 122 knows has registered with EES 122, or an available EAS 124 that EES 122 believes may be capable of satisfying the EAS discovery request. Furthermore, EES 122 may use any of a variety of criteria for discovery filter value matching to evaluate whether a candidate EAS 124 is an available EAS 124 (e.g., satisfies at least one discovery filter value). For example, if a given candidate EAS 124 has all discovery filter values, has at least (or more than) a threshold number of discovery filter values, or has at least one specific predetermined discovery filter value, then EES 122 can identify the given candidate EAS 124 as an available EAS 124. When performing discovery filter value matching, EES 122 can determine discovery filter value matching results indicating zero or at least one available EAS 124 that satisfies the EAS discovery request.

[0085] Additionally, once a discovery filter value match is complete, the EES 122 may generate a discovery request response that includes the discovery filter value match result, indicating zero or at least one available EAS 124 determined from the discovery filter value match. The discovery request response may also indicate the characteristics of each of the at least one available EAS 124. The EES 122 may send the discovery request response to the EEC 126, for example, via the EDGE-1 interface.

[0086] Upon receiving a discovery request response, EEC 126 can select a target EAS 124 from at least one available EAS 124 indicated in the discovery request response. In other words, EEC 126 can select one available EAS 124 as the target EAS 124 from at least one available EAS 124. As described above, the target EAS 124 can be an available EAS 124 that EEC 126 determines as the best or most suitable EAS 124 for transmitting the media stream with the 5GMS-aware application 110 during media streaming. If the discovery request response indicates that multiple available EAS 124s are available, EEC 126 can use any of the various standards to select one available EAS 124 instead of others as the target EAS 124 for the streaming session. When selecting a target EAS 124, at least one component of user equipment 102, such as at least one of media session processor 114, EEC 126, media stream processor 116, 5GMS aware application 110 and / or application client 128, is operable to establish a media session with the target EAS 124, such that the target EAS 124 delivers streaming media to user equipment 102 (such as with media stream processor 116) via an M4 interface during the streaming session.

[0087] Figure 2 This is a flowchart of an example method 200 for media streaming. Method 200 can be performed by a user equipment 102 that wants to stream media during a streaming session (in the downlink and / or uplink direction). In block 202, user equipment 102 can determine and identify a target EAS 124 for the streaming session. Any of the various modules or components of user equipment 102 can make this determination for any of a variety of reasons. For example, media session processor 114 and / or EEC 126 can identify that 5GMS-aware application 110 wants to or needs to transmit media streams during a streaming session, and thus identify the target EAS 124 for the streaming session. As another example, media session processor 114 and / or EEC 126 can identify 5GMS-aware application 110 and / or application client 128, and thus identify the target EAS 124 for 5GMS-aware application 110 and / or application client 128 for a future or upcoming media session involving 5GMS-aware application 110. As another example, the media session processor 114 may receive service access information from the 5GMS AF 118, which may in turn prompt the media session processor 114 and / or the EEC 126 to identify the target EAS 124 for a streaming session with the 5GMS-aware application 110.

[0088] In box 204, user equipment 102 may send a discovery request to edge DN 106 to identify at least one available EAS 124 for a media session. For example, as previously described, EEC 126 may send a discovery request to EES 122, such as via the EDGE-1 interface. The discovery request may include at least one discovery filter and at least one associated discovery filter value, which indicates at least one characteristic that EEC 126 expects the target EAS 124 to have. At least one discovery filter may include at least one attribute of the EAS discovery template listed in Table 2 above. For example, at least one discovery filter may match at least one attribute included in the EAS discovery template of service access information received by media session processor 114 from 5GMS AF 118. EEC 126 may select or determine that all or fewer of the attributes included in the EAS discovery template are at least one discovery filter included in the discovery request.

[0089] For at least some implementations, at least one of the discovery filters may include at least one of the following: a Key Performance Indicator (KPI) (serviceKpi), a service area, a service availability schedule, or service continuity scenarios. As described above, a service KPI is at least one service characteristic that EAS 124 must satisfy. A service area is a list of at least one geographical region for the EAS 124 service. A service availability schedule is the availability schedule of EAS 124. A service continuity scenario is at least one application context relocation scenario that EAS 124 supports for service continuity.

[0090] In block 206, user equipment 102 may receive a discovery request response corresponding to a discovery request, for example, from edge DN 106. For example, ECC 126 may receive the discovery request response from EES 122, for example, via an EDGE-1 interface. The discovery request response may indicate at least one candidate EAS 124 that satisfies the discovery request, for example, by having at least one discovery filter value indicated in the discovery request. In block 208, user equipment 102, such as having EEC 126, may select a target EAS 124 from the at least one candidate EAS 124 indicated in the discovery request response. In block 210, user equipment 102 may perform media streaming (in the downlink and / or uplink direction) during a streaming session with the target EAS 124 selected by user equipment 102 from the discovery request response. For example, media stream processor 116 may perform media streaming with the target EAS 124 via an M4 interface.

[0091] Figure 3 A flowchart of an example method 300 for media streaming performed by edge DN 106 is shown. At block 302, edge DN 106 may receive a discovery request from user equipment 102, the discovery request including at least one discovery filter and at least one associated discovery filter value. For example, the EES 122 of edge network 106 may receive the discovery request from the EEC of user equipment 102, for example, via an EDGE-1 interface. For at least some implementations, at least one discovery filter may match at least one attribute of an EAS discovery template sent by edge network 106 to user equipment 102. Accordingly, for some implementations, at block 302, edge network 106 may send a discovery filter template including at least one attribute, such as a portion of service access information as described above, and may receive a discovery request after and / or in response to sending the discovery filter template. Furthermore, in some example implementations, edge DN 106 may send a discovery filter template, such as a portion of service access information, after and / or in response to receiving configuration information about edge processing from DN 104. For example, the 5GMS AF 118 can receive edge processing configuration information from the 5GMS application provider 108 at DN 104 via the M1 interface during a provisioning session. In response to receiving the configuration information, the 5GMS AF 118 can send service access information to the media session processor 114, such as via the M5 interface. For at least some implementations, the information in the service access information (including at least one attribute included in the EAS discovery template) may depend on the configuration information received from the 5GMS application provider 108.

[0092] Furthermore, for at least some implementations, at least one discovery filter for the discovery request may include at least one attribute included in the EAS discovery template sent by edge DN106 to user equipment 102. At least one attribute may include at least one of the attributes listed in the EAS discovery template in Table 2 above. For at least some of these implementations, at least one of the discovery filters may include at least one of the following: key performance indicators (KPIs) (serviceKpi), service area, service availability schedule, or service continuity scenarios.

[0093] In box 304, in response to receiving a discovery request, edge DN 106 (e.g., via EES 122) may identify at least one available EAS 124 that satisfies the discovery request. As previously described, edge DN 106 may perform discovery value matching to determine which of the at least one candidate EAS 124 satisfies the discovery request and is thus identified as at least one available EAS 124. In box 306, edge DN 106 (e.g., utilizing EES 122) may generate a discovery request response and send it to user equipment 102 (e.g., EEC 126) via the EDGE-1 interface, the discovery request response including the identified at least one available EAS 124. In box 308, one of the at least one available EAS 124 indicated in the discovery request response may, after and / or in response to the discovery request response, transmit streaming media (in the downlink and / or uplink direction) during the streaming session.

[0094] As described above, in some implementations, the EAS discovery template sent by the edge network 106 to the user equipment 102 and / or the discovery request sent by the user equipment 102 to the edge network 106 may include at least one of the following attributes: service KPI, service area, service availability schedule, or service continuity scenarios. These specific implementations may include a combination of at least one of these attributes with at least one additional attribute including at least one of the following: EAS provider ID, EAS type, or at least one EAS feature. Such implementations can be contrasted with other implementations that do not include any of the service KPI, service area, service availability schedule, or service continuity scenarios. For example, such other implementations may include only one or more of the following: EAS provider ID, EAS type, or at least one EAS feature. However, by including at least one of a service KPI, service area, service availability schedule, or service continuity scenario in the discovery request, EES 122 can select an improved group 124 of EASs for participating in streaming sessions with user equipment 102. For example, EES 122 can identify candidate EASs 124 that are not present in a discovery request that does not include these attributes, and / or can avoid identifying certain EASs 124 as candidate EASs 124 because they do not have at least one of the specific service KPIs, specific service areas, specific service availability schedules, or specific service continuity scenarios that EES 126 desires the target EAS 124 to have, rather than being optimal.

[0095] Therefore, in some implementations, the 5GMS-aware application 110 may exemplify EAS 124. EAS 124 is exemplified when it is capable of running an application to stream media with user equipment 102. In a particular implementation, EAS 124 may be instantiated for a streaming session when the 5GMS-aware application is streaming media content during a streaming session, and when EAS 124 is capable of running an application that allows EAS 124 to stream media content with or for the 5GMS-aware application. Edge server requests received via the M1 interface are passed to user equipment (client) 102 via the M5 interface as part of service access information. User equipment (client) 102 may use at least one edge discovery interface (e.g., API) to discover at least one matching available EAS 124.

[0096] As previously described, the 5GMS application provider 108 can provide the new EAS 124 using the M1 interface. Through the M1 interface, the 5GMS application provider 108 can create, update, and / or retrieve edge resource configurations. In some implementations, the 5GMS application provider can do this using the operations listed in Table 3 below.

[0097] Table 3: Operational configurations for edge resources supported by 5GMS application providers

[0098]

[0099]

[0100] Additionally, for at least some implementations, the 5GMS application provider 108 may use at least one attribute of the edge resource configuration listed in Table 4 below.

[0101] Table 4: Edge Resource Configuration Attributes

[0102]

[0103]

[0104] Figure 4This is a flowchart of another example method 400 for media streaming performed by edge DN 106. In block 402, 5GMS AF 118 may receive edge resource information. Edge resource information may be received from 5GMS application provider 108 via the M1 interface. Alternatively or additionally, the edge resource information may be used to create an edge resource configuration. Alternatively or additionally, the edge resource information may be used to provide at least one EAS 124. In block 404, 5GMS AF 118 may send service access information to user equipment 102, such as sending service access information to media session processor 114. As previously described, for service addition or optionally, 5GMS AF 118 may send service access information to user equipment 102 via the M5 interface. Alternatively or additionally, the service access information may include an EAS discovery template, which includes at least one attribute as previously described. In some implementations, this at least one attribute may include one or more of the following: service KPI, service area, service availability plan, or service continuity scenario. Furthermore, in some embodiments, the EES 118 may receive a discovery request in response to sending service access information. The discovery request may include at least one discovery filter, wherein the at least one discovery filter matches at least one attribute included in the EAS discovery template. As previously described, the EES 118 may identify at least one available EAS 124 that satisfies the discovery request and send a discovery response identifying at least one available EAS 124.

[0105] In some implementations, the 5GMS application provider 108 may want to or determine to obtain a list of active EAS 124s. Active EAS 124s are EAS 124s that are already involved in streaming sessions and / or streaming media with user equipment 102. As described above, a target EAS 124 is an EAS that user equipment 102 can select from at least one available EAS 124 identified by edge DN 106. The target EAS 124 is active when user equipment 102 and the target EAS 124 are transmitting media during a streaming session. Depending on the number of active EAS 124s, the list may include zero or at least one active EAS 124 at any different time or under any circumstances. To obtain this list, the 5GMS application provider 108 may send an active EAS request to the 5GMS AF 118 via interface M1, which instructs or commands the 5GMS AF 118 to send or return the list to the 5GMS application provider 108. In some implementations, an activated EAS request may include an EAS identifier (ID) flag (e.g., easldFlag in Table 3). The EAS ID flag may indicate to the 5GMS AF 118 whether to return a list of activated EAS 124. For example, in some implementations, the EAS ID flag may be a first value (such as a Boolean logic "1" or logic "0") indicating to the 5GMS AF 118 to return a list or a second value (such as another Boolean logic "0" or logic "1") not to return a list.

[0106] In response to receiving an activated EAS request, the 5GMS AF 118 can retrieve a list of activated EAS 124 and, for example, return or send this list to the 5GMS application provider 108 via the M1 interface. For at least some implementations, the list may include the EAS ID (e.g., easld in Table 3) of the activated EAS 124 to indicate the activated EAS 124.

[0107] In some implementations, an activated EAS request may be part of an edge resource configuration request. For example, an edge resource configuration request may instruct or direct 5GMS AF 118 to retrieve an edge resource configuration and send the retrieved edge resource configuration to 5GMS application provider 108. The edge resource configuration request may include at least one of the following attributes from Table 4: edgeResourcesConfigurationID, edgeManagementMode, eligibilityCriteria, EASRequirements, or EASRelocationRequirements. The edge resource configuration request may also include an EAS ID flag indicating whether a list of active EAS 124 with edge resource configurations is included, or whether the 5GMS AF 118 returns the edge resource configuration to 5GMS application provider 108 as part of the edge resource configuration. Upon receiving an edge resource configuration request, 5GMS AF 118 may check the EAS ID flag. If the EAS ID flag indicates that a list of active EAS 124s should be returned (e.g., by using it as the first value), the 5GMS AF 118 can retrieve the list of active EAS 124s, including the list of active EAS 124s with the remaining edge resource configurations, and return the edge resource configurations with the list of active EAS 124s to the 5GMS application provider 108.

[0108] Alternatively or concurrently, in some embodiments, the activated EAS request and / or EAS ID flag may instruct or direct the 5GMS AF 118 to retrieve a list of activated EAS 124 during an edge resource configuration retrieval operation. That is, regardless of whether the activated EAS request and / or EAS ID flag is part of or included in the edge resource configuration request, the activated EAS request and / or EAS ID flag may instruct the 5GMS AF 118 to retrieve a list of activated EAS 124 during the edge resource configuration retrieval operation. Furthermore, when the 5GMS AF 118 performs an edge resource configuration retrieval operation, the 5GMS AF 118 may retrieve a list of activated EAS 124 as part of the operation.

[0109] Upon receiving a list of active EAS 124s, the 5GMS application provider 108 can perform at least one action associated with and / or using the EAS ID. For example, the 5GMS application provider 108 can determine the health status of a given active EAS 124, such as at least one processing capability used (e.g., central processing unit (CPU) power and / or graphics processing unit (GPU)), network bandwidth used, volatile memory used (e.g., random access memory (RAM)), and / or non-volatile memory used (memory storage devices). Once the EAS ID is known, the 5GMS application provider 108 can use the EAS ID to obtain at least one health status parameter of the active EAS identified by the EAS ID. As another example, the 5GMS application provider 108 can associate an EAS report with a specific EAS 124. For example, as a non-limiting example, the 5GMS application provider 108 may receive reports related to streaming sessions, such as consumption reports and / or QoE reports, including at least one of various parameters and / or statistics related to the streaming session, such as the duration of the streaming session, a portion of the media content transmitted or consumed, popularity statistics, and statistics related to the media content in the uplink and downlink directions. Upon receiving a listed active EAS 124, the 5GMS application provider 108 may use the active EAS ID included in the list to link or associate a given report with the given active EAS 124.

[0110] Additionally, in some embodiments, the 5GMS application provider 108 can obtain the EAS profile of at least one active EAS 124. For at least some of these embodiments, the 5GMS application provider 108 can retrieve at least one active EAS profile from the EES 122. Particularly in these embodiments, the 5GMS application provider 108 can communicate directly with the EES 122 via an interface 132 extending between the 5GMS application provider 108 and the EES 122 to obtain the EAS profile of the active EAS 124. Figure 1 As shown, interface 132 is an interface different from or separate from interface M1. 5GMS application provider 108 can, for example, send an active EAS profile request to EES 122 via interface 132. In response to receiving this request, 5GMS application provider 108 can obtain the EAS profile of at least one active EAS 124 and send or return the EAS profile to 5GMS application provider 108.

[0111] Additionally, in some implementations, the 5GMS application provider 108 may send an activated EAS profile request after receiving, for example, a list of activated EAS 124s from the 5GMS AF118 via the M1 interface. Upon receiving, or in response to receiving, the 5GMS application provider 108 may send an EAS profile request including the list of activated EAS 124s to the EES 122. In some implementations, the list of activated EAS 124s may include the EAS IDs of the activated EAS 124s (e.g., easld in Table 4), as previously described. Accordingly, in response to receiving the EAS IDs of the activated EAS 124s, the 5GMS application provider 108 may include the EAS IDs in the activated EAS profile request it sends to the EES 122. In response, EES 122 can obtain the EAS profile associated with the EAS ID and return these EAS profiles as part of its response to the request for an activated EAS profile to the 5GMS application provider 108.

[0112] In some embodiments, the 5GMS application provider 108 may use at least one EAS profile it receives to evaluate or confirm the allocation of at least one active EAS 124. For example, using the EAS profile, the 5GMS application provider 108 may evaluate whether the active EAS 124 associated with the EAS profile has been correctly allocated or selected for participation in a media session. For example, the allocated EAS 124 may have a set of associated maximum operating parameters, such as maximum CPU power, maximum GPU power, volatile and / or non-volatile memory capacity, and / or maximum bandwidth. In various embodiments, at least one of the maximum operating parameters may be defined by a service KPI. Using the EAS profile of the active EAS 124, the 5GMS application provider 108 may evaluate or confirm whether the actual operating parameters are within the range of the maximum operating parameters, and thus determine whether the active EAS 124 has been appropriately allocated.

[0113] Figure 5This is a flowchart of an example method 500 for edge resource processing. At block 502, the 5GMS application provider 108 may determine to obtain a list or record identifying at least one active EAS 124 in the edge DN 106. At block 504, the 5GMS application provider 108 may send an active EAS request to the 5GMS AF 118. For at least some implementations, the 5GMS application provider 108 may send the active EAS request via the M1 interface. Furthermore, for at least some implementations, the active EAS request may include an EAS identifier (ID) flag indicating to the 5GMS AF 118 whether to return the list of active EAS 124 to the 5GMS application provider 108. Additionally or optionally, for at least some implementations, the active EAS request and / or the EAS ID flag may be part of an edge resource configuration request. At block 506, the 5GMS application provider 108 may receive a response to the active EAS request and / or a list of at least one active EAS 124 associated with the active EAS request. In box 508, 5GMS application provider 108 may determine at least one health status based on or using a list of at least one active EAS 124 as described above, and / or link at least one report about at least one streaming session to at least one active EAS 124.

[0114] Figure 6 This is a flowchart of an example method 600 for edge resource processing. In block 602, the 5GMS AF 118 may receive an active EAS request to obtain a list or record identifying at least one active EAS 124 in the edge DN 106. In block 604, the 5GMS AF 118 may identify the active EAS 124 and indicate or include them in the list of active EAS 124. In block 606, the 5GMS AF may send the list of active EAS 124 to the 5GMS application provider 108. In some implementations, the 5GMS AF 118 may indicate that the active EAS 124 may include its EAS ID in the list.

[0115] Figure 7This is a flowchart of an example method 700 for edge resource processing. At block 702, the 5GMS application provider 108 may determine the EAS profile for the active EAS 124. At block 704, the 5GMS application provider 108 may generate and / or send an active EAS profile request to obtain the EAS profile. In some embodiments, particularly in these embodiments, the 5GMS application provider 108 sends the active EAS profile request to the EES 122 via an interface 132 separate from or different from the M1 interface. As explained, the separate interface 132 may extend between the 5GMS application provider 108 and the EES 122. Additionally or alternatively, in some embodiments, the 5GMS application provider may include the EAS ID of the active EAS 124 from which it wishes to receive the EAS profile. At block 706, the 5GMS application provider 108 may receive the EAS configuration of the active EAS 124 in response to the active EAS configuration request. In some embodiments, the 5GMS application provider 108 may receive the EAS profile from the ESS 122. Specifically in these embodiments, the 5GMS application provider 108 can receive an EAS profile via a separate interface 132 between the 5GMS application provider 108 and the EES 122. In block 708, the 5GMS application provider 108 can evaluate or confirm at least one allocation of at least one active EAS 124 based on or using the EAS profile, as previously described.

[0116] Figure 8 This is a flowchart of an example method 800 for edge resource processing. At block 802, EES 122 may receive an active EAS configuration file request. In some embodiments, EES 122 may receive the active EAS configuration file request via an interface 132 that is different from or separate from the M1 interface. At block 804, in response to the receipt of the active EAS configuration file request, EES 122 identifies or retrieves the EAS configuration file. At block 806, EES may send the EAS configuration file of the active EAS 124 to the 5GMS application provider 108. In some embodiments, EES 122 may send the EAS configuration file via a separate interface 132. Additionally or optionally, in some embodiments, the active EAS configuration request may include an EAS ID, and EES 122 may retrieve the EAS configuration of the active EAS identified by these EAS IDs (i.e., the EAS configuration associated with these EAS IDs).

[0117] Other methods for edge resource processing, combining at least one block of two or more of methods 400, 500, 700, and 800, are also possible. For example, in block 704, when the 5GMS application provider 108 generates an active EAS profile request, the 5GMS application provider 108 may include the active EAS 124 that it identifies from the active EAS request response it receives in block 406. For example, the 5GMS application provider 108 may receive a list of EAS IDs for the active EAS 124 and, in turn, include the EAS IDs in the active EAS profile request it sends to EES 122. Other similar methods combining at least one block of methods 500 and 800 may also be performed.

[0118] Additionally, as used in embodiments of this application, the term "module" refers to an electronic device implemented solely in hardware or in a combination of hardware and software, configured to implement or perform at least one function or action. For example, a module may include circuitry configured to execute computer-executable instructions, digital logic circuitry, a processor (e.g., a central processing unit (CPU)) or controller, a memory storing computer-executable instructions configured to be executed by the processor or controller, or any combination thereof.

[0119] Furthermore, the above-described technology can be implemented as computer software that uses computer-readable instructions and is physically stored in at least one computer-readable medium. For example, Figure 9 A computer device 900 is shown that is suitable for implementing certain embodiments of the disclosed subject matter.

[0120] Computer software can be encoded using any suitable machine code or computer language, which can be subject to assembly, compilation, linking or similar mechanisms to create code that includes instructions that can be executed directly or through interpretation, microcode execution or other means by one or more computer central processing units (CPUs), graphics processing units (GPUs), etc.

[0121] The instructions can be executed on various types of computers or their components, including, for example, personal computers, tablets, servers, smartphones, gaming devices, Internet of Things devices, etc.

[0122] Figure 9 The components shown for the computer device 900 are exemplary in nature and are not intended to impose any limitation on the scope or functionality of the computer software used to implement the embodiments of this application. The configuration of the components should also not be construed as having any dependency or requirement on any component or combination thereof shown in the exemplary embodiments of the computer device 900.

[0123] Computer device 900 may include certain human-machine interface input devices. Such human-machine interface input devices may respond to at least one human user through, for example, tactile input (such as keystrokes, swiping, data glove movements), audio input (such as voice, tapping), visual input (such as gestures), and olfactory input (not shown). The human-machine interface device may also be used to capture certain media that are not necessarily directly related to conscious human input, such as audio (such as voice, music, ambient sound), images (such as scanned images, photographic images acquired from still image cameras), and video (such as two-dimensional video, including three-dimensional video, stereoscopic video).

[0124] The input human-machine interface device may include at least one of the following (only one is depicted): keyboard 901, mouse 902, trackpad 903, touch screen 910, data glove (not shown), joystick 905, microphone 906, scanner 907, and camera 908.

[0125] Computer device 900 may also include certain human-machine interface (HMI) output devices. Such HMI output devices can stimulate the senses of at least one human user through, for example, tactile output, sound, light, and smell / taste. These HMI output devices may include tactile output devices (e.g., tactile feedback via touchscreen 910, data gloves (not shown), or joystick 905, but may also include tactile feedback devices not used as input devices), audio output devices (e.g., speakers 909, headphones (not shown)), visual output devices (such as screen 910 including CRT screens, LCD screens, plasma screens, OLED screens, each with or without touchscreen input capability, each with or without tactile feedback capability, some of which are capable of outputting two-dimensional or more than three-dimensional visual output in a manner such as stereoscopic output; virtual reality glasses (not shown), holographic displays, and smoke canisters (not shown)), and printers (not shown).

[0126] Computer device 900 may also include human-accessible storage devices and their associated media, such as optical media including media 921 such as CD / DVDROM / RW 920 with CD / DVD, thumb drives 922, removable hard disks or solid-state drives 923, conventional magnetic media such as magnetic tapes and floppy disks (not shown), devices based on dedicated ROM / ASIC / PLD such as secure Dow chips (not shown), etc.

[0127] Those skilled in the art should also understand that the term "computer-readable medium" as used in connection with the presently disclosed subject matter does not include transmission media, carrier waves, or other volatile signaling.

[0128] Computer device 900 may also include an interface 954 to at least one communication network 955. The network may be, for example, wireless, wired, or optical. The network may also be local, wide area, metropolitan, vehicular, industrial, real-time, latency-tolerant, etc. Examples of networks include local area networks such as Ethernet, wireless LANs, cellular networks including GSM, 3G, 4G, 5G, LTE, etc., TV wired or wireless wide area digital networks including cable television, satellite television, and terrestrial broadcast television, vehicle and industrial networks including CAN bus, etc. Some networks typically require external network interface adapters to connect to certain general-purpose data ports or peripheral buses 949 (e.g., USB ports of computer device 900); other systems are typically integrated into the core of computer device 900 by connecting to system buses as described below (e.g., Ethernet interface to a PC computer device or cellular network interface to a smartphone computer device). Using any of these networks, computer device (900) can communicate with other entities. Such communication can be unidirectional, receive-only (e.g., broadcasting TV), transmit-only (e.g., CANbus to certain CANbus devices), or bidirectional, such as to other computer devices using local or wide area digital networks. Certain protocols and protocol stacks can be used on each of those networks and network interfaces as described above.

[0129] The aforementioned human-machine interface device, human-accessible storage device, and network interface can be attached to the core 940 of the computer device 900.

[0130] Core 940 may include at least one central processing unit (CPU) 941, a graphics processing unit (GPU) 942, a dedicated programmable processing unit in the form of a field-programmable gate area (FPGA) 943, a hardware accelerator 944 for certain tasks, a graphics adapter 950, etc. These devices, along with read-only memory (ROM) 945, random access memory 946, and internal mass storage 947 such as an internal non-user-accessible hard disk drive (SD drive), etc., can be connected via system bus 948. In some computer devices, system bus 948 may be accessed as at least one physical connector to allow expansion by adding CPUs, GPUs, etc. Peripheral devices may be directly connected to core system bus 948 or connected via peripheral bus 949. In one example, screen 910 may be connected to graphics adapter 950. Peripheral bus architectures include PCI, USB, etc.

[0131] The CPU 941, GPU 942, FPGA 943, and accelerator 944 can execute certain instructions, and combinations of these instructions can constitute the aforementioned computer code. This computer code can be stored in ROM 945 or RAM 946. Transitional data can also be stored in RAM 946, while permanent data can be stored, for example, in internal mass storage 947. Fast storage and retrieval of any memory device can be enabled by using a cache memory, which can be closely associated with one or more CPUs 941, GPUs 942, mass storage devices 947, ROM 945, RAM 946, etc.

[0132] Computer-readable media may contain computer code for performing operations of various computer implementations. The media and computer code may be those specifically designed and constructed for the purposes of this application, or they may be of types known and available to those skilled in the art of computer software.

[0133] As a non-limiting example, a computer device having architecture 900, particularly core 940, can provide functionality as a result of a processor (including CPU, GPU, FPGA, accelerator, etc.) executing software contained in at least one tangible computer-readable medium. Such a computer-readable medium can be a medium associated with user-accessible mass storage as described above, and some memory of core 940 having non-volatile properties, such as core-internal mass storage 947 or ROM 945. Software implementing various embodiments of this application can be stored in such a device and executed by core 940. Depending on specific needs, the computer-readable medium may include at least one memory device or chip. The software can cause core 940, particularly the processor therein (including CPU, GPU, FPGA, etc.), to execute a specific process or a specific portion of a specific process described herein, including defining data structures stored in RAM 946 and modifying such data structures according to a software-defined process. Alternatively, the computer device can provide functionality as a result of logical hardwired or otherwise embodied in circuitry (e.g., accelerator 944), which can replace or operate with the software to execute the specific process or a specific portion of a specific process described in embodiments of this application. Where appropriate, references to software may include logic, and vice versa. Where appropriate, references to computer-readable media may include circuitry (such as integrated circuits (ICs)) storing software for execution, circuitry containing logic for execution, or both. This application includes any suitable combination of hardware and software.

[0134] In addition to the features mentioned in each of the independent aspects listed above, some examples may be shown individually or in combination of the optional features mentioned in the dependent aspects and / or disclosed in the description above and shown in the figures.

[0135] While several exemplary embodiments have been described in this application, there are variations, substitutions, and various alternative equivalents that fall within the scope of this application. Therefore, it should be understood that those skilled in the art will be able to design numerous systems and methods that, while not expressly shown or described herein, embody the principles of this application and are therefore within its spirit and scope.

[0136] Appendix A: Acronyms

[0137] 3GPP: Third Generation Partnership Project

[0138] 5GMS: Fifth Generation Media Streaming

[0139] AC: Application Client

[0140] ACR: Application Context Relocation

[0141] ACT: Application Context Transfer

[0142] AF: Application Functionality

[0143] AS: Application Server

[0144] DN: Data Network

[0145] EAS: Edge Application Server

[0146] ECS: Edge Configuration Server

[0147] EEC: Edge-Enabled Clients

[0148] EEL: Edge Enable Layer

[0149] EES: Edge Enabler Server

[0150] KPI: Key Performance Indicators

[0151] UE: User Equipment

Claims

1. A media stream transmission method, characterized in that, The method is applied to a user equipment and includes: For the 5GMS streaming sessions of the 5th generation media stream and the 5GMS-aware applications of the user equipment, identify the target edge application server (EAS). Receive service access information from the edge data network; The service access information is used to determine whether the 5GMS streaming session meets the eligibility criteria for requesting edge resources; When determining that the 5GMS streaming session meets the eligibility criteria for requesting edge resources: Send a discovery request to identify at least one available EAS for the streaming session, wherein the discovery request includes at least one discovery filter, the at least one discovery filter including at least one of the following: service key performance indicators (KPIs), service region, service availability plan, or service continuity scenario; Receive a discovery request response, the discovery request response indicating at least one available EAS that satisfies the discovery request; Select a target EAS from the at least one available EAS; and, Media streaming communication is performed with the target EAS during the streaming session.

2. The method according to claim 1, characterized in that, The method further includes: The service access information includes an EAS discovery template, which includes at least one of the service KPI, the service region, the service availability plan, or the service continuity scenario.

3. The method according to claim 2, characterized in that, The method further includes: The EAS discovery template in response to the service access information includes at least one of the service KPI, the service region, the service availability plan, or the service continuity scenario, and the at least one discovery filter is set to include at least one of the service KPI, the service region, the service availability plan, or the service continuity scenario.

4. A non-transitory computer-readable medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-3.

5. A computer device, characterized in that, It includes a processor and a memory, wherein the memory stores at least one instruction, which is loaded and executed by the processor to implement the method as described in any one of claims 1-3.

Images