Wireless communication method, user equipment and base station

Abstract

The invention discloses an uplink resource processing method, which is executed by user equipment (UE), and comprises the following steps of: reporting a buffer status report (BSR) containing time delay to a base station; or obtaining the indication of the uplink resource allocated by the base station from the base station; the uplink resource allocation method comprises the following steps of: in a logical channel priority (LCP) process, allocating an uplink resource to a logical channel (LCH) with time delay information, or in a logical channel priority (LCP) process, allocating the uplink resource to the logical channel (LCH) with the time delay information.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an uplink resource processing method, a user equipment (UE) and a base station. Background Art

[0002] 5G wireless communication systems are designed to provide traditional services such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC). In 5G or NR, the functions supporting eMBB, URLLC, and mMTC have been introduced in 3GPP Release 15 and enhanced in Release 16 and Release 17.

[0003] Extended reality (XR) is a general term for augmented reality (AR), mixed reality (MR), and virtual reality (VR). XR applications usually require high throughput and low latency. Cloud gaming is another application with the same requirements. XR and cloud gaming are important applications supported by 5G.

[0004] XR services are characterized by their special traffic data streams, which have real-time, high data rate and low latency characteristics. XR video streams are composed of different frames / video slices. For example, a group of picture (GOP) contains I frames, P frames and B frames. The 5G system needs to consider and support the special characteristics of this XR service flow.

[0005] Extended reality (XR) and cloud gaming services are important media applications supported by 5G. In 3GPP, a series of research projects have been conducted and it has been found that XR services have some unique characteristics, and the current 5G system may not be able to support XR services well.

[0006] Technical issues

[0007] For traditional services, when scheduling uplink service resources, the gNB usually allocates resources based on the buffer size information reported by the UE in the buffer status report (BSR). XR services may use the same mechanism. In addition, in the 5G system, traditional services and XR services may exist at the same time, and the gNB needs to schedule both services at the same time. Due to the characteristics of large data volume and jitter of XR services, in order to more accurately support XR BSR, 3GPP decided to enhance the XR BSR so that it can report latency information and buffer size information at the same time. When the BSRs of two services (XR services and traditional services) are reported at the same time, how does the gNB perform differentiated scheduling based on the amount of data reported by the BSRs of different services (XR services and traditional services)?

[0008] Therefore, there is an urgent need for an uplink resource processing method that can enhance XR services. Summary of the invention

[0009] The purpose of this application is to propose a user equipment (UE) and an uplink resource processing method.

[0010] In the first aspect of the present application, an uplink resource processing method is performed by a user equipment (UE), including: reporting a buffer status report (BSR) containing a delay to a base station; or obtaining an indication of the uplink resources allocated by the base station from the base station; or in a logical channel prioritization (LCP) process, allocating the uplink resources to a logical channel (LCH) with delay information.

[0011] In a second aspect of the present application, a user equipment (UE) stores instructions, which, when executed by a computer, cause the computer to execute the above method.

[0012] In a third aspect of the present application, an uplink resource processing method is performed by a base station, comprising: receiving a buffer status report (BSR) containing a delay from a user equipment (UE), wherein the BSR containing the delay includes delay information; allocating uplink resources in response to the BSR containing the delay; and sending an indication of the allocated uplink resources.

[0013] In a fourth aspect of the present application, a base station stores instructions, and when executed by a computer, the instructions cause the computer to execute the above method.

[0014] The disclosed method may be implemented in a chip. The chip may include a processor configured to call and run a computer program stored in a memory so that a device equipped with the chip executes the disclosed method.

[0015] The disclosed method can be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. After being loaded into a computer, the non-transitory computer-readable medium instructs a processor of the computer to execute the disclosed method.

[0016] The non-transitory computer-readable medium may include one of the following or a combination thereof: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), and a flash memory.

[0017] The disclosed method can be programmed as a computer program product, which enables a computer to perform the disclosed method.

[0018] The disclosed method can be programmed as a computer program, which causes a computer to perform the disclosed method.

[0019] Beneficial Effects

[0020] In this description, an embodiment is provided for the problem of how to perform differentiated scheduling under two BSR reporting mechanisms (XR service BSR and traditional service BSR). This application provides:

[0021] A mechanism by which a UE can simultaneously report the data volume of different services (XR services and traditional services) through BSR (XR BSR and / or traditional BSR);

[0022] A mechanism by which gNBs can perform differentiated scheduling and differentiated resource allocation indication;

[0023] A mechanism by which a UE can perform resource allocation for two different services (XR services and traditional services). BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present application or related technologies, the following briefly introduces the drawings to be described in the embodiments. Obviously, the drawings are only some embodiments of the present application, and ordinary technicians in this field can obtain other drawings based on these drawings without paying any price.

[0025] Figure 1 A schematic diagram of a communication system is shown.

[0026] Figure 2 A schematic diagram of a network embodiment for the disclosed uplink resource processing method is shown.

[0027] Figure 3 A schematic diagram showing the protocol layers of a transmitting device and a receiving device.

[0028] Figure 4 A schematic diagram showing an uplink data transmission process is shown.

[0029] Figure 5 A schematic diagram of an uplink resource processing method according to an embodiment of the present application is shown.

[0030] Figure 6 A schematic diagram showing the relationship between a logical channel group (LCG), a logical channel (LCH) and a protocol data unit (PDU) set.

[0031] Figure 7 A schematic diagram showing two uplink resources for traditional services and XR services is shown.

[0032] Figure 8 A system block diagram for wireless communication according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0033] The technical content, structural features, objectives and effects of the present application are described in detail below in conjunction with the accompanying drawings. Specifically, the terms in the embodiments of the present application are only used to describe the purpose of specific embodiments, and are not intended to limit the present application.

[0034] The abbreviations used in this manual are listed below:

[0035] Table 1:

[0036]

[0037]

[0038] The present application discloses an uplink resource processing method for processing XR traffic in extended reality (XR) services. XR services may include augmented reality (AR), virtual reality (VR) or mixed reality (MR). The requirements of XR services are different from traditional services, such as ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB) and massive machine type communication (mMTC). To simplify the description, communication services other than XR services are collectively referred to as non-XR services or traditional services.

[0039] In this specification, data packets, protocol data units (PDUs) and / or PDU sets may be collectively referred to as traffic data to simplify the description.

[0040] In this specification, a data packet may be a PDU or SDU of the protocol layer. To simplify the description, the term "data packet" may refer to a PDU or an SDU, and the term "PDU" may refer to a PDU or an SDU. In addition, the term "resource" includes wireless resources in both the time and frequency domains.

[0041] The user equipment (UE) can send a buffer status report (BSR) to the gNB. The BSR procedure is used to provide the serving gNB with information about the amount of uplink (UL) data in the MAC entity of the UE.

[0042] refer to Figure 1 A communication system involved in an embodiment of the present application includes UE 10a, UE 10b, a base station (BS) 20a and a network entity device 30, and the system executes the disclosed method. Figure 1For illustration only, not for limiting description, the system may also include more UE, BS and CN entities. The connections between the devices and device components in the figure are represented by lines and arrows. UE 10a may include a processor 11a, a memory 12a and a transceiver 13a. UE 10b may include a processor 11b, a memory 12b and a transceiver 13b. Base station 20a may include a processor 21a, a memory 22a and a transceiver 23a. Network entity device 30 may include a processor 31, a memory 32 and a transceiver 33. Processors 11a, 11b, 21a and 31 may be configured to implement various functions, processes and / or methods described in this application. The various layers of the wireless interface protocol may be implemented in these processors. Memories 12a, 12b, 22a and 32 may store various programs and information to operate the connected processors. Transceivers 13a, 13b, 23a and 33 may be coupled to corresponding processors and used to send and / or receive wireless signals or wired signals. UE 10a can communicate with UE 10b via a sidelink. Base station 20a can be an eNB, gNB or other types of wireless nodes, and can configure wireless resources for UE 10a and UE 10b.

[0043] The network entity device 30 may be a node in a core network (CN). CN may include an LTE core network (LTE CN) or a 5G core network (5G core, 5GC), wherein the 5GC includes a user plane function (UPF), a session management function (SMF), a 5G core access and mobility management function (AMF), a unified data management (UDM), a policy control function (PCF), a control plane (CP) / user plane (UP) separation (CUPS), an authentication server (AUSF), a network slice selection function (NSSF), and a network exposure function (NEF), etc.

[0044] Examples of UEs mentioned in this specification may include UE 10a or UE 10b. Examples of base stations mentioned in this specification may include base station 20a. Uplink (UL) transmission refers to a transmission operation in which a UE sends a control signal or data to a base station. Downlink (DL) transmission refers to a transmission operation in which a base station sends a control signal or data to a UE. Downlink control signals may include downlink control information (DCI) or radio resource control (RRC) signals, which are sent by a base station to a UE.

[0045] Figure 2 A 5G system transmission network model supporting XR services is shown. UE 10 is a 5G terminal that can support XR services and XR applications and can be called a client, client terminal or XR client. gNB 20 is a 5G wireless node that communicates with UE 10 via an NR Uu interface and provides NR user plane and control plane protocol termination for the UE. gNB 20 is connected to 5GC 300, i.e., 5G Core Network, via an NG interface. UPF 30b is the UPF in 5GC 300. DN 40 is a data network (DN) in which an XR server 41 is deployed, and XR server 41 provides XR services. DN40 can provide network operator services, Internet access or third-party services. XR server 41 may include: a processor 411 configured to perform functions, processes and / or methods related to XR services and can implement various layers of the wireless interface protocol. Memory 412 operatively stores various programs and information to operate the connected processor 411. The transceiver 413 is operatively coupled to the processor 411 and is configured to send and / or receive wireless signals or wired signals.

[0046] Each processor 411, 11a, 11b, 21a and 31 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. Each memory 412, 12a, 12b, 22a and 32 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium and / or other storage devices. Each transceiver 413, 13a, 13b, 23a and 33 may include a baseband circuit and a radio frequency (RF) circuit for processing radio frequency signals. When the embodiment is implemented in software, the technology may be implemented in the form of modules, processes, functions, entities, etc., and perform the functions described in this application. These modules may be stored in a memory and executed by a processor. The memory may be integrated inside or outside the processor and communicate with the processor through a known communication method. The device that performs the uplink resource processing method may be a sending device or a receiving device. The sending device is responsible for transmitting the traffic of the XR service, and the receiving device is responsible for receiving the traffic of the XR service. The traffic of the XR service may include one or more service data flows of the XR service. For example, the device that performs the uplink resource processing method may be the gNB 20, the XR server 41 in the data network 40, or the UE. In certain transmission scenarios of XR services, the XR server 41 in the data network 40 may be used as a sending device to perform the uplink resource processing method, and one or more XR clients (such as UE 10, UE 10a, and UE 10b) may be used as receiving devices to receive the XR service traffic from the sending device. Similarly, in certain transmission scenarios of XR services, the XR client (such as UE 10, UE 10a, and UE 10b) may be used as a sending device to perform the uplink resource processing method, and another XR client or XR server 41 may be used as a receiving device to receive the XR service traffic from the sending device. In addition, the sending device may also be an intermediate device between the UE 10 and the XR server 41. The UE 10 may include an embodiment of the UE 10a or the UE 10b. The gNB 20 may include an embodiment of the base station 20a. It should be noted that although gNB 20 and UPF / 5GC 30b are used as examples in this application, the uplink resource processing method can also be performed by other types of base stations, such as another gNB, eNB, a base station integrating eNB and gNB, or a base station for future 5G and higher level technologies. In addition, UPF / 5GC 30b may also include other network entities of 5GC.

[0047] A service traffic data flow 5 (eg, an XR data flow of an XR service) is established between the UE 10 and the XR server 41. The data flow 5 includes traffic 51 from the XR server 41 to the UE 10, and traffic 52 from the UE 10 to the XR server 41.

[0048] In this specification, a protocol layer (e.g., an application layer, a PDCP layer, an RLC layer, a MAC layer, or a physical layer (PHY layer or L1 layer)) may be a protocol layer entity in a transmitting device or a receiving device. The protocol layer entity may be implemented by a program or software module executed by a processor, or by a hardware module in an integrated circuit (IC).

[0049] refer to Figure 3 , an example of a transmitting device is shown as a transmitting device 10c, and an example of a receiving device is shown as a receiving device 10d. The transmitting device 10c includes a physical layer (PHY layer or L1 layer) 14c, a MAC layer 15c, an RLC layer 16c, a PDCP layer 17c, an RRC layer 18c, and an application layer 19c. The receiving device 10d includes a physical layer (PHY layer or L1 layer) 14d, a MAC layer 15d, an RLC layer 16d, a PDCP layer 17d, an RRC layer 18d, and an application layer 19d. For example, when the application layer 19c of the transmitting device 10c sends a PDU to the application layer 19d of the receiving device 10d through the lower layer (i.e., the PDCP layer 17c, the RLC layer 16c, the MAC layer 15c, and the physical layer 14c), each layer in the transmitting device 10c acts as a protocol layer entity of the transmitting end, and each layer in the receiving device 10d acts as a protocol layer entity of the receiving end. The embodiments of the present application can be implemented at the PDCP layer or the RLC layer. One or more steps (or modules) in the embodiments of the present application may be stored in the memory of the transmitting device as a computer program, instruction or software module, or integrated into the processor of the transmitting device as a circuit or hardware module, or implemented in the transmitting device by an IC chip, circuit or plug-in.

[0050] The video stream of the XR service is encoded and compressed in the form of frames and processed in a quasi-periodic manner. The period of each frame can be 1 / 60 second, 1 / 90 second or 1 / 120 second. Since the transmitting device may divide the video stream of the XR service into multiple transport units and encapsulate each transport unit as a transport packet for transmission over the network, the transmission mechanism of the XR service is actually based on packets rather than frames. The size of each packet is variable, and the number of packets is also variable and configurable, and can be adjusted according to the QoS (quality of service) requirements and characteristics of the XR service, such as packet delay budget (PDB), packet error rate (PER), packet loss rate (PLR), frame error rate, frame delay budget, resolution, frame rate and / or data rate.

[0051] When the base station performs uplink resource scheduling, it may not be able to accurately know how much data is waiting to be transmitted on the UE side. Therefore, according to the 3GPP standard, the UE needs to perform a BSR to report the service data volume information (i.e., the buffer size) to the base station so that the base station can perform uplink scheduling. Figure 4 As shown, in traditional services, the BSR process is a part of the uplink data transmission process.

[0052] UE 10 sends an uplink resource request to base station 20 via a scheduling request (SR) (step 201). After receiving the SR, base station 20 sends an uplink resource grant to UE 10 in response to the SR (step 202).

[0053] UE 10 monitors BSR triggering conditions, including: new data arrival; delay timer expiration; XR BSR triggering (step 203).

[0054] The BSR triggering conditions are described in detail. When one or more BSR triggering conditions are met, UE 10 sends a traditional BSR (step 204) and an XR BSR (step 205) to base station 20. After receiving the traditional BSR and the XR BSR, base station 20 performs uplink resource scheduling of UE 10 according to the information of the two BSRs (step 206). Subsequently, base station 20 sends the allocated uplink resource indication information to UE 10 through the first DCI 0 (step 207) and the second DCI 0 (step 208).

[0055] After receiving the first DCI 0 and the second DCI 0, UE 10 performs latency-aware LCP and allocates the uplink resources indicated by DCI 0 to the logical channel (step 209). Subsequently, UE 10 sends uplink data to gNB 20 in the logical channel through PUSCH (physical uplink shared channel) (step 210).

[0056] When the UE has uplink data to be sent, it needs to request uplink resources from the gNB. First, the UE needs to send an SR to the gNB, indicating that the UE has uplink data to transmit. However, the SR only indicates that there is data to be sent, and does not specify the specific amount of data. The BSR is responsible for indicating the amount of data to be transmitted in the uplink. After receiving the SR, the gNB may send an uplink resource grant to the UE to allow the UE to transmit the BSR.

[0057] The BSR reported by the UE to the gNB uses LCG as the basic granularity unit. In the BSR, each uplink data volume record (i.e., buffer size) corresponds to an LCH, and each LCH belongs to an LCG. The gNB is responsible for configuring the mapping relationship between LCH and LCG and controlling the priority of each LCH. When performing the mapping configuration from LCH to LCG, the gNB may aggregate LCHs with similar scheduling requirements into the same LCG. Therefore, the gNB needs to grasp the LCH information reported by the LCG in the BSR to perform the configuration task from LCH to LCG.

[0058] BSR is an uplink control message (UL MAC CE), which is carried at the end of the uplink MAC PDU (i.e., UL data is transmitted first, followed by UL MAC CE). The format of BSR includes a BSR MAC subheader and a MAC CE payload. The BSR MAC subheader is used to indicate the type of BSR, such as a long BSR or a short BSR. Among them, the long BSR is used to report the data volume of multiple LCGs, while the short BSR is only used to report the data volume of one LCG. The MAC CE payload contains the LCG ID to be reported and the buffer size information of the corresponding LCG, where the buffer size information is a summary of the data volume of all LCHs in the LCG. The definition of BSR can be found in the 3GPP standard.

[0059] For legacy services, the UE needs to send a BSR when the BSR triggering conditions are met. For example, when new data of high priority (LCH belongs to LCG) arrives, or the BSR timer times out, the UE needs to select the appropriate BSR format and type according to the actual situation and report the BSR to the gNB.

[0060] When the gNB receives the BSR sent by the UE, it allocates uplink resources according to the buffer size information in the BSR, and then sends uplink resource indication information to the UE through DCI 0. After receiving the uplink resource information indicated by DCI 0, the UE allocates uplink resources according to the logical channel priority and performs uplink data transmission.

[0061] For XR services, when scheduling uplink service resources, gNB also needs to allocate resources for the LCH of XR services based on the buffer size information reported by the UE in the XR BSR. Since XR services have large data volumes and jitter characteristics, in order to more accurately support XR BSR, 3GPP decided to enhance the XR BSR mechanism, but this also brings a major challenge: How can gNB achieve differentiated scheduling based on the BSR data volume reported by different services (XR services and traditional services)?

[0062] In this specification, multiple embodiments are provided to solve the problem of how to perform differentiated scheduling of two different types of BSRs (BSR for XR services and BSR for traditional services). The present invention provides the following mechanism: UE reports the data volume of different services (XR services and traditional services) simultaneously through BSR (XR BSR and / or traditional BSR). UE reports the data volume of different services (XR services and traditional services) simultaneously through BSR (XR BSR and / or traditional BSR). gNB performs differentiated scheduling and provides differentiated resource allocation indications. UE performs resource allocation for two different services (XR services and traditional services).

[0063] refer to Figure 5 UE 10 and gNB 20 execute the method of the present invention and start a service. The service may be an XR service, a critical mission service, a video streaming service, or a URLLC service.

[0064] UE 10 applies for uplink resources by sending a request to gNB 20. gNB 20 receives the uplink resource request from UE 10, where the uplink resource request includes latency information.

[0065] UE 10 sends a BSR including latency to gNB 20 (step 301). gNB 20 receives the BSR including latency, wherein the BSR includes latency information (step 302). The BSR including latency includes latency information and buffer size information of the LCH, LCG, or PDU set. The latency information refers to the remaining time of the LCH, LCG, or PDU set. The buffer size refers to the amount of available data of the LCH, LCG, or PDU set.

[0066] In one embodiment, when requesting uplink resources, UE 10 sends a BSR when a BSR triggering condition is met, wherein the BSR triggering condition includes at least one of the following: a change in the amount of data associated with the LCH, LCG, or PDU set exceeds a data amount change threshold, wherein the data amount change threshold is configured by the gNB through RRC signaling; a remaining time associated with the LCH, LCG, or PDU set reaches a remaining time threshold, wherein the remaining time threshold is configured by the gNB through RRC signaling.

[0067] gNB 20 allocates uplink resources (e.g., uplink resources related to the service) according to the BSR including the delay (step 304).

[0068] gNB 20 sends the allocated uplink resource indication information to UE 10 (step 306).

[0069] UE 10 obtains the uplink resource indication information allocated by gNB 20 from gNB 20 (step 307).

[0070] During the LCP process (step 309), the UE 10 allocates uplink resources to the LCH.

[0071] In one embodiment, the format of the BSR includes one MAC CE or two MAC CEs. In the BSR, the UE uses one MAC CE to report the buffer size and delay information, where the delay information indicates the delay budget remaining time of the LCH, LCG or PDU set. The MAC CE may include delay information corresponding to different buffer size ranges.

[0072] In another embodiment, the UE uses the first MAC CE to report the buffer size in the BSR and uses the second MAC CE to report the delay information. The buffer size in the first MAC CE and the delay information in the second MAC CE are associated through the LCH ID, LCG ID or PDU set ID.

[0073] The implementation plan for solving differentiated scheduling instructions and resource allocation will be described in detail in the subsequent content.

[0074] gNB needs to perform differentiated scheduling based on the amount of data reported by the BSR of XR services and traditional services. This problem can be broken down into three sub-problems.

[0075] The first sub-problem: How does the UE report two different types of BSRs (XR BSR and traditional BSR) at the same time?

[0076] Regarding how to report the data volume (i.e., the buffer size in 3GPP standard TS 38.321) and delay information to the gNB in ​​the BSR at the same time, the present invention provides two solutions:

[0077] (1) Method 1: Report buffer size and latency information (e.g., remaining time) in the same BSR. That is, one BSR can be used to report both traditional BSR information (buffer size only) and XR BSR information (buffer size + latency information). The latency information must be clearly identifiable and able to identify the BSR part (e.g., buffer or LCH / LCG) to which it corresponds, i.e., the latency information (e.g., remaining time) needs to be associated with a specific LCH / LCG or buffer. The latency information can be reported via the traditional BSR or the newly added MAC CE.

[0078] (2) Method 2: Put the buffer size and latency information (such as remaining time) into different uplink MAC CEs. The buffer size information is reported in the BSR, and the latency information (such as remaining time) is reported in the new uplink MAC CE. Therefore, an association needs to be established between the BSR and the new uplink MAC CE, for example, based on the logical channel ID, so that the BSR and the new uplink MAC CE can be reported to the gNB at the same time. The gNB can identify and associate the two uplink MAC CEs (i.e., the BSR and the new uplink MAC CE) based on the logical channel ID for resource scheduling and allocation.

[0079] In addition, the present invention also provides a triggering mechanism for triggering an XR BSR, wherein the XR BSR refers to a BSR for an XR service.

[0080] The second sub-question: How does gNB perform differentiated resource scheduling and resource indication according to different services?

[0081] In some embodiments of the present invention, the gNB may indicate differentiated resource information for XR services and non-XR services in downlink control information (DCI) in an explicit or implicit manner.

[0082] The third sub-question: How does the UE perform differentiated resource allocation for two different types of services?

[0083] In some embodiments of the present invention, the UE may perform delay-based LCP scheduling to allocate resources to the LCH.

[0084] Embodiment 1 (BSR triggering mechanism based on buffer size change):

[0085] After analyzing the first sub-problem, in order to support both traditional services and XR services, the UE needs to report the BSR of traditional services and the BSR of XR services to the gNB at the same time. During the BSR reporting process, the data traffic event of the LCH will trigger the reporting of the BSR. According to the standard protocol, for traditional services, when the BSR triggering conditions are met, the UE needs to send a BSR to the gNB. The triggering conditions of the BSR include the following situations: new data arrives on a high-priority LCH (the LCH belongs to a certain LCG and caches the UE's data); the BSR timer times out. When the above conditions are met, the UE will select the appropriate BSR format and BSR type according to the actual situation, and report the BSR to the gNB. However, how to trigger the BSR for the XR service needs to be redesigned. In the following content, the present invention discloses an XR BSR triggering mechanism based on buffer size changes.

[0086] XR services involve the application layer and may include video frames, where the traffic data of the XR services is transmitted on the Uu interface in units of PDU sets. A PDU set contains multiple data packets, and a PDU set represents a video frame. Some data packets in the PDU set have inter-packet correlation or inter-PDU set correlation, that is, the application layer of the receiving device requires complete PDU set information (that is, all data packets) to correctly receive and decode the video information. Therefore, when the core network transmits data to the gNB, each PDU set indicates to the gNB through the PDU Set Integrated Indication (PSII) parameter whether the PDU set requires the application layer (such as the application layer) to receive all data packets completely. Based on this, when transmitting XR service data on the Uu interface, if the PSII of a PDU set is set, but a data packet in the PDU set is lost, the gNB discards the entire PDU set. When this happens to one or more PDU sets, the amount of data (buffer size) in the current LCH will change significantly. If the gNB cannot obtain information about the change in buffer size, it may allocate resources to the UE that exceed the actual demand, resulting in resource waste. On the other hand, due to the data jitter characteristics of XR services, a large amount of data bursts may suddenly appear on the Uu interface. If the gNB fails to obtain the buffer size change information in time, it may allocate resources far below the UE requirements, resulting in the inability to schedule UE data resources in time, affecting the user experience. Therefore, it is necessary to design an XR BSR trigger mechanism based on the buffer size change. Specifically, the following XR BSR trigger scheme is triggered based on the buffer size change:

[0087] 1. When the LCH / LCG related buffer size increases or decreases and reaches a certain threshold, the UE triggers an XR BSR report.

[0088] 2. When the LCH / LCG related buffer size increases or decreases and reaches a certain threshold ratio, the UE triggers an XRBSR report.

[0089] 3. When the number of PDU sets in the LCH / LCG / PDU set increases or decreases and reaches a certain threshold, the UE triggers an XRBSR report.

[0090] 4. When the number of PDU sets in the LCH / LCG increases or decreases and reaches a certain threshold ratio, the UE triggers an XR BSR report.

[0091] The threshold or threshold ratio is called the Data Volume Change Threshold. In the XRBSR triggering mechanism, the gNB needs to configure the Data Volume Change Threshold for the LCH / LCG. The Data Volume Change Threshold is set by the gNB and is used to compare the data volume change associated with the LCH, LCG or PDU set. The Data Volume Change Threshold can be a specific threshold (Threshold Value) or a data volume change ratio (Threshold Ratio). The data volume can be measured in bits, bytes or the number of PDU sets. The data volume associated with the LCH or LCG includes the data volume in the buffer size, which is associated with the LCH or LCG. In addition, the data volume associated with the LCH or LCG can also represent the number of PDU sets, that is, the number of PDU sets in the logical channel or logical channel group. The data volume change associated with the LCH or LCG includes an increase or decrease in the buffer size. When the change in data volume reaches or exceeds the data volume change threshold set by the gNB, the reporting of the XR BSR will be triggered.

[0092] Embodiment 2 (trigger mechanism based on time delay timeout):

[0093] After analyzing the first sub-problem, in order to support both traditional services and XR services, the UE needs to report the BSR of traditional services and the BSR of XR services to the gNB. During the BSR reporting process, the data traffic event of LCH triggers the reporting of BSR. According to the standard protocol, for traditional services, when the triggering conditions of BSR are met, that is, new data arrives on the high-priority logical channel LCH (the LCH belonging to the LCG that caches UE buffered data) or the BSR timer times out, the UE will report the BSR to the gNB in ​​an appropriate BSR format and BSR type according to the actual situation. However, how to trigger BSR for XR services needs to be redesigned. In this embodiment, an XR BSR triggering mechanism based on remaining time timeout is provided.

[0094] According to the latest 3GPP standard protocol, when the UE reports the data volume (buffer size) for the XR service, it should also report the delay information (e.g., remaining time). That is, when the UE reports the data volume of LCH(s) / LCG(s) to the gNB on the Uu interface, it reports the remaining time information in an associative manner. Based on this information, the gNB can obtain the urgency of different LCH(s) / LCG(s) data volumes and perform resource scheduling based on the urgency. Based on this analysis, the UE should report the content of the XR BSR based on the delay information related to the specific data volume. The delay information may include at least the delay budget or the remaining time in the delay budget. The delay budget may include the PDU set delay budget (PSDB). Therefore, a trigger mechanism based on delay timeout can be used to trigger the reporting of the XR BSR. In this embodiment, the gNB can set a specific threshold for the trigger mechanism, which may be referred to as the threshold remaining time limit. The threshold remaining time limit can be timed by a timer (called a delay timer), and when the remaining time of the reported data volume (related to LCH or LCG) reaches the threshold remaining time limit, the timer expires. For example, when the remaining time of a certain data volume is lower than the threshold remaining time limit or the delay timer times out, the UE triggers a BSR. The specific scheme of the triggering mechanism will be described in detail in the following content.

[0095] The threshold remaining time limit may be a specific delay information (eg, remaining time) value or ratio. The threshold remaining time limit may be set based on the granularity of an LCG, an LCH, or a PDU set. Figure 6 The relationship between LCG, LCH and PDU set is shown: the PDU set is located in the LCH, and each LCH belongs to an LCG.

[0096] 1. LCG-based timeout trigger mechanism:

[0097] In one embodiment, the threshold remaining time limit is timed by a timer configured for the LCG. The remaining time associated with the LCH or LCG can be the average remaining time or the minimum remaining time of the LCH within the LCG. From the perspective of the current standard protocol, the gNB does not have the configuration information of the LCG, and the standard protocol only specifies the LCG to which the LCH belongs. The current 3GPP standard has not yet enhanced the LCG. However, from an implementation perspective, the LCG can be used to report the delay information of the LCH. For example, if an LCH is configured with a remaining time (calculated from the PSDB or packet delay budget (PDB) by the QoS flow), the average or minimum remaining time of the LCH can be used as the remaining time of the LCG, and when the remaining time of the LCH reaches the threshold remaining time limit, the reporting of the XR BSR can be triggered.

[0098] In addition, according to the threshold remaining time limit, a delay timer can be set at the LCG granularity as a mechanism for triggering XRBSR reporting. When the delay timer times out (timeout expires), the UE sends a BSR according to the description of the present invention.

[0099] In this case, the gNB may configure a threshold remaining time limit or a timer for the LCG.

[0100] 2. LCH-based timeout trigger mechanism:

[0101] In one embodiment, the threshold remaining time limit is timed by a timer configured for a specific LCH. The LCH-related remaining time may be an average remaining time or a minimum remaining time of a PDU set located in the specific LCH.

[0102] From the perspective of the current standard protocol, the configuration of LCH is set on a per-UE basis. The LCH configuration includes basic LCP parameters (priority / PBR / BSD) and parameters that limit the PUSCH resources that can be used by LCH (e.g., allowed SCS list, etc.). In one embodiment, latency information is used for the timeout-based trigger mechanism of LCH. Basically, the average or minimum remaining time of a PDU set within an LCH can be regarded as the remaining time of the LCH. Alternatively, the gNB can configure a threshold remaining time limit for each LCH in the LCH configuration.

[0103] In addition, according to the threshold remaining time limit, setting a delay timer at the LCH granularity is also a mechanism for triggering XR BSR reporting. When the delay timer times out (expires), the UE sends a BSR according to the description of the present invention.

[0104] In this case, the gNB may configure a threshold remaining time limit or a timer for the LCH.

[0105] 1. Timeout trigger mechanism based on PDU set:

[0106] In one embodiment, the threshold remaining time limit is timed by a timer configured for a PDU set associated with an LCH or LCG.

[0107] PSDB (PDU set delay budget) is one of the basic parameter information of PDU set in Uu transmission. gNB can set a threshold for each PDU set based on PSDB. When a PDU set reaches a specific delay threshold, XR BSR reporting should be triggered. Based on the delay timeout threshold (or timer timeout) is also a reasonable approach.

[0108] In addition, according to the threshold remaining time limit, setting a delay timer at the PDU set granularity is also a mechanism for triggering XR BSR reporting. When the delay timer times out (expires), the UE sends a BSR according to the description of the present invention.

[0109] In this case, the gNB may configure a threshold remaining time limit or a timer for the PDU set.

[0110] Example 3 (Format of traditional BSR and XR BSR mechanisms):

[0111] After analyzing the first sub-problem, in order to support both traditional services and XR services, the UE needs to report the BSR of traditional services and the BSR of XR services to the gNB. In addition to the BSR triggering mechanism described in detail in the above embodiment, the reporting method of BSR also needs to be further enhanced, including the format of the BSR reported to the gNB. The specific solution is as follows:

[0112] Option 1: The UE uses one BSR to report information of two services at the same time (ie, buffer size information of the traditional service, and buffer size and latency information of the XR service).

[0113] In this scheme, the data volume (buffer size) is reported together with the latency information. In this option, the reported BSR supports the following formats: BSR MAC CE format for traditional services (only reporting buffer size information for traditional services); BSR MAC CE format for XR services (reporting both buffer size information and latency information for XR services); BSR MAC CE format that supports both traditional and XR services (reporting buffer size information for traditional services, as well as buffer size information and latency information for XR services). In Option 1, the buffer size information and latency information are combined in one BSR for reporting, as shown below:

[0114] a) UE uses different ranges of latency information as the basic unit for reporting buffer size in BSR. BSR shows that each LCG / LCH has multiple remaining time ranges and the amount of data (buffer size) corresponding to each remaining time range. Table 1 shows an example of the correspondence between the remaining time range and the amount of data in BSR.

[0115] Table 1:

[0116] Remaining time range Data volume (buffer size) 0 to 10 ms First buffer size 1 to 20 ms Second buffer size …… ……

[0117] In this embodiment, the UE uses one MAC CE to simultaneously report the buffer size information of the traditional service, the buffer size of the XR service, and the information of different delay ranges of the XR service. The MAC CE includes the buffer size of the XR service and is associated with the different delay ranges of the XR service.

[0118] b) The UE uses the PDU set as the basic unit for reporting the buffer size in the BSR.

[0119] The BSR shows that each LCG / LCH has multiple PDU sets, and the data volume (buffer size) and remaining time corresponding to each PDU set. Table 2 shows an example of the corresponding relationship between the remaining time range and the data volume in the BSR.

[0120] Table 2:

[0121] PDU Set time left Data volume (buffer size) First PDU Set 10ms First buffer size Second PDU Set 20ms Second buffer size …… …… ……

[0122] Option 2: The UE uses two BSRs to report information about the two services (i.e., buffer size information for traditional services, and buffer size and latency information for XR services). In this solution, the UE uses two BSRs for reporting: one BSR is used to report the buffer status (i.e., buffer size information) of traditional services and XR services; the other BSR is used to report latency information of XR services.

[0123] Specifically, the data volume information is reported through the traditional BSR, and the latency information is reported through the new BSR / UL MACCE. In this solution, the latency information and buffer size information of the XR BSR belong to different UL MACCEs. When the gNB obtains the XR service information, it needs to obtain the buffer size information and latency information at the same time. Therefore, the two BSRs need to establish an association. For example, the association between the two BSRs can be established based on the LCG / LCH ID field.

[0124] In this embodiment, during the buffer status reporting process, the UE uses the first MAC CE to report the buffer size of the traditional service and the buffer size of the XR service, and uses the second MAC CE to report the delay information of the XR service. The buffer size information of the XR service and the delay information of the XR service in the first MAC CE are associated through the LCH ID field or the LCG ID field.

[0125] Option 3: The UE independently reports the traditional BSR and the XR BSR, that is, two different services are independently reported through different BSRs.

[0126] In this solution, the traditional BSR is still reported according to the current standard mechanism, while the XR BSR is an independent UL MACCE, which is different from the traditional BSR and is reported independently. The XR BSR mainly contains the buffer size of the XR service and the delay information corresponding to each buffer size. How to distinguish the delay information corresponding to different buffer sizes can refer to the solution in Option 1.

[0127] In this embodiment, during the buffer status reporting process, the UE uses the first MAC CE to report the buffer size of the traditional service, and uses the second MAC CE to report the buffer size and delay information of the XR service.

[0128] Embodiment 4 (resource scheduling and indication based on service type distinction):

[0129] After receiving the BSR of two types of services, the gNB should allocate resources for the two services based on differentiated scheduling, and allocate resources according to the latency information (XR service) and buffer size information in the BSR. The latency information indicates the urgency of the XR service, while the buffer size indicates the current data traffic volume of the XR service. Since XR services and traditional services have different requirements for bandwidth, latency and resources, XR services and traditional services may correspond to different physical layer parameters and resource requirements. Therefore, when the gNB schedules physical resources for the two services at the same time, the above factors need to be considered comprehensively. Therefore, the gNB may need to allocate two sets of physical resources with different numerical domains (Numerology) for traditional services and XR services respectively. The process is as follows Figure 4 shown. Figure 4 The resource allocation and indication based on service type are shown. The UE obtains the indication of uplink resources from the gNB via DCI 0. The uplink resources in the indication can be identified by at least one of the following identifiers (ID): LCH ID / LCG ID / DRB ID.

[0130] In one embodiment, in steps 207 and 208, the gNB sends an indication to the UE via two DCI 0s. The UE receives two resource allocation indications, each of which indicates physical resource allocation information for two services (including non-XR services and XR services).

[0131] In addition, the gNB can also send indications to the UE through two DCI 0s. The UE only receives one resource allocation indication, which contains physical resource allocation information for two services (including non-XR services and XR services).

[0132] When allocating two sets of physical resources for two services, the gNB sends the allocation information of the two sets of physical resources to the UE through DCI 0. However, in the standard protocol, it is not clear how the gNB indicates the service types corresponding to the two different sets of uplink resources. Therefore, it is necessary to enhance the physical resource indication mechanism of the gNB. Specifically, this embodiment provides two methods:

[0133] Method 1: The gNB explicitly sends two DCI 0s to the UE, each DCI 0 indicating the physical resource allocation information of two services.

[0134] In this mechanism, two DCI 0s need to carry identification information for distinguishing different services. The specific solution is as follows:

[0135] Since different service types are carried on LCH and transmitted through DRB, and LCH belongs to one or more LCGs, in order to distinguish different service types in DCI 0, gNB carries LCH / LCG / DRB ID information in each DCI 0. The DCI received by the UE contains one or more identification information of LCH, LCG and dynamic radio bearer (DRB) for resource allocation indication.

[0136] Optionally, since the traditional service only contains buffer size information, while the XR service contains buffer size information and latency information, in order to distinguish different services in DCI 0, the gNB carries latency information in the XR-specific DCI 0 to indicate the resource information of the XR service. The DCI received by the UE contains the latency information of the XR service and is associated with the physical resource allocation information of the XR service.

[0137] Optionally, a lookup table can be pre-designed between the UE and the gNB, which provides the correspondence between the DCI 0ID and the service type ID. Therefore, when the gNB sends DCI 0 with the service type ID, the UE can accurately determine which service type the resource allocation indicated by DCI 0 belongs to through the lookup table. The DCI received by the UE contains the service identifier of the XR service, which is pre-configured in the lookup table.

[0138] Method 2: The gNB only sends one DCI 0 to the UE, and DCI 0 indicates the physical resource allocation information of two groups of services. In this mechanism, DCI 0 needs to carry identification information that can distinguish different services. The specific scheme is as follows:

[0139] Since different service types are carried on LCH and transmitted through DRB, and LCH belongs to one or more LCGs, in order to distinguish different service types in DCI 0, gN carries the ID information of LCH / LCG / DRB in DCI 0 of each allocated physical resource. The DCI received by the UE contains the identification information of one or more of LCH, LCG and dynamic radio bearer (DRB) for resource allocation indication.

[0140] Optionally, since the traditional service only contains buffer size information, while the XR service contains buffer size information and latency information, in order to distinguish different services in DCI 0, the gNB carries the latency information of the XR service in DCI 0 to indicate the resource information of the XR service. The DCI received by the UE contains the latency information of the XR service and is associated with the physical resource allocation information of the XR service.

[0141] Embodiment 5 (uplink resource allocation based on different service types):

[0142] To solve the second sub-problem, the gNB provides the UE with two sets of physical resources corresponding to the traditional services and XR services respectively, and the UE performs resource allocation after receiving the physical resources indicated by the gNB. Figure 4 As shown, the UE may receive two sets of uplink physical resources from the gNB, namely uplink resources R1 and uplink resources R2.

[0143] In addition, gNB needs to consider how to efficiently perform uplink resource allocation. The uplink resource allocation process consists of two parts: inter-resource allocation between traditional services and XR services; and intra-resource allocation within traditional services or XR services.

[0144] The current standard protocol can be used for resource allocation within traditional services. In the current standard protocol, the specific algorithm is based on the priority of the LCH and the upper limit of the resources allocated to each LCH.

[0145] For cross-resource allocation between XR services and traditional services, as well as resource allocation within XR services, a resource allocation mechanism needs to be defined. The implementation example of the resource allocation mechanism is as follows:

[0146] Cross-resource allocation between XR business and traditional business:

[0147] When both traditional services and XR services exist in the system, the deployment of XR services and traditional services may belong to different LCGs (e.g. Figure 7 In either case, each XR service or traditional service uses an independent DRB, which is located in an independent LCH. Therefore, the gNB only needs to reclassify the traditional and XR services according to the LCH or DRB, and then allocate the uplink resources belonging to the traditional services and the uplink resources belonging to the XR services respectively. For traditional services, the uplink resource allocation follows the LCP processing flow in the current standard protocol (the specific algorithm is based on the priority of the LCH and the upper limit of the resources allocated to each LCH). For XR services, that is, the resource allocation within the XR service, the specific allocation mechanism will be described below.

[0148] Resource allocation within XR business:

[0149] When the UE receives uplink resources for XR services from the gNB, the UE uses the uplink resources for XR services to transmit XR service data carried on the LCH. According to the 3GPP standard protocol TS38.321-5.4.3.1.3, the UE determines the amount of resources allocated to each LCH through the Token Bucket Algorithm in the LCP process. The algorithm is specifically executed based on the priority of the LCH and the upper limit of the resources allocated to the LCH each time. Specifically, the UE allocates uplink resources to the LCH that meets the resource allocation constraints in descending order of LCH priority. Each LCH is assigned a token variable Bj (Bj is the maximum capacity of the token bucket). Before each LCP process starts, Bj increases by one unit; after each LCP process ends, Bj deducts the size of the resources allocated to the LCH in the LCP process. If there are still remaining resources after the LCP process ends, these remaining resources will be allocated only based on the priority of the LCH, without considering Bj.

[0150] The current mechanism does not take into account the latency information (e.g., remaining time) of the XR service. However, the latency information of the XR service is a very important influencing factor in the resource scheduling and allocation process. If the data packet of the XR service fails to complete the scheduling within the specified time (i.e., the latency budget), the receiving device cannot decode it, which seriously affects the user experience. Therefore, in the process of intra-resource allocation within XR service, in addition to considering the priority of LCH, the remaining time of the XR service also needs to be considered. In some embodiments, the UE uses latency information to allocate uplink resources to the LCH during the LCP process. The UE's LCH latency information is configured by the gNB through RRC signaling. Examples of latency information include: PSDB, PDB, remaining time, and delay timer.

[0151] The delay information includes a delay priority value or a delay-sensitive indication.

[0152] The specific plan is as follows:

[0153] Solution 1 (resource allocation based on LCH priority and combined with remaining time priority): UE allocates physical resources to the buffer of XR service based on LCH priority and combined with remaining time priority.

[0154] Step 1: The UE arranges the LCH buffers of the XR service in ascending order according to the priority value of the LCH (the smaller the LCH priority value, the higher the LCH priority), and then arranges them in ascending order according to the remaining time value of the buffer within each LCH priority value (the smaller the remaining time value, the higher the priority of the buffer).

[0155] Step 2: The UE calculates the average of the remaining time values ​​of all XR service buffers and uses the average as the remaining time threshold. Alternatively, the gNB sets the remaining time threshold directly to the UE. The UE obtains buffers in order from the highest LCH priority value to the lowest LCH priority value; for each buffer with LCH priority value, the UE performs the following operations: If the remaining time value of the buffer is lower than the remaining time threshold, the UE prioritizes resource allocation according to the LCH priority value of the buffer. If the remaining time value of the buffer is not lower than the remaining time threshold, the UE does not prioritize resource allocation to the buffer.

[0156] Step 3: When all buffers with remaining time values ​​lower than the remaining time threshold have been allocated resources, if there are still remaining uplink resources, the UE allocates resources to the buffers with remaining time values ​​higher than the remaining time threshold according to the LCH priority.

[0157] Solution 2 (resource allocation based on the remaining time priority and combined with the LCH priority): The UE allocates physical resources to the buffer of the XR service based on the remaining time priority and combined with the LCH priority.

[0158] Step 1: The UE arranges the LCH buffers of the XR service in ascending order according to the remaining time priority (the smaller the remaining time priority value, the higher the remaining time priority), and then arranges them in ascending order according to the LCH priority value within each remaining time priority value (the smaller the LCH priority value, the higher the buffer priority).

[0159] Step 2: The UE calculates the average value of the LCH priority values ​​of the XR service buffers and uses the average value as the LCH priority threshold. Alternatively, the gNB sets the LCH priority threshold directly to the UE. The UE obtains buffers in order from the highest remaining time priority value to the lowest remaining time priority value; for each buffer with a remaining time priority value, the UE performs the following operations: If the LCH priority value of the buffer is lower than the LCH priority threshold, the UE prioritizes resource allocation according to the remaining time priority value of the buffer. If the LCH priority value of the buffer is not lower than the LCH priority threshold, the UE does not prioritize resource allocation to the buffer.

[0160] Step 3: When all buffers with LCH priority values ​​lower than the LCH priority threshold have been allocated resources, if there are still uplink resources remaining, the UE allocates resources to the buffers with LCH priority values ​​higher than the LCH priority threshold according to the remaining time priority.

[0161] In this specification, various embodiments are provided to solve the problem of how to perform differentiated scheduling for two types of BSR reports (XR service BSR and traditional service BSR). The present invention provides:

[0162] A mechanism by which the UE can simultaneously report the data volume of different services (XR services and traditional services) through the BSR (XR BSR and / or traditional service BSR).

[0163] A mechanism by which the UE can simultaneously report the data volume of different services (XR services and traditional services) through the BSR (XR BSR and / or traditional service BSR).

[0164] A mechanism by which the gNB can perform differentiated scheduling and make differentiated resource allocation instructions.

[0165] A mechanism by which a UE can perform resource allocation for two different services (XR services and traditional services).

[0166] Figure 8 7 is a block diagram of an exemplary system 700 for wireless communication according to an embodiment of the present invention. The embodiments described herein may be implemented in the system by any suitably configured hardware and / or software. Figure 8 The system 700 includes a radio frequency (RF) circuit 710, a baseband circuit 720, a processing unit 730, a memory / storage device 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, which are at least as shown in FIG. Figure 8 shown coupled to each other.

[0167] The processing unit 730 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may be any combination of a general-purpose processor and a special-purpose processor (e.g., a graphics processor, an application processor). The processor may be connected to a memory / storage device and configured to execute instructions stored in the memory / storage device to support various applications and / or operating systems running on the system.

[0168] Radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency conversion, etc. In some embodiments, the baseband circuit may provide communication capabilities compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuit may support the ability to communicate with 5G NR, LTE, evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), and wireless personal area networks (WPAN). A baseband circuit that has the ability to support multiple wireless protocol communications may be referred to as a multi-mode baseband circuit in different embodiments. In various embodiments, the baseband circuit 720 may include circuits for processing baseband signals in a non-strict sense. For example, in some embodiments, the baseband circuit may include circuits for processing intermediate frequency signals (whose frequency is between the baseband frequency and the radio frequency).

[0169] In various embodiments, the system 700 may be a mobile computing device, such as, but not limited to, a laptop, a tablet, a netbook, an ultrabook, a smart phone, etc. In different embodiments, the system may include more or fewer components and may adopt different architectural designs. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored in a storage medium (such as a non-volatile storage medium).

[0170] The embodiment of the present invention is a combination of technical solutions, which can be used in 3GPP specifications to form a final product.

[0171] If the software functional unit is developed, used and sold as a product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution proposed in the present invention can be implemented in whole or in part in the form of a software product, or the part of the present invention that is beneficial to the prior art can be implemented as a software product. The software product in the computer is stored in a storage medium, including a plurality of instructions for a computing device (such as a personal computer, a server or a network device) to execute all or part of the steps disclosed in the embodiment of the present invention. The storage medium can be a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other medium that can store program code.

[0172] While the present disclosure has been described in connection with what is considered to be the most practical and preferred embodiment, it is to be understood that the present disclosure is not limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

1. A method for processing uplink resources, executed by a user equipment UE, characterized in that: include: Reporting a buffer status report BSR including the delay to the base station; or Obtaining, from the base station, an indication of uplink resources allocated by the base station; or In the logical channel priority LCP process, the uplink resource is allocated to the logical channel LCH with delay information.

2. The uplink resource processing method according to claim 1, characterized in that: The BSR including the delay includes the delay information and the buffer size of the LCH, the logical channel group LCG or the protocol data unit PDU set; The delay information is the remaining time of the LCH, the LCG or the PDU set; The buffer size is the amount of available data of the LCH, the LCG or the PDU set.

3. The uplink resource processing method according to claim 1, characterized in that: Reporting the BSR including the delay to the base station further includes: When a BSR triggering condition is met, the BSR is sent, wherein the BSR triggering condition includes one of the following: The data volume change related to the LCH, LCG or PDU set exceeds a data volume change threshold, wherein the data volume change threshold is configured by the base station through radio resource control RRC signaling; or The remaining time of the LCH, the LCG or the PDU set reaches a remaining time threshold, wherein the remaining time threshold is configured by the base station through the RRC signaling.

4. The uplink resource processing method according to claim 2, characterized in that: The format of the BSR includes one medium access control MAC control element CE or two MAC CEs.

5. The uplink resource processing method according to claim 4, characterized in that: In the BSR, the UE uses one MAC CE to report the buffer size and delay information, wherein the delay information is the remaining time of the delay budget of the buffer size of the LCH, the LCG or the PDU set.

6. The uplink resource processing method according to claim 5, characterized in that: The MAC CE contains delay information for different buffer size ranges.

7. The uplink resource processing method according to claim 2, characterized in that: In the BSR, the UE uses a first MAC CE to report the buffer size, and uses a second MAC CE to report the delay information.

8. The uplink resource processing method according to claim 7, characterized in that: The buffer size in the first MAC CE is associated with the delay information in the second MAC CE through an LCH identifier ID field or an LCG ID field or a PDU set ID field.

9. The uplink resource processing method according to claim 1, characterized in that: The UE obtains the indication of the uplink resource from the base station through DCI 0; The uplink resource in the indication is identified by at least one of the following IDs: LCH ID, LCG ID, DRB ID.

10. The uplink resource processing method according to claim 1, characterized in that: The UE allocates the uplink resource to the LCH in the LCP process using the delay information; The delay information of the LCH of the UE is configured by the base station using RRC signaling; The delay information includes a delay priority value or a delay sensitivity indication.

11. A user equipment UE, characterized in that: Instructions are stored which, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 10.

12. A chip, characterized in that: include: The processor is configured to call and run the computer program stored in the memory so that the device on which the chip is mounted executes the method according to any one of claims 1 to 10.

13. A computer-readable storage medium, characterized in that: A computer program is stored, the computer program causing a computer to execute the method according to any one of claims 1 to 10.

14. A computer program product, characterized in that A computer program is included, which causes a computer to execute the method according to any one of claims 1 to 10.

15. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 10.

16. An uplink resource processing method, executed by a base station, characterized in that: include: Receiving a buffer status report BSR including a delay from a user equipment UE, wherein the BSR including a delay includes delay information; allocating uplink resources in response to the BSR including the delay; and Sending an indication of the allocated uplink resources.

17. The uplink resource processing method according to claim 16, characterized in that: The BSR including the delay includes the delay information and the buffer size of the LCH, the logical channel group LCG or the protocol data unit PDU set; The delay information is the remaining time of the LCH, the LCG or the PDU set; The buffer size is the amount of available data of the LCH, the LCG or the PDU set.

18. The uplink resource processing method according to claim 16, characterized in that: Also includes: When a BSR triggering condition is met, receiving the BSR, wherein the BSR triggering condition includes one of the following: The data volume change related to the LCH, LCG or PDU set exceeds a data volume change threshold, wherein the data volume change threshold is configured by the base station through radio resource control RRC signaling; or The remaining time of the LCH, the LCG or the PDU set reaches a remaining time threshold, wherein the remaining time threshold is configured by the base station through the RRC signaling.

19. The uplink resource processing method according to claim 17, characterized in that: The format of the BSR includes one medium access control MAC control element CE or two MAC CEs.

20. The uplink resource processing method according to claim 19, characterized in that: In the BSR, the base station receives a MAC CE reporting a buffer size and delay information, wherein the delay information is a remaining time of a delay budget of a buffer size of the LCH, the LCG or the PDU set.

21. The uplink resource processing method according to claim 20, characterized in that: The MAC CE contains delay information for different buffer size ranges.

22. The uplink resource processing method according to claim 18, characterized in that: In the BSR, the base station receives a first MAC CE to report the buffer size, and receives a second MAC CE to report the delay information.

23. The uplink resource processing method according to claim 22, characterized in that: The buffer size in the first MAC CE is associated with the delay information in the second MAC CE through an LCH identifier ID field or an LCG ID field or a PDU set ID field.

24. The uplink resource processing method according to claim 16, characterized in that: The base station sends the indication of the uplink resource through DCI 0; The uplink resource in the indication is identified by at least one of the following IDs: LCH ID, LCG ID, DRB ID.

25. The uplink resource processing method according to claim 16, characterized in that: The UE allocates the uplink resource to the LCH in the LCP process using the delay information; The delay information of the LCH of the UE is configured by the base station using RRC signaling; The delay information includes a delay priority value or a delay sensitivity indication.

26. A base station, characterized in that: Instructions are stored which, when executed by a computer, cause the computer to perform the method of any one of claims 16 to 25.

27. A chip, characterized in that: include: The processor is configured to call and run the computer program stored in the memory so that the device on which the chip is mounted executes the method according to any one of claims 16 to 25.

28. A computer-readable storage medium, characterized in that: A computer program is stored, the computer program causing a computer to execute the method according to any one of claims 16 to 25.

29. A computer program product, characterized in that Comprising a computer program causing a computer to execute the method of any one of claims 16 to 25.

30. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 16 to 25.

Images