Method, device and system for data transmission

Abstract

The present disclosure generally relates to methods, devices, and systems for congestion control in wireless networks. One method implemented by a first network element is disclosed. The method may include determining, based on DL resource availability, that a DL burst arrival time of a DL burst for a wireless device needs to be adjusted; and transmitting a first message to a core network in a wireless communication system, the first message comprising a DL burst arrival time adjustment indication for the wireless device indicating that the DL burst arrival time of the DL burst for the wireless device needs to be adjusted.

Description

[Technical Field]

[0001] The present disclosure is directed generally to wireless communications, and more particularly to methods, devices, and systems for data transmission and resource scheduling in wireless networks. [Background technology]

[0002] Flexible and efficient wireless transmission resource scheduling is important in wireless communication networks. The ecosystem in wireless communication networks includes an increasing number of applications that require low latency. These applications include vehicle-to-vehicle communication, autonomous driving, mobile games, etc. Data transmission between various network elements in a wireless communication network needs to be coordinated to ensure smooth data transmission that meets delay budgets and requirements and to improve overall network performance. Summary of the Invention [Means for solving the problem]

[0003] The present disclosure is directed to methods, devices, and systems for data transmission and resource scheduling in wireless networks.

[0004] In some embodiments, a method implemented by a first network element is disclosed that may include determining, based on downlink (DL) resource availability, that a DL burst arrival time of a DL burst for a wireless device needs to be adjusted, and transmitting a first message to a core network in a wireless communication system, the first message comprising a DL burst arrival time adjustment indication for the wireless device indicating that the DL burst arrival time of the DL burst for the wireless device needs to be adjusted.

[0005] In some embodiments, a method implemented by a core network node in a wireless communication system is disclosed. The method may include receiving a first message from a base station in the wireless communication system, the first message comprising a DL burst arrival time adjustment indication for a wireless device indicating that a DL burst arrival time of a DL burst for the wireless device needs to be adjusted.

[0006] In some embodiments, a method implemented by a first network element is disclosed that may include determining, based on uplink (UL) resource availability, that a UL burst arrival time of a UL burst for a wireless device needs to be adjusted, and transmitting a first message to a core network in a wireless communication system, the first message comprising a UL burst arrival time adjustment indication for the wireless device.

[0007] In some embodiments, a method implemented by a core network node in a wireless communication system is disclosed that can include receiving a first message from a base station in the wireless communication system, the first message comprising a UL burst arrival time adjustment indication for a wireless device indicating that a UL burst arrival time of a UL burst for the wireless device needs to be adjusted.

[0008] In some embodiments, a method implemented by a wireless device is disclosed that may include transmitting a first message to a first network element in a wireless communication system, the first message comprising an UL burst arrival time adjustment indication for the wireless device, and receiving a second message from the first network element in response to the first message, the second message comprising confirmed UL burst arrival time information.

[0009] In some embodiments, there is a network element or device comprising a processor and a memory, the processor configured to read code from the memory and perform any method recited in any of the embodiments.

[0010] In some embodiments, a computer program product comprises computer readable program medium code stored thereon, the code, when executed by a processor, causing the processor to perform any of the methods recited in any of the embodiments.

[0011] The above embodiments, and other aspects and alternatives of their implementations, are described in more detail in the following drawings, description, and claims. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 illustrates an exemplary wireless communication network.

[0013] [Figure 2] FIG. 2 illustrates an exemplary wireless network element.

[0014] [Figure 3] FIG. 3 shows an exemplary user equipment.

[0015] [Figure 4] FIG. 4 illustrates an exemplary implementation of downlink (DL) burst arrival time adjustment.

[0016] [Figure 5] FIG. 5 shows exemplary uplink and downlink time domain patterns.

[0017] [Figure 6] FIG. 6 illustrates another exemplary implementation of downlink (DL) burst arrival time adjustment.

[0018] [Figure 7]7-9 show exemplary implementations of uplink (UL) burst arrival time adjustment. [Figure 8] 7-9 show exemplary implementations of uplink (UL) burst arrival time adjustment. [Figure 9] 7-9 show exemplary implementations of uplink (UL) burst arrival time adjustment.

[0019] [Figure 10] FIG. 10 shows exemplary periodic DL traffic and the mismatch between DL traffic arrival times and DRX cycles.

[0020] [Figure 11] FIG. 11 illustrates an exemplary application data unit (ADU) and application frame to Internet Protocol (IP) packet mapping.

[0021] [Figure 12] FIG. 12 shows an exemplary decoding and presentation timeline for an ADU.

[0022] [Figure 13] FIG. 13 illustrates an exemplary QoS subflow mapping to logical channels. DETAILED DESCRIPTION OF THE INVENTION

[0023] (wireless communication network) FIG. 1 shows an exemplary wireless communication network 100 including a core network 110 and a radio access network (RAN) 120. The core network 110 further includes at least one mobility management entity (MME) 112 and / or at least one access and mobility management function (AMF). Other functions that may be included in the core network 110 are not shown in FIG. 1. The RAN 120 further includes multiple base stations, e.g., base stations 122 and 124. The base stations may include at least one evolved NodeB (eNB) for 4G LTE, an enhanced LTE eNB (ng-eNB), or a next-generation NodeB (gNB) for 5G new radio (NR), or any other type of signal transmission / reception device, such as a UMTS NodeB. The eNB 122 communicates with the MME 112 via an S1 interface. Both the eNB 122 and the gNB 124 may connect to the AMF 114 via an Ng interface. Each base station manages and supports at least one cell. For example, base station gNB124 may be configured to manage and support cell 1, cell 2, and cell 3.

[0024] The gNB 124 may include a central unit (CU) and at least one distributed unit (DU). The CU and DU may be co-located or separated into different locations. The CU and DU may be connected via an F1 interface. Alternatively, for an eNB capable of connecting to a 5G network, it may also be similarly separated into a CU and at least one DU, which are referred to as ng-eNB-CU and ng-eNB-DU, respectively. The ng-eNB-CU and ng-eNB-DU may be connected via a W1 interface.

[0025] The wireless communication network 100 may include one or more tracking areas. A tracking area may include a set of cells managed by at least one base station. For example, tracking area 1, labeled as 140, includes cell 1, cell 2, and cell 3, and may further include more cells managed by other base stations and not shown in FIG. 1 . The wireless communication network 100 may also include at least one UE 160. The UE may select a cell from among multiple cells supported by the base station to communicate with the base station over an over-the-air (OTA) wireless communication interface and resources, and as the UE 160 moves within the wireless communication network 100, the UE 160 may reselect a cell for communication. For example, the UE 160 may initially select cell 1 to communicate with the base station 124, and the UE 160 may then reselect cell 2 at some later point in time. The cell selection or reselection by the UE 160 may be based on the wireless signal strength / quality of various cells and other factors.

[0026] The wireless communication network 100 may be implemented as, for example, a 2G, 3G, 4G / LTE, or 5G cellular communication network. Correspondingly, the base stations 122 and 124 may be implemented as 2G base stations, 3G NodeBs, LTE eNBs, or 5G NR gNBs. The UE 160 may be implemented as a mobile or fixed communication device capable of accessing the wireless communication network 100. The UE 160 may include, but is not limited to, a mobile phone, a laptop computer, a tablet, a personal digital assistant, a wearable device, an Internet of Things (IoT) device, an MTC / eMTC device, a distributed remote sensor device, a roadside assistance device, an XR device, and a desktop computer. The UE 160 may also be generally referred to as a wireless communication device or a wireless terminal. The UE 160 may support sidelink communication to another UE via a PC5 interface.

[0027] Although the following description focuses on a cellular wireless communication system, as shown in Figure 1, the underlying principles are applicable to other types of wireless communication systems for paging wireless devices. These other wireless systems may include, but are not limited to, Wi-Fi, Bluetooth, ZigBee, and WiMax networks.

[0028] 2 illustrates an example of an electronic device 200 for implementing a network base station (e.g., a radio access network node), a core network (CN), and / or operations and maintenance (OAM). Optionally, in one implementation, the exemplary electronic device 200 may include radio transmit / receive (Tx / Rx) circuitry 208 for transmitting / receiving communications with UEs and / or other base stations. Optionally, in one implementation, the electronic device 200 may also include network interface circuitry 209 (e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols) for allowing the base station to communicate with other base stations and / or the core network. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with an operator, etc.

[0029] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more of processors 221 to perform the functions of a network node. Parameters 228 may include parameters to support execution of instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0030] FIG. 3 illustrates an example of an electronic device for implementing a terminal device 300 (e.g., user equipment (UE)). The UE 300 may be a mobile device located in a vehicle, such as a smartphone or a mobile communications module. The UE 300 may include some or all of the following: a communications interface 302, system circuitry 304, an input / output interface (I / O) 306, display circuitry 308, and storage 309. The display circuitry may include a user interface 310. The system circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuitry. The system circuitry 304 may be implemented with, for example, one or more system-on-chip (SOC), application-specific integrated circuits (ASIC), discrete analog and digital circuits, and other circuitry. The system circuitry 304 may be part of the implementation of any desired functionality within the UE 300. In that regard, system circuitry 304 may include, by way of example, logic to facilitate music and video decoding and playback, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback, application launching, user input acceptance, saving and retrieving application data, establishing, maintaining, and terminating cellular phone calls or data connections for, by way of example, Internet connectivity, establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections, and displaying related information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0031] 3, the communications interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316, which handles the transmission and reception of signals through one or more antennas 314. The communications interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver including modulation / demodulation circuitry, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving through one or more antennas or (for some devices) over a physical (e.g., wired) medium. The transmitted and received signals may conform to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As one specific example, communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, Wi-Fi, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below are also applicable to other wireless communication technologies, whether arising from the 3rd Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partnership or standards body.

[0032] 3 , the system circuitry 304 may include one or more processors 321 and memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to perform desired functionality for the UE 300. The parameters 328 may provide and define configuration and operation options for the instructions 326. The memory 322 may store any BT, Wifi, 3G, 4G, 5G, or other data that the UE 300 transmits or receives through the communication interface 302. In various implementations, system power for the UE 300 may be supplied by a power storage device, such as a battery or a converter. (Data burst arrival time adjustment and regulation)

[0033] In a wireless network, radio resources are shared by various devices, such as user equipment. Radio resources may include time resources and spectrum resources. Delivery or transmission of user data needs to go through various network elements. For example, with respect to downlink traffic, data may start from a data network or application, proceed to a core network, a radio access network (RAN), and then be delivered by a base station to a UE over an air interface (e.g., a Uu interface). With respect to uplink traffic, data may start from a data network or application running on a UE and be delivered over an air interface to a base station, where the data will be further routed by the RAN to the core network. To ensure smooth data transmission and improve network performance, coordination efforts are needed between these various network elements.

[0034] For example, a base station may have resource constraints such that only certain resources can be used or allocated to a UE. For example, data may only be transmitted to a UE at certain times. In this case, it is desirable for the core network to deliver data to the RAN in a timely manner that satisfies the resource constraints at the base station. This means that when the base station receives data from the core network, it may have radio resources readily available or with minimal delay (e.g., below a threshold) so that the data can be transmitted to the UE and meet the delay requirements. Otherwise, the base station may need to buffer the data until the moment resources become available, which would lead to excessive transmission delays and also increase buffering costs.

[0035] To achieve this goal, the base station may coordinate data burst arrival times and therefore communicate with the core network so that the data burst arrival times match resource requirements at the base station side. The burst arrival times may be adjusted to be aligned with the radio resource pattern. In this disclosure, various embodiments are described for coordinating burst arrival time information between various network elements in a wireless network. Details regarding these embodiments are described below. (Embodiment 1: Downlink Burst Arrival Time Adjustment Trigger by Base Station Without CN Capability Indication)

[0036] In this embodiment, the base station initiates a request to the core network to adjust the downlink burst arrival time.

[0037] FIG. 4 shows exemplary message flows and interactions between various network elements, including a base station, a core network, a UE, and a data network or application running within the application layer, to implement DL burst arrival time adjustment. Step 1: This step is optional. A core network node, such as a core network or an Access and Mobility Management Function (AMF), may send a downlink (DL) burst scheduling configuration for the UE's DL data bursts to the base station. The DL burst scheduling configuration may include a DL burst arrival time and may further include a periodicity for the DL bursts. Step 2: The base station may determine whether the DL burst scheduling arrangement is aligned with its own DL resource availability or the DL resources that can be allocated to the UE. The base station may determine to adjust the DL burst arrival time so that the DL burst arrival time can be better aligned with the DL resource availability. The base station may send a DL burst arrival time adjustment indication to the core network (e.g., AMF) via signaling associated with the UE. The DL burst arrival time adjustment indication may include at least one of the following: Recommended DL burst arrival time, Recommended periodicity of DL bursts, The suggested DL burst arrival time offset relative to the current DL burst arrival time, Recommended DL burst arrival start time and recommended DL burst duration; A recommended DL burst arrival time pattern that matches the available downlink radio resources (e.g., Uu interface resources) for the UE; Cell-specific time division duplex (TDD) downlink time domain patterns, Cell-specific TDD uplink and downlink time domain patterns, or Instructions for removing DL burst arrival time related configurations; An indication that the current radio resource configuration does not match the current traffic pattern of the DL burst.

[0038] The DL burst arrival time pattern may be represented as a sequence of {DL burst arrival time, duration, periodicity}, for example, {start time 1, time duration 1, periodicity 1}, {start time 2, time duration 2, periodicity 2}.

[0039] The DL burst arrival time related configuration may include at least one of: a DL burst arrival start time, a DL burst periodicity.

[0040] The DL burst arrival start time and DL burst duration may be represented as a sequence of {start time, time duration}.

[0041] A cell-specific TDD downlink time domain pattern or a cell-specific uplink / downlink TDD configuration is used to indicate the quasi-periodic DL availability time. Figure 5 shows an example cell-specific TDD uplink and downlink time domain pattern. As shown in Figure 5, there are major cycles with periodicity P = 5 ms (milliseconds). In each major cycle, there are two minor cycles with periodicity P1 = 3 ms and P2 = 3 ms. The arrangement of downlink time allocation and uplink allocation is shown in each minor cycle.

[0042] In one implementation, the DL burst arrival time related configuration may include a DL arrival time and a periodicity for the DL burst. Step 3: Upon receiving the DL burst arrival time adjustment indication, if the core network agrees with the recommended DL burst arrival time, the core network may send a DL burst arrival time adjustment confirmation to the base station via signaling associated with the UE to confirm the DL burst arrival time adjustment recommended by the base station. The DL burst arrival time adjustment confirmation may include at least one of the following: DL burst arrival time, periodicity of DL bursts, DL burst arrival time offset relative to the current DL burst arrival time, DL burst arrival start time and DL burst duration, a DL burst arrival time pattern that matches the available downlink radio resources for the UE, or Instructions for removing DL burst arrival time related configurations.

[0043] As an example, the DL burst arrival time pattern may be represented as a sequence of {DL burst arrival time, periodicity}.

[0044] In one implementation, the DL burst arrival time related configuration may include a DL arrival time and a periodicity for the DL burst. Step 4: For DL bursts, the data network (DN) or application (APP) running at the application layer drives the data transmission, and the core network may therefore also send a DL burst arrival time adjustment indication to the DN or APP to trigger data transmission time adjustment at the DN / APP side so that the DL burst arrival time can meet the recommended value. Step 5: The core network may also send a DL burst arrival time adjustment indication to the UE via a non-access stratum (NAS) message. The UE may determine a 5G system (5GS) egress time for the DL data based on the DL burst arrival time adjustment indication. (Embodiment 2: Downlink Burst Arrival Time Adjustment Trigger by Base Station with CN Capability Indication)

[0045] In this embodiment, the core network may indicate to the base station whether DL burst arrival time adjustment is supported, or the base station may obtain through OAM whether DL burst arrival time adjustment is supported in the core network. Then, based on this indication, the base station may initiate a request to the core network to adjust the downlink burst arrival time.

[0046] FIG. 6 shows exemplary message flows and interactions between various network elements, including a base station, a core network, a UE, and a data network or application running within the application layer, to implement DL burst arrival time adjustment. Step 1: A core network node, such as a core network or AMF, may send a downlink (DL) burst scheduling configuration for a UE's DL data bursts to a base station. The DL burst scheduling configuration may include a DL burst arrival time and may further include a periodicity for the DL bursts. The core network may also send an indication to the base station indicating whether DL burst arrival time adjustment is supported. The granularity of the indication may include the UE level, the base station level, or the core network level. Step 2: The base station may determine whether the DL burst scheduling arrangement is aligned with the base station's own DL resource availability or the DL resources that can be allocated to the UE. The base station may determine to adjust the DL burst arrival time so that the DL burst arrival time can better align with the DL resource availability. The base station may send a DL burst arrival time adjustment indication to the core network (e.g., AMF) via signaling associated with the UE. The DL burst arrival time adjustment indication may include at least one of the following: Recommended DL burst arrival time, Recommended periodicity of DL bursts, The suggested DL burst arrival time offset relative to the current DL burst arrival time, Recommended DL burst arrival start time and recommended DL burst duration; A recommended DL burst arrival time pattern that matches the available downlink radio resources (e.g., Uu interface resources) for the UE; Cell-specific time division duplex (TDD) downlink time domain patterns, Cell-specific TDD uplink and downlink time domain patterns, An instruction to remove DL burst arrival time related configuration, or An indication that the current radio resource configuration does not match the current traffic pattern of the DL burst. Step 3: Unlike embodiment 1, upon receiving the DL burst arrival time adjustment indication, the core network does not need to send a response or confirmation back to the base station because the core network has already indicated to the base station that such adjustment is supported.

[0047] For DL bursts, the data network (DN) or application (APP) that initiates at the application layer drives the data transmission. The core network can send a DL burst arrival time adjustment indication to the DN or APP to trigger data transmission time adjustment at the DN / APP side so that the DL burst arrival time can match the recommended value. Step 4: The core network may further send a DL burst arrival time adjustment indication to the UE via the NAS message. The UE may determine a 5GS egress time for the DL data based on the DL burst arrival time adjustment indication. (Embodiment 3: Uplink burst arrival time adjustment triggered by base station without CN capability indication)

[0048] In this embodiment, the base station initiates a request to the core network to adjust the uplink burst arrival time. Before sending this request, the base station may not know whether the core network supports such an adjustment. Therefore, the base station expects confirmation from the core network to activate the adjustment.

[0049] FIG. 7 illustrates exemplary message flows and interactions between various network elements, including a base station, a core network, a UE, and a data network or application running within the application layer, to implement UL burst arrival time adjustment. Step 1: This step is optional. A core network node, such as a core network or AMF, may send a downlink (UL) burst scheduling configuration for the UE's UL data bursts to the base station. The UL burst scheduling configuration may include a UL burst arrival time and may further include a periodicity for the UL bursts. Step 2: The base station may determine whether the UL burst scheduling arrangement is aligned with the base station's own UL resource availability or with the UL resources that can be allocated to the UE. The base station may determine to adjust the UL burst arrival time so that the UL burst arrival time can better align with the UL resource availability. The base station may send a UL burst arrival time adjustment indication to the core network (e.g., AMF) via signaling associated with the UE. The UL burst arrival time adjustment indication may include at least one of the following: Recommended UL burst arrival time, Recommended periodicity of UL bursts, The recommended UL burst arrival time offset relative to the current UL burst arrival time, - Recommended UL burst arrival start time and recommended UL burst duration; A recommended UL burst arrival time pattern that matches the available uplink radio resources for the UE; Cell-specific time division duplex (TDD) uplink time domain patterns, Cell-specific TDD uplink and downlink time domain patterns, An instruction to remove UL burst arrival time related configuration, or An indication that the current radio resource configuration does not match the current traffic pattern of the UL burst.

[0050] The UL burst arrival time pattern may be represented as a sequence of {UL burst arrival time, duration, periodicity}, e.g., {start time 1, time duration 1, periodicity 1}, {start time 2, time duration 2, periodicity 2}.

[0051] The UL burst arrival start time and UL burst duration may be represented as a sequence of {start time, time duration}.

[0052] In one implementation, the UL burst arrival time related configuration may include a UL arrival time and a periodicity for the UL burst. Step 3: Upon receiving the UL burst arrival time adjustment indication from the base station, if the core network agrees on the recommended UL burst arrival time, the core network may send an UL burst arrival time adjustment confirmation to the base station via signaling associated with the UUE to confirm the UL burst arrival time adjustment recommended by the base station. The UL burst arrival time adjustment confirmation may include at least one of the following: UL burst arrival time, · Periodicity of UL bursts, UL burst arrival time offset relative to the current UL burst arrival time, UL burst arrival start time and UL burst duration, a UL burst arrival time pattern that matches the available downlink radio resources for the wireless device; or Instructions for removing UL burst arrival time related configurations.

[0053] In one implementation, the UL burst arrival time related configuration may include a UL arrival time and a periodicity for the UL burst. Step 4: The core network may further send a UL burst arrival time adjustment indication to the UE, for example, via a NAS message. Step 5: For UL bursts, a data network (DN) or an application (APP) running at the application layer drives data transmission. The APP may include applications running on the UE, such as an online meeting APP, a video streaming APP, etc. The UE may send a UL burst transmission time adjustment indication to the DN or APP to trigger data transmission time adjustment at the DN / APP side so that the UL burst arrival time can match the recommended value. (Embodiment 4: Uplink burst arrival time adjustment triggered by base station with CN capability indication)

[0054] In this embodiment, the core network may indicate to the base station whether UL burst arrival time adjustment is supported, and then, based on this indication, the base station may initiate a request to the core network to adjust the uplink burst arrival time.

[0055] FIG. 8 illustrates exemplary message flows and interactions between various network elements, including a base station, a core network, a UE, and a data network or application running within the application layer, to implement UL burst arrival time adjustment. Step 1: The UE may transmit at least one of the UL burst arrival time, the periodicity for the UL burst, and the UL burst arrival time adjustment support indication to the core network, for example, via a NAS message. In one implementation, the UL burst arrival time adjustment support indication may be implicitly indicated with a range of UL burst arrival times, i.e., the UE supports UL bursts arriving within this specified range. Step 2: A core network node, such as a core network or AMF, may send an UL burst scheduling configuration for the UE's UL data bursts to the base station. The UL burst scheduling configuration may include an UL burst arrival time and may further include a periodicity for the UL bursts. The core network may also send an indication to the base station indicating whether UL burst arrival time adjustment is supported. The granularity of the indication may include the UE level, the base station level, or the core network level. Step 3: The base station may determine whether the UL burst scheduling arrangement is aligned with the base station's own UL resource availability or with the UL resources that can be allocated to the UE. The base station may determine to adjust the UL burst arrival time so that the UL burst arrival time better aligns with the UL resource availability. The base station may send a UL burst arrival time adjustment indication to the core network (e.g., AMF) via signaling associated with the UE. The UL burst arrival time adjustment indication may include at least one of the following: Recommended UL burst arrival time, Recommended periodicity of UL bursts, The recommended UL burst arrival time offset relative to the current UL burst arrival time, - Recommended UL burst arrival start time and recommended UL burst duration; A recommended UL burst arrival time pattern that matches the available uplink radio resources for the UE; Cell-specific time division duplex (TDD) uplink time domain patterns, Cell-specific TDD uplink and downlink time domain patterns, An instruction to remove UL burst arrival time related configuration, or An indication that the current radio resource configuration does not match the current traffic pattern of the UL burst.

[0056] The UL burst arrival time pattern may be represented as a sequence of {UL burst arrival time, duration, periodicity}, e.g., {start time 1, time duration 1, periodicity 1}, {start time 2, time duration 2, periodicity 2}.

[0057] The UL burst arrival time related configuration may include the UL arrival time and the periodicity for the UL burst.

[0058] The UL burst arrival start time and UL burst duration may be represented as a sequence of {start time, time duration}. Step 4: Unlike embodiment 1, upon receiving the UL burst arrival time adjustment indication, the core network does not need to send a response or confirmation back to the base station because the core network has already indicated to the base station that such adjustment is supported.

[0059] The core network may send a UL burst arrival time adjustment indication to the UE via a NAS message. Step 5: For UL bursts, a data network (DN) or an application (APP) running at the application layer drives data transmission. The APP may include applications running on the UE, such as an online meeting APP, a video streaming APP, etc. The UE may send a UL burst transmission time adjustment indication to the DN or APP to trigger data transmission time adjustment at the DN / APP side so that the UL burst arrival time can match the recommended value. (Embodiment 5: UE-triggered uplink burst arrival time adjustment)

[0060] In this embodiment, the UE may initiate a request to the core network to adjust the uplink burst arrival time.

[0061] FIG. 9 illustrates exemplary message flows and interactions between various network elements for one option for implementing UL burst arrival time adjustment, including a base station, a core network, a UE, and a data network or application running within the application layer. (Option 1 (shown in Figure 9))

[0062] Step 1: The UE may have a recommended UL burst transmission configuration, or the UE may already have a UL burst transmission configuration. The UE may inform the core network of its current UL configuration or its preferred UL burst transmission configuration, for example, via a NAS message. The UE may include at least one of the following in the message: UL burst arrival time, or periodicity for UL bursts.

[0063] Alternatively, or in addition, the UE may send a UL burst arrival time adjustment indication to the core network (e.g., AMF) via a NAS message. The UL burst arrival time adjustment indication may include at least one of the following: Recommended UL burst arrival time, Recommended periodicity of UL bursts, The recommended UL burst arrival time offset relative to the current UL burst arrival time, - Recommended UL burst arrival start time and recommended UL burst duration; A recommended UL burst arrival time pattern that matches the available uplink radio resources for the UE; Cell-specific time division duplex (TDD) uplink time domain patterns, Cell-specific TDD uplink and downlink time domain patterns, An instruction to remove UL burst arrival time related configuration, or An indication that the current radio resource configuration does not match the current traffic pattern of the UL burst.

[0064] The UL burst arrival time related configuration may include the UL arrival time and the periodicity for the UL burst. Step 2: Upon receiving the UL burst arrival time adjustment indication from the UE, if the core network agrees on the recommended UL burst arrival time, the core network may send a UL burst arrival time adjustment confirmation to the UE via a NAS message to confirm the UL burst arrival time adjustment recommended by the UE. The UL burst arrival time adjustment confirmation may include at least one of the following: UL burst arrival time, · Periodicity of UL bursts, UL burst arrival time offset relative to the current UL burst arrival time, UL burst arrival start time and UL burst duration, a UL burst arrival time pattern that matches the available downlink radio resources for the wireless device; or Instructions for removing UL burst arrival time related configurations. Step 3: The core network may send an UL burst arrival time adjustment indication to the base station so that the base station may configure / reconfigure its UL resources for the UE accordingly. Step 4: For UL bursts, a data network (DN) or an application (APP) running at the application layer drives data transmission. The APP may include applications running on the UE, such as an online meeting APP, a video streaming APP, etc. The UE may send a UL burst transmission time adjustment indication to the DN or APP to trigger data transmission time adjustment at the DN / APP side so that the UL burst arrival time can match the recommended value.

[0065] In option 1, the UE sends the UL burst arrival time adjustment indication directly to the core network using a NAS message. Alternatively, in another option, the UE may use a base station as a relay to send the UL burst arrival time adjustment indication to the core network. Further details are described in option 2. (Option 2)

[0066] Step 1: The UE may have a recommended UL burst transmission configuration, or the UE may already have a UL burst transmission configuration. The UE may inform the base station of its current configuration or its preferred UL burst transmission configuration via an AS message, such as a Medium Access Control - Control Element (MAC CE) message, a UE-dedicated Radio Resource Control (RRC) message, etc. The UE may include at least one of the following in the message: UL burst arrival time, or periodicity for the UL bursts.

[0067] Alternatively or additionally, the UE may send a UL burst arrival time adjustment indication to the base station, which is similar to option 1 of this embodiment. Step 2: The base station may forward the message from the UE in step 1 to the core network via signaling associated with the UE. Step 3: If the core network agrees on the recommended UL burst arrival time, it may send a UL burst arrival time adjustment confirmation to the base station via signaling associated with the UE. Details regarding the confirmation may be found in Option 1 of this embodiment. Step 4: The base station forwards the UL burst arrival time adjustment confirmation to the UE via an AS message, such as a MAC CE message, a UE-specific RRC message, etc. Step 5: For UL bursts, a data network (DN) or an application (APP) running at the application layer drives data transmission. The APP may include applications running on the UE, such as an online meeting APP, a video streaming APP, etc. The UE may send a UL burst transmission time adjustment indication to the DN or APP to trigger data transmission time adjustment at the DN / APP side so that the UL burst arrival time can match the recommended value.

[0068] By way of example, the UL burst arrival time may include at least one of the following: The time offset relative to the currently used UL burst arrival time, a time offset relative to the current time of the wireless communication system when the second message is transmitted; or 5GS absolute time with at least one of the following: o System Frame Number (SFN), o Subframe number, o slot number, o Minislot number, o Coordinated Universal Time (UTC) time, or o The duration of time elapsed since a predefined time opportunity. (Embodiment 6:)

[0069] In current wireless networks, to reduce UE power consumption, connected mode discontinuous reception (CDRX) can be configured, which applies to both periodic and aperiodic traffic. In CDRX mode, the on duration start opportunity is calculated as follows: [Table 1] or [Table 2]

[0070] In the above equations (1) and (2), the periodicity for periodic traffic is not taken into account.

[0071] When CDRX is used to match the periodicity of periodic traffic and the above formula is used, and the DRX cycle (i.e., drx-LongCycle or drx-ShortCycle) in the formula is not an integer multiple of 10,240 ms (milliseconds), there is a mismatch between the periodicity of the periodic traffic and the DRX on duration cycle due to system frame number (SFN) wraparound. This issue can cause the DRX cycle to be out of sync with the arrival time of data traffic, e.g., Extended Reality (XR) traffic, as a result of SFN wraparound. This issue is further illustrated in Figure 10. In Figure 10, there is periodic downlink XR traffic. From SFN 0-1023, the periodicity of the XR traffic matches the DRX cycle, which is 70 ms. However, when the SFN is reset from 1023 to 0 (i.e., SFN wraparound), the periodicity of the XR traffic does not match the DRX cycle. This will lead to DL transmission failures or transmission delays for the XR service.

[0072] In this embodiment, to solve the SFN wraparound problem, the start opportunity of a CDRX on duration can be indicated by the network (e.g., radio access network or core network), and the start of a subsequent CDRX on duration can be determined based on a periodicity shift relative to the start of a previous adjacent (nearby) CDRX on duration.

[0073] In one implementation, after the CDRX is configured, the Medium Access Control (MAC) entity may consider the Nth CDRX On Duration to start at one of the following: SFN*10+subframe=[(SFNstart time×10+subframe start time)+ceil(N×periodicity)]modulo10240 (3)

[0074] SFNstart time and subframe start time are expressed in terms of the SFN number and subframe number of the first on-duration start opportunity when the CDRX is (re)configured, respectively; or (numberOfSlotsPerFrame × SFN + slot number within the frame) = [(numberOfSlotsPerFrame × SFNstart time + slotstart time) + ceil(N × periodicity × numberOfSlotsPerFrame / 10)] modulo(1024 × numberOfSlotsPerFrame) (4)

[0075] SFNstart time and slotstart time are, respectively, the SFN and slot number of the first on-duration start opportunity when the CDRX is (re)configured; or (numberOfSlotsPerFrame × SFN × numberOfSymbolsPerSlot + slot number within frame × numberOfSymbolsPerSlot + symbol number within frame) = [(numberOfSlotsPerFrame × SFNstart time × numberOfSymbolsPerSlot + slotstart time × numberOfSymbolsPerSlot + symbolstart time) + ceil(N × periodicity × numberOfSlotsPerFrame × numberOfSymbolsPerSlot / 10)] modulo(1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) (5)

[0076] The SFNstart time, slotstart time, and symbolstart time are respectively the SFN, slot, and symbol start time of the first on-duration start opportunity when the CDRX is (re)configured.

[0077] Ceil(X) is the ceiling operation to obtain the smallest integer value greater than or equal to X. In one implementation, the Ceil() operation can be removed from the equation if no non-integer CDRX periodicity values are configured.

[0078] In one implementation, the Ceil() operation may be replaced by FLOOR(), where FLOOR(X) is a floor operation to obtain the largest integer value less than or equal to X. (Embodiment 7:)

[0079] An XR service may be a video streaming service with fixed photo frames (e.g., H.264 frames), which may include I-frames, P-frames, and B-frames. FIG. 11 shows exemplary application frames and their mapping to IP packets. As shown in FIG. 11, each application frame (e.g., photo frame) may be mapped to multiple IP packets. For example, I-frame I1 is mapped to IP packet I2. 11 -I 1n B-frame B2 is mapped to IP packet B 21 -B 2m As shown in Figure 11, the application frame I1-B 12 form an Application Data Unit (ADU).

[0080] Because different picture frames are coded / decoded using different coding / decoding schemes, the Quality of Service (QoS) priorities or importance of different frames are also different. For example, the decoding timeline and presentation timeline for an ADU such as that shown in FIG. 11 are shown in FIG. 12.

[0081] I-frames are key frames; they store / transmit all of the data needed to display that frame. Typically, I-frames are interspersed within compressed video along with P-frames and B-frames. The more I-frames there are, the better the video will be; however, I-frames contain the most bits and therefore take up more space on the storage medium and consume more radio resources to deliver them over the Uu interface. P-frames are delta frames, meaning they only contain data that has changed from the previous I-frame (such as color or content changes), so they rely on the previous I-frame to fill in the majority of their data. B-frames are also delta frames; they contain only data that changes from the previous frame and is different from the data in the next frame. Therefore, B-frames rely on the frames that precede and follow them to fill in the majority of their data.

[0082] During ADU decoding, different application frames have different QoS priorities or importance levels, and considering that dependencies exist between different frames, it is beneficial to distinguish these frames within the RAN and weight / take into account the differences for radio resource scheduling.

[0083] In one implementation, one XR service (e.g., one video streaming) is mapped to one QoS flow, which can indicate a video frame sequence (e.g., a PDU set sequence based on a PDU set sequence number if one video frame is mapped to one PDU set). To distinguish the QoS priority or importance level of PDU sets within one QoS flow, there are two options: (Option 1: QoS subflow is introduced)

[0084] A QoS subflow may also be named a "sub-QoS flow," which is used to distinguish different QoS attributes (eg, priority levels) within the same QoS flow.

[0085] When QoS subflows are introduced, the gNB may map one QoS flow to one data radio bearer (DRB) and then map different QoS subflows of the same DRB to different logical channels (LCs), as shown in Figure 13. In Figure 13, the QoS flow ID is associated with the DRB identification in the DRB configuration, and the DRB identification is associated with the QoS subflow ID or QoS subflow priority in the RLC-BearerConfig. Thus, one QoS flow may be mapped to different logical channels.

[0086] In one implementation, user plane data PDUs are routed from a General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) to a Service Data Adaptation Protocol (SDAP) entity, then from the SDAP entity to a Packet Data Convergence Protocol (PDCP) entity, then from the PDCP entity to a Radio Link Control (RLC) entity, and then from the RLC entity to a Medium Access Control (MAC) entity. Radio resource scheduling may be performed in the MAC entity.

[0087] Considering that one PDCP entity is associated with a DRB, if different QoS subflows of the same DRB are mapped to different logical channels, the PDCP entity should be aware of the QoS subflow information so that it can appropriately route PDCP PDUs with different QoS subflows to different logical channels.

[0088] In order for the PDCP entity to be aware of the QoS subflow information, the QoS subflow ID or QoS subflow priority should be included in the SDAP PDU (e.g., by adding an SDPA header containing the QoS subflow ID and / or QoS subflow priority fields). (Option 2: Only the priority level or importance indication is introduced in the GTP-U header)

[0089] In one implementation, user plane data PDUs are routed from GTP-U (e.g., in DLPDU Session Information (PDU type 0) format) to the SDAP entity, then from the SDAP entity to the PDCP entity, then from the PDCP entity to the RLC entity, and then from the RLC entity to the MAC entity. Radio resource scheduling is performed in the MAC entity.

[0090] Considering that one PDCP entity is associated with a DRB, if no QoS subflow is introduced, one DRB is usually mapped to one logical channel.

[0091] If a priority level or importance indication is introduced in the GTP-U header so that the MAC entity can recognize the priority level or importance indication information regarding radio resource scheduling, the priority level or importance indication should be available in the MAC entity. This can be implemented using one of the following solutions: Solution 1:

[0092] A priority level or importance indication is included in the XnAP and / or F1AP user plane packet header (e.g., GTP-U header) to deliver priority level or importance indication information between different RAN network elements (e.g., between gNBs and / or between a gNB-CU and a gNB-DU). In the RAN network elements, the priority level or importance indication delivery can be based on the gNB implementation and / or the UE implementation. Solution 2:

[0093] The priority level or importance indication is included in the SDAP data PDU (e.g., by adding an SDPA header including a QoS subflow ID or QoS subflow priority field), then included in the PDCP data PDU (e.g., the priority level or importance indication is included in the header of the PDCP data PDU), and then included in the RLC data PDU (e.g., the priority level or importance indication is included in the header of the RLC PDU).

[0094] The above description and accompanying drawings provide specific exemplary embodiments and implementations. However, the described subject matter can be embodied in a variety of different forms, and therefore, it is intended that the covered or claimed subject matter be construed as not limited to any exemplary embodiments set forth herein. A reasonably broad scope for the claimed or covered subject matter is intended. Among other things, for example, the subject matter may be embodied as a method, device, component, system, or non-transitory computer-readable medium for storing computer code. Thus, embodiments may take the form of, for example, hardware, software, firmware, a storage medium, or any combination thereof. For example, the method embodiments described above may be implemented by a component, device, or system including a memory and a processor by executing computer code stored in the memory.

[0095] Throughout this specification and the claims, terms may have nuanced meanings that are suggested or implied in context beyond their explicitly stated meaning. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, it is intended that claimed subject matter include combinations of example embodiments, whether in whole or in part.

[0096] Generally, terminology can be understood, at least in part, from its use in context. For example, terms such as "and," "or," or "and / or," as used herein, can include a variety of meanings that may depend, at least in part, on the context in which such terms are used. Typically, "or," when used to relate a list such as "A, B, or C," is intended to mean "A, B, and C," which is used herein in an inclusive sense, as well as "A, B, or C," which is used herein in an exclusive sense. Additionally, as used herein, the term "one or more" can be used to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense, depending, at least in part, on the context. Similarly, terms such as "a," "an," or "the" can be understood to convey a singular usage or to convey a plural usage, depending, at least in part, on the context. Additionally, the term "based on" may be understood as not intended to convey a necessarily exclusive set of factors, but instead may allow for the existence of additional factors not necessarily explicitly described, again depending at least in part on the context.

[0097] References to features, advantages, or similar language throughout this specification do not imply that all of the features and advantages that can be realized using the present solution should or are included in any single implementation thereof. Rather, language referring to features and advantages is understood to mean that the specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of features and advantages and similar language throughout this specification may, but do not necessarily, refer to the same embodiment.

[0098] Furthermore, the described features, advantages, and characteristics of the solution may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that the solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in some embodiments that may not be present in all embodiments of the solution.

Claims

1. 1. A method for wireless communication implemented by a first network element in a wireless communication system, the method comprising: determining, based on downlink (DL) resource availability, that a DL burst arrival time of a DL burst for a wireless device needs to be adjusted; transmitting a first message to a core network in the wireless communication system; Including, the first message comprises a DL burst arrival time adjustment indication for the wireless device, the DL burst arrival time adjustment indication indicating that a DL burst arrival time of a DL burst for the wireless device needs to be adjusted.

2. The DL burst arrival time adjustment instruction is Recommended DL burst arrival time, the recommended periodicity of said DL bursts; the recommended DL burst arrival time offset relative to the current DL burst arrival time; Recommended DL burst arrival start time and recommended DL burst duration; a recommended DL burst arrival time pattern that matches available downlink radio resources for the wireless device; Cell-specific time division duplex (TDD) downlink time domain patterns; Cell-specific TDD uplink and downlink time domain patterns, or An indication that the current radio resource configuration does not match the current traffic pattern of said DL burst. The method of claim 1 , comprising at least one of:

3. The method of claim 1 or 2, wherein the first message comprises a signaling message associated with a user equipment (UE).

4. and receiving a second message from the core network in response to the first message, the second message comprising a DL burst arrival time confirmation, the DL burst arrival time confirmation comprising: DL burst arrival time, the periodicity of the DL bursts; the DL burst arrival time offset relative to the current DL burst arrival time, DL burst arrival start time and DL burst duration; a DL burst arrival time pattern that matches available downlink radio resources for the wireless device; or Instructions for deleting DL burst arrival time related configuration The method according to claim 1 or 2, comprising at least one of:

5. Before transmitting the first message to the core network, the method further comprises: receiving, from the core network, an indicator indicating whether DL burst arrival time adjustment is supported by the core network; transmitting the first message to a core network; 2. The method of claim 1, comprising transmitting the first message to the core network in response to the indicator that the DL burst arrival time adjustment is supported by the core network.

6. Receiving the first message by the core network includes: transmitting the DL burst arrival time adjustment indication to an entity that provides the DL burst for the wireless device, the entity comprising at least one of a data network or an application layer; or transmitting the DL burst arrival time adjustment indication to the wireless device; The method of claim 1 , further comprising: triggering the core network to implement at least one of:

7. transmitting the first message to the core network includes:

2. The method of claim 1, comprising transmitting the first message to an Access and Mobility Management Function (AMF) of the core network via UE associated signaling.

8. The first network element comprises a base station, the base station comprising: gNodeB (gNB), eNodeB (eNB), ng-eNodeB (ng-eNB), or Node B The method of claim 1 , comprising one of:

9. 1. A method for wireless communication implemented by a core network node in a wireless communication system, the method comprising: receiving a first message from a base station in the wireless communication system; 11. The method of claim 10, wherein the first message comprises a DL burst arrival time adjustment indication for a wireless device, the DL burst arrival time adjustment indication indicating that a DL burst arrival time of a DL burst for the wireless device needs to be adjusted.

10. The DL burst arrival time adjustment instruction is Recommended DL burst arrival time, the recommended periodicity of said DL bursts; the recommended DL burst arrival time offset relative to the current DL burst arrival time; Recommended DL burst arrival start time and recommended DL burst duration; a recommended DL burst arrival time pattern that matches available downlink radio resources for the wireless device; Cell-specific time division duplex (TDD) downlink time domain patterns; Cell-specific TDD uplink and downlink time domain patterns, or An indication that the current radio resource configuration does not match the current traffic pattern of said DL burst. The method of claim 9 , comprising at least one of:

11. 11. The method of claim 9, further comprising transmitting the DL burst arrival time adjustment indication to an entity that provides the DL burst for the wireless device, the entity comprising at least one of a data network or an application layer.

12. The method of claim 9 or 10, further comprising transmitting the DL burst arrival time adjustment indication to the wireless device.

13. Before receiving the first message from the base station, the method includes:

10. The method of claim 9, further comprising transmitting an indicator to the base station indicating whether DL burst arrival time adjustment is supported by the core network node.

14. transmitting to the base station a second message in response to the first message, the second message comprising a DL burst arrival time confirmation, the DL burst arrival time confirmation comprising: DL burst arrival time, the periodicity of the DL bursts; the DL burst arrival time offset relative to the current DL burst arrival time, DL burst arrival start time and DL burst duration; a DL burst arrival time pattern that matches available downlink radio resources for the wireless device; or Instructions for deleting DL burst arrival time related configuration The method of claim 13 , comprising at least one of:

15. The method of claim 9 , wherein the core network node comprises an AMF.

16. 1. A method for wireless communication implemented by a first network element in a wireless communication system, the method comprising: determining, based on uplink (UL) resource availability, that an UL burst arrival time of an UL burst for a wireless device needs to be adjusted; transmitting a first message to a core network in the wireless communication system; Including, The method, wherein the first message comprises a UL burst arrival time adjustment indication for the wireless device.

17. The UL burst arrival time adjustment indication is Recommended UL burst arrival time, the recommended periodicity of said UL bursts; a recommended UL burst arrival time offset relative to the current UL burst arrival time; Recommended UL burst arrival start time and recommended UL burst duration; a recommended UL burst arrival time pattern that matches available uplink radio resources for the wireless device; Cell-specific time division duplex (TDD) uplink time domain patterns; Cell-specific TDD uplink and downlink time domain patterns, or an indication that the current radio resource configuration does not match the current traffic pattern of said UL burst; 17. The method of claim 16, comprising at least one of:

18. and receiving a second message from the core network in response to the first message, the second message comprising an UL burst arrival time confirmation, the UL burst arrival time confirmation comprising: UL burst arrival time, the periodicity of the UL bursts; UL burst arrival time offset relative to the current UL burst arrival time, UL burst arrival start time and UL burst duration; an UL burst arrival time pattern that matches the available downlink radio resources for the wireless device; or Instructions for deleting UL burst arrival time related configuration 17. The method of claim 16, comprising at least one of:

19. Before transmitting the first message to the core network, the method further comprises: receiving, from the core network, an indicator indicating whether UL burst arrival time adjustment is supported by the core network; transmitting the first message to a core network; 17. The method of claim 16, comprising transmitting the first message to the core network in response to the indicator that the UL burst arrival time adjustment is supported by the core network.

20. Receipt of the first message by the core network triggers the core network to transmit the UL burst arrival time adjustment indication to the wireless device; 17. The method of claim 16, wherein receipt of the UL burst arrival time adjustment indication by the wireless device triggers the wireless device to transmit the UL burst arrival time adjustment indication to an entity that provides the UL burst for the wireless device, the entity comprising at least one of a data network or an application layer.

21. transmitting the first message to the core network includes:

17. The method of claim 16, comprising transmitting the first message to an AMF of the core network via UE associated signaling.

22. The first network element comprises a base station, the base station comprising: gNodeB (gNB), eNodeB (eNB), ng-eNodeB (ng-eNB), or Node B 17. The method of claim 16, comprising one of:

23. 1. A method for wireless communication implemented by a core network node in a wireless communication system, the method comprising: receiving a first message from a base station in the wireless communication system; 11. The method of claim 10, wherein the first message comprises an UL burst arrival time adjustment indication for a wireless device, the UL burst arrival time adjustment indication indicating that an UL burst arrival time of a UL burst for the wireless device needs to be adjusted.

24. The UL burst arrival time adjustment indication is Recommended UL burst arrival time, the recommended periodicity of said UL bursts; a recommended UL burst arrival time offset relative to the current UL burst arrival time; Recommended UL burst arrival start time and recommended UL burst duration; a recommended UL burst arrival time pattern that matches available uplink radio resources for the wireless device; Cell-specific time division duplex (TDD) uplink time domain patterns; Cell-specific TDD uplink and downlink time domain patterns, or an indication that the current radio resource configuration does not match the current traffic pattern of said UL burst; 24. The method of claim 23, comprising at least one of:

25. 25. The method of claim 23 or 24, further comprising transmitting the UL burst arrival time adjustment indication to the wireless device.

26. Before receiving the first message from the base station, the method includes:

24. The method of claim 23, further comprising transmitting, to the base station, a first indicator indicating whether UL burst arrival time adjustment for the wireless device is supported by the core network node.

27. Before transmitting the first indicator to the base station, the method further comprises:

27. The method of claim 26, further comprising receiving, from the wireless device, a second indicator indicating whether the UL burst arrival time adjustment is supported by the wireless device.

28. transmitting to the base station a second message in response to the first message, the second message comprising an UL burst arrival time confirmation, the UL burst arrival time confirmation comprising: UL burst arrival time, the periodicity of the UL bursts; UL burst arrival time offset relative to the current UL burst arrival time, UL burst arrival start time and UL burst duration; an UL burst arrival time pattern that matches the available downlink radio resources for the wireless device; or Instructions for deleting UL burst arrival time related configuration 24. The method of claim 23, comprising at least one of:

29. 24. The method of claim 23, wherein the core network node comprises an AMF.

30. 1. A method for wireless communication implemented by a wireless device in a wireless communication system, the method comprising: transmitting a first message to a first network element in the wireless communication system, the first message comprising an UL burst arrival time adjustment indication for the wireless device; receiving a second message from the first network element in response to the first message; Including, The method, wherein the second message comprises confirmed UL burst arrival time information.

31. The UL burst arrival time adjustment indication is the recommended UL burst arrival time, or Recommended periodicity of the UL bursts 31. The method of claim 30, comprising at least one of:

32. The confirmed UL burst arrival time information is UL burst arrival time, or Periodicity of the UL bursts and The UL burst arrival time is the time offset relative to the currently used UL burst arrival time, a time offset relative to the current time of the wireless communication system when the second message is transmitted; or The absolute value of the wireless communication system and The absolute value is System Frame Number (SFN), Subframe number, Slot number, Minislot number, Coordinated Universal Time (UTC) time, or Elapsed duration from a predefined time opportunity 31. The method of claim 30, comprising at least one of:

33. and transmitting a third message to an entity that provides the UL burst for the wireless device in response to receiving the second message, the entity comprising at least one of a data network or an application layer, the second message comprising the confirmed UL burst arrival time information; 31. The method of claim 30, wherein receipt of the third message by the entity triggers the entity to adjust UL burst transmissions for the wireless device according to the confirmed UL burst arrival time information.

34. transmitting the first message to a first network element in the wireless communication system; a MAC CE message, or RRC messages, transmitting the first message to a base station in the wireless communication system via an AS message comprising at least one of:

31. The method of claim 30, wherein receipt of the first message by the base station triggers the base station to forward the first message to the first network element.

35. The first network element AMF, or User Plane Function (UPF) 31. The method of claim 30, comprising at least one of:

36. A device for wireless communication comprising a memory for storing computer instructions and a processor in communication with said memory, said processor being configured, when executing said computer instructions, to perform a method according to any one of claims 1 to 35.

37. 36. A computer program product comprising a non-transitory computer readable program medium having stored thereon computer code which, when executed by one or more processors, causes the one or more processors to perform the method of any one of claims 1-35.

Images