Optimized uplink transmissions with UE assistance information

Abstract

Embodiments of the present disclosure relate to UL transmission with UE assistance information. The first device determines first preferred burst timing information for an application associated with the first device. The first device sends a message to a second device serving the first device, the message including the first preferred burst timing information. The first device receives updated burst timing information for the application from a third device. The first device causes the generation pattern of the UL traffic flow to be adjusted by the application based on the updated burst timing information.

Description

Technical Field

[0001] Various example embodiments relate to the field of telecommunications, and in particular to devices, methods, apparatus, and computer-readable storage media for uplink (UL) transmissions utilizing user equipment (UE) assistance information. Background Art

[0002] There are many applications that can generate periodic traffic flows. In other words, the application sends packets or bursts of packets periodically, for example, every two, five, or ten milliseconds (ms). Applications with periodic traffic can have extremely strict latency requirements on end-to-end network latency. For example, the latency of each burst needs to be constant, such as 2ms. Examples of such applications can include applications used in industrial automation, or consumer applications such as audio, video, gaming, extended reality (XR), or tactile communications. Summary of the invention

[0003] In general, example embodiments of the present disclosure provide a solution for UL transmission using UE assistance information.

[0004] In a first aspect, a first device is provided. The first device includes at least one processor and at least one memory storing instructions, wherein when the instructions are executed by the at least one processor, the first device at least: determines first preferred burst timing information for an application associated with the first device; sends a message to a second device serving the first device, the message including the first preferred burst timing information; receives updated burst timing information for the application from a third device; and causes a generation mode of a UL service flow to be adjusted by the application associated with the first device based on the updated burst timing information.

[0005] In a second aspect, a second device is provided. The second device includes at least one processor and at least one memory storing instructions, wherein when the instructions are executed by the at least one processor, the second device at least: receives a message from a first device served by the second device, the message including: first preferred burst timing information of an application associated with the first device; and sends the first preferred burst timing information to a third device.

[0006] In a third aspect, a third device is provided. The third device includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, causes the third device to at least: receive first preferred burst timing information for an application associated with a first device served by the second device from a second device; determine updated burst timing information for the application based on the first preferred burst timing information; and send the updated burst timing information to the first device.

[0007] In a fourth aspect, a method implemented at a first device is provided. The method includes: determining, at the first device, first preferred burst timing information for an application associated with the first device; sending a message to a second device serving the first device, the message including the first preferred burst timing information; receiving updated burst timing information for the application from a third device; and causing a generation mode of a UL traffic flow to be adjusted by the application associated with the first device based on the updated burst timing information.

[0008] In a fifth aspect, a method implemented at a second device is provided. The method includes: receiving, at the second device, a message from a first device served by the second device, the message including: first preferred burst timing information of an application associated with the first device; and sending the first preferred burst timing information to a third device.

[0009] In a sixth aspect, a method implemented at a third device is provided. The method includes: receiving, at the third device, first preferred burst timing information for an application associated with a first device served by the second device from a second device; determining updated burst timing information for the application based on the first preferred burst timing information; and sending the updated burst timing information to the first device.

[0010] In a seventh aspect, an apparatus is provided. The apparatus includes: a component for determining, at a first device, first preferred burst timing information for an application associated with the first device; a component for sending a message to a second device serving the first device, the message including the first preferred burst timing information; a component for receiving updated burst timing information for the application from a third device; and a component for causing a generation mode of a UL traffic flow to be adjusted by the application based on the updated burst timing information.

[0011] In an eighth aspect, an apparatus is provided. The apparatus includes: a component for receiving, at a second device, a message from a first device served by the second device, the message including first preferred burst timing information of an application associated with the first device; and a component for sending the first preferred burst timing information to a third device.

[0012] In a ninth aspect, an apparatus is provided. The apparatus includes: means for receiving, at a third device, from a second device, first preferred burst timing information for an application associated with a first device served by the second device; means for determining updated burst timing information for the application based on the first preferred burst timing information; and means for sending the updated burst timing information to the first device.

[0013] In a tenth aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium comprising program instructions for causing an apparatus to at least execute the program instructions of the method according to any one of the fourth to sixth aspects above.

[0014] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0016] Figure 1 illustrates an example communication environment in which embodiments of the present disclosure may be implemented;

[0017] Figure 2 illustrates a flow chart of a process for UL transmission according to some embodiments of the present disclosure;

[0018] Figures 3 to 5 An example of a medium access control element (MACCE) according to some embodiments of the present disclosure is respectively illustrated;

[0019] Figure 6 illustrates an example of reduced buffering delay according to some embodiments of the present disclosure;

[0020] Figure 7 A flowchart illustrating a method implemented at a first device according to some embodiments of the present disclosure is illustrated;

[0021] Figure 8 A flowchart illustrating a method implemented at a second device according to some other embodiments of the present disclosure is shown;

[0022] Fig. 9 A flowchart of a method implemented at a third device according to some other embodiments of the present disclosure is illustrated;

[0023] Fig.10 illustrates a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure; and

[0024] Fig.11 A block diagram of an example computer-readable medium is illustrated in accordance with some embodiments of the present disclosure.

[0025] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0026] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for illustrative purposes and help those skilled in the art to understand and implement the present disclosure, and do not represent any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various other ways except for the way described below.

[0027] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0028] In this disclosure, references to "one embodiment," "an embodiment," and "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, those skilled in the art recognize that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0029] It should be understood that although the terms "first" and "second" etc. can be used to describe various elements in this article, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the exemplary embodiment, the first element can be referred to as the second element, and similarly, the second element can be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0030] The term used herein is only used to describe specific embodiments, but is not intended to limit example embodiments. The singular form "one", "one" and "the" used herein also include plural forms, unless the context clearly states otherwise. It will be further understood that the term "includes", "comprising", "having", "having", "containing" and / or "containing" specifies the existence of the features, elements and / or components when used in this article, but does not exclude the existence or addition of one or more other features, elements, components and / or their combinations. As used in this article, "at least one of the following items: <list of two or more elements>" and "at least one of the lists of <two or more elements>" and similar wording (wherein the list of two or more elements is connected by "and" or "or") refer to at least any one element in these elements, or at least any two or more elements in these elements, or at least all elements in these elements.

[0031] As used in this application, the term "circuitry" may refer to one, more, or all of the following:

[0032] (a) a pure hardware circuit implementation (such as an implementation using only analog and / or digital circuitry), and

[0033] (b) a combination of hardware circuitry and software such as (where applicable):

[0034] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0035] (ii) any portion of hardware processor(s) (including digital signal processor(s)) with software, software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions), and

[0036] (c) Hardware circuits and / or processor(s), such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) to operate, but which may not be present when the software is not required for operation.

[0037] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0038] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as long term evolution (LTE), advanced LTE (LTE-A), wideband code division multiplexing (WCDMA), high speed packet access (HSPA), narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal equipment and the network equipment in the communication network can be performed according to any suitable generation of communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), future sixth generation (6G) communication protocol, and / or any other protocol currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. Considering the rapid development of communication, there will certainly be communication technologies and systems that can be used to embody future types of the present disclosure. It should not be regarded as limiting the scope of the present disclosure to the above-mentioned system.

[0039] As used herein, the term "network device" refers to a node in a communication network, via which a terminal device accesses the network and receives services from the network. A network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node (such as a femto, a pico), etc., depending on the terminology and technology applied.

[0040] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, the terminal device may also be referred to as a communication device, UE, subscriber station (SS), portable subscriber station, mobile station (MS), sensor device or access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device (such as a digital camera), a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, equipment operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0041] In the 3rd Generation Partnership Project (3GPP) Release 17, periodic delay-critical flows can be supported for Internet Protocol (IP) and Ethernet via a generic time-sensitive communication (TSC) mechanism. In this case, the application function (AF) directly provides quality of service (QoS) requirements to the fifth generation system (5GS), such as the maximum delay of a TSC QoS flow or a service flow. In addition, for periodic service flows, the AF can provide the period and / or burst size. For periodic service flows, if the AF can determine the burst arrival time (BAT), the AF can also provide the burst arrival time of the 5GS entry. Depending on the flow direction, examples of 5GS entry can include UE or user plane function (UPF). Therefore, the sender transmission time is not provided by the network, but is determined by the application itself.

[0042] The most critical part of the end-to-end network is the 5G Radio Access Network (RAN). In many cases, the 5G RAN introduces a significant portion of the end-to-end latency for traffic flows and is also the bottleneck from a capacity perspective. Even if simple prioritization and overbooking can work in other parts of the network, in the RAN, dedicated resources (e.g., uplink (UL) configuration grant (CG) resources) must be reserved for periodic delay-critical flows, especially considering the traffic with both latency and reliability requirements.

[0043] When time division duplexing (TDD) is used on specific 5G New Radio (NR) radio bands, radio transmissions in the UL and downlink (DL) alternate in a repeating cycle. While the periodic time and duration of the UL and DL transmission slots therein can be flexibly adjusted, at least some parts of the period are usually statically reserved for a specific direction. This does not even happen at the granularity of a single cell or a single gNB to avoid interference, but is common in larger areas. For example, currently in Japan, the regulated TDD operating mode has a DL:UL ratio of 4:1, and operators are not allowed to change this ratio. In addition, one may claim that the TDD operating mode can be adjusted in some areas. However, considering that there may be multiple UEs with similar requirements within a cell, it is impossible for the network to adjust the TDD operating mode for all UEs at the same time. Therefore, in practice, the TDD cycle and the direction of the slot cannot be adjusted based on the individual service flow according to the burst arrival time of the individual service flow, but the burst arrival time of the individual flow needs to be adjusted to the direction of the TDD cycle and slot to achieve the best performance.

[0044] According to an embodiment of the present disclosure, a solution for UL transmission using UE auxiliary information is provided. According to the solution, a first device sends a message to a second device serving the first device. The layer 2 message includes: first preferred burst timing information of an application associated with the first device. Furthermore, the first device receives updated burst timing information for the application from a third device. The updated burst timing information is determined by the third device based on the first preferred burst timing information. Then, the first device enables the generation mode of the service flow to be adjusted by the application based on the updated burst timing information. The solution can enable the application associated with the first device to adjust the UL service flow generation behavior based on the first preferred burst timing information. In this way, an optimal end-user experience can be achieved.

[0045] The principles and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Figure 1 , which illustrates an example communication environment 100 in which embodiments of the present disclosure may be implemented. Figure 1As shown, the communication environment 100 includes a first device 110 , a second device 120 , and a third device 130 .

[0046] In this example, for ease of discussion only, the first device 110 is illustrated as a terminal device, and the second device 120 is illustrated as an access network device serving the terminal device 110. For example, the first device 110 may be implemented as a UE. For example, the second device 120 may be implemented as a base station in an access network. Therefore, the service area of ​​the second device 120 is referred to as a cell 122. The cell 122 may be referred to as a serving cell of the first device 110.

[0047] It should be understood that the terminal device and the base station are merely example implementations of the first device 110 and the second device 120, respectively, and do not represent any limitation on the scope of the present application. Any other suitable implementations are also possible.

[0048] In some embodiments, the third device 130 may be implemented as a core network device. For example, the third device 130 may be implemented as an application function (AF) in the core network or a session management function (SMF) in the core network.

[0049] It should be understood that Figure 1 The number of first devices, second devices, and third devices and the number of cells shown in are for illustration purposes only and do not represent any limitation. Environment 100 may include any suitable number of first devices, second devices, and third devices and cells suitable for implementing the embodiments of the present disclosure.

[0050] Communications in environment 100 may conform to any suitable standard, including but not limited to LTE, LTE Evolution, Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM), etc. In addition, communications may be performed according to any generation of communications protocols currently known or to be developed in the future. Examples of communications protocols include but are not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), and sixth generation (6G) communications protocols.

[0051] Figure 2 A signaling diagram of a process 200 for UL transmission according to some example embodiments of the present disclosure is illustrated. For discussion purposes, reference will be made to Figure 1 Process 200 is described. Process 200 may involve Figure 1 The first device 110, the second device 120, and the third device 130 in the embodiment.

[0052] The first device 110 determines 225 first preferred burst timing information for an application associated with the first device.

[0053] In some embodiments, the application can be run on the first device. In other embodiments, the application can be run on an external device connected to the first device. Examples of external devices can include, but are not limited to, cameras.

[0054] In some embodiments, the first preferred burst timing information includes an indication of at least one of the following:

[0055] The identification of the data radio bearer (DRB) for the UL traffic flow,

[0056] The identification of the Quality of Service (QoS) flow associated with the UL traffic flow,

[0057] The identification of the set of packet data units (PDUs) associated with the UL traffic flow,

[0058] Optimize UL burst arrival time,

[0059] · Optimize UL burst arrival time offset,

[0060] The preferred length of the UL burst arrival window (BAW), or

[0061] ·The cycle of UL traffic flow.

[0062] In some embodiments, the ID of a DRB, the ID of a QoS flow, or the ID of a PDU set may indicate a target DRB, QoS flow, or PDU set to which the UL timing adjustment is to be applied.

[0063] In some embodiments, the preferred UL burst arrival time may be reported in an unsolicited reporting mode. The preferred UL burst arrival time may be in the format of an absolute time or a relative time (eg, using a known timing instance such as a specific system frame number (SFN)).

[0064] In some embodiments, based on observation of the UL traffic of the first device 110 and the available time slots for UL traffic transmission, the first device 110 may determine a preferred UL burst arrival time offset relative to the UL burst arrival time, and report the offset in a reactive mode to the second device 120. This option assumes that the first device 110 and the second device 120 know the UL burst arrival time of the UL traffic. Therefore, the preferred UL burst arrival time offset may be determined with reference to the UL burst arrival time.

[0065] In an embodiment using the proactive mode, the preferred UL burst arrival time window may be determined based on the preferred UL burst arrival time reported by the first device 110, and the preferred length of the UL burst arrival time window. Alternatively, in an embodiment using the reactive mode, the preferred UL burst arrival time window may be determined based on the preferred UL burst arrival time offset, the original UL burst arrival time, and the preferred length of the UL burst arrival time window. The preferred UL burst arrival time window may indicate the expected earliest and latest arrival times. In addition, the preferred UL burst arrival time window may provide greater flexibility (e.g., rather than a moment) for traffic generation at the application.

[0066] In some embodiments, the period of the UL traffic flow (also referred to as the preferred UL burst period) may be used by an application to set or adjust the traffic generation period.

[0067] In some embodiments, the first device 110 may determine the first preferred burst timing information based on at least one of the following: configuration of the first burst timing information, radio resource allocation from the second device 120, or processing time for a UL traffic flow.

[0068] In some embodiments, the configuration for the first preferred burst timing information includes at least one of the following items:

[0069] Information about the burst timing adjustment capability of the application,

[0070] UL burst arrival time,

[0071] at least one candidate length of the UL burst arrival time window,

[0072] At least one candidate period for a UL traffic flow, or

[0073] • A threshold or event for triggering the determination of the first preferred burst timing information.

[0074] In some embodiments, the burst timing adjustment capability information includes at least one of the following items:

[0075] an indication of whether the ID of the DRB of the UL traffic flow, the ID of the QoS flow, or the ID of the PDU set is to be included in the first preferred burst timing information,

[0076] Active mode for sending layer 2 messages,

[0077] Reactive mode for sending layer 2 messages, or

[0078] • Prefer timing granularity of UL burst arrival time offset.

[0079] In some embodiments, an indication of whether an ID of a DRB for a UL traffic flow (also referred to as a DRB ID), an ID of a QoS flow (also referred to as a QoS ID), or an ID of a PDU set (also referred to as a PDU set ID) is to be included in the first preferred burst timing information may be used to activate or deactivate reporting for each individual DRB, QoS flow, or PDU set. For example, by default, if no specific activation configuration is received, no reporting is required. It should be noted that, in principle, activation or deactivation of such reporting may also be performed via lower layer signaling, such as MAC CE or even physical layer (PHY) signaling.

[0080] In some embodiments, the active mode may be used, for example, during the PDU session establishment or modification phase, but before data traffic from an application is generated.

[0081] In some embodiments, after data traffic from an application arrives at the first device 110 , a reactive mode may be used.

[0082] In some embodiments, the timing granularity of the preferred UL burst arrival time offset may include one or more values ​​of the preferred UL burst arrival time offset. The timing granularity may be used to define the timing granularity of the reported value. A common or different value may be configured for each DRB. Alternatively, it may also be predefined in the standard specification without configuration.

[0083] In some embodiments, at least one candidate length of the UL burst arrival time window may be used to define the length of the UL burst arrival time window. Multiple values ​​may be configured, and the first device 110 may indicate which value is preferred via a layer 2 message. Alternatively, for example, one or more code points reported may be predefined in a standard specification without configuration.

[0084] In some embodiments, at least one candidate period of the UL traffic flow may be used to define a preferred period.Multiple values ​​may be configured, and the first device 110 may indicate which value is preferred via a layer 2 message.

[0085] In some embodiments, in the case of using the reactive mode, a threshold or event for triggering the determination of the first preferred burst timing information can be used to trigger the determination of the first preferred burst timing information. For example, after the buffer delay or timing offset (between the actual service and the preferred burst arrival time) is greater than a configured threshold, the determination of the first preferred burst timing information is triggered.

[0086] In some embodiments, the first device 110 may receive 220 a configuration for the first preferred burst timing information from the second device 120. For example, the first device 110 may receive the configuration via a radio resource control (RRC) message. In this regard, the configuration may be referred to as an RRC configuration.

[0087] In some embodiments, a first subset of parameters in a configuration for the first preferred burst timing information may be received from the second device 120. For example, the burst arrival time window may be determined by the second device 120 based on the preferred burst arrival time or preferred burst arrival time offset received from the first device 110.

[0088] In some embodiments, a second subset of parameters in the first preferred burst timing information configuration may be predefined. For example, a timing granularity of a preferred UL burst arrival time offset may be predefined. For another example, at least one candidate length of a UL burst arrival time window may be predefined.

[0089] In an embodiment where the configuration for the first preferred burst timing information includes burst timing adjustment capability information for the application, the second device 120 may receive 210 an indication of the burst timing adjustment capability information from the third device 130. Further, the second device 120 may determine 215 the burst timing adjustment capability information based on the indication.

[0090] Continue to refer Figure 2 , the first device 110 sends 230 a message to the second device 120 serving the first device 110. The message includes first preferred burst timing information.

[0091] In some embodiments, the message includes a layer 2 message. The layer 2 message may include a media access control element (MAC CE). The MAC CE includes the first preferred burst timing information. Figures 3 to 5 Some embodiments of the MAC CE are described.

[0092] Alternatively, in some embodiments, the layer 2 message may include a Packet Data Convergence Protocol (PDCP) control packet data unit (PDU). The PDCP control PDU includes the first preferred burst timing information.

[0093] Therefore, the second device 120 receives the layer 2 message including the first preferred burst timing information. Further, the second device 120 sends 240 the first preferred burst timing information to the third device 130.

[0094] After receiving the first preferred burst timing information, the third device 130 determines 245 updated burst timing information to apply based on the first preferred burst timing information. In turn, the third device 130 sends 250 the updated burst timing information to the first device 110.

[0095] After receiving the updated burst timing information, the first device 110 causes the generation mode of the UL traffic flow to be adjusted by the application based on the updated burst timing information. In this way, an optimal end-user experience can be achieved.

[0096] In some embodiments, the second device 120 may determine 235 second preferred burst timing information for the application based on the first preferred burst timing information. For example, in an embodiment where the first preferred burst timing information includes a preferred UL burst arrival time offset but does not include a preferred UL burst arrival time, the second device 120 may determine the preferred UL burst arrival time based on the preferred UL burst arrival time offset. Further, the second device 120 may include the preferred UL burst arrival time in the second preferred burst timing information. Further, the second device 120 sends the second preferred burst timing information to the third device 130.

[0097] In some embodiments, there is an overlap between the second preferred burst timing information and the first preferred burst timing information. In other words, the second preferred burst timing information may include the first preferred burst timing information and additional information. For example, in an embodiment where the first preferred burst timing information includes a preferred UL burst arrival time offset but does not include a preferred UL burst arrival time, the second preferred burst timing information may include: the first preferred burst timing information, and a preferred UL burst arrival time determined based on the first preferred burst timing information. In such an embodiment, the third device 130 may determine the updated burst timing information based on the second preferred burst timing information.

[0098] In some embodiments, there is no overlap between the second preferred burst timing information and the first preferred burst timing information. For example, in an embodiment where the first preferred burst timing information includes a preferred UL burst arrival time offset but does not include a preferred UL burst arrival time, the second preferred burst timing information may only include a preferred UL burst arrival time determined based on the first preferred burst timing information. In such an embodiment, the third device 130 may determine the updated burst timing information based on the first preferred burst timing information and the second preferred burst timing information.

[0099] In some embodiments, the first device 110 may determine the first preferred burst timing information based on determining that at least one trigger condition is satisfied.

[0100] In some embodiments, the first device 110 may determine that at least one trigger condition is satisfied by determining at least one of the following:

[0101] a delay critical guaranteed bit rate (GBR) bearer requested by the second device 120,

[0102] a difference between an observed burst arrival time of a data burst from an application associated with the first device 110 and a preferred burst arrival time of the data burst exceeds a first threshold, or

[0103] • The buffering delay for the data burst exceeds a second threshold.

[0104] As described above, the layer 2 message may include a MAC CE. The MAC CE includes the first preferred burst timing information. Figures 3 to 5 Some embodiments of the MAC CE are described.

[0105] Figure 3 An example of a burst arrival time offset MAC CE according to some embodiments of the present disclosure is illustrated. Figure 3 In the example of Figure 3 The preferred UL burst arrival time offset MAC CE is used to report the preferred UL burst arrival time offset to the second device 120. This corresponds to a reactive mode in which at least the first (ie, initial) data packet has been delivered to the first device 110.

[0106] In the Burst Arrival Time Offset MAC CE 300, the DRB ID is used to indicate which DRB(s) and corresponding QoS flow(s) the reported burst arrival time offset should be applied to. The "Burst Arrival Time Offset" is used to carry a value for the second device 120 to determine the burst arrival time offset compared to the original or current burst arrival time (e.g., based on the reported value and the configured timing granularity or possible code point). The second device 120 can then forward this information to the third device 130 (e.g., SMF, and further to the AF). For this example, the RRC configuration may include such reporting of the activated DRB(s), trigger conditions, and timing granularity.

[0107] Other MAC CE implementation examples may include more elements depending on the circumstances. Figure 4 Another example of a MAC CE according to some embodiments of the present disclosure is illustrated. Figure 4In the example of , in addition to reporting the preferred burst arrival time offset, the first device 110 can also report the preferred burst arrival time window and the preferred burst period. In this example, for both the preferred burst arrival time window and the preferred burst period, one value from the configured values ​​can be reported (a total of 16 values ​​can be configured as 4 bits long).

[0108] In case of using active mode, the preferred burst arrival time may be reported instead of the preferred burst arrival time offset. For example, the timing information may be referenced to the start of the SFN frame.

[0109] Figure 5 Another example of a MAC CE according to some embodiments of the present disclosure is illustrated. Figure 5 In the example of , the MAC CE may indicate reporting of multiple DRBs. If the first device 110 reports information applicable to multiple DRBs, the first device 110 may include multiple DRB-IDs in the MAC CE, such as Figure 5 as shown in .

[0110] Through the embodiments of the present disclosure, buffering delay can be reduced. Figure 6 Examples of buffering delays with and without embodiments of the present disclosure are illustrated. Figure 6 In the example of FIG, it is assumed that the TDD DL:UL ratio is 4:1. Slot-based scheduling is used. That is, scheduling can only be done at the beginning of a DL slot, i.e., packets arriving after the start point of a DL slot will be scheduled in the next DL slot.

[0111] Without using embodiments of the present disclosure, a packet arrives before the start point 610 of a DL timeslot, and the packet will be sent in a UL timeslot immediately after the end 630 of the DL timeslot. Therefore, there is a buffering delay 620 for the packet.

[0112] With the use of embodiments of the present disclosure, packets may arrive and be sent in a UL timeslot immediately after the end 630 of a DL timeslot. Thus, buffering delays may be significantly reduced.

[0113] Figure 7 FIG. 7 is a flowchart of an example method 700 implemented at a first device according to some example embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1 The method 700 is described from the perspective of the first device 110 .

[0114] At block 710 , the first device 110 determines first preferred burst timing information for an application associated with the first device 110 .

[0115] At block 720, the first device 110 sends a message to a second device serving the first device, the message including the first preferred burst timing information.

[0116] At block 730 , the first device 110 receives updated burst timing information for the application from the third device.

[0117] At block 740 , the first device 110 causes a generation pattern of a UL traffic flow to be adjusted by an application based on the updated burst timing information.

[0118] In some embodiments, the message comprises a layer 2 message, and the layer 2 message comprises a medium access control element (MAC CE), the MAC CE comprising the first preferred burst timing information.

[0119] In some embodiments, the message comprises a layer 2 message, and the layer 2 message comprises a packet data convergence protocol (PDCP) control packet data unit (PDU), the PDCP control PDU comprising the first preferred burst timing information.

[0120] In some embodiments, the first preferred burst timing information includes an indication of at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow associated with the service flow, an identification of a packet data unit (PDU) set associated with the service flow, a preferred uplink burst arrival time, a preferred uplink burst arrival time offset, a preferred length of an uplink burst arrival time window (BAW), or a period of the service flow.

[0121] In some embodiments, determining the first preferred burst timing information comprises determining the first preferred burst timing information based on at least one of: a configuration for the first preferred burst timing information, a radio resource allocation from the second device, or a processing time for the traffic flow.

[0122] In some embodiments, the configuration for the first preferred burst timing information includes at least one of the following items: burst timing adjustment capability information for the application, burst arrival time, at least one candidate length of the uplink burst arrival time window (BAW), at least one candidate period of the service flow, or a threshold or event for determining a trigger for the first preferred burst timing information.

[0123] In some embodiments, the burst timing adjustment capability information includes at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow, or an indication of whether an identification of a packet data unit (PDU) is to be included in the first preferred burst timing information, an active mode for sending layer 2 messages, a reactive mode for sending layer 2 messages, or a timing granularity for a preferred uplink burst arrival time offset.

[0124] In some embodiments, method 700 further includes: receiving, from the second device, a first subset of parameters in a configuration for the first preferred burst timing information.

[0125] In some embodiments, the second subset of parameters in the configuration for the first preferred burst timing information is predefined.

[0126] In some embodiments, determining the first preferred burst timing information comprises: determining the first preferred burst timing information based on determining that at least one trigger condition is satisfied.

[0127] In some embodiments, determining that at least one trigger condition is satisfied includes determining that at least one trigger condition is satisfied by determining at least one of the following items: a delay critical guaranteed bit rate (GBR) bearer requested by the second device, a difference between an observed burst arrival time of a data burst from an application and a preferred burst arrival time of the data burst exceeds a first threshold, or a buffering delay for the data burst exceeds a second threshold.

[0128] In some embodiments, the first device comprises a terminal device, the second device comprises an access network device, and the third device comprises a core network device.

[0129] Figure 8 FIG. 8 is a flowchart of an example method 800 implemented at a second device according to some example embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1 The method 800 is described from the perspective of the second device 120 .

[0130] At block 810 , the second device 120 receives a message from a first device served by the second device, the message including first preferred burst timing information for an application associated with the first device.

[0131] At block 820, the second device 120 sends the first preferred burst timing information to the third device.

[0132] In some embodiments, optionally, at block 830, the second device 120 may receive an indication of burst timing adjustment capability information from the third device 130. In turn, the second device 120 may determine the burst timing adjustment capability information based on the indication.

[0133] In some embodiments, the message comprises a layer 2 message, and the layer 2 message comprises a medium access control element (MAC CE), the MAC CE comprising the first preferred burst timing information.

[0134] In some embodiments, the message comprises a layer 2 message, and the layer 2 message comprises a packet data convergence protocol (PDCP) control packet data unit (PDU), the PDCP control PDU comprising the first preferred burst timing information.

[0135] In some embodiments, at least one item of the first preferred burst timing information includes an indication of at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow associated with the service flow, an identification of a packet data unit (PDU) set associated with the service flow, a preferred uplink burst arrival time, a preferred uplink burst arrival time offset, a preferred length of an uplink burst arrival time window (BAW), or a period of the service flow.

[0136] In some embodiments, method 800 further includes: sending a first subset of parameters in a configuration for the first preferred burst timing information to the first device.

[0137] In some embodiments, the configuration for the first preferred burst timing information includes at least one of the following items: burst timing adjustment capability information for the application, burst arrival time, at least one candidate length of the uplink burst arrival time window (BAW), at least one candidate period of the service flow, or a threshold or event for determining a trigger for the first preferred burst timing information.

[0138] In some embodiments, the burst timing adjustment capability information includes at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow, or an indication of whether an identification of a packet data unit (PDU) is to be included in the first preferred burst timing information, an active mode for sending layer 2 messages, a reactive mode for sending layer 2 messages, or a timing granularity for a preferred uplink burst arrival time offset.

[0139] In some embodiments, the method 800 further includes: determining second preferred burst timing information for the application based on the first preferred burst timing information; and sending the second preferred burst timing information to a third device.

[0140] In some embodiments, the first preferred burst timing information includes a preferred uplink burst arrival time offset. In some embodiments, determining the second preferred burst timing information includes determining a preferred uplink burst arrival time to be included in the second preferred burst timing information based on the preferred uplink burst arrival time offset.

[0141] In some embodiments, the first device comprises a terminal device, the second device comprises an access network device, and the third device comprises a core network device.

[0142] Fig. 9 FIG. 9 is a flowchart of an example method 900 implemented at a third device according to some example embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1 The method 900 is described from the perspective of the third device 130 .

[0143] At block 910 , the third device 130 receives, from a second device, first preferred burst timing information for an application associated with a first device served by the second device.

[0144] At block 920 , the third device 130 determines updated burst timing information for the application based on the first preferred burst timing information.

[0145] At block 930 , the third device 130 sends updated burst timing information to the first device.

[0146] In some embodiments, optionally, at block 940 , the third device 130 may send an indication of the burst timing adjustment capability information to the second device 120 .

[0147] In some embodiments, the first preferred burst timing information includes an indication of at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow associated with the service flow, an identification of a packet data unit (PDU) set associated with the service flow, a preferred uplink burst arrival time, a preferred uplink burst arrival time offset, a preferred length of an uplink burst arrival time window (BAW), or a period of the service flow.

[0148] In some embodiments, the first device comprises a terminal device, the third device comprises an access network device, and the second device comprises a core network device.

[0149] In some example embodiments, an apparatus in a radio access network capable of performing any of the methods 700 (e.g., the first device 110) may include a component for performing the corresponding operation of the method 700. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The first apparatus may be implemented as the first device 110 or included therein. In some example embodiments, the component may include a processor and a memory.

[0150] In some example embodiments, the apparatus includes: a component for determining, at a first device, first preferred burst timing information for an application associated with the first device; a component for sending a message to a second device serving the first device, the message including the first preferred burst timing information; a component for receiving updated burst timing information for the application from a third device; and a component for causing a generation mode of a UL service flow to be adjusted by the application based on the updated burst timing information.

[0151] In some embodiments, the message comprises a layer 2 message, and the layer 2 message comprises a medium access control element (MAC CE), the MAC CE comprising the first preferred burst timing information.

[0152] In some embodiments, the message comprises a layer 2 message, and the layer 2 message comprises a packet data convergence protocol (PDCP) control packet data unit (PDU), the PDCP control PDU comprising the first preferred burst timing information.

[0153] In some embodiments, the first preferred burst timing information includes an indication of at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow associated with the service flow, an identification of a packet data unit (PDU) set associated with the service flow, a preferred uplink burst arrival time, a preferred uplink burst arrival time offset, a preferred length of an uplink burst arrival time window (BAW), or a period of the service flow.

[0154] In some embodiments, the component for determining the first preferred burst timing information includes a component for determining the first preferred burst timing information based on at least one of the following items: configuration for the first preferred burst timing information, radio resource allocation from the second device, or processing time for the service flow.

[0155] In some embodiments, the configuration for the first preferred burst timing information includes at least one of the following items: burst timing adjustment capability information for the application, burst arrival time, at least one candidate length of the uplink burst arrival time window (BAW), at least one candidate period of the service flow, or a threshold or event for determining a trigger for the first preferred burst timing information.

[0156] In some embodiments, the burst timing adjustment capability information includes at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow, or an indication of whether an identification of a packet data unit (PDU) is to be included in the first preferred burst timing information, an active mode for sending layer 2 messages, a reactive mode for sending layer 2 messages, or a timing granularity for a preferred uplink burst arrival time offset.

[0157] In some embodiments, the apparatus further comprises means for receiving, from the second device, a first subset of parameters in a configuration for the first preferred burst timing information.

[0158] In some embodiments, the second subset of parameters in the configuration for the first preferred burst timing information is predefined.

[0159] In some embodiments, the means for determining the first preferred burst timing information comprises means for determining the first preferred burst timing information based on determining that at least one trigger condition is satisfied.

[0160] In some embodiments, the component for determining that at least one trigger condition is satisfied includes a component for determining that at least one trigger condition is satisfied by determining at least one of the following items: a delay critical guaranteed bit rate (GBR) bearer requested by the second device, a difference between an observed burst arrival time of a data burst from an application and a preferred burst arrival time of the data burst exceeds a first threshold, or a buffering delay for the data burst exceeds a second threshold.

[0161] In some embodiments, the first device comprises a terminal device, the second device comprises an access network device, and the third device comprises a core network device.

[0162] In some example embodiments, an apparatus in a radio access network capable of performing any of the methods 800 (e.g., the second device 120) may include a component for performing the corresponding operation of the method 800. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The first device may be implemented as the second device 120 or included therein. In some example embodiments, the component may include a processor and a memory.

[0163] In some example embodiments, the apparatus comprises: a component for receiving, at a second device, a message from a first device served by the second device, the message comprising: first preferred burst timing information of an application associated with the first device; and a component for sending the first preferred burst timing information to a third device.

[0164] In some embodiments, the apparatus further comprises: means for receiving an indication of burst timing adjustment capability information from a third device; and means for determining the burst timing adjustment capability information based on the indication.

[0165] In some embodiments, the message comprises a layer 2 message, and the layer 2 message comprises a medium access control element (MAC CE), the MAC CE comprising the first preferred burst timing information.

[0166] In some embodiments, the message comprises a layer 2 message, and the layer 2 message comprises a packet data convergence protocol (PDCP) control packet data unit (PDU), the PDCP control PDU comprising the first preferred burst timing information.

[0167] In some embodiments, at least one item of the first preferred burst timing information includes an indication of at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow associated with the service flow, an identification of a packet data unit (PDU) set associated with the service flow, a preferred uplink burst arrival time, a preferred uplink burst arrival time offset, a preferred length of an uplink burst arrival time window (BAW), or a period of the service flow.

[0168] In some embodiments, the apparatus further comprises means for sending a first subset of parameters in a configuration for the first preferred burst timing information to the first device.

[0169] In some embodiments, the configuration for the first preferred burst timing information includes at least one of the following items: burst timing adjustment capability information for the application, burst arrival time, at least one candidate length of the uplink burst arrival time window (BAW), at least one candidate period of the service flow, or a threshold or event for determining a trigger for the first preferred burst timing information.

[0170] In some embodiments, the burst timing adjustment capability information includes at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow, or an indication of whether an identification of a packet data unit (PDU) is to be included in the first preferred burst timing information, an active mode for sending layer 2 messages, a reactive mode for sending layer 2 messages, or a timing granularity for a preferred uplink burst arrival time offset.

[0171] In some embodiments, the apparatus further comprises: means for determining second preferred burst timing information for the application based on the first preferred burst timing information; and means for sending the second preferred burst timing information to a third device.

[0172] In some embodiments, the first preferred burst timing information includes a preferred uplink burst arrival time offset. In some embodiments, determining the second preferred burst timing information includes determining a preferred uplink burst arrival time to be included in the second preferred burst timing information based on the preferred uplink burst arrival time offset.

[0173] In some embodiments, the first device comprises a terminal device, the second device comprises an access network device, and the third device comprises a core network device.

[0174] In some example embodiments, an apparatus in a radio access network capable of performing any of the methods 900 (e.g., a third device 130) may include a component for performing the corresponding operation of the method 900. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The first device may be implemented as the third device 130 or included therein. In some example embodiments, the component may include a processor and a memory.

[0175] In some example embodiments, the apparatus includes: a component for receiving, at a third device, from a second device, first preferred burst timing information for an application associated with a first device served by the second device; a component for determining updated burst timing information for the application based on the first preferred burst timing information; and a component for sending the updated burst timing information to the first device.

[0176] In some embodiments, the apparatus further comprises means for sending an indication of the burst timing adjustment capability information to the second device.

[0177] In some embodiments, the first preferred burst timing information includes an indication of at least one of the following items: an identification of a data radio bearer (DRB) for a service flow, an identification of a quality of service (QoS) flow associated with the service flow, an identification of a packet data unit (PDU) set associated with the service flow, a preferred uplink burst arrival time, a preferred uplink burst arrival time offset, a preferred length of an uplink burst arrival time window (BAW), or a period of the service flow.

[0178] In some embodiments, the first device comprises a terminal device, the third device comprises an access network device, and the second device comprises a core network device.

[0179] Fig.10 is a simplified block diagram of a device 1000 suitable for implementing embodiments of the present disclosure. The device 1000 may be provided to implement a communication device, such as Figure 1 The first device 110, the second device 120, or the third device 130 is shown. As shown, the device 1000 includes one or more processors 1010, one or more memories 1040 coupled to the processor 1010, and one or more transmitters and / or receivers (TX / RX) 1040 coupled to the processor 1010.

[0180] TX / RX 1040 is used for bidirectional communication. TX / RX 1040 has at least one antenna to facilitate communication. The communication interface may represent any interface required for communication with other network elements.

[0181] Processor 1010 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 1000 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock synchronized with a main processor.

[0182] The memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1024, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1022 and other volatile memories that do not persist during power outages.

[0183] Computer program 1030 includes computer executable instructions executed by associated processor 1010. Program 1030 may be stored in ROM 1020. Processor 1010 may perform any suitable actions and processes by loading program 1030 into RAM 1020.

[0184] The embodiments of the present disclosure may be implemented by the program 1030 so that the device 1000 may execute the reference Figures 7 to 9 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0185] In some embodiments, the program 1030 may be tangibly contained in a computer-readable medium, which may be included in the device 1000 (such as in the memory 1020) or in other storage devices accessible to the device 1000. The device 1000 may load the program 1030 from the computer-readable medium to the RAM 1022 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Fig.11 An example of a computer readable medium 1100 in the form of a CD or DVD is shown. The computer readable medium has a program 1030 stored thereon.

[0186] Generally, various embodiments of the present disclosure may be implemented using hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0187] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as instructions included in a program module, which are executed in a device on a target real or virtual processor to perform the above reference Figure 7-Figure 9 Methods 700, 800 and 900 are described. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules can be combined or split between program modules as needed. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0188] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code is implemented when executed by the processor or controller in the flow chart and / or the block diagram. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0189] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0190] Computer readable medium can be a computer readable signal medium or a computer readable storage medium. Computer readable medium can include but is not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of computer readable storage medium will include electrical connections with one or more wires, portable computer floppy disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. The term "non-transient" used herein is a restriction on the medium itself (i.e., tangible, rather than signal), rather than a restriction on data storage persistence (e.g., RAM and ROM).

[0191] In addition, although the operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in order or performing all the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0192] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A first device, comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the first device to at least: determining first preferred burst timing information for an application associated with the first device; Sending a message to a second device serving the first device, the message including the first preferred burst timing information; receiving updated burst timing information for the application from a third device; as well as The generation mode of the traffic flow is adjusted by the application based on the updated burst timing information.

2. The first device of claim 1, wherein the message comprises a layer 2 message, and the layer 2 message comprises a medium access control element (MAC CE), the MAC CE comprising the first preferred burst timing information.

3. The first device of claim 1, wherein the message comprises a layer 2 message, and the layer 2 message comprises a packet data convergence protocol (PDCP) control packet data unit (PDU), the PDCP control PDU comprising the first preferred burst timing information.

4. The first device of claim 1 , wherein the first preferred burst timing information comprises an indication of at least one of the following: an identification of a data radio bearer (DRB) for the service flow, an identification of a Quality of Service (QoS) flow associated with the traffic flow, an identification of a set of packet data units (PDUs) associated with the service flow, Optimize uplink burst arrival time, Optimize uplink burst arrival time offset, The preferred length of the uplink burst arrival window (BAW), or The period of the service flow.

5. The first device according to claim 1, wherein the first device is caused to determine the first preferred burst timing information based on at least one of the following: For the configuration of the first preferred burst timing information, a radio resource allocation from the second device, or The processing time for the service flow.

6. The first device according to claim 5, wherein the configuration for the first preferred burst timing information comprises at least one of the following: burst timing adjustment capability information for the application, Burst arrival time, at least one candidate length of an uplink burst arrival time window (BAW), at least one candidate period of the traffic flow, or A threshold or event for triggering said determination of said first preferred burst timing information.

7. The first device according to claim 6, wherein the burst timing adjustment capability information comprises at least one of the following items: an indication of whether an identification of a data radio bearer (DRB) for the traffic flow, an identification of a quality of service (QoS) flow, or an identification of a packet data unit (PDU) is to be included in the first preferred burst timing information, Active mode for sending the layer 2 message, The response mode used to send the layer 2 message, or Timing granularity for preferred uplink burst arrival time offset.

8. The first device of claim 5, wherein the first device is further caused to: receive a first subset of parameters in the configuration for the first preferred burst timing information from the second device.

9. The first device of claim 5, wherein a second subset of parameters in the configuration for the first preferred burst timing information is predefined.

10. The first device of claim 1, wherein the first device is caused to determine the first preferred burst timing information based on determining that at least one trigger condition is satisfied.

11. The first device of claim 10, wherein the first device is caused to determine that the at least one trigger condition is satisfied by determining at least one of the following: a delay critical guaranteed bit rate (GBR) bearer requested by the second device, a difference between an observed burst arrival time of a data burst from the application and a preferred burst arrival time of the data burst exceeds a first threshold, or A buffering delay for the data burst exceeds a second threshold.

12. The first device according to any one of claims 1 to 11, wherein the first device comprises a terminal device, the second device comprises an access network device, and the third device comprises a core network device.

13. A second device, comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the second device to at least: receiving a message from a first device served by the second device, the message comprising first preferred burst timing information for an application associated with the first device; as well as The first preferred burst timing information is sent to a third device.

14. The second device of claim 13, wherein the message comprises a layer 2 message, and the layer 2 message comprises a medium access control element (MAC CE), the MAC CE comprising the first preferred burst timing information.

15. The second device of claim 13, wherein the message comprises a layer 2 message, and the layer 2 message comprises a packet data convergence protocol (PDCP) control packet data unit (PDU), the PDCP control PDU comprising the first preferred burst timing information.

16. The second device of claim 13, wherein at least one of the first preferred burst timing information comprises an indication of at least one of: an identification of a data radio bearer (DRB) for the service flow, an identification of a Quality of Service (QoS) flow associated with the traffic flow, an identification of a set of packet data units (PDUs) associated with the service flow, Optimize uplink burst arrival time, Optimize uplink burst arrival time offset, The preferred length of the uplink burst arrival window (BAW), or The period of the service flow.

17. The second device according to claim 13, wherein the second device is further caused to: A first subset of parameters in a configuration for the first preferred burst timing information is sent to the first device.

18. The second device according to claim 17, wherein the configuration for the first preferred burst timing information comprises at least one of the following: burst timing adjustment capability information for the application, Burst arrival time, at least one candidate length of an uplink burst arrival time window (BAW), at least one candidate period of the traffic flow, or A threshold or event for triggering said determination of said first preferred burst timing information.

19. The second device according to claim 18, wherein the burst timing adjustment capability information comprises at least one of the following items: an indication of whether an identification of a data radio bearer (DRB) for the traffic flow, an identification of a quality of service (QoS) flow, or an identification of a packet data unit (PDU) is to be included in the first preferred burst timing information, Active mode for sending the layer 2 message, The response mode used to send the layer 2 message, or Timing granularity for preferred uplink burst arrival time offset.

20. The second device according to claim 18, wherein the second device is further caused to: receiving an indication of the burst timing adjustment capability information from the third device; and Based on the indication, the burst timing adjustment capability information is determined.

21. The second device according to claim 16, wherein the second device is further caused to: determining second preferred burst timing information for the application based on the first preferred burst timing information; and The second preferred burst timing information is sent to the third device.

22. The second device of claim 21, wherein the first preferred burst timing information comprises the preferred uplink burst arrival time offset; and The second device is configured to determine the second preferred burst timing information by: Based on the preferred uplink burst arrival time offset, the preferred uplink burst arrival time is determined to be included in the second preferred burst timing information.

23. The second device according to any one of claims 13 to 22, wherein the first device comprises a terminal device, the second device comprises an access network device, and the third device comprises a core network device.

24. A third device, comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the third device to at least: receiving, from a second device, first preferred burst timing information for an application associated with a first device served by the second device; determining updated burst timing information for the application based on the first preferred burst timing information; as well as The updated burst timing information is sent to the first device.

25. The third device of claim 24, wherein the first preferred burst timing information comprises an indication of at least one of the following: an identification of a data radio bearer (DRB) for the service flow, an identification of a Quality of Service (QoS) flow associated with the traffic flow, an identification of a set of packet data units (PDUs) associated with the service flow, Optimize uplink burst arrival time, Optimize uplink burst arrival time offset, The preferred length of the uplink burst arrival window (BAW), or The period of the service flow.

26. The third device according to claim 24, wherein the third device is further caused to: An indication of burst timing adjustment capability information for the application is sent to the second device.

27. The third device according to any one of claims 24 to 26, wherein the first device comprises a terminal device, the third device comprises an access network device, and the second device comprises a core network device.

28. A method comprising: determining, at a first device, first preferred burst timing information for an application associated with the first device; Sending a message to a second device serving the first device, the message including the first preferred burst timing information; receiving updated burst timing information for the application from a third device; as well as The generation mode of the traffic flow is adjusted by the application based on the updated burst timing information.

29. A method comprising: receiving, at a second device, a message from a first device served by the second device, the message comprising first preferred burst timing information for an application associated with the first device; as well as The first preferred burst timing information is sent to a third device.

30. A method comprising: receiving, at a third device, from a second device, first preferred burst timing information for an application associated with a first device served by the second device; determining updated burst timing information for the application based on the first preferred burst timing information; as well as The updated burst timing information is sent to the first device.

31. An apparatus comprising: means for determining, at a first device, first preferred burst timing information for an application associated with the first device; means for sending a message to a second device serving the first device, the message comprising the first preferred burst timing information; means for receiving updated burst timing information for the application from a third device; as well as Means for causing a traffic flow generation pattern to be adjusted by said application based on said updated burst timing information.

32. An apparatus comprising: means for receiving, at a second device, a message from a first device served by the second device, the message comprising first preferred burst timing information for an application associated with the first device; and The device is configured to send the first preferred burst timing information to a third device.

33. An apparatus comprising: means for receiving, at a third device, from a second device, first preferred burst timing information for an application associated with a first device served by the second device; means for determining updated burst timing information for said application based on said first preferred burst timing information; as well as Means for sending the updated burst timing information to the first device.

34. A computer-readable medium comprising program instructions, which, when executed by at least one processor, cause an apparatus to at least perform the method according to any one of claims 28 to 30.

Images