Method executed by user equipment, and user equipment

Abstract

Provided in the present invention are a method executed by a user equipment, and a user equipment. The method executed by a user equipment (UE) comprises: for an active cell group, a UE triggering a buffer status report (BSR) when any one of the following conditions 1-3 is satisfied: condition 1: unnecessary PDUs or PDU sets or a synchronized PDU cluster are / is deleted, or the PDUs or the PDU sets or PDUs or PDU sets in the synchronized PDU cluster are deleted; condition 2: the amount of deleted PDUs or deleted PDU sets or the deleted PDUs or PDU sets in the synchronized PDU cluster or deleted data exceeds a configured threshold parameter for the amount of deleted data; and condition 3: deleting the PDUs or the PDU sets or the data results in an index corresponding to the total amount of data of all logical channels in at least one logical channel group being different from an index of logical channel groups contained in a BSR MAC CE most recently sent by the UE to a base station.

Description

Methods executed by user equipment and user equipment Technical Field

[0001] This invention relates to the field of wireless communication technology, and more specifically, to a method performed by a user equipment and a user equipment. Background Technology

[0002] Currently, one of the research goals related to Extended Reality (XR) in 3GPP is to improve effective support for XR applications with multi-modal inter-dependencies and multi-QoS flows, meeting multi-modal QoS requirements such as synchronization and / or coordination (see also TR22.847 and TR23.70060). The expected efficiency improvements in terms of capacity and power consumption are anticipated to be significant. Potential impacts include: a) enhanced RAN awareness through signaling from the core network and / or indications from the UE; b) enhanced user plane features such as scheduling, Logical Channel Priority (LCP), resource allocation, packet dropping, etc.

[0003] This invention discusses related issues involving multi-mode data synchronization and / or coordination. Summary of the Invention

[0004] To address at least some of the above-mentioned problems, the present invention provides a method performed by a user equipment and a user equipment thereof.

[0005] According to a first aspect of the present invention, a method performed by a user equipment (UE) is provided, comprising: for an active cell group, the UE triggering a buffer state report (BSR) when any one of the following conditions 1 to 3 is met: condition 1: unnecessary PDUs or PDU sets or synchronous PDU clusters are deleted, or PDUs or PDU sets in a synchronous PDU cluster are deleted; condition 2: the amount of deleted PDUs or PDU sets or PDU sets in a synchronous PDU cluster or the amount of deleted data exceeds a configured threshold parameter for the amount of deleted data; condition 3: the deletion of PDUs or PDU sets or data results in an index corresponding to the total amount of data of all logical channels in at least one logical channel group being different from the index of the logical channel group included in the BSR MAC CE most recently sent by the UE to the base station.

[0006] In the method of the first aspect described above, the UE is configured by the base station via an RRC message with a threshold parameter for the amount of data to be deleted.

[0007] In the method of the first aspect described above, each logical channel or logical channel group is configured with a threshold parameter for the amount of data to be deleted, and the BSR is triggered when the number of PDUs or PDU sets or the amount of data deleted in a logical channel exceeds the threshold parameter for the amount of data to be deleted.

[0008] In the method of the first aspect described above, the UE is configured with a threshold parameter for the amount of data deleted, and the BSR is triggered when the number of deleted PDUs or PDU sets or data in a logical channel exceeds the configured threshold parameter for the amount of data deleted, or when the total number of deleted PDUs or PDU sets or data in all logical channels of a logical channel group exceeds the configured threshold parameter for the amount of data deleted.

[0009] In the method of the first aspect described above, the UE is configured with a set of threshold parameters for the amount of data to be deleted that are associated with the index, data volume, or buffer size, and the corresponding threshold parameters for the amount of data to be deleted are determined based on the current buffer size.

[0010] In the method of the first aspect above, the UE is configured with an index offset parameter by the base station via an RRC message. When the deletion of a PDU or a PDU set or data causes the offset between the index corresponding to the data volume of one or more logical channel groups and the index of the corresponding logical channel group contained in the BSR MAC CE most recently sent by the UE to the base station to exceed the value indicated by the index offset parameter, the BSR is triggered.

[0011] In the method of the first aspect above, the UE is configured with the parameter bsrTriggerAllowed by the base station via an RRC message. The parameter bsrTriggerAllowed is used to indicate that the UE is allowed to trigger BSR due to a change in the amount of data in one or more logical channel groups caused by the deletion of PDUs or PDU sets or data.

[0012] In the method of the first aspect described above, the BSR is a regular BSR or a periodic BSR.

[0013] In the method of the first aspect mentioned above, when a regular BSR or periodic BSR is triggered when multiple logical channels delete PDUs or PDU sets or data, each logical channel that deletes PDUs or PDU sets or data triggers a BSR.

[0014] Furthermore, according to a second aspect of the present invention, a user equipment is provided, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the methods described above.

[0015] Invention Effects

[0016] According to the method performed by the user equipment provided by the present invention and the corresponding user equipment, the resource waste caused by the base station still providing uplink resources according to the uplink data volume previously reported by the UE can be avoided when all the data in a synchronous PDU cluster is deleted. Attached Figure Description

[0017] The above and other features of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, wherein:

[0018] Figure 1 is a schematic diagram of the protocol stack involved in the air interface transmission of data according to the present invention.

[0019] Figure 2 is a flowchart illustrating the processing procedure in Embodiment 1 of the present invention.

[0020] Figure 3 is a flowchart illustrating the processing procedure in Embodiment 2 of the present invention.

[0021] Figure 4 is a flowchart illustrating the processing procedure in Embodiment 3 of the present invention.

[0022] Figure 5 is a block diagram illustrating the user equipment (UE) involved in this invention. Detailed Implementation

[0023] The following describes some of the terms involved in this invention. For the specific meanings of these terms, please refer to the latest relevant 3GPP documents, such as TS38.300, TS38.321, TS38.323, and TS38.331. Furthermore, this invention is described using broadcast / multicast services as an example, but the embodiments of this invention are not limited to broadcast / multicast services and can also be applied to other application scenarios.

[0024] UE: User Equipment.

[0025] RRC: Radio Resource Control.

[0026] RRC_CONNECTED: RRC connection state.

[0027] RRC_INACTIVE: RRC inactive state.

[0028] RRC_IDLE: RRC idle state.

[0029] RAN: Radio Access Network.

[0030] NR: New RAT, New Radio Access Technology.

[0031] AS: Access Stratum.

[0032] NAS: NonAccess Stratum.

[0033] RB: Radio Bearer. DRB: Data Radio Bearer.

[0034] PDU: Protocol Data Unit

[0035] SDU: Service Data Unit

[0036] SDAP: Service Data Adaptation Protocol

[0037] PDCP: Packet Data Convergence Protocol

[0038] RLC: Radio Link Control

[0039] MAC: Medium Access Control

[0040] HARQ: Hybrid Automatic Repeat reQuest. The HARQ entity or process is located at the MAC layer or MAC entity.

[0041] BSR: Buffer Status Reporting. The Buffer Status Reporting process is used to provide the serving gNB with information about the amount of uplink UL data in the MAC entity. The UE uses this process to send a BSR MAC Control Element (BSR MAC CE) to the base station. The BSR MAC CE contains the buffer size corresponding to each Logical Channel Group (LCG) (indicated by the LCG ID field in the BSR MAC CE or by bits in a bitmap corresponding to each LCG). The buffer size is indicated by a buffer size field, which identifies the total amount of data available on all logical channels of the corresponding logical channel group after the MAC PDU is constructed, based on the data volume calculation process in TS 38.322-i10 and 38.323-i20. The value of the buffer size field is an index defined in Table 6.1.3.1-1 (applicable when the buffer size field occupies 5 bits, denoted as Table 1) or Table 6.1.3.1-2 (applicable when the buffer size field occupies 8 bits, denoted as Table 2) in TS38.321-i20. The buffer size indicated by each index corresponds to the range indicated by the BS value.

[0042] Table 1: Buffer size levels for the 5-bit buffer size field (in bytes)

[0043] Table 2: Buffer size levels (in bytes) for the 8-bit buffer size field

[0044] A PDU set consists of one or more PDUs that carry the payload of a single information unit (SDU) generated at the application level (e.g., a frame or video slice of the XRM service used in TR 26.926). In some implementations, the application layer requires all PDUs in the PDU set to use the corresponding SDU. In other implementations, the application layer can still recover some or all of the SDUs even if some PDUs are lost. One PDU in the PDU set corresponds to one PDCP SDU.

[0045] Multi-modal data is defined as input data from different types of devices / sensors or output data to different types of destinations (e.g., one or more UEs) required to describe the same task or application. Multi-modal data consists of multiple single-modal data sets, each with strong dependencies on the others. A single-modal data set can be viewed as a single type of data. Each single-modal data set can be mapped to a data flow.

[0046] Multi-modal service: A multi-modal service is a communication service consisting of multiple interconnected data streams that require application coordination. These data streams can transmit different types of data (e.g., audio, video, location, haptic data) and may originate from different sources (e.g., a single UE, a single device connected to a single UE, or multiple devices, or multiple UEs). In the case of a single UE, these data streams (i.e., multi-modal data) are closely related and require strong application coordination to execute multi-modal applications correctly; therefore, all these data streams are transmitted within a single PDU session.

[0047] A Multi-modal Service ID (MMSID) is used to indicate a data flow associated with a multi-modal service. Data flows with the same MMSID belong to the same multi-modal service.

[0048] Synchronization threshold: A multi-modal synchronization threshold can be defined as the maximum tolerable temporal separation of the onset of two stimuli, one presented to one sense and the other to another sense, such that the accompanying sensory objects are perceived as being synchronous. Synchronization relationships may exist between single-mode data within the same multi-modal dataset. A PDU set from one single-mode dataset may be synchronized with PDU sets from one or more other single-mode datasets. For example, when data transmission of one PDU set begins (or ends), data transmission of one or more synchronized PDU sets must begin (or end) within the time limit limited by the synchronization threshold. In this disclosure, the collection of PDU sets consisting of two or more synchronized PDU sets is referred to as a synchronized PDU cluster.

[0049] Figure 1 illustrates an example of the protocol stack involved in air interface data transmission according to this disclosure. The protocol stack, from top to bottom, consists of SDAP, PDCP, RLC, MAC, and the physical layer. The lower layer of the SDAP layer can be PDCP and / or RLC and / or MAC, the lower layer of the PDCP layer can be RLC and / or MAC, and the lower layer of the RLC layer can be MAC. Correspondingly, the upper layer of the MAC layer can be SDAP and / or PDCP and / or RLC, the upper layer of the RLC layer can be SDAP and / or PDCP, and the upper layer of the PDCP layer can be SDAP. The functions of each layer are implemented by corresponding entities. Specifically, the functions of the MAC layer are implemented by the MAC entity, the RLC layer by the RLC entity, the PDCP layer by the PDCP entity, and the SDAP layer by the SDAP entity. In this disclosure, layers and entities are used interchangeably. When referring to a certain layer or entity, if it is not specifically stated whether it is an entity or a layer, those skilled in the art can infer from the context whether it refers to the corresponding layer or entity.

[0050] From the UE's perspective, for downlink, when the physical layer receives data from the base station, it delivers it to the MAC layer. The MAC layer processes the data and then transmits it to the RLC layer. The RLC layer processes the data and then transmits it to the PDCP layer. The PDCP layer processes the data and then transmits it to the SDAP layer. The SDAP layer processes the data and then transmits it to the upper layer (e.g., the NAS layer). For uplink, the SDAP layer receives data from the upper layer (e.g., the NAS layer), processes it, and then submits it to the PDCP layer. The PDCP layer processes the data and then submits it to the RLC layer. The RLC layer processes the data and then submits it to the MAC layer. The MAC layer processes the data and then submits it to the physical layer. The physical layer processes the data and then transmits it to the base station over the air interface. For each layer, the data received from the upper layer is called SDU, and the data submitted to the lower layer is called PDU. For example, data received or transmitted from the SDAP layer to the SDAP layer by the PDCP layer is called PDCP SDU (i.e., SDAP PDU), and data received or submitted from the RLC layer to the RLC layer by the PDCP layer is called PDCPPDU (i.e., RLC SDU), and the same applies to other layers.

[0051] In this invention, the network, base station, and RAN can be used interchangeably. The network can be a Long Term Evolution (LTE) network, an NR network, an enhanced Long Term Evolution (eLTE) network, or other networks defined in subsequent 3GPP evolution versions, such as a 6G network.

[0052] One aspect of the current R19 XR discussion focuses on is the synchronization between multi-mode data. In other words, to achieve synchronization or coordination between data (or PDUs or sets of PDUs) from different data streams, when data transmission of a PDU set begins (or ends), the transmission of data from one or more PDU sets synchronized with it (i.e., other PDU sets within the synchronized PDU cluster) must begin (or end) within a time limit restricted by a synchronization threshold. When data from a PDU set (the entire PDU set or a portion of the PDUs within the PDU set) is deleted or not correctly received (or confirmed as not correctly received or transmission failed), all PDU sets belonging to the same multi-mode data (or synchronized PDU cluster) as the said PDU set may be deleted, or data in the synchronized PDU cluster may be deleted because it was not sent within the time limit restricted by the synchronization threshold. In this disclosure, PDUs or sets of PDUs deleted for the above reasons or other reasons may be referred to as unnecessary PDUs or sets of PDUs. Currently, the UE reports the current buffered uplink data volume to the base station by sending a BSR MAC CE (Control Element) through the BSR procedure. The base station then provides corresponding uplink resources to enable the UE to send the buffered data. However, if all the data in a synchronization PDU cluster is deleted, the base station may still provide uplink resources based on the previously reported uplink data volume without knowing this information, leading to resource waste.

[0053] The following examples are provided to solve this problem.

[0054] The following describes an example of a UE triggering a BSR when data in the synchronized PDU cluster is deleted.

[0055] Example 1

[0056] In Example 1, as shown in Figure 2, for an activated cell group, when the condition "unnecessary PDUs or PDU sets or synchronization PDU clusters are deleted or PDUs or PDU sets in synchronization PDU clusters are deleted" is met (step S101), BSR is triggered (step S102).

[0057] Example 2

[0058] In Embodiment 2, as shown in Figure 3, for an active cell group, BSR is triggered (step S202) when the condition "the deleted PDUs, the deleted PDU set, or the PDUs or PDU set in the deleted synchronization PDU cluster, or the deleted data amount (i.e., the data amount of deleted data) exceeds the configured threshold parameter for the deleted data amount (i.e., the value configured for the parameter)" is met (step S201). In this embodiment, the base station needs to configure the threshold parameter for the deleted data amount for the UE through an RRC message (e.g., an RRC reconfiguration message). After configuring the threshold parameter for the deleted data amount, the UE determines whether the condition for triggering BSR set in this embodiment is met. Optionally, a threshold parameter for the deleted data amount can be configured for each logical channel or logical channel group. BSR is triggered only when the deleted PDUs or PDU set or data amount of a logical channel exceeds its corresponding threshold for the deleted data amount, or when the total deleted PDUs or PDU set or data amount of all logical channels in the LCG exceeds its corresponding threshold for the deleted data amount. Optionally, a threshold parameter for the amount of deleted data can be configured for the UE. BSR is triggered only if the number of deleted PDUs or PDU sets or the amount of data for at least one logical channel exceeds the configured threshold, or if the total number of deleted PDUs or PDU sets or the amount of data for all logical channels in at least one logical channel group exceeds the configured threshold. Optionally, the base station can also configure a set of threshold parameters for the amount of deleted data associated with an index, data volume, or buffer size for the UE via an RRC message. The UE determines the corresponding threshold based on the current buffer size. BSR is triggered only if the number of deleted PDUs or PDU sets or the amount of data for one logical channel exceeds its corresponding threshold, or if the total number of deleted PDUs or PDU sets or the amount of data for all logical channels in an LCG exceeds its corresponding threshold. An additional parameter can be added to the RRC message to indicate the table to which the index applies, which can be Table 1 or Table 2. For example, the threshold for the amount of data deleted is set to 10 bytes for index 5, 1500 bytes for index 20, and 2500 bytes for index 31. If the UE's current (or data before deleting a PDU, PDU set, or data) buffer size or the amount of data indicated in the most recently transmitted BSRMAC CE is less than the BS value indicated by index 20 but greater than the BS value indicated by index 5, and the amount of deleted PDUs, PDU sets, or data exceeds 1500 bytes, then a BSR is triggered.

[0059] Example 3

[0060] In Example 3, for an active cell group, if the condition is met that "the index corresponding to the amount of data for one or more logical channel groups caused by deleting PDUs or PDU sets or data (i.e., the total amount of data or buffer size of all logical channels in at least one logical channel group caused by deleting PDUs or PDU sets or data) is different from (may be greater than or less than) the index of the logical channel group contained in the BSR MAC CE most recently sent by the UE to the base station (i.e., the value of the buffer size field corresponding to the logical channel group in the BSR MAC CE)" (step S301), then BSR is triggered (step S302). The base station can also first configure an index offset parameter for the UE via an RRC message (e.g., an RRC reconfiguration message). In this scenario, for an active cell group, a BSR is triggered when the following condition is met: Deleting a PDU or PDU set or data results in the index corresponding to the total amount of data (or buffer size) of all logical channels in at least one logical channel group being offset from the index of that logical channel group (i.e., the value of the buffer size field) contained in the BSR MAC CE most recently sent by the UE to the base station, exceeding (can be greater than or less than) the value indicated by the index offset parameter. For example, if the configured index offset parameter value is 3, the index of the logical channel group contained in the BSR MAC CE most recently sent by the UE to the base station is 28, and after the UE deletes a PDU or PDU set or data, there exists an index corresponding to the total amount of data of all logical channels in a logical channel group that is 20. Since the offset between 20 and 28 is 8, which is greater than 3, a BSR is triggered. It should be noted that the deletion of a PDU or PDU set or data is event-triggered. When the event occurs, the UE determines whether the deletion of a PDU or PDU set or data results in the index corresponding to the total amount of data or buffer size of all logical channels in at least one logical channel group being different from the value or index of the buffer size field corresponding to the logical channel group contained in the BSR MAC CE most recently sent by the UE to the base station.

[0061] Optionally, in embodiments 1-3, when calculating the deleted PDUs or PDU sets or data, the amount of data sent by the UE from the last time it sent a BSR MAC CE until the PDU or PDU set or data was deleted can be included in the calculation.

[0062] In this embodiment of the disclosure, the deleted PDU or PDU set or data volume is the deleted PDU or PDU set or deleted data volume in the synchronous PDU cluster.

[0063] Regarding embodiments 1-3 for triggering BSR described above, optionally, the base station first configures a parameter bsrTriggerAllowed via an RRC message (e.g., an RRC reconfiguration message) to indicate that BSR is triggered due to a change in the amount of data in one or more logical channel groups caused by the deletion of a PDU or PDU set or data. This change can be one of the conditions for triggering BSR defined in the above embodiments. Only when the UE is configured with the parameter bsrTriggerAllowed does the UE determine whether the conditions for triggering BSR defined in embodiments 1-3 of this disclosure are met, and triggers BSR if the conditions are met. The RRC message carrying the parameter bsrTriggerAllowed can be the same message or a different message from the RRC message mentioned in the embodiments for triggering BSR described above.

[0064] Regarding embodiments 1-3 of this disclosure for triggering BSR, it can be stipulated that a BSR triggered due to the fulfillment of the conditions set in the embodiments of this disclosure for triggering BSR is a regular BSR.

[0065] Regarding embodiments 1-3 of this disclosure for triggering BSR, it can also be stipulated that the BSR triggered due to the fulfillment of the conditions set in embodiments 1-3 of this disclosure for triggering BSR is a periodic BSR.

[0066] Regarding embodiments 1-3 of this disclosure for triggering BSR, it can be stipulated that each logical channel that deletes a PDU or PDU set or data triggers a BSR. In other words, when multiple logical channels delete PDUs or PDU sets or data and trigger a regular BSR or periodic BSR, each logical channel that deletes a PDU or PDU set or data triggers a BSR.

[0067] For embodiments 1-3 of this disclosure regarding triggering BSR, it can be stipulated that only one BSR is triggered each time a PDU or PDU set or data is deleted, and it is considered that the logical channel that triggers the BSR is the logical channel with the highest (or lowest) priority corresponding to the deleted PDU or PDU set or data, or that the logical channel that triggers the BSR is a logical channel with uplink data to be transmitted and the highest (or lowest) priority.

[0068] In this disclosure, fields, domains, and information elements are used interchangeably. In embodiments of this disclosure, if multiple operations are included, embodiments obtained by changing the execution order of the operations are also within the scope of protection of this disclosure. Similarly, when multiple parallel judgment conditions are included, embodiments obtained by changing the order of the judgment conditions are also within the scope of protection of this disclosure. The terms "and," "or," "and / or," "and," and "and" in the conditions involved in the embodiments of this disclosure are used interchangeably, and embodiments obtained from these interchangeably are also within the scope of this disclosure.

[0069] Hereinafter, FIG5 will be used to illustrate a user equipment that can perform the method described in detail above as an embodiment of the present invention.

[0070] Figure 5 is a block diagram illustrating the user equipment (UE) involved in this invention.

[0071] As shown in Figure 5, the user equipment UE400 includes a processor 401 and a memory 402. The processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 402 may include, for example, volatile memory (such as random access memory, RAM), a hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory. Program instructions are stored on the memory 402. When executed by the processor 401, these instructions can perform the methods described in detail herein, executed by the user equipment.

[0072] The above describes in detail the method executed by the user equipment and the user equipment involved in the present invention based on Embodiment 1, etc. However, the present invention is not limited to the method executed by the user equipment and the user equipment; it can also be implemented in other ways as long as the main idea of ​​the present invention can be achieved.

[0073] For example, the present invention can also be implemented through a base station or a communication system including user equipment and a base station. For example, the base station communicates with the user equipment, configures various parameters (e.g., parameters related to BSR) for the user equipment, and receives BSR-related information sent by the user equipment.

[0074] The methods and related apparatus of this disclosure have been described above in conjunction with preferred embodiments. Those skilled in the art will understand that the methods shown above are merely exemplary, and the various embodiments described above can be combined with each other without contradiction. The methods of the present invention are not limited to the steps and order shown above.

[0075] In the embodiments of this disclosure, when multiple operations are included, the execution order of each operation is exemplarily listed. Embodiments obtained by changing the execution order of each operation are also within the scope of protection of this disclosure. Furthermore, when multiple judgment conditions are included, embodiments obtained by changing the execution order of each judgment condition are also within the scope of protection of this disclosure. In addition, unless otherwise specified in this disclosure, the meaning of a domain defined in one embodiment can also be applied to the corresponding domain involved in other embodiments. Furthermore, in the embodiments of this disclosure, "if…", "when…", "when…", "in…", "satisfies…", or "satisfies…condition" can be replaced with "in the case of…". In the embodiments of this disclosure, embodiments obtained by replacing "and", "and", and "and" in some or all conditions with "or" are also within the scope of protection of this disclosure; embodiments obtained by replacing "or" in some or all conditions with "and" are also within the scope of protection of this disclosure.

[0076] Furthermore, the user equipment shown above may include more modules, such as modules that can be developed or will be developed in the future for use with base stations, MMEs, or UEs, etc. The various identifiers shown above are merely exemplary and not limiting, and this disclosure is not limited to the specific information elements exemplified by these identifiers. Many variations and modifications can be made by those skilled in the art based on the teachings of the illustrated embodiments.

[0077] It should be understood that the above embodiments of this disclosure can be implemented by software, hardware, or a combination of both. For example, the various components inside the base station and user equipment in the above embodiments can be implemented by a variety of devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, proprietary integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic devices (CPLDs), and so on.

[0078] Furthermore, the computer-executable instructions or program running on the device according to the invention can be a program that enables the computer to perform the functions of the embodiments of the invention by controlling the central processing unit (CPU). The program or the information processed by the program can be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.

[0079] Computer-executable instructions or programs for implementing the functions of the various embodiments of the present invention can be recorded on a computer-readable storage medium. The corresponding functions can be implemented by causing a computer system to read and execute the programs recorded on the recording medium. The term "computer system" here can refer to a computer system embedded in the device, and may include an operating system or hardware (such as peripheral devices). "Computer-readable storage medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a short-time dynamic program storage medium, or any other computer-readable recording medium.

[0080] Various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (e.g., monolithic or multi-chip integrated circuits). Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), proprietary integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. A general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The above circuits may be digital circuits or analog circuits. In cases where advancements in semiconductor technology have led to new integrated circuit technologies that replace existing integrated circuits, one or more embodiments of the present invention may also be implemented using these new integrated circuit technologies.

[0081] Furthermore, the present invention is not limited to the embodiments described above. Although various examples of the embodiments have been described, the present invention is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0082] As described above, embodiments of the present invention have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above embodiments, and the present invention also includes any design modifications that do not depart from the spirit of the invention. Furthermore, various modifications can be made to the present invention within the scope of the claims, and embodiments obtained by appropriately combining the technical means invented in different embodiments are also included within the technical scope of the present invention. In addition, components with the same effects described in the above embodiments can be substituted for each other.

Claims

1. A method performed by a user equipment (UE), comprising: for an activated cell group, the UE triggers a buffer status report (BSR) when any one of the following conditions 1-3 is met, condition 1: a deleted PDU or PDU set or PDU or PDU set in a deleted synchronization PDU set group; condition 2: a deleted amount of data in a deleted PDU or a deleted PDU set or a PDU or a PDU set in a deleted synchronization PDU set group exceeds a configured threshold of deleted data amount; condition 3: deletion of a PDU or a PDU set or data results in that an index corresponding to a total amount of data of all logical channels in at least one logical channel group is different from an index of the logical channel group contained in a BSR MAC CE that the UE sent to a base station last time. 2.The method of claim 1, wherein the UE is configured by the base station with the threshold of deleted data amount by RRC message. 3.The method of claim 2, wherein each logical channel or logical channel group is configured with a threshold of deleted data amount, the BSR is triggered when a deleted PDU or PDU set or amount of data of one logical channel exceeds the respective threshold of deleted data amount. 4.The method of claim 2, wherein the UE is configured with one threshold of deleted data amount, the BSR is triggered when a deleted PDU or PDU set or amount of data of one logical channel exceeds the configured threshold of deleted data amount, or a total amount of deleted PDU or PDU set or data of all logical channels in one logical channel group exceeds the configured threshold of deleted data amount. 5.The method of claim 2, wherein the UE is configured with a set of thresholds of deleted data amount associated with an index or amount of data or buffer size, and determines the corresponding threshold of deleted data amount according to a current buffer size. 6.The method of claim 1, wherein the UE is configured by the base station with an index offset parameter by RRC message, the BSR is triggered when deletion of a PDU or a PDU set or data results in that an offset of an index corresponding to an amount of data of one or more logical channel groups from an index of the corresponding logical channel group contained in a BSR MAC CE that the UE sent to the base station last time exceeds a value indicated by the index offset parameter. 7.The method of claim 1, wherein the UE is configured by the base station with a parameter bsrTriggerAllowed by RRC message, the parameter bsrTriggerAllowed is used to indicate that the UE is allowed to trigger a BSR due to a change of an amount of data corresponding to one or more logical channel groups caused by deletion of a PDU or a PDU set or data. 8.The method of claim 1, wherein the BSR is a regular BSR or a periodic BSR. 9.The method of claim 1, wherein When multiple logical channels are deleted PDU or PDU set or data trigger regular BSR or periodic BSR, each logical channel of the deleted PDU or PDU set or data triggers a BSR.

10. A user equipment (UE), comprising: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, perform the method of any of claims 1-9.

Images