MÉTODO E APARELHO DE SUPORTE DE RELATÓRIO DE TEMPO DE CHEGADA DE RAJADA (BAT)

Abstract

Various aspects of the present disclosure relate to a method and apparatus of supporting burst arrival time (BAT) reporting. An exemplary UE includes: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, a request of BAT of a QoS flow, from a network side; determine a BAT of the QoS flow, wherein the BAT of the QoS flow is a time value relative to a boundary of a system frame number (SFN); and transmit the determined BAT of the QoS flow to the network side.

Description

1 / 47 METHOD AND APPARATUS FOR SUPPORTING BURST ARRIVAL TIME (BAT) REPORTING TECHNICAL FIELD

[001] This disclosure relates to wireless communications and, more specifically, to the burst time-of-arrival (BAT) reporting support technique. BACKGROUND

[002] A wireless communication system may include one or more network communication devices, such as base stations, which may support wireless communications to one or more user communication devices, which may also be known as user equipment (UE) or other suitable terminology. The wireless communication system may support wireless communications with one or more user communication devices by utilizing wireless communication system features (e.g., timing features (e.g., symbols, slots, subframes, frames, or the like) or frequency features (e.g., subcarriers, carriers, or the like).In addition, the wireless communications system can support wireless communications in various radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies besides 5G (e.g., sixth generation (6G)). SUMMARY

[003] An article before an element is unrestricted and understood as referring to at least one of those elements or to one or more of those elements. The terms at least one, one or more, and at least one of one or more may be interchangeable. As used in this document, including in the claims, or as used in a list of items (for example, a list of items preceded by a phrase such as by). Petition 870250084078, dated 09 / 18 / 2025, page 10 / 69 2 / 47 less than one of or one or more of or one or both of) indicates an inclusive list, so 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 in this document, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an example step described as based on condition A could be based on either condition A or condition B without departing from the scope of this disclosure. In other words, as used in this document, the expression "based on" should be interpreted in the same way as the expression "based at least in part on." Furthermore, as used in this document, including in the claims, a "set" may include one or more elements.

[004] Some implementations of the methods and devices described in this document may include a UE for wireless communication, wherein the UE includes: at least one memory; and at least one processor coupled to at least one memory and configured to make the UE: receive a BAT request from a QoS stream, from a network side; determine a BAT from the QoS stream, wherein the QoS stream BAT is a time value relative to a limit of a system frame number (SFN); and transmit the determined BAT from the QoS stream to the network side.

[005] In some implementations of the methods and devices described in this document, at least one processor is configured to perform the UE: receive the QoS stream BAT request from a source RAN node; determine the QoS stream BAT used in the source RAN node; and transmit the determined QoS stream BAT to the source RAN node.

[006] In some implementations of the methods and devices described in this document, at least one processor is configured to perform the UE: receive the BAT request from the QoS stream, from a master node (MN); determine the BAT of Petition 870250084078, dated 09 / 18 / 2025, page 11 / 69 3 / 47 QoS stream used in the MN; and transmit the determined BAT of the QoS stream to the MN.

[007] In some implementations of the methods and devices described in this document, the determined BAT of the QoS stream is transmitted to the network side in an EU assistance information message.

[008] In some implementations of the methods and devices described in this document, at least one processor is configured to make the UE: receive the QoS stream BAT request from an MN; determine the QoS stream BAT according to a data radio carrier (DRB) type to which the QoS stream belongs; and transmit the determined QoS stream BAT to the MN.

[009] In some cases of the methods and devices described in this document, at least one processor is configured to make the UE: receive information indicating an updated DRB type to which the QoS flow belongs; and determine the BAT of the QoS flow according to the updated DRB type to which the QoS flow belongs.

[010] In some cases of the methods and devices described in this document, at least one processor is configured to perform the UE: determine the QoS flow BAT using the SEN time of a primary cell (PCell) if the DRB is served only by the master cell group (MCG); or determine the QoS flow BAT using the SEN time of the secondary primary cell (PSCell) if the DRB is served by secondary cell groups (SCG) only; or determine a first QoS flow BAT using the SEN time of the PCell and a second QoS flow BAT using the SEN time of the PSCell if the DRB is served by both the MCG and the SCG; or determine the QoS flow BAT using the SEN time of a special cell (SPCell) of a configured primary path if the DRB is served by the split uplink carrier. Petition 870250084078, dated 09 / 18 / 2025, page 12 / 69 4 / 47 [Oil]In some implementations of the methods and devices described in this document, at least one processor is configured to perform the UE: receive the QoS stream BAT request from a MN; determine the QoS stream BAT according to a cell indicated by the MN for BAT calculation; and transmit the determined QoS stream BAT to the MN.

[012] In some cases of the methods and devices described in this document, at least one processor is configured to perform the UE: determine the QoS flow BAT using the SEN time of a PCell if only the PCell or MCG is indicated; or determine the QoS flow BAT using the SEN time of a PSCell if only the PSCell or SCG is indicated; or determine a first QoS flow BAT using the SEN time of the PCell and a second QoS flow BAT using the SEN time of the PSCell if both PCell and PSCell are indicated or both MCG and SCG are indicated.

[013] In some cases of the methods and devices described in this document, at least one processor is configured to perform the UE: transmit the first BAT and the second BAT to the MN with information indicating which BAT is for the MCG and which BAT is for the SCG, in the case of both the first BAT and the second BAT being determined.

[014] In some implementations of the methods and devices described in this document, at least one processor is configured to make the UE: receive the QoS stream BAT request in the MCG configuration, from an MN; determine the QoS stream BAT using the SEN time of a PCell and transmit the determined QoS stream BAT to the MN.

[015] In some implementations of the methods and devices described in this document, at least one processor is configured to perform the UE: receive the BAT request of the QoS stream in the SCG configuration, from an MN; determine the BAT of the QoS stream using the SEN time of a Petition 870250084078, dated 09 / 18 / 2025, page 13 / 69 5 / 47 PSCell; and transmit the determined BAT of the QoS stream to the MN.

[016] In some implementations of the methods and devices described in this document, at least one processor is configured to make the UE: receive the QoS stream BAT request from an MN or an SN, where the QoS stream BAT is configured to be reported by a signaling radio carrier (SRB) 3; determine the QoS stream BAT using the SEN time of an SCG PSCell; and transmit the determined QoS stream BATs to the SN.

[017] In some implementations of the methods and devices described in this document, at least one processor is configured to make the UE: receive the QoS stream BAT request from an MN or an SN, where the QoS stream BAT is configured by an SRB3; determine the QoS stream BAT using the SEN time of an SCG PSCell; and transmit the determined QoS stream BATs to the SN by the SRB3.

[018] In some implementations of the methods and devices described in this document, the limit of a SEN is a limit of a reference SEN, or a limit of a SEN in which the BAT is transmitted.

[019] In some implementations of the methods and devices described in this document, the reference SEN and the reference SEN boundary are configured or are default, and / or the SEN boundary at which the BAT is transmitted is a starting point of an initial SEN subframe.

[020] Some implementations of the methods and devices described in this document may also include a processor for wireless communication, wherein the processor includes: at least one controller coupled to at least one memory and configured to make the processor: receive a BAT request from a QoS stream, from one side of the network; determine a BAT from the QoS stream, wherein the BAT of the QoS stream is a time value. Petition 870250084078, dated 09 / 18 / 2025, page 14 / 69 6 / 47 relating to an SFN limit; and transmit the determined BAT of the QoS flow to the network side.

[021] Some implementations of the methods and devices described in this document may also include a method performed by a UE, in which the method includes: receiving a BAT request from a QoS flow, from one network side; determining a BAT from the QoS flow, where the QoS flow BAT is a time value relative to an SFN limit; and transmitting the determined BAT from the QoS flow to the network side.

[022] Some implementations of the methods and devices described in this document may also include a RAN node for wireless communication, wherein the RAN node includes: at least one memory; and at least one processor coupled to at least one memory and configured to make the RAN node: receive a first BAT of a QoS stream used in a first RAN node; and determine a second BAT of the QoS stream used in a second RAN node according to the first BAT and SFN time difference between the first RAN node and the second RAN node, wherein each BAT of the QoS stream is a time value relative to an SFN boundary, and the RAN node is the first RAN node or the second RAN node.

[023] In some implementations of the methods and devices described in this document, at least one processor is configured to perform the UE: the boundary of an SFN is a boundary of a reference SFN, or a boundary of an SFN on which the BAT is transmitted.

[024] In some implementations of the methods and devices described in this document, the RAN node is the second node, and the processor is configured to make the RAN node: receive the first BAT of the QoS stream from the first RAN node; and receive an SFN offset from the first RAN node, where the SFN time difference between the first RAN node and the second RAN node is a difference between Petition 870250084078, dated 09 / 18 / 2025, page 15 / 69 / 47, the SFN displacement of the first RAN node and an SFN displacement of the second RAN node.

[025] In some cases of the methods and devices described in this document, if the first BAT of the QoS stream is a time value relative to the reference SFN boundary, the processor is configured to make the RAN node: receive the reference SFN to calculate the first BAT of the QoS stream from the first RAN node; and determine the second BAT of the QoS stream according to the first BAT, the SFN time difference between the first RAN node and the second RAN node and the reference SFN to calculate the first BAT.

[026] In some cases of the methods and devices described in this document, if the first BAT of the QoS stream is a time value relative to the SFN boundary in which the BAT is transmitted, the processor is configured to make the RAN node: receive the SFN in which the BAT is transmitted to calculate the first BAT of the QoS stream of the first RAN node; and determine the second BAT of the QoS stream according to the first BAT, the SFN time difference between the first RAN node and the second RAN node and the SFN in which the BAT is transmitted to calculate the first BAT.

[027] In some implementations of the methods and devices described in this document, the first RAN node is a source RAN node or MN, and the second RAN node is a target RAN node or SN.

[028] In some cases of the methods and devices described in this document, if the first RAN node is a source RAN node and the second RAN node is a target RAN node, the first BAT of the QoS flow is received in a transfer request message; or if the first RAN node is an MN and the second RAN node is an SN, the first BAT of the QoS flow is received in an SNG-RAN node addition request message or an SNG-RAN node modification request message. Petition 870250084078, dated 09 / 18 / 2025, page 16 / 69 2 / 47

[029] In some implementations of the methods and devices described in this document, the RAN node is the first node, and the processor is configured to make the RAN node: receive the first BAT of the QoS stream from a UE; and receive a SEN offset from the second RAN node, wherein the SEN time difference between the first RAN node and the second RAN node is a difference between a SEN offset from the first RAN node and the SEN offset from the second RAN node.

[030] In some cases of the methods and devices described in this document, if the second BAT of the QoS stream is a time value relative to the reference SEN boundary, the processor is configured to make the RAN node: receive the reference SEN to calculate the second BAT of the QoS stream of the second RAN node; and determine the second BAT of the QoS stream according to the first BAT, the time difference of the SEN between the first RAN node and the second RAN node and the reference SEN to calculate the second BAT.

[031] In some cases of the methods and devices described in this document, the first RAN node is a source RAN node or MN, and the second RAN node is a target RAN node or SN.

[032] In some cases of the methods and devices described in this document, the processor is configured to make the RAN node: transmit the second BAT of the QoS stream to the second RAN node in a transfer request message if the first RAN node is a source RAN node and the second RAN node is a target RAN node; or transmit the second BAT of the QoS stream to the second RAN node in an S-NG-RAN node addition request message or an S-NG-RAN node modification request message if the first RAN node is an MN and the second RAN node is an SN.

[033] In some implementations of the methods and devices described in this document, the reference SEN and the SFN limit Petition 870250084078, dated 09 / 18 / 2025, page 17 / 69 Reference 9 / 47s are configured or are set by default, and / or the SFN boundary at which the BAT is transmitted is a starting point of an initial SFN subframe. BRIEF DESCRIPTION OF THE DRAWINGS

[034] Figure 1 illustrates an example of a wireless communication system in accordance with aspects of the present disclosure.

[035] Figure 2 illustrates an example of another wireless communication system in accordance with aspects of the present disclosure.

[036] Figure 3 illustrates some exemplary BATs according to aspects of the present disclosure.

[037] Figure 4 is a flowchart that illustrates a method for supporting BAT reporting in accordance with aspects of this disclosure.

[038] Figure 5 is a flowchart that illustrates another method of supporting BAT reporting in accordance with aspects of this disclosure.

[039] Figure 6 illustrates an example of a UE in accordance with aspects of this disclosure.

[040] Figure 7 illustrates an example of a processor in accordance with aspects of the present disclosure.

[041] Figure 8 illustrates an example of a network equipment (NE) according to aspects of the present disclosure.

[042] Figure 9 illustrates a flowchart of a method performed by a UE in accordance with aspects of this disclosure.

[043] Figure 10 illustrates a flowchart of a method performed by a NE in accordance with aspects of this disclosure. DETAILED DESCRIPTION

[044] Extended reality (XR), including augmented reality (AR) and virtual reality (VR), as well as cloud gaming (CG), presents a promising new category of connected devices, applications, and services. Awareness of XR traffic characteristics (or XR traffic awareness) in RAN will assist in scheduling and optimizing resources. Petition 870250084078, dated 09 / 18 / 2025, page 18 / 69 10 / 47 gNB radio. For awareness of uplink XR traffic (UL), the RAN2#122 meeting agreed that the UE should report BAT and UL jitter per QoS flow to the network side, e.g., to a gNB. According to some implementations of this disclosure, for BAT, the UE may report a relative time, e.g., a time relative to a SEN boundary to the network side. However, there may be misunderstanding of BAT due to temporal desynchronization between cells, e.g., between the source cell and the target cell in the case of transfer or between PSCell and PCell in the case of NRDC.

[045] For example, in the case of transfer, the UE calculates the BAT according to the time (or time) in the source cell and reports the BAT to the source gNB before the transfer. The source gNB forwards the reported BAT to the target gNB. However, the reported BAT cannot be used directly by the target gNB if the target cell is not synchronized with the source cell.

[046] In the case of dual NR connectivity (DC), the MCG and SCG may not be synchronized in time. For example, PCell and PSCell are out of time. The UE can calculate the BAT according to the time of the PCell in the MCG and report it to the network. Since the PSCell in the SN is not synchronized in time with the PCell in the MN, the reported BAT cannot be used directly by the SN.

[047] At least to solve the above technical problem, the implementations of this disclosure provide a technical solution for BAT reporting support, for example, a method and device for BAT reporting support.

[048] For example, according to some implementations of this disclosure, the UE calculates (determines, or similar) the BAT of a QoS stream in the source cell and reports it to the source RAN node, for example, the source gNB. The source gNB transmits the BAT used in the source cell, the SEN offset in the source cell and, optionally, a reference SFN (a Petition 870250084078, dated 09 / 18 / 2025, page 19 / 69 11 / 47 The configured or default SFN (SFN) in the source cell for the target RAN node, for example, the target gNB in ​​a transfer request message or similar. The target gNB calculates the BAT used in the target cell according to the received BAT used in the source cell, the SFN time difference (or SFN offset difference, or SFN offset difference, or similar) between the source cell and the target cell (which can be determined by the SFN offset in the source cell and the SFN offset in the target cell), and the optional reference SFN of the source cell.

[049] According to some other implementations of this disclosure, the UE calculates the BAT of a QoS stream in the source cell and reports it to the source gNB. The source gNB calculates the BAT used in the target gNB according to the SFN time difference between the source cell and the target cell, and sends the calculated BAT used in the target gNB to the target gNB.

[050] According to some other implementations of this disclosure, the UE will be responsible for determining (calculating, or similar) the BAT for the corresponding node(s) in the case of NR-DC. For example, according to some implementations of this disclosure, the UE calculates the BAT using the SFN time of PCell or PSCell according to the type of DRB carrier to which the QoS flow belongs. According to some other implementations of this disclosure, the UE calculates the BAT using the SFN time of the cell indicated by the network side. According to some other implementations of this disclosure, the UE calculates the BAT using the SFN time of the cell whose Radio Resource Control (RRC) configuration is configured.

[051] This disclosure solves the technical problem of BAT report support, preventing misunderstanding of BAT between cells, especially in transfer and NR-DC cases. Consequently, this disclosure will support awareness of XR traffic in RAN and assist in scheduling. Petition 870250084078, dated 09 / 18 / 2025, page 20 / 69 12 / 47 and in optimizing radio resources on the network side.

[052] Aspects of the present disclosure are described in the context of a wireless communication system.

[053] Figure 1 illustrates an example of a wireless communication system 100, according to aspects of the present disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104 and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G Advanced (5G-A) network or a 5G ultra-wideband (5G-UWB) network. In other implementations, the 100 wireless communication system may be a combination of a 4G network and a 5G network, or other suitable radio access technology, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20 standards.The 100 wireless communication system can support radio access technologies beyond 5G, for example, 6G. Furthermore, the 100 wireless communication system can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA), etc.

[054] One or more NEs 102 may be dispersed across a geographic region to form the wireless communication system 100. One or more of the NE 102 described in this document may be, include, or be referred to as a network node, a base station, a network element, a network function, a network entity, a RAN, a RAN node, a B Node, an eB Node (eNB), a next-generation B Node (gNB), or other suitable terminology. An NE 102 and an UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 Petition 870250084078, dated 09 / 18 / 2025, page 21 / 69 13 / 47 and a UE 104 can perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[055] A NE 102 can provide a geographic coverage area for which the NE 102 can support services for one or more UEs 104 within the geographic coverage area. For example, a NE 102 and a UE 104 can support wireless communication of service-related signals (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different NE 102s.

[056] One or more UEs 104 may be dispersed across a geographic region of the wireless communication system 100. A UE 104 may include or be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine-like communication (MTC) device, among other examples.

[057] A UE 104 can support wireless communication directly with other UE 104s via a communication link. For example, a UE 104 can support wireless communication directly with another UE 104 via a communication link device. Petition 870250084078, dated 09 / 18 / 2025, page 22 / 69 14 / 47 to device (D2D). In some implementations, such as vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or cellular V2X deployments, the communication link 114 may be referred to as a side link. For example, a UE 104 may support wireless communication directly with another UE 104 via a PC5 interface.

[058] A 102 NE can support communications with a 106 CN, or with another 102 NE, or both. For example, a 102 NE can interact with another 102 NE or with the 106 CN through one or more backhaul links (e.g., S1, N2, N2, or network interface). In some deployments, the 102 NEs can communicate directly. In other implementations, the 102 NEs can communicate with each other or indirectly (e.g., through the 106 CN). In some implementations, one or more 102 NEs can include subcomponents, such as an access network entity, which can be an example of an access node controller (ANC). An ANC can communicate with one or more UEs 104 through one or more other access network transmission entities, which may be called radio heads, smart radio heads, or transmit-receive points (TRPs).

[059] The CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a Mobility Management Entity (MME), an Access and Mobility Management Function (AME)) and a user plane entity that routes packets or interconnects with external networks (e.g., a service gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, Petition 870250084078, dated 09 / 18 / 2025, page 23 / 69 15 / 47 Authentication and carrier management (e.g., data carriers, signal carriers, etc.) for one or more UEs 104 served by one or more NEs 102 associated with CN 106.

[060] A CN 106 can communicate with a packet data network via one or more backhaul links (e.g., via an S1, N2, N2, or other network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 can communicate with the application server. A UE 104 can establish a session (e.g., a Protocol Data Unit (PDU) session or similar) with the CN 106 via a NE 102. The CN 106 can route traffic (e.g., control information, data, and similar) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session can be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[061] In the wireless communication system 100, NEs 102 and UEs 104 can utilize resources of the wireless communication system 100 (e.g., timing resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, NEs 102 and UEs 104 can support different resource structures. For example, NEs 102 and UEs 104 can support different frame structures. In some implementations, such as in 4G, NEs 102 and UEs 104 can support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, NEs 102 and UEs 104 can support multiple frame structures (i.e., multiple frame structures). The NE 102 and UE 104 can support various frame structures based on one or more numerologies. Petition 870250084078, dated 09 / 18 / 2025, p. 24 / 69 16 / 47

[062] One or more numerologies may be supported in the 100 wireless communication system, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ = 2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix.A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[063] A time interval of a resource (for example, a communication resource) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, of 10 milliseconds (ms). In some implementations, each frame can include several subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[064] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) can be organized according to slots. For example, a subframe might include a number (e.g., quantity) of Petition 870250084078, dated 09 / 18 / 2025, p. 25 / 69 / 47 slots. The number of slots in each subframe may also depend on one or more numerologies supported in the 100 wireless communication system. For example, the first, second, third, fourth, and fifth numerologies (i.e., μ = 0, μ = 1, μ = 2, μ = 3, μ = 4) associated with the respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may use a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on numerology. For a normal cyclic prefix, a slot might include 14 symbols.For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that the reference to a first numerology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[065] In the 100 wireless communication system, an electromagnetic (EM) spectrum can be divided, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the 100 wireless communication system can support one or multiple operating frequency bands, such as the frequency band designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz) and FR5 (114.25 GHz - 300 GHz). In some implementations, the NE 102 and UE 104 can perform wireless communications in one or more of the frequency bands of Petition 870250084078, dated 09 / 18 / 2025, page 26 / 69 18 / 47 operation. In some implementations, FR1 can be used by NEs 102 and UEs 104, among other equipment or devices, for cellular communications traffic (e.g., control information, data). In some implementations, FR2 can be used by NEs 102 and UEs 104, among other equipment or devices, for short-range, high-data-rate capabilities.

[066] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., μ=0), which includes a subcarrier spacing of 15 kHz; a second numerology (e.g., μ=1), which includes a subcarrier spacing of 30 kHz; and a third numerology (e.g., μ=2), which includes a subcarrier spacing of 60 kHz. FR2 may be associated with one or multiple numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology (e.g., μ=2), which includes a subcarrier spacing of 60 kHz; and a fourth numerology (e.g., μ=3), which includes a subcarrier spacing of 120 kHz.

[067] In an NR-DC scenario, a UE with multiple transceivers can be configured to utilize resources provided by two different nodes connected by non-ideal backhauls. One node can provide NR access and the other can provide terrestrial radio access (UTRA) (E-UTRA) or NR access to the evolved universal mobile telecommunications system (UMTS). One node can act as an MN and the other as an SN. The MN and SN are connected via a network interface, for example, the Xn interface, as specified in the 3GPP standard documents, and at least the MN is connected to the CN.

[068] For example, Figure 2 illustrates an example of another wireless communication system in accordance with aspects of the present disclosure. Petition 870250084078, dated 09 / 18 / 2025, page 27 / 69 19 / 47 [ O 69] As shown in Figure 2, the wireless communication system 200 can be a dual connectivity system 200 that includes at least one UE 201, at least one MN 202, and at least one SN 203. In particular, the dual connectivity system 200 in Figure 2 includes one UE 201, one MN 202, and one SN 203, shown for illustrative purposes. Although a specific number of UEs 201, MNs 202, and SNs 203 are represented in Figure 2, it is considered that any number of UEs 201, MNs 202, and SNs 203 can be included in the wireless communication system 200.

[070] Referring to Figure 2, UE 201 can connect to MN 202 and SN 203 via an interface, for example, the Uu interface, as specified in the 3GPP standard documents. MN 202 and SN 203 can be connected to each other via a network interface, for example, the Xn interface, as specified in the 3GPP standard documents. MN 202 can be connected to the core network via a network interface (not shown in Figure 2), for example, the NG interface, as specified in the 3GPP standard documents. UE 201 can be configured to utilize resources provided by MN 202 and SN 203 to perform data transmission.

[071] MN 202 refers to a RAN node that provides a control plane connection to the core network. In some implementations of this disclosure, in the E-UTRA-NR DC (EN-DC) scenario, MN 202 may be an eNB. In some other implementations of this disclosure, in the next-generation E-UTRA-NR DC (NGEN-DC) scenario, MN 202 may be a next-generation (ng)-eNB. In some other implementations of this disclosure, in the NR-DC or NR-E-UTRA DC (NE-DC) scenario, MN 202 may be a gNB. An MN 202 may also be called a master-NG-RAN (M-NG-RAN) node in some implementations of this disclosure.

[072] An MCG may refer to a group of service cells associated with MN 202 and include a PCell and, optionally, a Petition 870250084078, dated 09 / 18 / 2025, p. 28 / 69 20 / 47 or more secondary cells (SCells). A PCell can provide a control plane connection with the UE 201.

[073] SN 203 may refer to a radio access network node without a control plane connection to the core network, but which provides additional capabilities to UE 201. In some implementations of this disclosure, in the ENS-DC scenario, SN 203 may be an en-gNB. In some other implementations of this disclosure, in the NR-DC scenario, SN 203 may be an ng-eNB. In another implementation of this disclosure, in the NR-DC or NGEN-DC scenario, SN 203 may be a gNB. An SN 203 may also be called a secondary NG-RAN node (S-NG-RAN) in some implementations of this disclosure.

[074] An SCG may refer to a group of service cells associated with the SN and include a PSCell and, optionally, one or more SCells. The PCell of the MCG and the PSCell of the SCG may also be called SpCell.

[075] According to the RAN2#122 agreement, the UE must report the BAT per QoS flow to the network side, which can at least support XR traffic detection on the network side. In some implementations of this disclosure, the BAT may be an absolute time (or an absolute time value) or a relative time (or a relative time value), for example, a time relative to a SEN boundary. The SEN may be a reference SEN, which is a configured or default SEN, or it may be a SEN in which the BAT is transmitted. The SEN boundary is configured or specified by default.

[076] Figure 3 illustrates some exemplary BATs according to aspects of the present disclosure.

[077] As shown in Figure 3, according to some implementations of this disclosure, the BAT of a QoS flow can be represented by a time relative to a boundary of a reference SFN, for example, BAT (a) shown in Figure 3. For example, both the reference SFN and its boundary are standard, Petition 870250084078, dated 09 / 18 / 2025, page 29 / 69 21 / 47 for example, the limit of the reference SFN being an initial point of SFN 0 and subframe 0. For another example, the reference SFN is configured to be SFN 512, the SFN limit is an initial point of an initial subframe of the SFN by default and therefore the limit of the reference SFN is an initial point of SFN 512 and subframe 0.

[078] According to some implementations of this disclosure, the BAT of a QoS stream can be represented by a time relative to a boundary of an SFN in which the BAT is transmitted (or will be transmitted), for example, BAT(b) shown in Figure 3. For example, the SFN boundary is configured to be or specified by default as a starting point of an initial subframe of the SFN in which the BAT is transmitted, for example, the starting point of subframe 0 of the SFN in which the BAT is transmitted. An SFN in which the BAT is transmitted can also be called a sending (or transmitting) BAT SFN. Considering that the UE can report the BAT to the originating gNB in ​​a UE assistance information message, an exemplary sending BAT SFN can be a sending UE assistance information SFN.

[079] However, the same SFN boundary may correspond to different times in different cells (or RAN nodes), i.e., there may be temporal desynchronization between cells. Thus, if the BAT is a relative time, there may be problems interpreting the BAT due to temporal desynchronization between cells, which needs to be avoided. In this document, some implementations of this disclosure will be specifically illustrated considering a BAT as a time relative to an SFN boundary. Furthermore, although the BAT is illustrated as a QoS flow BAT, subject matter experts should be aware that the technical solution disclosed and taught in this document can also be applied to the BAT expressed in other ways (e.g., the BAT is illustrated as a DRB BAT). Petition 870250084078, dated 09 / 18 / 2025, page 30 / 69 22 / 47

[080] Figure 4 is a flowchart illustrating a BAT reporting support method in accordance with aspects of this disclosure. Although the method is illustrated at the system level between a UE, a first RAN node and a second RAN node, those skilled in the art should understand that the method implemented in the UE and the two RAN nodes can be implemented separately and / or incorporated by other devices with similar functions.

[081] In different scenarios, the first RAN node and the second RAN node may play different roles. For example, in some scenarios, such as transfer scenarios, the first RAN node is a source RAN node, such as a source gNB, and the second RAN node is a target RAN node, such as a target gNB. In other scenarios, such as NR-DC scenarios, the first RAN node is an MN and the second RAN node is an SN.

[082] Taking the transfer scenarios as an example, as shown in Figure 4, in step 401, the UE will receive a BAT request for a QoS flow from the first RAN node, for example, the originating RAN node. The UE will determine (or calculate, or similarly) the BAT of the QoS flow used in the originating RAN node (or originating cell) in step 403. The BAT of the QoS flow used in the first RAN node, for example, the originating RAN node (or originating cell), can also be called the first BAT of the QoS flow for simplification. As mentioned earlier, since a QoS BAT can be represented in various ways, there are several ways to determine the BAT of the QoS stream. For example, the QoS BAT used at the originating RAN node can be determined as a time relative to the boundary of a reference SFN, or it can be determined as a time relative to the boundary of the SFN in which the BAT is transmitted.

[083] The UE will report the determined BAT of the QoS flow used in the source cell, i.e., the first BAT for the source RAN node in step 405, for example, in an UE assistance information message. Petition 870250084078, dated 09 / 18 / 2025, page 31 / 69 23 / 47

[084] After receiving the first BAT from the UE, the originating RAN node will transmit the first BAT to the target RAN node in step 407, for example, in a transfer request message. For example, the first BAT can be included in an inter-node RRC message as an RRC container or in an explicit information element (IE) of an Xn-AP message. In the case where the first BAT is a time relative to the boundary of a reference SEN, the originating RAN node can also send the reference SEN to determine the first BAT to the target RAN node, for example, in the transfer request message or in another message. However, if the reference SEN is specified as a fixed (default) value, the reference SEN does not need to be transmitted to the target RAN node.If the first BAT is a time relative to the SEN limit at which the BAT is transmitted, the SEN at which the BAT is transmitted will also be provided to the target RAN node, for example, in the transfer request message.

[085] The source RAN node can also transmit the SEN offset from the source RAN node (or source cell) to the target RAN node (or target cell), so that the SEN time difference between the source RAN node and the target RAN node is determined at the target RAN node. Regarding a SEN offset, it contains the time offset between an absolute time reference and the start of an initial SEN, for example, SEN 0 starts. The SEN offset is calculated assuming that the SEN transmission started at the absolute time reference. An exemplary absolute time reference is 1980-01-06 TOO :00:19 International Atomic Time (TAI). In some cases, the source RAN node and the target RAN node can transmit their respective SFN offsets to each other at step 400 as a legacy, for example, in an Xn configuration request message or NG-RAN node configuration update message. In some other cases, the originating RAN node may transmit the Petition 870250084078, dated 09 / 18 / 2025, page 32 / 69 24 / 47 SFN offset from the source RAN node in another step or transmit the SFN time difference between the source and target cells directly from the source RAN node in the transfer request message or similar. [08 6] In step 409, the target RAN node will determine the BAT of the QoS flow used in the target RAN node (or target cell) according to the first BAT and SFN time difference between the source RAN node and the target RAN node. The SFN time difference between the source RAN node and the target RAN node can be a difference between the SFN offset of the first RAN node and an SFN offset of the second RAN node.

[087] The QoS flow BAT used in the second RAN node, for example, the target RAN node (or target cell), can also be called the second QoS flow BAT for simplification. If the BAT used in the source cell, i.e., the first BAT, is a time relative to the boundary of a reference SFN, the target RAN node will determine the second BAT as a time relative to the boundary of the reference SFN. According to the first BAT, the SFN time difference between the source RAN node and the target RAN node, and the reference SFN of the source cell. For example, the BAT used in the target cell, i.e., the second BAT, can be determined by (target cell SFN offset - source cell SFN offset + the BAT used in the source cell) assuming that the source cell's reference SFN is SFN 0.If the BAT used in the originating cell is a time relative to the transmission SFN limit of the first BAT, the target RAN node will determine the second BAT as a time relative to the transmission SFN limit of the first BAT according to the first BAT, the SFN time difference between the originating RAN node and the target RAN node, and the transmission SFN of the first BAT.

[088] The identical or similar technical solution to that illustrated in view of the transfer scenarios in Figure 4 may also be Petition 870250084078, dated 09 / 18 / 2025, p. 33 / 69 25 / 47 applied in NR-DC scenarios, where the first RAN node is an MN and the second RAN node is an SN. That is, the source RAN node illustrated above will be replaced by an MN, for example, a master NG-RAN node, and the target RAN node will be replaced by an SN, for example, a secondary NG-RAN node. Information related to BAT determination or reporting can also be transmitted in adaptive messages between the MN and the SN. For example, the transfer request message, where the first BAT (the BAT used in the first RAN node) will be transmitted, is replaced by an S-NG-RAN node addition request message or an S-NG-RAN node modification request message or similar.

[089] Figure 5 is a flowchart illustrating another method of supporting BAT reporting in accordance with aspects of this disclosure. Although the method is illustrated at the system level between a UE, a first RAN node and a second RAN node, those skilled in the art should understand that the method implemented in the UE and the two RAN nodes can be implemented separately and / or incorporated by other devices with similar functions.

[090] Similarly, in different scenarios, the first RAN node and the second RAN node may play different roles. For example, in some scenarios, for example, in transfer scenarios, the first RAN node is a source RAN node, for example, a source gNB, and the second RAN node is a target RAN node, for example, a target gNB. In some other scenarios, for example, in NR-DC scenarios, the first RAN node is an MN, for example, a master NG-RAN node, and the second RAN node is an SN, for example, a secondary NG-RAN node.

[091] Still taking the transfer scenarios as an example, as shown in Figure 5, in step 501, the UE will receive a BAT request from a QoS flow from the source RAN node. The UE will determine (or calculate or similar) the BAT of the QoS flow used in the source RAN node (or source cell), i.e., Petition 870250084078, dated 09 / 18 / 2025, page 34 / 69 26 / 47 a first BAT of the QoS stream in step 503. Similarly, since a QoS BAT can be represented in various ways, there are various ways to determine the QoS stream BAT. For example, the QoS BAT used in the originating RAN node, i.e., the first BAT, can be determined as a time relative to the boundary of a reference SFN, or it can be determined as a time relative to the boundary of the SFN in which the BAT is transmitted.

[092] The UE will report the determined BAT of the QoS flow used in the source cell, i.e., the first BAT for the source RAN node in step 505, for example, in an UE assistance information message.

[093] In step 507, the source RAN node will determine a BAT of the QoS flow used in the second RAN node, that is, the second BAT of the QoS flow according to the time difference between the first BAT and the SFN between the first RAN node and the second RAN node. In some cases, the time difference between the first RAN node and the second RAN node may be a difference between the SFN offset of the first RAN node and an SFN offset of the second RAN node. Before that, the source RAN node may also receive the SFN offset from the target RAN node (or target cell). In some cases, the source RAN node and the target RAN node may transmit their respective SFN offset to each other in step 500 as legacy, for example, in an Xn configuration request message or an NG-RAN node configuration update message.The target RAN node can optionally transmit a reference SFN with the SFN offset to the source cell at step 500 in some cases. In other cases, the source RAN node can receive the SFN offset from the target RAN node at a later step.

[094] If the BAT used in the source cell is, i.e., the first BAT is a time relative to the boundary of a reference SFN, the source RAN node will determine the second BAT as Petition 870250084078, dated 09 / 18 / 2025, page 35 / 69 27 / 47 a time relative to the reference SFN boundary According to the first BAT, the SFN time difference between the source RAN node and the target RAN node, and the reference SFN of the source cell. For example, the BAT used in the target cell, i.e., the second BAT, can be determined by (target cell SFN offset - source cell SFN offset + the BAT used in the source cell) assuming the reference SFN is SFN 0. In the case where the BAT used in the source cell, i.e., the first BAT, is a time relative to the transmission SFN boundary of the first BAT, the source RAN node will determine the second BAT as a time relative to the transmission SFN boundary of the first BAT according to the first BAT, the SFN time difference between the source RAN node and the target RAN node, and the transmission SFN of the first BAT.

[095] After determining the second BAT of the QoS flow, the source RAN node will transmit the second BAT to the target RAN node in step 509, for example, in a transfer request message. For example, the second BAT can be included in an RRC message between nodes as an RRC container or in an explicit IE of an Xn-AP message.

[096] Similarly, the identical or similar technical solution to that illustrated in view of the transfer scenarios in Figure 5 can be applied in NR-DC scenarios, where the first RAN node is an MN and the second RAN node is an SN. That is, the source RAN node illustrated above will be replaced by an MN, for example, a master NG-RAN node, and the target RAN node will be replaced by an SN, for example, a secondary NG-RAN node. Information related to BAT determination or reporting can also be transmitted in adaptive messages between the MN and the SN. For example, the transfer request message, in which the second BAT (the BAT used in the second RAN node) will be transmitted, can be replaced by an S-NG-RAN node addition request message or a modification request message. Petition 870250084078, dated 09 / 18 / 2025, pp. 36 / 69 28 / 47 node of S-NG-RAN.

[097] According to aspects of this disclosure, a technical solution for determining or calculating BAT by the UE, instead of the network side, is also provided to support BAT reporting in NR-DC scenarios, which can also avoid misunderstanding of BAT due to temporal desynchronization between MN and SN. The BAT determined by the UE can be a BAT used in the MN, i.e., the first BAT, or it can be a BAT used in the SN, i.e., the second BAT, which can be a time relative to a SEN boundary, as mentioned above. The UE can perform BAT determination as requested by the network side, which can be explicitly or implicitly requested.

[098] In some implementations of this disclosure, the UE calculates the BAT using the SFN time of PCell or PSCell according to the type of DRB carrier to which the QoS stream belongs. The cell (e.g., PCell or SCell) or group of cells (e.g., MCG or SCG) that will be used for the BAT calculation depends on the type of DRB carrier. The cell or group of cells used for the BAT calculation may also be called the reference point. That is, the UE autonomously determines the reference point based on the DRB type.

[099] If the DRB carries MCG or SCG only, the UE will calculate the BAT according to the MCG or SCG, respectively. In other words, if the DRB is served only by MCG or SCG, the UE calculates the BAT according to the SFN time (e.g., SFN offset) of PCell or PSCell, respectively. For example, in some cases, the MN configures the UE to report the BAT of a QoS flow or a DRB. If the QoS flow or the DRB is served only by MCG or SCG (MCG carrier or SCG carrier only), the UE will use the SFN time of PCell (MCG) or PSCell (SCG) to calculate the BAT, respectively.

[100] If the DRB is configured with the carrier type Petition 870250084078, dated 09 / 18 / 2025, p. 37 / 69 29 / 47 duplicated or split, i.e., the DRB is served by both MCG and SCG, the UE can calculate the BAT of the PCell (MCG) and the BAT of the PSCell (SCG) and report them to the network. For example, if the MN configures the UE to report the BAT of a QoS flow or a DRB, where the UL data transmission of the QoS flow or the DRB is served by both MCG and SCG (split UL carrier), the UE will use the SEN time of the PCell (MCG) to calculate the BAT of the PCell (MCG) and will use the SEN of the PSCell (SCG) to calculate the BAT of the PSCell (SCG). The UE reports the BAT of the PCell and the BAT of the PSCell to the network side and explicitly or implicitly indicates which BAT is for the PCell (MCG) and which BAT is for the PSCell (SCG).

[101] According to some other implementations of this disclosure, if the DRB is serviced by a split UL carrier, the UE calculates the SPCell BAT of the primary path configured by the network. For example, for a split UL carrier, the network may configure a primary path (e.g., MCG or SCG) for UL data transmission. If MCG is configured as the primary path, the UE will use the SEN time of the SPCell (MCG) to calculate the BAT. If SCG is configured as the primary path, the UE will use the SEN time of the SPCell (SCG) to calculate the BAT.

[102] The network side may change (or update) the carrier type by RRC reconfiguration or similar. In the event of a DRB type change, the UE will update the BAT according to the updated DRB type and report the updated BAT to the network side accordingly.

[103] For example, the DRB is configured as an MCG carrier and the UE uses the PCell SEN time (MCG) to initially calculate the BAT. The network side reconfigures the DRB to be an SCG carrier. Upon receiving the carrier type change indication from MCG carrier to SCG carrier, the UE will determine or calculate or update the BAT according to the PCell SFN time (SCG), and report the updated BAT to Petition 870250084078, dated 09 / 18 / 2025, pp. 38 / 69 30 / 47 the network side, for example, to the MN and the MN will forward the updated BAT to the SN.

[104] For another example, the DRB is configured as an MCG carrier and the UE uses the SEN time of the PCell (MCG) to calculate the BAT initially. Then, the network side reconfigures the DRB to be a split carrier. Upon receiving the carrier type change indication from MCG carrier to split carrier, the UE will also determine or calculate the BAT according to the SEN time of the PSCell (SCG), and will also report the BAT according to the SEN time of the PSCell (SCG) to the network side, for example, it will report to the MN and the MN will forward the BAT according to the SEN time of the PSCell (SCG) to the SN.

[105] In another example, the DRB is configured as a split carrier and the MCG is configured as the primary path, and the UE uses the SEN time of the PCell (MCG) to initially calculate the BAT. Then, the network side reconfigures the primary path from the split DRB to the SCG. Upon receiving the primary path change indication from the split carrier to the SCG, the UE will determine, calculate, or update the BAT according to the SEN time of the PCell (SCG) and report the updated BAT to the network side, for example, to the MN, and the MN will forward the updated BAT to the SN.

[106] In some implementations of this disclosure, the network side will configure which cell will be referenced for the BAT calculation, for example, PCell or SCell, MCG or SCG, or both, etc. The UE will calculate the BAT according to the cell indicated by the network side. If the network side configures that PCell (MCG) is used to calculate the BAT, the UE will use the SEN time of PCell (MCG) to calculate the BAT. If the network side configures that PSCell (SCG) is used to calculate the BAT, the UE will use the SEN time of PSCell (SCG) to calculate the BAT. If the network side configures that both PCell (MCG) and PSCell (SCG) are used to calculate the BAT, the UE uses Petition 870250084078, dated 09 / 18 / 2025, pp. 39 / 69 31 / 47 uses the SEN time of PCell (MCG) to calculate the BAT of PCell (MCG) and uses the SFN time of PSCell (SCG) to calculate the BAT of PSCell (SCG). Consequently, the UE will report both BATs to the network side and also, explicitly or implicitly, indicate which BAT is for MCG and which BAT is for SCG.

[107] In some implementations of this disclosure, UE calculates BAT according to the SFN time of the cell (or node) from which the RRC configuration is set.

[108] For example, if the network side requests BAT reports in the MCG configuration, for example, in IE masterCellGroup, the UE will use the SFN time of the PCell (MCG) to calculate the BAT.

[109] If the network side requests BAT reports in the SCG configuration, for example, in IE secondaryCellGroup, the UE will use the SFN time of the PSCell (SCG) to calculate the BAT.

[110] If the network side requests that the BAT be reported by SRB 3 or the BAT be configured by SRB 3, the UE will use the PSCell SFN time (SCG) to calculate the BAT and report it to the SN via SRB3 directly.

[111] Figure 6 illustrates an example of UE 600 according to aspects of the present disclosure. The UE 600 may include a processor 602, a memory 604, a controller 606 and a transceiver 608. The processor 602, the memory 604, the controller 606 or the transceiver 608, or various combinations thereof or various components thereof, may be examples of means of carrying out various aspects of the present disclosure as described in this document. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) by means of one or more interfaces.

[112] 0 processor 602, memory 604, controller 606 or transceiver 608, or various combinations or components thereof, may be implemented in hardware (for example, a set of Petition 870250084078, dated 09 / 18 / 2025, pp. 40 / 69 32 / 47 circuits). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means to perform the functions described in this disclosure.

[113] 0 Processor 602 may include an intelligent hardware device (for example, a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, Processor 602 may be configured to operate Memory 604. In other implementations, Memory 604 may be integrated into Processor 602. Processor 602 may be configured to execute computer-readable instructions stored in Memory 604 to enable UE 600 to perform various functions of this disclosure.

[114] Memory 604 may include volatile or non-volatile memory. Memory 604 may store computer-readable and computer-executable code, including instructions that, when executed by processor 602, cause UE 600 to perform various functions described in this document. The code may be stored on a non-transient computer-readable medium, such as memory 604 or another type of memory. Computer-readable media include both non-transient storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. A non-transient storage medium may be any available medium that can be accessed by a general-purpose or specific-purpose computer.

[115] In some implementations, processor 602 and memory 604 coupled to processor 602 can be configured to cause UE 600 to perform one or more of the functions described in this document (for example, executing instructions stored in memory 604 by processor 602). For example, the Petition 870250084078, dated 09 / 18 / 2025, page 41 / 69 Processor 33 / 47 602 can support wireless communication on the UE 600, according to the examples disclosed in this document. The UE 600 can be configured to support a means of receiving a BAT request from a QoS flow, from one network side; to support a means of determining a BAT from the QoS flow, where the QoS flow's BAT is a time value relative to an SFN threshold; and to support a means of transmitting the determined BAT from the QoS flow to the network side.

[116] In some implementations, at least one processor is configured to perform the UE: receive the QoS stream BAT request from a source RAN node; determine the QoS stream BAT used on the source RAN node; and transmit the determined QoS stream BAT to the source RAN node.

[117] In some implementations, at least one processor is configured to perform the UE: receive the QoS stream BAT request from an MN; determine the QoS stream BAT used in the MN; and transmit the determined QoS stream BAT to the MN.

[118] In some implementations, the determined BAT of the QoS flow is transmitted to the network side in the UE assistance information message.

[119] In some implementations, at least one processor is configured to perform the UE: receive the QoS stream BAT request from an MN; determine the QoS stream BAT according to the DRB type to which the QoS stream belongs; and transmit the determined QoS stream BAT to the MN.

[120] In some cases, at least one processor is configured to perform the UE: receive information indicating an updated DRB type to which the QoS flow belongs; and determine the BAT of the QoS flow according to the updated DRB type to which the QoS flow belongs.

[121] In some cases, at least one processor is configured to do the UE: determine the BAT of the QoS stream using the time Petition 870250084078, dated 09 / 18 / 2025, page 42 / 69 34 / 47 of SFN from a PCell in the case where the DRB is served only by the MCG; or determine the BAT of the QoS stream using the SFN time of a PSCell in the case where the DRB is served only by the SCG; or determine a first BAT of the QoS flow using the SFN time of the PCell and a second BAT of the QoS flow using the SFN time of the PSCell in the case where the DRB is served by both the MCG and the SCG; or determine the BAT of the QoS flow using the SFN time of an SPCell n of a configured primary path in the case where the DRB is served by the split uplink carrier.

[122] In some implementations, at least one processor is configured to perform the UE: receive the QoS stream BAT request from an MN; determine the QoS stream BAT according to a cell indicated by the MN for BAT calculation; and transmit the determined QoS stream BAT to the MN.

[123] In some cases, at least one processor is configured to perform the UE: determine the QoS flow BAT using the SFN time of a PCell if only the PCell or MCG is indicated; or determine the QoS flow BAT using the SFN time of a PSCell if only the PSCell or SCG is indicated; or determine a first QoS flow BAT using the SFN time of the PCell and a second QoS flow BAT using the SFN time of the PSCell if both PCell and PSCell are indicated or both MCG and SCG are indicated.

[124] In some cases, at least one processor is configured to do the UE: transmit the first BAT and the second BAT to the MN with information indicating which BAT is for the MCG and which BAT is for the SCG, in the case of both the first BAT and the second BAT being determined.

[125] In some implementations, at least one processor is configured to perform the UE: receive the QoS stream BAT request in the MCG configuration, from an MN; determine the QoS stream BAT using the SFN time of a PCell and transmit the determined QoS stream BAT to the MN. Petition 870250084078, dated 09 / 18 / 2025, page 43 / 69 35 / 47

[126] In some implementations, at least one processor is configured to perform the UE: receive the QoS stream BAT request in the SCG configuration, from an MN; determine the QoS stream BAT using the SFN time of a PSCell; and transmit the determined QoS stream BAT to the MN.

[127] In some implementations, at least one processor is configured to perform the UE: receive the QoS stream BAT request from an MN or an SN, where the QoS stream BAT is configured to be reported by an SRB n 3; determine the QoS stream BAT using the SFN time of an SCG PSCell; and transmit the determined QoS stream BATs to the SN.

[128] In some implementations, at least one processor is configured to perform the UE: receive the QoS stream BAT request from an MN or an SN, where the QoS stream BAT is configured by an SRB3; determine the QoS stream BAT using the SFN timing of an SCG PSCell; and transmit the determined QoS stream BATs to the SN by the SRB3. [12 9] In some implementations, the boundary of an SFN is a boundary of a reference SFN or a boundary of an SFN in which the BAT is transmitted.

[130] In some implementations, the reference SFN and the reference SFN boundary are configured or are default, and / or the SFN boundary at which the BAT is transmitted is a starting point of an initial SFN subframe.

[131] The 606 controller can manage input and output signals for the UE 600. The 606 controller can also manage peripherals not integrated into the UE 600. In some implementations, the 606 controller can utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the 606 controller can be implemented as part of the 602 processor. Petition 870250084078, dated 09 / 18 / 2025, pp. 44 / 69 36 / 47

[132] In some implementations, the UE 600 may include at least one 608 transceiver. In other implementations, the UE 600 may have more than one 608 transceiver. The 608 transceiver may represent a wireless transceiver. The 608 transceiver may include one or more 610 receiver chains, one or more 612 transmitter chains, or a combination thereof.

[133] A 610 receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the 610 receiver chain may include one or more antennas to receive the signal via aerial or wireless transmission. The 610 receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The 610 receiver chain may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by inverting the modulation technique applied during signal transmission. The 610 receiver chain may include at least one decoder to decode and process the demodulated signal to receive the transmitted data.

[134] A 612 transmitter chain can be configured to generate and transmit signals (e.g., control information, data, packets). The 612 transmitter chain may include at least one modulator to modulate data into a carrier signal, preparing the signal for wireless transmission. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes, such as phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The 612 transmitter chain may also include at least one power amplifier configured to amplify the modulated signal to a power level appropriate for wireless transmission. The chain Petition 870250084078, dated 09 / 18 / 2025, pp. 45 / 69 The 37 / 47 612 transmitter may also include one or more antennas to transmit the amplified signal over the air or wirelessly.

[135] Figure 7 illustrates an example of a 700 processor according to aspects of the present disclosure. The 700 processor may be an example of a processor configured to perform various operations according to the examples described in this document. The 700 processor may include a 702 controller configured to perform various operations according to the examples described in this document. The 700 processor may optionally include at least one 704 memory, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the 700 processor may optionally include one or more arithmetic logic units (ALUs) 706. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) by means of one or more interfaces (e.g., buses).

[136] The 700 processor may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, retrieve, transmit, send, forward, store, determine, identify, access, write, read) as described in the examples in this document. The processor chipset may include one or more cores, one or more caches (e.g., local memory or memory included in the processor chipset (e.g., the 700 processor) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PGM), and others).

[137] The 702 controller can be configured to manage Petition 870250084078, dated 09 / 18 / 2025, pp. 46 / 69 38 / 47 and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the 700 processor to enable the 700 processor to support various operations, as described in the examples in this document. For example, the 702 controller can operate as a control unit for the 700 processor, generating control signals that manage the operation of various components of the 700 processor. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[138] Controller 702 can be configured to fetch (e.g., get, retrieve, receive) instructions from memory 704 and determine the subsequent instruction(s) to be executed to enable processor 700 to support various operations as described in this document. Controller 702 can be configured to track the memory address of instructions associated with memory 704. Controller 702 can be configured to decode instructions to determine the operation to be performed and the operands involved. For example, controller 702 can be configured to interpret the instruction and determine the control signals to be sent to other components of processor 700 to enable processor 700 to support various operations as described in this document. Additionally, or alternatively, controller 702 can be configured to manage the data flow within processor 700.The 702 controller can be configured to control data transfer between registers, arithmetic logic units (ALUs), and other functional units of the 700 processor.

[139] Memory 704 may include one or more caches (per Petition 870250084078, dated 09 / 18 / 2025, pp. 47 / 69 39 / 47 example, local memory or memory included in the 700 processor or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the 704 memory may reside within or on a processor chipset (e.g., local to the 700 processor). In some other implementations, the 704 memory may reside externally to the processor chipset (e.g., remote to the 700 processor).

[140] Memory 704 can store computer-readable and computer-executable code, including instructions that, when executed by processor 700, cause processor 700 to perform various functions described in this document. The code can be stored in a non-transient, computer-readable medium, such as system memory or another type of memory. Controller 702 and / or processor 700 can be configured to execute computer-readable instructions stored in memory 704 to cause processor 700 to perform various functions. For example, processor 700 and / or controller 702 can be coupled to memory 704 or to memory 704; processor 700, controller 702, and memory 704 can be configured to perform various functions described in this document. In some examples, processor 700 can include multiple processors and memory 704 can include multiple memories.One or more of the multiple processors can be coupled to one or more of the multiple memories, which can be configured, individually or collectively, to perform various functions described in this document.

[141] One or more 706 ALUs can be configured to support various operations, as described in the examples in this document. In some implementations, one or more 706 ALUs may reside within or on a processor chipset (e.g., the 700 processor). In other implementations, one or more 706 ALUs may reside externally to the processor chipset (e.g., the 700 processor). One or more ALUs Petition 870250084078, dated 09 / 18 / 2025, pp. 48 / 69 40 / 47 706 ALUs can perform one or more calculations, such as addition, subtraction, multiplication, and division, on data. For example, one or more 706 ALUs can receive input operands and an operation code, which determines the execution of an operation. One or more 706 ALUs can be configured with a variety of logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, one or more 706 ALUs can support logical operations such as AND, OR, XOR, NOR, and NAND, allowing one or more 706 ALUs to handle conditional operations, comparisons, and bitwise operations.

[142] The 700 processor can support wireless communication according to the examples disclosed in this document. The 700 processor can be configured or operated to support a means of receiving a BAT request from a QoS flow on a network side; to support a means of determining a BAT from the QoS flow, wherein the QoS flow BAT is a time value relative to an SFN threshold; and to support a means of transmitting the determined BAT from the QoS flow to the network side.

[143] Figure 8 illustrates an example of an NE 800, for example, the first RAN node or the second RAN node according to aspects of the present disclosure. The NE 800 may include a processor 802, a memory 804, a controller 806 and a transceiver 808. The processor 802, the memory 804, the controller 806 or the transceiver 808, or various combinations thereof or various components thereof, may be examples of means of carrying out various aspects of the present disclosure as described in this document. These components may be coupled (for example, operatively, communicatively, functionally, electronically, electrically) by means of one or more interfaces.

[144] The 802 processor, 804 memory, 806 controller or Petition 870250084078, dated 09 / 18 / 2025, pp. 49 / 69 41 / 47 The 808 transceiver, or various combinations or components thereof, may be implemented in hardware (e.g., circuit assembly). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in this disclosure.

[145] The 802 processor may include an intelligent hardware device (for example, a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the 802 processor may be configured to operate the 804 memory. In other implementations, the 804 memory may be integrated into the 802 processor. The 802 processor may be configured to execute computer-readable instructions stored in the 804 memory to enable the NE 800 to perform various functions of the present disclosure.

[146] 804 memory may include volatile or non-volatile memory. 804 memory may store computer-readable and computer-executable code, including instructions that, when executed by the 802 processor, cause the NE 800 to perform various functions described in this document. The code may be stored on a non-transient computer-readable medium, such as 804 memory or another type of memory. Computer-readable media include both non-transient storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. A non-transient storage medium may be any available medium that can be accessed by a general-purpose or specific-purpose computer.

[147] In some implementations, the 802 processor and the 804 memory coupled to the 802 processor can be configured to cause the NE 800 to perform one or more of the functions described. Petition 870250084078, dated 09 / 18 / 2025, pages 50 / 69 42 / 47 in this document (for example, executing instructions stored in memory 804 by the 802 processor). For example, the 802 processor can support wireless communication on the NE 800, according to the examples disclosed in this document. The NE 800 can be configured to support a means of receiving a first BAT of a QoS stream used in a first RAN node; and to support a means of determining a second BAT of the QoS stream used in a second RAN node according to the first BAT and SFN time difference between the first RAN node and the second RAN node, where each BAT of the QoS stream is a time value relative to an SFN boundary, and the RAN node is either the first RAN node or the second RAN node.

[148] In some implementations, at least one processor is configured to do the UE: the boundary of an SFN is a boundary of a reference SFN, or a boundary of an SFN on which the BAT is transmitted.

[149] In some implementations, the RAN node is the second node, and the processor is configured to make the RAN node: receive the first BAT of the QoS stream from the first RAN node; and receive an SFN offset from the first RAN node, wherein the SFN time difference between the first RAN node and the second RAN node is a difference between the SFN offset of the first RAN node and an SFN offset of the second RAN node.

[150] In some cases, in the case where the first BAT of the QoS stream is a time value relative to the reference SFN boundary, the processor is configured to make the RAN node: receive the reference SFN to calculate the first BAT of the QoS stream from the first RAN node; and determine the second BAT of the QoS stream according to the first BAT, the SFN time difference between the first RAN node and the second RAN node and the reference SFN to calculate the first BAT.

[151] In some cases, in the case of the first BAT of the stream of Petition 870250084078, dated 09 / 18 / 2025, pp. 51 / 69 43 / 47 QoS being a time value relative to the SFN boundary in which the BAT is transmitted, the processor is configured to make the RAN node: receive the SFN in which the BAT is transmitted to calculate the first BAT of the QoS stream from the first RAN node; and determine the second BAT of the QoS stream according to the first BAT, the time difference of the SFN between the first RAN node and the second RAN node and the SFN in which the BAT is transmitted to calculate the first BAT.

[152] In some implementations, the first RAN node is a source RAN node or MN, and the second RAN node is a target RAN node or SN.

[153] In some cases, in the case where the first RAN node is a source RAN node and the second RAN node is a target RAN node, the first BAT of the QoS flow is received in a transfer request message; or in the case where the first RAN node is an MN and the second RAN node is an SN, the first BAT of the QoS flow is received in an S-NG-RAN node addition request message or an S-NG-RAN node modification request message.

[154] In some implementations, the RAN node is the first node, and the processor is configured to make the RAN node: receive the first BAT of the QoS stream from a UE; and receive an SFN offset from the second RAN node, wherein the SFN time difference between the first RAN node and the second RAN node is a difference between an SFN offset from the first RAN node and the SFN offset from the second RAN node.

[155] In some cases, if the second BAT of the QoS stream is a time value relative to the reference SFN boundary, the processor is configured to make the RAN node: receive the reference SFN to calculate the second BAT of the QoS stream from the second RAN node; and determine the second BAT of the QoS stream according to the first BAT, the SFN time difference between the Petition 870250084078, dated 09 / 18 / 2025, pp. 52 / 69 44 / 47 first RAN node and the second RAN node and the reference SFN to calculate the second BAT.

[156] In some cases, the first RAN node is a source RAN node or MN, and the second RAN node is a target RAN node or SN.

[157] In some cases, the processor is configured to make the RAN node: transmit the second BAT of the QoS stream to the second RAN node in a transfer request message if the first RAN node is a source RAN node and the second RAN node is a target RAN node; or transmit the second BAT of the QoS stream to the second RAN node in an S-NG-RAN node addition request message or an S-NG-RAN node modification request message if the first RAN node is an MN and the second RAN node is an SN.

[158] In some implementations, the reference SFN and the reference SFN boundary are configured or are default, and / or the SEN boundary at which the BAT is transmitted is a starting point of an initial SFN subframe.

[159] 0 The 806 controller can manage input and output signals for the NE 800. The 806 controller can also manage peripherals not integrated into the NE 800. In some implementations, the 806 controller may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the 806 controller may be implemented as part of the 802 processor.

[160] In some implementations, the NE 800 may include at least one 808 transceiver. In other implementations, the NE 800 may have more than one 808 transceiver. The 808 transceiver may represent a wireless transceiver. The 808 transceiver may include one or more 810 receiver chains, one or more 812 transmitter chains, or a combination thereof.

[161] An 810 receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the chain Petition 870250084078, dated 09 / 18 / 2025, pp. 53 / 69 A 45 / 47 810 receiver may include one or more antennas to receive the signal over the air or wirelessly. The 810 receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The 810 receiver chain may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by inverting the modulation technique applied during signal transmission. The 810 receiver chain may include at least one decoder to decode and process the demodulated signal to receive the transmitted data.

[162] An 812 transmitter chain can be configured to generate and transmit signals (e.g., control information, data, packets). The 812 transmitter chain may include at least one modulator to modulate data into a carrier signal, preparing the signal for wireless transmission. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes, such as phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The 812 transmitter chain may also include at least one power amplifier configured to amplify the modulated signal to a power level appropriate for wireless transmission. The 812 transmitter chain may also include one or more antennas to transmit the amplified signal into the air or to a wireless medium.

[163] Figure 9 illustrates a flowchart of a method according to aspects of the present disclosure. The method operations can be implemented by a UE as described in this document. In some implementations, the UE may perform a set of instructions to control the UE's functional elements to perform the described functions.

[164] In step 902, the method may include receiving a BAT request from a QoS stream, from one side of Petition 870250084078, dated 09 / 18 / 2025, pp. 54 / 69 46 / 47 network. The operations of step 902 can be performed according to the examples described in this document. In some implementations, aspects of the operations of step 902 can be performed by a UE, as described with reference to Figure 6.

[165] In step 904, the method may include determining a QoS flow BAT, where the QoS flow BAT is a time value relative to an SFN boundary. The operations in step 904 can be performed according to the examples described in this document. In some implementations, aspects of the operations in step 904 may be performed by a UE, as described with reference to Figure 6.

[166] In step 906, the method may include transmitting the determined BAT of the QoS stream to the network side. The operations of step 906 can be performed according to the examples described in this document. In some implementations, aspects of the operations of step 906 may be performed by a UE, as described with reference to Figure 6.

[167] It should be noted that the method described in this document describes one possible implementation, and that the operations and steps may be rearranged or modified in other ways and that other implementations are possible.

[168] Figure 10 illustrates a flowchart of a method according to aspects of the present disclosure. The method operations can be implemented by a NE, as described in this document. In some implementations, the NE can execute a set of instructions to control the NE's functional elements to perform the described functions.

[169] In step 1002, the method may include receiving a first BAT from a QoS stream used in a first RAN node. The operations of step 1002 can be performed according to the examples described in this document. In some implementations, aspects of the operations of step 1002 may be performed by a Petition 870250084078, dated 09 / 18 / 2025, pp. 55 / 69 47 / 47 NE, as described with reference to Figure 8.

[170] In step 1004, the method may include determining a second BAT of the QoS flow used in a second RAN node based on the first BAT and SFN time difference between the first RAN node and the second RAN node, where each BAT of the QoS flow is a time value relative to an SFN boundary, and the RAN node is either the first RAN node or the second RAN node. The operations in step 1004 may be performed according to the examples described in this document. In some implementations, aspects of the operations in step 1004 may be performed as NE, as described with reference to Figure 8.

[171] It should be noted that the method described in this document describes possible implementations, and that the operations and steps may be rearranged or modified in other ways and that other implementations are possible.

[172] The description presented in this document is intended to enable a person with common technical knowledge in the field to create or use this disclosure. Several modifications to the disclosure will be evident to a person with common technical knowledge in the field, and the generic principles defined in this document can be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and projects described in this document, but should be given the broader scope consistent with the principles and new features disclosed in this document. Petition 870250084078, dated 09 / 18 / 2025, pp. 56 / 69

Claims

1 / 7 CLAIMS 1. User equipment (UE) for wireless communication, characterized in that it comprises: at least one memory; and at least one processor coupled with the at least one memory and configured to make the UE: receive a burst arrival time (BAT) request from a Quality of Service (QoS) stream, from a network side; determine a BAT of the QoS stream, wherein the BAT of the QoS stream is a time value relative to a limit of a System Frame Number (SFN); and transmit the determined BAT of the QoS stream to the network side.

2. UE, according to claim 1, characterized in that at least one processor is configured to make the UE: receive the BAT request of the QoS stream from a source radio access network (RAN) node; determine the BAT of the QoS stream used in the source RAN node; and transmit the determined BAT of the QoS stream to the source RAN node.

3. UE, according to claim 1, characterized in that at least one processor is configured to perform the UE: receive the BAT request of the QoS stream from a master node (MN); determine the BAT of the QoS stream used in the MN; and transmit the determined BAT of the QoS stream to the MN.

4. UE, according to claim 1, characterized in that at least one processor is configured to make the UE: Petition 870250084078, dated 09 / 18 / 2025, page 57 / 69 2 / Ί receive the BAT request of the QoS stream, from a master node (MN); determine the BAT of the QoS stream according to a data radio carrier (DRB) type to which the QoS stream belongs; and transmit the determined BAT of the QoS stream to the MN.

5. UE, according to claim 4, characterized in that at least one processor is configured to perform the UE: determine the BAT of the QoS flow using the SFN time of a primary cell (PCell) in the case where the DRB is served only by the master cell group (MCG); or determine the BAT of the QoS flow using the SFN time of a secondary primary cell (PSCell) in the case where the DRB is served only by the secondary cell group (SCG); or determine a first BAT of the QoS flow using the SFN time of the PCell and a second BAT of the QoS flow using the SFN time of the PSCell in the case where the DRB is served by the MCG and the SCG; or determine the BAT of the QoS flow using the SFN time of a special cell (SPCell) of a configured primary path in the case where the DRB is served by the split uplink carrier.

6. UE, according to claim 1, characterized in that at least one processor is configured to perform the UE: receive the QoS stream BAT request from a master node (MN); determine the QoS stream BAT according to a cell indicated by the MN for BAT calculation; and transmit the determined QoS stream BAT to the MN.

7. UE, according to claim 6, characterized in that at least one processor is configured to perform Petition 870250084078, dated 09 / 18 / 2025, page 58 / 69 3 / 7 the UE: determine the QoS flow BAT using the SFN time of a primary cell (PCell) in the case where only the PCell or the master cell group (MCG) is indicated; or determine the QoS flow BAT using the SFN time of a secondary primary cell (PSCell) in the case where only the PSCell or the secondary cell group (SCG) is indicated; or determine a first QoS flow BAT using the SFN time of the PCell and a second QoS flow BAT using the SFN time of the PSCell in the case where PCell and PSCell are indicated or MCG and SCG are indicated.

8. UE, according to claim 1, characterized in that at least one processor is configured to perform the UE: receive the BAT request of the QoS stream in the master cell group (MCG) configuration, from a master node (MN); determine the BAT of the QoS stream using the SFN time of a primary cell (PCell); and transmit the determined BAT of the QoS stream to the MN.

9. UE, according to claim 1, characterized in that at least one processor is configured to perform the UE: receive the BAT request of the QoS stream in the secondary cell group (SCG) configuration, from a master node (MN); determine the BAT of the QoS stream using the SFN time of a secondary primary cell (PSCell); and transmit the determined BAT of the QoS stream to the MN.

10. UE, according to claim 1, characterized in that at least one processor is configured to make the UE: receive the QoS flow BAT request from a master node (MN) or a secondary node (SN), where the QoS flow BAT is configured to be reported by a signaling radio carrier (SRB) 3; determine the QoS flow BAT using the SFN time of a primary secondary cell (PSCell) of the secondary cell group (SCG); and transmit the determined QoS flow BATs to the SN.

11. UE, according to claim 1, characterized in that at least one processor is configured to make the UE: receive the QoS stream BAT request from a master node (MN) or a secondary node (SN), where the QoS stream BAT is configured by a signaling radio carrier (SRB) 3; determine the QoS stream BAT using the SFN timing of a primary secondary cell (PSCell) of the secondary cell group (SCG); and transmit the determined QoS stream BATs to the SN by the SRB3.

12. EU, according to claim 1, characterized in that the limit of an SFN is a limit of a reference SFN, or a limit of an SFN in which the BAT is transmitted.

13. Processor for wireless communication, characterized in that it comprises: at least one controller coupled to at least one memory and configured to make the processor: receive a burst arrival time (BAT) request from a Quality of Service (QoS) stream, from a network side; determine a BAT of the QoS stream, wherein the BAT of the QoS stream is a time value relative to a limit of a System Frame Number (SFN); and transmit the determined BAT of the QoS stream to the network side. Petition 870250084078, dated 09 / 18 / 2025, pp. 60 / 69 5 / 7 14. Radio access network (RAN) node for wireless communication, characterized in that it comprises: at least one memory; and at least one processor coupled to at least one memory and configured to make the RAN node: receive a first burst arrival time (BAT) of a quality of service (QoS) stream used in a first RAN node; and determine a second BAT of the QoS stream used in a second RAN node according to the time difference of the first BAT and the system frame number (SFN) between the first RAN node and the second RAN node, wherein each BAT of the QoS stream is a time value relative to a boundary of an SFN, and the RAN node is the first RAN node or the second RAN node.

15. RAN node, according to claim 14, characterized in that the boundary of an SFN is a boundary of a reference SFN, or a boundary of an SFN in which the BAT is transmitted.

16. RAN node, according to claim 15, characterized in that the RAN node is the second node, and the processor is configured to make the RAN node: receive the first BAT of the QoS stream from the first RAN node; and receive an SFN offset from the first RAN node, wherein the SFN time difference between the first RAN node and the second RAN node is a difference between the SFN offset of the first RAN node and an SFN offset of the second RAN node.

17. RAN node, according to claim 16, characterized in that, if the first BAT of the QoS stream is a time value relative to the reference SFN boundary, the processor is configured to make the RAN node: receive the reference SFN to calculate the first BAT of the QoS stream of the first RAN node; and determine the second BAT of the QoS stream according to the first BAT, the SFN time difference between the first RAN node and the second RAN node and the reference SFN to calculate the first BAT.

18. RAN node, according to claim 15, characterized in that the RAN node is the first node, and the processor is configured to make the RAN node: receive the first BAT of the QoS stream from a user equipment (UE); and receive an SFN offset from the second RAN node, wherein the SFN time difference between the first RAN node and the second RAN node is a difference between an SFN offset from the first RAN node and the SFN offset from the second RAN node.

19. RAN node, according to claim 18, characterized in that, in the case where the second BAT of the QoS stream is a time value relative to the reference SFN boundary, the processor is configured to make the RAN node: receive the reference SFN to calculate the second BAT of the QoS stream from the second RAN node; and determine the second BAT of the QoS stream according to the first BAT, the SFN time difference between the first RAN node and the second RAN node and the reference SFN to calculate the second BAT.

20. A method implemented by a user device (UD), characterized in that it comprises: receiving a burst arrival time (BAT) request for a Quality of Service (QoS) stream from a network side; determining a BAT of the QoS stream, wherein the QoS stream's BAT is a time value relative to a limit of a System Frame Number (SFN); and transmitting the determined BAT of the QoS stream to the network side.

Images