UE-driven enhanced downlink media delivery

Abstract

A method includes transmitting, by a user equipment (UE), a first message to a first apparatus, the first message including at least one metric requirement for at least a first sub- application of a first application including one or more sub-applications. The UE receives a second message from the first apparatus, the second message including an indication of a first application server for providing a first content. The UE establishes a communication session to the first application server based upon the indication, and receives a third message from the first apparatus, the third message including the first content from the first application server.

Description

UE-DRIVEN ENHANCED DOWNLINK MEDIA DELIVERYFIELD

[0001] Various example embodiments relate generally to wireless networks and, more particularly, for a method and apparatus for user equipment (UE)-driven enhanced downlink media delivery.BACKGROUND

[0002] A mobile telecommunication network or cellular network (generally referred to herein as a communication network) enables communications between two or more communication devices, provides communication devices access to a data network, delivers services provides by third-party applications to communication devices, or provides services offered by the communication network to communication devices.

[0003] A communication network and communication devices may operate in accordance with cellular technologies (otherwise referred to as radio access technologies), such as GSM, UTMS, LTE, LTE-A, and NR. Cellular technologies are standardized by various standards organization, such as the Third Generation Partnership Project (3 GPP) or ETSI (European Telecommunications Standards Institute). 3GPP is currently developing standards for 5th generation cellular technologies (generally referred to a 5G or NR standards) and 6thgeneration cellular technologies (generally referred to a 6G standards). Communication networks that operate in accordance with 5G or NR standards are generally referred to as 5G networks and communication networks that operate in accordance with 6G standards are generally referred to as 6G networks.

[0004] A communication network (e.g., a 5G network or a 6G network) includes access networks (e.g., radio access networks) that can communicate wirelessly with one or multiple communication devices by sharing available resources (e.g., bandwidth, transmit power, etc.) of the access network (e.g., radio access network). A communication network can also establish reliable, secure connectivity between communication devices and a core network of the communication network via access networks. A communication network (e.g., a 5G network) may provide enhanced mobile broadband services (e.g., telephony, video, data, short message services messaging services), ultra-reliable low-latency communication services (e.g., XR services), or massive machine type communication services to communication devices.SUMMARY

[0005] In an aspect of the present disclosure, a method includes transmitting, by a user equipment (UE), a first message to a first apparatus, the first message including at least one metric requirement for at least a first sub-application of a first application including one or more subapplications. The UE receives a second message from the first apparatus, the second message including an indication of a first application server for providing a first content. The UE establishes a communication session to the first application server based upon the indication, and receives a third message from the first apparatus, the third message including the first content from the first application server.

[0006] In an aspect of the method, the method includes receiving, by the UE, a request message from the first apparatus requesting the at least one metric requirement for the first sub-application and UE capabilities.

[0007] In an aspect of the method, the method includes receiving, by the UE, from the first apparatus, a configuration information relating to one or more application servers.

[0008] In an aspect of the method, the configuration information includes one or more of an application capability, application version, features, or energy consumption.

[0009] In an aspect of the method, the method includes selecting by the UE, the first application server from among the one or more application servers for receiving content.

[0010] In an aspect of the method, the method includes receiving, by the UE, configuration information from the first apparatus relating to the first application server as a selected server to receive content.

[0011] In an aspect of the method, the first message includes a metric requirement for a second sub-application of the first application.

[0012] In an aspect of the method, the first message includes information indicating the at least one sub-application relating to the first application.

[0013] In an aspect of the method, a metric requirement of a sub-application includes one or more of a sub-application energy related metric, a sub-stream identification, or UE aggregation capabilities.

[0014] In an aspect of the method, the method includes receiving a fourth message including second content from a second application server.

[0015] In an aspect of the method, the third message includes the second content.

[0016] In an aspect of the method, the first application server is a same server currently providing the first content to the UE.

[0017] In an aspect of the method, the first application server is a different server than a server currently providing the first content to the UE.

[0018] In an aspect of the present disclosure, a method includes receiving, by a first apparatus, a first message from a user equipment (UE), the first message including at least one first metric requirement for at least a first sub-application of a first application including one or more subapplications; receiving, by the first apparatus, analytics data from a second apparatus relating to at least one second metric requirement for the first sub-application; performing, by the first apparatus, processing based on the at least one first metric requirement and the at least one second metric requirement; transmitting, by the first apparatus, a request to a first application server for a metric relating to the first application server; receiving, by the first apparatus, a report from the first application server including the metric relating to the first application server; transmitting, by the first apparatus, a second message to the UE, the second message including information relating to the first application server; and transmitting, by the first apparatus, a request for content to the first application server.

[0019] In an aspect of the method, the method includes transmitting, by the first apparatus, a request message to the UE requesting the at least one metric requirement for the first subapplication and UE capabilities.

[0020] In an aspect of the method, the method includes transmitting, by the first apparatus, a configuration information relating to one or more application servers to the UE.

[0021] In an aspect of the method, the method includes modifying, by the first apparatus, an existing session from an application server currently providing content to the UE to the first application server.

[0022] In an aspect of the method, the method includes selecting, by the first apparatus, an application server out of one or more application servers as the first application server.

[0023] In an aspect of the method, the method includes transmitting, by the first apparatus, configuration information relating to the first application server as a selected server to receive content to the UE.

[0024] In an aspect of the method, the first message includes a metric requirement for a second sub-application of the first application.

[0025] In an aspect of the method, the second message includes information relating to a second application server for providing a second content.

[0026] In an aspect of the method, the first application server is an application server having a highest energy efficiency out of a plurality of application servers.

[0027] In an aspect of the method, the method includes determining, by the first apparatus whether an application server is to transmit aggregated or non-aggregated data based upon a UE capability.

[0028] In an aspect of the method, the first apparatus selects the first application server to aggregate data for transmission and for one or more additional application servers transmit their data to the first application server for aggregation.

[0029] In an aspect of the present disclosure, a UE includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, causes the UE at least to perform any of the foregoing methods.

[0030] In an aspect of the present disclosure, an apparatus includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, causes the apparatus at least to perform any of the foregoing methods.

[0031] In an aspect of the present disclosure, a processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform any of the foregoing methods.

[0032] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Some example embodiments will now be described with reference to the accompanying drawings.

[0034] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0035] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0036] FIG. 3 is a diagram of a media session utilizing a UE as a media aggregator, according to one illustrated aspect of the disclosure;

[0037] FIG. 4 is a diagram of a media session utilizing an application server (AS) as a media aggregator, according to one illustrated aspect of the disclosure;

[0038] FIG. 5 is a diagram of an example embodiment of signals and operations among a UE and the network according to one illustrated aspect of the disclosure;

[0039] FIG. 6 is a diagram of an example block diagram of a wireless station or node (e.g., network node (such as gNB), user node or UE, relay node, or other node), according to one illustrated aspect of the present disclosure.DETAILED DESCRIPTION

[0040] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0041] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0042] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE- Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0043] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0044] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0045] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5GNR and embodiments that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0046] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2, which is hereby incorporated by reference herein.

[0047] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0048] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g.:o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC quality of service (QoS) flows; o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0049] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0050] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0051] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en- gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0052] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, or a gNB-DU, or any combination of them. A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 5 below.

[0053] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipmentand one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open-RAN (O- RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0054] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0055] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, XR devices, HMD devices, etc. among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 6. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0056] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0057] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0058] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0059] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0060] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0061] Additional components and functions of the core network 210 may include an application function 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, and operations and management function (0AM) 223.

[0062] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The DN 226 identifies services from service providers, Internet access, and third party services, for example.

[0063] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0064] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0065] The UDM 217 generates authentication vectors for use by the AUSF 211 and ADM 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0066] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The 0AM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0067] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system maynot include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0068] Interactive extended reality (XR) applications necessitate the coordination of at least three or more different (multimedia) sub-streams, namely audio sub-streams (captured using one or more microphones), video sub-streams (captured using one or more cameras) as well as sensor signal sub-streams (captured based on haptic movements, position and location coordinates etc.) to upload, download and / or stream / view a content.

[0069] Accordingly, an interactive XR application may have several sub-applications, which may also be referred to as sub-modules (e.g., modules corresponding to each subapplication) at a user equipment (UE) client side, each sub-module responsible for a particular workflow (e.g, turn-on mic, turn-on camera, capture haptics signals, etc.), all of them related to one protocol data unit (PDU) session (or several PDU sessions within a slice).

[0070] In various embodiments, workflow requests for each sub-module may be multimedia sub-streams related to each sub-module that is sent to an application function (AF) from a Media Session Handler (MSH) present inside the UE client via, for example, an M5 interface, or an RTC-5 interface or a similar interface between the Media session Handler (MSH) of the UE client and the Application Function (AF) Persons of skill in the art may appreciate that other interfaces from the UE side to the Application Function (AF) are possible.

[0071] Conventional architectures for media delivery standardized so far in, for example, 3 GPP SA4 deal with one-to-one relationship with client and servers (e.g., between one UE client and one application server (AS) and one AF). However, this one-to-one relationship may be optimized in the context of XR applications and services for XR devices (e.g., a blind person trying to play an XR game by accessing augmented reality (AR) glasses may not require video streams to be downloaded, since the priority may be haptic traffic and audio traffic, while a deaf person accessing AR glasses may not require audio stream traffic but only video traffic and haptic traffic). In these cases, AS required to deliver content to both the users are not the same, even though the application use case scenario is the same (both players are trying to play the same XR game).

[0072] The downlink media is delivered based on the application requests sent in the uplink direction from the UE client to the AF, which UE then may receive the requested content from more than one AS. In the above context, the following may apply.

[0073] In various embodiments, the number of ASs may not be limited to only one. And therefore, the interaction between the AF and ASs becomes ‘one-to-many’ relationship. The AF, need additional information from UE, to identify and correlate different sub-applications of the same XR application.

[0074] In various embodiments, an AF may desire to map these multimedia sub-streams from the UE to separate ASs to distribute network load across ASs , optimize costs, as well as improve quality of service (QoS), for example. To do so, an AF may desire to choose an AS to satisfy the demand of a particular sub-application requirements and priority within the UE . Additionally, the AF may need to relocate the AS considering different scenarios (e.g. AS load, AS energy consumption, AS current quality of experience (QoE) metrics, etc.). In some deployments, this may include collective relocation. Also, to relocate the sub streams, the AF may identify which all sub streams are related to the same XR application.

[0075] Accordingly, described herein is a method and apparatus for enabling optimized multimedia handling and delivery from multiple multimedia sub-streams, while optimizing end- to-end Quality of Service (QoS) at the network side (AS) and Quality of Experience (QoE) at the UE side. In various embodiments, the methods described herein may apply to AR / VR / XR content handling and interactions, real time communication services (RTC) as well as video streaming and multimedia telephony services which can be delivered by wireless networks (e.g. 5G / 6G networks). However, persons of skill in the art may appreciate that other applications are possible.

[0076] Although further detail is provided below, described herein is a method wherein information about each sub-module workflow requests from the different streams of the UE client is used to select different ASs based on the sub-module workflow requests from the multimedia streams.

[0077] In various embodiments, two different data networks that host two different ASs, which each host a different multimedia content may be accessed. For example, a first AS may host video codecs, while a second AS may host haptic signals. In various embodiments, this access could be via a network slice. An application provider may negotiate with the MNO to setup a network slice. The operator provisions the network slice and provides connectivity services to both the DNsthrough the slice.

[0078] In various embodiments, an AS may be setup in each of the trusted DNs or may have a multi-homing interface through each of the trusted DNs. In order to map the respective submodule workflow requests from the respective multimedia stream, as a first step, the XR Application Provider may deliver service access information through a reference point (e.g., M8d defined in TS 26.501 for Media streaming architecture) to the XR application. The service access information delivered to the XR application may have information about different operation points accessible through each of the DNs. For example, the sub-module workflow requests from the “video streams” from the UE client may utilize an AS (e.g., an AS hosted at the CDN with video media codec processing capabilities but may not satisfy very low delay / latency requirements) which is different from the AS hosting the haptic signals (e.g., an AS hosted at the CDN with very high delay / latency requirements). XR applications requests from the UE client for video related requests may use a PDU session terminating in the video specific AS via the AF, while some other sub-module workflow requests are sent through PDU Sessions terminating in a different AS via the AF.

[0079] In various embodiments, an AS may act as a backup server and be utilized by the UE client if the primary AS is inaccessible or unavailable for any reason. In order to map the respective workflow requests based on particular metrics (for instance the ‘energy consumption’, current network throughput, etc. of that particular sub-application), the application function (AF) may collect those particular metrics (e.g., the energy consumption information) from the UE. For example, the sub-application workflow requests from the “video streams” from the UE client may report a higher energy consumption compared to the energy consumption reported by the subapplication workflow requests from the “haptic streams”.

[0080] While this is done, the AF may also collect the required allowed metrics (for instance energy consumption information, individual QoE, current load) from the individual Application Servers (ASs). Accordingly, individual sub-apps may be mapped based on their collected metrics to individual ASs. For instance, taking energy consumption as a criterion as stated in the above example, in various embodiments, the most energy efficient application server for the highest energy consuming sub-application may be selected. For example, sub-applications requests from the UE client for video streams related requests use the PDU Session terminating in the AS with the most energy efficiency via the AF.

[0081] FIG. 3 is a diagram of a media session 300 utilizing a UE as a media aggregator, according to one illustrated aspect of the disclosure. In various embodiments, various components depicted in FIG. 3 may coincide with similar components described above in FIGS. 1 and 2. Also shown in FIG. 3 is an XR application having at least a first and second sub-application (e.g., video and / or audio sub-applications). The UE 150 depicted in FIG. 3 may include a UE client (e.g., 5GMS client, RTC client, split rendering client), and the UE 150 may apply URSP rules in case of network slicing.

[0082] On the network side, the AF 218 supplies information to a first AS 310a and a second AS 310b. In various embodiments, the first AS 310a may correspond to one application service while the second AS 310b may correspond to an application service.

[0083] In various embodiments, metrics reporting is transmitted by and / or received from the UE 150, AS 310a and AS 310b, while metrics consumption and processing may be performed in the AF 218. The AF 218 may be in 3 GPP domain or non 3 GPP domain.

[0084] As shown in FIG. 3, the UE 150 performs aggregation of the media session handling. In various embodiments, media (e.g., video data, haptic data) may be provided in a single network slice instance X over several PDU sessions. The AS 310a provides first media / data over PDU session #1 and the AS 310b provides second media / data over PDU session #2. The first and second media / data is received by the UE 150 and aggregated for provision to the sub-applications of the XR application.

[0085] FIG. 4 is a diagram of a media session 400 delegating an AS to be the media aggregator, according to one illustrated aspect of the disclosure. In various embodiments, various components depicted in FIG. 4 may coincide with similar components described above in FIGS. 1 and 2. Also shown in FIG. 4 is an XR application having at least a first and second sub-application (e.g., video and / or audio sub-applications). The UE 150 depicted in FIG. 4 may include a UE client (e.g., 5GMS client, RTC client, split rendering client), and the UE 150 may apply URSP rules in case of network slicing.

[0086] On the network side, the AF 218 supplies information to a first AS 310a and a second AS 310b. In various embodiments, the first AS 310a may provide video codecs while the second AS 310b may provide haptics.

[0087] In various embodiments, metrics reporting is transmitted by and / or received from the UE 150, AS 310a and AS 310b, while metrics consumption and processing may be performed in the AF 218. The AF 218 may be in a 3 GPP domain or non 3 GPP domain.

[0088] As shown in FIG. 4, the AS 310a performs aggregation of the media session handling. In various embodiments, media (e.g., video data, haptic data) is provided in a single network slice instance X over a single PDU session since the aggregated traffic is directly sent from the AS to the UE. The AS 310a provides first media / data over PDU session #1 that includes second media / data received from AS 310b. The first and second media / data is aggregated by AS 310a and transmitted over PDU session #1 to the UE 150 for provision to the sub-applications of the XR application.

[0089] In various embodiments, the UE (e.g., UE 150) is enabled to send to the AF (e.g, AF 218) the requirements of each sub-application (for instance energy consumption information, latency requirements, etc.) (for instance via the M5 interface, RTC-5 interface, etc.), and the UE is enabled to send to the AF information about its aggregation capability (for instance via the M5 interface, RTC-5 interface, etc.).

[0090] In various embodiments, the UE may have the capability to receive several sub-streams and aggregate them via the MSH in the UE. The UE decision may be based on its own information about its available computing capacity, applications running and energy availability.

[0091] In response, the AF may decide to send different sub-streams to UE or not based on UE capability indication, QoS information which may be taken from the 5GS system (e.g. 3GPP 0AM, NWDAF). For example, if the reported QoS are lower than a threshold and it is predicted to be lower than the threshold for the coming sessions, the AF may decide to send only one stream instead of multiple sub-streams.

[0092] In various embodiments, the UE may not have the capability of receiving several substreams and the aggregation may be performed in the server side. In this case, the AF, based on different sub-streams requirements, may select different ASs to process each of the sub-streams and then select one AS to aggregate all the sub-streams based on AS processing capacity, AS load and AS energy consumption info.

[0093] In various embodiments, the AF, based on different sub-streams requirements, may select one AS to process all the sub-streams and then aggregate in that AS or select one other AS to aggregate all the sub-streams.

[0094] In various embodiments, the AF may select the ASs based on the collected requirements about sub-applications from the UE client. For example, the AF may select different ASs and content on them for different sub-applications / sub-modules based on AS metrics and subapplication metrics in the UE.

[0095] In various embodiments, the UE may receive several sub-streams from different ASs by indication about details of each sub-stream to UE over M4 interface. The AS may provide an indication to the UE that this sub-stream is related to which submodules for the specific XR application.

[0096] FIG. 5 is a diagram of an example embodiment of signals and operations among a UE and the network according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 5 may correspond to similar components described above in FIGS. 1-4. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[0097] As shown in FIG. 5, the UE may include trusted functions such as a media session handler and a media access function, as well as a trusted or untrusted sub-applications (e.g., sub- app 1... n). As described above, a first sub-application may be a video sub-application while a second sub-application may be a haptic sub-application.

[0098] On the network side, trusted or untrusted network functions such as an AF, application servers (e.g., AS1... .n), NWDAF / ADAES, and an application provider.

[0099] At operation 501, configuration and provision a of a new XR session is performed. In various embodiments, XR streaming and playback may be established.

[0100] At operation 502, the sub-app transmits a start of XR session message to the media access function and the media access function receives the start of XR session message.

[0101] At operation 503, the XR session setup is performed between the media session handler and the media access function.

[0102] At operation 504, XR session setup is performed between the media session handler and the AF, as well as between the AF and the AS. At operation 505, the application provider transmits media content to the AS and the AS receives the media content.

[0103] At operation 506, media content is provided between the AS and the media access function.

[0104] At operation 507, the media access function transmits the start of XR media playback to the media session handler and the media session handler receives the start of XR media playback.

[0105] At operation 508, setup of the media playback pipeline is performed between the subapplication and media access function, the media access function and the AS, and the AS and theapplication provider. Collectively, in various embodiments, operations 502-508 may be referred to as an XR session initialization.

[0106] At operation 509, the AF transmits a request for sub-app requirements and UE capabilities message to the media session handler and the media session handler receives the request for sub-app requirements and UE capabilities message. In various embodiments, the request for sub-app requirements and UE capabilities message includes a request for sub-app energy-related metrics, sub-streams identification (association to an application on the UE), UE aggregation capabilities, etc. Persons of skill in the art may appreciate that other requirements from the UE side are possible.

[0107] At operation 510, the media session handler transmits a sub-app requirements and UE capabilities collection confirmed message to the AF and the AF receives the sub-app requirements and UE capabilities collection confirmed message. In various embodiments, the sub-app requirements and UE capabilities collection confirmed message includes a request for sub-app energy-related metrics, sub-streams identification (association to an application on the UE), UE aggregation capabilities, etc. Persons of skill in the art may appreciate that other requirements from the UE side are possible. At operation 511, the UE transmits a report for current metrics for a duration to the AF at particular intervals (frequency at which such information is sent, i.e. every 1ms, 5ms, 10 ms, etc.) and the AF receives the report for current metrics for a duration. In various embodiments, the duration may include a time T <= X ms at particular intervals (frequency at which such information is sent, i.e. every 1ms, 5ms, 10 ms, etc.).

[0108] At operation 512, analytics data from the NWDAF on UE sub-app requirements and UE capabilities is exchanged between the AF and the NWDAF / ADAES.

[0109] At operation 513, sub-apps metrics data processing based on reported metrics from the UE and NWDAF is performed by the AF.

[0110] Collectively, operations 509-513 may be referred to as a reporting of UE and sub-apps operation.

[0111] At operation 514, the AF transmits a request for application server metrics collection to the AS(s) and the AS(s) receives the request application server metrics collection message. In various embodiments, the request for application server metrics collection may receive application capability, supported versions, features, current server load, number of users connected, and energy consumption. Persons of skill in the art may appreciate that other requirements from the AS side are possible.

[0112] At operation 515, the AS transmits a metrics collection confirmed message to the AF and the AF receives the metrics collection confirmed message.

[0113] At operation 516, the AS transmits an application server metrics report to the AF and the AF receives the application server metrics report.

[0114] At operation 517, analytics data from the NWDAF on the AS is exchanged between the AF and the NWDAF / AD AES.

[0115] At operation 518, the AF performs application server metric report processing and at operation 519, the AF performs application server and application features selection for each substream based on the UE and AS metrics.

[0116] Collectively, operations 514-519 may be referred to as reporting of AS.

[0117] Upon completion of operation 519, several different alternatives may be performed.

[0118] In a first alternative (e.g., solutionl), at operation 520, the AF sends a configuration information with the available list of most suitable AS(s) to the media session handler, and the media session handler receives the configuration information with the available list of most suitable AS(s). In various embodiments, configuration information may include one or more of an application capability or an application version, features, and / or energy consumption.

[0119] Upon receipt of the configuration information with the available list of most suitable AS(s) at operation 520, at operation 521, the media session handler selects the new AS.

[0120] At operation 522, restarting of XR media playback with the new AS (e.g., selected AS) is performed.

[0121] At operation 523, the existing session is modified with the new server between the media session handler and the AF.

[0122] At operation 524, the AF transmits a request for XR content message to the newly selected AS and the AS receives the request . In various embodiments, the AS may be the selected AS.

[0123] At operation 525, an XR session is established between the media session handler and the AF, as well as between the AF and the AS.

[0124] At operation 526, media is exchanged between the media access function and the newly selected AS.

[0125] At operation 527, the media access function retransmits this information to the media session handler and the media session handler is ready to start of XR media playback.

[0126] In a second alternative (e.g., solution2) upon completion of operation 519, at operation 528, the AF selects the new AS.

[0127] Accordingly, at operation 529, the AF sends a configuration information of the most suitable AS message to the media session handler, and the media session handler receives the configuration information of the most suitable AS message. Upon receipt of the configuration information of the most suitable AS message at operation 529, at operation 530, restarting of XR media playback with the new AS (e.g., most suitable AS) is performed between the media session handler and the media access function. At operation 531, the existing session is modified with the new application server.

[0128] At operation 532, the AF transmits a request for XR content message to the AS and the AS receives the request for XR content message. In various embodiments, the AS may be the newly selected AS.

[0129] At operation 533, an XR session is established between the AF and the AS, and the AF and the media session handler.

[0130] At operation 534, media content from the most energy efficient AS is exchanged between the media access function and the AS.

[0131] At operation 535, the media access function transmits the start of XR media playback to the media session handler and the media session handler receives the start of XR media playback.

[0132] Collectively, operations 520-527 and operations 528-535 may be referred to as a selection of new AS operation.

[0133] At operation 536, media playback is performed.

[0134] The operations of FIG. 5 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 5. In embodiments, the operations may not include every operation illustrated in FIG. 5. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 5. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 5.

[0135] The following describes operations from the perspective of a UE. From such a perspective, a method may include transmitting, by the UE, a first message to a first apparatus,the first message including at least one metric requirement for at least a first sub-application of a first application including one or more sub-applications; receiving, by the UE, a second message from the first apparatus, the second message including an indication of a first application server for providing a first content; establishing, by the UE, a communication session to the first application server based upon the indication; and receiving, by the UE, a third message from the first apparatus, the third message including the first content from the first application server.

[0136] The following describes operations from the perspective of a network apparatus (e.g., first apparatus). From such a perspective, a method may include receiving, by the first apparatus, a first message from a user equipment (UE), the first message including at least one first metric requirement for at least a first sub-application of a first application including one or more subapplications; receiving, by the first apparatus, analytics data from a second apparatus relating to at least one second metric requirement for the first sub-application; performing, by the first apparatus, processing based on the at least one first metric requirement and the at least one second metric requirement; transmitting, by the first apparatus, a request to a first application server for a metric relating to the first application server; receiving, by the first apparatus, a report from the first application server including the metric relating to the first application server; transmitting, by the first apparatus, a second message to the UE, the second message including information relating to the first application server; and transmitting, by the first apparatus, a request for content to the first application server.

[0137] FIG. 6 is a block diagram of a wireless station or node (e.g., UE, user device, AP, BS, eNB, gNB, RAN node, network node, TRP, or other node) 600, according to one illustrated aspect of the present disclosure. The wireless station 600 may include, for example, one or more (e.g., two as shown in FIG. 6) RF (radio frequency) or wireless transceivers 602A, 602B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit / entity (controller) 604 to execute instructions or software and control transmission and receptions of signals, and a memory 606 to store data and / or instructions.

[0138] Processor 604 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 604, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wirelesstransceiver 602 (602A or 602B). Processor 604 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 602, for example). Processor 604 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 604 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination of these. Using other terminology, processor 604 and transceiver 602 together may be considered as a wireless transmitter / receiver system, for example.

[0139] In addition, referring to FIG. 6, a controller (or processor) 608 may execute software and instructions, and may provide overall control for the station 600, and may provide control for other systems not shown in FIG. 6, such as controlling input / output devices (e.g., display, keypad), and / or may execute software for one or more applications that may be provided on wireless station 600, such as, for example, an email program, audio / video applications, a word processor, a Voice over IP application, or other application or software.

[0140] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 604, or other controller or processor, performing one or more of the functions or tasks described above.

[0141] According to another example embodiment, RF or wireless transceiver(s) 602A / 602B may receive signals or data and / or transmit or send signals or data. Processor 604 (and possibly transceivers 602A / 602B) may control the RF or wireless transceiver 602A or 602B to receive, send, broadcast or transmit signals or data.

[0142] Example embodiments are provided or described for each of the example methods, including: An apparatus (e.g., 600, FIG. 6) including means (e.g., processor 604, RF transceivers 602A and / or 602B, and / or memory 606, in FIG. 6) for carrying out any of the methods; a non- transitory computer-readable storage medium (e.g., memory 606, FIG. 6) comprising instructions stored thereon that, when executed by at least one processor (processor 604, FIG. 6), are configured to cause a computing system (e.g., 600, FIG. 6) to perform any of the example methods; and an apparatus (e.g., 600, FIG. 6) including at least one processor (e.g., processor 604, FIG. 6), and at least one memory (e.g., memory 606, FIG. 6) including computer program code, the at least one memory (606) and the computer program code configured to, with the at least one processor (604),cause the apparatus (e.g., 600) at least to perform any of the example methods.

[0143] Further embodiments of the present disclosure include the following examples.

[0144] Example 1.1. A user equipment (UE), comprising: means for transmitting, by a user equipment (UE), a first message to a first apparatus, the first message including at least one metric requirement for at least a first sub-application of a first application including one or more sub-applications; means for receiving, by the UE, a second message from the first apparatus, the second message including an indication of a first application server for providing a first content; means for establishing, by the UE, a communication session to the first application server based upon the indication; and means for receiving, by the UE, a third message from the first apparatus, the third message including the first content from the first application server.

[0145] Example 1.2. The UE of example 1.1, further comprising means for receiving, by the UE, a request message from the first apparatus requesting the at least one metric requirement for the first sub-application and UE capabilities.

[0146] Example 1.3. The UE as in any one of examples 1.1 or 1.2, further comprising means for receiving, by the UE, from the first apparatus, a configuration information relating to one or more application servers.

[0147] Example 1.4. The UE of example 1.3, wherein the configuration information includes one or more of an application capability, application version, features, or energy consumption.

[0148] Example 1.5. The UE as in any one of examples 1.1 to 1.4, further comprising means for selecting by the UE, the first application server from among the one or more application servers for receiving content.

[0149] Example 1.6. The UE as in any one of examples 1.1 to 1.5, further comprising means for receiving, by the UE, configuration information from the first apparatus relating to the first application server as a selected server to receive content.

[0150] Example 1.7. The UE as in any one of examples 1.1 to 1.6, wherein the first message includes a metric requirement for a second sub-application of the first application.

[0151] Example 1.8. The UE as in any one of examples 1.1 to 1.7, wherein the first message includes information indicating the at least one sub-application relating to the first application.

[0152] Example 1.9. The UE as in any one of examples 1.1 to 1.8, wherein a metric requirement of a sub-application includes one or more of a sub-application energy related metric, a sub-stream identification, or UE aggregation capabilities.

[0153] Example 1.10. The UE as in any one of examples 1.1 to 1.9, further comprising means for receiving a fourth message including second content from a second application server.

[0154] Example 1.11. The UE as in any one of examples 1.1 to 1.9, wherein the third message includes the second content.

[0155] Example 1.12. The UE as in any one of examples 1.1 to 1.11, wherein the first application server is a same server currently providing the first content to the UE.

[0156] Example 1.13. The UE as in any one of examples 1.1 to 1.12, wherein the first application server is a different server than a server currently providing the first content to the UE.

[0157] Example 2.1. An apparatus, comprising: means for receiving, by a first apparatus, a first message from a user equipment (UE), the first message including at least one first metric requirement for at least a first sub-application of a first application including one or more sub-applications; means for receiving, by the first apparatus, analytics data from a second apparatus relating to at least one second metric requirement for the first sub-application; means for performing, by the first apparatus, processing based on the at least one first metric requirement and the at least one second metric requirement; means for transmitting, by the first apparatus, a request to a first application server for a metric relating to the first application server; means for receiving, by the first apparatus, a report from the first application server including the metric relating to the first application server; means for transmitting, by the first apparatus, a second message to the UE, the second message including information relating to the first application server; and means for transmitting, by the first apparatus, a request for content to the first application server.

[0158] Example 2.2. The apparatus of example 2.1, further comprising means for transmitting, by the first apparatus, a request message to the UE requesting the at least one metric requirement for the first sub-application and UE capabilities.

[0159] Example 2.3. The apparatus as in any one of examples 2.1 or 2.2, further comprising means for transmitting, by the first apparatus, a configuration information relating toone or more application servers to the UE.

[0160] Example 2.4. The apparatus as in any one of examples 2.1 to 2.3, further comprising means for modifying, by the first apparatus, an existing session from an application server currently providing content to the UE to the first application server.

[0161] Example 2.5. The apparatus as in any one of examples 2.1 to 2.4, further comprising means for selecting, by the first apparatus, an application server out of one or more application servers as the first application server.

[0162] Example 2.6. The apparatus of example 2.5, further comprising means for transmitting, by the first apparatus, configuration information relating to the first application server as a selected server to receive content to the UE.

[0163] Example 2.7. The apparatus as in any one of examples 2.1 to 2.6, wherein the first message includes a metric requirement for a second sub-application of the first application.

[0164] Example 2.8. The apparatus of example 2.7, wherein the second message includes information relating to a second application server for providing a second content.

[0165] Example 2.9. The apparatus as in any one of examples 2.1 to 2.8, wherein the first application server is an application server having a highest energy efficiency out of a plurality of application servers.

[0166] Example 2.10. The apparatus as in any one of examples 2.1 to 2.9, further comprising means for determining, by the first apparatus whether an application server is to transmit aggregated or non-aggregated data based upon a UE capability.

[0167] Example 2.11. The apparatus as in any one of examples 2.1 to 2.10, wherein the first apparatus selects the first application server to aggregate data for transmission and for one or more additional application servers transmit their data to the first application server for aggregation.

[0168] As described herein and above, energy consumption metrics collection and reporting can be done in different ways, depending on the relationship between the Application Provider and the AS and AF and the UE client. The following clauses show simplified signaling examples where an AF reports the collected energy consumption metrics of the UE sub-applications and the collected energy consumption metrics of Application Servers (ASs).

[0169] In various embodiments, FIG. 5 above illustrates a scenario where the energy consumption metrics collection and reporting is configured by the AF (for both UE and the AS). In this example, it is assumed that the energy consumption metrics configuration / provided by theAF comprises instructions / rules regarding metrics collection and reporting for the scheme that is defined by 3 GPP belonging to the 5 GMS System operator / XR application operator.

[0170] It requires the UE Client as well as the AS to perform metrics reporting to the AF according to the configuration rules provided by the AF. Furthermore, it is assumed that the AF is required to deliver metrics reports obtained from the UE Client and the AS to separate destination entities (for instance NWDAF), upon optionally having performed post-processing of the original report information, according to the configuration rules of each metrics scheme.

[0171] In various embodiments, the signals and / or operations shown in FIG. 5 may be steps. For example, based on steps 501-508, an on-going XR media session is established.

[0172] Following this, once the session is established, in step 509, the Application Function (AF) requests the UE to start sending relevant UE metrics (in this case, the UE sends the energy consumption of individual sub-applications).

[0173] This is confirmed by the UE in step 510 and provided via step 511 where UE provides sub application relevant metrics, limited to a certain duration of X ms, in order to protect the UE privacy.

[0174] The AF could optionally send this info the NWDAF for further analytics processing, if allowed by UE privacy settings. This allows the NWDAF also to store, process and send UE related analytics data to the AF when requested in the future. This is processed in step 512.

[0175] Now in step 513, AF processes the received collected data information from NWDAF as well as the UE in order to select the AS corresponding the UE collected and subsequently processed metrics. For example, NWDAF may provide UEs predicted behavior. For instance, this predicted behavior could be UE device capabilities and energy information at a particular instance in time TO, between 12 noon and 14h. The UE and the requested sub-apps metrics are now available in the AF.

[0176] The AF has now the requirements of individual sub-applications of the UE during the ongoing XR session. Following this, the AF now begins to monitor, collect and report the energy consumption of the application servers (As) who are actively serving the UE. This is done in Step 514.

[0177] In step 514, the AF requests the ASs to send different metrics related to ASs and the application running and content existing on them related to UE application (e.g., their energy consumption) in its current form.

[0178] The ASs confirms sending this requested information to the AF in step 515 and therequested metrics (for example energy consumption at that particular time instance) are sent to the AF in step 516.

[0179] The AF could optionally send this info the NWDAF for further analytics processing. This allows the NWDAF also to store, process and send AS related analytics data to the AF when requested in the future. This is processed in step 517.

[0180] The AF now processes the received information in step 518.

[0181] The UE sub-apps metrics and the AS metrics are now available in the AF in step 519.

[0182] In step 520, the AF sends the new configuration information to the UE client (Media session Handler), with the list of new available application servers (ASs). This could be sent as a meta-data to the UE client, via M5 interface.

[0183] In step 521, the UE client is allowed to select another new AS most suitable for its current session without modifying the on-going session.

[0184] A new AS is selected in step 522.

[0185] The UE client sends a new request to modify the existing session to the AF in step 523, which is forwarded to the respective Application Server from the AF in step 524.

[0186] The existing XR session now successfully modified with the new AS in step 526.

[0187] Media transfer continues in step 527.

[0188] In various embodiments, all steps remain the same, except for step 528, where the application server selection is done by the AF.

[0189] This selected AS is sent to the UE without sending a list of available AS as meta-data in step 529.

[0190] The UE connects to the new Application Server (AS) in step 530.

[0191] The UE client sends a new request to modify the existing session to the AF in step 531, which is forwarded to the respective Application Server from the AF in step 532.

[0192] The existing XR session now successfully modified with the new AS in step 523.

[0193] Media transfer continues in step 534 and 535.

[0194] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually anyappropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[0195] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[0196] In various embodiments, the terms “first message” and “second message”, as well as any subsequent messages may refer to any messages that are transmitted or received in an order and are not necessarily limited to any particular message.

[0197] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C) ”

[0198] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta- languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[0199] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particularaspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

1. 29CLAIMS:

1. A method, comprising: transmitting, by a user equipment (UE), a first message to a first apparatus, the first message including at least one metric requirement for at least a first sub-application of a first application including one or more sub-applications; receiving, by the UE, a second message from the first apparatus, the second message including an indication of a first application server for providing a first content; establishing, by the UE, a communication session to the first application server based upon the indication; and receiving, by the UE, a third message from the first apparatus, the third message including the first content from the first application server.

2. The method of claim 1, further comprising receiving, by the UE, a request message from the first apparatus requesting the at least one metric requirement for the first sub-application and UE capabilities.

3. The method as in any one of claims 1 or 2, further comprising receiving, by the UE, from the first apparatus, a configuration information relating to one or more application servers.

4. The method of claim 3, wherein the configuration information includes one or more of an application capability, application version, features, or energy consumption.

5. The method as in any one of claims 1 to 4, further comprising selecting by the UE, the first application server from among the one or more application servers for receiving content.

6. The method as in any one of claims 1 to 5, further comprising receiving, by the UE, configuration information from the first apparatus relating to the first application server as a selected server to receive content.

7. The method as in any one of claims 1 to 6, wherein the first message includes a metric requirement for a second sub-application of the first application.

308. The method as in any one of claims 1 to 7, wherein the first message includes information indicating the at least one sub-application relating to the first application.

9. The method as in any one of claims 1 to 8, wherein a metric requirement of a subapplication includes one or more of a sub-application energy related metric, a sub-stream identification, or UE aggregation capabilities.

10. The method as in any one of claims 1 to 9, further comprising receiving a fourth message including second content from a second application server.

11. The method as in any one of claims 1 to 9, wherein the third message includes the second content.

12. The method as in any one of claims 1 to 11, wherein the first application server is a same server currently providing the first content to the UE.

13. The method as in any one of claims 1 to 12, wherein the first application server is a different server than a server currently providing the first content to the UE.

14. A method comprising: receiving, by a first apparatus, a first message from a user equipment (UE), the first message including at least one first metric requirement for at least a first sub-application of a first application including one or more sub-applications; receiving, by the first apparatus, analytics data from a second apparatus relating to at least one second metric requirement for the first sub-application; performing, by the first apparatus, processing based on the at least one first metric requirement and the at least one second metric requirement; transmitting, by the first apparatus, a request to a first application server for a metric relating to the first application server; receiving, by the first apparatus, a report from the first application server including the metric relating to the first application server;transmitting, by the first apparatus, a second message to the UE, the second message including information relating to the first application server; and transmitting, by the first apparatus, a request for content to the first application server.

15. The method of claim 14, further comprising transmitting, by the first apparatus, a request message to the UE requesting the at least one metric requirement for the first subapplication and UE capabilities.

16. The method as in any one of claims 14 or 15, further comprising transmitting, by the first apparatus, a configuration information relating to one or more application servers to the UE.

17. The method as in any one of claims 14 to 16, further comprising modifying, by the first apparatus, an existing session from an application server currently providing content to the UE to the first application server.

18. The method as in any one of claims 14 to 17, further comprising selecting, by the first apparatus, an application server out of one or more application servers as the first application server.

19. The method of claim 18, further comprising transmitting, by the first apparatus, configuration information relating to the first application server as a selected server to receive content to the UE.

20. The method as in any one of claims 14 to 19, wherein the first message includes a metric requirement for a second sub-application of the first application.

21. The method of claim 20, wherein the second message includes information relating to a second application server for providing a second content.

22. The method as in any one of claims 14 to 21, wherein the first application server is an application server having a highest energy efficiency out of a plurality of application servers.

23. The method as in any one of claims 14 to 22, further comprising determining, by the first apparatus whether an application server is to transmit aggregated or non-aggregated data based upon a UE capability.

24. The method as in any one of claims 14 to 23, wherein the first apparatus selects the first application server to aggregate data for transmission and for one or more additional application servers transmit their data to the first application server for aggregation.

25. A user equipment (UE), comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the UE at least to perform a method as in any one of claims 1-13.

26. An apparatus, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the apparatus at least to perform a method as in any one of claims 14-24.

27. A processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform a method as in any one of claims 1 to 24.

28. A user equipment (UE), comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the UE at least to perform: transmitting, by the UE, a first message to a first apparatus, the first message including at least one metric requirement for at least a first sub-application of a first application including one or more sub-applications; receiving, by the UE, a second message from the first apparatus, the second message including an indication of a first application server for providing a first content;33 establishing, by the UE, a communication session to the first application server based upon the indication; and receiving, by the UE, a third message from the first apparatus, the third message including the first content from the first application server.

29. An apparatus, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the apparatus at least to perform: receiving, by a first apparatus, a first message from a user equipment (UE), the first message including at least one first metric requirement for at least a first sub-application of a first application including one or more sub-applications; receiving, by the first apparatus, analytics data from a second apparatus relating to at least one second metric requirement for the first sub-application; performing, by the first apparatus, processing based on the at least one first metric requirement and the at least one second metric requirement; transmitting, by the first apparatus, a request to a first application server for a metric relating to the first application server; receiving, by the first apparatus, a report from the first application server including the metric relating to the first application server; transmitting, by the first apparatus, a second message to the UE, the second message including information relating to the first application server; and transmitting, by the first apparatus, a request for content to the first application server.

Images