Patent Description:
Reference is made to XP009517533 of Gabriel Brown entitled "Ultra-Reliable Low-Latency <NUM> for Industrial Automation", Heavy reading White Paper (https://www. com/media/documents/files/read-the-white-paper-by-heavy-reading. pdf), <NUM>-<NUM>-<NUM>, Qualcomm Inc. Reference is also made to XP015118602 of Y. Jiang Huawei Technologies L. Geng China Mobile entitled "Deterministic Networking Flow Information Model; draft-zha-detnet-flow-info-model-<NUM>. txt", Internet Engineering Task Force, IETF; StandardWorkingDraft, Internet Society (ISOC) <NUM>, rue des Falaises CH- <NUM> Geneva, Switzerland.

The 3GPP document entitled "TSN - QoS framework" by Nokia provides a solutions for the 3GPP support of a deterministic and time-sensitive communication service to support integration into TSN networks.

In some aspects, a method of wireless communication, performed by a network controller of a wireless communication system, may include receiving a time-sensitive network (TSN) traffic configuration that indicates a duration of a gate open state for a TSN traffic flow and a periodicity with which the gate open state occurs; configuring one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry the TSN traffic flow, wherein the one or more QoS parameters are configured based at least in part on one or more TSN capability parameters associated with the network controller and at least one of the duration of the gate open state or the periodicity; and transmitting the one or more QoS parameters to a base station of the wireless communication system.

In some aspects, a network controller of a wireless communication system may include memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to receive a time-sensitive network (TSN) traffic configuration that indicates a duration of a gate open state for a TSN traffic flow and a periodicity with which the gate open state occurs; configure one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry the TSN traffic flow, wherein the one or more QoS parameters are configured based at least in part on one or more TSN capability parameters associated with the network controller and at least one of the duration of the gate open state or the periodicity; and transmit the one or more QoS parameters to a base station of the wireless communication system.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a network controller of a wireless communication system, may cause the one or more processors to receive a time-sensitive network (TSN) traffic configuration that indicates a duration of a gate open state for a TSN traffic flow and a periodicity with which the gate open state occurs; configure one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry the TSN traffic flow, wherein the one or more QoS parameters are configured based at least in part on one or more TSN capability parameters associated with the network controller and at least one of the duration of the gate open state or the periodicity; and transmit the one or more QoS parameters to a base station of the wireless communication system.

In some aspects, an apparatus of a wireless communication system may include means for receiving a time-sensitive network (TSN) traffic configuration that indicates a duration of a gate open state for a TSN traffic flow and a periodicity with which the gate open state occurs; means for configuring one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry the TSN traffic flow, wherein the one or more QoS parameters are configured based at least in part on one or more TSN capability parameters associated with the apparatus and at least one of the duration of the gate open state or the periodicity; and means for transmitting the one or more QoS parameters to a base station of the wireless communication system.

In some aspects, a method of wireless communication, performed by a base station of a wireless communication system, may include receiving an indication of one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry a time-sensitive network (TSN) traffic flow, wherein the one or more QoS parameters are based at least in part on one or more TSN capability parameters and at least one of a duration of a gate open state for the TSN traffic flow or a periodicity with which the gate open state occurs; and processing the TSN traffic flow based at least in part on the one or more QoS parameters.

In some aspects, a base station of a wireless communication system may include memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to receive an indication of one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry a time-sensitive network (TSN) traffic flow, wherein the one or more QoS parameters are based at least in part on one or more TSN capability parameters and at least one of a duration of a gate open state for the TSN traffic flow or a periodicity with which the gate open state occurs; and process the TSN traffic flow based at least in part on the one or more QoS parameters.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a base station of a wireless communication system, may cause the one or more processors to receive an indication of one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry a time-sensitive network (TSN) traffic flow, wherein the one or more QoS parameters are based at least in part on one or more TSN capability parameters and at least one of a duration of a gate open state for the TSN traffic flow or a periodicity with which the gate open state occurs; and process the TSN traffic flow based at least in part on the one or more QoS parameters.

In some aspects, an apparatus of a wireless communication system may include means for receiving an indication of one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry a time-sensitive network (TSN) traffic flow, wherein the one or more QoS parameters are based at least in part on one or more TSN capability parameters and at least one of a duration of a gate open state for the TSN traffic flow or a periodicity with which the gate open state occurs; and means for processing the TSN traffic flow based at least in part on the one or more QoS parameters.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network controller, wireless communication device, and processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, controller/processor <NUM> of network controller <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with quality of service mapping for time-sensitive network traffic in a wireless communication system, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, controller/processor <NUM> of network controller <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM>, <NUM>, and <NUM> may store data and program codes for base station <NUM>, UE <NUM>, and network controller <NUM>, respectively.

In some aspects, network controller <NUM> may include means for receiving a time-sensitive network (TSN) traffic configuration that indicates a duration of a gate open state for a TSN traffic flow and a periodicity with which the gate open state occurs; means for configuring one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry the TSN traffic flow, wherein the one or more QoS parameters are configured based at least in part on one or more TSN capability parameters associated with network controller <NUM> and at least one of the duration of the gate open state or the periodicity; means for transmitting the one or more QoS parameters to a base station of the wireless communication system; and/or the like. In some aspects, one or more TSN capability parameters associated with a network controller <NUM> may be associated with the wireless communication system. As a result, the one or more TSN capability parameters may depend on one or more capabilities of the wireless communication system. For example, different wireless communications systems using the network controller <NUM> may have different TSN capability parameters depending on various parameters, such as supported subcarrier spacings, bandwidth, quality of backhauls, and/or the like. In some aspects, such means may include one or more components of network controller <NUM> described in connection with <FIG>.

In some aspects, base station <NUM> may include means for receiving an indication of one or more quality of service (QoS) parameters, associated with the wireless communication system, for a QoS flow that is to carry a time-sensitive network (TSN) traffic flow, wherein the one or more QoS parameters are based at least in part on one or more TSN capability parameters and at least one of a duration of a gate open state for the TSN traffic flow or a periodicity with which the gate open state occurs; means for processing the TSN traffic flow based at least in part on the one or more QoS parameters; and/or the like. In some aspects, such means may include one or more components of base station <NUM> described in connection with <FIG>.

The ANC <NUM> may be a central unit (CU) of the distributed RAN <NUM>. The backhaul interface to the next generation core network (NG-CN) <NUM> may terminate at the ANC <NUM>. The backhaul interface to neighboring next generation access nodes (NG-ANs) may terminate at the ANC <NUM>. The ANC <NUM> may include one or more TRPs <NUM> (which may also be referred to as BSs, NR BSs, Node Bs, <NUM> NBs, APs, gNB, or some other term). As described above, a TRP <NUM> may be used interchangeably with "cell. " In some aspects, multiple TRPs <NUM> may be included in a single base station <NUM>. Additionally, or alternatively, different TRPs <NUM> may be included in different base stations <NUM>. In some aspects, network controller <NUM> may include ANC <NUM>.

A TRP <NUM> may be a distributed unit (DU). A TRP <NUM> may be connected to a single ANC <NUM> or multiple ANCs <NUM>. For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, the TRP <NUM> may be connected to more than one ANC <NUM>. A TRP <NUM> may include one or more antenna ports. The TRPs <NUM> may be configured to individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission) serve traffic to a UE <NUM>.

The architecture may be defined to support fronthauling solutions across different deployment types. The NG-AN <NUM> may share a common fronthaul for LTE and NR. For example, cooperation may be preset within a TRP <NUM> and/or across TRPs <NUM> via the ANC <NUM>. In some aspects, no inter-TRP interface may be needed/present.

In some aspects, a dynamic configuration of split logical functions may be present within the architecture of RAN <NUM>. The packet data convergence protocol (PDCP), radio link control (RLC), media access control (MAC) protocol, and/or the like may be adaptably placed at the ANC <NUM> or TRP <NUM>. According to various aspects, a base station <NUM> may include a central unit (CU) (e.g., ANC <NUM>) and/or one or more distributed units (e.g., one or more TRPs <NUM>).

The C-CU <NUM> may be centrally deployed. Functionality of the C-CU <NUM> may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity. In some aspects, the C-RU <NUM> may host core network functions locally. In some aspects, the C-RU <NUM> may have distributed deployment. A distributed unit (DU) <NUM> may host one or more TRPs <NUM>. The DU <NUM> may be located at edges of the network with radio frequency (RF) functionality. In some aspects, network controller <NUM> may include C-CU <NUM>.

<FIG> is a diagram illustrating an example <NUM> of a network architecture for transmission of time-sensitive network traffic via a wireless communication system, in accordance with various aspects of the present disclosure.

Time-sensitive network (TSN) traffic is a traffic type associated with low latency and high reliability, and is defined by a set of Ethernet communication standards (e.g., as part of the Institute of Electrical and Electronics Engineers (IEEE) <NUM>). The standards define mechanisms for synchronized, time-sensitive transmission of data over wired Ethernet networks, including a variety of parameters that can be configured to meet various latency requirements, reliability requirements, jitter requirements, and/or the like. In some scenarios, transmission of TSN traffic via a wireless communication system, such as a New Radio (e.g., <NUM>) wireless communication system, may require strict latency and/or reliability requirements in a wireless communication scenario, such as provided by ultra-reliability low latency communication (URLLC) services, for industrial Internet of Things (IIoT) traffic, factory automation traffic, and/or like use cases. Some techniques and apparatuses described herein assist with translating TSN traffic parameters to traffic parameters capable of being used in a wireless communication system, such as a <NUM> system, thereby permitting TSN traffic to be carried via a wireless communication system while satisfying stringent communication requirements.

As shown in <FIG>, TSN endpoints <NUM> may communication with one another via a wireless communication system <NUM> and/or a TSN bridge <NUM>. In some aspects, the wireless communication system <NUM> may act as a TSN bridge <NUM>. The wireless communication system <NUM> may include a network controller <NUM>, which may receive TSN configuration information from a centralized network configuration (CNC) device in a wired TSN. In some aspects, a TSN endpoint <NUM> may include a UE <NUM>.

As an example, a first TSN endpoint <NUM> may include a device configured as a transmitter (e.g., referred to as a "talker" in TSN), and a second TSN endpoint <NUM> may include a device configured as a receiver (e.g., referred to as a "listener" in TSN). In some aspects, the talker may include a programmable logic controller (PLC) and/or the like. Additionally, or alternatively, the listener may include a sensor, an actuator, and/or the like (e.g., a robotic arm, a manufacturing device, an industrial robot, and/or the like). The talker may transmit TSN traffic to the listener using a TSN protocol (e.g., according to one or more TSN communication standards). The TSN traffic may be assigned to a traffic class (e.g., one of eight Ethernet traffic classes corresponding to different priorities).

A wired TSN bridge <NUM> may process the TSN traffic according to the traffic class and a TSN traffic configuration, as described in more detail below in connection with <FIG>. The TSN traffic configuration may be received from a CNC device in a wired TSN. Because the TSN traffic configuration is associated with a wired communication standard (e.g., Ethernet), the parameters used to process TSN traffic, handle admission control (e.g., with certain guarantees or requirements, such as a maximum latency and/or the like), perform traffic scheduling (e.g., scheduling of data transmission), and/or the like may be specific to a wired communication standard, and those parameters may be different from those used in the wireless communication system <NUM>. When a wireless communication system <NUM> processes and/or carries TSN traffic, various wireless protocols, wireless communication standards, and/or the like may be employed. Some techniques and apparatuses described herein assist with translating a TSN traffic configuration, intended for use in a wired communication system, to parameters that are capable of being used in a wireless communication system <NUM> (e.g., a flow bit rate, a maximum data burst volume, and/or the like). In this way, requirements associated with TSN traffic may be used for admission control, scheduling, and/or the like in a wireless communication system <NUM>.

In some aspects, the network controller <NUM> may perform some techniques described herein to assist with such translation of TSN traffic configuration to parameters capable of being used in a wireless communication system <NUM>, such as a <NUM> system. The network controller <NUM> may include, for example, one or more devices and/or functions of a core network of the wireless communication system <NUM>. For example, the network controller <NUM> may include an access and mobility function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), and/or the like. Additionally, or alternatively, the network controller <NUM> may be a separate entity in a core network (e.g., an adapter function connecting a wired TSN network to wireless communication system <NUM>) or may be part of an SMF, a PCF, an AMF, a UPF, and/or the like. As described in more detail below, the network controller <NUM> may transmit one or more parameters, associated with handling of TSN traffic, to a base station <NUM> (e.g., which may act as a TSN bridge <NUM>). The base station <NUM> may apply those parameter(s) to perform operations associated with handling TSN traffic, such as admission control, scheduling, and/or the like.

For example, in some aspects, the network architecture may not include a wired TSN bridge <NUM>.

<FIG> is a diagram illustrating an example <NUM> of a time-sensitive network traffic configuration, in accordance with various aspects of the present disclosure.

As shown by reference number <NUM>, a TSN traffic configuration may indicate parameters associated with one or more TSN traffic classes (e.g., one of eight possible Ethernet classes), where different TSN traffic classes may be handled with different priorities. As shown by reference number <NUM>, the TSN traffic configuration may indicate a duration of time that a traffic class is associated with a gate open state, shown as being indicated in a gate control list. A TSN bridge <NUM> (or a device acting as a TSN bridge <NUM>, such as base station <NUM> and/or the like) may schedule and/or transmit TSN traffic of that traffic class during a time period in which that traffic class is associated with the gate open state. In some aspects, the TSN traffic configuration may indicate durations of a gate open state for multiple TSN traffic classes. Additionally, or alternatively, as shown by reference number <NUM>, the TSN traffic configuration may indicate a periodicity with which such gate open states occur (e.g., shown as a cycle time).

In example <NUM>, the TSN traffic configuration indicates a gate open state with a duration of <NUM> microseconds (us) for traffic class <NUM>, followed by a gate open state with a duration of <NUM> microseconds for traffic class <NUM>, followed by a gate open state with a duration of <NUM> microseconds for all other traffic classes (e.g., traffic classes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>). The gate open state for traffic class <NUM> is indicated by 'o' in CCCCCoCC (or, e.g., <NUM> or <NUM>), where each bit corresponds to a traffic class, and a value of the bit (e.g., <NUM> or <NUM>) indicates whether the gate is open or closed for that traffic class, and a corresponding duration of <NUM> microseconds. Similarly, the gate open state for traffic class <NUM> is indicated by 'o' in CCCCCCoC with a corresponding duration of <NUM> microseconds, and the gate open state for the remaining traffic classes is indicated by "o" entries of oooooCCo with a corresponding duration of <NUM> microseconds. The periodicity of the gate open states is <NUM> microseconds, indicating that a specific state is triggered every <NUM> microseconds, which is also equal to the sum of the durations of each gate open state (e.g., <NUM> + <NUM> + <NUM> = <NUM>).

As shown by reference number <NUM>, using this example TSN traffic configuration, a first gating period begins with a first time period where TSN traffic class <NUM> is associated with a gate open state, which lasts for <NUM> microseconds. During the first time period, a TSN bridge <NUM> and/or a base station <NUM> may transmit only TSN traffic of traffic class <NUM>, and may not transmit any other TSN traffic classes (e.g., since the gate control list indicates that all other traffic classes, other than traffic class <NUM>, are associated with a gate closed state during the first time period). Accordingly, the TSN bridge <NUM> and/or the base station <NUM> may schedule only TSN traffic of traffic class <NUM> for transmission in the first time period.

As shown by reference number <NUM>, after the first time period expires (e.g., after <NUM> microseconds), a second time period occurs where TSN traffic class <NUM> is associated with a gate open state, which lasts for <NUM> microseconds. During the second time period, a TSN bridge <NUM> and/or a base station <NUM> may transmit only TSN traffic of traffic class <NUM>, and may not transmit any other TSN traffic classes (e.g., since the gate control list indicates that all other traffic classes, other than traffic class <NUM>, are associated with a gate closed state during the second time period). Accordingly, the TSN bridge <NUM> and/or the base station <NUM> may schedule only TSN traffic of traffic class <NUM> for transmission in the second time period.

As shown by reference number <NUM>, after the second time period expires (e.g., after <NUM> microseconds), a third time period occurs where TSN traffic classes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are associated with a gate open state, which lasts for <NUM> microseconds. During the third time period, a TSN bridge <NUM> and/or a base station <NUM> may transmit only TSN traffic having one of these traffic classes, and may not transmit any other TSN traffic classes (e.g., class <NUM> or class <NUM>). Accordingly, the TSN bridge <NUM> and/or the base station <NUM> may schedule only TSN traffic of traffic classes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> for transmission in the third time period.

As shown by reference number <NUM>, after the third time period expires, a second gating period begins. The second gating period includes time periods corresponding to the first time period, the second time period, and the third time period described above. Thus, a first gate open period for traffic class <NUM>, a second gate open period for traffic class <NUM>, and a third gate open period for the remaining traffic classes each re-occur with a periodicity indicated by the TSN traffic configuration (e.g., <NUM> microseconds in example <NUM>).

For example, the number of time periods in a gating period, the duration of the time periods, the traffic classes associated with a gate open period during the time periods, the periodicity, and/or the like may differ from what was described above in connection with <FIG>.

<FIG> is a diagram illustrating an example <NUM> of quality of service mapping for time-sensitive network traffic in a wireless communication system, in accordance with various aspects of the present disclosure.

As shown by reference number <NUM>, a network controller <NUM>, associated with a wireless communication system <NUM> (e.g., a <NUM> or New Radio wireless communication system) may receive a TSN traffic configuration (also referred to as an IEEE <NUM>. 1Qbv configuration and/or the like). In some aspects, the network controller <NUM> may receive the TSN traffic configuration from a device associated with a TSN, such as a TSN endpoint <NUM>, a TSN bridge <NUM>, a CNC, a device that receives user input to configure the TSN, and/or the like. Additionally, or alternatively, the network controller <NUM> may generate the TSN traffic configuration based at least in part on one or more requirements associated with the TSN, TSN endpoints <NUM>, TSN traffic to be carried via the TSN, and/or the like. In some aspects, the network controller <NUM> may determine and/or receive the TSN traffic configuration in association with establishing a TSN traffic flow for communication between TSN endpoints <NUM>. In some aspects, the network controller <NUM> may be collocated with another network device. For example, network controller <NUM> may be collocated with base station <NUM> or with a TSN configuration entity, such as a CNC. In this case, the network controller <NUM> and the base station <NUM> may communicate with one another by providing information to one another.

As described above in connection with <FIG>, the TSN traffic configuration may indicate a duration of a gate open state (shown as "G", and which may also be referred to as a gate state octet) for a TSN traffic flow (e.g., having a specific traffic class) and a periodicity with which the gate open state occurs (shown as "T", and which may also be referred to as a time interval). In some aspects, the TSN traffic configuration may indicate multiple durations corresponding to multiple gate open states for different combinations of TSN traffic flows. For example, the TSN traffic configuration may indicate a gate open state with a duration of <NUM> microseconds for traffic class <NUM>, followed by a gate open state with a duration of <NUM> microseconds for traffic class <NUM>, followed by a gate open state with a duration of <NUM> microseconds for all other traffic classes (e.g., traffic classes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>), as described above in connection with <FIG>.

As shown by reference number <NUM>, the network controller <NUM> may determine one or more TSN capability parameters associated with the network controller <NUM>. A TSN capability parameter may indicate a capability, associated with the network controller <NUM> and/or a wireless communication system <NUM> (e.g., one or more devices included in the wireless communication system <NUM>) in which the network controller <NUM> operates, relating to transmission of TSN traffic. In some aspects, a TSN capability parameter may depend on one or more capabilities of the wireless communication system. For example, different wireless communications systems using the network controller <NUM> may have different TSN capability parameters depending on various parameters, such as supported subcarrier spacings, bandwidth, quality of backhauls, and/or the like.

In some aspects, a TSN capability parameter may relate to a delay associated with transmission of TSN traffic. For example, a TSN capability parameter may relate to a delay associated with transmission of TSN traffic via a wireless communication system <NUM> in which the network controller <NUM> operates, such as a minimum delay for a frame (e.g., a packet, an Ethernet frame, an encapsulated Ethernet frame, and/or the like) to traverse the wireless communication system <NUM> (e.g., between TSN endpoints <NUM>), a maximum delay for a frame to traverse the wireless communication system <NUM>, and/or the like.

In some aspects, a TSN capability parameter may include a frame-dependent TSN capability parameter, which may depend on a size of a frame (e.g., a frame size, a packet size, and/or the like). For example, a frame-dependent TSN capability parameter may include a maximum dependent delay parameter (e.g., a maximum delay for a frame to traverse the wireless communication system <NUM> depending on a size of the frame, which may also be referred to as a dependentDelayMax parameter), a minimum dependent delay parameter (e.g., a minimum delay for a frame to traverse the wireless communication system <NUM> depending on a size of the frame, which may also be referred to as a dependentDelayMin parameter), a port transmit rate parameter (e.g., a rate at which one or more ports of one or more devices of the wireless communication system <NUM> are capable of transmitting frames, depending on size of the frames, which may also be referred to as a portTransmitRate parameter), and/or the like.

Additionally, or alternatively, a TSN capability parameter may include a frame-independent TSN capability parameter, which may not depend on a size of a frame. For example, a frame-independent TSN capability parameter may include a maximum independent delay parameter (e.g., a maximum delay for a frame to traverse the wireless communication system <NUM> independent of a size of the frame, which may also be referred to as an independentDelayMax parameter), a minimum independent delay parameter (e.g., a minimum delay for a frame to traverse the wireless communication system <NUM> independent of a size of the frame, which may also be referred to as an independentDelayMin parameter), a transmission propagation delay parameter (e.g., a propagation delay associated with transmitting a frame, such as via an over-the-air transmission, independent of a size of the frame, which may also be referred to as a txPropagationDelay parameter), and/or the like.

As shown by reference number <NUM>, the network controller <NUM> may configure one or more quality of service (QoS) parameters, associated with the wireless communication system <NUM>, for a QoS flow that is to carry the TSN traffic flow (e.g., that is to carry TSN traffic having a specific traffic class). The network controller <NUM> may configure a QoS parameter for a QoS flow based at least in part on a TSN capability parameter (e.g., described above), a duration of a gate open state associated with a TSN traffic flow to be carried via the QoS flow, and/or the periodicity indicated by the TSN traffic configuration. As shown, a QoS parameter may include a maximum data burst volume (MDBV) parameter, a guaranteed flow bit rate (GFBR) parameter, a maximum flow bit rate (MFBR) parameter, a <NUM> QoS indicator (5QI) parameter, and/or the like. In some aspects, parameters determined by the network controller <NUM> may assist with configuration and/or transmission of a TSN traffic flow, and thus may be referred to as time-sensitive communication assistance information (TSCAI). Examples of TSCAI can be found with reference to 3GPP Technical Specification (TS) <NUM> (such as in section <NUM>. <NUM> and <NUM>. <NUM> of version <NUM>.

As shown by reference number <NUM>, in some aspects, the network controller <NUM> may configure a QoS parameter for a QoS flow for carrying a TSN traffic flow based at least in part on a frame-dependent TSN capability parameter (shown as "c") and at least one of a duration of a gate open state for the TSN traffic flow (shown as "G") or the periodicity (shown as "T"). For example, the MDBV parameter may be configured based at least in part on the frame-dependent TSN capability parameter and the duration (e.g., as MDBV = c × G). Additionally, or alternatively, the GFBR parameter may be configured based at least in part on the frame-dependent TSN capability parameter, the duration, and the periodicity (e.g., as GFBR = c × G/T). Additionally, or alternatively, the MFBR parameter may be configured based at least in part on the frame-dependent TSN capability parameter, the duration, and the periodicity (e.g., as MFBR = c × G/T). In some aspects, "c" may be set equal to a value of <NUM>/dependentDelayMax, a value of <NUM>/dependentDelayMin, a value of portTransmitRate, and/or the like. In some aspects, the MDBV parameter, the GFBR parameter, and/or the MFBR parameter may be based at least in part on TSCAI. The TSCAI may be determined based at least in part on a duration of the gate open state, one or more TSN capability parameters, and/or a periodicity, in a similar manner as described above.

Additionally, or alternatively, the 5QI parameter may be configured based at least in part on the frame-dependent TSN capability parameter, the duration, and/or the periodicity. For example, the 5QI parameter may be configured as a function of the frame-dependent TSN capability parameter and at least one of the duration or the periodicity (e.g., shown as 5QI = f(c, G and/or T)). In some aspects, the 5QI parameter may be determined by calculating one or more other QoS parameters (e.g., MDBV, GFBR, MFBR, and/or the like) and determining a standardized or pre-specified 5QI parameter that has corresponding QoS parameter(s) that are closest to the calculated QoS parameter(s) (e.g., closest in value, closest to and greater than in value, closest to and less than in value, and/or the like). In this way, the calculated QoS parameters may be mapped to a corresponding 5QI parameter that permits the QoS parameters to be satisfied. In some aspects, the 5QI parameter may be determined based at least in part on TSCAI.

As shown by reference number <NUM>, in some aspects, the network controller <NUM> may configure a QoS parameter for a QoS flow for carrying a TSN traffic flow based at least in part on a frame-dependent TSN capability parameter (shown as "c"), a frame-independent TSN capability parameter (shown as "k"), and at least one of a duration of a gate open state for the TSN traffic flow (shown as "G") or the periodicity (shown as "T"). For example, the MDBV parameter may be configured based at least in part on the frame-dependent TSN capability parameter, the frame-independent TSN capability parameter, and the duration (e.g., as MDBV = c × (G-k)). Additionally, or alternatively, the GFBR parameter may be configured based at least in part on the frame-dependent TSN capability parameter, the frame-independent TSN capability parameter, the duration, and the periodicity (e.g., as GFBR = c × (G-k)/T). Additionally, or alternatively, the MFBR parameter may be configured based at least in part on the frame-dependent TSN capability parameter, the frame-independent TSN capability parameter, the duration, and the periodicity (e.g., as MFBR = c × (G-k)/T). In some aspects, "k" may be set equal to a value of independentDelayMax, a value of independentDelayMin, a value of txPropagationDelay, and/or the like. In some aspects, the MDBV parameter, the GFBR parameter, and/or the MFBR parameter may be determined based at least in part on TSCAI. The TSCAI may be determined based at least in part on a duration of the gate open state, one or more TSN capability parameters, and/or a periodicity, in a similar manner as described above.

Additionally, or alternatively, the 5QI parameter may be configured based at least in part on the frame-dependent TSN capability parameter, the frame-independent TSN capability parameter, the duration, and/or the periodicity. For example, the 5QI parameter may be configured as function of the frame-dependent TSN capability parameter, the frame-independent TSN capability parameter, and at least one of the duration or the periodicity (e.g., shown as 5QI = f(c, k, G and/or T)). In some aspects, the 5QI parameter may be determined by calculating one or more other QoS parameters (e.g., MDBV, GFBR, MFBR, and/or the like) and determining a standardized or pre-specified 5QI parameter that has corresponding QoS parameter(s) that are closest to the calculated QoS parameter(s) (e.g., closest in value, closest to and greater than in value, closest to and less than in value, and/or the like). In this way, the calculated QoS parameters may be mapped to a corresponding 5QI parameter that permits the QoS parameters to be satisfied. In some aspects, the 5QI parameter may be determined based at least in part on TSCAI.

As shown by reference number <NUM>, in some aspects, the network controller <NUM> may configure a QoS parameter for a QoS flow for carrying a TSN traffic flow based at least in part on a frame-dependent TSN capability parameter (shown as "c"), a frame-independent TSN capability parameter (shown as "k") and at least one of a duration of a gate open state for the TSN traffic flow (shown as "G") or the periodicity (shown as "T").

As shown by reference number <NUM>, the network controller <NUM> may transmit the one or more QoS parameters for a QoS traffic flow to a base station <NUM> associated with the wireless communication system <NUM>, such as a base station <NUM> with a coverage area that includes one or more TSN endpoints <NUM> communicating using the TSN traffic. In some aspects, the network controller <NUM> may transmit the one or more QoS parameters to the base station <NUM> prior to the establishment of a QoS flow to carry the TSN traffic. Additionally, or alternatively, the base station <NUM> and/or the network controller <NUM> may use the QoS parameters to perform admission control for the TSN traffic. In some aspects, the network controller <NUM> may be collocated with another network device. For example, network controller <NUM> may be collocated with base station <NUM> or with a TSN configuration entity, such as a CNC. In this case, the network controller <NUM> and the base station <NUM> may communicate with one another by providing information to one another.

For example, the base station <NUM> and/or the network controller <NUM> may determine whether the QoS parameters are capable of being satisfied (e.g., based at least in part on a traffic load, a number of UEs <NUM> and/or TSN endpoints <NUM>, network conditions, and/or the like associated with the base station <NUM>, the wireless communication system <NUM>, and/or the like). If the QoS parameters are capable of being satisfied, then the base station <NUM> and/or the network controller <NUM> may establish a QoS flow (and/or a radio bearer) to carry the TSN traffic according to the QoS parameter(s). If the QoS parameters are not capable of being satisfied, then the base station <NUM> and/or the network controller <NUM> may not establish a QoS flow (and/or a radio bearer) to carry the TSN traffic according to the QoS parameter(s). In this way, quality of service for TSN traffic may be guaranteed when that TSN traffic is carried over a wireless communication system <NUM>, such as a <NUM> network and/or the like.

As shown by reference number <NUM>, the base station <NUM> may process the TSN traffic flow based at least in part on the one or more QoS parameters. For example, the base station <NUM> may use the one or more QoS parameters to perform admission control in association with the TSN traffic flow, as described above. Additionally, or alternatively, the base station <NUM> may schedule transmission of TSN traffic, of the TSN traffic flow, via the QoS flow based at least in part on the one or more QoS parameters. For example, the base station <NUM> may schedule (and/or transmit) TSN traffic such that the QoS parameters are satisfied. In this way, quality of service for TSN traffic may be guaranteed when that TSN traffic is carried over a wireless communication system <NUM>, such as a <NUM> network and/or the like. Furthermore, aspects of the wireless communication system <NUM> may be improved, such as reliability of the wireless communication system <NUM> (e.g., by permitting latency and/or reliability requirements to be guaranteed), flexibility of the wireless communication system <NUM> (e.g., by permitting TSN traffic to be carried), efficiency of the wireless communication system <NUM> (e.g., due to standardized translation of a TSN traffic configuration to QoS parameters), and/or the like.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a network controller, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a network controller (e.g., network controller <NUM> and/or the like) performs operations associated with quality of service mapping for time-sensitive network traffic in a wireless communication system.

As shown in <FIG>, in some aspects, process <NUM> may include receiving a time-sensitive network (TSN) traffic configuration that indicates a duration of a gate open state for a TSN traffic flow and a periodicity with which the gate open state occurs (block <NUM>). For example, the network controller (e.g., using controller/processor <NUM>, memory <NUM>, communication unit <NUM>, and/or the like) may receive a TSN traffic configuration that indicates a duration of a gate open state for a TSN traffic flow and a periodicity with which the gate open state occurs, as described above.

As shown in <FIG>, in some aspects, process <NUM> may include configuring one or more quality of service (QoS) parameters, associated with a wireless communication system, for a QoS flow that is to carry the TSN traffic flow, wherein the one or more QoS parameters are configured based at least in part on one or more TSN capability parameters associated with the network controller and at least one of the duration of the gate open state or the periodicity (block <NUM>). For example, the network controller (e.g., using controller/processor <NUM>, memory <NUM>, communication unit <NUM>, and/or the like) may configure one or more QoS parameters, associated with a wireless communication system associated with the network controller, for a QoS flow that is to carry the TSN traffic flow, as described above. In some aspects, the one or more QoS parameters are configured based at least in part on one or more TSN capability parameters associated with the network controller and at least one of the duration of the gate open state or the periodicity.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting the one or more QoS parameters to a base station of the wireless communication system (block <NUM>). For example, the network controller (e.g., using controller/processor <NUM>, memory <NUM>, communication unit <NUM>, and/or the like) may transmit the one or more QoS parameters to a base station of the wireless communication system, as described above.

In a first aspect, the one or more QoS parameters are used for admission control or scheduling of the QoS flow.

In a second aspect, alone or in combination with the first aspect, the one or more QoS parameters include at least one of: a maximum data burst volume (MDBV) parameter, a guaranteed flow bit rate (GFBR) parameter, a maximum flow bit rate (MFBR) parameter, a <NUM> QoS indicator (5QI) parameter, or a combination thereof.

In a third aspect, alone or in combination with one or more of the first and second aspects, the MDBV parameter is configured based at least in part on at least one of the duration of the gate open state or the one or more TSN capability parameters.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the MDBV parameter is determined based at least in part on time-sensitive communication assistance information (TSCAI), and wherein the TSCAI is determined based at least in part on at least one of the duration of the gate open state or the one or more TSN capability parameters.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, at least one of the GFBR parameter or the MFBR parameter is configured based at least in part on the duration of the gate open state, the periodicity, and the one or more TSN capability parameters.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the 5QI parameter is configured based at least in part on the duration of the gate open state, the periodicity, and the one or more TSN capability parameters.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the one or more TSN capability parameters include at least one of: a maximum dependent delay parameter, a minimum dependent delay parameter, a port transmit rate parameter, a maximum independent delay parameter, a minimum independent delay parameter, a transmission propagation delay parameter, or a combination thereof.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the one or more TSN capability parameters include a first TSN capability parameter relating to a dependent delay and a second TSN capability parameter relating to an independent delay.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the first TSN capability parameter includes at least one of: a maximum dependent delay parameter, a minimum dependent delay parameter, a port transmit rate parameter, or a combination thereof.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the second TSN capability parameter includes at least one of: a maximum independent delay parameter, a minimum independent delay parameter, a transmission propagation delay parameter, or a combination thereof.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a base station (e.g., base station <NUM> and/or the like) performs operations associated with quality of service mapping for time-sensitive network traffic in a wireless communication system.

As shown in <FIG>, in some aspects, process <NUM> may include receiving an indication of one or more quality of service (QoS) parameters, associated with a wireless communication system, for a QoS flow that is to carry a time-sensitive network (TSN) traffic flow, wherein the one or more QoS parameters are based at least in part on one or more TSN capability parameters and at least one of a duration of a gate open state for the TSN traffic flow or a periodicity with which the gate open state occurs (block <NUM>). For example, the base station (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive an indication of one or more QoS parameters, associated with a wireless communication system of the base station, for a QoS flow that is to carry a TSN traffic flow, as described above. In some aspects, the one or more QoS parameters are based at least in part on one or more TSN capability parameters and at least one of a duration of a gate open state for the TSN traffic flow or a periodicity with which the gate open state occurs.

As shown in <FIG>, in some aspects, process <NUM> may include processing the TSN traffic flow based at least in part on the one or more QoS parameters (block <NUM>). For example, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may process the TSN traffic flow based at least in part on the one or more QoS parameters, as described above.

In a first aspect, processing the TSN traffic flow comprises at least one of: performing admission control in association with the TSN traffic flow, or scheduling transmission of TSN traffic, of the TSN traffic flow, via the QoS flow.

In a third aspect, alone or in combination with one or more of the first and second aspects, the MDBV parameter is based at least in part on at least one of the duration of the gate open state or the one or more TSN capability parameters.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the MDBV parameter is based at least in part on time-sensitive communication assistance information (TSCAI), and wherein the TSCAI is based at least in part on at least one of the duration of the gate open state or the one or more TSN capability parameters.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, at least one of the GFBR parameter or the MFBR parameter is based at least in part on the duration of the gate open state, the periodicity, and the one or more TSN capability parameters.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the 5QI parameter is based at least in part on the duration of the gate open state, the periodicity, and the one or more TSN capability parameters.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the one or more TSN capability parameters include a first TSN capability parameter relating to dependent delay and a second TSN capability parameter relating to independent delay.

Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of possible aspects. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible aspects includes each dependent claim in combination with every other claim in the claim set.

Claim 1:
A method of wireless communication performed by a network controller of a wireless communication system, comprising:
receiving (<NUM>) a time-sensitive network, TSN, traffic configuration that indicates a duration of a gate open state for a TSN traffic flow and a periodicity with which the gate open state occurs;
configuring (<NUM>) one or more quality of service, QoS, parameters, associated with the wireless communication system, for a QoS flow that is to carry the TSN traffic flow, wherein the one or more QoS parameters are configured based at least in part on one or more TSN capability parameters associated with the network controller and at least one of the duration of the gate open state or the periodicity; wherein the one or more QoS parameters include at least one of:
a maximum data burst volume, MDBV, parameter,
a guaranteed flow bit rate, GFBR, parameter,
a maximum flow bit rate, MFBR, parameter,
a <NUM> QoS indicator, 5QI, parameter, or
a combination thereof; and
transmitting (<NUM>) the one or more QoS parameters to a base station of the wireless communication system.