Method, device and system for data transmission

Abstract

The present disclosure generally relates to a method, device and system for congestion control in a wireless network. A method performed 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 the wireless communication system, the first message including 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 for a DL burst of the wireless device needs to be adjusted.

Description

Technical Field

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

[0002] Flexible and efficient wireless transmission resource scheduling is critical in wireless communication networks. The ecosystem of wireless communication networks includes more and more applications that require low latency. These applications include vehicle-to-vehicle communication, autonomous driving, mobile gaming, etc. Data transmission between various network elements in wireless communication networks needs to be coordinated to ensure smooth data transmission that meets the latency budget and requirements, and improves overall network performance. Summary of the invention

[0003] The present disclosure relates to a method, device and system for data transmission and resource scheduling in a wireless network.

[0004] In some embodiments, a method performed by a first network element is disclosed. The method may include: determining that a DL burst arrival time for a DL burst of a wireless device needs to be adjusted based on downlink (DL) resource availability; and sending a first message to a core network in a wireless communication system, the first message including 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 for a DL burst of the wireless device needs to be adjusted.

[0005] In some embodiments, a method performed 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 including 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 for a DL burst of the wireless device needs to be adjusted.

[0006] In some embodiments, a method performed by a first network element is disclosed. The method may include: determining that an UL burst arrival time for an UL burst of a wireless device needs to be adjusted based on UL resource availability; and sending a first message to a core network in a wireless communication system, the first message including an UL burst arrival time adjustment indication for the wireless device.

[0007] In some embodiments, a method performed 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 including 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 for an UL burst of the wireless device needs to be adjusted.

[0008] In some embodiments, a method performed by a wireless device is disclosed. The method may include: sending a first message to a first network element in a wireless communication system, the first message including an UL burst arrival time adjustment indication for the wireless device; and receiving a second message from the first network element as a response to the first message, the second message including confirmed UL burst arrival time information.

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

[0010] In some embodiments, a computer program product includes a computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any method described in any embodiment.

[0011] Other aspects and alternatives of the above-described embodiments and their implementations are described in more detail in the following figures, description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 An example wireless communication network is shown.

[0013] Figure 2 An example wireless network element is shown.

[0014] Figure 3 An example user device is shown.

[0015] Figure 4 An exemplary implementation of downlink (DL) burst arrival time adjustment is shown.

[0016] Figure 5 Exemplary uplink and downlink time domain patterns are shown.

[0017] Figure 6 Another exemplary implementation of downlink (DL) burst arrival time adjustment is shown.

[0018] Figure 7-Figure 9 An exemplary implementation of uplink (UL) burst arrival time adjustment is shown.

[0019] Fig.10 Exemplary periodic DL traffic and the mismatch between DL traffic arrival time and the DRX cycle are shown.

[0020] Fig.11 An exemplary application data unit (ADU) and mapping from application frames to Internet Protocol (IP) packets are shown.

[0021] Fig.12 An exemplary decoding time sequence and presentation time sequence of an ADU is shown.

[0022] Fig.13 An exemplary QoS sub-flow mapping to logical channels is shown. DETAILED DESCRIPTION

[0023] Wireless communication network

[0024] Figure 1 An exemplary wireless communication network 100 is shown including a core network 110 and a radio access network (RAN) 120. The core network 110 also 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 described in detail in the following. Figure 1 120. The RAN 120 also includes a plurality of base stations, such as base stations 122 and 124. The base station 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 be connected to the AMF 114 via an Ng interface. Each base station manages and supports at least one cell. For example, the base station gNB 124 may be configured to manage and support cell 1, cell 2, and cell 3.

[0025] The gNB 124 may include a central unit (CU) and at least one distributed unit (DU). The CU and the DU may be collocated in the same location, or may be split in different locations. The CU and the DU may be connected via an F1 interface. Alternatively, for an eNB capable of connecting to a 5G network, it may also be similarly divided into a CU and at least one DU, referred to as ng-eNB-CU and ng-eNB-DU, respectively. The ng-eNB-CU and the ng-eNB-DU may be connected via a W1 interface.

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

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

[0028] Although the following description focuses on Figure 1 The cellular wireless communication system shown, but the basic 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.

[0029] Figure 2 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) is shown. Optionally, in one implementation, the example electronic device 200 may include a radio transmit / receive (Tx / Rx) circuit system 208 for sending / receiving communications with a UE and / or other base stations. Optionally, in one implementation, the electronic device 200 may also include a network interface circuit system 209 for enabling the base station to communicate with other base stations and / or the core network, such as optical or wired interconnection, Ethernet, and / or other data transmission media / protocols. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with an operator or the like.

[0030] The electronic device 200 may also include a system circuit system 204. The system circuit system 204 may include (multiple) processors 221 and / or memory 222. The memory 222 may include an operating system 224, instructions 226, and parameters 228. The instructions 226 may be configured for one or more processors 221 to perform the functions of a network node. The parameters 228 may include parameters for supporting the execution of the instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocations, and / or other parameters.

[0031] Figure 3 An example of an electronic device (e.g., user equipment (UE)) for implementing a terminal device 300 is shown. UE 300 may be a mobile device, such as a smart phone or a mobile communication module provided in a vehicle. UE 300 may include some or all of the following: a communication interface 302, a system circuit system 304, an input / output interface (I / O) 306, a display circuit system 308, and a storage device 309. The display circuit system may include a user interface 310. The system circuit system 304 may include any combination of hardware, software, firmware, or other logic / circuitry systems. The system circuit system 304 may be implemented, for example, with one or more systems on a chip (SoC), application specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuit systems. The system circuit system 304 may be part of the implementation of any desired function in UE 300. In this regard, the system circuit system 304 may include logic for facilitating the following (as examples): decoding and playing music and video, such as MP3, MP4, MPEG, AVI, FLAC, AC3 or WAV decoding and playing; running applications; accepting user input; saving and retrieving application data; establishing, maintaining and terminating cellular phone calls or data connections, such as Internet connections; establishing, maintaining and terminating wireless network connections, Bluetooth connections or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the 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. Other examples of the I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0032] refer to Figure 3, the communication interface 302 may include a radio frequency (RF) transmission (Tx) and reception (Rx) circuit system 316 for processing the transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver that includes a modulation / demodulation circuit system, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), a filter, a waveform shaper, a filter, a preamplifier, a power amplifier, and / or other logic for transmitting and receiving through one or more antennas or (for some devices) through a physical (e.g., wired) medium. The signals sent and received may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, the communication interface 302 may include a transceiver that supports transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA) +, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below are applicable to other wireless communication technologies, whether from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0033] refer to Figure 3 , the system circuit system 304 may include one or more processors 321 and a 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 implement the desired functions of the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will send or has received through the communication interface 302. In various implementations, the system power of the UE 300 may be provided by a power storage device such as a battery or a transformer.

[0034] Data burst arrival time coordination and regulation

[0035] In a wireless network, radio resources are shared by various devices (such as user equipment). Radio resources may include time resources and spectrum resources. The delivery or transmission of user data needs to pass through various network elements. For example, for downlink services, data may start from a data network or application, go to the core network, and then to the radio access network (RAN), and then it can be delivered to the UE by the base station via a radio interface (e.g., Uu interface). For uplink services, data may come from a data network or an application running on the UE, and be delivered to the base station via an air interface, and the data will be further routed by the RAN to the core network. In order to ensure smooth data transmission and improve network performance, coordination between these different network elements is required.

[0036] For example, the base station has resource constraints such that only certain resources can be used or allocated to the UE. For example, data may be sent to the UE only at certain times. In this case, the core network is expected to deliver the data to the RAN at the right time that satisfies the resource constraints on the base station. This means that after receiving the data from the core network, the base station may have radio resources available at any time or with minimum latency (e.g., below a threshold) so that the data can be sent to the UE to meet the latency requirements. Otherwise, the base station may have to buffer the data until the moment when resources are available, and this will result in excessive transmission delays and will also increase buffering costs.

[0037] To achieve this goal, the base station can communicate with the core network to coordinate the data burst arrival time so that the data burst arrival time matches the resource conditions on the base station side. The burst arrival time can be adjusted to align with the radio resource pattern. In the present disclosure, various embodiments for coordinating burst arrival time information between various network elements in a wireless network are described. The details of these embodiments are described below.

[0038] Embodiment 1: Downlink burst arrival time adjustment by a base station without CN capability indication trigger

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

[0040] Figure 4 Exemplary message flows and interactions between various network elements (including base stations, core networks, UEs, and data networks or applications running in the application layer) for implementing DL burst arrival time adjustment are shown.

[0041] Step 1:

[0042] This step is optional. The core network or a core network node (such as an access and mobility management function (AMF)) may send a downlink (DL) burst scheduling arrangement of the UE's DL data bursts to the base station. The DL burst scheduling arrangement may include the DL burst arrival time and may also include the period of the DL burst.

[0043] Step 2:

[0044] 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 decide to adjust the DL burst arrival time so that it 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 UE-related signaling. The DL burst arrival time adjustment indication may include at least one of the following:

[0045] Recommended DL burst arrival time;

[0046] Recommended period for DL ​​bursts;

[0047] The recommended DL burst arrival time offset relative to the current DL burst arrival time;

[0048] Recommended DL burst arrival start time and recommended DL burst duration;

[0049] · The available downlink radio resources for the UE (e.g., Uu interface resources)

[0050] Matching recommended DL burst arrival time pattern;

[0051] Cell-specific time division duplex (TDD) downlink time domain mode;

[0052] Cell-specific TDD uplink and downlink time domain modes; or

[0053] ·Indication to delete DL burst arrival time related configuration;

[0054] • An indication that the current radio resource configuration does not match the current traffic pattern of DL bursts.

[0055] The DL burst arrival time pattern can be represented as a sequence {DL burst arrival time, duration, period}, for example, the sequences {StartTime1, TimeDuration1, Periodicity1}, {StartTime2, TimeDuration2, Periodicity2}.

[0056] The DL burst arrival time-related configuration may include at least one of the following: a DL burst arrival start time, a DL burst period.

[0057] The DL burst arrival start time and the DL burst duration can be expressed as a sequence {StartTime, TimeDuration}.

[0058] A cell-specific TDD downlink time domain pattern or a cell-specific uplink / downlink TDD configuration is used to indicate the quasi-periodic DL available time. Figure 5 Exemplary cell-specific TDD uplink and downlink time domain modes are shown. Figure 5 As shown, there is a large cycle with a period (periodicity) of P = 5 ms (milliseconds). In each large cycle, there are two small cycles with periods of P1 = 3 ms and P2 = 3 ms. The arrangement of downlink time allocation and uplink allocation is shown in each small cycle.

[0059] In one implementation, the DL burst arrival time related configuration may include the DL arrival time and a period for the DL burst.

[0060] Step 3:

[0061] Upon receiving the DL burst arrival time adjustment indication, if the core network agrees to recommend the DL burst arrival time, it may send a DL burst arrival time adjustment confirmation to the base station via UE-related signaling 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:

[0062] DL burst arrival time;

[0063] ·The period of DL burst;

[0064] DL burst arrival time offset relative to the current DL burst arrival time;

[0065] DL burst arrival start time and DL burst duration;

[0066] DL burst arrival time pattern that matches the available downlink radio resources for the UE; or

[0067] · Indication to remove DL burst arrival time related configuration.

[0068] For example, the DL burst arrival time pattern can be represented as a sequence {DL burst arrival time, period}.

[0069] In one implementation, the DL burst arrival time related configuration may include the DL arrival time and a period for the DL burst.

[0070] Step 4:

[0071] For DL ​​bursts, the data network (DN) or the application (APP) running at the application layer is driving the data transmission. The core network can also send a DL burst arrival time adjustment indication to the DN or APP to trigger the data transmission time adjustment on the DN / APP side so that the DL burst arrival time matches the recommended value.

[0072] Step 5:

[0073] 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) exit time for DL ​​data based on the DL burst arrival time adjustment indication.

[0074] Embodiment 2: Downlink burst arrival time adjustment by a base station with CN capability indication trigger

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

[0076] Figure 6 Exemplary message flows and interactions between various network elements (including base stations, core networks, UEs, and data networks or applications running in the application layer) for implementing DL burst arrival time adjustment are shown.

[0077] Step 1:

[0078] The core network or a core network node (such as an AMF) may send a downlink (DL) burst scheduling arrangement for a DL data burst of a UE to a base station. The DL burst scheduling arrangement may include a DL burst arrival time and may also include a period of a DL burst. 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 a UE level, a base station level, or a core network level.

[0079] Step 2:

[0080] 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 decide to adjust the DL burst arrival time so that it 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 UE-related signaling. The DL burst arrival time adjustment indication may include at least one of the following:

[0081] Recommended DL burst arrival time;

[0082] Recommended period for DL ​​bursts;

[0083] The recommended DL burst arrival time offset relative to the current DL burst arrival time;

[0084] Recommended DL burst arrival start time and recommended DL burst duration;

[0085] · The available downlink radio resources for the UE (e.g., Uu interface resources)

[0086] Matching recommended DL burst arrival time pattern;

[0087] Cell-specific time division duplex (TDD) downlink time domain mode;

[0088] Cell-specific TDD uplink and downlink time domain modes;

[0089] · an indication to delete the DL burst arrival time related configuration; or

[0090] • An indication that the current radio resource configuration does not match the current traffic pattern of DL bursts.

[0091] Step 3:

[0092] Different from the first embodiment, when 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 indicated to the base station that such adjustment is supported.

[0093] For DL ​​bursts, the data network (DN) or the application (APP) running at the application layer is driving the data transmission. The core network can send a DL burst arrival time adjustment indication to the DN or APP to trigger the data transmission time adjustment on the DN / APP side so that the DL burst arrival time matches the recommended value.

[0094] Step 4:

[0095] The core network may also send a DL burst arrival time adjustment indication to the UE via a NAS message. The UE may determine the 5GS exit time for DL ​​data based on the DL burst arrival time adjustment indication.

[0096] Embodiment 3: Uplink burst arrival time adjustment triggered by base station without CN capability indication

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

[0098] Figure 7Exemplary message flows and interactions between various network elements (including base stations, core networks, UEs, and data networks or applications running in the application layer) for implementing UL burst arrival time adjustment are shown.

[0099] Step 1:

[0100] This step is optional. The core network or a core network node (such as an AMF) may send an uplink (UL) burst scheduling arrangement for UL data bursts of the UE to the base station. The UL burst scheduling arrangement may include UL burst arrival times and may also include a period of the UL bursts.

[0101] Step 2:

[0102] The base station may determine whether the UL burst scheduling arrangement is aligned with its own UL resource availability or the UL resources that can be allocated to the UE. The base station may decide to adjust the UL burst arrival time so that it can be better aligned with the UL resource availability. The base station may send an UL burst arrival time adjustment indication to the core network (e.g., AMF) via UE-related signaling. The UL burst arrival time adjustment indication may include at least one of the following:

[0103] Recommended UL burst arrival time;

[0104] UL emergency recommended cycle;

[0105] The recommended UL burst arrival time offset relative to the current UL burst arrival time;

[0106] Recommended UL burst arrival start time and recommended UL burst duration;

[0107] Recommended UL burst matching the available uplink radio resources for the UE

[0108] Arrival time pattern;

[0109] Cell-specific time division duplex (TDD) uplink time domain mode;

[0110] Cell-specific TDD uplink and downlink time domain modes;

[0111] · an indication to delete the UL burst arrival time related configuration; or

[0112] • An indication that the current radio resource configuration does not match the current traffic pattern of UL bursts.

[0113] The UL burst arrival time pattern may be represented as a sequence {UL burst arrival time, duration, period}, for example, a sequence {StartTime1, TimeDuration1, Periodicity1}, {StartTime2, TimeDuration2, Periodicity2}.

[0114] The UL burst arrival start time and the UL burst duration may be represented as a sequence {StartTime, TimeDuration}.

[0115] In one implementation, the UL burst arrival time related configuration may include the UL arrival time and the period of the UL burst.

[0116] Step 3:

[0117] Upon receiving the UL burst arrival time adjustment indication from the base station, if the core network agrees with the recommended UL burst arrival time, it may send a UL burst arrival time adjustment confirmation to the base station via UE-related signaling 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:

[0118] UL burst arrival time;

[0119] UL burst period;

[0120] UL burst arrival time offset relative to the current UL burst arrival time;

[0121] UL burst arrival start time and UL burst duration;

[0122] · a UL burst arrival time pattern that matches the available downlink radio resources for the wireless device; or

[0123] · Delete the indication of UL burst arrival time related configuration.

[0124] In one implementation, the UL burst arrival time related configuration may include the UL arrival time and the period of the UL burst.

[0125] Step 4:

[0126] The core network may also send a UL burst arrival time adjustment indication to the UE via, for example, a NAS message.

[0127] Step 5:

[0128] For UL bursts, the data network (DN) or the application (APP) running at the application layer is driving the data transmission. The APP may include applications running on the UE, such as online conference APP, video streaming APP, etc. The UE may send an UL burst transmission time adjustment indication to the DN or APP to trigger the data transmission time adjustment on the DN / APP side so that the UL burst arrival time matches the recommended value.

[0129] Embodiment 4: Uplink burst arrival time adjustment triggered by a base station with a CN capability indication

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

[0131] Figure 8 Exemplary message flows and interactions between various network elements (including base stations, core networks, UEs, and data networks or applications running in the application layer) for implementing UL burst arrival time adjustment are shown.

[0132] Step 1:

[0133] The UE may send at least one of the following to the core network via, for example, a NAS message: an UL burst arrival time, a period of the UL burst, and an UL burst arrival time adjustment support indication. In one implementation, the UL burst arrival time adjustment support indication may be implicitly indicated by a UL burst arrival time range, i.e., the UE supports UL bursts arriving within the specified range.

[0134] Step 2:

[0135] The core network or a core network node (such as an AMF) may send a UL burst scheduling arrangement for a UL data burst of a UE to a base station. The UL burst scheduling arrangement may include a UL burst arrival time, and may also include a period of the UL burst. 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 a UE level, a base station level, or a core network level.

[0136] Step 3:

[0137] The base station may determine whether the UL burst scheduling arrangement is aligned with its own UL resource availability or the UL resources that can be allocated to the UE. The base station may decide to adjust the UL burst arrival time so that it can be better aligned with the UL resource availability. The base station may send an UL burst arrival time adjustment indication to the core network (e.g., AMF) via UE-related signaling. The UL burst arrival time adjustment indication may include at least one of the following:

[0138] Recommended UL burst arrival time;

[0139] UL emergency recommended cycle;

[0140] The recommended UL burst arrival time offset relative to the current UL burst arrival time;

[0141] Recommended UL burst arrival start time and recommended UL burst duration;

[0142] Recommended UL burst matching the available uplink radio resources for the UE

[0143] Arrival time pattern;

[0144] Cell-specific time division duplex (TDD) uplink time domain mode;

[0145] Cell-specific TDD uplink and downlink time domain modes;

[0146] · an indication to delete the UL burst arrival time related configuration; or

[0147] • An indication that the current radio resource configuration does not match the current traffic pattern of UL bursts.

[0148] The UL burst arrival time pattern may be represented as a sequence {UL burst arrival time, duration, period}, for example, a sequence {StartTime1, TimeDuration1, Periodicity1}, {StartTime2, TimeDuration2, Periodicity2}.

[0149] The UL burst arrival time related configuration may include the UL arrival time and the period of the UL burst.

[0150] The UL burst arrival start time and the UL burst duration may be represented as a sequence {StartTime, TimeDuration}.

[0151] Step 4:

[0152] Different from the first embodiment, when 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 indicated to the base station that such adjustment is supported.

[0153] The core network may send a UL burst arrival time adjustment indication to the UE via a NAS message.

[0154] Step 5:

[0155] For UL bursts, the data network (DN) or the application (APP) running at the application layer is driving the data transmission. The APP may include applications running on the UE, such as online conference APP, video streaming APP, etc. The UE may send an UL burst transmission time adjustment indication to the DN or APP to trigger the data transmission time adjustment on the DN / APP side so that the UL burst arrival time matches the recommended value.

[0156] Embodiment 5: Uplink burst arrival time adjustment triggered by UE

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

[0158] Fig. 9 Exemplary message flows and interactions between various network elements (including base stations, core networks, UEs, and data networks or applications running in the application layer) for implementing one option for UL burst arrival time adjustment are shown.

[0159] Option 1 (such as Fig. 9 (shown)

[0160] Step 1:

[0161] 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 configuration or its preferred UL burst transmission configuration via, for example, a NAS message. The UE may include at least one of the following in the message: UL burst arrival time or UL burst period.

[0162] Alternatively or additionally, 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:

[0163] Recommended UL burst arrival time;

[0164] UL emergency recommended cycle;

[0165] The recommended UL burst arrival time offset relative to the current UL burst arrival time;

[0166] Recommended UL burst arrival start time and recommended UL burst duration;

[0167] Recommended UL burst matching the available uplink radio resources for the UE

[0168] Arrival time pattern;

[0169] Cell-specific time division duplex (TDD) uplink time domain mode;

[0170] Cell-specific TDD uplink and downlink time domain modes;

[0171] · an indication to delete the UL burst arrival time related configuration; or

[0172] • An indication that the current radio resource configuration does not match the current traffic pattern of UL bursts.

[0173] The UL burst arrival time related configuration may include the UL arrival time and the period of the UL burst.

[0174] Step 2:

[0175] Upon receiving the UL burst arrival time adjustment indication from the UE, if the core network agrees with the recommended UL burst arrival time, it 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:

[0176] UL burst arrival time;

[0177] UL burst period;

[0178] UL burst arrival time offset relative to the current UL burst arrival time;

[0179] UL burst arrival start time and UL burst duration;

[0180] · a UL burst arrival time pattern that matches the available downlink radio resources for the wireless device; or

[0181] · Delete the indication of UL burst arrival time related configuration.

[0182] Step 3:

[0183] The core network may send a 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.

[0184] Step 4:

[0185] For UL bursts, the data network (DN) or the application (APP) running at the application layer is driving the data transmission. The APP may include applications running on the UE, such as online conference APP, video streaming APP, etc. The UE may send an UL burst transmission time adjustment indication to the DN or APP to trigger the data transmission time adjustment on the DN / APP side so that the UL burst arrival time matches the recommended value.

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

[0187] Option 2

[0188] Step 1:

[0189] The UE may have a recommended UL burst transmission configuration, or the UE may already have a UL burst transmission configuration. The UE may notify the base station of its current configuration or its preferred UL burst transmission configuration via, for example, an AS message (such as a media access control control element (MAC CE) message, a UE-specific radio resource control (RRC) message, etc.). The UE may include at least one of the UL burst arrival time or the period of the UL burst in the message.

[0190] Alternatively or additionally, the UE may send a UL burst arrival time adjustment indication to the base station. The UL burst arrival time adjustment indication is similar to Option 1 of this embodiment.

[0191] Step 2:

[0192] In step 1, the base station may forward the message from the UE to the core network via UE-related signaling.

[0193] Step 3:

[0194] If the core network agrees with the recommended UL burst arrival time, the core network may send a UL burst arrival time adjustment confirmation to the base station via UE-related signaling. Details on the confirmation can be found in Option 1 of this embodiment.

[0195] Step 4:

[0196] The base station forwards the UL burst arrival time adjustment confirmation to the UE via, for example, an AS message (such as a MAC CE message, a UE-specific RRC message, etc.).

[0197] Step 5:

[0198] For UL bursts, the data network (DN) or the application (APP) running at the application layer is driving the data transmission. The APP may include applications running on the UE, such as online conference APP, video streaming APP, etc. The UE may send an UL burst transmission time adjustment indication to the DN or APP to trigger the data transmission time adjustment on the DN / APP side so that the UL burst arrival time matches the recommended value.

[0199] Exemplarily, the UL burst arrival time may include at least one of the following:

[0200] The time offset relative to the currently used UL burst arrival time;

[0201] a time offset relative to the current time of the wireless communication system when the second message is sent; or

[0202] 5GS absolute time, including at least one of the following:

[0203] ○ System frame number (SFN);

[0204] ○Subframe number;

[0205] ○Time slot number;

[0206] ○Mini time slot number;

[0207] ○ Coordinated Universal Time (UTC); or

[0208] ○ The duration that has elapsed since the predefined time instance.

[0209] Embodiment 6:

[0210] In current wireless networks, in order to reduce UE power consumption, a connected mode discontinuous reception (CDRX) applicable to both periodic services and aperiodic services can be configured. In CDRX mode, the on-duration start timing is calculated as follows:

[0211]

[0212] or

[0213]

[0214] In the above formulas (1) and (2), the period of the periodic service is not taken into consideration.

[0215] If CDRX is used to align with the cycle of periodic services, and the above formula is used, and if the DRX cycle in the formula (i.e., drx-LongCycle or drx-ShortCycle) is not an integer multiple of 10240ms (milliseconds), there is a mismatch between the cycle of periodic services and the DRX On Duration cycle due to System Frame Number (SFN) wraparound. This issue may cause the DRX cycle to be out of sync with the arrival time of data services (e.g., Extended Reality (XR) services) due to SFN wraparound. This issue is addressed in Fig.10 It is further shown in Fig.10In the SFN 0-1023, there is periodic downlink XR service. Starting from SFN 0-1023, the period of XR service matches the DRX cycle (which is 70ms). However, when SFN is reset from 1023 to 0 (i.e., SFN wraparound), the period of XR service does not match the DRX cycle. This will cause DL transmission failure or transmission delay of XR service.

[0216] In this embodiment, in order to solve the SFN wrap-around problem, the start timing of the CDRX on-duration can be indicated by the network (e.g., the radio access network or the core network), and the start of the subsequent CDRX on-duration can be determined based on a periodic offset relative to the start of the previous adjacent (neighbor) CDRX on-duration.

[0217] In one implementation, after CDRX is configured, the media access control (MAC) entity may consider the Nth CDRX on-duration to start from one of the following: SFN*10+subframe=[(SFNstart time*10+subframe start time)+ceil(N×period)]modulo 10240 (3)

[0219] The SFNstart time and the subframe start time are respectively represented by the SFN number and the subframe number of the first on-duration start opportunity when CDRX is (re)configured.

[0220] or

[0221] (numberOfSlotsPerFrame×SFN+time slot number in frame)=

[0222] [(numberOfSlotsPerFrame×SFNstart time+slotstart time)+ceil(N×

[0223] period × numberOfSlotsPerFrame / 10)]modulo(1024×

[0224] numberOfSlotsPerFrame) (4)

[0226] The SFNstart time and slotstart time are respectively the SFN and time slot number of the first start duration start timing when CDRX is (re)configured.

[0227] Or (numberOfSlotsPerFrame×SFN×numberOfSymbolsPerSlot+number of slots in a frame×numberOfSymbolsPerSlot+number of symbols in a frame)=

[0228] [(numberOfSlotsPerFrame×SFNstart time×numberOfSymbolsPerSlot

[0229] + slotstart time × numberOfSymbolsPerSlot + symbolstart time) + ceil(N × cycle × numberOfSlotsPerFrame × numberOfSymbolsPerSlot /

[0230] 10)]modulo(1024×numberOfSlotsPerFrame×

[0231] numberOfSymbolsPerSlot) (5)

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

[0234] Where ceil(X) is a ceiling operation used to obtain the smallest integer value greater than or equal to X. In one implementation, if a non-integer CDRX period value is not configured, the ceil() operation may be removed from the formula.

[0235] In one implementation, the ceil() operation may be replaced with FLOOR(), where FLOOR(X) is a floor operation used to obtain the maximum integer value less than or equal to X.

[0236] Embodiment 7:

[0237] The XR service may be a video streaming service with fixed picture frames (eg, H.264 frames, which may include I-frames, P-frames, B-frames). Fig.11 An example application frame and its mapping to an IP packet are shown. Fig.11 As shown, each application frame (eg, picture frame) can be mapped to multiple IP packets. For example, I frame I1 is mapped to IP packet I 11 to I 1n , and B frame B2 is mapped to IP packet B21 To B 2m . Similarly Fig.11 As shown, application frames I1 to B 12 Form an Application Data Unit (ADU).

[0238] Since different picture frames are encoded / decoded using different encoding / decoding schemes, the Quality of Service (QoS) priority or importance of different frames is also different. Fig.11 The decoding time series and presentation time series of the ADU are shown in Fig.12 Shown in.

[0239] An I frame is a key frame that stores / sends all the data needed to display the frame.

[0240] In compressed video, I frames are interspersed with P frames and B frames. The more I frames are included, the better the video quality; however, I frames contain the most bits and therefore take up more space on the storage medium and consume more radio resources to deliver over the Uu interface.

[0241] • A P frame is a delta frame that contains only data that is different from the previous I frame (such as color or content changes). Therefore, a P frame relies on the previous I frame to fill in most of the data.

[0242] A B frame is also a delta frame, which contains only data that is different from the previous frame and different from the data in the next frame. Therefore, a B frame relies on the previous and following frames to fill most of the data.

[0243] Considering that different application frames have different QoS priorities or importance levels during ADU decoding, and there are dependencies between different frames, it is beneficial to distinguish these frames in the RAN and weight / consider the difference for radio resource scheduling.

[0244] In one implementation, an XR service (e.g., a video stream) is mapped to a QoS flow, which may indicate a video frame sequence (e.g., a PDU set sequence based on a PDU set sequence number if a video frame is mapped to another PDU set). To differentiate the QoS priority or importance level of PDU sets in a QoS flow, there are two options:

[0245] Option 1: Introducing QoS sub-flows

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

[0247] When QoS sub-flows are introduced, the gNB can map one QoS flow to one data radio bearer (DRB), and then map different QoS sub-flows of the same DRB to different logical channels (LCs), such as Fig.13 As shown. Fig.13 In the RLC-BearerConfig, the QoS flow ID is associated with the DRB identifier in the DRB configuration, and the DRB identifier is associated with the QoS sub-flow ID or QoS sub-flow priority in the RLC-BearerConfig. Therefore, one QoS flow can be mapped to different logical channels.

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

[0249] 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 know the QoS subflow information so that it can correctly route PDCP PDUs with different QoS subflows to different logical channels.

[0250] In order for the PDCP entity to know the QoS sub-flow information, the QoS sub-flow ID or the QoS sub-flow priority should be included in the SDAP PDU (eg, by adding an SDPA header including a QoS sub-flow ID and / or a QoS sub-flow priority field).

[0251] Option 2: Introduce only priority or importance indication in the GTP-U header

[0252] In one implementation, user data-only PDUs are routed from GTP-U (e.g., in DL PDU 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 finally from the RLC entity to the MAC entity. Radio resource scheduling is performed in the MAC entity.

[0253] Considering that one PDCP entity is associated with a DRB, if QoS sub-flow is not introduced, one DRB is usually mapped to one logical channel.

[0254] If a priority or importance indication is introduced in the GTP-U header so that the MAC entity can know the priority or importance indication information for radio resource scheduling, the priority or importance indication should be available in the MAC entity. This can be achieved using one of the following solutions:

[0255] Solution 1:

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

[0257] Solution 2:

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

[0259] The above description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter may be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be interpreted as not being limited to any example embodiment described herein. It is intended to provide a reasonably broad scope for the subject matter claimed or covered. In addition, for example, the subject matter may be embodied as a method, device, component, system, or non-transitory computer-readable medium for storing computer code. Therefore, for example, the embodiment may take the form of hardware, software, firmware, storage medium, or any combination thereof. For example, the above method embodiment may be implemented by a component, device, or system including a memory and a processor by executing a computer code stored in the memory.

[0260] Throughout the specification and claims, terms may have subtle meanings that are suggested or implied from the context, beyond the explicitly stated meanings. Likewise, the phrase "in one embodiment / implementation" used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" used herein does not necessarily refer to a different embodiment. For example, the claimed subject matter includes combinations of all or part of the example embodiments.

[0261] In general, terms can be understood at least in part from usage in context. For example, terms used herein (such as "and", "or", or "and / or") can include various meanings that can depend at least in part on the context in which such terms are used. In general, "or" if used to associate a list (such as A, B, or C) means A, B, and C, which is used in an inclusive sense here; and A, B, or C, which is used in an exclusive sense here. In addition, the term "one or more" used in this article can be used in a singular sense to describe any feature, structure, or characteristic, and can also be used in a plural sense to describe a combination of features, structures, and characteristics, which depends at least in part on the context. Similarly, terms such as "a", "an", or "the" can be understood to convey singular or plural usage, which depends at least in part on the context. In addition, the term "based on" can be understood to not necessarily be intended to convey a set of exclusive factors, but can allow for the presence of other factors that are not necessarily explicitly described, which depends at least in part on the context.

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

[0263] In addition, the above-mentioned features, advantages and characteristics of the present solution can be combined in any suitable manner in one or more embodiments. Based on the description herein, a person of ordinary skill in the relevant art will recognize that the present solution can be practiced without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages that may not be present in all embodiments of the present solution can be recognized in certain embodiments.

Claims

1. A method for wireless communication, performed 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 for a DL burst of a wireless device needs to be adjusted; as well as A first message is sent to a core network in the wireless communication system, wherein the first message includes a DL burst arrival time adjustment indication for the wireless device, wherein the DL burst arrival time adjustment indication indicates that a DL burst arrival time for a DL burst of the wireless device needs to be adjusted.

2. The method of claim 1 , wherein the DL burst arrival time adjustment indication comprises at least one of the following: Recommended DL burst arrival time; The recommended period of the DL burst; 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 mode; Cell-specific TDD uplink and downlink time domain modes; or An indication that a current radio resource configuration does not match a current traffic pattern of said DL burst.

3. The method according to claim 1 or 2, wherein the first message comprises a user equipment (UE) related signaling message.

4. The method according to claim 1 or 2, further comprising: receiving a second message from the core network as a response to the first message, the second message comprising a DL burst arrival time confirmation, and the DL burst arrival time confirmation comprises at least one of the following: DL burst arrival time; a period of the DL burst; 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 Indication to delete the DL burst arrival time related configuration.

5. The method according to claim 1, wherein: Before sending the first message to the core network, the method further includes: receiving an indicator from the core network, the indicator indicating whether the core network supports DL burst arrival time adjustment; and Sending the first message to the core network includes: In response to the indicator indicating that the core network supports the DL burst arrival time adjustment, the first message is sent to the core network.

6. The method according to claim 1, wherein the core network's reception of the first message triggers the core network to perform at least one of the following: Sending the DL burst arrival time adjustment indication to an entity providing the DL burst to the wireless device, the entity comprising at least one of: a data network; or an application layer; or The DL burst arrival time adjustment indication is sent to the wireless device.

7. The method according to claim 1, wherein sending the first message to the core network comprises: The first message is sent to an access and mobility management function (AMF) of the core network via UE-related signaling.

8. The method according to claim 1, wherein the first network element comprises a base station, and the base station comprises one of the following: gNodeB(gNB); eNodeB (eNB); ng-eNodeB (ng-eNB); or NodeB.

9. A method for wireless communication, performed by a core network node in a wireless communication system, the method comprising: A first message is received from a base station in the wireless communication system, the first message including 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 for a DL burst of the wireless device needs to be adjusted.

10. The method of claim 9, wherein the DL burst arrival time adjustment indication comprises at least one of the following: Recommended DL burst arrival time; The recommended period of the DL burst; 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 mode; Cell-specific TDD uplink and downlink time domain modes; or An indication that a current radio resource configuration does not match a current traffic pattern of said DL burst.

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

12. The method according to claim 9 or 10, further comprising: The DL burst arrival time adjustment indication is sent to the wireless device.

13. The method according to claim 9, wherein: Before receiving the first message from the base station, the method further includes: An indicator is sent to the base station, the indicator indicating whether the core network node supports DL burst arrival time adjustment.

14. The method according to claim 13, further comprising: sending a second message to the base station as a response to the first message, the second message comprising a DL burst arrival time confirmation, and the DL burst arrival time confirmation comprises at least one of the following: DL burst arrival time; a period of the DL burst; 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 Indication to delete the DL burst arrival time related configuration.

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

16. A method for wireless communication, performed 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 for an UL burst of a wireless device needs to be adjusted; as well as A first message is sent to a core network in the wireless communication system, wherein the first message includes a UL burst arrival time adjustment indication for the wireless device.

17. The method of claim 16, wherein the UL burst arrival time adjustment indication comprises at least one of the following: Recommended UL burst arrival time; The recommended period of the UL burst; 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 available uplink radio resources for the wireless device; Cell-specific time division duplex (TDD) uplink time domain mode; Cell-specific TDD uplink and downlink time domain modes; or An indication that a current radio resource configuration does not match a current traffic pattern of the UL burst.

18. The method according to claim 16, further comprising: receiving a second message from the core network as a response to the first message, the second message comprising a UL burst arrival time confirmation, and the UL burst arrival time confirmation comprises at least one of the following: UL burst arrival time; a period of the UL burst; 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 available downlink radio resources for the wireless device; or An indication of deleting the UL burst arrival time related configuration.

19. The method of claim 16, wherein: Before sending the first message to the core network, the method further includes: receiving an indicator from the core network, the indicator indicating whether the core network supports UL burst arrival time adjustment; and Sending the first message to the core network includes: In response to the indicator indicating that the core network supports the UL burst arrival time adjustment, the first message is sent to the core network.

20. The method of claim 16, wherein: Receipt of the first message by the core network triggers the core network to send the UL burst arrival time adjustment indication to the wireless device; and Receipt of the UL burst arrival time adjustment indication by the wireless device triggers the wireless device to send the UL burst arrival time adjustment indication to an entity providing UL bursts for the wireless device, the entity comprising at least one of: a data network; or an application layer.

21. The method according to claim 16, wherein sending the first message to the core network comprises: The first message is sent to the AMF of the core network via UE-related signaling.

22. The method according to claim 16, wherein the first network element comprises a base station, and the base station comprises one of the following: gNodeB(gNB); eNodeB (eNB); ng-eNodeB (ng-eNB); or NodeB.

23. A method for wireless communication, performed by a core network node in a wireless communication system, the method comprising: A first message is received from a base station in the wireless communication system, the first message including 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 for an UL burst of the wireless device needs to be adjusted.

24. The method of claim 23, wherein the UL burst arrival time adjustment indication comprises at least one of the following: Recommended UL burst arrival time; The recommended period of the UL burst; 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 available uplink radio resources for the wireless device; Cell-specific time division duplex (TDD) uplink time domain mode; Cell-specific TDD uplink and downlink time domain modes; or An indication that a current radio resource configuration does not match a current traffic pattern of the UL burst.

25. The method according to claim 23 or 24, further comprising: The UL burst arrival time adjustment indication is sent to the wireless device.

26. The method of claim 23, wherein before receiving the first message from the base station, the method further comprises: A first indicator is sent to the base station, the first indicator indicating whether the core network node supports UL burst arrival time adjustment for the wireless device.

27. The method according to claim 26, wherein before sending the first indicator to the base station, the method further comprises: A second indicator is received from the wireless device, the second indicator indicating whether the wireless device supports the UL burst arrival time adjustment.

28. The method of claim 23, further comprising: sending a second message to the base station as a response to the first message, the second message comprising a UL burst arrival time confirmation, and the UL burst arrival time confirmation comprises at least one of the following: UL burst arrival time; a period of the UL burst; 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 available downlink radio resources for the wireless device; or An indication of deleting the UL burst arrival time related configuration.

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

30. A method for wireless communication, performed by a wireless device in a wireless communication system, the method comprising: Sending a first message to a first network element in the wireless communication system, the first message including a UL burst arrival time adjustment indication for the wireless device; as well as A second message is received from the first network element as a response to the first message, the second message including confirmed UL burst arrival time information.

31. The method of claim 30, wherein the UL burst arrival time adjustment indication comprises at least one of the following: Recommended UL burst arrival time; or The recommended period of the UL burst.

32. The method of claim 30, wherein the confirmed UL burst arrival time information comprises at least one of the following: UL burst arrival time; or a period of the UL burst; The UL burst arrival time is represented by one of the following: The time offset relative to the currently used UL burst arrival time; a time offset relative to a current time of the wireless communication system when the second message is sent; or The absolute value of the wireless communication system includes at least one of the following: System frame number (SFN); Subframe number; Time slot number; Mini slot number; Coordinated Universal Time (UTC); or The duration that has elapsed since the start of a predefined time instance.

33. The method of claim 30, further comprising: In response to receiving the second message, sending a third message 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, the second message including the confirmed UL burst arrival time information, Wherein reception of the third message by the entity triggers the entity to adjust UL burst transmission for the wireless device according to the confirmed UL burst arrival time information.

34. The method of claim 30, wherein sending the first message to the first network element in the wireless communication system comprises one of: The first message is sent to a base station in the wireless communication system via an AS message, where the AS message includes at least one of the following: MAC CE message; or RRC message, 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 method according to claim 30, wherein the first network element comprises at least one of the following: AMF; or User Plane Function (UPF).

36. A device for wireless communication, comprising a memory for storing computer instructions, and a processor in communication with the memory, wherein when the processor executes the computer instructions, the processor is configured to implement the method according to any one of claims 1 to 35.

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

Images