Apparatus and method for efficient uplink communication
By identifying and processing delay data in user equipment, generating control signals to notify the network of its state changes, thereby eliminating redundant transmission in wireless communication systems, solving the redundancy problem caused by delay data in uplink transmission, and improving the system Efficiency and power utilization of UE.
Patent Information
- Application Number
- CN202380027516.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-26
- Filing Date
- 2023-04-24
- Publication Date
- 2024-11-01
AI Technical Summary
The existing wireless communication system has delayed data in uplink transmission, resulting in redundant transmission, increasing the power consumption of UE and waste of radio resources, and affecting system capacity.
By determining the delay data stored in the buffer in the user equipment and generating a control signal to inform the network of its changing state, resources are freed to improve network efficiency without transmitting the delay data.
Effectively eliminate useless uplink transmission, reduce system interference, save UE's power, extend battery life, and improve the efficiency of wireless systems.
Smart Images

Figure CN118891952A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 335,156, filed on April 26, 2022, entitled “Device and Method for Efficient Uplink Communications,” the entire contents of which are hereby incorporated by reference. Technical Field
[0003] The present disclosure relates to wireless communications, and more particularly, to apparatus and methods for adapting uplink communications in a telecommunications system to improve the efficiency of uplink signaling. Background Art
[0004] A wireless communication system may include one or more network communication devices, such as a base station, which may also be referred to as an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). In addition, a wireless communication system may support wireless communication across radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies other than 5G.
[0005] It is not always possible to transmit uplink signals within the allocated time budget. Certain applications, such as those related to mixed reality, do not use transmission data exceeding the packet delay budget (PDB), making such data redundant. Telecommunication systems would benefit from techniques that minimize redundant or unnecessary data transmissions. Summary of the invention
[0006] The present disclosure relates to methods, apparatus and systems that support determining that data stored in a buffer for uplink communication is expected to be transmitted at a time that is too delayed to be used, and generating a control signal to notify the network of the changed state of the buffered data. By removing the delayed data from the buffer and not transmitting the delayed data, the UE can save power. The network can allocate resources that would otherwise be used to process the delayed data, thereby improving network efficiency.
[0007] Some embodiments of the methods and apparatus described herein may include an apparatus for wireless communication, the apparatus comprising a processor and a memory coupled to the processor, the processor being configured to determine, based on a criterion, that first data for uplink transmission stored in the memory is not suitable for subsequent uplink scheduling, and to trigger transmission of a control message indicating an amount of the first data that will not be provided in the uplink transmission.
[0008] In some embodiments of the methods and apparatus described herein, the first data is associated with at least one of a logical channel and a logical channel group.
[0009] In some embodiments of the methods and apparatus described herein, the first data is stored in at least one of a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC), and a Medium Access Control (MAC) layer.
[0010] In some embodiments of the methods and apparatus described herein, the criterion is based on at least one of a timer state and a packet loss threshold.
[0011] In some embodiments of the methods and apparatus described herein, a timer is associated with a packet delay budget, and the criterion is expiration of the timer.
[0012] In some embodiments of the methods and apparatus described herein, the threshold is associated with at least one of a packet loss rate or a percentage of lost packets, and the criterion is exceeding the threshold.
[0013] In some embodiments of the methods and apparatus described herein, the control message is a MAC Control element.
[0014] In some embodiments of the methods and apparatus described herein, the MAC control element comprises a buffer status report (BSR).
[0015] In some embodiments of the methods and apparatus described herein, the control message is a scheduling request transmitted on a physical uplink control channel (PUCCH).
[0016] In some embodiments of the methods and apparatus described herein, the criterion is exceeding an application data budget of an application data unit.
[0017] Some embodiments of the methods and apparatus described herein may include a method performed by a user equipment in a telecommunications network, the method comprising determining, based on a criterion, that first data stored in a memory of the user equipment for uplink transmission is not suitable for subsequent uplink scheduling, generating a control message indicating an amount of the first data that will not be provided in the uplink transmission, and transmitting the control message to a base station. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Figure 1 An example of a wireless communication system supporting efficient uplink communications according to aspects of the present disclosure is illustrated.
[0019] Figure 2 An example of a block diagram of a device supporting efficient uplink communication according to aspects of the present disclosure is illustrated.
[0020] Figure 3 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 and Fig.11 A flow chart of a method of supporting efficient uplink communications according to aspects of the present disclosure is illustrated.
[0021] Fig. 9 An example of an information element having a field for associating a DRB identity is illustrated.
[0022] Fig.10 An example of a protocol stack with bearers of different priorities is illustrated. DETAILED DESCRIPTION
[0023] In wireless environments, it is not always possible to successfully complete uplink transmissions within the packet delay budget (PDB). Certain applications, including those related to extended reality (XR) such as virtual reality and augmented reality, will discard delayed data, making delayed UE transmissions redundant.
[0024] XR applications can refer to the real and virtual combined environment and human-computer interaction generated by computer technology and wearable devices. It includes representative forms such as augmented reality (AR), mixed reality (MR), virtual reality (VR), and areas inserted between them. The level of virtual range ranges from partial sensory input to fully immersive VR. One aspect of XR is the expansion of human experience, especially the experience related to presence (represented by VR) and cognitive acquisition (represented by AR). For example, XR is explained in more detail in 3GPP TR 26.928.
[0025] If a frame of an XR application can no longer be decoded due to a high percentage of packet loss in the frame or exceeding the PDB of an Application Data Unit (ADU) or a frame or PDU set, it is not beneficial to transmit the remaining data of the relevant ADU or frame, as the application may not benefit from these transmissions. Instead, such delayed transmissions ultimately lead to increased UE power consumption and waste of radio resources, which negatively affects system capacity.
[0026] A service-oriented design that considers XR traffic characteristics can provide more efficient XR service delivery. XR traffic characteristics may include (a) variable packet arrival rates, such as packets arriving at 30-120 frames / second with some jitter, (b) packets with variable and large packet sizes, (c) B-frames and P-frames depending on I-frames, and (d) the presence of multiple traffic or data streams in the uplink, such as gesture and video scenes. Efficient XR service delivery can be achieved by meeting the XR service requirements of more UEs or, for example, in terms of UE energy saving.
[0027] The delay requirement for XR traffic on the Radio Access Network (RAN) side or on the air interface is modeled as a Packet Delay Budget (PDB). The PDB is a finite time budget for a packet to be transmitted over the air from a base station (such as a next-generation NodeB (gNB)) to a UE, or from a UE to a gNB. A delay budget can also be defined for an ADU, which is referred to as an ADU Delay Budget (ADB). An ADU can be the smallest data unit that can be processed independently by an application, such as for processing that manipulates out-of-order traffic data. In this disclosure, a protocol data unit (PDU) set may be used interchangeably with an ADU, so the information and activities discussed about an ADU apply to a PDU set, and vice versa. A PDU set or ADU consists of one or more PDUs, which carry a payload of an information unit generated at the application layer (e.g., a frame or video clip of an XR service, etc.).
[0028] For a given packet, the delay incurred by the packet in the air interface is measured from the time the packet arrives at the gNB to the time it is successfully delivered to the UE. If the delay is greater than the given PDB for the packet, the packet is said to violate the PDB, otherwise the packet is said to be successfully delivered. The value of the PDB may vary for different applications and traffic types, depending on the application, the value of the PDB can be 10-20 milliseconds (see TR 26.926).
[0029] According to R1-2112245, the 5G arrival time of data bursts on the downlink can be quasi-periodic, i.e., with jittery periodicity. Some factors that cause jitter in burst arrivals include different server rendering times, encoder times, RTP packet times, links between servers and 5G gateways, etc. 3GPP agreed to use a truncated Gaussian distribution to simulate the XR evaluation model DL traffic arrival jitter, with mean: 0ms, standard deviation: 2ms, range: [-4ms, 4ms] (baseline), [-5ms, 5ms] (optional).
[0030] Applications can have certain delay requirements for ADUs, which may not be adequately translated into packet delay budget requirements. For example, if the ADU delay budget (ADB) is 10ms, the PDB can be set to 10ms only if all packets of the ADU arrive at the 5G system at the same time. If the packets are dispersed, the ADU delay budget can be measured based on the arrival of the first packet of the ADU or the last packet of the ADU. In either case, a given ADB will result in different PDB requirements for different packets of the ADU. It is observed that specifying the ADB for 5G systems can be beneficial.
[0031] If the delay budget of a packet or ADU is known to one or both of the network entity (e.g., the gNB) and the scheduler in the UE, the gNB is able to take this information into account when scheduling transmissions. For example, the gNB is able to prioritize transmissions that are close to their delay budget limit instead of scheduling transmissions. The UE is also able to utilize this information to determine whether it can drop uplink transmissions, such as the Physical Uplink Control Channel (PUCCH) in response to a Physical Downlink Shared Channel (PDSCH), an UL Proposal, or a Physical Uplink Shared Channel (PUSCH) corresponding to a transmission that exceeds its delay budget. In addition, the UE may not wait for a retransmission of the PDSCH and retain an erroneously received PDSCH in its buffer for soft combining with a retransmission that never occurred. When using unlicensed spectrum, the UE can determine how much of its channel occupancy time can be shared with the gNB.
[0032] The remaining delay budget for downlink transmission can be indicated to the UE in downlink channel information (DCI), such as DCI for a grouping of a video frame, slice, or ADU, or via a medium access control control element (MAC-CE) for the video frame, slice, or ADU. The remaining budget for uplink transmission can be indicated to the gNB via uplink transmission (such as uplink control information (UCI), PUSCH transmission, etc.). The present disclosure provides embodiments of an apparatus and system for indicating such a remaining delay budget.
[0033] Embodiments of the present disclosure include a UE configured to transmit a signal indicating that a scheduled transmission is useless. In addition, embodiments provide criteria for determining data delays. The network can use this information to update the transmission schedule to replace the delayed data transmission, and the UE can discard the useless data. For example, the UE can transmit a signal indicating a future planned uplink transmission delay. In response, the network can allocate resources that would otherwise be used by the delayed transmission.
[0034] In some embodiments of the present disclosure, the UE may consider the interdependencies between different LCHs during uplink scheduling. The UE may suspend transmission of a specific LCH or bearer until a packet or ADU of another related bearer or LCH has been successfully transmitted.
[0035] Some embodiments relate to the behavior on the transmit side and the receive side when "unnecessary" packets are dropped on the transmitter side, including control signaling to inform the receiver of the dropped packets. Some embodiments take PDB into account during the Logical Channel Prioritization (LCP) procedure.
[0036] The technology described by the present disclosure can improve the efficiency of wireless systems by eliminating useless uplink transmissions. Eliminating unnecessary transmissions can reduce system interference and free up resources that can be allocated to useful transmissions. In addition, eliminating unnecessary transmissions can save power in UEs, thereby extending battery life.
[0037] Various aspects of the present disclosure are described in the context of a wireless communication system. Various aspects of the present disclosure are further illustrated and described with reference to device diagrams, flow charts related to efficient uplink communication.
[0038] Figure 1 An example of a wireless communication system 100 that supports efficient uplink communication according to various aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other embodiments, the wireless communication system 100 may be a 5G network, such as an NR network. In other embodiments, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support radio access technologies other than 5G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).
[0039] One or more base stations 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more base stations 102 described herein may be or include or may be referred to as a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. The base station 102 and the UE 104 may communicate via a communication link 108, which may be a wireless or wired connection. For example, the base station 102 and the UE 104 may communicate wirelessly via a Uu interface.
[0040] The base station 102 may provide a geographic coverage area 110, and the base station 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 110. For example, the base station 102 and the UE 104 may support wireless communications of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some embodiments, the base station 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some embodiments, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 110 may be associated with different base stations 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0041] One or more UEs 104 may be dispersed throughout the geographic area of the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term. In some embodiments, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally, or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc. In some embodiments, UE 104 may be stationary in the wireless communication system 100. In some other embodiments, UE 104 may move in the wireless communication system 100.
[0042] One or more UEs 104 may be devices of different forms or with different capabilities. Figure 1 Some examples of UE 104 are illustrated. UE 104 may be able to communicate with various types of devices, such as base station 102, other UE 104, or network equipment (e.g., core network 106, relay equipment, integrated access and backhaul (IAB) node, or another network device), such as Figure 1 Additionally, or alternatively, the UE 104 can support communications with other base stations 102 or UEs 104 that can act as relays in the wireless communication system 100 .
[0043] The UE 104 may also be capable of supporting direct wireless communications with other UEs 104 via a communication link 112. For example, the UE 104 may support direct wireless communications with another UE 104 via a device-to-device (D2D) communication link. In some embodiments, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 112 may be referred to as a side link. For example, the UE 104 may directly support wireless communications with another UE 104 via a PC5 interface.
[0044] The base stations 102 may support communications with the core network 106, or with other base stations 102, or both. For example, the base stations 102 may interface with the core network 106 via one or more backhaul links 114 (e.g., via S1, N2, N2 or other network interfaces). The base stations 102 may communicate with each other via backhaul links 114 (e.g., via X2, Xn or other network interfaces). In some embodiments, the base stations 102 may communicate with each other directly (e.g., between the base stations 102). In some other embodiments, the base stations 102 may communicate with each other or indirectly (e.g., via the core network 106). In some embodiments, one or more base stations 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmission-reception points (TRPs).
[0045] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some embodiments, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of one or more UEs 104 served by one or more base stations 102 associated with the core network 106.
[0046] Figure 2An example of a block diagram 200 of a device 202 supporting efficient uplink communications in accordance with aspects of the present disclosure is illustrated. The device 202 may be an example of a UE 104 described herein. The device 202 may support wireless communications with one or more base stations 102, UEs 104, or any combination thereof. The device 202 may include components for bidirectional communications, including components for transmitting and receiving communications, such as a communication manager 204, a processor 206, a memory 208, a receiver 210, a transmitter 212, and an I / O controller 214. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).
[0047] The communication manager 204, the receiver 210, the transmitter 212, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure described herein. For example, the communication manager 204, the receiver 210, the transmitter 212, or various combinations or components thereof, may support methods for performing one or more functions described herein.
[0048] In some embodiments, the communication manager 204, the receiver 210, the transmitter 212, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports means for performing the functions described in the present disclosure. In some embodiments, the processor 206 and the memory 208 coupled to the processor 206 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 208 by the processor 206).
[0049] Additionally or alternatively, in some embodiments, the communication manager 204, the receiver 210, the transmitter 212, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by the processor 206. If implemented in code executed by the processor 206, the functionality of the communication manager 204, the receiver 210, the transmitter 212, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).
[0050] In some embodiments, the communication manager 204 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 210, the transmitter 212, or both. For example, the communication manager 204 may receive information from the receiver 210, send information to the transmitter 212, or be integrated with the receiver 210, the transmitter 212, or both to receive information, transmit information, or perform various other operations described herein. Although the communication manager 204 is illustrated as a separate component, in some embodiments, one or more functions described with reference to the communication manager 204 may be supported or performed by the processor 206, the memory 208, or any combination thereof. For example, the memory 208 may store code that may include instructions executable by the processor 206 to cause the device 202 to perform various aspects of the present disclosure described herein, or the processor 206 and the memory 208 may be otherwise configured to perform or support such operations.
[0051] For example, the efficient uplink communication manager 204 can support wireless communication at a first device (e.g., device 202) according to examples disclosed herein. The communication manager 204 can be configured as or otherwise support a memory coupled to a processor, the processor configured to determine, based on a criterion, that first data stored in the memory for uplink transmission is not suitable for subsequent uplink scheduling, and trigger transmission of a control message indicating an amount of the first data that will not be provided in the uplink transmission.
[0052] The processor 206 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some embodiments, the processor 206 may be configured to operate a memory array using a memory controller. In some other embodiments, the memory controller may be integrated into the processor 206. The processor 206 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 208) to cause the device 202 to perform various functions of the present disclosure.
[0053] The memory 208 may include random access memory (RAM) and read-only memory (ROM). The memory 208 may store computer-readable, computer-executable code, including instructions, which, when executed by the processor 206, cause the device 202 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some embodiments, the code may not be directly executed by the processor 206, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some embodiments, the memory 208 may include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0054] I / O controller 214 can manage the input and output signals of device 202. I / O controller 214 can also manage peripheral devices that are not integrated into device 202. In some embodiments, I / O controller 214 can represent a physical connection or port to an external peripheral device. In some embodiments, I / O controller 214 can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX® or other known operating systems. In some embodiments, I / O controller 214 can be implemented as a part of a processor (such as processor 206). In some embodiments, a user can interact with device 202 via I / O controller 214 or via a hardware component controlled by I / O controller 214.
[0055] In some embodiments, the device 202 may include a single antenna 216. However, in some other embodiments, the device 202 may have more than one antenna 216, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously. The receiver 210 and the transmitter 212 may communicate bidirectionally via one or more antennas 216, wired or wireless links, as described herein. For example, the receiver 210 and the transmitter 212 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem to modulate packets, provide the modulated packets to one or more antennas 216 for transmission, and demodulate the packets received from the one or more antennas 216.
[0056] In an embodiment of the present disclosure, a symbol, a time slot, a sub-time slot, or a time transmission interval (TTI) may be a time unit having a specific duration. For example, a symbol may be a fraction or percentage of an OFDM symbol length associated with a specific subcarrier spacing (SCS). In the case where the priority may have gaps between transmissions, where the gaps are short enough in duration so that channel sensing or listen-before-talk (LBT) operations do not need to be performed between transmissions, an UL transmission (which may be a UL transmission burst) may consist of multiple transmission blocks of the same or different priorities. In addition, the UE and the base station with which the UE is communicating may know which transmission blocks (TBs) are associated with packets and / or application data units (ADUs), for example, through downlink control information (DCI) indications or MAC control element (MAC-CE) indications.
[0057] In an embodiment, the UE provides an indication to the network that scheduling uplink resources for some logical channels (LCH) and logical channel groups (LCG) is no longer valid. Some applications, especially those related to extended reality (XR), require data to be transmitted within a certain period of time in order for the application to use the data. Such data may be referred to as delayed or invalid data. The delayed data is no longer useful to the application, and the resources used to manipulate the delayed data (late data) are effectively wasted. Situations that lead to delayed data include high levels of packet loss, or when the packet data budget (PDB) is exceeded. Resources allocated to delayed data, such as configured grant (CG) resources, may be reallocated by the network.
[0058] In an embodiment, the UE informs the network, for example by signaling to the gNB, that no further UL resources are needed for UL transmission of a specific LCH or LCG or set of LCHs or sets of LCGs. This new signaling may be beneficial for embodiments where a frame can no longer be decoded due to a high percentage of packet loss of the frame or exceeding the PDB of an Application Data Unit (ADU) or frame. In these scenarios, it is useless to transmit the remaining data of the associated LCH, ADU or frame, as the application may not benefit from these transmissions. Instead, such transmissions result in unnecessarily increased UE power consumption and waste of radio resources, which has a negative impact on system capacity.
[0059] Figure 3 A flow chart of a method 300 for supporting efficient uplink communication according to aspects of the present disclosure is illustrated. The operations of the method 300 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 300 may be implemented by reference to Figure 1 and Figure 2The described UE 104 performs. In some embodiments, the device may execute an instruction set to control functional elements of the device to perform the described functions. Additionally, or alternatively, the device may use dedicated hardware to perform various aspects of the described functions. The method 300 may be performed only for certain data, such as data that cannot be used by the application if the data is delayed.
[0060] At 305, the method may include determining, based on a criterion, that first data for uplink transmission stored in the memory is not suitable for subsequent uplink scheduling. The operations of 305 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 305 may be described with reference to Figure 1 The device described performs the following.
[0061] For example, the UE may determine that the remaining packets of the ADU or frame still waiting for transmission in the buffer are no longer useful to the application, and therefore the remaining packets are delayed or invalid data. In an embodiment, the UE uses the lost packet information as a criterion to perform this determination. For example, the UE may compare the lost packet value (which may be the rate of lost packets or the number of lost packets) with a threshold. The amount of lost packets may be the amount of packets lost within a predetermined time. Specifically, the amount of lost packets may be the percentage of packets lost over a period of time. If the lost packet value exceeds the threshold, the UE may determine that the data associated with the ADU or frame in the UE's buffer is not suitable for subsequent uplink scheduling.
[0062] In another embodiment, the UE may compare the ADU or frame with the PDB. Specifically, the UE may determine the amount of time it will take to transmit the ADU or frame under current transmission conditions and compare it with the PDB. If the time to transmit the ADU or frame exceeds the PDB, the UE determines that the data in the ADU or frame is delayed data and is not suitable for subsequent uplink scheduling. In an embodiment, the UE may distinguish between useful data that can still be transmitted within the associated PDB and data that is not suitable for subsequent uplink scheduling, data that can be used for transmission (e.g., in a transmission buffer). In an embodiment, the UE may specify information in the buffer based on whether the data is expected to be transmitted within the PDB. Determining that the data in the UE buffer is delayed data may trigger the generation of a control signal.
[0063] At 310, the method may include generating a control signal. In an embodiment, the control signal indicates to the base station that the buffer status of the previously reported LCG is no longer valid. The operations of 310 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 310 may be described with reference to Figure 1 The control signal may indicate that the data reported in the previous BSR continues to be valid or is no longer valid, such as the delayed data determined at 305 .
[0064] The control signal generated at 310 may include a new buffer status report (BSR). For example, the UE may generate a BSR reporting zero bytes for each LCH or LCG associated with data (e.g., delayed data) that is not expected to be transmitted within a predetermined time at 305. Thus, the control signal may indicate an amount of data from the UE's buffer that will not be provided in an uplink transmission.
[0065] In an embodiment, the control signal generated at 310 may be a BSR indicating only timely or useful data. In such an embodiment, the BSR indicating only useful or valid data may replace the previously reported BSR. The UE may discard the delayed data and generate a new BSR at 310 using the timely or valid data remaining in the UE's buffer.
[0066] In an embodiment, at 310, the UE may generate a new scheduling request (SR). The new SR may inform the network that the data in the UE's buffer has been delayed, as determined at 305. The SR may include an indication that informs the network that delayed data is waiting in the buffer for the associated LCH (mapping between LCH and SR configuration) and that no additional uplink resources are specified for the associated data. Thus, the new SR may be a negative SR that informs the network not to allocate uplink resources as scheduled.
[0067] In an embodiment, the control signal is a new PUCCH format that includes an indication with two bits indicating three different states. The first state of the SR may indicate that a BSR has been triggered, for example for legacy purposes. The second state may indicate that there is no valid or useful data in the UE buffer, and may be specified when there is delayed data in the UE's buffer. The third state may indicate no SR.
[0068] When the network receives a control signal indicating the second state, the network is notified that the resources previously identified for uplink transmission are no longer valid. The network may deactivate the configuration grant (CG) PUSCH resources allocated to the UE and may reallocate these resources to different communications. The indication may be performed by multiplying the SR data by an orthogonal sequence to provide three states. After transmitting the control signal indicating the second state, the UE may not monitor the PDCCH for uplink DCI associated with the delayed data.
[0069] When the control signal is a BSR, the UE may generate a long BSR or a short BSR for a regular or periodic BSR. If more than one LCG is associated with valid and timely data for uplink transmission, the UE may generate and transmit a long BSR for all LCGs with valid and timely data. Otherwise, the UE may generate and transmit a short BSR. In an embodiment, if at least one additional LCH or LCG has useful data, or if at least one additional LCH or LCG has delayed data that was not reported to the base station in a previous BSR that has been explicitly or implicitly acknowledged by the base station, the UE generates and transmits a long BSR when a new BSR is triggered.
[0070] In an embodiment, the UE may generate and transmit an ACK as HARQ feedback for downlink transmission associated with the ADU or frame including delayed data determined at 305. The ACK may be transmitted regardless of the decoding result. In such an embodiment, the soft buffer may be flushed.
[0071] At 320, the method may include skipping uplink transmission. The operations of 320 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 320 may be described with reference to Figure 1 The device described performs the following.
[0072] Skipping uplink transmission at 320 may include skipping the UL DCI for delayed or inappropriate data determined at 305. In an embodiment, the UE skips transmission using a new criterion as a result of the determination at 305.
[0073] Figure 4 A flow chart of a method 400 for supporting processes associated with authorization of configuration according to aspects of the present disclosure is illustrated. The operations of the method 400 may be implemented by the devices described herein or components thereof. For example, the operations of the method 400 may be implemented by reference to Figure 1 and 2 The UE 104 described herein performs. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.
[0074] In method 400, a UE having delayed data in its buffer and to which CG PUSCH resources have been allocated may indicate to the network that the CG PUSCH configuration or CG configuration group should be deactivated and / or that the CG PUSCH resources of the CG configuration can be reallocated, for example, to other users.
[0075] At 405, the method may include providing an SR. The operations of 405 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 405 may be described by reference to Figure 1 The device described performs the following.
[0076] If one or more CG configurations are activated for the UE, the UE may generate and transmit an SR associated with the CG configuration, which indicates that one or more CGs can be deactivated. When the CG configuration is activated, normal SR transmission may be prohibited for the LCH mapped to the CG configuration, in which case, Configuration can be used for SR. When CG configuration is disabled, SR linked to CG configuration (LCH to CG mapping) can indicate that there is valid or timely data in the UE buffer.
[0077] At 410, the method may include generating configured grant uplink control information (CG-UCI). The operations of 410 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 410 may be described by reference to Figure 1 The device described performs the following.
[0078] Here, the CG-UCI may include information about the length of time that the UE has not used CG resources or which CG PUSCH resources of the CG PUSCH configuration have not been used by the UE for uplink transmission. In other words, the CG-UCI may provide pause information related to the amount of time that the CG resources are not suitable or not used. For example, the CG-UCI may indicate an amount of time, such as the number of milliseconds or intervals of a CG configuration or a CG configuration group. The amount of time may be associated with the amount of delayed or invalid data stored in the UE's buffer.
[0079] In an embodiment, this amount of time may be associated with the expected time that data for a subsequent ADU will be available for transmission. In such an embodiment, the CG-UCI may indicate to the network that CG resources are no longer applicable for the current ADU or frame that is not expected to be transmitted in a timely manner, but CG resources are requested for the next transmission.
[0080] At 410, a CG-UCI may be generated when a hybrid automatic repeat request (HARQ) process ID is given by a formula. In such an embodiment, the CG-UCI content may be different compared to an embodiment in which New Radio Unlicensed (NR-U) is used.
[0081] At 415, the method may include adapting a logical channel priority (LCP) limit. The operations of 415 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 415 may be described with reference to Figure 1 The device described performs the following.
[0082] When there is no valid or timely data associated with CG resources in the UE's buffer, the UE can adaptively change the LCP restriction rules. For example, the UE can adapt the mapping of LCH to CG to map valid or timely data to CG resources and remove the mapping between invalid data and CG resources.
[0083] At 420, the method may include lowering the priority of the CG. The operations of 420 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 420 may be described by reference to Figure 1 The device described performs the following.
[0084] In one embodiment, the UE treats the configuration grant associated with the delayed data as a grant with a lower priority. A MAC entity of a configured uplink grant may be considered as a reduced priority uplink grant if the corresponding PUSCH transmission of the configured uplink grant is cancelled by the CI-RNTI as specified in clause 11.2A of TS 38.213 or by a high PHY priority PUCCH transmission as specified in clause 9 of TS 38.213, or the remaining delay budget of the associated packet or ADU is exceeded or the number of packet errors of the associated ADU exceeds the target. If the reduced priority uplink grant is configured with , then the corresponding HARQ process of the downgraded uplink grant (if running) is stopped.
[0085] Figure 5 A flow chart of a method 500 for supporting discarding delayed data stored in a buffer of a UE according to aspects of the present disclosure is illustrated. The operations of the method 500 may be implemented by an apparatus described herein or a component thereof. For example, the operations of the method 500 may be implemented by reference to Figure 1 to Figure 2 The described UE 104 performs, while some elements may be performed by the base station 102 or other network entities. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. Additionally, or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.
[0086] At 505, the method may include determining a service data unit (SDU) associated with the ADU or frame associated with the delayed data determined at 305. The operations of 505 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 505 may be described with reference to Figure 1 The device described performs the following.
[0087] In an embodiment, at 505, the UE or PDCP transmitting entity determines which PDCP SDUs are associated with ADUs or frames that are not expected to be transmitted in time to be useful to the application. In one example, a Service Data Adaptation Protocol (SDAP) header is provided with an ADU index or sequence number (SN), and SDUs belonging to the same ADU or frame all have the same index or SN. That is, the SDUs are associated with the ADU or frame by a shared index or SN.
[0088] In another example, a transmitting entity such as a PDCP layer informs the receiving UE of the PDCP SNs belonging to the same ADU or frame. In one example, this information can be transmitted within a PDCP control PDU. Therefore, a PCDP transmitting entity that knows the ADU or frame size can inform the UE of the association, and the determination of the SDU associated with the ADU or frame can be performed by the UE through information from the PCDP transmitting entity.
[0089] At 510, the method may include setting a PDCP discard timer for the ADU or frame. The operations of 510 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 510 may be described with reference to Figure 1 The device described performs the following.
[0090] In an embodiment, at 510, the UE or PDCP transmitting entity ensures that the PDCP discard timer has the same value for each PDCP service data unit (SDU) associated with the ADU or frame. In one embodiment, the PDCP discard timer is maintained at the ADU or frame level so that the PDCP SDUs associated with the ADU or frame are treated identically with respect to the PDCP discard timer manipulation. Assigning the same discard timer to the SDUs associated with the ADU or frame can ensure that the PDCP discard timers of all PDCP SDUs associated with the ADU or frame expire at the same time.
[0091] At 515, the method may include applying a discard timer for an SDU to the SDU set. The operations of 515 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 515 may be described with reference to Figure 1 The device described performs the following.
[0092] As an alternative to 510, at 515, when the PDCP discard timer of one of the PDCP SDUs of the ADU or frame (e.g., the first or earliest PDCP SDU) expires, the UE or PDCP transmitting entity considers that the PDCP discard timers of all PDCP SDUs associated with the ADU / PDU set or frame have expired. In this embodiment, all SDUs associated with the delayed ADU or frame are discarded using a single timer value instead of changing the corresponding timer values as described for 510. From the PDCP perspective, PDCP discard based on the PDCP discard timer can be performed on a per ADU or per frame basis.
[0093] At 520, the method may include notifying a receiving entity of packets discarded by a transmitter (e.g., a UE), and at 525, the receiving entity may adjust parameters based on the discarded packet information. The operations of 520 and 525 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 520 and 525 may be described with reference to Figure 1 The device described performs the following.
[0094] Dropping the packet at the transmitter side may include notifying a corresponding receiving entity of the dropped packet at 520. Specifically, the receiving entity (e.g., UE) may be notified of the SDU dropped by the UE. The receiving entity may update its receiving window based on an identifier of the dropped packet (such as an SN of the dropped packet) and may block a request for RLC retransmission of the dropped RLC SDU at 525. Otherwise, the receiving entity may assume that the packet has been lost and request retransmission of data that is no longer useful to the application.
[0095] Specifically, when receiving information about the discarded packet, the T reordering timer in the PDCP layer or the T reassembly timer in the RLC may be updated or stopped. In addition, the UE may refuse to transmit a radio link control (RLC) status report of the discarded packet or a PDCP status report of the discarded packet. Therefore, the UE may adjust its parameters and the receiving entity at 525.
[0096] In an embodiment, a new RLC control or status RLC protocol data unit (PDU) is transmitted which indicates to the RLC receiving entity which packets or SDUs have been discarded, for example by providing the SN value of the discarded RLC SDU. In an embodiment, the RLC transmitting entity notifies the receiving entity of the discarded packets using a new PDU format at 520, wherein the RLC PDU associated with the discarded RLC service data unit SDU includes a header with an SN value but without any payload. In an embodiment, an ADU may be used instead of a PDU set and vice versa.
[0097] Upon receiving a new RLC control or status PDU or a new RLC PDU format, the receiving entity may update its timer status and receive window status. For example, the receiving entity may update RX_NEXT, which serves as the lower limit of the receive window. The RLC entity may notify the PDPC layer on the receiving side of the discarded packets so that the PDCP can update the timer status (e.g., T reordering timer) and the receive window.
[0098] In an embodiment, when the PDB or discard timer expires and the relevant PDCP SDU contained in the transport block (TB) is located in the HARQ buffer waiting for retransmission, the UE may discard the TB and no longer retransmit it. Specifically, the UE may ignore the dynamic grant (DG) for retransmission and not perform autonomous retransmission. Therefore, at 525, the UE may adjust its parameters to avoid retransmitting data that is no longer useful to the application.
[0099] In an embodiment where the timer of the PDB controlling the ADU expires, the MAC may notify the higher layer of the timer expiration. This timer event may be used to trigger certain operations of the RLC / PDCP layer, including advancing the RLC receive window, not requesting RLC retransmission through RLC status report or PDCP retransmission, etc., depending on where the timer is maintained.
[0100] For example, the UE may start a counter or timer of a remaining delay budget (RDB) value based on a received DCI indicating an RDB. The RDB may be the amount of time remaining in the PDB. The time or count may be decremented for each time slot associated with the ADU or frame, and when the counter or timer expires, at 305, the UE determines that the delay budget of the ADU or frame has been exceeded. Then, at 315, the UE may indicate to a higher layer (such as an application layer) that the delay budget of the frame or ADU has been exceeded. If the counter or timer is running and another DCI indicating an RDB for the ADU or frame is received, the counter or timer will be restarted with one or more newly indicated RDB values.
[0101] Since the application layer may not benefit from delayed packets, it is helpful to ensure that packets are successfully received within relevant delay bounds. The probability of packet delay can be reduced by enhancing the Logical Channel Prioritization (LCP) process.
[0102] Figure 6 600 according to various aspects of the present disclosure. The operations of the method 600 may be implemented by the device described herein or its components. For example, the operations of the method 600 may be implemented by reference to Figure 1 and Figure 2The described UE 104 performs. In some embodiments, the device can execute an instruction set to control the functional elements of the device to perform the described functions. Additionally, or alternatively, the device can use dedicated hardware to perform various aspects of the described functions.
[0103] At 605, the method may include establishing a logical channel in response to the configuration. The operations of 605 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 605 may be described with reference to Figure 1 The described device performs.
[0104] The configuration of 605 may be an RRC reconfiguration message for establishing a radio bearer. The RRC reconfiguration message includes An information element (IE) that carries LCH specific configuration fields including the priority value of the logical channel. This configuration may be received by the UE from a network entity such as a base station, e.g., a gNB.
[0105] In an embodiment, a radio bearer or logical channel is configured with a new field indicating that the LCH or radio bearer carries traffic for which special treatment is applied during the LCP procedure. The new field may be Field within the information element. This field may indicate whether the priority value of the bearer or LCH can be adapted, or is static. Additionally, or alternatively, this field may indicate that the LCH or bearer carries XR traffic.
[0106] In other implementations of this embodiment, the DCI (e.g., UL DCI) that allocates uplink resources for the initial transmission indicates within a field whether the uplink resources are specifically allocated to LCHs or radio bearers (RBs) carrying certain traffic (such as XR traffic). In one example, such a field is a 1-bit flag.
[0107] In response to receiving a UL DCI with an indication that uplink resources are reserved for certain bearers or LCHs (e.g., bearers or LCHs carrying XR traffic), the UE may consider only those LCHs configured by the network for which uplink MAC SDUs from that logical channel can be transmitted on PUSCH resources reserved for certain bearers or LCHs, e.g. The field in indicates the presence of an LCH or radio bearer carrying specific traffic.
[0108] In one example, a field in the DCI indicates whether PUSCH resources are reserved for XR traffic. In a particular embodiment, a field in the DCI may indicate whether PUSCH resources are reserved for I frames or P frames. The field within the IE may indicate whether the MAC SDU of the LCH is allowed to be transmitted on the PUSCH resources allocated by the DCI. Therefore, this field may be a restriction on the LCH.
[0109] At 610, the method may include determining a priority value for one or more logical channels. The priority value may be determined based on a logical channel priority from a network entity and a first parameter associated with uplink data allocated to the logical channel. The operations of 610 may be performed according to examples described herein. In some embodiments, aspects of the operations of 610 may be described with reference to Figure 1 The device described here performs the following. A specific embodiment of determining the priority value of a logical channel is described with respect to method 700.
[0110] At 615, the method may include allocating resources to a logical channel having a determined priority based on the priority value determined at 610. The operations of 615 may be performed according to examples described herein. In some embodiments, aspects of the operations of 615 may be described with reference to Figure 1 The described device performs the following. The resources allocated to the logical channel may be resources allocated by the uplink grant or UL DCI received at 605 .
[0111] Figure 7 A flow chart of a method 700 for supporting determination of a priority value of a logical channel according to aspects of the present disclosure is illustrated. The operations of the method 700 may be implemented by an apparatus described herein or a component thereof. For example, the operations of the method 700 may be implemented by reference to Figure 1 and Figure 2 The UE 104 described herein performs. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.
[0112] At 705, the method may include determining a residual delay budget (RDB). The operations of 705 may be performed according to examples described herein. In some embodiments, aspects of the operations of 705 may be described by reference to Figure 1 The device described performs the following.
[0113] In an embodiment, the RDB is the difference between the PDB of the ADU, frame or packet and the current time, or the amount of time remaining in the PDB. Thus, determining the RDB may include determining the difference between the current time and the PDB of the ADU, frame or packet. The difference is the amount of time remaining in the delay budget.
[0114] At 710, the method may include comparing the remaining delay budget to a predetermined value. The operations of 710 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 710 may be described by reference to Figure 1 The device described performs the following.
[0115] In an embodiment, when the packets waiting for transmission of the LCH are close to the PDB, the UE increases the priority of the LCH. At 710, the condition can be determined by comparing the RDB with a threshold, and at 715, the priority can be increased when the remaining delay budget of the ADU, frame or packet is below the threshold.
[0116] The threshold may be a preconfigured value that is set. For example, the threshold may be a time, such as the number of milliseconds before the PDB expires. In such an embodiment, the UE may increase the priority of the LCH based on comparing the RDB with the preconfigured value.
[0117] At 715, the method may include increasing a logical channel value or a channel access priority class (CAPC). The operations of 715 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 715 may be described by reference to Figure 1 The device described performs the following.
[0118] In an embodiment, the LCH priority is increased by a predefined step value. For example, the LCH priority may be increased according to the following algorithm: The LCH priority is an integer value between 1 and 8, with 1 being the highest priority. Therefore, the value of X can be an integer equal to or greater than 1.
[0119] Additionally or alternatively, the LCH priority may be set to 1, or the highest LCH priority. In an embodiment, the LCH priority may be set to 1 depending on the difference between the RDB and the PDB. In such an embodiment, if the UE determines that the RDB is equal to or less than a predetermined value, the priority is raised to the highest possible level. For example, if the remaining delay budget is within X milliseconds of the packet delay budget, the priority value of the LCH may be set to 1.
[0120] In another embodiment, when the RDB of the packets of the LCH waiting for transmission falls within a predefined range, the UE increases the priority of the LCH step by step. The steps can be a series of priority values, and the priority depends on the RDB being increased by these priority values. For example, when the RDB is less than a first predetermined value, the UE can increase the LCH priority by a first step size, and when the RDB is less than a second predetermined value, the UE can increase the LCH priority by a second step size, and so on. The values of the step sizes can be the same or different and can increase as the RDB decreases. In an embodiment, one or more LCHs with an RDB equal to or less than a predefined threshold are processed with a higher priority than a MAC control element (CE).
[0121] At 715, when the UE is operating in a shared spectrum environment, when the RDB is less than a preconfigured threshold for the following situation, when a transport block (TB) performing listen-before-talk (LBT) contains data associated with an RDB less than the preconfigured threshold, the UE may increase the CAPC (channel access priority class). In such an embodiment, the CAPC may be treated the same as the priority value described above. For example, the CAPC may be incremented, set to the highest priority class, adjusted to different levels depending on the RDB, etc.
[0122] In an embodiment, when the UE is power limited based on the RDB of a packet, frame, or ADU, the UE may prioritize data of certain LCHs or other uplink channels over other uplink data. For example, the UE may prioritize a PUSCH transmission of a MAC SDU carrying an LCH whose RDB is less than a preconfigured threshold over another PUSCH transmission or a specific PUCCH transmission to ensure that the PDB is not exceeded.
[0123] In an embodiment, RDB is considered when determining the priority order of UL channels in a UE power limited situation. For example, power scaling or dropping of UL channel transmissions may be applied.
[0124] At 720, the method may include providing a control signal based on the remaining delay budget. The operations of 720 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 720 may be described with reference to Figure 1 The device described performs the following.
[0125] In an embodiment, the UE indicates the RDB of the corresponding data for which the buffer level is reported in the BSR. In one example, the BSR may include the RDB value for each LCH or LCG in the BSR.
[0126] The UE may trigger a BSR or SR when the RDB of data waiting to be transmitted is below a configured threshold. In such an embodiment, the UE may ignore the SR prohibit timer and trigger an SR even if the SR prohibit timer is running. The UE may trigger an SR only for specific or pre-configured logical channels when the RDB is below the threshold for these logical channels.
[0127] Certain applications have dependencies between different data streams. This is especially true for video data, especially for XR applications. Embodiments of the present disclosure may take into account certain interdependencies between the transmission of different bearers, LCHs, or streams. For example, frame or ADU-level QoS constraints for XR and dependencies of different QoS streams may be provided.
[0128] XR services include multiple types of data, which may include I frames or P frames of video streams, audio streams, gesture and control streams, etc. Different streams may correspond to different QoS flows or radio bearers and may have different QoS requirements, and there may be dependencies between different streams. For example, the decoding of a P frame may depend on the decoding of the latest I frame.
[0129] Figure 8 A flow chart of a method 800 for supporting dependencies between data and associated processes according to aspects of the present disclosure is illustrated. The operations of the method 800 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 800 may be implemented by reference to Figure 1 and Figure 2 The described UE 104 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.
[0130] At 805, the method may include receiving a signal indicating that bearers with related data are linked. The operations of 805 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 805 may be performed by reference to Figure 1 The device described performs the following.
[0131] At 805, a bearer may be linked to another bearer. In one example, a radio bearer or radio link control (RLC) bearer is linked to one or more radio bearers or RLC bearers. Examples of linked bearers include a radio bearer carrying I frames that is linked to one or more bearers carrying P frames. Another example is mapping the transmission of left-eye and right-eye video streams to two linked bearers or LCHs. Thus, bearers may be linked when the data of the linked bearers have some association or dependency between them.
[0132] Linking the bearer may include providing data to a data field indicating a link. In one example, The new field in the IE indicates one or more identities of the associated radio bearer. For example, The IE may contain a field referencing the identity of one or more associated bearers, such as a Data Radio Bearer Identity (DRB ID). Fig. 9 An example of an IE 900 having a field for an associated DRB identifier is provided in FIG. According to another example, The IE includes a field identifying the associated RLC bearer or logical channel.At 805, the UE may receive the IE.
[0133] At 810, the method may include pausing transmission of data associated with the link bearer. The operations of 810 may be performed according to examples described herein. In some embodiments, aspects of the operations of 810 may be described with reference to Figure 1 The device described performs the following.
[0134] In an embodiment, the UE suspends transmission of the first data of the first LCH until transmission of the second data of the second LCH has been confirmed by the network. For example, at 805, when the first data is linked to the second data (e.g., by linking the bearer or channel of the data), the UE may suspend transmission of the first data until an event, such as an ACK that the second data has been successfully received by the network entity. In another embodiment, the UE may suspend transmission of the first data until some other event occurs (such as expiration of a timer).
[0135] In an example, the UE transmits an I frame and pauses transmitting the associated P frame until receipt of the I frame is acknowledged by a network entity. Upon receiving an explicit acknowledgement, such as an ACK, or an implicit acknowledgement such as timer expiration, the UE removes the pause and transmits a P frame linked to the I frame.
[0136] In one example, the UE should poll the RLC status report to confirm the reception of the I frame after transmitting the I frame or the last PDCP / RLC PDU of the I frame. Alternatively, and according to another example, the UE or other transmitting entity may request the transmission of the PDCP status report after transmitting the I frame.
[0137] In one example, it is configured by the network whether the UE suspends an LCH (such as an LCH carrying a P frame) until the data for transmitting another LCH is confirmed, because for some use cases, suspension may not be appropriate. In other words, the UE can be configured to suspend link data or not suspend link data in certain situations. When the UE is configured with carrier aggregation, I frames and P frames may be transmitted or mapped on different carriers. For this scenario, suspending the LCH carrying P frames until the transmission of I frames is confirmed may not be appropriate.
[0138] At 815, the method may include pausing the prioritization process. The operations of 815 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 815 may be described by reference to Figure 1 The device described in the embodiment of the present invention performs. Specifically, the prioritization process suspended at 815 can be the logical channel prioritization process 600 discussed above. If the first data is not received within the PDB, any data associated with the first data may not be of any use to the application. Therefore, resources can be saved by waiting until the first data is confirmed to be received before raising the priority of the second data.
[0139] At 820, the method may include suspending BSR reporting. The operations of 820 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 820 may be described with reference to Figure 1 The device described performs the following.
[0140] In an embodiment, for a bearer carrying first data (such as a P frame), BSR reporting is suspended until transmission of second data (such as an I frame) is confirmed. In an example, when data for an LCH is suspended, the data is considered unavailable for the LCH, at least for the purpose of BSR reporting.
[0141] In an embodiment, a new type of bearer is used to transport QoS flows consisting of packets of different priorities. Examples of such bearers are XR bearers carrying separate streams of left-eye and right-eye video or separate streams of I and P frames. In one example, a bearer consists of a PDCP entity with two or more associated RLC entities, which is similar to a split bearer.
[0142] Fig.10 An example of a protocol stack for splitting bearers with different priorities according to aspects of the present disclosure is illustrated.
[0143] like Fig.10 As shown, data is sent from a higher layer (which may be an IP layer) to the SDAP layer and then transmitted to the PDCP layer. According to an embodiment, one PDCP entity may be associated with multiple RLC entities or logical channels, which may have different logical channel priorities to support packets of different priorities within one radio bearer or QoS flow.
[0144] For example, an XR traffic QoS flow may support critical packets that have a higher priority or urgency than other packets. These high priority packets may take precedence over other packets within the same radio bearer or QoS flow. In one example, a left eye video stream may be mapped to one RLC entity or LCH, while a right eye video stream may be mapped to another RLC entity or LCH associated with the same PDCP entity.
[0145] Fig.11 100 is a flowchart of a method 1100 for supporting different bearer priorities according to aspects of the present disclosure. The operations of the method 1100 may be implemented by the devices described herein or components thereof. For example, the operations of the method 1100 may be implemented by reference to Figure 1 to Figure 2 The described UE 104 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. Additionally, or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.
[0146] In an embodiment, the SDAP layer provides an indication in the SDAP header that is used to route the SDU to different RLC entities associated with the PDCP layer. In a traditional environment, the SDAP data PDU may include an optional 1-byte header. Uplink and downlink SDAP headers may be configured per DRB. In another embodiment, such packet marking or labeling may be performed by a higher layer, such as an application layer.
[0147] The downlink SDAP header may include a 1-bit RDI (reflective QoS flow indicated to the DRB mapping), a 1-bit RQI (reflective QoS indication), and a 6-bit QFI (QoS flow identifier). The uplink SDAP header includes the QFI. In one example, a new field is included in the SDAP header that indicates routing information, such as whether a packet or PDCP SDU is a high priority packet for routing to a high priority RLC entity in the PDCP layer. In such an embodiment, a high priority SDU may be routed to a high priority LCH associated with the PDCP entity. Conversely, a low priority SDU may be routed to a low priority LCH associated with the PDCP entity based on the data in the new field.
[0148] At 1105, the method may include receiving a tagged SDU at the UE. The operations of 1105 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 1105 may be described with reference to Figure 1 The device described performs the following.
[0149] In an embodiment, a PDCP entity in a UE receives an SDU with a tag indicating whether the SDU is considered urgent, and receives routing information that can be used in the PDCP layer for routing to an appropriate RLC entity or LCH. A PDCP PDU containing an SDU marked as a high priority packet will be submitted to another RLC entity that handles such a critical packet (an RLC entity other than the RLC entity for "normal" packets). If there are different urgency levels, the PDCP PDU containing such an SDU may be submitted to the RLC entity that handles the corresponding urgency level. Therefore, a specific RLC entity or LCH may support the corresponding urgency level.
[0150] At 1110, the method may include calculating the PDCP SDU size. The operations of 1110 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 1110 may be described with reference to Figure 1 The device described performs the following.
[0151] In an embodiment, the UE calculates the bearer data volume as the sum of the PDCP data volume and the data volume of the associated RLC entity for buffer status reporting.In an example, multiple RLC entities associated with a PDCP entity may be mapped to the same LCG.
[0152] In another example, the UE splits the data amount of a common PDCP entity among multiple associated RLC entities in order to calculate the data amount of each RLC bearer so that the data amount of the RLC bearer corresponds to the sum of the RLC data amount and the PDCP data amount associated with the corresponding RLC entity.
[0153] At 1115, the method may include routing the PDCP data unit to different priority RLCs. The operations of 1115 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 1115 may be described with reference to Figure 1 The device described performs the following.
[0154] At 1115, the UE may route PDCP data units having different urgency values or priority values to different RLCs having corresponding urgency values. Fig.10 Only two urgency levels (high and low) are shown in FIG. 1 , but in other embodiments, there may be more than two urgency levels.
[0155] In an embodiment where the PDCP entity is associated with two different RLC entities (e.g., one for left-eye video and another LCH for right-eye video), the PDCP data volume is split into two parts, one of which corresponds to the left-eye PDCP SDU or PDU and the other corresponds to the right-eye PDCP SDU or PDU. The data may also be split based on other factors.
[0156] In another example, routing the PDCP PDU or SDU to the associated RLC entity or LCH is performed based on the packet size or PDCP SDU size determined at 1115. According to one embodiment, the UE may route the PDCP PDU or SDU to the associated RLC entity depending on whether the PDCP SDU size is greater than a predefined threshold.
[0157] In an embodiment, a PDCP entity is associated with two RLC entities, which are configured to carry I frames and P frames, respectively. Since the average packet size of I frames is much larger than the average packet size of P frames, the PDCP entity may consider performing PDCP SDU routing based on packet size. For example, when the PDCP SDU size is greater than a preconfigured threshold, the corresponding PDCP PDU may be routed to the first RLC entity, while other PDCP PDUs whose PDCP SDU size is less than the preconfigured threshold may be routed to a second RLC entity having a different urgency level from the first RLC entity.
[0158] Although embodiments have been described for left-eye and right-eye information and I-frame and P-frame data, the scope of the present disclosure is not limited to these specific examples. Those skilled in the art will recognize that a variety of different implementations may be used to minimize the likelihood that data is transmitted in time to be useful to the application, and to prevent the transmission of data that is no longer useful to the application.
[0159] It should be noted that the methods described herein describe possible implementations, and that operations and steps may be rearranged or otherwise modified or omitted, and that other implementations are possible. In addition, aspects of two or more methods may be combined.
[0160] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0161] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium or transmitted by a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented in different physical locations.
[0162] Computer-readable media include non-transitory computer storage media and communication media, which include any media that facilitate the transfer of computer programs from one place to another. Non-transitory storage media can be any available media that can be accessed by a general-purpose or special-purpose computer. As an example and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to carry or store the required program code means in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.
[0163] Any connection can be properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwave are all included in the definition of computer-readable media. Disks and discs, as used herein, include CDs, laser discs, compact discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs use lasers to reproduce data optically. Combinations of the above are also included within the scope of computer-readable media.
[0164] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one" or "one or more") indicates an inclusive list, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". In addition, as used herein, including in the claims, a "set" may include one or more elements.
[0165] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be implemented without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0166] The description herein is intended to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should conform to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A device for wireless communication, comprising: processor; as well as a memory coupled to the processor, wherein the processor is configured to: determining, based on a criterion, that first data for uplink transmission stored in the memory is not suitable for subsequent uplink scheduling; and The transmission of a control message is triggered, the control message indicating an amount of the first data which is not to be provided in an uplink transmission.
2. The device according to claim 1, wherein: The first data is associated with at least one of a logical channel and a logical channel group.
3. The device according to claim 1, wherein: The first data is stored in at least one of a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer.
4. The device according to claim 1, wherein: The criterion is based on at least one of a timer status and a packet loss threshold.
5. The device according to claim 4, wherein: The timer is associated with a packet delay budget, and the criterion is expiration of the timer.
6. The device according to claim 4, wherein: The threshold is associated with at least one of a packet loss rate and a percentage of lost packets, and the criterion is exceeding the threshold.
7. The device according to claim 1, wherein: The control message is a MAC control element.
8. The device according to claim 7, wherein: The MAC control element includes a buffer status report (BSR).
9. The device according to claim 1, wherein: The control message is a scheduling request transmitted on the Physical Uplink Control Channel (PUCCH).
10. The device according to claim 1, wherein: The criterion is that the application data budget of the application data unit is exceeded.
11. A method performed by a user equipment in a telecommunications network, the method comprising: determining, based on a criterion, that first data for uplink transmission stored in a memory of the user equipment is not suitable for subsequent uplink scheduling; generating a control message indicating an amount of the first data that is not to be provided in an uplink transmission; as well as The control message is transmitted to a base station.
12. The method according to claim 11, wherein: The first data is associated with at least one of a logical channel and a logical channel group.
13. The method according to claim 11, wherein: The first data is stored in at least one of a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer.
14. The method according to claim 11, wherein: The criterion is based on at least one of a timer status and a packet loss threshold.
15. The method according to claim 14, wherein: The timer is associated with a packet delay budget, and the criterion is expiration of the timer.
16. The method according to claim 14, wherein: The threshold is associated with at least one of a packet loss rate and a percentage of lost packets, and the criterion is exceeding the threshold.
17. The method according to claim 11, wherein: The control message is a MAC control element including a buffer status report (BSR).
18. The method according to claim 11, wherein: The control message is a scheduling request transmitted on the Physical Uplink Control Channel (PUCCH).
19. The method according to claim 11, wherein: The criterion is that the application data budget of the application data unit is exceeded.
20. A wireless communication device, comprising: processor; as well as a memory coupled to the processor, wherein the processor is configured to: receiving a control message from a user equipment (UE), the control message indicating an amount of first data stored in a memory of the UE that is not to be provided in an uplink transmission; updating a receive window for the uplink transmission; as well as Retransmission requests for discarded service data units associated with the first data are prevented.
