CN112703708B

CN112703708B - Delay budget for low latency communications

Info

Publication number: CN112703708B
Application number: CN201980060165.9A
Authority: CN
Inventors: R·普拉卡什; V·约瑟夫; 朱西鹏; G·B·霍恩; O·厄兹蒂尔克; L·F·B·洛佩斯
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2018-09-28
Filing date: 2019-09-24
Publication date: 2024-03-12
Anticipated expiration: 2039-09-24
Also published as: US20200107339A1; US10904905B2; US10904907B2; EP3857829A1; WO2020068847A1; SG11202101544TA; CN117955923A; TW202025821A; CN112703708A; US20200205177A1

Abstract

In general terms, the described techniques provide for a core network to signal to a base station a delay budget configuration indicating a determined latency 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, wherein the delay budget configuration may include a first delay budget. The base station may be capable of determining 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 communications with the UE.

Description

Delay budget for low latency communications

Cross reference

This patent application claims priority to enjoying the following applications: U.S. patent application Ser. No. 16/579,792, entitled "DELAY BUDGET FOR LOW LATENCY COMMUNICATIONS (delay budget for Low latency communications)" filed by Prakash et al at 2019, 9 and 23; and U.S. provisional patent application No. 62/739,130, entitled "DELAY BUDGET FOR LOW LATENCY COMMUNICATIONS (delay budget for low latency communications)" filed by PRAKASH et al at 9, 28, 2018, each of which is assigned to the assignee of the present application and each of which is incorporated herein by reference in its entirety.

Background

Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems, such as Long Term Evolution (LTE) systems, LTE-advanced (LTE-a) systems, or LTE-a professional systems, and fifth generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems may employ techniques 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-spectrum OFDM (DFT-S-OFDM).

A wireless multiple-access communication system may include multiple base stations or network access nodes, each supporting communication for multiple communication devices, which may be otherwise referred to as User Equipment (UE), simultaneously. In some cases, various applications (e.g., motion control, discrete manufacturing) may utilize relatively stringent reliability and latency requirements.

Disclosure of Invention

The described technology relates to improved methods, systems, devices, and apparatus supporting delay budgets for low latency communications. In general terms, the described techniques provide for a first device (such as a core network entity) to signal a delay budget configuration to a second device (such as a base station), the delay 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 downlink transmissions, the delay budget configuration may include a first variable delay budget incurred between the core network entity and the radio access node (e.g., at the base station). The delay budget configuration may also include a second variable delay budget incurred between the base station and the UE. Together, the total delay budget may define a total delay for communication between the UE and the core network entity.

According to some aspects, one or more delay 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 delay budget configuration may include one or more delay budgets (e.g., variable or non-variable delay budgets) incurred between the CU and the DU. For example, the delay budget configuration may indicate a balanced budget (e.g., an average split delay budget) between the CU, the DU, and the UE. In such a case, the delay budget configuration may indicate that the second variable delay budget (e.g., between the base station of the RAN and the UE) is divided into respective delay budgets for each of CU to DU and DU to UE. In other examples, the delay 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 delay budget.

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

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

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

An apparatus for wireless communication is described. The apparatus 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 apparatus to: identifying a communication link for traffic associated with a first latency type between the UE and a core network node via the radio access node; determining a first variable delay budget for communications with a first latency type between the radio access node and the core network node via the communication link; and transmitting a delay budget configuration to the wireless access node, the delay budget configuration indicating a first variable delay budget and a second variable delay budget for communications between the UE and the core network node via the communication link having the first delay type.

Another apparatus for wireless communication is described. The apparatus may include means for: identifying a communication link for traffic associated with a first latency type between the UE and a core network node via the radio access node; determining a first variable delay budget for communications with a first latency type between the radio access node and the core network node via the communication link; and transmitting a delay budget configuration to the wireless access node, the delay budget configuration indicating a first variable delay budget and a second variable delay budget for communications between the UE and the core network node via the communication link having the first delay type.

A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: identifying a communication link for traffic associated with a first latency type between the UE and a core network node via the radio access node; determining a first variable delay budget for communications with a first latency type between the radio access node and the core network node via the communication link; and transmitting a delay budget configuration to the wireless access node, the delay budget configuration indicating a first variable delay budget and a second variable delay budget for communications between the UE and the core network node via the communication link having the first delay type.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second variable delay budget may be for communications between the UE and the wireless access node via a communication link having a first latency type.

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

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

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions to: an overall delay budget for communications with the first latency type over the communication link between the UE and the core network node is determined based on the delay budget configuration.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the first variable delay budget may include operations, features, units, or instructions to: at a Session Management Function (SMF), a first variable delay budget between a radio access node and a core network node for communications over a communication link having a first delay type is determined.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions to: the delay budget configuration is sent to a User Plane Function (UPF).

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

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions to: receiving a request for: a handover of the UE, a Packet Data Unit (PDU) session establishment of the UE, a PDU session modification of the UE, or any combination thereof, wherein the first variable delay budget may be determined in response to the request.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions to: a set of RAN capabilities for a wireless access node is identified, wherein a first variable delay budget may be determined based on the set of RAN capabilities.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the RAN capability set includes: a subcarrier spacing for communication via a wireless access node, support for micro-slot communication via a wireless access node, a frame structure for communication via a wireless access node, a bandwidth portion for communication via a wireless access node, or any combination thereof.

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

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

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions to: configuration information of the UE, the radio access node, or the core network node is determined, wherein the first variable delay budget may be determined based on the configuration information.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the configuration information may be based on a Time Sensitive Network (TSN) procedure for determining capabilities of the wireless communication system.

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

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

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions to: the delay budget configuration is sent based on: 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.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the transmit delay budget configuration may include operations, features, elements, or instructions to: transmitting a first Information Element (IE) indicating a total delay budget between the UE and the core network node for communications over the communication link having a first delay type; and transmitting a second IE indicating the first variable delay budget.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first variable delay budget may be indicated as a fraction of the second variable delay budget.

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

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

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

An apparatus for wireless communication is described. The apparatus 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 apparatus to: identifying a communication link for traffic associated with a first latency type between the UE and a core network node via the radio access node; receiving, from a core network node, a delay budget configuration indicating a first variable delay budget for communications between a wireless access node and the core network node via a communication link having a first delay type and a second variable delay budget for communications between a UE and the core network node via the communication link having the first delay type; and scheduling communications between the UE and the wireless access node based on the first variable delay budget and the second variable delay budget.

Another apparatus for wireless communication is described. The apparatus may include means for: identifying a communication link for traffic associated with a first latency type between the UE and a core network node via the radio access node; receiving, from a core network node, a delay budget configuration indicating a first variable delay budget for communications between a wireless access node and the core network node via a communication link having a first delay type and a second variable delay budget for communications between a UE and the core network node via the communication link having the first delay type; and scheduling communications between the UE and the wireless access node based on the first variable delay budget and the second variable delay budget.

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

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions to: identifying an uplink variable delay budget for uplink communications having a first latency type via the communication link based on the delay budget configuration; and identifying a downlink variable delay budget for downlink communications with a first latency type via the communication link based on the delay budget configuration, wherein communications between the UE and the wireless access node may be scheduled based on the uplink variable delay budget or the downlink variable delay budget.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions to: a total delay budget for communications with the first latency type between the UE and the core network node via the communication link is determined based on the delay budget configuration, wherein communications between the UE and the radio access node may be scheduled based on the total delay budget.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the receive delay budget configuration may include operations, features, units, or instructions to: receiving a first IE indicating a total delay budget between the UE and the core network node for communications over the communication link having a first delay type; and receiving a second IE indicating the first variable delay budget.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first variable delay budget may be based on a set of RAN capabilities for the wireless access node.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first variable delay budget may be based on a set of system capabilities for communication between the UE and the core network node.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first variable delay budget may be determined based on configuration information of the UE, the radio access node, or the core network node, wherein 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.

Drawings

Fig. 1 illustrates an example of a wireless communication system supporting a delay budget for low latency communications in accordance with aspects of the present disclosure.

Fig. 2 illustrates an example of a wireless communication system that supports a delay budget for low latency communications in accordance with aspects of the present disclosure.

Fig. 3 illustrates an example of a process flow supporting a delay budget for low latency communications in accordance with aspects of the present disclosure.

Fig. 4 and 5 illustrate block diagrams of devices supporting a delay budget for low latency communications in accordance with aspects of the present disclosure.

Fig. 6 illustrates a block diagram of a communication manager that supports a delay budget for low latency communication in accordance with aspects of the disclosure.

Fig. 7 illustrates a diagram of a system including a device that supports a delay budget for low latency communications in accordance with aspects of the present disclosure.

Fig. 8 and 9 illustrate block diagrams of devices supporting a delay budget for low latency communications in accordance with aspects of the present disclosure.

Fig. 10 illustrates a block diagram of a communication manager that supports a delay budget for low latency communication in accordance with aspects of the disclosure.

Fig. 11 illustrates a diagram of a system including a device that supports a delay budget for low latency communications in accordance with aspects of the present disclosure.

Fig. 12-16 show flowcharts illustrating methods of supporting delay budgets for low latency communications in accordance with aspects of the present disclosure.

Detailed Description

Some wireless communication systems may be used to facilitate communication in a network that relies on relatively tight timing synchronization of network components (sometimes referred to as time-sensitiveNetwork (TSN) system). Such a system may be used to support, for example, factory automation. Some TSN systems specify relatively stringent 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 may be supported in wireless communication systems that use high reliability services, such as ultra-reliable low latency communication (URLLC) services.

In a wireless communication system (e.g., a TSN-carrying communication), qoS requirements for a particular QoS flow may define a target Packet Delay Budget (PDB). The target PDB may set a target delay or total time delay for communication between the UE and the core network of the wireless communication system below which the transmitted data packets may be used. For example, in the case of downlink transmissions, the PDB may include a first delay component incurred between the core network and a wireless access node (e.g., at a base station of a wireless communication system). The PDB may also include a second delay component induced between the base station and the UE. Together, the total PDB having a first delay component and a second delay component may define a target delay from the core network to the UE via the base station. In the case of uplink transmissions, the PDB may similarly define a target delay from the UE to the core network via the base station. If the total delay in transmitting the data packet exceeds the total PDB, the data packet may not be used and may be ignored or discarded.

The base station may schedule uplink and downlink transmissions using a first delay component incurred between the core network and the base station. In some wireless communication systems, a first delay component incurred between the core network and the base station 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 contemplated: wherein the core network and the base station are located in relatively close geographic proximity and thus the first delay component may be significantly smaller than the defined delay (e.g., meaning less than a configured delay of 1 ms). The first delay component may vary based on, for example, the capability of a backhaul link with which the base station communicates with the core network and based on one or more other capabilities (e.g., radio Access Network (RAN) capabilities) such as: subcarrier spacing for communication, support for minislot communication, frame structure configuration, or bandwidth portion for communication via a base station. Thus, if the base station schedules communications with the UE based on the configured delay, the scheduling decision may be overly aggressive or overly conservative, depending on the actual delay.

Accordingly, techniques are discussed herein that provide signaling a PDB configuration to a base station that indicates a determined delay incurred between a core network and the base station, between a UE and the base station, or between the core network and the UE. For example, the core network may send a PDB configuration to the base station indicating a combination of: delay between the core network and the base station, delay between the base station and the UE 115, and total delay between the UE and the core network. Determining an estimate of the actual delay in such communications in the wireless communication system based on the PDB configuration, the base station (or another device) may schedule communications between the UE, the base station, and the core network relatively more accurately.

In some cases, the core network may determine the PDB configuration at an adapter function (e.g., session Management Function (SMF)) supported by the system. For example, when a core network entity receives a request to establish or modify a QoS flow, the core network may determine a PDB configuration. The core network may also send the PDB configuration via an adapter function supported by the system. For example, the core network may send the PDB configuration to the base station via the SMF.

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 portion, etc.). Additionally or alternatively, the core network may determine the PDB configuration based on the capabilities of a backhaul communication link (e.g., an ethernet link) to be used for communication with the base station. Additionally or alternatively, the core network may determine the PDB configuration based on capabilities of the wireless communication system (e.g., delay constraints associated with transmitting communications within the wireless communication system, which may be configured based on, for example, traffic class (e.g., qoS class)).

Aspects of the present disclosure are first described in the context of a wireless communication system and process flow. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to delay budgets for low latency communications.

Fig. 1 illustrates an example of a wireless communication system 100 supporting a delay budget for low latency communications 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 LTE-advanced (LTE-a) network, an LTE-a professional network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low cost and low complexity devices.

Base station 105 may communicate wirelessly with UE 115 via one or more base station antennas. The base stations 105 described herein may include or may be referred to by those skilled in the art as base station transceivers, radio base stations, access points, radio transceivers, node bs, evolved node bs (enbs), next generation node bs or giganode bs (any of which may be referred to as a gNB), home node bs, home evolved node bs, or some other suitable terminology. The wireless communication system 100 may include different types of base stations 105 (e.g., macrocell base stations or small cell base stations). The UEs 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.).

Each base station 105 may be associated with a particular geographic coverage area 110 in which communications with a respective UE 115 are supported. Each base station 105 may provide communication coverage for a respective 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 links 125 shown in the wireless communication system 100 may include: uplink transmissions from UE 115 to base station 105, or downlink transmissions from base station 105 to UE 115. The downlink transmission may also be referred to as a forward link transmission, while the uplink transmission may also be referred to as a reverse link transmission.

The geographic coverage area 110 for a base station 105 may be divided into sectors that 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 macrocell, a small cell, a hotspot, or other type of cell, or various combinations thereof. In some examples, the base station 105 may be mobile 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 comprise, for example, heterogeneous LTE/LTE-a professional or NR networks, wherein different types of base stations 105 provide coverage for respective geographic coverage areas 110.

The term "cell" refers to a logical communication entity for communication (e.g., on a carrier) with the base station 105 and may be associated with an identifier (e.g., physical Cell Identifier (PCID), virtual Cell Identifier (VCID)) for distinguishing between neighboring cells operating via 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 geographic coverage area 110 over which the logical entity operates.

The UEs 115 may be dispersed throughout the wireless communication system 100, and each UE115 may be stationary or mobile. UE115 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 terminology, where "device" may also be referred to as a unit, station, terminal, or client. The UE115 may also be a personal electronic device such as a cellular telephone, a Personal Digital Assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE115 may also refer to a Wireless Local Loop (WLL) station, an internet of things (IoT) device, a internet of things (IoE) device, or an MTC device, etc., which may be implemented in various items such as appliances, vehicles, meters, etc.

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 data communication techniques that allow devices to communicate with each other or base station 105 without human intervention. In some examples, M2M communications or MTC may include communications from devices integrated with sensors or meters to measure or capture information and relay the information to a central server or application that may utilize or present the information to humans interacting with the program or application. Some UEs 115 may be designed to collect information or to implement automated behavior of the machine. 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.

Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception rather than simultaneous transmission and reception). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power saving techniques for UE 115 include: when not engaged in active communications or operating on limited bandwidth (e.g., according to narrowband communications), a "deep sleep" mode of power saving is entered. 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 communications for these functions.

In some cases, the UE 115 may also be capable of communicating directly with other UEs 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more UEs 115 of a group of UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside of the geographic 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 scheduling of resources for D2D communications. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

The base stations 105 may communicate with the core network 130 and with each other. For example, the base station 105 may interface with the core network 130 through 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 the base stations 105) or indirectly (e.g., via the core network 130) over the backhaul link 134 (e.g., via X2, xn, or other interface).

The core network 130 may provide user authentication, access authorization, tracking, internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an Evolved Packet Core (EPC) that may 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 may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC. The user IP packets may be transmitted through the S-GW, which itself may be coupled with the P-GW. The P-GW may provide IP address assignment as well as other functions. The P-GW may be coupled with a network operator IP service. The operator IP services may include access to the internet, intranets, IP Multimedia Subsystem (IMS) or Packet Switched (PS) streaming services.

At least some of the network devices, such as base stations 105, may include subcomponents, such as access network entities, which may be examples of Access Node Controllers (ANCs). Each access network entity may communicate with UE 115 through a plurality of other access network transmission entities, which may be referred to as radio heads, intelligent radio heads, or transmission/reception points (TRPs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or incorporated into a single network device (e.g., base station 105).

The wireless communication system 100 may operate using one or more frequency bands, for example, in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300MHz to 3GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band, because wavelengths range in length from approximately one decimeter to one meter. UHF waves may be blocked or redirected by building and environmental features. However, the waves may be sufficient to penetrate the structure for the macro cell to serve the UE 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers (km)) than transmission of smaller frequencies and longer waves using the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz.

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

The wireless communication system 100 may also operate in the Extremely High Frequency (EHF) region of the spectrum (e.g., from 30GHz to 300 GHz), also referred to as the millimeter-frequency band. In some examples, wireless communication system 100 may support millimeter wave (mmW) communication between UE 115 and base station 105, and EHF antennas of respective devices may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate the use of antenna arrays within UE 115. However, the propagation of EHF transmissions may suffer from even greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary depending on the country or regulatory agency.

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 frequency band (e.g., 5GHz ISM band). When operating in the unlicensed radio frequency spectrum band, wireless devices, such as base station 105 and UE 115, may employ Listen Before Talk (LBT) procedures to ensure that the frequency channels are idle before transmitting data. In some cases, operation in the unlicensed band may be based on a carrier aggregation configuration that incorporates component carriers operating in the licensed band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these. Duplex in the unlicensed spectrum may be based on Frequency Division Duplex (FDD), time Division Duplex (TDD), or a combination of both.

In some examples, base station 105 or UE 115 may be equipped with multiple antennas, which may 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., base station 105) and a receiving device (e.g., UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication may employ multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers (which may be referred to as spatial multiplexing). For example, the transmitting device may transmit multiple signals via different antennas or different combinations of antennas. Also, the receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the plurality of 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 a different data stream. The different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (in which multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (in which multiple spatial layers are transmitted to multiple devices).

Beamforming (which may also be referred to as spatial filtering, directional transmission or directional reception) is a signal processing technique as follows: the techniques may be used at a transmitting device or a receiving device (e.g., base station 105 or UE 115) to form or steer 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 may be achieved by: signals transmitted via antenna elements of the antenna array are combined such that signals propagating in a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. The adjusting of the signal transmitted via the antenna element may include: the transmitting device or the receiving device applies an amplitude and phase offset to the signal carried via each of the antenna elements associated with the device. The adjustment associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to an antenna array of the transmitting device or the receiving device, or relative to some other orientation).

In one example, the base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with the UE 115. For example, the 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, which may include signals transmitted according to different sets of beamforming weights associated with different transmission directions. The transmissions in the different beam directions may be used (e.g., by the base station 105 or a receiving device, such as the UE 115) to identify the beam direction for subsequent transmission or reception by the base station 105. The 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 the UE 115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based at least in part on signals transmitted in different beam directions. For example, the UE115 may receive one or more of the signals transmitted by the base station 105 in different directions, and the UE115 may report an indication to the base station 105 of the signal it received with the highest signal quality or otherwise acceptable signal quality. Although these techniques are described with reference to signals transmitted by the base station 105 in one or more directions, the UE115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or in a single direction (e.g., to transmit data to a receiving device).

When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from the 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 directions of reception by receiving via different antenna sub-arrays, by processing received signals according to different antenna sub-arrays, by receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different sets of receive beamforming weights 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 directions of reception). In some examples, a receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving a data signal). The individual receive beams may be aligned on 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).

In some cases, the antennas of base station 105 or UE 115 may be located within one or more antenna arrays, which may support MIMO operation 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 the base station 105 may be located in different geographic locations. The base station 105 may have an antenna array with multiple rows and columns of antenna ports that the base station 105 may use to support beamforming for communication with the UE 115. Also, UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.

In some cases, the 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, a Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. The Medium Access Control (MAC) layer may perform priority processing 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, a Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between the UE 115 and the base station 105 or core network 130, which supports radio bearers for user plane data. At the Physical (PHY) layer, transport channels may be mapped to physical channels.

In some cases, the UE 115 and the 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 properly received over the 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 under poor radio conditions (e.g., signal and noise conditions). In some cases, a wireless device may support the same slot HARQ feedback, where the device may provide HARQ feedback in a particular slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

May be in a basic time unit (e.g., it may refer to T _s Sample period=1/30,720,000 seconds) to represent a time interval in LTE or NR. The time intervals of the communication resources may be organized according to radio frames each having a duration of 10ms, where a frame period may be denoted as T _f ＝307,200T _s . The radio frames may be identified by a System Frame Number (SFN) ranging from 0 to 1023. Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms. The subframe may be further divided into 2 slots, each slot having a duration of 0.5ms, and each slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). Excluding the cyclic prefix, each symbol period may contain 2048 sampling periods. In some cases, a subframe may be the smallest scheduling unit of the wireless communication system 100 and may be referred to as a Transmission Time Interval (TTI). In other cases, the smallest scheduling unit of the wireless communication system 100 may be shorter than a subframe or may be dynamically selected (e.g., in bursts of shortened TTIs (sTTI) or in selected component carriers using sTTI).

In some wireless communication systems, a time slot may be further divided into a plurality of minislots containing one or more symbols. In some examples, the symbols of the minislots or the minislots may be the smallest scheduling units. Each symbol may vary in duration depending on, for example, subcarrier spacing or frequency band of operation. Further, some wireless communication systems may implement slot aggregation, in which multiple slots or micro-slots are aggregated together and used for communication between the UE 115 and the base station 105.

The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communications over the communication link 125. For example, the carrier of the communication link 125 may include portions of the radio frequency spectrum band that operate in accordance with the physical layer channel for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. The carrier may be associated with a predefined frequency channel, e.g., an evolved universal terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN), and may be placed according to a channel grid for discovery by the UE 115. The carrier may be downlink or uplink (e.g., in FDD mode), or may be configured to carry downlink and uplink communications (e.g., in TDD mode). In some examples, the signal waveform transmitted on the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or discrete fourier transform spread spectrum OFDM (DFT-S-OFDM)).

The organization of the carriers may be different for different radio access technologies (e.g., LTE-A, LTE-a specialty, NR). For example, communications on carriers may be organized according to TTIs or time slots, each of which may include user data and control information or signaling to support decoding of the user data. The carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling to coordinate operation for the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.

The physical channels may be multiplexed on the carrier according to various techniques. For example, the physical control channels and physical data channels may be multiplexed on the downlink carrier using Time Division Multiplexing (TDM), frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques. In some examples, control information transmitted in the physical control channel may be distributed among different control regions in a cascaded manner (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

The carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a plurality of predetermined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) for a carrier of a particular radio access technology. In some examples, each served UE 115 may be configured to operate over part or all of the carrier bandwidth. In other examples, some UEs 115 may be configured for operation using narrowband protocol types associated with predefined portions or ranges within a carrier (e.g., a set of subcarriers or Resource Blocks (RBs)) (e.g., an "in-band" deployment of narrowband protocol types).

In a system employing MCM techniques, a resource element may include one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may 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 for the UE 115 may be. In a MIMO system, wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers may further increase the data rate for communication with UE 115.

A device of the wireless communication system 100 (e.g., the base station 105 or the UE 115) may have a hardware configuration that supports communication over a particular carrier bandwidth or may be configurable to support communication over one of a set of carrier bandwidths. In some examples, wireless communication system 100 may include a base station 105 or UE115 capable of supporting simultaneous communications via carriers associated with more than one different carrier bandwidth.

The wireless communication system 100 may support communication with UEs 115 over multiple cells or carriers (a feature that may be referred to as carrier aggregation or multi-carrier operation). According to a carrier aggregation configuration, the UE115 may be configured with a plurality of downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with both FDD and TDD component carriers.

In some cases, the wireless communication system 100 may utilize an enhanced component carrier (eCC). An eCC may 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, an eCC may 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). An eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g., where more than one operator is allowed to use the spectrum). An eCC characterized by a wide carrier bandwidth may include one or more segments that may be used by UEs 115 that are unable to monitor the entire carrier bandwidth or are otherwise configured to use a limited carrier bandwidth (e.g., to save power).

In some cases, an eCC may utilize a different symbol duration than other component carriers, which may include using a reduced symbol duration as compared to the symbol durations of other component carriers. The shorter symbol duration may be associated with an increased spacing between adjacent subcarriers. Devices utilizing eccs, such as UEs 115 or base stations 105, may transmit wideband signals (e.g., according to frequency channels or carrier bandwidths of 20, 40, 60, 80MHz, etc.) with reduced symbol durations (e.g., 16.67 microseconds). The TTI in an eCC may include one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) may be variable.

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

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

In wireless communication system 100 (e.g., carrying TSN communications), qoS criteria for a particular QoS flow may define a target PDB. The target PDB may set a target delay or total time delay for communication between the UE115 and the core network 130 of the wireless communication system 100 below which the transmitted data packets may be used. In the case of downlink transmissions, the PDB may include a first delay component incurred between the core network 130 (e.g., from a User Plane Function (UPF), SMF, or other adapter function) and the wireless access node (e.g., at the base station 105). The PDB may also include a second delay component induced between the base station 105 and the UE 115. Together, the total PDB defines a target delay from the UPF to the UE115 via the base station 105. In the case of uplink transmissions, the PDB may similarly define a target delay from the UE115 to the UPF or SMF via the base station 105. If the total delay in transmitting the data packet exceeds the total PDB defined by the PDB configuration, the data packet may not be used and may be ignored.

The base station 105 may schedule uplink and downlink communications, for example, with the UE 115 using a first delay component incurred between the core network 130 and the base station 105. In some wireless communication systems, it may be assumed that the first delay component incurred between the core network 130 and the base station 105 is a defined delay (e.g., 1 ms), e.g., based on a delay configuration. However, in the wireless communication system 100 (e.g., is a TSN system), the following deployment is contemplated: where the core network 130 and the base station 105 are located in relatively close geographic proximity, and thus the first delay component may be significantly smaller than the defined delay (e.g., meaning less than the 1ms delay assumed from the delay configuration). The first delay component may also vary based on, for example, the particular 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 portions for communication via the base station 105. Thus, if the base station 105 schedules communications with the UE 115 based on a defined delay, the scheduling decision may be overly aggressive or overly conservative, depending on the actual delay.

Techniques are discussed herein that provide signaling to the base station 105 a PDB configuration that indicates a determined delay incurred between any of the core network 130, the UE 115, and the base station 105. For example, core network 130 may send a PDB configuration to base station 105 indicating a combination of: a first delay component (e.g., a delay between the core network 130 and the base station 105), a second delay component (e.g., a delay between the base station 105 and the UE 115), or a total delay (e.g., between the UE 115 and the core network 130). Based on the indication of the actual delay 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.

Fig. 2 illustrates an example of a wireless communication system 200 that supports a delay budget for low latency communications in accordance with aspects of the present disclosure. In some examples, wireless communication system 200 may implement aspects of wireless communication system 100. The wireless communication system 200 may include a UE 115-a, which may be an example of a UE 115 as described with reference to fig. 1. The wireless communication system 200 may include wireless access nodes at the base station 105-a, which may each be an example of the base station 105 as described with reference to fig. 1. The wireless communication system 200 may include a core network entity 205 (e.g., EPC, next Generation Core (NGC), fifth generation core (5 GC), etc.), which may be an example of an entity of the core network 130 as described with reference to fig. 1. It is to be understood that references to specific Radio Access Technologies (RATs) (e.g., LTE or NR) in the following figures are provided for illustrative purposes, and that different RATs not specifically referenced herein may be used interchangeably with those RATs described herein.

The base station 105-a may communicate with the core network entity 205 using one or more communication links 210 and the base station 105-a may communicate with the UE 115-a using communication links 215. In some cases, the core network entity 205 may include an SMF220, a UPF 225, an Access and Mobility Function (AMF), or a Control Plane Function (CPF). In some cases, SMF220 may provide session management services for UE 115-a. The SMF220 may communicate with different nodes in the wireless communication system 200 to signal different QoS procedures to the nodes, e.g., to be performed for different QoS criteria. In some cases, the UPF 225 may process user information, such as PDCP, RLC, MAC and PHY communications. In some cases, the SMF220 and the UPF 225 may be communicatively coupled in the core network entity 205 via a communication link 218. Although the SMF220 and the UPF 225 are shown in fig. 2 as being communicatively coupled in the core network entity 205, the SMF220 and the UPF 225 may alternatively be located at separate nodes in the wireless communication system 200.

The core network entity 205 may signal a PDB configuration to the base station 105-a for a particular QoS flow, the PDB configuration indicating a delay between devices of the wireless communication system 200. Fig. 2 also shows an example PDB timeline illustrating example delays incurred before the core network entity 205, the base station 105-a, and the UE 115-a. For example, the core network entity 205 may send a PDB configuration (e.g., using the communication link 210-a) to the base station 105-a, the PDB configuration indicating a combination of: a first delay component 250 (e.g., a delay between the core network entity 205 and the base station 105-a), a second delay component 255 (e.g., a delay between the base station 105-a and the UE 115-a), and a total PDB 260. The PDB configuration may include an IE including one or more fields or subfields for indicating one or more of the first delay component 250, the second delay component 255, and the total PDB 260. In some cases, the PDB configuration may indicate that the same delay is for uplink transmissions as for downlink transmissions. Alternatively, the PDB configuration may indicate that the delay is different for uplink and downlink transmissions. Based on the indication of the one or more delays in the PDB configuration, the base station 105-a may schedule communications between the UE 115-a and the base station 105-a. In some cases, scheduling based on the indication of delay may allow for more efficient use of network resources, as well as other benefits, relative to scheduling without an indication of delay.

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

According to some aspects, the base station 105-a may be a node of a RAN and may include multiple units or functional units, such as a Distributed Unit (DU) 265 and a Central Unit (CU) 270. In other cases, one or more of DU 265 and CU 270 may be separate from base station 105-a and may be separate entities associated with the RAN. In some cases, DU 265 and CU 270 may 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 may perform operations similar to those of core network entity 205, and DU 265 may perform operations similar to a node of the RAN (e.g., base station 105-a).

In some examples, the total PDB 260 may also include a delay component between the DU265 and the CU 270. For example, the first delay component 250 may be divided (e.g., uniformly or non-uniformly) between the DU265 and the CU 270 (e.g., between the base station 105-a or RAN and the UE 115-a). The PDB configuration may indicate that the first delay component 250 is divided into a third delay component 275 between the UE 115-a and the DU265 and a fourth delay component 280 between the DU265 and the CU 270. The PDB configuration may indicate at least some of the four components (if not each component) individually (e.g., via separate fields in the signaling of the PDB configuration), or may additionally or alternatively indicate at least some of the four components (e.g., a subset) (if not each component) and the total PDB 260. The signaling may include information about how the total PDB 260 is to be divided between the core network entity 205, the base station 105-a, the DUs 265, the CUs 270, and the UEs 115-a. In some cases, the third delay component 275 and the fourth delay component 280 may be different for uplink and downlink transmissions.

In some cases, the third delay component 275 and the fourth delay component 280 may be balanced (e.g., the same) or may be different. For example, the PDB configuration may indicate a balanced delay budget (e.g., a uniformly split delay budget) between the DUs 265, CUs 270, and UEs 115-a. In such a case, the PDB configuration may indicate that the first delay component 250 (e.g., between the base station 105-a of the RAN and the UE 115-a) is divided into respective delay budgets (e.g., third delay component 275 and fourth delay component 280) for each of CUs 270-DU 265 and DU 265-UE 115-a. In other examples, the delay budget between the RAN and the UE 115-a may be unbalanced (e.g., unevenly split) between the DU265, CU 270, and UE 115-a or may be defined separately from the first delay component 250.

The core network entity 205 may 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 may determine the PDB configuration. Additionally or alternatively, the core network entity 205 may determine the PDB configuration when, for example, 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 may send the PDB configuration via an adapter function supported by the system. For example, core network entity 205 may send the PDB configuration via base station 105-a via SMF 220 using communication link 210-a. Additionally or alternatively, the core network entity 205 may send the PDB configuration via one or more other adapter function 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 may also send the PDB configuration to the UE 115-a, e.g., using one or more AMFs. Further additionally or alternatively, the core network entity 205 may send the PDB configuration to the UPF 225, e.g., via the communication link 218. The UPF 225 may use the PDB configuration, for example, to: uplink transmissions are received from UE 115-a via base station 105-a using communication link 210-b.

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 minislot communication, frame structure configuration, radio frequency spectrum bandwidth, bandwidth portion, etc.). For example, the second delay component 255 may be determined to be relatively short for one subcarrier spacing (e.g., 60 kHz) with a shorter time slot relative to another subcarrier spacing (e.g., 30 kilohertz (kHz)). Additionally or alternatively, the core network entity 205 may determine the PDB configuration based on the capabilities (e.g., bandwidth of a backhaul link between the core network entity 205 and the base station 105-a) of a communication link 210 (e.g., an ethernet link) to be used for communication with the node of the wireless communication system 200. For example, the second delay component 255 may be determined to be relatively longer for another ethernet link of the core network entity 205 having a larger bandwidth (e.g., 10 gigabits per second (Gbps)) than for an ethernet link of the core network entity 205 having a lower bandwidth (e.g., 1 gigabit per second (Gbps)). Additionally or alternatively, the core network entity 205 may determine the PDB configuration based on capabilities of the wireless communication system 200 (e.g., delay constraints associated with transmitting communications within the wireless communication system 200, which may be configured based on, for example, traffic class (e.g., qoS class)). For example, the second delay component 255 may be 0.5ms for the first QoS class and the second delay component 255 may be 0.3ms for the second QoS class. The core network entity 205 may associate different traffic classes with different PDB configurations, e.g., using a look-up table or the like. In some cases, core network entity 205 may additionally or alternatively determine the PDB configuration based on subscription information associated with UE 115 (e.g., a type of UE 115 and a service subscribed to by UE 115).

In some cases, the core network entity 205 may dynamically determine the PDB configuration. For example, the core network entity 205 may recalibrate the PDB configuration based on, for example, varying link conditions. In this case, the core network entity 205 may perform a process over the communication link 210 for determining 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 greater number of backhaul resources are available for the first QoS flow than the second QoS flow, the first delay component 250 may be determined to be relatively longer for the first QoS flow relative to the second QoS flow, because in this case the delay between the base station 105-a and the core network entity 205 may be relatively higher.

In some cases, the core network entity 205 may send the PDB configuration in a message that includes one or more fields (which include parameters for the PDB configuration). For example, core network entity 205 may send the PDB configuration using a QoS profile, one or more QoS rules, one or more uplink packet detection rules, or one or more downlink packet detection rules. The PDB configuration may be indicated in one or more fields or subfields of an IE (e.g., PDB Information Element (IE)). For example, the IE may include one or more fields or subfields that indicate: a parameter representing the first delay component 250, a parameter representing the second delay component 255, or a parameter representing the total PDB 260. The delay budget parameter may be indicated in terms of a length of time (e.g., nanoseconds or milliseconds). Additionally or alternatively, the delay budget parameter of the first delay component 250 or the second delay component 255 may be indicated as a fraction of the total PDB 260.

Fig. 3 illustrates an example of a process flow 300 supporting a delay budget for low latency communications in accordance with aspects of the present disclosure. In some examples, process flow 300 may implement aspects of wireless communication systems 100 and 200. For example, process flow 300 includes UE 115-b, base station 105-b, and core network entity 205-a, which may be examples of corresponding devices described with reference to fig. 1 and 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 UPF 225-a are provided for illustrative purposes only. Different RATs, devices, nodes, functional units, etc. may perform similar functions. The process flow 300 may illustrate an example in which the core network entity 205-a determines and signals to the base station 105-b a PDB configuration indicating a delay budget to be used for communications between the UE 115-b and the core network entity 205-a (e.g., a PDB as described with reference to fig. 2 and 3).

At 305, the SMF 220-a may identify a communication link for traffic associated with the first delay type between the UE 115-b and the 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, 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.

At 315, the SMF220-a may identify one or more capability sets, and at 320, the SMF220-a may determine one or more delay budgets based on the one or more capability sets. For example, SMF220-a may identify a set of RAN capabilities for base station 105-b. In some cases, the RAN capability set may include: subcarrier spacing for communication via base station 105-b, support for micro-slot communication via base station 105-b, frame structure for communication via base station 105-b, bandwidth portion for communication via base station 105-b, or any combination. Additionally or alternatively, the SMF220-a may identify a set of system capabilities for communication between the UE 115-b and the core network entity 205-a. In some cases, the set of system capabilities may include: delay limits for traffic associated with the first delay type, traffic class for traffic associated with the first delay type, or any combination. Additionally or alternatively, the SMF220-a may determine configuration information for 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 procedure for determining capabilities of the wireless communication system. In some cases, the configuration information may include dynamic information from a TSN system associated with UE 115-b or TSN traffic class associated with a QoS flow corresponding to the communication link. In some cases, the configuration information may include subscription information associated with UE 115-b.

At 320, the SMF 220-a may determine a first variable delay budget for communications with a first delay 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 described with reference to fig. 1 and 2). In some cases, determining the first variable delay budget may include: an uplink variable delay budget for uplink communications over a communication link having a first latency type is determined. Determining the first variable delay budget may further include: a downlink variable delay budget for downlink communications over a communication link having a first latency type is determined. In some cases, the first variable delay budget may be determined based on the set of RAN capabilities as may have been identified at 315. In some cases, the first variable delay budget may be determined based on a set of system capabilities as may have been identified at 315. In some cases, the first variable delay budget may be determined based on configuration information as may have been determined at 315. In some cases, the SMF 220-a may receive a request to establish or modify a QoS flow corresponding to the communication link, wherein the first variable delay budget may be determined in response to the request. In some cases, SMF 220-a may receive a request for: a handover of the UE 115-b, a PDU session establishment of the UE 115-b, a PDU session modification of the UE 115-b, or any combination thereof, wherein the first variable delay budget may be determined in response to the request.

At 325, the SMF 220-a may send a delay budget configuration to the base station 105-b and the base station 105-b may receive the delay budget configuration from the SMF 220-a, the delay budget configuration indicating a first variable delay budget and a second variable delay budget for communications between the UE 115-b and the core network entity 205-a via the communication link having the first delay type. In some cases, the second variable delay budget may additionally or alternatively be used for communications between the UE 115-b and the base station 105-b via the communication link having the first delay type. In some cases, the SMF 220-a may send the delay budget configuration based on: qoS associated with UE 115-b, 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. In some cases, the transmit delay budget configuration may include: a first IE is sent indicating a total delay budget between the UE 115-b and the core network entity 205-a for communications over the communication link having the first delay type. In some cases, the transmit delay budget configuration may include: a second IE indicating the first variable delay budget is sent. In some cases, the first variable delay budget may be indicated as a fraction of the second variable delay budget.

At 330, the SMF220-a may send the delay budget configuration to the UPF225-a and the UPF225-a may receive the delay budget configuration from the SMF 220-a. The UPF225 can use the delay budget configuration, for example, to receive uplink transmissions from the UE 115-b using the communication link. At 335, the SMF220-a may determine an overall delay budget between the UE 115-b and the core network entity 205-a for communications with the first delay type via the communication link based on the delay budget configuration.

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

At 345, the base station 105-b may determine an overall delay budget between the UE 115-a and the core network entity 205-a for communications over the communication link having the first delay type based on the delay budget configuration.

At 350, the base station 105-b may schedule communications between the UE115-b and the base station 105-b based on the first variable delay budget and the second variable delay budget. For example, the base station 105-b may send one or more scheduling messages to the UE115-b and the UE115-b may receive one or more scheduling messages from the base station 105-b indicating, for example, time and frequency resources with which to communicate. In some cases, communication between the UE115-b and the base station 105-b may be scheduled based on the total delay budget. In some cases, communication between the UE115-b and the base station 105-b may be scheduled based on an uplink variable delay budget or a downlink variable delay budget as may have been identified at 340.

Fig. 4 illustrates a block diagram 400 of a device 405 supporting a delay budget for low latency communications 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).

The receiver 410 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 delay budgets for low latency communications, etc.). Information may be passed to other components of device 405. Receiver 410 may be an example of aspects of transceiver 720 described with reference to fig. 7. The receiver 410 may utilize a single antenna or a group of antennas.

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

The communications manager 415 or its subcomponents 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 415 or its subcomponents may 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.

The communications manager 415, or sub-components thereof, 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, the communication manager 415 or its subcomponents may be separate and distinct components in accordance with aspects of the present disclosure. In some examples, the communication manager 415 or sub-components thereof may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a web server, another computing device, one or more other components described in the present disclosure, or a combination thereof, in accordance with various aspects of the present disclosure.

Transmitter 420 may transmit signals generated by other components of device 405. In some examples, the transmitter 420 may be co-located with the receiver 410 in a transceiver module. For example, transmitter 420 may be an example of aspects of transceiver 720 described with reference to fig. 7. Transmitter 420 may utilize a single antenna or a group of antennas.

Fig. 5 illustrates a block diagram 500 of a device 505 that supports a delay budget for low latency communications in accordance with aspects of the present disclosure. The device 505 may be an example of aspects of the device 405 or the base station 105 as described herein. The device 505 may include a receiver 510, a communication manager 515, and a transmitter 535. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

The receiver 510 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 delay budgets for low latency communications, etc.). Information may be passed to other components of the device 505. Receiver 510 may be an example of aspects of transceiver 720 described with reference to fig. 7. The receiver 510 may utilize a single antenna or a group of antennas.

The communication manager 515 may be an example of aspects of the communication manager 415 as described herein. The communication manager 515 may include a communication link module 520, a delay budget configuration module 525, and a communication scheduler 530. The communication manager 515 may be an example of aspects of the communication manager 710 described herein.

The communication link module 520 may identify a communication link for traffic associated with the first latency type between the UE and the core network node via the radio access node.

The delay budget configuration module 525 may receive, from the core network node, a delay budget configuration indicating a first variable delay budget for communications between the wireless access node and the core network node via the communication link having a first delay type and a second variable delay budget for communications between the UE and the core network node via the communication link having the first delay type.

The communication scheduler 530 may schedule communications between the UE and the wireless access node based on the first variable delay budget and the second variable delay budget.

Transmitter 535 may transmit 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 fig. 7. Transmitter 535 may utilize a single antenna or a group of antennas.

Fig. 6 illustrates a block diagram 600 of a communication manager 605 supporting a delay budget for low latency communication in accordance with aspects of the disclosure. The communication manager 605 may be an example of aspects of the communication manager 415, the communication manager 515, or the communication manager 710 described herein. The communication manager 605 may include a communication link module 610, a delay budget configuration module 615, a communication scheduler 620, a variable delay budget module 625, and a total delay budget module 630. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

The communication link module 610 may identify a communication link for traffic associated with a first latency type between the UE and the core network node via the 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.

The delay budget configuration module 615 may receive a delay budget configuration from the core network node indicating a first variable delay budget for communications between the wireless access node and the core network node via the communication link having a first delay type and a second variable delay budget for communications between the UE and the core network node via the communication link having the first delay type.

In some examples, the delay budget configuration module 615 may receive a first IE indicating an overall delay budget between the UE and the core network node for communications with the first delay type via the communication link. In some cases, the second variable delay budget is for communications between the UE and the wireless access node via the communication link having the first latency type.

The communication scheduler 620 may schedule communication between the UE and the wireless access node based on the first variable delay budget and the second variable delay budget. The variable delay budget module 625 can identify an uplink variable delay budget for uplink communications with the first delay type via the communication link based on the delay budget configuration.

In some examples, the variable delay budget module 625 may identify a downlink variable delay budget for downlink communications with a first latency type via the communication link based on the delay budget configuration, wherein communications between the UE and the wireless access node are scheduled based on the uplink variable delay budget or the downlink variable delay budget.

In some examples, the variable delay budget module 625 may receive a second IE indicating the 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.

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, wherein the configuration information comprises: 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.

The total delay budget module 630 may determine a total delay budget for communications with the first latency type between the UE and the core network node via the communication link based on the delay budget configuration, wherein communications between the UE and the radio access node are scheduled based on the total delay budget.

Fig. 7 illustrates a diagram of a system 700 that includes a device 705 that supports a delay budget for low latency communications in accordance with aspects of the present disclosure. Device 705 may be an example of device 405, device 505, or base station 105 as described herein or a component comprising device 405, device 505, or base station 105. Device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communications manager 710, a network communications manager 715, a transceiver 720, an antenna 725, a memory 730, a processor 740, and an inter-station communications manager 745. These components may be in electronic communication via one or more buses (e.g., bus 750).

The communication manager 710 may do the following: identifying a communication link for traffic associated with a first latency type between the UE and a core network node via the radio access node; receiving, from a core network node, a delay budget configuration indicating a first variable delay budget for communications between a wireless access node and the core network node via a communication link having a first delay type and a second variable delay budget for communications between a UE and the core network node via the communication link having the first delay type; and scheduling communications between the UE and the wireless access node based on the first variable delay budget and the second variable delay budget.

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

Transceiver 720 may communicate bi-directionally via one or more antennas, wired or wireless links as described herein. For example, transceiver 720 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. Transceiver 720 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, as well as demodulate 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 sending or receiving multiple wireless transmissions simultaneously.

Memory 730 may include Random Access Memory (RAM), read Only Memory (ROM), or a combination thereof. Memory 730 may store computer readable code 735, the computer readable code 735 comprising instructions that when executed by a processor (e.g., processor 740) cause a device to perform various functions described herein. In some cases, memory 730 may contain, among other things, a basic I/O system (BIOS) that may control basic hardware or software operations, such as interactions with peripheral components or devices.

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, discrete hardware components, or any combination thereof). In some cases, 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. Processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 730) to cause device 705 to perform various functions (e.g., functions or tasks that support a latency budget for low latency communications).

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

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

Fig. 8 illustrates a block diagram 800 of a device 805 that supports a delay budget for low latency communications in accordance with aspects of the disclosure. Device 805 may be an example of aspects of a network entity as described herein. 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).

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 delay budgets for low latency communications, etc.). Information may be passed to other components of device 805. Receiver 810 may be an example of aspects of transceiver 1120 described with reference to fig. 11. The receiver 810 may utilize a single antenna or a set of antennas.

The communication manager 815 may perform the following operations: identifying a communication link for traffic associated with a first latency type between the UE and a core network node via the radio access node; determining a first variable delay budget for communications with a first latency type between the radio access node and the core network node via the communication link; and transmitting a delay budget configuration to the wireless access node, the delay budget configuration indicating a first variable delay budget and a second variable delay budget for communications between the UE and the core network node via the communication link having the first delay type. Communication manager 815 may be an example of aspects of communication manager 1110 described herein.

The communications manager 815 or its subcomponents may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communications manager 815 or its subcomponents may be performed by a general purpose processor, DSP, ASIC, 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.

The communications manager 815 or its subcomponents 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, the communication manager 815 or its subcomponents may be separate and distinct components according to various aspects of the present disclosure. In some examples, the communication manager 815 or subcomponents thereof may be combined with one or more other hardware components (including, but not limited to, an I/O component, a transceiver, a web server, another computing device, one or more other components described in the present disclosure, or a combination thereof) in accordance with various aspects of the present disclosure.

The transmitter 820 may transmit 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 fig. 11. Transmitter 820 may utilize a single antenna or a set of antennas.

Fig. 9 illustrates a block diagram 900 of an apparatus 905 that supports a delay budget for low latency communications in accordance with aspects of the disclosure. The device 905 may be an example of aspects of the device 805 or a network entity (such as the UE 115) as 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).

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 delay budgets for low latency communications, etc.). Information may be passed to other components of the device 905. Receiver 910 may be an example of aspects of transceiver 1120 described with reference to fig. 11. The receiver 910 may utilize a single antenna or a group of antennas.

The communication manager 915 may be an example of aspects of the communication manager 815 as described herein. The communication manager 915 may include a communication link manager 920, a variable delay budget manager 925, and a delay 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 the first latency type between the UE and the core network node via the radio access node.

The variable delay budget manager 925 may determine a first variable delay budget for communications with a first delay type between the wireless access node and the core network node via the communication link. The delay budget configuration manager 930 can send a delay budget configuration to the radio access node, the delay budget configuration indicating a 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. The transmitter 935 may transmit signals generated by other components of the device 905. In some examples, transmitter 935 may be co-located with 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 fig. 11. Transmitter 935 may utilize a single antenna or a set of antennas.

Fig. 10 illustrates a block diagram 1000 of a communication manager 1005 supporting a delay budget for low latency communication in accordance with aspects of the disclosure. The communication manager 1005 may be an example of aspects of the communication manager 815, 915, or 1110 described herein. The communication manager 1005 may include a communication link manager 1010, a variable delay budget manager 1015, a delay budget configuration manager 1020, a total delay budget manager 1025, an SMF manager 1030, and a capability manager 1035. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

The communication link manager 1010 may identify a communication link for traffic associated with a first latency type between the UE and the core network node via the 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.

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

In some examples, the variable delay budget manager 1015 may receive requests 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 delay budget is determined in response to the request. In some examples, the variable delay budget manager 1015 may send a second IE indicating the first variable delay budget. In some cases, the second variable delay budget is for communications between the UE and the wireless access node via the communication link having the first latency type. 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.

The delay budget configuration manager 1020 may send a delay budget configuration to the radio access node, the delay budget configuration indicating a 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. In some examples, the delay budget configuration manager 1020 can send the delay budget configuration to the UPF. In some examples, delay budget configuration manager 1020 may send a delay budget configuration based on: 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.

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

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.

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

Fig. 11 illustrates a diagram of a system 1100 that includes a device 1105 supporting a delay budget for low latency communications in accordance with aspects of the disclosure. Device 1105 may be an example of device 805, device 905, or a network entity as described herein or a component comprising device 805, device 905, or a network entity. Device 1105 may include components for bi-directional voice and data communications, including components for sending and receiving communications, including a communications manager 1110, an I/O controller 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1135. These components may be in electronic communication via one or more buses (e.g., bus 1145).

The communication manager 1110 may do the following: identifying a communication link for traffic associated with a first latency type between the UE and a core network node via the radio access node; determining a first variable delay budget for communications with a first latency type between the radio access node and the core network node via the communication link; and transmitting a delay budget configuration to the wireless access node, the delay budget configuration indicating a first variable delay budget and a second variable delay budget for communications between the UE and the core network node via the communication link having the first delay type.

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

The transceiver 1120 may communicate bi-directionally via one or more antennas, wired or wireless links as described herein. For example, transceiver 1120 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1120 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, as well as demodulate packets received from the antenna.

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

Memory 1130 may include RAM and ROM. The memory 1130 may store computer-readable, computer-executable code 1140, the code 1140 comprising instructions that when executed cause a processor to perform the various functions described herein. In some cases, memory 1130 may contain, among other things, a BIOS that may control basic hardware or software operations, such as interactions with peripheral components or devices.

The processor 1135 may include an intelligent hardware device (e.g., a general purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic, 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 that support a latency budget for low latency communications).

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

Fig. 12 shows a flow chart illustrating a method 1200 of supporting a delay budget for low latency communications in accordance with aspects of the present disclosure. The operations of method 1200 may be implemented by a network entity or component thereof as described herein. For example, the operations of method 1200 may be performed by a communication manager as described with reference to fig. 8-11. In some examples, a network entity may execute a set of instructions 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.

At 1205, the network entity may identify a communication link for traffic associated with the first delay type between the UE and the core network node via the radio access node. Operations of 1205 may be performed in accordance with 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 fig. 8-11.

At 1210, the network entity may determine a first variable delay budget for communications with a first delay type between the radio access node and the core network node via the communication link. The operations 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 delay budget manager as described with reference to fig. 8-11.

At 1215, the network entity may send a delay budget configuration indicating a first variable delay budget to the wireless access node. The operations of 1215 may be performed according to the methods described herein. In some examples, aspects of the operation of 1215 may be performed by a delay budget configuration manager as described with reference to fig. 8-11.

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 communications with the first delay type between the UE and the core network node via the communication link. The operations of 1220 may be performed according to the methods described herein. In some examples, aspects of the operation of 1220 may be performed by a delay budget configuration manager as described with reference to fig. 8-11.

Some wireless communication systems may be used to facilitate communications in networks that rely on relatively tight timing synchronization of network components (sometimes referred to as TSN systems). In some wireless communication systems, qoS criteria for a particular QoS flow may define a target PDB. The target PDB may set a target delay or total time delay for communication between the UE and the network entity of the wireless communication system below which the transmitted data packets 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 a target latency from the network entity to the UE via the radio access node.

The wireless access node may schedule uplink and downlink transmissions using a first delay component incurred between the network entity and the wireless access node. In some wireless communication systems, a first delay component incurred between a network entity and a wireless 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 contemplated: wherein the network entity and the radio access node are located in relatively close geographical proximity and thus the first delay component may be significantly smaller than the defined delay (e.g. meaning a delay of less than 1ms is configured). Thus, if the radio access node schedules communications with the UE based on the configured delay, the scheduling decision may be overly aggressive or overly conservative, depending on the actual delay.

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

Fig. 13 shows a flow chart illustrating a method 1300 of supporting a delay budget for low latency communications in accordance with aspects of the present disclosure. The operations of method 1300 may be implemented by a network entity or component thereof as described herein. For example, the operations of method 1300 may be performed by a communication manager as described with reference to fig. 8-11. In some examples, a network entity may execute a set of instructions 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.

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

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. Operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operations of 1310 may be performed by a capability manager as described with reference to fig. 8-11.

At 1315, the network entity may determine a first variable delay budget for communications with a first delay type between the radio access node and the core network node via the communication link. The operations of 1315 may be performed in accordance with the methods described herein. In some examples, aspects of the operation of 1315 may be performed by a variable delay budget manager as described with reference to fig. 8-11.

At 1320, the network entity may send a delay budget configuration indicating the first variable delay budget to the wireless access node. Operations of 1320 may be performed according to the methods described herein. In some examples, aspects of the operation of 1320 may be performed by a delay budget configuration manager as described with reference to fig. 8-11.

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 communications with the first delay type between the UE and the core network node via the communication link. The operations of 1325 may be performed according to the methods described herein. In some examples, aspects of the operation of 1325 may be performed by a delay budget configuration manager as described with reference to fig. 8-11.

Thus, the method 1300 provided herein provides for signaling a delay budget configuration to a wireless access node, the delay budget configuration indicating a first variable delay budget between the wireless 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 wireless access node, wherein the first variable delay budget is determined based on the set of RAN capabilities, the network entity may provide a relatively more accurate determination of the first variable delay budget. Based on the delay budget configuration, the wireless access node can determine an estimate of an actual delay in such communication of the wireless communication system. Thus, based on signaling the determined delay to the radio access node, the radio access node may schedule communications between the UE, the radio access node, and the network entity relatively more accurately.

Fig. 14 shows a flow chart illustrating a method 1400 of supporting a delay budget for low latency communications in accordance with aspects of the present disclosure. The operations of method 1400 may be implemented by a network entity or component thereof as described herein. For example, the operations of method 1400 may be performed by a communication manager as described with reference to fig. 8-11. In some examples, a network entity may execute a set of instructions 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.

At 1405, the network entity may identify a communication link for traffic associated with the first delay type between the UE and the core network node via the radio access node. Operations 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 communications link manager as described with reference to fig. 8-11.

At 1410, the network entity 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. The operations 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 capability manager as described with reference to fig. 8-11.

At 1415, the network entity may determine a first variable delay budget for communications with a first delay type between the radio access node and the core network node via the communication link. The operations 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 fig. 8-11.

At 1420, the network entity may send to the wireless access node a delay budget configuration indicating the first variable delay budget. Operations of 1420 may be performed according to the methods described herein. In some examples, aspects of the operation of 1420 may be performed by a delay budget configuration manager as described with reference to fig. 8-11.

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 communications with the first delay type between the UE and the core network node via the communication link. The operations of 1425 may be performed according to the methods described herein. In some examples, aspects of the operation of 1425 may be performed by a delay budget configuration manager as described with reference to fig. 8-11.

Thus, the method 1400 provided herein provides for signaling a delay budget configuration to a wireless access node, the delay budget configuration indicating a first variable delay budget between the wireless 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 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), the network entity may provide a relatively more accurate determination of the first variable delay budget. Based on the delay budget configuration, the wireless access node can determine an estimate of an actual delay in such communication of the wireless communication system. Thus, based on signaling the determined delay to the radio access node, the radio access node may schedule communications between the UE, the radio access node, and the network entity relatively more accurately.

Fig. 15 shows a flow chart illustrating a method 1500 of supporting a delay budget for low latency communications in accordance with aspects of the present disclosure. The operations of method 1500 may be implemented by a network entity or component thereof as described herein. For example, the operations of method 1500 may be performed by a communication manager as described with reference to fig. 8-11. In some examples, a network entity may execute a set of instructions 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.

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

At 1510, the network entity may determine configuration information for the UE, the radio access node, or the core network node, wherein the first variable delay budget is determined based on the configuration information. The operations of 1510 may be performed according to the methods described herein. In some examples, aspects of the operation of 1510 may be performed by a capability manager as described with reference to fig. 8-11.

At 1515, the network entity may determine a first variable delay budget for communications with a first delay type between the wireless access node and the core network node via the communication link. The operations of 1515 may be performed according to methods described herein. In some examples, aspects of the operation of 1515 may be performed by a variable delay budget manager as described with reference to fig. 8-11.

At 1520, the network entity may send a delay budget configuration indicating the first variable delay budget to the wireless access node. Operations of 1520 may be performed according to the methods described herein. In some examples, aspects of the operation of 1520 may be performed by a delay budget configuration manager as described with reference to fig. 8-11.

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 communications with the first delay type between the UE and the core network node via the communication link. The operations of 1525 may be performed according to the methods described herein. In some examples, aspects of the operation of 1525 may be performed by a delay budget configuration manager as described with reference to fig. 8-11.

Thus, the method 1500 provided herein provides for signaling a delay budget configuration to a wireless access node, the delay budget configuration indicating a first variable delay budget between the wireless access node and a network entity node and a second variable delay budget for communication between a UE and the network entity node. By determining configuration information of the UE, the radio access node, or the core network node, wherein the first variable delay budget is determined based on the configuration information, the network entity may provide a relatively more accurate determination of the first variable delay budget. Based on the delay budget configuration, the wireless access node can determine an estimate of an actual delay in such communication of the wireless communication system. Thus, based on signaling the determined delay to the radio access node, the radio access node may schedule communications between the UE, the radio access node, and the network entity relatively more accurately.

Fig. 16 shows a flow chart illustrating a method 1600 of supporting a delay budget for low latency communications in accordance with aspects of the present disclosure. The operations of method 1600 may be implemented by base station 105 or components thereof as described herein. For example, the operations of method 1600 may be performed by a communication manager as described with reference to fig. 4-7. In some examples, a 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.

At 1605, the base station may identify a communication link for traffic associated with the first latency type between the UE and the core network node via the radio access node. The operations 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 fig. 4-7.

At 1610, the base station may receive, from the core network node, a delay budget configuration indicating a first variable delay budget for communications between the wireless access node and the core network node via the communication link having a first delay type and a second variable delay budget for communications between the UE and the core network node via the communication link having a first delay type. The operations 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 delay budget configuration module as described with reference to fig. 4-7.

At 1615, the base station may schedule communications between the UE and the wireless access node based on the first variable delay budget and the second variable delay budget. The operations of 1615 may be performed according to the methods described herein. In some examples, aspects of the operation of 1615 may be performed by a communications scheduler as described with reference to fig. 4-7.

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

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

The techniques described herein may be used for 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. A CDMA system may implement a radio technology such as CDMA2000, universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. The IS-2000 version may be generally referred to as CDMA2000 1X, etc. IS-856 (TIA-856) IS commonly referred to as CDMA2000 1xEV-DO, high Rate Packet Data (HRPD), or the like. UTRA includes wideband CDMA (W-CDMA) and other variations of CDMA. TDMA systems may implement radio technologies such as global system for mobile communications (GSM).

OFDMA systems may 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, and the like. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). LTE, LTE-a and LTE-a professions are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-a profession, NR and GSM are described in documents from an organization named "3 rd generation partnership project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "3 rd generation partnership project 2" (3 GPP 2). The techniques described herein may be used for the systems and radio technologies mentioned herein as well as other systems and radio technologies. Although aspects of the LTE, LTE-A, LTE-a specialty or NR system may be described for purposes of example, and LTE, LTE-A, LTE-a specialty or NR terminology may be used in much of the description, the techniques described herein may be applicable to areas outside of LTE, LTE-A, LTE-a specialty or NR applications.

A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 with service subscription with the network provider. The small cell may be associated with a lower power base station 105 than the macro cell, and the small cell may operate in the same or a different (e.g., licensed, unlicensed, etc.) frequency band as the macro cell. According to various examples, small cells may include pico cells, femto cells, and micro cells. For example, a pico cell may cover a small geographic area and may allow unrestricted access by UEs 115 with service subscriptions with the network provider. A femto cell may also cover a small geographic area (e.g., a residence) and may provide limited access by UEs 115 having an association with the femto cell (e.g., UEs 115 in a Closed Subscriber Group (CSG), UEs 115 for users in the residence, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, pico eNB, femto eNB, or home eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells and may also support communications using one or more component carriers.

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

The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, 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 may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software for execution by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable medium. 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 may be implemented using software executed by a processor, hardware, firmware, hardwired or a combination of any of these items. Features that implement the functions may also be physically located at various locations including being distributed such that each portion of the functions is implemented at a different physical location.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may 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 comprise RAM, ROM, electrically Erasable Programmable ROM (EEPROM), flash memory, compact Disk (CD) ROM or other optical disk 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 means 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. Further, any connection is properly termed a non-transitory computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless 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 medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

As used herein (including in the claims), an "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of" indicates an inclusive list, such that, for example, a list of at least one of A, B or C means a or B or C or AB or AC or BC or ABC (i.e., a and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, exemplary steps 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 "based at least in part on" is interpreted.

In the drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type may be distinguished by following the reference label by a dash and a second label that is used to distinguish between similar components. If only the first reference number is used in the specification, the description applies to any one of the similar components having the same first reference number, regardless of what the second reference number or other subsequent reference numbers are.

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

The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the widest 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 communications with the first delay type between the wireless access node and the core network node via the communication link; and

transmitting a delay budget configuration to the wireless access node,

wherein transmitting the delay budget configuration comprises: transmitting a first Information Element (IE) and a second IE, the first IE indicating a total delay budget between the UE and the core network node for communications over the communication link having the first delay type, the second IE indicating the first variable delay budget; and wherein the total delay budget and the first variable delay budget are different.

2. The method of claim 1, wherein determining the first variable delay budget comprises:

determining an uplink variable delay budget for uplink communications via the communication link having the first latency type; and

A downlink variable delay budget for downlink communications via the communication link having the first latency type is determined.

3. The method of claim 2, wherein the uplink variable delay budget and the downlink variable delay budget are different.

4. The method of claim 1, wherein the total delay budget is configured based at least in part on the delay budget.

5. The method of claim 1, wherein determining the first variable delay budget comprises:

at a Session Management Function (SMF), determining the first variable delay budget between the radio access node and the core network node for communications of the first delay type via the communication link.

6. The method of claim 5, further comprising:

the delay budget configuration is sent to a User Plane Function (UPF).

7. The method of claim 5, further comprising:

a request to establish or modify a quality of service (QoS) flow corresponding to the communication link is received, wherein the first variable delay budget is determined in response to the request.

8. The method of claim 5, further comprising:

receiving a request for: the method may include switching 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 determined in response to the request.

9. The method of claim 1, further comprising:

a set of Radio Access Network (RAN) capabilities for the radio access node is identified, wherein the first variable delay budget is determined based at least in part on the RAN capabilities set.

10. The method of claim 9, wherein the RAN capability set comprises: a subcarrier spacing for communication via the wireless access node, support for micro-slot communication via the wireless access node, a frame structure for communication via the wireless access node, a bandwidth portion for communication via the wireless access node, or any combination thereof.

11. The method of claim 1, further comprising:

a set of system capabilities for communication between the UE and the core network node is identified, wherein the first variable delay budget is determined based at least in part on the set of system capabilities.

12. The method of claim 11, wherein the set of system capabilities comprises: delay limits for traffic associated with the first delay type, traffic categories for traffic associated with the first delay type, or any combination thereof.

13. The method of claim 1, further comprising:

configuration information of the UE, the radio access node, or the core network node is determined, wherein the first variable delay budget is determined based at least in part on the configuration information.

14. The method of claim 13, wherein the configuration information is based at least in part on a Time Sensitive Network (TSN) procedure for determining capabilities of a wireless communication system.

15. The method of claim 13, wherein the configuration information comprises dynamic information from a Time Sensitive Network (TSN) system associated with the UE or a TSN traffic class associated with a quality of service (QoS) flow corresponding to the communication link.

16. The method of claim 13, wherein the configuration information comprises subscription information associated with the UE.

17. The method of claim 1, further comprising:

The delay budget configuration is transmitted based at least in part on: a 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 of claim 1, wherein the first variable delay budget is indicated as part of a second variable delay budget.

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

20. The method of claim 1, wherein the traffic associated with the first latency type comprises Time Sensitive Network (TSN) traffic.

21. A method for wireless communication at a wireless access node, comprising:

identifying a communication link for traffic associated with a first latency type between a User Equipment (UE) and a core network node via the radio access node;

receiving a delay budget configuration indicating a first variable delay budget from the core network node, the first variable delay budget being used for communications between the radio access node and the core network node via the communication link having the first delay type, wherein receiving the delay budget configuration comprises: receiving a first Information Element (IE) and a second IE, the first IE indicating a total delay budget between the UE and the core network node for communications over the communication link having the first delay type, the second IE indicating the first variable delay budget; wherein the total delay budget and the first variable delay budget are different; and

Communications between the UE and the wireless access node are scheduled based at least in part on the first variable delay budget.

22. The method of claim 21, further comprising:

identifying an uplink variable delay budget for uplink communications having the first latency type via the communication link based at least in part on the delay budget configuration; and

a downlink variable delay budget for downlink communications with the first latency type via the communication link is identified based at least in part on the delay budget configuration, wherein the communications between the UE and the wireless access node are scheduled based at least in part on the uplink variable delay budget or the downlink variable delay budget.

23. The method of claim 22, wherein the uplink variable delay budget and the downlink variable delay budget are different.

24. The method of claim 21, wherein the first variable delay budget is indicated as part of a second variable delay budget.

25. The method of claim 21, wherein the communication link corresponds to a quality of service (QoS) flow associated with the first latency type.

26. The method of claim 21, wherein the traffic associated with the first latency type comprises Time Sensitive Network (TSN) traffic.

27. An apparatus for wireless communication at a core network node, comprising:

the processor may be configured to perform the steps of,

a memory coupled to the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

transmitting a delay budget configuration to the wireless access node,

28. The apparatus of claim 27, wherein the instructions to determine the first variable delay budget are executable by the processor to cause the apparatus to:

29. The apparatus of claim 28, wherein the uplink variable delay budget and the downlink variable delay budget are different.

30. The apparatus of claim 27, wherein the total delay budget is configured based at least in part on the delay budget.

31. The apparatus of claim 27, wherein the instructions to determine the first variable delay budget are executable by the processor to cause the apparatus to:

32. The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

the delay budget configuration is sent to a User Plane Function (UPF).

33. The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

34. The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

35. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to:

36. The apparatus of claim 35, wherein the RAN capability set comprises: a subcarrier spacing for communication via the wireless access node, support for micro-slot communication via the wireless access node, a frame structure for communication via the wireless access node, a bandwidth portion for communication via the wireless access node, or any combination thereof.

37. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to:

38. The apparatus of claim 37, wherein the set of system capabilities comprises: delay limits for traffic associated with the first delay type, traffic class for traffic associated with the first delay type, or any combination thereof.

39. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to:

40. The apparatus of claim 39, wherein the configuration information is based at least in part on a Time Sensitive Network (TSN) procedure for determining capabilities of a wireless communication system.

41. The apparatus of claim 39, wherein the configuration information comprises dynamic information from a Time Sensitive Network (TSN) system associated with the UE or a TSN traffic class associated with a quality of service (QoS) flow corresponding to the communication link.

42. The apparatus of claim 39, wherein the configuration information comprises subscription information associated with the UE.

43. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to:

44. The apparatus of claim 27, wherein the first variable delay budget is indicated as part of a second variable delay budget.

45. The apparatus of claim 27, wherein the communication link corresponds to a quality of service (QoS) flow associated with the first latency type.

46. The apparatus of claim 27, wherein the traffic associated with the first latency type comprises Time Sensitive Network (TSN) traffic.

47. An apparatus for wireless communication at a wireless access node, comprising:

the processor may be configured to perform the steps of,

a memory coupled to the processor; and

receiving a delay budget configuration indicating a first variable delay budget from the core network node, wherein the first variable delay budget is used for communications between the wireless access node and the core network node via the communication link having the first delay type, wherein receiving the delay budget configuration comprises: receiving a first Information Element (IE) and a second IE, the first IE indicating a total delay budget between the UE and the core network node for communications over the communication link having the first delay type, the second IE indicating the first variable delay budget; and wherein the total delay budget and the first variable delay budget are different; and

48. The apparatus of claim 47, wherein the instructions are further executable by the processor to cause the apparatus to:

49. The apparatus of claim 48, wherein the uplink variable delay budget and the downlink variable delay budget are different.

50. The apparatus of claim 47, wherein the first variable delay budget is indicated as part of a second variable delay budget.

51. The apparatus of claim 47, wherein the communication link corresponds to a quality of service (QoS) flow associated with the first latency type.

52. The apparatus of claim 47, wherein the traffic associated with the first latency type comprises Time Sensitive Network (TSN) traffic.

53. An apparatus for wireless communication at a core network node, comprising:

means for 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;

means for transmitting a delay budget configuration to the wireless access node, wherein transmitting the delay budget configuration comprises: transmitting a first Information Element (IE) and a second IE, the first IE indicating a total delay budget between the UE and the core network node for communications over the communication link having the first delay type, the second IE indicating the first variable delay budget; and wherein the total delay budget and the first variable delay budget are different.

54. An apparatus for wireless communication at a wireless access node, comprising:

means for identifying a communication link for traffic associated with a first latency type between a User Equipment (UE) and a core network node via the radio access node;

means for receiving a delay budget configuration indicating a first variable delay budget from the core network node, wherein the first variable delay budget is used for communications between the wireless access node and the core network node via the communication link having the first delay type, wherein receiving the delay budget configuration comprises: receiving a first Information Element (IE) and a second IE, the first IE indicating a total delay budget between the UE and the core network node for communications over the communication link having the first delay type, the second IE indicating the first variable delay budget; and wherein the total delay budget and the first variable delay budget are different; and

means for scheduling communications between the UE and the wireless access node based at least in part on the first variable delay budget.

55. A non-transitory computer-readable medium storing code for wireless communication at a core network node, the code comprising instructions executable by a processor to:

transmitting a delay budget configuration to the wireless access node, wherein transmitting the delay budget configuration comprises: transmitting a first Information Element (IE) and a second IE, the first IE indicating a total delay budget between the UE and the core network node for communications over the communication link having the first delay type, the second IE indicating the first variable delay budget; and wherein the total delay budget and the first variable delay budget are different.

56. A non-transitory computer-readable medium storing code for wireless communication at a wireless access node, the code comprising instructions executable by a processor to: