Method and apparatus for delay budget in low-latency communication

Abstract

Generally speaking, the described technology provides for signaling from a core network to a base station a delay budget configuration that indicates a determined time delay for communication between the core network, the base station, and a user equipment (UE). In some cases, the core network may determine a first variable delay budget between the core network and the base station based on capability information associated with the wireless communication system. The core network may send a delay budget configuration to the base station, where the delay budget configuration may include the first delay budget. The base station may be able to determine a delay between the UE and the base station based on the delay budget configuration. Using the delay budget configuration, the base station may then schedule communication with the UE.

Description

[0001] This application is a divisional application of the patent application with the application date of September 24, 2019, the invention name of "DELAY BUDGET FOR LOW LATENCY COMMUNICATIONS", and the application number of 201980060165.9.

[0002] Cross-reference

[0003] This patent application claims priority to the following applications: U.S. Patent Application No. 16 / 579,792, titled "DELAY BUDGET FOR LOW LATENCY COMMUNICATIONS", filed on September 23, 2019, by Prakash et al.; and U.S. Provisional Patent Application No. 62 / 739,130, titled "DELAY BUDGET FOR LOW LATENCY COMMUNICATIONS", filed on September 28, 2018, by PRAKASH et al. Each of the above applications is assigned to the assignee of this application, and each application is hereby incorporated by reference in its entirety. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems can be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems (such as Long-Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread OFDM (DFT-S-OFDM).

[0005] A wireless multi-access communication system may include multiple base stations or network access nodes, each of which simultaneously supports communication for multiple communication devices (which may also be referred to as user equipment (UE)). In some cases, various applications (e.g., motion control, discrete manufacturing) may utilize relatively strict reliability and latency requirements. Summary of the Invention

[0006] The described techniques relate to improved methods, systems, devices, and apparatus for supporting latency budgets for low-latency communication. Generally speaking, the described techniques provide for a first device (such as a core network entity) to signal a latency budget configuration to a second device (such as a base station), the latency budget configuration indicating a determined latency for communication between the core network and the base station, between a user equipment (UE) and the base station, or between the core network and the UE. For example, in the case of a downlink transmission, the latency budget configuration may include a first variable latency budget incurred between a core network entity and a radio access node (e.g., at the base station). The latency budget configuration may also include a second variable latency budget incurred between the base station and the UE. Together, this total latency budget may define the total latency for communication between the UE and the core network entity.

[0007] According to some aspects, one or more latency budgets may be partitioned within a radio access network (RAN). For example, the RAN may include a central unit (CU) and a distributed unit (DU). The latency budget configuration may include one or more latency budgets (e.g., variable or immutable latency budgets) incurred between the CU and the DU. For example, the latency budget configuration may indicate a balanced budget (e.g., an evenly split latency budget) between the CU, DU, and the UE. In such a case, the latency budget configuration may indicate partitioning the second variable latency budget (e.g., between the base station of the RAN and the UE) into respective latency budgets for each of the CU-to-DU and DU-to-UE. In other examples, the latency budget between the RAN and the UE may be unbalanced (e.g., unevenly split) between the CU, DU, and the UE or may be defined separately from the second variable latency budget.

[0008] In some cases, the core network entity may determine the first variable latency budget based on configured capability information associated with the wireless communication system. For example, the core network entity may determine the first variable latency budget based on RAN capabilities such as at least one of the following: subcarrier spacing to be used for communication, support for micro-slot communication, frame structure configuration, radio frequency spectrum bandwidth, bandwidth part, etc. Additionally or alternatively, the core network entity may determine the first variable latency budget based on the capabilities of the communication to be used for communication with the base station. Additionally or alternatively, the core network entity may determine the first variable latency budget based on one or more capabilities of the wireless communication system (e.g., latency limits associated with transmitting communication within the wireless communication system, the latency limits may be configured based on, for example, traffic class). The core network entity may similarly determine a second variable latency budget for communication, for example, between the UE and the core network entity.

[0009] The core network entity may send a latency budget configuration to the base station, where the latency budget configuration may include a first variable latency budget and a second latency budget, and in some cases, the second latency budget may be variable. By signaling these two parameters to the base station, the base station may also be able to determine the latency between the UE and the base station based on the total latency and the latency between the core network entity and the base station. Using the latency budget configuration, the base station may schedule communication with another device (such as a UE).

[0010] A method for wireless communication is described. The method may include: identifying a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node; determining a first variable latency budget for communication with the first latency type between the radio access node and the core network node via the communication link; and sending a latency budget configuration to the radio access node, the latency budget configuration indicating the first variable latency budget and a second variable latency budget for communication with the first latency type between the UE and the core network node via the communication link.

[0011] A device for wireless communication is described. The device may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to perform the following operations: identifying a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node; determining a first variable latency budget for communication with the first latency type between the radio access node and the core network node via the communication link; and sending a latency budget configuration to the radio access node, the latency budget configuration indicating the first variable latency budget and a second variable latency budget for communication with the first latency type between the UE and the core network node via the communication link.

[0012] Another device for wireless communication is described. The device may include units for performing the following operations: identifying a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node; determining a first variable latency budget for communication with the first latency type between the radio access node and the core network node via the communication link; and sending a latency budget configuration to the radio access node, the latency budget configuration indicating the first variable latency budget and a second variable latency budget for communication with the first latency type between the UE and the core network node via the communication link.

[0013] Describes a non - transitory computer - readable medium storing code for wireless communication. The code may include instructions executable by a processor to perform the following operations: identify a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node; determine a first variable delay budget for communication with the first latency type between the radio access node and the core network node via the communication link; and send a delay budget configuration to the radio access node, the delay budget configuration indicating the first variable delay budget and a second variable delay budget for communication with the first latency type between the UE and the core network node via the communication link.

[0014] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the second variable delay budget may be for communication with the first latency type between the UE and the radio access node via the communication link.

[0015] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, determining the first variable delay budget may include operations, features, units, or instructions for performing the following: determining an uplink variable delay budget for uplink communication with the first latency type via the communication link; and determining a downlink variable delay budget for downlink communication with the first latency type via the communication link.

[0016] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the uplink variable delay budget and the downlink variable delay budget may be different.

[0017] Some examples of the methods, apparatuses, and non - transitory computer - readable media described herein may also include operations, features, units, or instructions for performing the following: determining a total delay budget for communication with the first latency type between the UE and the core network node via the communication link based on the delay budget configuration.

[0018] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, determining the first variable delay budget may include operations, features, units, or instructions for performing the following: at a session management function unit (SMF), determining the first variable delay budget for communication with the first latency type between the radio access node and the core network node via the communication link.

[0019] Some examples of the methods, apparatuses, and non - transitory computer - readable media described herein may also include operations, features, units, or instructions for performing the following: sending the delay budget configuration to a user plane function unit (UPF).

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving a request to establish or modify a quality of service (QoS) flow corresponding to a communication link, wherein a first variable delay budget may be determined in response to the request.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving a request for any of the following: handover of a UE, establishment of a packet data unit (PDU) session of a UE, modification of a PDU session of a UE, or any combination thereof, wherein a first variable delay budget may be determined in response to the request.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: identifying a set of RAN capabilities for a radio access node, wherein a first variable delay budget may be determined based on the set of RAN capabilities.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the set of RAN capabilities includes: subcarrier spacing for communication via a radio access node, support for micro-slot communication via a radio access node, frame structure for communication via a radio access node, bandwidth for communication via a radio access node, bandwidth part for communication via a radio access node, or any combination thereof.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: identifying a set of system capabilities for communication between a UE and a core network node, wherein a first variable delay budget may be determined based on the set of system capabilities.

[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the set of system capabilities includes: a delay limit for traffic associated with a first delay type, a traffic class of traffic associated with a first delay type, or any combination thereof.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining configuration information of a UE, a radio access node, or a core network node, wherein a first variable delay budget may be determined based on the configuration information.

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration information may be based on a time-sensitive networking (TSN) process for determining the capabilities of a wireless communication system.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration information includes dynamic information from a TSN system associated with a UE or a TSN traffic class associated with a QoS flow corresponding to a communication link.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration information includes subscription information associated with a UE.

[0030] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: sending a latency budget configuration based on the following: QoS associated with a UE, one or more QoS rules associated with a communication link, one or more uplink packet detection rules, one or more downlink packet detection rules, or any combination thereof.

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the latency budget configuration may include operations, features, units, or instructions for performing the following: sending a first information element (IE) that indicates a total latency budget for communication with a first latency type via a communication link between a UE and a core network node; and sending a second IE that indicates a first variable latency budget.

[0032] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first variable latency budget may be indicated as a fraction of the second variable latency budget.

[0033] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the communication link corresponds to a QoS flow associated with a first latency type.

[0034] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the traffic associated with the first latency type includes TSN traffic.

[0035] A method for wireless communication is described. The method may include: identifying a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node; receiving, from the core network node, a latency budget configuration indicating a first variable latency budget and a second variable latency budget, the first variable latency budget for communication with the first latency type between the radio access node and the core network node via the communication link, and the second variable latency budget for communication with the first latency type between the UE and the core network node via the communication link; and scheduling communication between the UE and the radio access node based on the first variable latency budget and the second variable latency budget.

[0036] A device for wireless communication is described. The device may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to perform the following operations: identifying a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node; receiving, from the core network node, a latency budget configuration indicating a first variable latency budget and a second variable latency budget, the first variable latency budget for communication with the first latency type between the radio access node and the core network node via the communication link, and the second variable latency budget for communication with the first latency type between the UE and the core network node via the communication link; and scheduling communication between the UE and the radio access node based on the first variable latency budget and the second variable latency budget.

[0037] Another device for wireless communication is described. The device may include units for performing the following operations: identifying a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node; receiving, from the core network node, a latency budget configuration indicating a first variable latency budget and a second variable latency budget, the first variable latency budget for communication with the first latency type between the radio access node and the core network node via the communication link, and the second variable latency budget for communication with the first latency type between the UE and the core network node via the communication link; and scheduling communication between the UE and the radio access node based on the first variable latency budget and the second variable latency budget.

[0038] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to perform the following operations: identifying a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node; receiving, from the core network node, a latency budget configuration indicating a first variable latency budget and a second variable latency budget, the first variable latency budget for communication with the first latency type between the radio access node and the core network node via the communication link, and the second variable latency budget for communication with the first latency type between the UE and the core network node via the communication link; and scheduling communication between the UE and the radio access node based on the first variable latency budget and the second variable latency budget.

[0039] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second variable latency budget may be for communication with the first latency type between the UE and the radio access node via the communication link.

[0040] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following operations: identifying an uplink variable latency budget for uplink communication with the first latency type via the communication link based on the latency budget configuration; and identifying a downlink variable latency budget for downlink communication with the first latency type via the communication link based on the latency budget configuration, wherein communication between the UE and the radio access node may be scheduled based on the uplink variable latency budget or the downlink variable latency budget.

[0041] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the uplink variable latency budget and the downlink variable latency budget may be different.

[0042] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following operations: determining a total latency budget for communication with the first latency type between the UE and the core network node via the communication link based on the latency budget configuration, wherein communication between the UE and the radio access node may be scheduled based on the total latency budget.

[0043] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving a latency budget configuration can include operations, features, units, or instructions for: receiving a first IE that indicates a total latency budget for communication between a UE and a core network node via a communication link having a first latency type; and receiving a second IE that indicates a first variable latency budget.

[0044] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first variable latency budget can be indicated as a fraction of a second variable latency budget.

[0045] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first variable latency budget can be based on a set of RAN capabilities for a radio access node.

[0046] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first variable latency budget can be based on a set of system capabilities for communication between a UE and a core network node.

[0047] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first variable latency budget can be determined based on configuration information of a UE, a radio access node, or a core network node, where the configuration information includes: dynamic information from a TSN system associated with the UE, a TSN traffic class associated with a QoS flow corresponding to the communication link, subscription information associated with the UE, or any combination thereof.

[0048] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the communication link corresponds to a QoS flow associated with the first latency type.

[0049] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the traffic associated with the first latency type includes TSN traffic. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 Examples of wireless communication systems supporting latency budgets for low-latency communication are shown in accordance with aspects of the present disclosure.

[0051] Figure 2 Examples of wireless communication systems supporting latency budgets for low-latency communication are shown in accordance with aspects of the present disclosure.

[0052] Figure 3 Examples of process flows supporting latency budgets for low-latency communication are shown in accordance with aspects of the present disclosure.

[0053] Figure 4 and Figure 5 Aspects of the present disclosure illustrate a block diagram of an apparatus supporting a latency budget for low-latency communication.

[0054] Figure 6 Aspects of the present disclosure illustrate a block diagram of a communication manager supporting a latency budget for low-latency communication.

[0055] Figure 7 Aspects of the present disclosure illustrate a diagram of a system including an apparatus supporting a latency budget for low-latency communication.

[0056] Figure 8 and Figure 9 Aspects of the present disclosure illustrate a block diagram of an apparatus supporting a latency budget for low-latency communication.

[0057] Figure 10 Aspects of the present disclosure illustrate a block diagram of a communication manager supporting a latency budget for low-latency communication.

[0058] Figure 11 Aspects of the present disclosure illustrate a diagram of a system including an apparatus supporting a latency budget for low-latency communication.

[0059] Figures 12 to 16 Aspects of the present disclosure illustrate a flowchart depicting a method for supporting a latency budget for low-latency communication. Detailed Description

[0060] Some wireless communication systems can be used to facilitate communication in networks that rely on relatively strict timing synchronization of network components (sometimes referred to as time-sensitive network (TSN) systems). Such systems can be used to support, for example, factory automation. Some TSN systems specify relatively strict quality of service (QoS) parameters, such as latency, jitter, and reliability requirements for data traffic (e.g., less than 1 millisecond (ms) latency and 10 -6 reliability). In some cases, such data traffic can be supported in wireless communication systems using high-reliability services, such as ultra-reliable low-latency communication (URLLC) services.

[0061] In a wireless communication system (e.g., carrying TSN communication), QoS requirements for a specific QoS flow can define a target packet delay budget (PDB). The target PDB can be set for the target latency or total time delay for communication between a UE and a core network in the wireless communication system, and data packets being transmitted can be used in cases where the target latency or total time delay is below. For example, in the case of downlink transmission, the PDB can include a first delay component incurred between the core network and a radio access node (e.g., at a base station in the wireless communication system). The PDB can also include a second delay component incurred between the base station and the UE. Together, this total PDB with the first and second delay components can define the target latency from the core network via the base station to the UE. In the case of uplink transmission, the PDB can similarly define the target latency from the UE via the base station to the core network. If the total delay in transmitting a data packet exceeds the total PDB, the data packet may not be used and may be ignored or discarded.

[0062] The base station can use the first delay component incurred between the core network and the base station to schedule uplink and downlink transmissions. In some wireless communication systems, the first delay component incurred between the core network and the base station can be configured as a defined delay (e.g., 1 ms). However, for example, in a wireless communication system carrying TSN communication, the following deployment is expected: where the core network and the base station are in relatively close geographical proximity, and thus the first delay component may be significantly less than the defined delay (e.g., meaning less than the configured delay of 1 ms). The first delay component can vary based on, for example, the capabilities of the backhaul link by which the base station communicates with the core network and based on one or more other capabilities such as the following (e.g., radio access network (RAN) capabilities): subcarrier spacing for communication, support for micro-slot communication, frame structure configuration, or the bandwidth or bandwidth part for communication via the base station. Thus, if the base station schedules communication with the UE based on the configured delay, the scheduling decision may be overly aggressive or overly conservative, depending on the actual delay.

[0063] Accordingly, techniques for signaling a PDB configuration to the base station are discussed herein, the PDB configuration indicating the determined delay incurred between the core network and the base station, between the UE and the base station, or between the core network and the UE. For example, the core network can send a PDB configuration to the base station that indicates a combination of the following: the delay between the core network and the base station, the delay between the base station and UE115, and the total delay between the UE and the core network. Based on the PDB configuration to determine an estimate of the actual delay in such communication in the wireless communication system, the base station (or another device) can schedule communication between the UE, the base station, and the core network relatively more accurately.

[0064] In some cases, the core network may determine the PDB configuration at an adapter functional unit supported by the system (e.g., a session management functional unit (SMF)). For example, when the core network entity receives a request for establishing or modifying a QoS flow, the core network may determine the PDB configuration. The core network may also send the PDB configuration via an adapter functional unit supported by the system. For example, the core network may send the PDB configuration to the base station via the SMF.

[0065] In some cases, the core network may determine the PDB configuration based on the configured capability information associated with the wireless communication system. For example, the core network may determine the PDB configuration based on RAN capabilities (such as subcarrier spacing to be used for communication, support for micro-slot communication, frame structure configuration, radio frequency spectrum bandwidth, bandwidth part, etc.). Additionally or alternatively, the core network may determine the PDB configuration based on the capabilities of the backhaul communication link (e.g., an Ethernet link) to be used for communicating with the base station. Additionally or alternatively, the core network may determine the PDB configuration based on the capabilities of the wireless communication system (e.g., the latency limit associated with transmitting communications within the wireless communication system, and the latency limit may be configured based on, for example, a traffic class (e.g., a QoS class)).

[0066] Aspects of the present disclosure are first described in the context of a wireless communication system and a process flow. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts related to a delay budget for low-latency communication.

[0067] Figure 1 An example of a wireless communication system 100 that supports a delay budget for low-latency communication is shown in accordance with aspects of the present disclosure. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an enhanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices.

[0068] Base station 105 may communicate wirelessly with UE 115 via one or more base station antennas. The base station 105 described herein may include or may be referred to by those skilled in the art as a base station transceiver, radio base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or Gigabit Node B (any of which may be referred to as a gNB), home Node B, home evolved Node B, or some other suitable term. The wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). The UE 115 described herein may be capable of communicating with various types of base stations 105 and network devices (including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.).

[0069] Each base station 105 may be associated with a particular geographic coverage area 110 in which communication with respective UEs 115 is supported. Each base station 105 may provide communication coverage for the corresponding geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 may include: an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. The downlink transmission may also be referred to as a forward link transmission, and the uplink transmission may also be referred to as a reverse link transmission.

[0070] The geographic coverage area 110 for the base station 105 may be divided into sectors, which form part of the geographic coverage area 110, and each sector may be associated with a cell. For example, each base station 105 may provide communication coverage for a macro cell, small cell, hot spot, or other type of cell, or various combinations thereof. In some examples, the base station 105 may be movable and thus provide communication coverage for a mobile geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, and the overlapping geographic coverage areas 110 associated with different technologies may be supported by the same base station 105 or different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous LTE / LTE-A / LTE-A Pro or NR network, where different types of base stations 105 provide coverage for respective geographic coverage areas 110.

[0071] The term "cell" refers to a logical communication entity for communication with the base station 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a Physical Cell Identifier (PCID), a Virtual Cell Identifier (VCID)) used to distinguish adjacent cells operating on the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., Machine Type Communication (MTC), NarrowBand Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types), which may provide access for different types of devices. In some cases, the term "cell" may refer to a portion (e.g., a sector) of the geographical coverage area 110 over which the logical entity operates.

[0072] UEs 115 may be scattered throughout the wireless communication system 100, and each UE 115 may be stationary or mobile. A UE 115 may also be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a user equipment, or some other suitable term, where "device" may also be referred to as a unit, a station, a terminal, or a client. A UE 115 may also be a personal electronic device such as a cellular phone, a Personal Digital Assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may also refer to a Wireless Local Loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or an MTC device, etc., which may be implemented in various articles such as appliances, vehicles, meters, etc.

[0073] Some UEs 115 (such as MTC or IoT devices) may be low-cost or low-complexity devices, and may provide automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to a data communication technology that allows devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices integrated with sensors or meters to measure or capture information and relay that information to a central server or application, which may utilize the information or present the information to a human who interacts with the program or application. Some UEs 115 may be designed to collect information or implement automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, device monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.

[0074] Some UEs 115 may be configured to operate in a power consumption-reduced mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception rather than simultaneous transmission and reception). In some examples, the half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the UE 115 include entering a power-saving "deep sleep" mode when not participating in active communication or operating on a limited bandwidth (e.g., according to narrowband communication). In some cases, the UE 115 may be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communication for these functions.

[0075] In some cases, the UE 115 may also be able to communicate directly with other UEs 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more UEs 115 in a group of UEs 115 utilizing D2D communication may be within the geographical coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographical coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105. In some cases, a group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE 115 transmits to each other UE 115 in the group. In some cases, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.

[0076] The base stations 105 may communicate with the core network 130 and with each other. For example, the base stations 105 may interface with the core network 130 via a backhaul link 132 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 may communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via the core network 130) on a backhaul link 134 (e.g., via X2, Xn, or other interfaces).

[0077] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC), which can include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME can manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for a UE 115 served by a base station 105 associated with the EPC. User IP packets can be transmitted through the S-GW, which itself can be coupled to the P-GW. The P-GW can provide IP address allocation and other functions. The P-GW can be coupled to network operator IP services. The operator IP services can include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or packet-switched (PS) streaming services.

[0078] At least some of the network devices (such as base station 105) can include subcomponents such as access network entities, which can be examples of access node controllers (ANC). Each access network entity can communicate with a UE 115 through a plurality of other access network transmission entities (which can be referred to as radio heads, intelligent radio heads, or transmit / receive points (TRP)). In some configurations, the various functions of each access network entity or base station 105 can be distributed across various network devices (e.g., radio heads and access network controllers) or combined into a single network device (e.g., base station 105).

[0079] The wireless communication system 100 can operate using one or more frequency bands (e.g., in the range of 300 megahertz (MHz) to 300 gigahertz (GHz)). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band because the wavelength range is approximately from one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features. However, the waves can be sufficient to penetrate structures to serve a UE 115 located indoors in a macro cell. Compared to transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmissions can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers (km)).

[0080] The wireless communication system 100 can also operate in the super-high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz (also known as the centimeter band). The SHF region includes frequency bands such as the 5 GHz industrial, scientific, and medical (ISM) band, which can be opportunistically used by devices that can tolerate interference from other users.

[0081] The wireless communication system 100 may also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices may be even smaller and more closely spaced compared to UHF antennas. In some cases, this may facilitate the use of antenna arrays within the UE 115. However, the propagation of EHF transmissions may suffer from even greater atmospheric attenuation and shorter distances compared to SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designation of frequency bands across these frequency regions may vary according to the country or regulatory body.

[0082] In some cases, the wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band (e.g., the 5 GHz ISM band). When operating in an unlicensed radio frequency spectrum band, wireless devices such as the base station 105 and the UE 115 may employ a listen-before-talk (LBT) procedure to ensure that the frequency channel is idle before transmitting data. In some cases, operation in the unlicensed band may be based on a carrier aggregation configuration that combines component carriers operating in a licensed band (e.g., LAA). Operation in the unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these. Duplexing in the unlicensed spectrum may be based on frequency-division duplexing (FDD), time-division duplexing (TDD), or a combination of both.

[0083] In some examples, the base station 105 or the UE 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, the wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., the base station 105) and a receiving device (e.g., the UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication can utilize multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers (which can be referred to as spatial multiplexing). For example, the transmitting device may transmit multiple signals via different antennas or different combinations of antennas. Similarly, the receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0084] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., the base station 105 or the UE 115) to form or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining the signals transmitted via the antenna elements of an antenna array such that the signals propagating in a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals transmitted via the antenna elements can include the transmitting device or the receiving device applying amplitude and phase offsets to the signals carried by each of the antenna elements associated with the device. The adjustment associated with each of the antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0085] In one example, base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with UE 115. For example, base station 105 may transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions, where the some signals may include signals transmitted according to different beamforming weight sets associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by base station 105 or a receiving device such as UE 115) to identify a beam direction for subsequent transmissions or receptions performed by base station 105. Base station 105 may transmit some signals (such as data signals associated with a particular receiving device) in a single beam direction (e.g., a direction associated with a receiving device such as UE 115). In some examples, the beam direction associated with a transmission along a single beam direction may be determined at least in part based on signals transmitted in different beam directions. For example, UE 115 may receive one or more of the signals transmitted by base station 105 in different directions, and UE 115 may report to base station 105 an indication of the signal that it received with the highest signal quality or otherwise acceptable signal quality. Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmissions or receptions performed by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0086] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, a receiving device (e.g., UE 115, which may be an example of a mmW receiving device) may attempt multiple receive beams. For example, the receiving device may attempt multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array (any of the above operations may be referred to as "listening" according to different receive beams or receive directions). In some examples, the receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving a data signal). The single receive beam may be aligned in a beam direction determined based on listening according to different receive beam directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio, or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0087] In some cases, the antennas of base station 105 or UE 115 may be located within one or more antenna arrays, and the one or more antenna arrays may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with base station 105 may be located at different geographical locations. Base station 105 may have an antenna array having multiple rows and columns of antenna ports that base station 105 may use to support beamforming for communications with UE 115. Similarly, UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.

[0088] In some cases, wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or packet data convergence protocol (PDCP) layer may be IP-based. In some cases, the radio link control (RLC) layer may perform packet segmentation and reassembly for communication over logical channels. The media access control (MAC) layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use hybrid automatic repeat request (HARQ) to provide retransmissions at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide the establishment, configuration, and maintenance of an RRC connection (which supports radio bearers for user plane data) between UE 115 and base station 105 or core network 130. At the physical (PHY) layer, transport channels may be mapped to physical channels.

[0089] In some cases, UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. HARQ feedback is a technique that increases the likelihood that data is correctly received over communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., signal-to-noise conditions). In some cases, a wireless device may support same-slot HARQ feedback, where the device may provide HARQ feedback for data received in previous symbols in a particular slot during that slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0090] It may be in a basic time unit (e.g., which may refer to T sThe time intervals in LTE or NR are represented as multiples of a sampling period of 1 / 30,720,000 seconds. The time intervals of communication resources can be organized based on radio frames each having a duration of 10 ms, where the frame period can be represented as T f = 307,200T s The radio frame can be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame can include 10 subframes numbered from 0 to 9, and each subframe can have a duration of 1 ms. The subframe can be further divided into 2 time slots, each having a duration of 0.5 ms, and each time slot can contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix added in front of each symbol period). Excluding the cyclic prefix, each symbol period can contain 2048 sampling periods. In some cases, the subframe can be the smallest scheduling unit of the wireless communication system 100 and can be referred to as a transmission time interval (TTI). In other cases, the smallest scheduling unit of the wireless communication system 100 can be shorter than the subframe or can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs) or in a component carrier that selects to use sTTIs).

[0091] In some wireless communication systems, a time slot can be further divided into multiple mini-slots each containing one or more symbols. In some instances, the symbols of the mini-slot or the mini-slot can be the smallest scheduling unit. The duration of each symbol can vary depending on, for example, the subcarrier spacing or the operating frequency band. Additionally, some wireless communication systems can implement time slot aggregation, where multiple time slots or mini-slots are aggregated together and used for communication between the UE 115 and the base station 105.

[0092] The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication on the communication link 125. For example, the carrier of the communication link 125 can include a portion of the radio frequency spectrum band that operates according to the physical layer channels for a given radio access technology. Each physical layer channel can carry user data, control information, or other signaling. The carrier can be associated with a predefined frequency channel (e.g., the evolved universal terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and can be placed according to the channel grid for discovery by the UE 115. The carrier can be downlink or uplink (e.g., in the FDD mode), or can be configured to carry both downlink and uplink communications (e.g., in the TDD mode). In some examples, the signal waveform transmitted on the carrier can be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)).

[0093] For different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR), the organizational structure of a carrier can be different. For example, communication on a carrier can be organized according to a TTI or a time slot, each of which can include user data and control information or signaling for supporting decoding of the user data. A carrier can also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling for coordinating operations for the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier can also have acquisition signaling or control signaling for coordinating operations for other carriers.

[0094] Physical channels can be multiplexed on a carrier according to various techniques. For example, time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. In some examples, control information transmitted in a physical control channel can be distributed in a cascaded manner between different control regions (e.g., between a common control region or a common search space and one or more UE-specific control regions or UE-specific search spaces).

[0095] A carrier can be associated with a specific bandwidth of radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth can be one of a plurality of predetermined bandwidths for a carrier of a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). In some examples, each served UE 115 can be configured to operate on part or all of the carrier bandwidth. In other examples, some UEs 115 can be configured to operate using a narrowband protocol type associated with a predefined part or range within the carrier (e.g., a set of subcarriers or resource blocks (RBs)) (e.g., "in-band" deployment of the narrowband protocol type).

[0096] In a system employing MCM technology, a resource element can include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme). Thus, the more resource elements received by the UE 115 and the higher the order of the modulation scheme, the higher the data rate can be for the UE 115. In an MIMO system, wireless communication resources can refer to a combination of radio frequency spectrum resources, time resources, and space resources (e.g., spatial layers), and the use of multiple spatial layers can further increase the data rate for communication with the UE 115.

[0097] Devices (e.g., base station 105 or UE 115) of the wireless communication system 100 can have a hardware configuration that supports communication on a specific carrier bandwidth or can be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 can include a base station 105 or UE 115 capable of supporting simultaneous communication via carriers associated with more than one different carrier bandwidth.

[0098] The wireless communication system 100 can support communication with the UE 115 on multiple cells or carriers (a feature that can be referred to as carrier aggregation or multi-carrier operation). According to the carrier aggregation configuration, the UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used with both FDD and TDD component carriers.

[0099] In some cases, the wireless communication system 100 can utilize an enhanced component carrier (eCC). The eCC can be characterized by one or more features including: a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, the eCC can be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have sub-optimal or non-ideal backhaul links). The eCC can also be configured for use in unlicensed spectrum or shared spectrum (e.g., where more than one operator is allowed to use the spectrum). The eCC characterized by a wide carrier bandwidth can include one or more segments that can be used by a UE 115 that cannot monitor the entire carrier bandwidth or is otherwise configured to use a limited carrier bandwidth (e.g., to save power).

[0100] In some cases, the eCC can utilize a symbol duration different from that of other component carriers, which can include using a symbol duration that is reduced compared to the symbol duration of other component carriers. The shorter symbol duration can be associated with an increased spacing between adjacent subcarriers. A device (such as UE 115 or base station 105) utilizing the eCC can transmit a broadband signal (e.g., according to a frequency channel or carrier bandwidth of 20, 40, 60, 80 MHz, etc.) with a reduced symbol duration (e.g., 16.67 microseconds). The TTI in the eCC can include one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) can be variable.

[0101] In addition, a wireless communication system (such as an NR system) can utilize any combination of licensed, shared, and unlicensed spectrum bands. The flexibility of the eCC symbol duration and subcarrier spacing can allow the use of eCC across multiple spectrums. In some examples, NR shared spectrum can improve spectrum utilization and spectral efficiency, especially through dynamic vertical (e.g., across the frequency domain) and horizontal (e.g., across the time domain) sharing of resources.

[0102] Some wireless communication systems (e.g., wireless communication system 100) can be used to facilitate communication in a network that relies on relatively strict timing synchronization of network components (sometimes referred to as a TSN system). Such systems can be used to support, for example, factory automation. Some TSN systems specify relatively strict QoS parameters, such as jitter for data traffic, reliability targets (e.g., packet error loss), or latency targets (e.g., PDB, latency target, etc.). For example, a TSN system can have targets such as a latency of less than 1 ms and a packet error rate of less than 10 -6 such as that. In some cases, such data traffic can be supported in a wireless communication system using high-reliability services (such as URLLC services).

[0103] In wireless communication system 100 (e.g., carrying TSN communication), the QoS standard for a specific QoS flow can define a target PDB. The target PDB can set the target latency or total time delay for communication between UE 115 and core network 130 in wireless communication system 100, below which the transmitted data packets can be used. In the case of downlink transmission, the PDB can include a first delay component incurred between core network 130 (e.g., from a user plane function unit (UPF), SMF, or other adapter function unit) and the radio access node (e.g., at base station 105). The PDB can also include a second delay component incurred between base station 105 and UE 115. Together, this total PDB defines the target latency from the UPF via base station 105 to UE 115. In the case of uplink transmission, the PDB can similarly define the target latency from UE 115 via base station 105 to the UPF or SMF. If the total delay in transmitting a data packet exceeds the total PDB defined by the PDB configuration, the data packet may not be used and may be ignored.

[0104] The base station 105 may use a first latency component incurred between the core network 130 and the base station 105 to schedule uplink and downlink communications with, for example, the UE 115. In some wireless communication systems, it may be assumed, for example, based on a latency configuration, that the first latency component incurred between the core network 130 and the base station 105 is a defined latency (e.g., 1 ms). However, in the wireless communication system 100 (e.g., a TSN system), the following deployment is expected: wherein the core network 130 and the base station 105 are in a relatively close geographical proximity, and thus the first latency component may be significantly less than the defined latency (e.g., meaning less than the latency assumed to be 1 ms according to the latency configuration). This first latency component may also vary based on, for example, the specific capabilities of the backhaul link 132 or other RAN capabilities (such as subcarrier spacing for communication, support for micro-slot communication, frame structure configuration, or bandwidth or bandwidth part for communication via the base station 105). Thus, if the base station 105 schedules communications with the UE 115 based on the defined latency, the scheduling decision may be overly aggressive or overly conservative, depending on the actual latency.

[0105] Techniques are discussed herein for signaling a PDB configuration to the base station 105, the PDB configuration indicating a determined latency incurred between any of the core network 130, the UE 115, and the base station 105. For example, the core network 130 may send a PDB configuration to the base station 105 that indicates a combination of: a first latency component (e.g., the latency between the core network 130 and the base station 105), a second latency component (e.g., the latency between the base station 105 and the UE 115), or the total latency (e.g., between the UE 115 and the core network 130). Based on the indication of the actual latency in the PDB configuration, the base station 105 may schedule communications between the UE 115, the base station 105, and the core network 130 relatively more accurately.

[0106] Figure 2 Aspects in accordance with the present disclosure illustrate an example of a wireless communication system 200 that supports a latency budget for low latency communications. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a UE 115-a, which may be an example of the UE 115 as described with reference to Figure 1 described. The wireless communication system 200 may include radio access nodes at a base station 105-a, each of which may be an example of the base station 105 as described with reference to Figure 1 described. The wireless communication system 200 may include a core network entity 205 (e.g., EPC, Next Generation Core (NGC), Fifth Generation Core (5GC), etc.), which may be as described with reference to Figure 1Examples of entities of the described core network 130. It is to be understood that references to a particular radio access technology (RAT) (e.g., LTE or NR) in the figures below are provided for illustrative purposes and different RATs not specifically referenced herein may be used interchangeably with those described herein.

[0107] Base station 105-a may communicate with core network entity 205 using one or more communication links 210, and base station 105-a may communicate with UE 115-a using communication link 215. In some cases, core network entity 205 may include SMF 220, UPF 225, an access and mobility function unit (AMF), or a control plane function unit (CPF). In some cases, SMF 220 may provide session management services for UE 115-a. SMF 220 may communicate with different nodes in wireless communication system 200 to signal to the nodes different QoS procedures to be performed, for example, for different QoS criteria. In some cases, UPF 225 may process user information such as PDCP, RLC, MAC, and PHY communications. In some cases, SMF 220 and UPF 225 may be communicatively coupled in core network entity 205 via communication link 218. Although SMF 220 and UPF 225 are Figure 2 shown as communicatively coupled in core network entity 205, SMF 220 and UPF 225 may alternatively be located at separate nodes in wireless communication system 200.

[0108] Core network entity 205 may signal to base station 105-a a PDB configuration for a particular QoS flow, the PDB configuration indicating the latency between devices in wireless communication system 200. Figure 2An example PDB timeline is also shown, which shows example latencies incurred before the core network entity 205, base station 105-a, and UE 115-a. For example, the core network entity 205 can send a PDB configuration to the base station 105-a (e.g., using communication link 210-a), where the PDB configuration indicates a combination of the following: a first latency component 250 (e.g., the latency between the core network entity 205 and the base station 105-a), a second latency component 255 (e.g., the latency between the base station 105-a and the UE 115-a), and a total PDB 260. The PDB configuration can include an IE, and the IE includes one or more fields or sub-fields for indicating one or more of the first latency component 250, the second latency component 255, and the total PDB 260. In some cases, the PDB configuration can indicate the same latency for uplink transmissions and downlink transmissions. Alternatively, the PDB configuration can indicate different latencies for uplink transmissions and downlink transmissions. Based on the indication of one or more latencies in the PDB configuration, the base station 105-a can schedule communications between the UE 115-a and the base station 105-a. In some cases, scheduling based on the indication of latency can allow for more efficient use of network resources and other benefits compared to scheduling without an indication of latency.

[0109] In different cases, different ones of these three parameters can be signaled to the base station 105-a in the PDB configuration. For example, given that the sum of the first latency component 250 and the second latency component 255 equals the total PDB 260, the core network entity 205 can signal any two of the first latency component 250, the second latency component 255, and the total PDB 260. By signaling two of these three parameters, the third parameter can be calculated by adding or subtracting latency components with respect to the total PDB 260. Thus, in some cases, any two of these three parameters can be included in the PDB configuration. Alternatively, the PDB configuration can signal all three parameters in the PDB configuration.

[0110] According to some aspects, base station 105-a can be a node of the RAN and can include multiple units or functional units (such as distributed unit (DU) 265 and central unit (CU) 270). In other cases, one or more of DU 265 and CU 270 can be separate from base station 105-a and can be separate entities associated with the RAN. In some cases, DU 265 and CU 270 can communicate with each other (e.g., via base station 105-a, within base station 105-a, or separately from base station 105-a (via a separate communication link)). In some examples, CU 270 can perform operations similar to those of core network entity 205, and DU 265 can perform operations similar to those of a node of the RAN (e.g., base station 105-a).

[0111] In some examples, the total PDB 260 can also include a latency component between DU 265 and CU 270. For example, a first latency component 250 (e.g., between base station 105-a or the RAN and UE 115-a) can be divided (e.g., evenly or unevenly) between DU 265 and CU 270. The PDB configuration can indicate that the first latency component 250 is divided into a third latency component 275 between UE 115-a and DU 265 and a fourth latency component 280 between DU 265 and CU 270. The PDB configuration can indicate (e.g., via separate fields in the signaling of the PDB configuration) at least some of the four components (if not indicating each component) individually, or can alternatively or additionally indicate at least some of the four components (e.g., a subset) (if not indicating each component) and the total PDB 260. The signaling can include information on how the total PDB 260 will be divided between core network entity 205, base station 105-a, DU 265, CU 270, and UE 115-a. In some cases, the third latency component 275 and the fourth latency component 280 can be different for uplink transmissions and downlink transmissions.

[0112] In some cases, the third delay component 275 and the fourth delay component 280 can be balanced (e.g., the same) or can be different. For example, the PDB configuration can indicate a balanced delay budget (e.g., a uniformly split delay budget) between the DU 265, the CU 270, and the UE 115-a. In such a case, the PDB configuration can indicate dividing the first delay component 250 (e.g., between the base station 105-a in the RAN and the UE 115-a) into corresponding delay budgets (e.g., the third delay component 275 and the fourth delay component 280) for each of the CU 270 to the DU 265 and the DU 265 to the UE 115-a. In other examples, the delay budget between the RAN and the UE 115-a may be unbalanced (e.g., non-uniformly split) between the DU 265, the CU 270, and the UE 115-a or can be defined separately from the first delay component 250.

[0113] The core network entity 205 can determine the PDB configuration at the SMF 220. For example, when the core network entity 205 receives a request to establish a QoS flow or a request to modify a QoS flow, the core network entity 205 can determine the PDB configuration. Additionally or alternatively, for example, when the core network entity 205 receives a request to perform a handover to the UE 115-a, a request to establish a PDU session with the UE 115-a, or a request to modify a PDU session with the UE 115-a, the core network entity 205 can determine the PDB configuration.

[0114] The core network entity 205 can send the PDB configuration via an adapter functional unit supported by the system. For example, the core network entity 205 can send the PDB configuration via the SMF 220 via the base station 105-a using the communication link 210-a. Additionally or alternatively, the core network entity 205 can send the PDB configuration via one or more other adapter functional units (including, for example, one or more PCFs, one or more additional SMFs, one or more AMFs, one or more UPFs, etc.). Additionally or alternatively, the core network entity 205 can also send the PDB configuration to the UE 115-a using, for example, one or more AMFs. Further additionally or alternatively, the core network entity 205 can send the PDB configuration to the UPF 225 via, for example, the communication link 218. The UPF 225 can use the PDB configuration to, for example, perform the following operations: receive an uplink transmission from the UE 115-a via the base station 105-a using the communication link 210-b.

[0115] In some cases, the core network entity 205 may determine the PDB configuration based on the configured capability information associated with the wireless communication system 200. For example, the core network entity 205 may determine the PDB configuration based on RAN capabilities (such as subcarrier spacing to be used for communication, support for micro-slot communication, frame structure configuration, radio frequency spectrum bandwidth, bandwidth part, etc.). For example, with respect to one subcarrier spacing (e.g., 30 kilohertz (kHz)), for another subcarrier spacing with shorter time slots (e.g., 60 kHz), the second delay component 255 may be determined to be relatively short. Additionally or alternatively, the core network entity 205 may determine the PDB configuration based on the capabilities of the communication link 210 (e.g., Ethernet link) to be used for communicating with the nodes of the wireless communication system 200 (e.g., the bandwidth of the backhaul link between the core network entity 205 and the base station 105-a). For example, compared to an Ethernet link of the core network entity 205 with a lower bandwidth (e.g., 1 gigabit per second (Gbps)), the second delay component 255 may be determined to be relatively longer for another Ethernet link of the core network entity 205 with a larger bandwidth (e.g., 10 Gbps). Additionally or alternatively, the core network entity 205 may determine the PDB configuration based on the capabilities of the wireless communication system 200 (e.g., the delay limitation associated with transmitting communications within the wireless communication system 200, and the delay limitation may be configured based on, for example, the traffic class (e.g., QoS class)). For example, for the first QoS class, the second delay component 255 may be 0.5 ms, and for the second QoS class, the second delay component 255 may be 0.3 ms. The core network entity 205 may associate different traffic classes with different PDB configurations, for example, using a look-up table, etc. In some cases, the core network entity 205 may additionally or alternatively determine the PDB configuration based on the subscription information associated with the UE 115 (e.g., the type of the UE 115 and the services subscribed by the UE 115).

[0116] In some cases, the core network entity 205 may dynamically determine the PDB configuration. For example, the core network entity 205 may re-calibrate the PDB configuration based on, for example, changing link conditions. In such a case, the core network entity 205 may perform a process on the communication link 210 to determine the PDB configuration based on the current (e.g., instantaneous or substantially instantaneous) characteristics or capabilities of the wireless communication system 200. For example, if the core network entity 205 dynamically determines that a larger number of backhaul resources are available for the first QoS flow compared to the second QoS flow, then the first delay component 250 may be determined to be relatively longer for the first QoS flow with respect to the second QoS flow, because in this case, the time delay between the base station 105-a and the core network entity 205 may be relatively high.

[0117] In some cases, the core network entity 205 may send the PDB configuration in a message that includes one or more fields that include parameters for PDB configuration. For example, the core network entity 205 may use a QoS profile, one or more QoS rules, one or more uplink packet detection rules, or one or more downlink packet detection rules to send the PDB configuration. The PDB configuration may be indicated in one or more fields or sub-fields of an IE (e.g., a PDB information element (IE)). For example, the IE may include one or more fields or sub-fields that indicate the following: a parameter representing the first latency component 250, a parameter representing the second latency component 255, or a parameter representing the total PDB 260. The latency budget parameter may be indicated in terms of a length of time (e.g., nanoseconds or milliseconds). Additionally or alternatively, the latency budget parameter for the first latency component 250 or the second latency component 255 may be indicated as a fraction of the total PDB 260.

[0118] Figure 3 Aspects in accordance with the present disclosure illustrate an example of a procedure flow 300 that supports a latency budget for low latency communication. In some examples, the procedure flow 300 may implement aspects of the wireless communication systems 100 and 200. For example, the procedure flow 300 includes a UE 115-b, a base station 105-b, and a core network entity 205-a, which may be examples of the corresponding devices described with reference to Figure 1 and Figure 2 respectively. The core network entity 205-a may include an SMF 220-a and a UPF 225-a, but it should be understood that the SMF 220-a and the UPF 225-a are provided for illustrative purposes only. Different RATs, devices, nodes, functional units, etc. may perform similar functions. The procedure flow 300 may illustrate an example in which the core network entity 205-a determines a PDB configuration and signals the PDB configuration to the base station 105-b, where the PDB configuration indicates the latency budget (e.g., the PDB as described with reference to Figure 2 and Figure 3 respectively) to be used for communication between the UE 115-b and the core network entity 205-a.

[0119] At 305, the SMF 220-a may identify a communication link for traffic associated with a first latency type between the UE 115-b and a core network node (e.g., at the core network entity 205-a) via the base station 105-b. In some cases, the communication link may correspond to a QoS flow associated with the first latency type. In some cases, the traffic associated with the first latency type may include TSN traffic. At 310, the base station 105-b may identify a communication link for traffic associated with the first latency type between the UE 115-b and the core network entity 205-a via the base station 105-b.

[0120] At 315, the SMF 220-a may identify one or more sets of capabilities, and at 320, the SMF 220-a may determine one or more delay budgets based on the one or more sets of capabilities. For example, the SMF 220-a may identify a RAN set of capabilities for the base station 105-b. In some cases, the RAN set of capabilities may include: subcarrier spacing for communication via the base station 105-b, support for micro-slot communication via the base station 105-b, frame structure for communication via the base station 105-b, bandwidth for communication via the base station 105-b, bandwidth part for communication via the base station 105-b, or any combination. Additionally or alternatively, the SMF 220-a may identify a system set of capabilities for communication between the UE 115-b and the core network entity 205-a. In some cases, the system set of capabilities may include: latency limits for traffic associated with the first latency type, traffic class of traffic associated with the first latency type, or any combination. Additionally or alternatively, the SMF 220-a may determine configuration information of the UE 115-b, the base station 105-b, or the core network entity 205-a. In some cases, the configuration information may be based on a TSN process for determining the capabilities of a wireless communication system. In some cases, the configuration information may include dynamic information from a TSN system associated with the UE 115-b or a TSN traffic class associated with the QoS flow corresponding to the communication link. In some cases, the configuration information may include subscription information associated with the UE 115-b.

[0121] At 320, the SMF 220-a may determine a first variable delay budget for communication with a first latency type between the base station 105-b and the core network entity 205-a via the communication link (e.g., a first delay component incurred between the core network entity 205-a and the base station 105-b, as referred to in Figure 1 and Figure 2(as described). In some cases, determining the first variable delay budget may include: determining an uplink variable delay budget for uplink communication with a first latency type via the communication link. Determining the first variable delay budget may also include: determining a downlink variable delay budget for downlink communication with a first latency type via the communication link. In some cases, the first variable delay budget may be determined based on a set of RAN capabilities that may have been identified at 315. In some cases, the first variable delay budget may be determined based on a set of system capabilities that may have been identified at 315. In some cases, the first variable delay budget may be determined based on configuration information that may have been determined at 315. In some cases, SMF 220-a may receive a request to establish or modify a QoS flow corresponding to the communication link, where the first variable delay budget may be determined in response to the request. In some cases, SMF 220-a may receive a request for any of the following: handover of UE 115-b, PDU session establishment of UE 115-b, PDU session modification of UE 115-b, or any combination thereof, where the first variable delay budget may be determined in response to the request.

[0122] At 325, SMF 220-a may send a delay budget configuration to base station 105-b and base station 105-b may receive the delay budget configuration from SMF 220-a, the delay budget configuration indicating the first variable delay budget and a second variable delay budget for communication with a first latency type between UE 115-b and core network entity 205-a via the communication link. In some cases, the second variable delay budget may additionally or alternatively be used for communication with a first latency type between UE 115-b and base station 105-b via the communication link. In some cases, SMF 220-a may send the delay budget configuration based on any of the following: QoS associated with UE 115-b, one or more QoS rules associated with the communication link, one or more uplink packet detection rules, one or more downlink packet detection rules, or any combination. In some cases, sending the delay budget configuration may include: sending a first IE that indicates the total delay budget for communication with a first latency type between UE 115-b and core network entity 205-a via the communication link. In some cases, sending the delay budget configuration may include: sending a second IE that indicates the first variable delay budget. In some cases, the first variable delay budget may be indicated as a fraction of the second variable delay budget.

[0123] At 330, the SMF 220-a may send a latency budget configuration to the UPF 225-a and the UPF 225-a may receive the latency budget configuration from the SMF 220-a. The UPF 225 may use the latency budget configuration to receive an uplink transmission from the UE 115-b via a communication link, for example. At 335, the SMF 220-a may determine a total latency budget for communication between the UE 115-b and the core network entity 205-a via the communication link with a first latency type based on the latency budget configuration.

[0124] At 340, the base station 105-b may identify one or more variable latency budgets. For example, the base station 105-b may identify an uplink variable latency budget for uplink communication with a first latency type via the communication link based on a latency budget configuration that may have been received at 325. In some cases, the base station 105-b may also identify a downlink variable latency budget for downlink communication with a first latency type via the communication link based on the latency budget configuration. In some cases, the uplink variable latency budget and the downlink variable latency budget may be different.

[0125] At 345, the base station 105-b may determine a total latency budget for communication between the UE 115-a and the core network entity 205-a via the communication link with a first latency type based on the latency budget configuration.

[0126] At 350, the base station 105-b may schedule communication between the UE 115-b and the base station 105-b based on a first variable latency budget and a second variable latency budget. For example, the base station 105-b may send one or more scheduling messages to the UE 115-b and the UE 115-b may receive one or more scheduling messages from the base station 105-b, the one or more scheduling messages for indicating, for example, time and frequency resources to utilize for communication. In some cases, communication between the UE 115-b and the base station 105-b may be scheduled based on the total latency budget. In some cases, communication between the UE 115-b and the base station 105-b may be scheduled based on an uplink variable latency budget or a downlink variable latency budget that may have been identified at 340.

[0127] Figure 4 Block diagram 400 of a device 405 is shown that supports a latency budget for low latency communication in accordance with aspects of the present disclosure. The device 405 may be an example of aspects of the base station 105 as described herein. The device 405 may include a receiver 410, a communication manager 415, and a transmitter 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0128] The receiver 410 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to the latency budget for low-latency communication, etc.). The information can be passed to other components of the device 405. The receiver 410 can be an example of aspects of the transceiver 720 described with reference to Figure 7 FIG. The receiver 410 can utilize a single antenna or a set of antennas.

[0129] The communication manager 415 can identify a communication link for traffic associated with a first latency type between the UE and a core network node via a radio access node. The communication manager 415 can also receive a latency budget configuration from the core network node indicating a first variable latency budget and a second variable latency budget, where the first variable latency budget is for communication with the first latency type between the radio access node and the core network node via the communication link, and the second variable latency budget is for communication with the first latency type between the UE and the core network node via the communication link. The communication manager 415 can also schedule communication between the UE and the radio access node based on the first variable latency budget and the second variable latency budget. The communication manager 415 can be an example of aspects of the communication manager 710 described herein.

[0130] The communication manager 415 or its sub-components can be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 415 or its sub-components can be performed by 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0131] The communication manager 415 or its sub-components can be physically located at various locations, including being distributed such that some of the functions are implemented by one or more physical components at different physical locations. In some examples, according to aspects of this disclosure, the communication manager 415 or its sub-components can be separate and distinct components. In some examples, according to aspects of this disclosure, the communication manager 415 or its sub-components can be combined with one or more other hardware components (including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or a combination thereof).

[0132] Transmitter 420 can send signals generated by other components of device 405. In some examples, transmitter 420 can be co-located with receiver 410 in a transceiver module. For example, transmitter 420 can be an example of aspects of transceiver 720 described with reference to Figure 7 Transmitter 420 can utilize a single antenna or a set of antennas.

[0133] Figure 5 Block diagram 500 of device 505 in accordance with aspects of the present disclosure shows support for a latency budget for low latency communication. Device 505 can be an example of aspects of device 405 or base station 105 described herein. Device 505 can include receiver 510, communication manager 515, and transmitter 535. Device 505 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0134] Receiver 510 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to a latency budget for low latency communication, etc.). The information can be passed to other components of device 505. Receiver 510 can be an example of aspects of transceiver 720 described with reference to Figure 7 Receiver 510 can utilize a single antenna or a set of antennas.

[0135] Communication manager 515 can be an example of aspects of communication manager 415 described herein. Communication manager 515 can include communication link module 520, latency budget configuration module 525, and communication scheduler 530. Communication manager 515 can be an example of aspects of communication manager 710 described herein.

[0136] Communication link module 520 can identify a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node.

[0137] Latency budget configuration module 525 can receive a latency budget configuration from the core network node indicating a first variable latency budget and a second variable latency budget, the first variable latency budget for communication with a first latency type between the radio access node and the core network node via the communication link, and the second variable latency budget for communication with a first latency type between the UE and the core network node via the communication link.

[0138] Communication scheduler 530 can schedule communication between the UE and the radio access node based on the first variable latency budget and the second variable latency budget.

[0139] Transmitter 535 may send signals generated by other components of device 505. In some examples, transmitter 535 may be co-located with receiver 510 in a transceiver module. For example, transmitter 535 may be an example of aspects of transceiver 720 described with reference to Figure 7 Transmitter 535 may utilize a single antenna or a set of antennas.

[0140] Figure 6 FIG. 600 is a block diagram showing a communication manager 605 that supports a latency budget for low latency communication in accordance with aspects of the present disclosure. Communication manager 605 may be an example of aspects of communication manager 415, communication manager 515, or communication manager 710 described herein. Communication manager 605 may include a communication link module 610, a latency budget configuration module 615, a communication scheduler 620, a variable latency budget module 625, and a total latency budget module 630. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0141] Communication link module 610 may identify a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node. In some cases, the communication link corresponds to a QoS flow associated with the first latency type. In some cases, the traffic associated with the first latency type includes TSN traffic.

[0142] Latency budget configuration module 615 may receive a latency budget configuration from the core network node indicating a first variable latency budget and a second variable latency budget, the first variable latency budget for communication with the first latency type between the radio access node and the core network node via the communication link, and the second variable latency budget for communication with the first latency type between the UE and the core network node via the communication link.

[0143] In some examples, latency budget configuration module 615 may receive a first IE indicating a total latency budget for communication with the first latency type between the UE and the core network node via the communication link. In some cases, the second variable latency budget is for communication with the first latency type between the UE and the radio access node via the communication link.

[0144] Communication scheduler 620 may schedule communication between the UE and the radio access node based on the first variable latency budget and the second variable latency budget. Variable latency budget module 625 may identify an uplink variable latency budget for uplink communication with the first latency type via the communication link based on the latency budget configuration.

[0145] In some examples, the variable delay budget module 625 may identify a downlink variable delay budget for downlink communication having a first delay type via a communication link based on a delay budget configuration, wherein communication between the UE and the radio access node is scheduled based on an uplink variable delay budget or a downlink variable delay budget.

[0146] In some examples, the variable delay budget module 625 may receive a second IE indicating a first variable delay budget. In some cases, the uplink variable delay budget and the downlink variable delay budget are different. In some cases, the first variable delay budget is indicated as a fraction of the second variable delay budget. In some cases, the first variable delay budget may be based on a set of RAN capabilities for the radio access node. In some cases, the first variable delay budget is based on a set of system capabilities for communication between the UE and the core network node.

[0147] In some cases, the first variable delay budget is determined based on configuration information of the UE, the radio access node, or the core network node, where the configuration information includes: dynamic information from a TSN system associated with the UE, a TSN traffic class associated with a QoS flow corresponding to the communication link, subscription information associated with the UE, or any combination thereof.

[0148] The total delay budget module 630 may determine a total delay budget for communication having a first delay type between the UE and the core network node via a communication link based on a delay budget configuration, wherein communication between the UE and the radio access node is scheduled based on the total delay budget.

[0149] Figure 7 FIG. shows a system 700 including a device 705 that supports a delay budget for low latency communication in accordance with aspects of the present disclosure. The device 705 may be an example of the device 405, the device 505, or the base station 105 described herein or include components of the device 405, the device 505, or the base station 105. The device 705 may include components for two-way voice and data communication, including components for sending and receiving communication, including a communication manager 710, a network communication manager 715, a transceiver 720, an antenna 725, a memory 730, a processor 740, and an inter-station communication manager 745. These components may communicate electronically via one or more buses (e.g., bus 750).

[0150] The communication manager 710 may perform the following operations: identify a communication link for traffic associated with a first latency type between the UE and a core network node via a radio access node; receive from the core network node a latency budget configuration indicating a first variable latency budget and a second variable latency budget, the first variable latency budget for communication with the first latency type between the radio access node and the core network node via the communication link, and the second variable latency budget for communication with the first latency type between the UE and the core network node via the communication link; and schedule communication between the UE and the radio access node based on the first variable latency budget and the second variable latency budget.

[0151] The network communication manager 715 may manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 715 may manage the transmission of data communication for client devices (such as one or more UEs 115).

[0152] The transceiver 720 may communicate bidirectionally via one or more antennas, wired or wireless links as described herein. For example, the transceiver 720 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 720 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna. In some cases, the wireless device may include a single antenna 725. However, in some cases, the device may have more than one antenna 725, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0153] The memory 730 may include random access memory (RAM), read-only memory (ROM), or a combination thereof. The memory 730 may store computer-readable code 735, which includes instructions that, when executed by a processor (e.g., processor 740), cause the device to perform the various functions described herein. In some cases, in addition, the memory 730 may also contain a basic input / output system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0154] The processor 740 may include intelligent hardware devices (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks supporting a latency budget for low-latency communication).

[0155] The inter-station communication manager 745 may manage communication with other base stations 105 and may include a controller or scheduler for collaboratively controlling communication with the UE 115 with other base stations 105. For example, the inter-station communication manager 745 may coordinate the scheduling of transmissions to the UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communication manager 745 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between the base stations 105.

[0156] The code 735 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. The code 735 may be stored in a non-transitory computer-readable medium (such as system memory or other types of memory). In some cases, the code 735 may not be directly executable by the processor 740, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0157] Figure 8 Block diagram 800 illustrates a device 805 in accordance with aspects of the present disclosure that supports a latency budget for low-latency communication. The device 805 may be an example of aspects of a network entity as described herein. The device 805 may include a receiver 810, a communication manager 815, and a transmitter 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0158] The receiver 810 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to a latency budget for low-latency communication, etc.). The information may be passed to other components of the device 805. The receiver 810 may be an example of aspects of the transceiver 1120 described with reference to Figure 11 The receiver 810 may utilize a single antenna or a set of antennas.

[0159] The communication manager 815 may perform the following operations: identify a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node; determine a first variable delay budget for communication with the first latency type between the radio access node and the core network node via the communication link; and send a delay budget configuration to the radio access node, the delay budget configuration indicating the first variable delay budget and a second variable delay budget for communication with the first latency type between the UE and the core network node via the communication link. The communication manager 815 may be an example of aspects of the communication manager 1110 described herein.

[0160] The communication manager 815 or its sub-components may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 815 or its sub-components may be performed by a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0161] The communication manager 815 or its sub-components may be physically located at various locations, including being distributed such that some of the functions are implemented by one or more physical components at different physical locations. In some examples, in accordance with aspects of this disclosure, the communication manager 815 or its sub-components may be separate and distinct components. In some examples, in accordance with aspects of this disclosure, the communication manager 815 or its sub-components may be combined with one or more other hardware components, including but not limited to I / O components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0162] The transmitter 820 may send signals generated by other components of the device 805. In some examples, the transmitter 820 may be co-located with the receiver 810 in a transceiver module. For example, the transmitter 820 may be an example of aspects of the transceiver 1120 described with reference to Figure 11 The transmitter 820 may utilize a single antenna or a group of antennas.

[0163] Figure 9FIG. 900 is a block diagram of a device 905 that, in accordance with aspects of the present disclosure, supports a latency budget for low latency communications. The device 905 may be an example of aspects of a device 805 or a network entity (such as a UE 115) described herein. The device 905 may include a receiver 910, a communication manager 915, and a transmitter 935. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0164] The receiver 910 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to a latency budget for low latency communications, etc.). The information may be passed to other components of the device 905. The receiver 910 may be an example of aspects of the transceiver 1120 described with reference to Figure 11 . The receiver 910 may utilize a single antenna or a set of antennas.

[0165] The communication manager 915 may be an example of aspects of the communication manager 815 described herein. The communication manager 915 may include a communication link manager 920, a variable latency budget manager 925, and a latency budget configuration manager 930. The communication manager 915 may be an example of aspects of the communication manager 1110 described herein. The communication link manager 920 may identify a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node.

[0166] The variable latency budget manager 925 may determine a first variable latency budget for communications having a first latency type between a radio access node and a core network node via the communication link. The latency budget configuration manager 930 may send a latency budget configuration to the radio access node, the latency budget configuration indicating the first variable latency budget and a second variable latency budget for communications having a first latency type between a UE and a core network node via the communication link. The transmitter 935 may send signals generated by other components of the device 905. In some examples, the transmitter 935 may be co-located with the receiver 910 in a transceiver module. For example, the transmitter 935 may be an example of aspects of the transceiver 1120 described with reference to Figure 11 . The transmitter 935 may utilize a single antenna or a set of antennas.

[0167] Figure 10FIG. 1000 is a block diagram showing a communication manager 1005 that supports a latency budget for low latency communication in accordance with aspects of the present disclosure. The communication manager 1005 may be an example of aspects of the communication manager 815, communication manager 915, or communication manager 1110 described herein. The communication manager 1005 may include a communication link manager 1010, a variable latency budget manager 1015, a latency budget configuration manager 1020, an overall latency budget manager 1025, an SMF manager 1030, and a capabilities manager 1035. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0168] The communication link manager 1010 may identify a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node. In some cases, the communication link corresponds to a QoS flow associated with the first latency type. In some cases, the traffic associated with the first latency type includes TSN traffic.

[0169] The variable latency budget manager 1015 may determine a first variable latency budget for communication with a first latency type between a radio access node and a core network node via the communication link. In some examples, the variable latency budget manager 1015 may determine an uplink variable latency budget for uplink communication with a first latency type via the communication link. In some examples, the variable latency budget manager 1015 may determine a downlink variable latency budget for downlink communication with a first latency type via the communication link. In some examples, the variable latency budget manager 1015 may receive a request to establish or modify a QoS flow corresponding to the communication link, wherein the first variable latency budget is determined in response to the request.

[0170] In some examples, the variable latency budget manager 1015 may receive a request for: a handover of the UE, a PDU session establishment of the UE, a PDU session modification of the UE, or any combination thereof, wherein the first variable latency budget is determined in response to the request. In some examples, the variable latency budget manager 1015 may send a second IE indicating the first variable latency budget. In some cases, the second variable latency budget is for communication with a first latency type between the UE and the radio access node via the communication link. In some cases, the uplink variable latency budget and the downlink variable latency budget are different. In some cases, the first variable latency budget is indicated as a fraction of the second variable latency budget.

[0171] The delay budget configuration manager 1020 may send a delay budget configuration to a radio access node, the delay budget configuration indicating a first variable delay budget and a second variable delay budget for communication with a first latency type via a communication link between the UE and a core network node. In some examples, the delay budget configuration manager 1020 may send the delay budget configuration to the UPF. In some examples, the delay budget configuration manager 1020 may send the delay budget configuration based on the following: QoS associated with the UE, one or more QoS rules associated with the communication link, one or more uplink packet detection rules, one or more downlink packet detection rules, or any combination thereof.

[0172] The total delay budget manager 1025 may determine a total delay budget for communication with a first latency type via a communication link between the UE and a core network node based on the delay budget configuration. In some examples, the total delay budget manager 1025 may send a first IE, the first IE indicating the total delay budget for communication with a first latency type via a communication link between the UE and a core network node. The SMF manager 1030 may, at the SMF, determine a first variable delay budget for communication with a first latency type via a communication link between the radio access node and the core network node.

[0173] The capability manager 1035 may identify a set of RAN capabilities for the radio access node, wherein the first variable delay budget is determined based on the set of RAN capabilities. In some examples, the capability manager 1035 may identify a set of system capabilities for communication between the UE and the core network node, wherein the first variable delay budget is determined based on the set of system capabilities.

[0174] In some examples, the capabilities manager 1035 may determine configuration information of a UE, a radio access node, or a core network node, wherein a first variable latency budget is determined based on the configuration information. In some cases, the RAN capabilities set includes: subcarrier spacing for communication via a radio access node, support for micro-slot communication via a radio access node, frame structure for communication via a radio access node, bandwidth for communication via a radio access node, bandwidth part for communication via a radio access node, or any combination thereof. In some cases, the system capabilities set may include: latency limits for services associated with a first latency type, service classes of services associated with a first latency type, or any combination thereof. In some cases, the configuration information is based on the TSN process for determining the capabilities of a wireless communication system. In some cases, the configuration information includes dynamic information from a TSN system associated with the UE or a TSN service class associated with a QoS flow corresponding to a communication link. In some cases, the configuration information includes subscription information associated with the UE.

[0175] Figure 11 Aspects in accordance with the present disclosure are illustrated in a diagram of a system 1100 that includes a device 1105 that supports a latency budget for low latency communication. The device 1105 may be an example of a device 805, a device 905, or a network entity as described herein or include components of a device 805, a device 905, or a network entity. The device 1105 may include components for two-way voice and data communication, including components for sending and receiving communication, including a communication manager 1110, an I / O controller 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1135. These components may communicate electronically via one or more buses (e.g., bus 1145).

[0176] The communication manager 1110 may perform the following operations: identify a communication link for communication of a service associated with a first latency type between a UE and a core network node via a radio access node; determine a first variable latency budget for communication with a first latency type between the radio access node and the core network node via the communication link; and send a latency budget configuration to the radio access node, the latency budget configuration indicating the first variable latency budget and a second variable latency budget for communication with a first latency type between the UE and the core network node via the communication link.

[0177] The I / O controller 1115 can manage the input and output signals for the device 1105. The I / O controller 1115 can also manage peripheral devices not integrated into the device 1105. In some cases, the I / O controller 1115 can represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1115 can utilize an operating system such as or another known operating system. In other cases, the I / O controller 1115 can represent, or interact with, a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 1115 can be implemented as part of a processor. In some cases, a user can interact with the device 1105 via the I / O controller 1115 or via the hardware components controlled by the I / O controller 1115.

[0178] The transceiver 1120 can communicate bidirectionally via one or more antennas, wired or wireless links as described herein. For example, the transceiver 1120 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1120 can also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna.

[0179] In some cases, the wireless device can include a single antenna 1125. However, in some cases, the device can have more than one antenna 1125, which can be capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0180] The memory 1130 can include RAM and ROM. The memory 1130 can store computer-readable, computer-executable code 1140 that includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, in addition, the memory 1130 can contain a BIOS that can control basic hardware or software operations, such as interactions with peripheral components or devices.

[0181] The processor 1135 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting a latency budget for low-latency communication).

[0182] The code 1140 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. The code 1140 may be stored in a non-transitory computer-readable medium (such as system memory or other types of memory). In some cases, the code 1140 may not be directly executable by the processor 1135, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0183] Figure 12 Flowcharts illustrating a method 1200 for supporting a latency budget for low-latency communication are shown in accordance with aspects of the present disclosure. Operations of the method 1200 may be implemented by a network entity or its components as described herein. For example, operations of the method 1200 may be performed by a communication manager as described with reference to Figures 8 to 11 described. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the functions described herein. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the functions described herein.

[0184] At 1205, the network entity may identify a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node. The operation of 1205 may be performed according to the methods described herein. In some examples, aspects of the operation of 1205 may be performed by a communication link manager as described with reference to Figures 8 to 11 described.

[0185] At 1210, the network entity may determine a first variable latency budget for communication having a first latency type between a radio access node and a core network node via the communication link. The operation of 1210 may be performed according to the methods described herein. In some examples, aspects of the operation of 1210 may be performed by a variable latency budget manager as described with reference to Figures 8 to 11 described.

[0186] At 1215, a network entity may send a delay budget configuration indicating a first variable delay budget to a radio access node. The operation at 1215 may be performed according to the methods described herein. In some examples, aspects of the operation at 1215 may be performed by a delay budget configuration manager as described with reference to Figures 8 to 11 .

[0187] At 1220, the network entity may optionally send a delay budget configuration to the radio access node, the delay budget configuration indicating a second variable delay budget for communication having a first delay type between a UE and a core network node via a communication link. The operation at 1220 may be performed according to the methods described herein. In some examples, aspects of the operation at 1220 may be performed by a delay budget configuration manager as described with reference to Figures 8 to 11 .

[0188] Some wireless communication systems may be used to facilitate communication in networks that rely on relatively strict timing synchronization of network components (sometimes referred to as TSN systems). In some wireless communication systems, a QoS standard for a particular QoS flow may define a target PDB. The target PDB may set a target latency or total time delay for communication between a UE and a network entity in the wireless communication system, below which data packets being transmitted may be used. The PDB may also include a second delay component incurred between the radio access node and the UE. Together, the total PDB defines the target latency from the network entity, via the radio access node, to the UE.

[0189] The radio access node may use a first delay component incurred between the network entity and the radio access node to schedule uplink and downlink transmissions. In some wireless communication systems, the first delay component incurred between the network entity and the radio access node may be configured as a defined delay (e.g., 1 ms). However, for example, in a wireless communication system carrying TSN communication, the following deployment is expected: where the network entity and the radio access node are in relatively close geographical proximity, and thus the first delay component may be significantly less than the defined delay (e.g., meaning less than the configured delay of 1 ms). Thus, if the radio access node schedules communication with the UE based on the configured delay, the scheduling decision may be overly aggressive or overly conservative, depending on the actual delay.

[0190] Accordingly, the method 1200 provided herein provides for signaling a delay budget configuration to a radio access node, the delay budget configuration indicating a first variable delay budget between the radio access node and a network entity node and a second variable delay budget for communication between the UE and the network entity node. Based on the delay budget configuration, the radio access node can determine an estimate of the actual delay in such communication of the wireless communication system. Accordingly, based on signaling the determined delay to the radio access node, the radio access node can schedule communication between the UE, the radio access node, and the network entity relatively more accurately.

[0191] Figure 13 Aspects in accordance with the present disclosure illustrate a flowchart depicting a method 1300 for supporting a delay budget for low latency communication. Operations of the method 1300 may be implemented by a network entity or components thereof as described herein. For example, operations of the method 1300 may be performed by a communication manager as described with reference to Figures 8 to 11 the description. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the functions described herein. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the functions described herein.

[0192] At 1305, the network entity may identify a communication link for traffic associated with a first latency type between the UE and a core network node via a radio access node. The operation at 1305 may be performed in accordance with the methods described herein. In some examples, aspects of the operation at 1305 may be performed by a communication link manager as described with reference to Figures 8 to 11 the description.

[0193] At 1310, the network entity may identify a set of RAN capabilities for the radio access node, wherein the first variable delay budget is determined based on the set of RAN capabilities. The operation at 1310 may be performed in accordance with the methods described herein. In some examples, aspects of the operation at 1310 may be performed by a capabilities manager as described with reference to Figures 8 to 11 the description.

[0194] At 1315, the network entity may determine a first variable delay budget for communication having the first latency type between the radio access node and the core network node via the communication link. The operation at 1315 may be performed in accordance with the methods described herein. In some examples, aspects of the operation at 1315 may be performed by a variable delay budget manager as described with reference to Figures 8 to 11 the description.

[0195] At 1320, a network entity may send a delay budget configuration indicating a first variable delay budget to a radio access node. The operation at 1320 may be performed according to the methods described herein. In some examples, aspects of the operation at 1320 may be performed by a delay budget configuration manager as described with reference to Figures 8 to 11 the delay budget configuration manager described.

[0196] At 1325, the network entity may optionally send a delay budget configuration to the radio access node, the delay budget configuration indicating a second variable delay budget for communication of a first delay type via a communication link between the UE and a core network node. The operation at 1325 may be performed according to the methods described herein. In some examples, aspects of the operation at 1325 may be performed by a delay budget configuration manager as described with reference to Figures 8 to 11 the delay budget configuration manager described.

[0197] Some wireless communication systems may be used to facilitate communication in a network (sometimes referred to as a TSN system) that relies on relatively strict timing synchronization of network components. In some wireless communication systems, a QoS standard for a particular QoS flow may define a target PDB. The target PDB may set a target latency or total time delay for communication between a UE and a network entity in the wireless communication system, below which data packets being transmitted may be used. The PDB may also include a second delay component incurred between the radio access node and the UE. Together, the total PDB defines the target latency from the network entity, via the radio access node, to the UE.

[0198] The radio access node may use a first delay component incurred between the network entity and the radio access node to schedule uplink and downlink transmissions. In some wireless communication systems, the first delay component incurred between the network entity and the radio access node may be configured as a defined delay (e.g., 1 ms). However, for example, in a wireless communication system carrying TSN communication, the following deployment is expected: where the network entity and the radio access node are in a relatively close geographical proximity, and thus the first delay component may be significantly less than the defined delay (e.g., meaning less than the configured delay of 1 ms). Therefore, if the radio access node schedules communication with the UE based on the configured delay, the scheduling decision may be overly aggressive or overly conservative, depending on the actual delay.

[0199] Accordingly, the method 1300 provided herein provides for signaling a delay budget configuration to a radio access node, the delay budget configuration indicating a first variable delay budget between the radio access node and a network entity node and a second variable delay budget for communication between a UE and the network entity node. By identifying a set of RAN capabilities for the radio access node, based on which the first variable delay budget is determined, the network entity can provide a relatively more accurate determination of the first variable delay budget. Based on the delay budget configuration, the radio access node can determine an estimate of the actual delay in such communication in the wireless communication system. Accordingly, based on signaling the determined delay to the radio access node, the radio access node can schedule communication between the UE, the radio access node, and the network entity relatively more accurately.

[0200] Figure 14 Aspects in accordance with the present disclosure are shown in a flow diagram illustrating a method 1400 for supporting a delay budget for low latency communication. Operations of the method 1400 may be implemented by a network entity or components thereof as described herein. For example, operations of the method 1400 may be performed by a communication manager as described with reference to Figures 8 to 11 the description. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the functions described herein. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the functions described herein.

[0201] At 1405, the network entity may identify a communication link for traffic associated with a first latency type between a UE and a core network node via a radio access node. The operation of 1405 may be performed according to the methods described herein. In some examples, aspects of the operation of 1405 may be performed by a communication link manager as described with reference to Figures 8 to 11 the description.

[0202] At 1410, the network entity may identify a set of system capabilities for communication between the UE and the core network node, based on which the first variable delay budget is determined. The operation of 1410 may be performed according to the methods described herein. In some examples, aspects of the operation of 1410 may be performed by a capabilities manager as described with reference to Figures 8 to 11 the description.

[0203] At 1415, the network entity may determine a first variable delay budget for communication having the first latency type between the radio access node and the core network node via the communication link. The operation of 1415 may be performed according to the methods described herein. In some examples, aspects of the operation of 1415 may be performed by a variable delay budget manager as described with reference to Figures 8 to 11 the description.

[0204] At 1420, a network entity may send a delay budget configuration indicating a first variable delay budget to a radio access node. The operation at 1420 may be performed according to the methods described herein. In some examples, aspects of the operation at 1420 may be performed by a delay budget configuration manager as described with reference to Figures 8 to 11 the description.

[0205] At 1425, the network entity may optionally send a delay budget configuration to the radio access node, the delay budget configuration indicating a second variable delay budget for communication having a first delay type between a UE and a core network node via a communication link. The operation at 1425 may be performed according to the methods described herein. In some examples, aspects of the operation at 1425 may be performed by a delay budget configuration manager as described with reference to Figures 8 to 11 the description.

[0206] Some wireless communication systems may be used to facilitate communication in a network (sometimes referred to as a TSN system) that relies on relatively strict timing synchronization of network components. In some wireless communication systems, a QoS standard for a particular QoS flow may define a target PDB. The target PDB may set a target latency or total time delay for communication between a UE and a network entity in the wireless communication system, below which data packets being transmitted may be used. The PDB may also include a second delay component incurred between the radio access node and the UE. Together, this total PDB defines the target latency from the network entity, via the radio access node, to the UE.

[0207] The radio access node may use a first delay component incurred between the network entity and the radio access node to schedule uplink and downlink transmissions. In some wireless communication systems, the first delay component incurred between the network entity and the radio access node may be configured as a defined delay (e.g., 1 ms). However, for example, in a wireless communication system carrying TSN communication, the following deployment is expected: where the network entity and the radio access node are in a relatively close geographical proximity, and thus the first delay component may be significantly less than the defined delay (e.g., meaning less than the configured delay of 1 ms). Thus, if the radio access node schedules communication with the UE based on the configured delay, the scheduling decision may be overly aggressive or overly conservative, depending on the actual delay.

[0208] Accordingly, the method 1400 provided herein provides for signaling a delay budget configuration to a radio access node, the delay budget configuration indicating a first variable delay budget between the radio access node and a network entity node and a second variable delay budget for communication between the UE and the network entity node. By identifying a set of system capabilities for communication between the UE and a core network node, where the first variable delay budget is determined based on the set of system capabilities, the network entity can provide a relatively more accurate determination of the first variable delay budget. Based on the delay budget configuration, the radio access node can determine an estimate of the actual delay in such communication in the wireless communication system. Accordingly, based on signaling the determined delay to the radio access node, the radio access node can schedule communication between the UE, the radio access node, and the network entity relatively more accurately.

[0209] Figure 15 Aspects in accordance with the present disclosure illustrate a flowchart depicting a method 1500 for supporting a delay budget for low latency communication. Operations of the method 1500 may be implemented by a network entity or components thereof as described herein. For example, operations of the method 1500 may be performed by a communication manager as described with reference to Figures 8 to 11 the description. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the functions described herein. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the functions described herein.

[0210] At 1505, the network entity may identify a communication link for traffic associated with a first latency type between the UE and a core network node via a radio access node. The operation at 1505 may be performed according to the methods described herein. In some examples, aspects of the operation at 1505 may be performed by a communication link manager as described with reference to Figures 8 to 11 the description.

[0211] At 1510, the network entity may determine configuration information of the UE, the radio access node, or the core network node, where the first variable delay budget is determined based on the configuration information. The operation at 1510 may be performed according to the methods described herein. In some examples, aspects of the operation at 1510 may be performed by a capabilities manager as described with reference to Figures 8 to 11 the description.

[0212] At 1515, the network entity may determine a first variable delay budget for communication having a first latency type between the radio access node and the core network node via the communication link. The operation at 1515 may be performed according to the methods described herein. In some examples, aspects of the operation at 1515 may be performed by a variable delay budget manager as described with reference to Figures 8 to 11 the description.

[0213] At 1520, a network entity may send a delay budget configuration indicating a first variable delay budget to a radio access node. The operation at 1520 may be performed according to the methods described herein. In some examples, aspects of the operation at 1520 may be performed by a delay budget configuration manager as described with reference to Figures 8 to 11 the description.

[0214] At 1525, the network entity may optionally send a delay budget configuration to the radio access node, the delay budget configuration indicating a second variable delay budget for communication of a first delay type via a communication link between a UE and a core network node. The operation at 1525 may be performed according to the methods described herein. In some examples, aspects of the operation at 1525 may be performed by a delay budget configuration manager as described with reference to Figures 8 to 11 the description.

[0215] Some wireless communication systems may be used to facilitate communication in a network (sometimes referred to as a TSN system) that relies on relatively strict timing synchronization of network components. In some wireless communication systems, a QoS standard for a particular QoS flow may define a target PDB. The target PDB may set a target latency or total time delay for communication between a UE and a network entity in the wireless communication system, below which data packets to be transmitted may be used. The PDB may also include a second delay component incurred between the radio access node and the UE. Together, the total PDB defines the target latency from the network entity, via the radio access node, to the UE.

[0216] The radio access node may use a first delay component incurred between the network entity and the radio access node to schedule uplink and downlink transmissions. In some wireless communication systems, the first delay component incurred between the network entity and the radio access node may be configured as a defined delay (e.g., 1 ms). However, for example, in a wireless communication system carrying TSN communication, a deployment is expected where the network entity and the radio access node are in relatively close geographical proximity, and thus the first delay component may be significantly less than the defined delay (e.g., meaning less than the configured delay of 1 ms). Therefore, if the radio access node schedules communication with the UE based on the configured delay, the scheduling decision may be overly aggressive or overly conservative, depending on the actual delay.

[0217] Accordingly, the method 1500 provided herein provides signaling to a radio access node of a latency budget configuration that indicates a first variable latency budget between the radio access node and a network entity node and a second variable latency budget for communication between the UE and the network entity node. By determining configuration information of the UE, the radio access node, or a core network node, based on which the first variable latency budget is determined, the network entity can provide a relatively more accurate determination of the first variable latency budget. Based on the latency budget configuration, the radio access node can determine an estimate of the actual latency in such communication in a wireless communication system. Accordingly, based on signaling the determined latency to the radio access node, the radio access node can schedule communication between the UE, the radio access node, and the network entity relatively more accurately.

[0218] Figure 16 Aspects in accordance with the present disclosure are shown in a flow diagram illustrating a method 1600 for supporting a latency budget for low latency communication. Operations of method 1600 may be implemented by a base station 105 or components thereof as described herein. For example, operations of method 1600 may be performed by a communication manager as described with reference to Figures 4 to 7 described. In some examples, the base station may execute a set of instructions to control functional elements of the base station to perform the functions described herein. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described herein.

[0219] At 1605, the base station may identify a communication link for traffic associated with a first latency type between the UE and a core network node via a radio access node. The operation of 1605 may be performed according to the methods described herein. In some examples, aspects of the operation of 1605 may be performed by a communication link module as described with reference to Figures 4 to 7 described.

[0220] At 1610, the base station may receive from the core network node a latency budget configuration indicating a first variable latency budget and a second variable latency budget, the first variable latency budget for communication having a first latency type between the radio access node and the core network node via the communication link, and the second variable latency budget for communication having a first latency type between the UE and the core network node via the communication link. The operation of 1610 may be performed according to the methods described herein. In some examples, aspects of the operation of 1610 may be performed by a latency budget configuration module as described with reference to Figures 4 to 7 described.

[0221] At 1615, the base station may schedule communication between the UE and the radio access node based on a first variable latency budget and a second variable latency budget. The operations at 1615 may be performed according to the methods described herein. In some examples, aspects of the operations at 1615 may be performed by a communication scheduler as described with reference to Figures 4 to 7 described.

[0222] Some wireless communication systems may be used to facilitate communication in a network that relies on relatively strict timing synchronization of network components (sometimes referred to as a TSN system). In some wireless communication systems, QoS criteria for a particular QoS flow may define a target PDB. The target PDB may set a target latency or total time delay for communication between a UE and a network entity in the wireless communication system, below which data packets being transmitted may be used. The PDB may also include a second delay component incurred between the radio access node and the UE. Together, the total PDB defines the target latency from the network entity, via the radio access node, to the UE.

[0223] The radio access node may use a first delay component incurred between the network entity and the radio access node to schedule uplink and downlink transmissions. In some wireless communication systems, the first delay component incurred between the network entity and the radio access node may be configured as a defined delay (e.g., 1 ms). However, for example, in a wireless communication system carrying TSN communication, the following deployment is expected: where the network entity and the radio access node are in relatively close geographical proximity, and thus the first delay component may be significantly less than the defined delay (e.g., meaning less than the configured delay of 1 ms). Therefore, if the radio access node schedules communication with the UE based on the configured delay, the scheduling decision may be overly aggressive or overly conservative, depending on the actual delay.

[0224] Accordingly, method 1600 provided herein provides for signaling a delay budget configuration to the radio access node, the delay budget configuration indicating a first variable latency budget between the radio access node and the network entity node and a second variable latency budget for communication between the UE and the network entity node. Based on the delay budget configuration, the radio access node may determine an estimate of the actual delay in such communication in the wireless communication system. Accordingly, based on signaling the determined delay to the radio access node, the radio access node may schedule communication between the UE, the radio access node, and the network entity relatively more accurately.

[0225] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Additionally, aspects from two or more methods may be combined.

[0226] The techniques described herein can be used in various wireless communication systems such as 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), and other systems. CDMA systems can implement radio technologies such as CDMA 2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers standards such as IS-2000, IS-95, and IS-856. The IS-2000 version is often referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is often referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (W-CDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM).

[0227] OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used in the systems and radio technologies mentioned herein as well as other systems and radio technologies. Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for purposes of illustration and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein can be applied beyond LTE, LTE-A, LTE-A Pro, or NR applications.

[0228] Macro cells typically cover a relatively large geographical area (e.g., with a radius of several kilometers) and can permit unrestricted access by UEs 115 having a service subscription with the network provider. Compared to macro cells, small cells can be associated with lower power base stations 105, and small cells can operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells. According to various examples, small cells can include picocells, femtocells, and microcells. For example, a picocell can cover a small geographical area and can permit unrestricted access by UEs 115 having a service subscription with the network provider. A femtocell can also cover a small geographical area (e.g., a residence) and can provide restricted access by UEs 115 associated with the femtocell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 for users in a residence, etc.). The eNB for a macro cell can be referred to as a macro eNB. The eNB for a small cell can be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB can support one or more (e.g., two, three, four, etc.) cells and can also support communication using one or more component carriers.

[0229] The wireless communication system 100 or systems described herein can support synchronous operation or asynchronous operation. For synchronous operation, the base stations 105 can have similar frame timings, and transmissions from different base stations 105 can be approximately aligned in time. For asynchronous operation, the base stations 105 can have different frame timings, and transmissions from different base stations 105 can not be aligned in time. The techniques described herein can be used for synchronous operation or asynchronous operation.

[0230] The information and signals described herein can be represented using any of a variety of different technologies and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0231] The various illustrative blocks and modules described in connection with the disclosure herein can be implemented or performed using a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0232] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a non-transitory computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located in various places, including being distributed such that portions of the functions are implemented at different physical locations.

[0233] Computer-readable media includes both non-transitory computer storage media and communication media, where communication media includes any medium that facilitates transfer of a computer program from one place to another. The non-transitory storage media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc read only memory (CD-ROM) or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code units in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Additionally, any connection is properly termed a non-transitory computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0234] As used herein (including in the claims), the "or" as used in a list of items (e.g., a list of items that ends with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of A, B, or C, for example, means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Further, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0235] In the figures, similar components or features may have the same reference numeral. Additionally, various components of the same type may be distinguished by following the reference numeral with a dash and a second numeral, the second numeral being used to differentiate among similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second numeral or any other subsequent numerals.

[0236] The description set forth herein with reference to the figures describes example configurations and does not represent all examples that may be implemented or that are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples". For the purpose of providing an understanding of the described technology, the detailed description includes specific details. However, the technology may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0237] The present description is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein but is accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a core network node, comprising: identifying a communication link for traffic associated with a first latency type between a user equipment (UE) and the core network node via a radio access node; determining a first variable delay budget for communication with the first latency type between the radio access node and the core network node via the communication link; and sending a delay budget configuration to the radio access node, the delay budget configuration indicating the first variable delay budget and a second variable delay budget for communication with the first latency type between the UE and the core network node via the communication link, wherein the second variable delay budget is for communication with the first latency type between the UE and the radio access node via the communication link, and the first variable delay budget is different from the second variable delay budget.

2. The method according to claim 1, wherein, The second variable delay budget is at least partially based on subtracting the first variable delay budget from a total delay budget.

3. The method according to claim 1, wherein Determining the first variable delay budget includes: at a session management function unit (SMF), determining the first variable delay budget for communication with the first latency type between the radio access node and the core network node via the communication link.

4. The method according to claim 3, further comprising: sending the delay budget configuration to a user plane function unit (UPF).

5. The method according to claim 3, further comprising: receiving a request to establish or modify a quality of service (QoS) flow corresponding to the communication link, wherein the first variable delay budget is determined in response to the request.

6. The method according to claim 5, further comprising: determining the first variable delay budget at least partially based on the QoS flow.

7. The method according to claim 3, further comprising: receiving a request for any of: handover of the UE, packet data unit (PDU) session establishment of the UE, PDU session modification of the UE, or any combination thereof, wherein the first variable delay budget is at least partially based on the request.

8. The method according to claim 1, further comprising: identifying a radio access network (RAN) capability set for the radio access node, wherein the first variable delay budget is at least partially based on the RAN capability set.

9. The method according to claim 1, wherein Determining the first variable delay budget includes: determining an uplink variable delay budget for uplink communication with the first latency type via the communication link; and determining a downlink variable delay budget for downlink communication with the first latency type via the communication link.

10. The method according to claim 9, wherein, The uplink variable delay budget and the downlink variable delay budget are the same.

11. The method according to claim 1, further comprising: Determine a total delay budget for communication with the first delay type via the communication link between the UE and the core network node, at least partially based on the delay budget configuration.

12. The method according to claim 1, further comprising: Identifying a set of system capabilities for communication between the UE and the core network node, wherein the first variable delay budget is determined at least partially based on the set of system capabilities.

13. The method according to claim 12, wherein The set of system capabilities includes: a delay limit for the service associated with the first delay type, a QoS class for the service associated with the first delay type, or any combination thereof.

14. The method according to claim 1, further comprising: Determining configuration information of the UE, the radio access node, or the core network node, wherein the first variable delay budget is determined at least partially based on the configuration information.

15. The method according to claim 14, wherein, The configuration information is at least partially based on a time-sensitive network (TSN) process for determining the capabilities of a wireless communication system.

16. The method according to claim 14, wherein, The configuration information includes dynamic information from a time-sensitive network (TSN) system associated with the UE or a TSN service class associated with a quality of service (QoS) flow corresponding to the communication link.

17. The method according to claim 1, further comprising: Transmitting the delay budget configuration at least partially based on the following: quality of service (QoS) associated with the UE, one or more QoS rules associated with the communication link, one or more uplink packet detection rules, one or more downlink packet detection rules, or any combination thereof.

18. The method according to claim 1, wherein, The communication link corresponds to a quality of service (QoS) flow associated with the first delay type.

19. The method according to claim 1, wherein The service associated with the first delay type includes a time-sensitive network (TSN) service.

20. A method for wireless communication at a radio access node, comprising: Identifying a communication link for communication of a service associated with a first delay type between a user equipment (UE) and a core network node via the radio access node; Receiving a delay budget configuration from the core network node, the delay budget configuration indicating a first variable delay budget for communication with the first delay type via the communication link between the radio access node and the core network node, the delay budget configuration indicating a second variable delay budget for communication with the first delay type via the communication link between the UE and the core network node, wherein the second variable delay budget is for communication with the first delay type between the UE and the radio access node via the communication link, and the first variable delay budget is different from the second variable delay budget; And Scheduling communication between the UE and the radio access node at least partially based on the first variable delay budget and the second variable delay budget.

21. The method according to claim 20, further comprising: Identify an uplink variable delay budget for uplink communication with the first delay type via the communication link, at least in part based on the delay budget configuration; And Identify a downlink variable delay budget for downlink communication with the first delay type via the communication link, at least in part based on the delay budget configuration, wherein the communication between the UE and the radio access node is scheduled at least in part based on the uplink variable delay budget or the downlink variable delay budget.

22. The method according to claim 21, wherein, The uplink variable delay budget and the downlink variable delay budget are the same.

23. The method according to claim 20, wherein The communication link corresponds to a quality of service (QoS) flow associated with the first delay type.

24. The method according to claim 20, wherein The traffic associated with the first delay type includes time-sensitive network (TSN) traffic.

25. An apparatus for wireless communication at a core network node, comprising: A processor, A memory coupled to the processor; And Instructions stored in the memory and executable by the processor to cause the apparatus to: Identify a communication link for traffic associated with a first delay type between a user equipment (UE) and the core network node via a radio access node; Determine a first variable delay budget for communication with the first delay type between the radio access node and the core network node via the communication link; And Send a delay budget configuration to the radio access node, the delay budget configuration indicating the first variable delay budget and a second variable delay budget for communication with the first delay type between the UE and the core network node via the communication link, wherein the second variable delay budget is for communication with the first delay type between the UE and the radio access node via the communication link, and the first variable delay budget is different from the second variable delay budget.

26. An apparatus for wireless communication at a radio access node, comprising: A processor, A memory coupled to the processor; And Instructions stored in the memory and executable by the processor to cause the apparatus to: Identify a communication link for traffic associated with a first delay type between a user equipment (UE) and a core network node via the radio access node; Receive a delay budget configuration from the core network node, the delay budget configuration indicating a first variable delay budget for communication with the first delay type between the radio access node and the core network node via the communication link, the delay budget configuration indicating a second variable delay budget for communication with the first delay type between the UE and the core network node via the communication link, wherein the second variable delay budget is for communication with the first delay type between the UE and the radio access node via the communication link, and the first variable delay budget is different from the second variable delay budget; And Schedule communication between the UE and the radio access node, at least in part, based on the first variable delay budget and the second variable delay budget.

Images