Technology for file-aware communication

Abstract

Certain aspects of the present disclosure provide techniques for wireless communications. The method generally includes: determining one or more target metrics associated with a file having a plurality of packets, the plurality of packets including at least one of a plurality of uplink packets or a plurality of downlink packets; determining one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file; and communicating the plurality of packets with a second network entity based on the determined one or more communication parameters.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 16 / 893,239, filed on June 4, 2020, which claims the benefit of and priority to U.S. Provisional Application No. 62 / 858,701, filed on June 7, 2019, and U.S. Provisional Application No. 62 / 859,470, filed on June 10, 2019, both of which are assigned to the assignee of this application and are hereby expressly incorporated herein by reference as if fully set forth below and for all applicable purposes.

[0003] background

[0004] Public domain

[0005] Aspects of the present disclosure relate to wireless communications and, more particularly, to techniques for file aware communications.

[0006] Related technical description

[0007] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name just a few.

[0008] In some examples, a wireless multiple access communication system may include several base stations (BS), each of which is capable of supporting communication of multiple communication devices (also referred to as user equipment (UE)) simultaneously. In an LTE or LTE-A network, a set of one or more base stations may define an evolved B node (eNB). In other examples (e.g., in a next generation, new radio (NR), or 5G network), a wireless multiple access communication system may include several distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with several central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more DUs in communication with a CU may define an access node (e.g., which may be referred to as a BS, a next generation B node (gNB or g B node), a TRP, etc.). A BS or DU may communicate with a set of UEs on a downlink channel (e.g., for transmission from a BS or DU to a UE) and an uplink channel (e.g., for transmission from a UE to a BS or DU).

[0009] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. New radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is an enhancement set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0010] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies.

[0011] Overview

[0012] The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed in the appended claims, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled "Detailed Description," it will be understood how the features of the present disclosure provide advantages including improved communication between access points and stations in a wireless network.

[0013] Certain aspects provide a method for wireless communication by a first network entity. The method generally includes determining one or more target metrics associated with a file having a plurality of packets, the plurality of packets including at least one of a plurality of uplink packets or a plurality of downlink packets. The method may also include determining one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file. The method may also include communicating the plurality of packets with a second network entity based on the determined one or more communication parameters.

[0014] Certain aspects provide a first network entity for wireless communication. In some examples, the first network entity includes a memory and a processor coupled to the memory. In general, the memory and the processor are configured to determine one or more target metrics associated with a file having a plurality of packets, the plurality of packets including at least one of a plurality of uplink packets or a plurality of downlink packets. In some examples, the memory and the processor are configured to determine one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file. In some examples, the memory and the processor are configured to communicate the plurality of packets with a second network entity based on the determined one or more communication parameters.

[0015] Certain aspects relate to an apparatus for wireless communications. The apparatus generally includes means for determining one or more target metrics associated with a file having a plurality of packets, the plurality of packets including at least one of a plurality of uplink packets or a plurality of downlink packets. The apparatus may also include means for determining one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file. The apparatus may also include means for communicating the plurality of packets with a network entity based on the determined one or more communication parameters.

[0016] Certain aspects relate to a non-transitory computer-readable storage medium storing instructions that, when executed by a processor of an apparatus, cause the apparatus to perform a method for wireless communication. In some examples, the method includes determining one or more target metrics associated with a file having a plurality of packets, the plurality of packets including at least one of a plurality of uplink packets or a plurality of downlink packets. In some examples, the method includes determining one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file. In some examples, the method includes communicating the plurality of packets with a network entity based on the determined one or more communication parameters.

[0017] To achieve the foregoing and related ends, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are only indicative of several of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to understand in detail the manner in which the above-stated features of the present disclosure are used, a more particular description of the content briefly summarized above may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

[0020] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

[0021] Figure 2 is a block diagram illustrating an example architecture of a core network (CN) in communication with a radio access network (RAN) in accordance with certain aspects of the present disclosure.

[0022] Figure 3 is a table illustrating various fifth generation (5G) quality indicators according to certain aspects of the present disclosure.

[0023] Figure 4 is a table illustrating various use cases for extended reality (XR) in accordance with aspects of the present disclosure.

[0024] Figure 5

[0013] Illustrated is a wireless communication system for XR in accordance with certain aspects of the present disclosure.

[0025] Figure 6 Traffic flows for packet communications associated with various files are illustrated in accordance with certain aspects of the present disclosure.

[0026] Figure 7 Illustrated is communication of file-level metric information in a wireless communication system for XR, in accordance with certain aspects of the present disclosure.

[0027] Figure 8 is a flow diagram illustrating example operations for wireless communications in accordance with certain aspects of the present disclosure.

[0028] Fig. 9 Illustrated are communications devices that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.

[0029] Fig.10is a block diagram illustrating an example architecture of a distributed radio access network (RAN) in accordance with certain aspects of the present disclosure.

[0030] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation.

[0031] Detailed Description

[0032] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for using file-level metrics to serve extended reality (XR) applications.

[0033] Wireless communication systems, such as 5G New Radio (NR) systems, may support services, such as XR services, that require data communications with a particular quality of service (QoS). In one example, XR QoS requires relatively high bit rates, high reliability, and low latency relative to aspects of other enhanced mobile broadband (eMBB) and ultra-reliable, low-latency communication services. XR applications may support virtual reality (VR) and augmented reality (AR) applications, cloud gaming, and the like. As such, XR services may require interoperability between (e.g., 5G) network devices and XR applications.

[0034] In general, wireless communications are packet-centric communications. For example, network devices (such as in LTE or 5G networks) communicate data packets so that the QoS of the packetized data is determined and communicated on a per-packet basis. In contrast, some examples of XR applications use a file-centric basis for communication. In other words, each file has a specific QoS associated with it, and thus, each packet of the file shares the same QoS requirements of the file.

[0035] Thus, aspects of the present disclosure describe technologies and methods for wireless communications that support interoperability between (e.g., 5G) network devices and XR applications. For example, an XR application client running on a user equipment (UE) may generate a file containing multiple packets. Each packet in the file may include an identifier that identifies the file to which the packet belongs. The application client then communicates the packet to the UE. The UE may also receive uplink file information that provides the UE with QoS parameters for the file identified by the packet received by the UE. For example, the uplink file information may include one or more of a file error rate (FER) or a file delay budget (FDB). In some examples, the uplink file information may include one or more of a FER or FDB for each type of file in a file burst communicated by the application client to the UE. That is, the uplink file information provides the UE with QoS information for uplink communication of packets received from the application client.

[0036] In a similar manner, a node (e.g., a base station) in a radio access network (RAN) may receive a file from an XR application server along with downlink file information that is configured to provide QoS information to the RAN node for downlink communication of packets received from the application server.

[0037] The following description provides examples rather than limiting the scope, applicability or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace, or add various procedures or components. For example, the described method may be performed in an order different from the order described, and various steps may be added, omitted, or combined. Moreover, the features described with reference to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such equipment or methods practiced using other structures, functionalities, or structures and functionalities as supplements to the various aspects of the present disclosure set forth herein or in addition. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The wording "exemplary" is used herein to mean "used as an example, instance, or explanation". Any aspect described as "exemplary" herein need not be interpreted as being superior to or superior to other aspects.

[0038] The techniques described herein may be used for various wireless communication technologies, such as 3GPP Long Term Evolution (LTE), Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably.

[0039] CDMA networks may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), CDMA 2000, etc. UTRA includes Wideband CDMA (WCDMA) and other CDMA variants. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. TDMA networks may implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks may implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the Third Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).

[0040] The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although various aspects may be described herein using terms typically associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations, such as 5G and later generations, including NR technologies.

[0041] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure may be performed. For example, the wireless communication network 100 may be a NR system (e.g., a 5G NR network). Figure 1 As shown in FIG. 1 , the wireless communication network 100 may be in communication with a core network (CN) 130. The CN 130 may be in communication with one or more BSs 110 and / or UEs 120 via one or more interfaces, and may also be in communication with an application server (AS) 140, as described below with reference to FIG. Figure 2 discussed in more detail.

[0042] The user equipment (UE) 120a includes an XR module 122, which can be configured to manage the communication of XR application data generated by an application server (AS) 140 (e.g., a cloud server), or an XR application client resident on the UE 120a (e.g., an XR application on the UE 120a), or an XR application client communicatively coupled to the UE 120a (e.g., a device separate from the UE 120a that communicates the XR application file to the UE 120). According to various aspects described herein, the BS 110a also includes an XR module 112, which can be configured to manage the communication of XR data for the XR application between the AS 140 and the UE 120a.

[0043] In some examples, the XR modules (122 and 112) are configured to communicate (e.g., receive and transmit) multiple packets received from the XR application and / or AS 140 according to QoS parameters corresponding to the file or file type. In one example, the XR modules (122 and 112) may determine communication parameters for communicating each of the multiple packets so that the multiple packets are communicated within the QoS requirements for the files to which the packets correspond. For example, a file may have one or more target metrics (such as a file error rate (FER) and / or a file delay budget (FDB)), or any other suitable QoS requirements that specify one or more communication parameters for communicating the file. Thus, the XR modules (122 and 112) may determine one or more communication parameters for transmitting each packet contained in the file so that all packets of the file are communicated according to the target metrics of the file.

[0044] Radio access network (RAN) 150 may include network controller 160 and BS 110. RAN 150 may be in communication with CN 130 and AS 140. According to certain aspects, BS 110 and UE 120 may be configured for one or more services (e.g., URLLC, eMBB, XR, etc.) involving an application provider (e.g., AS 140) and / or traffic flows between BS 110 and UE 120 associated with one or more applications running on UE 120. For example, UE 120a may request admission for one or more traffic flows for application-related services (e.g., requesting BS 110a to serve as a link between UE 120a and AS 140).

[0045] like Figure 1As illustrated in , the wireless communication network 100 may include several BSs 110a-z (each also individually referred to herein as BS 110, or collectively referred to as BS 110) and other network entities. BS 110 may provide communication coverage for a particular geographic area (sometimes referred to as a "cell"), which may be stationary or mobile depending on the location of the mobile BS 110. In some examples, BS 110 may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless communication network 100 via various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.) using any suitable transport network. Figure 1 In the example shown in FIG. 1 , BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more cells. A network controller 160 may be coupled to a set of BSs 110 and provide coordination and control (e.g., via a backhaul) for these BSs 110.

[0046] BS 110 communicates with UEs 120a-y (each also individually referred to herein as UE 120, or collectively referred to as UE 120) in the wireless communication network 100. UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. The wireless communication network 100 may also include a relay station (e.g., relay station 110r) (also referred to as a relay, etc.) that receives transmissions of data and / or other information from an upstream station (e.g., BS 110a or UE 120r) and sends transmissions of data and / or other information to a downstream station (e.g., UE 120 or BS 110), or that relays transmissions between UEs 120 to facilitate communication between the devices.

[0047] exist Figure 1 In FIG. 1 , a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and / or uplink. A thin dashed line with double arrows indicates potentially interfering transmissions between a UE and a BS.

[0048] Figure 2 is an illustration of a CN 200 (eg, such as a RAN 150 or AS 140) in communication with the RAN 150 and the AS 140 according to certain aspects of the present disclosure. Figure 1 A block diagram of an example architecture of a CN 130 in FIG. Figure 2As shown in FIG, the example architecture includes CN 200, RAN 150, UE 120, and data network (DN) 228 (eg, operator services, Internet access, or third-party services).

[0049] CN 200 may host core network functions. CN 200 may be centrally deployed. CN 200 functionality may be offloaded (e.g., to Advanced Wireless Services (AWS)) in an effort to handle peak capacity. Figure 2 As shown in the figure, the example CN 200 can be implemented by one or more network entities that perform network functions (NFs), including a network slice selection function (NSSF) 204, a network exposure function (NEF) 206, a NF repository function (NRF) 208, a policy control function (PCF) 210, a unified data management (UDM) 212, an application function (AF) 214, an authentication server function (AUSF) 216, an access and mobility management function (AMF) 218, a session management function (SMF) 220; a user plane function (UPF) 226, and various other functions (not shown), such as an unstructured data storage function (UDSF); a unified data repository (UDR); a 5G equipment identity register (5G-EIR); and / or a security edge protection proxy (SEPP).

[0050] AMF 218 may include the following functionality (some or all of the AMF functionality may be supported in one or more instances of the AMF): termination of the RAN control plane (CP) interface (N2); termination of the non-access stratum (NAS) (e.g., N1), NAS encryption and integrity protection; registration management; connection management; reachability management; mobility management; lawful interception (for AMF events and interfaces to LI systems); transmission of session management (SM) messages between UE 120 and SMF 220; transparent proxy for routing SM messages; access authentication; access authorization; transmission of short message service (SMS) messages between UE 120 and SMS function (SMSF); security anchor functionality (SEAF); security context management (SCM), which receives keys from SEAF, which uses the keys to derive access network specific keys; location service management for regulated services; between UE 120 and location management function (LMF) and RAN Transmission of positioning service messages between 150 and LMF; EPS bearer ID allocation for interworking with Evolved Packet Service (EPS); and / or UE mobility event notification; and / or other functionality.

[0051] The SMF 220 may support: session management (e.g., session establishment, modification, and release), UE IP address allocation and management, Dynamic Host Configuration Protocol (DHCP) functions, termination of NAS signaling related to session management, downlink data notification, and traffic steering configuration for UPF for correct traffic routing. The UPF 226 may support: packet routing and forwarding, packet inspection, quality of service (QoS) handling, external protocol data unit (PDU) session interconnection point to DN 228, and anchor point for intra-RAT and inter-RAT mobility. The PCF 210 may support: unified policy framework, providing policy rules to control protocol functions, and / or access to subscription information in UDR for policy decisions. The AUSF 216 may act as an authentication server. The UDM 212 may support: generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The NRF 208 may support: service discovery functions, and maintenance of NF profiles and available NF instances. The NSSF may support: selection of a network slice instance for serving UE 120, determination of allowed network slice selection assistance information (NSSAI), and / or determination of an AMF set to be used to serve UE 120.

[0052] NEF 206 may support: opening of capabilities and events, secure provision of information from external applications to the 3GPP network, and translation of internal / external information. AF 214 may support: application influence on traffic routing, access to NEF 206, and / or interaction with the policy framework for policy control. Figure 2 As shown in FIG, CN 200 may communicate with AS 140, UE 120, RAN 150, and DN 228. In some examples, CN 200 communicates with external AS 140 via NEF 206 and / or AF 214.

[0053] A communication system, such as a wireless communication network 100 (e.g., RAN 150), may provide communication services to a UE (e.g., UE 120 / 120a). For example, 5G NR may support services such as enhanced mobile broadband (eMBB) services targeting wide bandwidth (e.g., 80 MHz or more), ultra-reliable low latency communication (URLLC) services, and other services including XR services discussed in more detail below. These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements.

[0054] The traffic requirements of a service can be summarized via a set of target metrics (e.g., QoS parameters) and associated with the traffic flow supporting the service. Parameters may include file error rate (FER) or packet error rate (PER), file delay budget (FDB) or packet delay budget (PDB), and / or guaranteed bit rate (GBR) (not shown). FER / PER can be the ratio (in percentage) of successfully received packets / files. For example, PER can define the upper limit of the ratio of PDUs (e.g., IP packets) that have been processed by the sender of the link layer protocol (e.g., RLC in the RAN accessed by 3GPP) but not successfully delivered to the upper layer (e.g., PDCP in the RAN accessed by 3GPP) by the corresponding receiver. Thus, FER / PER can define the upper limit of the non-congestion related file / packet loss rate. FDB / PDB can be defined as the upper limit of the time that a file / packet can be delayed between a source node and a target node. For example, the source node can be a UE (e.g., UE 120) and the target node can be a UPF (e.g., UPF 226) or AS140. The GBR may indicate the bandwidth (bit rate) guaranteed by the network or AS 140. In some examples, the FER and / or FDB may be set by AS 140.

[0055] The resource type may determine whether dedicated network resources associated with a QoS flow-level guaranteed flow bit rate (GFBR) value are permanently allocated (e.g., by an admission control function in a radio base station), whereas non-GBR QoS flows may be pre-authorized via static policy and charging control. GBR QoS flows may use either a GBR resource type or a delay-critical GBR resource type. For traffic flows of the "delay-critical GBR" type (e.g., for URLLC traffic flows), a parameter called the Maximum Data Burst Volume (MDBV) is specified to describe the traffic burst. The MDBV indicates the maximum amount of data that a RAN node (e.g., base station 110 / 110a) is required to serve during a PDB period. The MDBV may be signaled to the RAN (e.g., RAN 150) along with a standardized indicator value (e.g., 5QI), and if an MDBV is received, it should be used instead of a default value.

[0056] Figure 3Table 300 illustrating example QoS parameters that may be configured for various services is illustrated. In some examples, conversational voice services, conversational video services (e.g., such as live streaming), and video services (e.g., such as buffered streaming) and / or TCP-based services (e.g., such as the World Wide Web, email, chat, ftp, p2p file sharing, progressive video, etc.) may be associated with eMBB services. In some examples, remote control services (e.g., UEs are remotely operated by people or computers (such as remote drivers or vehicle-to-everything (V2X) applications) to operate remote vehicles without drivers or remote vehicles located in dangerous environments) may be associated with URLCCs. In some examples, low latency eMBB applications may be associated with XR services. XR services may refer to services such as augmented reality (AR), virtual reality (VR), and cloud gaming. AR and VR services may be characterized by human interaction with the environment or people, or controlling the UE and relying on audio-visual feedback. In use cases like VR and interactive conversations, latency requirements include latency at the application layer (e.g., codec), which may be specified outside of 3GPP.

[0057] Figure 3 The QoS parameters and services shown in table 300 of FIG. 3 are merely illustrative, and various other QoS parameters and services may be specified.

[0058] At high PDB values ​​(e.g., equal to or exceeding 100ms), traffic bursts over the PDB range can be approximated by GBR*PDB. For certain traffic flows measured at each PDB, the percentage of time that the burst exceeds GBR*PDB is small relative to the PER. Dropping packets for such bursts can have a negligible effect on the PER of the traffic. Thus, for such traffic flows, it may not be important to convey the size of the traffic burst. However, for traffic flows at low PDB and low PER values, the amount of traffic handled by the 5G system may be much higher than GBR*PDB. In this case, it is useful to describe the traffic burst.

[0059] As mentioned above, MDBV is specified for "delay-critical GBR" type traffic flows, which are expected to handle low-throughput traffic. Thus, in some cases, the MDBV value range is capped at 4095 bytes (e.g., when signaled on the 5G network interface). Even if the PDB is 1ms (millisecond), the throughput cap of 4095 bytes means that the maximum throughput on the flow cannot exceed 4095 bytes / millisecond (i.e., approximately 32.76Mbps). The supported throughput may be even lower on traffic flows with larger PDB values. However, for some services, such as XR services (e.g., AR, VR, cloud gaming), the throughput requirements (e.g., up to 250Mbps) and the PDB requirements (e.g., 25ms) may be higher.

[0060] As discussed, 5G NR may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or more), millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or more), massive machine type communication MTC (mMTC) targeting non-backward compatible MTC technology, and / or mission critical targeting ultra-reliable low latency communication (URLLC). These services may include latency (e.g., packet delay budget (PDB)) and reliability requirements (e.g., packet error rate (PER)), and may also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. Extended reality (VR) is a wireless communication service for services requiring low latency (e.g., packet delay budget (PDB) between 5 ms and 25 ms) and high bit rate (e.g., packet error rate less than or equal to 1e-3). However, certain XR services may include different latency (e.g., file delay budget (FDB)) and reliability requirements (e.g., file error rate (FER)) than 5G NR to meet corresponding QoS requirements.

[0061] Figure 4 Table 400 illustrating various use cases for XR is illustrated. For example, VR can be used for cloud gaming, virtual reality (VR) split rendering, augmented reality (AR) split computing. Cloud gaming generally refers to gaming on a user device where at least some graphics processor unit (GPU) processing is done on a cloud server (e.g., Figure 1 140). Similarly, GPU processing for VR and AR can be split between the GPU on the cloud and the GPU on the user device. However, cloud gaming, split rendering, and split compute services require low latency to maintain an acceptable gaming experience. As illustrated, cloud gaming can be implemented using QoS or over-the-top (OTT) on a 5G network. Furthermore, as illustrated, different use cases may have different location and mobility requirements.

[0062] Figure 5 is a block diagram illustrating a wireless communication system 500 for XR. As illustrated, a 5G system 502 may include a UE 120, a radio access network (RAN) 110, and a core network (CN) 504 (e.g., Figure 1 CN 130 or Figure 2CN 200). In some aspects, UE 120 may be associated with a head mounted display (HMD) 540 for VR or AR applications. As illustrated, the 5G system 502 may communicate with an edge cloud server 140, which may include logical entities such as an XR edge data network (DN) 522 and an XR edge application function 524. An edge cloud server generally refers to a cloud server located closer to the UE, thereby allowing data communication for various applications with lower latency as described herein. For example, the latency from the CN to the XR edge server may be negligible compared to the 5G system latency. As illustrated, the edge cloud server 140 may be associated with an XR public cloud AF 530. CN 504 may communicate with the XR edge DN via the N6 interface (user plane). In addition, CN504 may communicate with the XR edge AF via the N5 and N33 interfaces. N5 and N33 are interfaces from the XR edge application function 524 to the 5G system.

[0063] Figure 6 6 is a block diagram illustrating a traffic flow 600 for communicating packets (e.g., Internet Protocol (IP) packets) associated with various files. For example, packets 602, 604, 606 may be associated with a file (e.g., file 1), and packets 608, 610, 612 may be associated with another file (e.g., file 2). Files may be sent in multiple bursts. For example, as illustrated, files 1 and 2 may be sent in a first burst (e.g., burst 1), files 3, 4, 5 may be sent in a second burst (e.g., burst 2), and file 6 may be sent in a third burst (e.g., burst 3). In other words, a "file" may generally be associated with a set of packets that are jointly processed by an XR application or an XR application server. Traffic flow 600 may be associated with certain communication parameters (such as GBR, PBR, and / or PDB), which may be configured by BS 110a or UE 120a based on target metrics (e.g., FER and / or FDB) for each file. A "burst" may generally relate to one or more files generated by an application at approximately the same time.

[0064] As discussed, the 5G system may only be aware of packet-level metrics. In other words, the traffic flow 600 may be controlled via packet filters and metrics based on PER and PDB. However, the XR application may specify metrics for groups of packets (e.g., files). For example, the XR application may specify FER instead of PER, or FDB instead of PDB. In addition, the reliability requirements of files may be different. In some cases, the XR application may specify policies related to file handling. For example, the XR application may specify that a file can be used only when all packets of the file are received, or that a continuous packet stream up to the first erroneous packet may be used.

[0065] Example Techniques for File-Aware Communication

[0066] When a file-level metric (such as FER) can be translated into a packet-level metric (such as PER for a 5G system), information may be lost, resulting in inaccurate handling of the file-level requirements of an application. For example, the conversion of packet-level metrics to file-level metrics assumes that independent packet losses occur. For example, a 0.083% PER metric for regulatory packets (e.g., as opposed to giant packets) may be translated into a 1% FER metric assuming that independent packet losses occur. However, in reality, packet losses may be clustered together. Therefore, a 5G system may determine and report that a lower percentage of users have met the packet-level metric (e.g., 0.083% PER) when a larger number of users may actually have met the required file-level metric (e.g., 1% FER). For example, 64% of users may have met the 0.083% PER metric, while in fact 100% of users met the 1% FER metric.

[0067] Thus, certain aspects of the present disclosure relate to techniques for using file-level metrics to serve XR applications.

[0068] Figure 7 7 is a block diagram illustrating the communication of files and file-level metric information in a wireless communication system 700 in accordance with certain aspects of the present disclosure. Figure 7 As illustrated in FIG. 7 , the communication paths may apply to the communication of uplink files 712 and uplink file information 718, and downlink files 714 and downlink file information 716. In this case, the uplink files are files communicated from the application client 710 to the user equipment (UE) 120, and the downlink files are files communicated from the application server 140 to the radio access network (RAN) 110. Of course, the communication structure is not limited to the configuration shown, and may alternatively include additional or fewer components and / or communication paths. The communication system 700 may include Figure 1 , 2 and the components explained in 5.

[0069] As illustrated, the RAN 110 may receive a downlink file 714 (eg, Figure 6 In some examples, the DN 522 may encapsulate each of the plurality of packets with an indicator configured to identify the downlink file to which each packet belongs. As illustrated, the downlink file 714 may be communicated to the RAN 110 via a user plane function (UPF) 706 of the core network (CN) 504.

[0070] The RAN 110 may also receive downlink file information 716 from an application function (AF) 524 of the AS 140, wherein the downlink file information 716 corresponds to the downlink file 714. The AF 524 may generate the downlink file information 716 and communicate it to the RAN 110 via one or more of a policy control function (PCF) / network exposure function (NEF) 704 of the CN 504, a session management function (SMF) 708 of the CN 504, and an access and mobility management function (AMF) 702 of the CN 504, as illustrated. In some examples, the downlink file information 716 includes a target metric (e.g., a QoS requirement (such as a FER or FDB)) for the downlink file 714 identified by each packet in the plurality of packets. In some examples, the downlink file information 716 may include one or more additional target metrics for each additional downlink file communicated to the RAN 110 via a file burst.

[0071] Now, with both the plurality of packets of the downlink file 714 and the downlink file information 716, the RAN 110 knows that the plurality of packets belong to a particular file having a certain target metric for its communication. Accordingly, the RAN 110 can communicate the plurality of packets as if they were a homogeneous group, rather than processing each of the plurality of packets according to its own PER and / or PDB. For example, the RAN 110 will now communicate the group of packets according to the target metric (e.g., FER / FDB) of the corresponding downlink file 714. This is in contrast to an approach that converts or derives the PER or PDB of each packet based on the FER or FDB of the corresponding file, and then transmits each packet individually regardless of the file to which the packet belongs. Thus, various network algorithms (such as rate adaptation target algorithms, HARQ retransmission algorithms, and any other suitable algorithms) can be forced to be implemented more aggressively to meet the target metric for communicating the group of packets.

[0072] Accordingly, various network algorithms may be set by the RAN 110 to achieve a file-level target metric (e.g., FER / FDB) instead of a packet-level target metric (e.g., PER / PDB). For example, if the downlink file 714 has one or more corresponding target metrics, and one of the one or more target metrics is a target FER, the RAN 110 determining one or more communication parameters may also include: determining and setting a rate adaptation target for communicating each of the plurality of packets in the downlink file 714 so that communication of the plurality of packets meets the target FER. The RAN 110 determining one or more communication parameters may also include: determining and setting a number of retransmissions for communicating each of the plurality of packets in the downlink file 714 so that communication of the plurality of packets meets the target FER.

[0073] In another example, if one of the corresponding target metrics of the downlink file 714 is a target FDB, the RAN 110 determining the one or more communication parameters may include determining and setting a packet delivery deadline for each of the plurality of packets to meet the target FDB.

[0074] As discussed, simply converting or deriving the PER or PDB of each packet based on the FER or FDB of the corresponding file can result in information loss and delay. For example, due to other traffic, interference, etc. at different components in the 5G system, or because the XR application releases the packets of the file at different times, the packets may arrive at the 5G system dispersed in time. If the packets are simply communicated individually according to the derived PER / PDB, the probability that the group of packets belonging to a particular file will be communicated according to the FER or FDB is reduced relative to the probability that the group of packets is regarded as a homogeneous group and communicated according to the corresponding FER or FDB. Because the packets are dispersed, the communication of packets by the RAN 110 on an individual basis will result in the packets being communicated over a time window that is almost equal to the time window over which the packets are dispersed. This can also cause problems because the XR application can only use the packets of the file when it has all the packets belonging to the file. As a result, the XR application cannot utilize any initial packets it receives from the RAN 110 at the beginning of the time window.

[0075] In contrast, if the RAN 110 communicates the plurality of packets as if the plurality of packets were a homogeneous group, the RAN 110 may communicate the packet group according to a target metric (e.g., FER / FDB) for the corresponding downlink file 714. For example, if the RAN 110 receives a packet group that is dispersed over a time window, it may temporarily store any initially received packets (e.g., in a buffer) until it has the entire packet group. The RAN 110 may then determine one or more communication parameters (e.g., FER and / or FDB, or alternatively, PER and / or PDB) for communicating the plurality of packets according to the target metric associated with the file. For example, the RAN 110 may map the FER and / or FDB of the plurality of packets directly to various network algorithms for communicating the plurality of packets (e.g., bypassing PER / PDB), or the RAN 110 may map the FER and / or FDB to a PER and / or PDB for one or more of the plurality of packets and then map the PER and / or PDB to various network algorithms.

[0076] In some examples, instead of storing the initial packet until all packets in the plurality of packets are received, the RAN 110 may determine one or more communication parameters (e.g., PER and / or PDB) for communicating the initial packet in accordance with a target metric (e.g., FER / FDB) of a corresponding file so that the initial packet is configured to reach its target destination. For example, the RAN 110 may transmit any initially received packet at a less stringent PER and / or PDB. In this case, the RAN 110 gradually increases the one or more communication parameters of the packet to ensure that the packet group is communicated in accordance with the FER / FDB of the corresponding file. It should be noted that while the foregoing generally provides a description of operations from the perspective of the RAN 110, aspects of the same operations also apply to other network nodes, including the CN 504 and the UE 120.

[0077] For example, still referring to Figure 7 , UE 120 may communicate with application client 710 (e.g., Figure 5 540). The application client 710 may communicate an uplink file 712 to the UE 120, as illustrated. As with the downlink file 714 described above, the uplink file 712 may include a plurality of packets, each of which includes an indicator configured to identify the uplink file to which the packet belongs. The UE 120 may then communicate the uplink file 712 to, for example, the RAN 110 or the AS 140 using the same methods and techniques described above with reference to the RAN 110 communicating the downlink file.

[0078] However, it should be noted that the RAN 110 may receive the uplink file information 718 from the CN 504. In this example, the AF 524 may generate the uplink file information 718 and communicate the uplink file information 718 to the RAN 110 via the CN 504. In this example, the AMF 702 may communicate the uplink file information 718 to the RAN 110. In some examples, the uplink file information 718 includes a target metric (e.g., a QoS requirement (such as a FER or FDB)) for the uplink file 712 identified by each of the plurality of packets.

[0079] In one example, if the UE 120 receives the uplink file 712 from the application client 710, the UE 120 may request uplink resources for communicating the uplink file 712 to the RAN 110. Since the RAN 110 receives the uplink file information 718, the RAN 110 may determine and reserve uplink resources required for the UE 120 to communicate the uplink file 712 to the RAN 110 or the CN 504 based on the target metric of the uplink file 712. Once the RAN 110 or the CN 504 has received the uplink file 712 from the UE 120, the RAN 110 or the CN 504 may determine communication parameters for communicating the uplink file 712 to the AS 140.

[0080] In another example, if the CN 504 (e.g., the UPF 706) receives the downlink file 714 from the DN 522, the CN 504 may determine the communication parameters for communicating the downlink file 714 to the RAN 110 or the UE 120 based on the target metric of the downlink file 714 provided by the downlink file information 716. Once the RAN 110 receives the downlink file, the RAN may determine the communication parameters for communicating the downlink file 714 to the UE 120 based on the target metric of the downlink file 714 provided by the downlink file information 716.

[0081] Example Techniques for Grouping Packets in File Aware Communications

[0082] As indicated above, one or more aspects of the present disclosure provide communication interoperability between XR applications and 5G systems to ensure latency and / or reliability requirements that vary from XR application to XR application in the 5G system. As discussed above, the 5G system can group multiple packets based on the files to which the multiple packets correspond. Here, the files are associated with one or more target metrics regarding QoS, so the nodes in the 5G system will group the multiple packets based on the corresponding files and determine the communication parameters for communicating the multiple packets based on these target metrics.

[0083] Certain aspects of the present disclosure also describe grouping packets according to one or both of corresponding files and specific types of files. In some examples, a file may be one of a plurality of different types, where each file type corresponds to a latency and / or reliability requirement for the file. Here, these different types of files may benefit from having multiple latency and / or reliability targets that are distinct from one another. For example, a frame may be communicated between an XR application and a 5G system, where the frame contains one or more files. Here, different frames may be compressed at different levels of importance. Thus, the files in each frame may be associated with a certain file type depending on, for example, the importance level and / or compression type of the frame.

[0084] In one example, the three types of frames used for video compression include I-frames (intra-coded type), P-frames (predictive type), and B-frames (bi-directional predictive type). Generally speaking, an I-frame may include a complete video frame or image, such as a JPG or BMP image file. In contrast, a P-frame may include only the changes in the image compared to the previous frame. For example, only the parts of the image that have changed since the previous frame are encoded, and the unchanged pixels in the frame (e.g., the background) are not stored by the encoder, thereby saving space. B-frames save even more space by specifying their content using the difference between the current frame and both the previous and next frames.

[0085] As described above, some frames and files contained in frames of XR applications may have different latency and reliability requirements, depending on the frame type associated with each file. For example, the latency requirement of a file in a first frame may be lower than the latency requirement of another file in a second frame. In general, latency refers to the delay associated with receiving data at the intended destination of the data, and can be quantified by FDB / PDB metrics. In some configurations, files of a frame may include data with relatively high reliability requirements. For example, the reliability requirement of a file in a first type of frame may be higher than the reliability requirement of a file in a second type of frame. In general, reliability refers to the degree of consistency in which the intended destination successfully and error-free receives the data, and can be quantified by the FER / PER metric.

[0086] Return to reference Figure 7 , the RAN 110 may receive a downlink file 714 including a plurality of packets and downlink file information 716 that identifies a file of which each packet in the plurality of packets is a part and a file type (e.g., a compression type used for a frame of which the file is a part, or whether the file is part of an I frame, a P frame, or a B frame). The downlink file information 716 may be generated by the AF 524 and communicated to the RAN 110 via the CN 504.

[0087] For example, the downlink profile information 716 may be received by a policy control function (PCF) or a network exposure function (NEF) of the CN 504. In some examples, the PCF / NEF 704 communicates the downlink profile information 716 to a session management function (SMF) 708, which then passes the downlink profile information 716 to an access and mobility management function (AMF). The RAN 110 may receive the downlink profile information 716 in a transmission from the AMF 702.

[0088] In certain aspects, the RAN 110 may be configured to use the received downlink file information 716 to determine the file type (e.g., Figure 6 1, where file 1 has a particular file type). In this case, RAN 110 may determine one or more target metrics (e.g., FER and / or FDB) associated with the file based on the file type. In one example, downlink file information 716 may include a mapping between the file type and the target metric for communicating the file.

[0089] In certain aspects, the RAN 110 may be configured to group the plurality of packets according to files identified by the plurality of packets received from the AS 140 and / or file types identified by the plurality of packets. Here, the RAN 110 may determine one or more target metrics associated with each of the plurality of packets based on the determined file types of the files to which the plurality of packets correspond, and then determine one or more communication metrics for communicating the plurality of packets according to the target metrics of the determined file types. For example, the RAN 110 may transmit downlink packets received from the AS 140 via the CN 504 to the UE 120 according to the determined communication metrics, so that the downlink packets are communicated using the target metrics corresponding to the file types of the files to which the downlink packets belong.

[0090] Similarly, the RAN 110 may transmit uplink packets received from the application client 710 via the UE 120 to the AS 140 via the CN 504 based on the determined communication metric, so that the uplink packets are communicated using a target metric corresponding to the file type of the file to which the uplink packets belong. In this example, the RAN 110 may provide the UE 120 with uplink resources for communicating the uplink packets to the RAN 110 based on the target metric corresponding to the file type. Thus, in some aspects, the UE 120 may be configured to group the multiple packets received from the application client 710 into files based on the file type associated with the file to which each packet belongs. The RAN 110 may then determine one or more target metrics associated with each packet in the multiple packets based on the determined file type, and provide the UE 120 with resources for communicating the multiple packets based on the one or more target metrics.

[0091] Figure 8 800 for wireless communications in accordance with certain aspects of the present disclosure. Operations 800 may be performed, for example, by a radio access network (RAN), such as a BS (e.g., BS 110 in wireless communication network 100) or a user equipment (UE) (e.g., UE 120 in wireless communication network 100). Operations 800 may be implemented as a processor (e.g., Fig.10 In addition, the communication (eg, transmission and reception) of signals in operation 800 may be performed, for example, by one or more antennas (eg, Fig.10 In some aspects, the transmission and reception of signals may be implemented via a bus interface of one or more processors (eg, controller / processor 1040) that obtain and / or output signals.

[0092] Operations 800 may begin at block 805 by determining one or more target metrics associated with a file having a plurality of packets, the plurality of packets including at least one of a plurality of uplink packets or a plurality of downlink packets. For example, the one or more target metrics may include at least one of a target file error rate (FER) associated with the file or a target file delay budget (FDB) associated with the file.

[0093] Operations 800 may proceed at block 810 to determine one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file.

[0094] Operations may proceed at block 815 to communicate the plurality of packets with the second network entity in accordance with the determined one or more communication parameters.

[0095] In certain aspects, operations 800 may include communicating each of the plurality of downlink packets in accordance with the one or more communication parameters.In certain aspects, communicating the plurality of downlink packets may include transmitting the plurality of downlink packets to a user equipment (UE).

[0096] In certain aspects, determining one or more communication parameters for communicating the multiple packets based on the one or more target metrics associated with the file may include: configuring a user equipment (UE) to transmit the multiple uplink packets based on the one or more communication parameters, and communicating the multiple uplink packets may include: receiving the multiple uplink packets from the UE based on the one or more communication parameters.

[0097] In certain aspects, each of the plurality of packets includes one or more of a first indicator configured to identify a file and a second indicator configured to identify a type of the file.

[0098] In some aspects, the plurality of groups includes at least the second indicator.In some aspects, operation 800 includes determining one or more target metrics associated with the file, including determining the one or more target metrics associated with a file type of the file.

[0099] In certain aspects, the plurality of groups includes a first indicator and a second indicator, the method further comprising grouping the plurality of groups according to file and file type.

[0100] In certain aspects, the one or more target metrics associated with the file include at least one of a target file error rate (FER) or a target file delay budget (FDB).

[0101] In some aspects, the one or more target metrics include a target file error rate (FER) associated with the file, and wherein determining one or more communication parameters for communicating the plurality of packets further includes: setting a rate adaptation target for communicating each of the plurality of packets to meet the target FER; and setting a number of retransmissions for communicating each of the plurality of packets to meet the target FER.

[0102] In some aspects, the one or more target metrics include a target file delay budget (FDB) associated with the file, and wherein determining one or more communication parameters for communicating the plurality of packets further includes setting a packet delivery deadline for each of the plurality of packets to satisfy the target FDB.

[0103] In certain aspects, determining the one or more target metrics associated with the file includes: receiving downlink file information from a core network, the downlink file information indicating the one or more target metrics associated with the file to which the multiple downlink packets belong, and wherein communicating the multiple packets includes: transmitting the multiple downlink packets to a user equipment (UE).

[0104] In certain aspects, the downlink file information is generated by a data network (DN) external to the core network, and wherein the downlink file information is received via a user plane function (UPF) of the core network.

[0105] In certain aspects, determining the one or more target metrics associated with the file includes receiving uplink file information from a second network entity, the uplink file information indicating the one or more target metrics associated with the file to which the plurality of uplink packets belong.

[0106] In certain aspects, the first network entity is a user equipment (UE) and the second network entity is a radio access network (RAN) node.

[0107] In certain aspects, an indication of the one or more target metrics associated with the file is received from a core network.

[0108] In certain aspects, the indication of the one or more target metrics is received from an application function via a core network.

[0109] Fig. 9 The description may include a method configured to perform operations for the techniques disclosed herein (such as Figure 8 900 includes a communication device 900 including various components (e.g., corresponding to means-plus-function components) of the operations illustrated in the foregoing. The communication device 900 includes a processing system 902 coupled to a transceiver 908. The transceiver 908 is configured to transmit and receive signals for the communication device 900 (such as various signals as described herein) via an antenna 910. The processing system 902 may be configured to perform processing functions for the communication device 900, including processing signals received by the communication device 900 and / or to be transmitted by the communication device 900.

[0110] The processing system 902 includes a processor 904 coupled to a computer readable medium / memory 912 via a bus 906. In some aspects, the computer readable medium / memory 912 is configured to store instructions (e.g., computer executable code) that, when executed by the processor 904, cause the processor 904 to perform Figure 8 or other operations for performing the various techniques discussed herein.

[0111] In some aspects, computer readable medium / memory 912 stores code 914 for determining one or more target metrics, code 916 for determining one or more communication parameters, and code 918 for communicating a plurality of packets. In some aspects, processor 904 has circuitry configured to implement the code stored in computer readable medium / memory 912. Processor 904 includes circuitry 920 for determining one or more target metrics, circuitry 924 for determining one or more communication parameters, and circuitry 926 for communicating a plurality of packets.

[0112] Fig.10 Explains methods that can be used to implement various aspects of the present disclosure (e.g., Figure 1 100 of an example component 1000 of a BS 110a and a UE 120a in a wireless communication network 100. For example, antenna 1052, processors 1066, 1058, 1064, and / or controller / processor 1080 of UE 120a and / or antenna 1034, processors 1020, 1030, 1038, and / or controller / processor 1040 of BS 110a may be used to perform the various techniques and methods described herein.

[0113] At BS 110a, a transmit processor 1020 may receive data from a data source 1012 and control information from a controller / processor 1040. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a PDCCH, a group common PDCCH (GC PDCCH), etc. The data may be for a PDSCH, etc. The processor 1020 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 1020 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 1030 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide output symbol streams to modulators (MODs) 1032a-1032t. Each modulator 1032 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 1032a-1032t may be transmitted via antennas 1034a-1034t, respectively.

[0114] At UE 120a, antennas 1052a-1052r may receive downlink signals from BS 110a and may provide received signals to demodulators (DEMODs) in transceivers 1054a-1054r, respectively. Each demodulator 1054 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 1056 may obtain received symbols from all demodulators 1054a-1054r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 1058 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to a data sink 1060, and provide decoded control information to a controller / processor 1080.

[0115] On the uplink, at the UE 120a, a transmit processor 1064 may receive and process data from a data source 1062 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 1080 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 1064 may also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 1064 may be precoded by a TX MIMO processor 1066, if applicable, further processed by a demodulator 1054a-1054r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At BS 110a, the uplink signal from UE 120a may be received by antenna 1034, processed by modulator 1032, detected by MIMO detector 1036 if applicable, and further processed by receive processor 1038 to obtain decoded data and control information sent by UE 120a. Receive processor 1038 may provide decoded data to data sink 1039 and decoded control information to controller / processor 1040.

[0116] Memories 1042 and 1082 may store data and program codes for BS 110a and UE 120a, respectively.A scheduler 1044 may schedule UEs for data transmission on the downlink and / or uplink.

[0117] The controller / processor 1080 and / or other processors and modules at the UE 120a may perform or direct the execution of processes for the techniques described herein. Fig.10As shown in , the controller / processor 1040 of BS 110a and the controller / processor 1080 of UE 120 have XR modules ( 112 / 122 , respectively) for serving XR applications using file-level metrics in accordance with various aspects described herein.

[0118] Additional considerations

[0119] Each method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be changed without departing from the scope of the claims.

[0120] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0121] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0122] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one" (unless specifically stated) but "one or more". Unless otherwise specifically stated, the term "some / some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents currently or hereafter known to those of ordinary skill in the art and are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly recorded in the claims. Any element of the claim should not be interpreted under the provisions of 35 U.S.C. § 112 (f), unless the element is explicitly stated using the phrase "device for..." or in the case of a method claim, the element is stated using the phrase "step for...".

[0123] The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These devices may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where there are operations illustrated in the accompanying drawings, these operations may have corresponding paired device-plus-function components with similar numbers.

[0124] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0125] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the user terminal 120 (see Figure 1 ), a user interface (e.g., a keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art and will not be described further. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall system.

[0126] If implemented in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both computer storage media and communication media, which include any media that facilitate the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separated from a wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any part thereof may be integrated into a processor, such as a cache and / or a general register file, which may be the case. As an example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be implemented in a computer program product.

[0127] A software module may include a single instruction, or many instructions, and may be distributed over several different code segments, distributed between different programs, and distributed across multiple storage media. A computer-readable medium may include several software modules. These software modules include instructions that cause a processing system to perform various functions when executed by an apparatus such as a processor. These software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded into a RAM from a hard drive. During the execution of a software module, a processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When describing the functionality of a software module as described below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0128] Any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray Disks, where disks often reproduce data magnetically, and discs reproduce data optically with lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0129] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored (and / or encoded) thereon instructions that can be executed by one or more processors to perform the operations described herein. For example, instructions for performing the operations described herein.

[0130] In addition, it should be appreciated that modules and / or other appropriate means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.) so that once the storage device is coupled to or provided to a user terminal and / or base station, the device can obtain the various methods. In addition, any other suitable technology suitable for providing the methods and techniques described herein to a device may be utilized.

[0131] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various changes, substitutions and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication by a first network entity, comprising: determining one or more target metrics associated with a file having a plurality of packets, the plurality of packets comprising at least one of a plurality of uplink packets or a plurality of downlink packets, wherein the one or more target metrics associated with the file comprise at least one of a target file error rate (FER) or a target file delay budget (FDB); determining one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file; as well as The plurality of packets are communicated with the second network entity in accordance with the determined one or more communication parameters.

2. The method of claim 1, wherein: Each of the plurality of groups includes one or more of a first indicator configured to identify the file and a second indicator configured to identify a file type of the file.

3. The method of claim 2, wherein: The plurality of packets include at least the second indicator; and Determining one or more target metrics associated with the file includes determining the one or more target metrics associated with the file type of the file.

4. The method of claim 2, wherein: The plurality of packets include the first indicator and the second indicator, and the method further includes grouping the plurality of packets according to the file and the file type.

5. The method of claim 1, wherein: The one or more target metrics include the FER associated with the file, and wherein determining one or more communication parameters for communicating the plurality of packets further comprises: setting a rate adaptation target for communicating each packet of the plurality of packets to meet the target FER; and A number of retransmissions for communicating each packet of the plurality of packets is set to meet the target FER.

6. The method of claim 1, wherein: The one or more target metrics include the FDB associated with the file, and wherein determining one or more communication parameters for communicating the plurality of packets further includes setting a packet delivery deadline for each packet in the plurality of packets to satisfy the target FDB.

7. The method of claim 1, wherein: Determining the one or more target metrics associated with the file includes: receiving downlink file information from a core network, the downlink file information indicating the one or more target metrics associated with the file to which the multiple downlink packets belong, and wherein communicating the multiple packets includes: transmitting the multiple downlink packets to a user equipment (UE).

8. The method of claim 7, wherein: The downlink file information is generated by a data network (DN) external to the core network, and wherein the downlink file information is received via a user plane function (UPF) of the core network.

9. The method of claim 1, wherein: Determining the one or more target metrics associated with the file includes receiving uplink file information from the second network entity, the uplink file information indicating the one or more target metrics associated with the file to which the plurality of uplink packets belong.

10. The method of claim 9, wherein: The first network entity is a user equipment (UE) and the second network entity is a radio access network (RAN) node.

11. The method of claim 1, further comprising: An indication of the one or more target metrics associated with the file is received from a core network.

12. The method of claim 11, wherein: The indication of the one or more target metrics is received from an application function via the core network.

13. A first network entity for wireless communication, comprising: Memory; as well as a processor coupled to the memory, the memory and the processor being configured to: determining one or more target metrics associated with a file having a plurality of packets, the plurality of packets comprising at least one of a plurality of uplink packets or a plurality of downlink packets, wherein the one or more target metrics associated with the file comprise at least one of a target file error rate (FER) or a target file delay budget (FDB); determining one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file; as well as The plurality of packets are communicated with the second network entity in accordance with the determined one or more communication parameters.

14. The first network entity according to claim 13, wherein: Each of the plurality of packets includes one or more of a first indicator configured to identify the file and a second indicator configured to identify a type of the file.

15. The first network entity according to claim 14, wherein: The plurality of packets include at least the second indicator; and The memory and the processor configured to determine one or more target metrics associated with the file are further configured to determine the one or more target metrics associated with a file type of the file.

16. The first network entity according to claim 14, wherein: The plurality of packets include the first indicator and the second indicator, and wherein the memory and the processor are further configured to group the plurality of packets according to the file and the file type.

17. The first network entity according to claim 13, wherein: The one or more target metrics include the FER associated with the file, and wherein the memory and the processor configured to determine one or more communication parameters for communicating the plurality of packets are further configured to: setting a rate adaptation target for communicating each packet of the plurality of packets to meet the target FER; as well as A number of retransmissions for communicating each packet of the plurality of packets is set to meet the target FER.

18. The first network entity according to claim 13, wherein: The one or more target metrics include the FDB associated with the file, and wherein the memory and the processor configured to determine one or more communication parameters for communicating the plurality of packets are further configured to set a packet delivery deadline for each of the plurality of packets to satisfy the target FDB.

19. The first network entity according to claim 13, wherein: The memory and the processor configured to determine the one or more target metrics associated with the file are further configured to: receive downlink file information from a core network, the downlink file information indicating the one or more target metrics associated with the file to which the plurality of downlink packets belong; and Wherein, the memory and the processor configured to communicate the plurality of packets are further configured to transmit the plurality of downlink packets to a user equipment (UE).

20. The first network entity according to claim 19, wherein: The downlink file information is generated by a data network (DN) external to the core network, and wherein the downlink file information is received via a user plane function (UPF) of the core network.

21. The first network entity of claim 13, wherein: The memory and the processor configured to determine the one or more target metrics associated with the file are further configured to: receive uplink file information from the second network entity, the uplink file information indicating the one or more target metrics associated with the file to which the multiple uplink packets belong.

22. The first network entity of claim 13, wherein: The memory and the processor are further configured to receive, from a core network, an indication of the one or more target metrics associated with the file.

23. The first network entity according to claim 22, wherein: The indication of the one or more target metrics is received from an application function via the core network.

24. A device for wireless communication, comprising: means for determining one or more target metrics associated with a file having a plurality of packets, the plurality of packets comprising at least one of a plurality of uplink packets or a plurality of downlink packets, wherein the one or more target metrics associated with the file comprise at least one of a target file error rate (FER) or a target file delay budget (FDB); means for determining one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file; as well as Means for communicating the plurality of packets with a network entity in accordance with the determined one or more communication parameters.

25. The apparatus of claim 24, wherein: Each of the plurality of packets includes one or more of a first indicator configured to identify the file and a second indicator configured to identify a type of the file.

26. The apparatus of claim 24, wherein: The one or more target metrics include the FER associated with the file, and wherein the means for determining one or more communication parameters for communicating the plurality of packets further comprises: means for setting a rate adaptation target for communicating each packet of the plurality of packets to meet the target FER; and Means for setting a number of retransmissions for communicating each packet of the plurality of packets to meet the target FER.

27. The apparatus of claim 24, wherein: The one or more target metrics include the FDB associated with the file, and wherein means for determining one or more communication parameters for communicating the plurality of packets further comprises means for setting a packet delivery deadline for each of the plurality of packets to satisfy the target FDB.

28. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor of a device, cause the device to perform a method for wireless communication, the method comprising: determining one or more target metrics associated with a file having a plurality of packets, the plurality of packets comprising at least one of a plurality of uplink packets or a plurality of downlink packets, wherein the one or more target metrics associated with the file comprise at least one of a target file error rate (FER) or a target file delay budget (FDB); determining one or more communication parameters for communicating the plurality of packets based on the one or more target metrics associated with the file; as well as The plurality of packets are communicated with a network entity in accordance with the determined one or more communication parameters.

Images