File delivery failure feedback and application feedback
By detecting and feedbacking data packet communication failures between UE and server entities in the wireless communication system, timely processing and adjustment of file delivery failures is realized, the problem of difficulty in fault detection in the prior art is solved, and the service quality is improved System efficiency.
Patent Information
- Application Number
- CN202080040353.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-06-02
- Filing Date
- 2020-06-03
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2040-06-03
AI Technical Summary
The existing wireless communication systems are difficult to effectively detect and feedback faults during file delivery, resulting in a decline in service quality and the inability to timely adjust data communication parameters to reduce faults, affecting user experience and system efficiency.
In a wireless communication system, a corresponding message is generated and sent to the server entity to achieve fault detection and feedback by detecting temporary degradation events and burst rate reductions associated with data packet communication between user equipment (UE) and server entity. mechanism and adjust traffic flow based on feedback to reduce failure occurrence.
Timely detection and feedback of file delivery failures is realized, allowing application servers and user clients to take measures to reduce failures, improve service quality and system efficiency, adapt to different bandwidth needs, and improve user experience.
Smart Images

Figure CN114451003B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Application No. 16 / 890,550, filed on June 2, 2020, which claims priority to U.S. Provisional Application No. 62 / 858,674, filed on June 7, 2019, and U.S. Provisional Application No. 62 / 859,476, filed on June 10, 2019, all of which are assigned to the assignee of this application and are hereby expressly incorporated herein by reference in their entirety.
[0003] background
[0004] Public domain
[0005] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for file delivery failure feedback and application feedback in wireless communication systems.
[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. Summary of the invention
[0011] The systems, methods, and devices of the present disclosure each have several aspects, no single aspect 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 briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," those skilled in the art will understand how the features of the present disclosure provide advantages including application feedback in wireless communication systems, wherein such feedback can implement various actions adapted to the feedback, such as adaptive traffic flow using a desired amount of bandwidth.
[0012] Certain aspects provide a method for wireless communication. The method generally includes communicating files with a user equipment (UE), each of the files having a plurality of packets, determining that a delivery failure has occurred for at least one of the files, and sending a notification of the delivery failure to a server entity.
[0013] Certain aspects provide a method for wireless communication. The method generally includes communicating files with a network entity, each of the files having a plurality of packets, determining that a delivery failure has occurred for at least one of the files, and sending a notification of the delivery failure to an application client.
[0014] Certain aspects provide a method of wireless communication by a network entity. The method generally includes determining a temporary degradation (TD) event associated with data packet communication between a user equipment (UE) and a server entity, generating a message indicating the TD event to the server entity, and sending the message to the server entity.
[0015] Certain aspects provide a method of wireless communications by a network entity. The method generally includes determining a reduction in a burst rate associated with data packet communications between a user equipment (UE) and a server entity, the burst rate comprising a burst rate that a communication link between the UE and the server entity can support, generating a message to the server entity indicating the reduction in the burst rate, and sending the message to the server entity.
[0016] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes a transceiver configured to communicate files with one of a network entity or a user equipment (UE), each of the files having a plurality of packets. The apparatus also includes a processing system configured to determine that a delivery failure has occurred for at least one of the files and to send a notification of the delivery failure to one of an application client or a server entity.
[0017] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes a processing system configured to determine a temporary degradation (TD) event associated with data packet communication between a user equipment (UE) and a server entity, generate a message indicating the TD event to the server entity, and send the message to the server entity. The apparatus also includes a memory coupled to the processing system.
[0018] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes a processing system configured to determine a reduction in a burst rate associated with data packet communication between a user equipment (UE) and a server entity, the burst rate comprising a burst rate that a communication link between the UE and the server entity can support, generate a message to the server entity indicating the reduction in the burst rate, and send the message to the server entity. The apparatus also includes a memory coupled to the processing system.
[0019] Certain aspects provide an apparatus for wireless communications. The apparatus generally includes means for communicating files with one of a network entity or a user equipment (UE), each of the files having a plurality of packets, means for determining that a delivery failure has occurred for at least one of the files, and means for sending a notification of the delivery failure to one of an application client or a server entity.
[0020] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes means for determining a temporary degradation (TD) event associated with data packet communication between a user equipment (UE) and a server entity, means for generating a message indicating the TD event to the server entity, and means for sending the message to the server entity.
[0021] Certain aspects provide an apparatus for wireless communications. The apparatus generally includes means for determining a reduction in a burst rate associated with data packet communications between a user equipment (UE) and a server entity, the burst rate comprising a burst rate that a communication link between the UE and the server entity is capable of supporting, means for generating a message to the server entity indicating the reduction in the burst rate, and means for sending the message to the server entity.
[0022] Certain aspects provide a computer-readable medium having instructions stored thereon for communicating files with one of a network entity or a user equipment (UE), each of the files having a plurality of packets, determining that a delivery failure has occurred for at least one of the files, and sending a notification of the delivery failure to one of an application client or a server entity.
[0023] Certain aspects provide a computer-readable medium having instructions stored thereon for determining a temporary degradation (TD) event associated with data packet communications between a user equipment (UE) and a server entity, generating a message indicating the TD event to the server entity, and sending the message to the server entity.
[0024] Certain aspects provide a computer-readable medium having instructions stored thereon for determining a reduction in a burst rate associated with data packet communications between a user equipment (UE) and a server entity, the burst rate comprising a burst rate that a communication link between the UE and the server entity is capable of supporting, generating a message to the server entity indicating the reduction in the burst rate, and sending the message to the server entity.
[0025] 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
[0027] 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.
[0028] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.
[0029] 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.
[0030] Figure 3 This is a table explaining various fifth generation (5G) quality indicators.
[0031] Figure 4 is a table explaining various use cases of extended reality (XR).
[0032] Figure 5 A wireless communication system for XR is explained.
[0033] Figure 6 Traffic flows for communication of packets associated with various files are illustrated.
[0034] Figure 7 An example XR traffic flow of a file burst with a file delivery failure is illustrated in accordance with certain aspects of the present disclosure.
[0035] Fig. 8A An example feedback path for file delivery failure notification from a RAN to an application function of a server entity is illustrated in accordance with certain aspects of the present disclosure.
[0036] Figure 8B Another example feedback path for file delivery failure notification from a RAN to a data network of a server entity is illustrated in accordance with certain aspects of the present disclosure.
[0037] Figure 8C An example feedback path for file delivery failure notification from a user equipment to an application client is illustrated in accordance with certain aspects of the present disclosure.
[0038] Fig. 9A An example communication flow for notification configuration of downlink file delivery failures is illustrated in accordance with certain aspects of the present disclosure.
[0039] Fig. 9B An example communication flow for notification configuration of uplink file delivery failures is illustrated in accordance with certain aspects of the present disclosure.
[0040] Fig.10 is a call flow diagram illustrating example operations for providing file delivery failure notification on downlink traffic in accordance with certain aspects of the present disclosure.
[0041] Fig.11 is a call flow diagram illustrating example operations for providing file delivery failure notification on uplink traffic in accordance with certain aspects of the present disclosure.
[0042] Fig.12 is a flow diagram illustrating example operations for wireless communications by a network entity in accordance with certain aspects of the present disclosure.
[0043] Fig.13 is a flow diagram illustrating example operations for wireless communications by user equipment in accordance with certain aspects of the present disclosure.
[0044] Fig.14 is a flow diagram illustrating example operations for wireless communications in accordance with certain aspects of the present disclosure.
[0045] Fig.15A and 15B A notification path for indicating a temporary downgrade (TD) event in accordance with certain aspects of the present disclosure is illustrated.
[0046] Fig.16 is a flow diagram illustrating example operations for wireless communications in accordance with certain aspects of the present disclosure.
[0047] Fig.17 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.
[0048] Fig.18is a block diagram conceptually illustrating designs of example base stations and user equipment in accordance with certain aspects of the present disclosure.
[0049] 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.
[0050] Detailed Description
[0051] Various aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for providing file delivery failure feedback and / or application feedback to an application client or server (such as an extended reality (XR) client or server) across a wireless communication system. In some aspects, a radio access network (RAN) may send a delivery failure notification associated with one or more files to a server entity (e.g., an application server). In other aspects, a user equipment (UE) may send a delivery failure notification associated with one or more files to an application client. The notification may adopt various feedback paths as further described herein. As further described herein, the notification may enable an application client or application server to take actions to reduce further delivery failures or correct past delivery failures. In some cases, the RAN may determine a temporary degradation (TD) of communications between a UE and a server entity (e.g., an application server) and provide an indication of the TD to the server entity, thereby allowing the application to adjust the data communication parameters of the application accordingly.
[0052] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure may be performed. The wireless communication network 100 may be a NR system (e.g., a 5G NR network). Figure 1 As shown in , according to various aspects described herein, UE 120a has an application manager 122 that can be configured to provide file-based services (such as XR). As described in more detail herein, BS 110a includes an application manager 112 for providing file-based services (such as XR). In some cases, the application manager 112 can be configured to obtain a traffic burst factor (e.g., a burst rate). In certain aspects of the present disclosure, as described in more detail herein, the application manager 112 can provide feedback to an application server (e.g., an edge cloud server or a server entity) indicating a reduction in the burst rate supported by the communication link between the UE and the application server.
[0053] The traffic burst factor (e.g., burst rate) can be defined as a multiplication factor of the GBR associated with a traffic flow (e.g., uplink and / or downlink traffic flow) such that the product of the burst factor multiplied by the GBR is the minimum link rate (e.g., minimum constant link rate) for service coverage. Service coverage is said to be met when the number of packets lost or delayed beyond the PDB associated with the traffic flow is less than the PER associated with the traffic flow. In some examples, the burst factor can be different for uplink and downlink traffic flows.
[0054] The burst factor is associated with the coverage and capacity of the service in the wireless network. For example, different traffic flows associated with different traffic burst factors can achieve different levels of service coverage.
[0055] Radio access network (RAN) 150 may include BS 110 and / or network controller 160. Figure 2 Discussed in greater detail, the RAN 150 may be in communication with a core network (CN) 130 and an application server 140 .
[0056] 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., application server 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 of an application-related service (e.g., requesting BS 110a to serve as a link between UE 120a and AS 140).
[0057] like Figure 1 As illustrated in FIG. 1 , a wireless communication network 100 may include a number of base stations (BSs) 110 and other network entities. Figure 1 In the example shown in , 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 (e.g., three) cells. The wireless communication network 100 may also include relay stations. In Figure 1 In the example shown in , a relay station 110r may communicate with a BS 110a and a UE 120r to facilitate communication between the BS 110a and the UE 120r. A relay station may also be referred to as a relay BS, a relay, or the like.
[0058] UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless communication network 100, and each UE may be stationary or mobile. 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.
[0059] A network controller 160 may couple to a set of BSs and provide coordination and control for the BSs. The network controller 160 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other (eg, directly or indirectly) via a wireless or wired backhaul.
[0060] Figure 2 is an illustration of a method for communicating with the RAN 150 and the AS 202 (eg, Figure 1 AS 140 in the CN 200 (for example, Figure 1 A block diagram of an example architecture of a CN 130 in FIG. Figure 2 As 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).
[0061] 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 example CN 200, 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).
[0062] 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; communication between UE 120 and location service management (LMF) and the 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.
[0063] 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: a unified policy framework, providing policy rules for controlling protocol functions and / or accessing subscription information for policy decisions in the UDR. 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.
[0064] NEF 206 can support: opening of capabilities and events, secure provision of information from external applications to 3GPP network, translation of internal / external information. AF 214 can support: application influence on traffic routing, access to NEF 206 and / or interaction with policy framework for policy control. Figure 2As shown in FIG, CN 200 may communicate with AS 202, UE 120, RAN 150, and DN 228. In some examples, CN 200 communicates with external AS 202 via NEF 206 and / or AF 214.
[0065] A communication system, such as a wireless communication network 100, may provide communication services to a UE 120. For example, 5G NR may support services such as enhanced mobile broadband (eMBB) services targeting wide bandwidth (e.g., 80 megahertz (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.
[0066] The traffic requirements of a service may be summarized by a set of parameters (e.g., QoS parameters) and associated with a traffic flow supporting the service. These parameters may include a packet error rate (PER), a packet delay budget (PDB), and / or a guaranteed bit rate (GBR) (not shown). PER may be a ratio of successfully received packets in a percentage form. For example, PER may define an upper limit on the ratio of PDUs (e.g., IP packets) that have been processed by a sender of a link layer protocol (e.g., RLC in a RAN accessed by 3GPP) but have not been successfully delivered to an upper layer (e.g., PDCP in a RAN accessed by 3GPP) by a corresponding receiver. Thus, PER may define an upper limit on a non-congestion related packet loss rate. PDB may be defined as an upper limit on the time that a packet may be delayed between a UE (e.g., UE 120) and a UPF (e.g., UPF 226) on the CN side. GBR may indicate a bandwidth (bit rate) guaranteed by the network.
[0067] The resource type determines 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), while non-GBR QoS flows may be pre-authorized via static policy and charging control. GBR QoS flows may use a GBR resource type or a delay-critical GBR resource type. For traffic flows of type "delay-critical GBR" (e.g., for URLLC traffic flows), a parameter called the maximum data burst volume (MDBV) is specified to describe the traffic burst. The MDBV represents the maximum amount of data that the 5G-AN is required to serve within a 5G-AN PDB (e.g., the 5G-AN portion of the PDB) period. The MDBV may be signaled to the RAN 150 along with a standardized indicator value (e.g., 5QI) and, if received, should be used instead of a default value.
[0068] Figure 3 Table 300 in shows example QoS parameters that may be configured for various services. 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 a person or computer, such as a remote driver or V2X application for operating a remote vehicle without a driver or a remote vehicle located in a dangerous environment) may be associated with URLCC. 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 a person, 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. Figure 3 The QoS parameters and services shown in table 300 are merely illustrative, and various other QoS parameters and services may be specified.
[0069] At high PDB values (e.g., equal to or exceeding 100 ms (milliseconds)), traffic bursts that exceed 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. Therefore, for such traffic flows, it may not be important to communicate 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.
[0070] As mentioned above, MDBV is specified for "delay-critical GBR" type traffic flows, which are expected to handle low-throughput traffic. Therefore, in some cases, the MDBV value range is capped at 4095 bytes (for example, when transmitting signals on a 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 lower on traffic flows with larger PDB values. However, for some services, such as XR services (e.g., AR, VR, cloud gaming), throughput requirements (e.g., up to 8250Mbps) and PDB requirements (e.g., 25ms) may be higher.
[0071] Sample file delivery failure feedback
[0072] New Radio (NR) is an emerging wireless communication technology being developed in collaboration with the 5G Technical Forum (5GTF). NR access (e.g., 5G NR) can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or higher), 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 and reliability requirements and may also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. Extended Reality (XR) may include a variety of services (e.g., cloud gaming, split rendering, split computing, virtual reality (VR), augmented reality (AR), or mixed reality (MR)) that use low latency (e.g., packet delay budget (PDB) between 5 ms and 25 ms) communications with highly reliable bit rates (e.g., packet error rate less than or equal to 1e-3).
[0073] Figure 4 4 is a table 400 illustrating various use cases for XR. For example, XR traffic flow policies (e.g., latency and reliability requirements) may be used for cloud gaming, VR split rendering, or AR split computing. Cloud gaming generally refers to gaming on a user device, where at least some graphics processor unit (GPU) processing is performed on a cloud server that may implement a more powerful GPU. Similarly, GPU processing for VR and AR may be split between a GPU on the cloud and a GPU on the user device. However, cloud gaming, split rendering, and split computing services use low latency communications to maintain an acceptable gaming or virtual experience. As illustrated, cloud gaming may 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.
[0074] Figure 5A wireless communication system 500 for XR is illustrated. As illustrated, a 5G system 502 may include a UE 120, a RAN 150, and a core network (CN) 504. In some aspects, the 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 520, 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 near 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 520 may be associated with an XR public cloud AF 530. The CN 506 may communicate with the XR edge DN via an N6 interface (user plane). In addition, CN 504 can communicate with XR edge AF via N5 and N33 interfaces. N5 and N33 are the interfaces of XR edge application function 524 to 5G system.
[0075] Figure 6 Traffic flow 600 for communication of packets associated with various files is illustrated. For example, packets 602, 604, 606 may be associated with a file (e.g., file 1), while 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 generally refers to a group of packets processed jointly by an application. Files may be decomposed into packets according to a maximum transmission unit (MTU) setting on a stack interfaced with an application. Packets may be further segmented into smaller packet segments. A burst generally refers to one or more files generated by an application at approximately the same time. Traffic flow 600 may be associated with a certain guaranteed bit rate (GBR) (also referred to as a guaranteed flow bit rate (GFBR)) that may be preconfigured by RAN 110. In addition, a traffic flow may be associated with a packet delay budget (PDB) and a packet error rate (PER).In some cases, the delivery deadline of a packet may be approximately equal to the time of arrival (ToA) of the packet plus the PDB of the traffic flow to which the packet belongs.
[0076] 5G wireless communication systems may only be aware of packet-level metrics. In other words, traffic flows may be specified by packet filters and by metrics of PER and PDB. However, XR applications may specify metrics for groups of packets (e.g., files). For example, an XR application may specify a file error rate (FER) instead of a PER. In addition, the reliability requirements for files may be different. For example, the reliability requirements for intra-coded frames (I frames) and predicted frames (P frames) on an XR traffic flow may be different. In some cases, an XR application may specify policies related to file handling. For example, an 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 until the first erroneous packet can be used.
[0077] When file-level metrics (such as FER) are converted to packet-level metrics (such as PER for 5G systems), information may be lost, resulting in inaccurate handling of the file-level requirements of the application. As an example, an application may not have file-level delivery failure information related to XR traffic from downlink traffic (e.g., from RAN to UE) or uplink traffic (e.g., from UE to RAN) unless the application implements application client feedback. However, file delivery failure feedback over the air may be delayed, which may hinder the latency of traffic flows and introduce additional uplink traffic, which may reduce the bandwidth capacity and bit rate reliability of the wireless communication system.
[0078] Certain aspects of the present disclosure generally relate to techniques for providing services for XR applications using file-level metrics, such as providing file delivery failure feedback to an application client or server. In some aspects, the RAN may send a delivery failure notification associated with one or more files to a server entity (e.g., an edge cloud server 520). In other aspects, the UE may send a delivery failure notification associated with one or more files to an application client. The notification may enable the application client or server entity to take actions to reduce further delivery failures or correct past delivery failures. For example, if a server entity receives a delivery failure notification, the server entity may adjust the compression scheme of the traffic flow to reduce the possibility of further delivery failures (i.e., increase the possibility of successful delivery). As an example, the server entity may change from a compression scheme of only predicted frames (P frames) to a compression scheme including P frames and on-demand intra-coded frames (I frames) based on the feedback notification described herein. In some cases, an IPPP frame stream may use a bandwidth of at least 100 Mbps, while a traffic stream adapted to the delivery feedback described herein may use a bandwidth of at least 80 Mbps, thereby significantly reducing the bandwidth of the application traffic stream. In other words, various techniques for file delivery failure notifications may enable adaptive traffic flows using the desired amount of bandwidth.
[0079] Figure 7An example XR traffic flow 700 for file communication in accordance with certain aspects of the present disclosure is illustrated. As shown, the traffic flow 700 may be communicated via bursts 702, 704, 706, 708, 710, 712 including one or more files 714, which may include multiple packets as previously described herein.
[0080] Assuming that the traffic flow is downlink traffic from the RAN to the UE, the RAN may determine that a delivery failure of the file 716 has occurred in the second burst 704. In response to the delivery failure, the RAN may generate a notification 720 including one or more file identifiers 722 associated with the file(s) experiencing the delivery failure. That is, the RAN may generate the notification on a per-file basis or on a file group basis. As further described herein, the RAN may send the notification to a server entity.
[0081] The application server (e.g., cloud edge server 520) can take various actions in response to the notification. For example, in response to the notification, the application server can change the compression scheme as indicated by file 718 in fifth burst 710. File 718 can use a different type of compression scheme (e.g., I-frame or P-frame) relative to other files in traffic flow 700.
[0082] Traffic flow 700 may also apply to uplink traffic flow from UE to RAN.For example, the UE may send notification 720 to the application client, and the application client may take various actions in response to the notification.
[0083] Fig. 8A An example feedback path of a file delivery failure notification from the RAN 150 to an application function of a server entity in accordance with certain aspects of the present disclosure is illustrated. As shown, the RAN 150 may send one or more notifications to the application via logical functions of the core network 504 including a policy control function (PCF) 804, a session management function (SMF) 806, and an access and mobility management function (AMF) 808. For example, the notification may be sent from the RAN to the AMF 808, from the AMF 808 to the SMF 806, and from the PCF 804 to the AF 524 of the server entity. Fig. 8A The feedback path depicted in the example can use the Nef interface, such as to Figure 2 The NEF 206 communications link. Fig. 8A The feedback path depicted in can be a QoS feedback path for communicating quality of service (QoS) feedback to AF 524.
[0084] Figure 8BAnother example feedback path of a file delivery failure notification from the RAN 150 to a server entity via a user plane function according to certain aspects of the present disclosure is illustrated. As shown, the RAN 150 may send one or more notifications to the core network 504 having a logical function (such as, the user plane function 810), and the core network 504 may forward the notification to the data network 522 of the server entity. The communication flow through the UPF 810 avoids the AF 802 having to forward the feedback to the data network 522, which may result in reduced delays in notifying the data network 522 of the delivery failure. The RAN 150 may send notifications to the UPF 810 via a feedback interface 820, and the UPF 810 may send notifications to the data network 522 via another feedback interface 822. The feedback interfaces 820 and 822 may be separate interfaces dedicated to delivering feedback from the RAN to the data network.
[0085] Figure 8C 8 illustrates an example feedback path for file delivery failure notification from UE 120 to application client 812 according to certain aspects of the present disclosure. As shown, for example, Figure 7 As shown in , UE 120 can determine that a file delivery occurs on a traffic flow, and UE 120 can send a notification of the file delivery to application client 812, which can be a software component executed and running on one or more processors of the UE.
[0086] In some aspects, the application function of the server entity can configure notifications for file delivery failure feedback. The configuration can be specified for uplink file delivery failure, downlink file delivery failure, or a combination thereof. For example, Fig. 9A An example communication flow for configuration of notifications for downlink file delivery failures according to certain aspects of the present disclosure is illustrated. As shown, an application function 524 of a server entity may send a configuration for notifications to the RAN 150 via the core network 504. The core network 504 may forward the configuration via logical functions including the PCF 804, the SMF 806, and the AMF 808. In certain aspects, the configuration may be sent from the AF 524 of the server entity to the PCF 804, from the PCF 804 to the SMF 806, and from the AMF 808 to the RAN 150. In various aspects, the server entity may specify that notifications are to be sent on a per-file basis or grouped with multiple file failures, as described herein with respect to Figure 7 That is, the configuration may indicate that a notification is sent each time a delivery failure of a file or each time a delivery failure of a group of files occurs. The configuration may indicate to the RAN 150 whether to use Fig. 8A The feedback path shown in Figure 8BThat is, the configuration may indicate the AF to the server entity for the notification (e.g., Fig. 8A ) or via the UPF of the core network to the data network (e.g., as depicted in Figure 8B ) feedback path depicted in .
[0087] For uplink traffic feedback, the server entity may send an indication of the configuration to the UE. For example, Fig. 9B An example communication flow for notification configuration for uplink file delivery failure according to certain aspects of the present disclosure is illustrated. As shown, the application function 524 of the server entity can send a configuration for notification to the UE 120. The application function 524 can send the configuration via a logical function including the PCF 804, the SMF 806, and the AMF 808. In certain aspects, the configuration can be sent from the AF 524 to the PCF 804, from the PCF 804 to the SMF 806, and from the AMF 808 to the UE 120. In various aspects, the configuration can indicate that a notification is sent at each delivery failure of a file or at each delivery failure of a group of files.
[0088] Fig.10 1 is a call flow diagram illustrating example operations 1000 for providing file delivery failure notification on downlink traffic in accordance with certain aspects of the present disclosure. At 1002, server entity 520 may send a notification configuration to RAN 150 via core network 504, as described herein with respect to Fig. 9A At 1004, the server entity 520 may communicate the application traffic (e.g., traffic flow 700) to the core network 504, which may forward the traffic to the RAN 150 at 1006. At 1008, the RAN may transmit the application traffic to the UE 120. Downlink transmission of the application traffic may continue in the remainder of the operations 1000.
[0089] At 1010, the RAN 150 may determine that a delivery failure has occurred for one or more files being delivered on application traffic. For example, the RAN 150 may determine that a delivery failure has occurred between the CN 504 and the RAN 150 or between the RAN 150 and the UE 120. At 1012, the RAN 150 may send a file delivery failure notification to the core network 504. In various aspects, the RAN 150 may generate a notification based on the configuration received at 1002. At 1014, the core network 504 may forward the notification to the server entity 520, as described herein with respect to Fig. 8A and 8B The server entity 520 may then take various actions to correct the delivery failure or reduce future delivery failures, such as by resending the file(s) and / or changing the compression scheme for the application traffic.
[0090] Fig.11 1 is a call flow diagram illustrating example operations 1100 for providing file delivery failure notification on uplink traffic in accordance with certain aspects of the present disclosure. As shown, at 1102, server entity 520 may send a notification configuration to UE 120, as described herein with respect to Fig. 9B At 1104, UE 120 may transmit application traffic (e.g., traffic flow 700) to RAN 150. At 1106, RAN 150 may forward the application traffic to core network 504, which may also forward the application traffic to server entity 520 at 1108 (e.g., via UPF). Uplink transmission of application traffic may continue in the remainder of operation 1100.
[0091] At 1110, UE 120 may determine that a delivery failure has occurred for one or more files being communicated on application traffic. For example, UE 120 may determine that a delivery failure has occurred between RAN 150 and UE 120. At 1112, UE 120 may send a file delivery failure notification to an application client. In various aspects, UE 120 may generate a notification based on the configuration received at 1102. The application client may then take various actions, such as by resending the file(s) and / or changing the compression scheme for the application traffic, to correct the delivery failure or reduce future delivery failures.
[0092] Fig.12 1 is a flow diagram illustrating example operations 1200 for wireless communications by a network entity in accordance with certain aspects of the present disclosure. Operations 1200 may be performed, for example, by a network entity (e.g., RAN 150 or BS 110). Operations 1200 may be implemented as a processor on one or more processors (e.g., Fig.18 Further, the signal transmission and reception by the network entity in operation 1200 may be performed by one or more antennas (e.g., Fig.18 In some aspects, the transmission and / or reception of signals by a network entity may be implemented via a bus interface of one or more processors (eg, controller / processor 1840) that obtain and / or output signals.
[0093] Operations 1200 may begin at 1202, where a network entity may communicate files (e.g., traffic flow 700) with a UE (e.g., UE 120), each of the files having a plurality of packets. At 1204, the network entity may determine that a delivery failure has occurred for at least one of the files. At 1206, the network entity may send a notification (e.g., notification 720) of the delivery failure to a server entity (e.g., edge cloud server 520).
[0094] In various aspects, the notification may indicate a file identifier associated with the file for which the delivery failure occurred (e.g., file identifier 722). The notification may be for a group of files, wherein the notification indicates an identifier for each file in the group. That is, the notification may indicate that a delivery failure occurred for a group of files that includes at least one of the files determined at 1204, and the notification may further indicate a file identifier for each file in the group.
[0095] According to certain aspects, as described herein with respect to FIG. 9 , the server entity may configure file delivery failure feedback. For example, operation 1200 may further include the network entity receiving a configuration for notifications from the server entity and generating notifications according to the configuration. The configuration may indicate that a notification is sent upon each delivery failure of a file or upon each delivery failure of a group of files. As an example, if the configuration specifies group-based feedback, the network entity may only generate a notification after multiple file delivery failures are identified. As described herein with respect to FIG. Fig. 9A As described, the network entity may receive the configuration from the server entity. That is, the network entity may receive the configuration from the application function (AF) of the server entity. In various aspects, the network entity may receive the configuration from the AF via a policy control function (PCF) of the core network, a session management function (SMF) of the core network, and an access and mobility management function (AMF) of the core network.
[0096] In various aspects, the delivery of the file at 1202 may include delivering downlink traffic to the UE. Fig.10 As described, a network entity may generate a file for transmission and transmit the file to a UE.
[0097] At 1204, the network entity may determine that a delivery failure has occurred between a downlink communication link from the RAN to the UE, for example, based on the network entity receiving a negative acknowledgement (NACK) associated with a packet in the file. At 1204, the network entity may determine that a delivery failure has occurred between a backhaul communication link from the server entity to the RAN via the core network based on a file identifier in a packet of the traffic flow.
[0098] The network entity may use various feedback paths to send feedback at 1206. For example, as described herein with respect to Fig. 8AAs described, the network entity may send a notification to the AF of the server entity. In aspect, the network entity may send a notification to the AF (e.g., AF 524) via a logical function of the core network, the logical function of the core network including an AMF of the core network (e.g., AMF 808), an SMF of the core network (e.g., SMF 806), and a PCF of the core network (e.g., PCF 804). The notification may be sent via a QoS notification (e.g., notification 720) over a QoS feedback path, the QoS notification having a field (e.g., file identifier 722) indicating a delivery failure for at least one of the files.
[0099] In other respects, such as this article on Figure 8B As described, the network entity may send a notification to the data network of the server entity via a UPF (e.g., UPF 810). The network entity may send the notification to the data network via a message including a notification (e.g., notification 720) and via an interface communicating with the data network (e.g., feedback interfaces 820 and 822).
[0100] Fig.13 1 is a flow diagram illustrating example operations 1300 for wireless communications by a user equipment in accordance with certain aspects of the present disclosure. Operations 1300 may be performed, for example, by a UE (e.g., UE 120). Operations 1300 may be complementary to operations 1200 performed by a network entity. Operations 1300 may be implemented as a processor on one or more processors (e.g., Fig.18 In addition, signal transmission and reception by the UE in operation 1300 may be performed by one or more antennas (e.g., Fig.18 In some aspects, the transmission and / or reception of signals by the UE may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 1880).
[0101] Operations 1300 may begin at 1302, where a UE may communicate files (e.g., traffic flow 700) with a network entity (e.g., RAN 150 or BS 110), each of the files having a plurality of packets. At 1304, the UE may determine that a delivery failure has occurred for at least one of the files. At 1306, the UE may send a notification of the delivery failure to an application client.
[0102] In various aspects, the notification may indicate a file identifier associated with the file for which the delivery failure occurred (e.g., file identifier 722). The notification may be for a group of files, wherein the notification indicates an identifier for each file in the group. That is, the notification may indicate that a delivery failure occurred for a group of files that includes at least one of the files determined at 1204, and the notification may further indicate a file identifier for each file in the group.
[0103] According to certain aspects, as described herein with respect to Fig. 9B As described, the server entity may configure file delivery failure feedback. In some aspects, the configuration may be specified for uplink traffic feedback. The configuration may indicate that a notification is sent each time a file delivery failure occurs or each time a file group delivery failure occurs. Operation 1300 may further include the UE receiving a configuration for the notification from the server entity, and the UE may generate a notification based on the configuration. In various aspects, the UE may receive the configuration from an application function (AF) of the server entity. In some aspects, the UE may receive the configuration from the AF via a policy control function (PCF) of the core network, a session management function (SMF) of the core network, and an access and mobility management function (AMF) of the core network. As an example, if the configuration specifies group-based feedback, the UE may only generate a notification after multiple file delivery failures are identified.
[0104] In various aspects, the delivery of the file at 1302 may include delivering uplink traffic to a network entity. Fig.11 As described, the UE may generate a file for transmission and transmit the file to a network entity.
[0105] At 1304, the UE may determine that a delivery failure has occurred between an uplink communication link from the UE to the RAN, for example, based on the UE receiving a NACK associated with a packet in the file. At 1306, the UE may use the information described herein with respect to Figure 8C The feedback path described is used to send notifications.
[0106] Example techniques for providing app feedback
[0107] In some cases, a quality of service (QoS) notification message may be sent from the 5G system to the AF 524. For example, the QoS notification message may be passed from the RAN 110 to the session management function (SMF) of the CN 504, the PCF of the CN 504, the policy control function (PCF) of the CN 504, and the AF 524. In some cases, the QoS notification message may indicate that the preconfigured GFBR can no longer be handled. The 5G system may then be expected to continue serving the traffic flow, waiting for the AF 524 to take further action in response to the QoS notification.
[0108] In certain aspects of the present disclosure, the 5G system may determine a temporary degradation (TD) event associated with data packet communications. For example, a TD event may be associated with a temporary degradation of a target metric such as a preconfigured GFBR, a preconfigured PER, or a preconfigured PDB, as described in more detail herein. In other words, as described in more detail herein, instead of simply indicating that a preconfigured metric (such as GFBR) can no longer be processed, the RAN may instead indicate a TD associated with the preconfigured metric, and optionally, a duration associated with the TD event. In various aspects, TD event feedback may enable the AF or DN to take various actions to mitigate service degradation at the UE, such as changing the compression scheme of the traffic flow, reducing the application bit rate, and the like.
[0109] Fig.14 1400 is a flow diagram illustrating example operations 1400 for wireless communication in accordance with certain aspects of the present disclosure. Operations 1400 may be performed, for example, by a radio access network (RAN), such as a BS (e.g., BS 110 in wireless communication network 100) and / or a network controller (e.g., network controller 160). Operations 1400 may be implemented as a processor (e.g., Fig.18 In addition, signal transmission and reception by the BS in operation 1400 may be performed by one or more antennas (e.g., Fig.18 In some aspects, the transmission and / or reception of signals by the BS may be implemented via a bus interface of one or more processors (eg, controller / processor 1840) that obtain and / or output signals.
[0110] At block 1402, operation 1400 may start by determining, by the RAN, a TD event associated with data packet communication between the UE and a server entity (e.g., an edge cloud server 520). In some aspects, the TD event may be associated with a TD of at least one of a preconfigured GFBR, a preconfigured PER, or a preconfigured PDB. In some aspects, the TD event may be associated with a TD of at least one of a preconfigured GFBR, a preconfigured file error rate (FER), or a preconfigured file delay budget (FDB). As described herein, one or more packets may be associated with a file. In contrast to PER, which refers to an error rate at the packet level, FER generally refers to an error rate associated with a file. Similarly, in contrast to PDB, which refers to a delay budget of a packet, FDB generally refers to a delay budget associated with a file. For example, a TD event may be associated with at least one of a temporarily higher PDB (or FDB) for data packet communication, a temporarily higher PER (or FER) for data packet communication, or a temporarily higher GFBR for data packet communication.
[0111] In box 1404, the RAN generates a message (e.g., a QoS notification message) indicating a TD event to the server entity, and in box 1406, the RAN sends the message to the server entity. In some aspects, the message may indicate a duration associated with the TD event. In some cases, the message may indicate the start time of the TD event. For example, when a network entity (e.g., RAN 110) and a server entity (e.g., edge cloud server 520) operate using a common clock or using a synchronized clock, the start time of the TD event may be indicated. In other words, when the RAN and the edge cloud server operate using a common clock or a synchronized clock, the timestamp indicating the start of the TD event communicated by the RAN 110 may be correctly processed by the edge cloud server 520.
[0112] In some aspects, the message may be sent prior to the start of a TD event. In other words, a TD event may be anticipated or predicted based on one or more TD event triggering conditions. For example, a TD event triggering condition may include a mobility event (e.g., a UE switching from one cell to another) or an overheating condition (e.g., a UE overheating due to increased power usage that may be indicated by the UE to the RAN). In response to an indication of a TD event, the application may do nothing if the user experience degradation is acceptable during the duration of the TD event, or may temporarily reduce the application bit rate (e.g., for the duration of the TD event).
[0113] Fig.15A and 15B A notification path for indicating a TD event according to certain aspects of the present disclosure is illustrated. Fig.15A As illustrated, a message conveying a TD event (e.g., a QoS notification message) may be indicated by the RAN 110 to the AF 524 via the session management function (SMF) 1502 of the CN 504 and via the policy control function (PCF) 1504 of the CN 504, as illustrated. The TD event indicated to the AF 524 may also be communicated by the AF 524 to the DN 522 for managing applications based on the communicated TD event. Fig. 15B As illustrated in , a message conveying a TD event (eg, a QoS notification message) may be indicated to the DN 522 via the user plane function (UPF) 1510 of the CN 504.
[0114] Fig.16 1 is a flow diagram illustrating example operations 1600 for wireless communication in accordance with certain aspects of the present disclosure. Operations 1600 may be performed, for example, by a radio access network (RAN), such as a BS (e.g., BS 110 in wireless communication network 100) and / or a network controller (e.g., network controller 160). Operations 1600 may be implemented as a processor (e.g., Fig.18 In addition, signal transmission and reception by the BS in operation 1600 may be performed by, for example, one or more antennas (e.g., Fig.18 In some aspects, the transmission and / or reception of signals by the BS may be implemented via a bus interface of one or more processors (eg, controller / processor 1840) that obtain and / or output signals.
[0115] At block 1602, operations 1600 may begin by the RAN determining a reduction in a burst rate associated with data packet communication between a UE and a server entity, the burst rate comprising a burst rate that a communication link between the UE and the server entity can support. In some cases, the determination of the reduction in the burst rate may include anticipating the reduction in the burst rate based on a mobility event or a heating condition of the UE. In some cases, the reduction in the burst rate may be predicted based on one or more triggering conditions, such as a mobility event or a heating condition of the UE.
[0116] At block 1604, the RAN generates a message (e.g., a QoS notification message) indicating a reduction in the burst rate to the server entity, and at block 1606, the RAN sends the message to the server entity. In certain aspects, the determination of the reduction in the burst rate may include determining a TD event, the reduction in the burst rate being a temporary reduction in a preconfigured burst rate during the TD event.
[0117] In some cases, when the preconfigured GFBR cannot be supported, the supportable GFBR (e.g., associated with the burst rate) may be indicated to the server entity (e.g., edge cloud server). In certain aspects of the present disclosure, the RAN may also indicate whether the determined reduction in the burst rate is a TD event. When the reduction in the burst rate is a TD event, the message may indicate the duration associated with the TD event (e.g., the duration associated with the reduction in the burst rate). When the network entity and the server entity operate using a common clock or operate using a synchronized clock, the message may also indicate the time at which the reduction in the burst rate occurs.
[0118] As about Fig.15A As described, a message (e.g., a QoS notification message) may be indicated by the RAN 110 via the SMF 1502 of the CN 504 and via the PCF 1504 of the CN 504 to the AF 524, as illustrated. Fig. 15BAs explained in , a message (e.g., a QoS notification message) may be indicated to the DN 522 via the UPF 1510 of the CN 504. In response, the application may adjust the peak to the average value of the generated traffic to reduce the required burst rate. For example, for a 10ms PDB, the application may reduce the average value of the burst rate of packets spanning a 10ms time period to the peak burst rate spanning a 10ms time period, thereby effectively reducing the burst rate required for the traffic. Although the examples described herein describe techniques for communicating TD events for a 5G system to facilitate understanding, the techniques described herein may be applied to any of a variety of suitable radio access technologies.
[0119] Fig.17 The description may include operations configured to perform the techniques disclosed herein (such as, Figure 10-13 , 14 and 16) of the communication device 1700 (e.g., BS 110, UE 120 or RAN 150). The communication device 1700 includes a processing system 1702 coupled to a transceiver 1708. The transceiver 1708 is configured to transmit and receive signals for the communication device 1700 (such as various signals as described herein) via an antenna 1710. The processing system 1702 can be configured to perform processing functions for the communication device 1700, including processing signals received and / or to be transmitted by the communication device 1700.
[0120] The processing system 1702 includes a processor 1704 coupled to a computer readable medium / memory 1712 via a bus 1706. In some aspects, the computer readable medium / memory 1712 is configured to store a program that, when executed by the processor 1704, causes the processor 1704 to execute Figure 10-14 16 or instructions (e.g., computer executable code) for performing the operations illustrated in the various techniques discussed herein. In some aspects, the computer-readable medium / memory 1712 stores code for communicating 1720, code for determining 1722, code for sending 1724, code for receiving 1726, code for transmitting 1728, and / or code for generating 1730. In some aspects, the processor 1704 has circuitry configured to implement the code stored in the computer-readable medium / memory 1712. The processor 1704 includes circuitry for communicating 1740, circuitry for determining 1742, circuitry for sending 1744, circuitry for receiving 1746, circuitry for transmitting 1748, and / or circuitry for generating 1750.
[0121] Fig.18BS 110 and UE 120 (eg, in Figure 1 1800 of the wireless communication network 100). For example, antenna 1852, processors 1866, 1858, 1864 and / or controller / processor 1880 of UE 120 and / or antenna 1834, processors 1820, 1830, 1838 and / or controller / processor 1840 of BS 110 may be used to perform the various techniques and methods described herein. For example, Fig.18 As shown in , according to various aspects described herein, the controller / processor 1840 of BS 110 has an application manager that can be configured for file-based services (such as, XR). According to various aspects described herein, the controller / processor 1880 of UE 120 has an application manager that can be configured for file-based services (such as, XR).
[0122] At BS 110, a transmit processor 1820 may receive data from a data source 1812 and control information from a controller / processor 1840. 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 physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 1820 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 1820 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 1830 may perform spatial processing (e.g., precoding) on data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to modulators (MODs) 1832a-1832t. Each modulator 1832 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 up-convert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 1832a-1832t may be transmitted via antennas 1834a-1834t, respectively.
[0123] At UE 120, antennas 1852a-1852r may receive downlink signals from BS 110 and may provide received signals to demodulators (DEMODs) 1854a-1854r in the transceiver, respectively. Each demodulator 1854 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 1856 may obtain received symbols from all demodulators 1854a-1854r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 1858 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to a data sink 1860, and provide decoded control information to a controller / processor 1880.
[0124] On the uplink, at the UE 120, a transmit processor 1864 may receive and process data from a data source 1862 (e.g., data for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 1880 (e.g., control information for a physical uplink control channel (PUCCH)). The transmit processor 1864 may also generate reference symbols for a reference signal (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 1864 may be precoded by a TX MIMO processor 1866, if applicable, further processed by a demodulator 1854a-1854r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At BS 110, uplink signals from UE 120 may be received by antenna 1834, processed by modulator 1832, detected by MIMO detector 1836 if applicable, and further processed by receive processor 1838 to obtain decoded data and control information sent by UE 120. Receive processor 1838 may provide decoded data to data sink 1839 and decoded control information to controller / processor 1840.
[0125] Controllers / processors 1840 and 1880 may direct the operation at BS 110 and UE 120, respectively. Controller / processor 1840 and / or other processors and modules at BS 110 may perform or direct the execution of processes for the techniques described herein. Memories 1842 and 1882 may store data and program codes for BS 110 and UE 120, respectively. Scheduler 1844 may schedule UEs for data transmission on the downlink and / or uplink.
[0126] 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 herein as "exemplary" need not be interpreted as being superior to or superior to other aspects.
[0127] 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.
[0128] A CDMA network may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network may implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network 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-OFDMA, etc. UTRA and E-UTRA are parts 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).
[0129] 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.
[0130] A BS may be a station that communicates with a user equipment (UE). Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of a B node (NB) and / or a NB subsystem that serves the coverage area, depending on the context in which the term is used. In the NR system, the terms "cell" and BS, next generation B node (gNB or g B node), access point (AP), distributed unit (DU), carrier, or transmit receive point (TRP) may be used interchangeably. In some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the mobile BS. In some examples, the BS may be interconnected to each other and / or to one or more other BSs or network nodes in a wireless communication network via various types of backhaul interfaces (such as direct physical connections, wireless connections, virtual networks, or analogs using any suitable transmission networks).
[0131] A BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS.
[0132] A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a BS or UE) and sends transmissions of the data and / or other information to a downstream station (e.g., a UE or BS). A relay station may also be a UE that relays transmissions for other UEs.
[0133] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, subcarrier, frequency channel, frequency modulation, subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0134] The wireless communication network may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relays, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless communication network. For example, a macro BS may have a high transmit power level (e.g., 20 watts), while a pico BS, a femto BS, and a relay may have a lower transmit power level (e.g., 1 watt).
[0135] The wireless communication network may support synchronous or asynchronous operation. For synchronous operation, each BS may have similar frame timing, and transmissions from different BSs may be roughly aligned in time. For asynchronous operation, each BS may have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.
[0136] UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical equipment, biometric sensor / device, wearable device (such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), transportation component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. Some UEs may be considered machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can provide connectivity for or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.
[0137] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into subbands. For example, a subband may cover 1.08 MHz (e.g., 6 RBs), and for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, there may be 1, 2, 4, 8, or 16 subbands, respectively. In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe. In NR, a subframe is still 1 ms, but the basic TTI is called a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16... slots), depending on the subcarrier spacing. NR RBs are 12 consecutive frequency subcarriers. NR may support a base subcarrier spacing of 15 KHz, and other subcarrier spacings may be defined relative to the base subcarrier spacing, e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. The symbol and slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing.
[0138] NR may utilize OFDM with CP on both uplink and downlink and include support for half-duplex operation using TDD. Beamforming may be supported and beam directions may be dynamically configured. MIMO transmissions with precoding may also be supported. In some examples, MIMO configurations in the DL may support up to 8 transmit antennas (with multi-layer DL transmissions of up to 8 streams) and up to 2 streams per UE. In some examples, multi-layer transmissions of up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells.
[0139] In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., BS) allocates resources for communication between some or all devices and equipment within its service area or cell. A scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, subordinate entities utilize resources allocated by the scheduling entity. A base station is not the only entity that can be used as a scheduling entity. In some examples, a UE may be used as a scheduling entity, and resources for one or more subordinate entities (e.g., one or more other UEs) may be scheduled, and other UEs may use resources scheduled by the UE for wireless communications. In some examples, a UE may act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In a mesh network example, UEs may communicate directly with each other in addition to communicating with a scheduling entity.
[0140] In some examples, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh networks, and / or various other suitable applications. Generally, a sidelink signal may refer to a signal that is communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, the sidelink signal may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).
[0141] 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.
[0142] 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 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).
[0143] 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.
[0144] 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 readily apparent to those skilled in the art, and the universal principles defined herein may 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 indicate that there is 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 a 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...".
[0145] 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.
[0146] 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.
[0147] 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 of the processing system and the overall design constraints, 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 user equipment 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.
[0148] 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.
[0149] 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.
[0150] 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 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.
[0151] 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, such as for performing the operations described herein and in Figure 10-14 and instructions for the operations explained in 16.
[0152] 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.
[0153] 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 device for wireless communication, comprising: A transceiver, the transceiver being configured to: communicating files with one of a network entity or a user equipment (UE), each of the files having a plurality of packets; receiving a notification of a delivery failure for at least one of the files; and A processing system configured to: determining that the delivery failure has occurred for the at least one of the files, and The notification of the delivery failure is sent to one of an application client or a server entity, wherein when the configuration is a first configuration, the notification is sent to a data network of the server entity via a user plane function (UPF) of a core network, and when the configuration is a second configuration, the notification is sent to an application function (AF) of the server entity.
2. The device according to claim 1, wherein: The notification indicates a file identifier associated with the at least one of the files.
3. The device according to claim 1, wherein: The notification indicates that a delivery failure has occurred for a group of files that includes the at least one of the files, and the notification further indicates a file identifier for each file in the group.
4. The device of claim 1, wherein: The transceiver is configured to receive the configuration for the notification from the AF of the core network or the server entity; and The processing system is configured to generate the notification according to the configuration.
5. The device according to claim 4, wherein: The configuration indicates that the notification is sent each time a delivery failure of a file occurs or each time a delivery failure of a file group occurs.
6. The device according to claim 4, wherein: The configuration indicates a feedback path for the notification to the AF of the server entity or to the data network of the server entity via the UPF of the core network.
7. The device of claim 4, wherein: The transceiver is configured to receive the configuration from the AF via a policy control function (PCF) of the core network, a session management function (SMF) of the core network, and an access and mobility management function (AMF) of the core network.
8. The apparatus of claim 1, wherein: The processing system is configured to send the notification to the AF of the server entity via an access and mobility management function (AMF) of the core network, a session management function (SMF) of the core network, and a policy control function (PCF) of the core network; as well as The notification is a quality of service notification including a field indicating the delivery failure of at least one of the files.
9. The device of claim 1, wherein: The processing system is configured to send the notification to the data network via a message including the notification and through an interface in communication with the data network of the server entity.
10. A method for wireless communication, comprising: communicating files with one of a network entity or a user equipment (UE), each of the files having a plurality of packets; receiving a configuration for notification of a delivery failure for at least one of the files; determining that the delivery failure has occurred for the at least one of the files, and The notification of the delivery failure is sent to one of an application client or a server entity, wherein when the configuration is a first configuration, the notification is sent to a data network of the server entity via a user plane function (UPF) of a core network, and when the configuration is a second configuration, the notification is sent to an application function (AF) of the server entity.
11. The method of claim 10, wherein: The notification indicates a file identifier associated with the at least one of the files.
12. The method of claim 10, wherein: The notification indicates that a delivery failure has occurred for a group of files that includes the at least one of the files, and the notification further indicates a file identifier for each file in the group.
13. The method of claim 10, further comprising: receiving the configuration for the notification from the AF of the core network or the server entity; as well as The notification is generated according to the configuration.
14. The method of claim 13, wherein: The configuration indicates that the notification is sent each time a delivery failure of a file occurs or each time a delivery failure of a file group occurs.
15. The method of claim 13, wherein: The configuration indicates a feedback path for the notification to the AF of the server entity or to the data network of the server entity via the UPF of the core network.
16. The method of claim 13, wherein: The configuration is received from the AF via a Policy Control Function (PCF) of the core network, a Session Management Function (SMF) of the core network, and an Access and Mobility Management Function (AMF) of the core network.
17. The method of claim 10, wherein: The notification is sent to the AF of the server entity via the access and mobility management function (AMF) of the core network, the session management function (SMF) of the core network and the policy control function (PCF) of the core network; and the notification is a quality of service notification including a field indicating the delivery failure of at least one of the files.
18. A device for wireless communication, comprising: means for communicating files with one of a network entity or a user equipment (UE), each of the files having a plurality of packets; means for receiving a configuration for notification of a delivery failure for at least one of the files; means for determining that said delivery failure has occurred for said at least one of said files, and A device for sending the notification of the delivery failure to one of an application client or a server entity, wherein when the configuration is a first configuration, the notification is sent to a data network of the server entity via a user plane function (UPF) of a core network, and when the configuration is a second configuration, the notification is sent to an application function (AF) of the server entity.
19. The apparatus of claim 18, wherein: The notification indicates a file identifier associated with the at least one of the files.
20. The apparatus of claim 18, wherein: The notification indicates that a delivery failure has occurred for a group of files that includes the at least one of the files, and the notification further indicates a file identifier for each file in the group.
21. The apparatus of claim 18, further comprising: means for receiving said configuration for said notification from said AF of said core network or said server entity; as well as means for generating the notification in accordance with the configuration.
22. The apparatus of claim 21, wherein: The configuration indicates that the notification is sent each time a delivery failure of a file occurs or each time a delivery failure of a file group occurs.
23. The apparatus of claim 21, wherein: The configuration indicates a feedback path for the notification to the AF of the server entity or to the data network of the server entity via the UPF of the core network.
24. The apparatus of claim 21, wherein: The configuration is received from the AF via a Policy Control Function (PCF) of the core network, a Session Management Function (SMF) of the core network, and an Access and Mobility Management Function (AMF) of the core network.
25. The apparatus of claim 18, wherein the notification is sent to the AF of the server entity via an access and mobility management function (AMF) of the core network, a session management function (SMF) of the core network, and a policy control function (PCF) of the core network; and the notification is a quality of service notification including a field indicating the delivery failure of at least one of the files.
