Information processing method, communication device, communication system, and storage medium

Abstract

The embodiment of the disclosure provides an information processing method, a communication device, a communication system and a storage medium. The information processing method is executed by a terminal and includes: in the case that at least two first events are detected, sending first information, wherein the first information is used for indicating at least a data amount associated with a second event; wherein the second event is determined based on the at least two first events; and the first event is an event of a BSR or an event of a DSR.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to an information processing method, communication device, communication system and storage medium. Background Technology

[0002] In the field of communication technology, a reporting mechanism for Buffer Status Report (BSR) and / or a reporting mechanism for Delay Status Report (DSR) have been introduced. Summary of the Invention

[0003] The embodiments disclosed herein need to address the reporting problem when BSR and DSR are triggered in parallel.

[0004] According to a first aspect of the present disclosure, an information processing method is proposed, executed by a terminal, comprising: sending first information upon detecting the triggering of at least two first events, wherein the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; and the first events are events of a BSR or events of a DSR.

[0005] According to a second aspect of the present disclosure, an information processing method is proposed, executed by a network device, comprising: receiving first information, wherein the first information is sent by a terminal upon detecting the triggering of at least two first events; the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; and the first event is a BSR event or a DSR event.

[0006] According to a third aspect of the present disclosure, an information processing method is proposed, executed by a communication system, the communication system including a terminal and a network device, the method comprising: the terminal sending first information to the network device upon detecting the triggering of at least two first events, wherein the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; the first events are events of a BSR or events of a DSR.

[0007] According to a fourth aspect of the present disclosure, a terminal is provided, comprising: a first transceiver module configured to send first information upon detecting the triggering of at least two first events, wherein the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; and the first events are events of a BSR or events of a DSR.

[0008] According to a fifth aspect of the present disclosure, a network device is provided, comprising: a second transceiver module configured to receive first information, wherein the first information is sent by a terminal upon detecting the triggering of at least two first events; the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; and the first event is a BSR event or a DSR event.

[0009] According to a sixth aspect of the embodiments of this disclosure, a communication device is provided, which is used to perform an implementation of such a first aspect, a second aspect, or an optional implementation of the first and second aspects.

[0010] According to a seventh aspect of the present disclosure, a communication system is provided, comprising: a terminal and a network device; wherein the terminal is configured to perform the method described in the optional implementation of the first aspect, and the network device is configured to perform the method described in the optional implementation of the second aspect.

[0011] According to an eighth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect, the second aspect, or an optional implementation of the first and second aspects.

[0012] According to a ninth aspect of the present disclosure, a program product is provided, including at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the method described as in the first aspect, the second aspect, or an optional implementation of the first and second aspects.

[0013] The embodiments disclosed herein enable information reporting in a unified format when BSR and DSR are triggered in parallel. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0015] Figure 1A This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0016] Figure 1B This is a schematic diagram illustrating a DSR format according to an embodiment of the present disclosure.

[0017] Figure 2A This is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.

[0018] Figure 2BThis is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.

[0019] Figure 2C This is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.

[0020] Figure 3 This is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.

[0021] Figure 4A This is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure.

[0022] Figure 4B This is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure.

[0023] Figure 5A This is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0024] Figure 5B This is a schematic diagram of the chip structure provided according to an embodiment of the present disclosure. Detailed Implementation

[0025] This disclosure provides an information processing method, a communication device, a communication system, and a storage medium.

[0026] In a first aspect, embodiments of this disclosure propose an information processing method executed by a terminal, comprising: sending first information upon detecting the triggering of at least two first events, wherein the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; and the first events are events of a BSR or events of a DSR.

[0027] In the above embodiments, when at least two first events (e.g., BSR or DSR events) are triggered, the data volume associated with the second event can be reported based on the first information in a unified format. The second event is determined based on at least two first events. In this way, when BSR and DSR are triggered in parallel, the reporting of a first information (i.e., the reporting of information in a unified format) can be realized, thereby reducing the waste of uplink resources and simplifying the reporting mechanism.

[0028] In conjunction with some embodiments of the first aspect, in some embodiments, the BSR event includes at least one of the following: a regular BSR event, a filling BSR event, a retransmission BSR event, and a periodic BSR event; at least two first events, including one of the following: a regular BSR event and a DSR event; a filling BSR event and a DSR event; a retransmission BSR event and a DSR event; a periodic BSR event and a DSR event.

[0029] In the above embodiments, the parallel triggering of different types of BSR and DSR can enable the reporting of a first piece of information (i.e., the reporting of information in a unified format) when at least two first events are triggered, thereby helping the base station to optimize uplink resource allocation and reduce resource waste.

[0030] In conjunction with some embodiments of the first aspect, in some embodiments, before sending the first information, one of the following is further included: determining a second event based on at least two first events; maintaining at least two first events.

[0031] In the above embodiments, the terminal can merge at least two first events into one trigger event or maintain at least two independent trigger events, which enables the terminal to make decisions based on specific circumstances and improves the flexibility of the terminal.

[0032] In conjunction with some embodiments of the first aspect, in some embodiments, determining a second event based on at least two first events includes one of the following: determining one of the at least two first events as the second event, and canceling other events among the at least two first events except for the first event of the first type; determining the second event when the at least two first events include a second event of the first type and a third event of the first type, wherein the data associated with the second event of the first type and the data associated with the third event of the first type are associated, or the data associated with the second event of the first type and the data associated with the third event of the first type are not associated.

[0033] In the above embodiments, when the data associated with at least two first events are not related, the at least two first events can be merged into a new event. This facilitates the terminal in merging the information that needs to be reported into a single report, saving uplink resources and simplifying the reporting mechanism. Alternatively, when the data associated with at least two first events are related, for example, if the data associated with a second type of first event contains data associated with a third type of first event, then a first piece of information can be reported based on the second type of first event, thereby saving uplink resources and simplifying the mechanism.

[0034] Alternatively, one of the at least two first events can be retained, while the other events are canceled from triggering; this also makes it easier to merge the information that needs to be reported into one information report, thereby saving uplink resources and simplifying the reporting mechanism.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: sending a scheduling request (SR), wherein the SR is used to request a resource for sending the first information.

[0036] In the above embodiments, resources for sending the first information can be obtained by reporting the SR, which can effectively request transmission resources and facilitate the acquisition of suitable transmission resources, thereby improving the reliability of transmission.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, sending a scheduling request (SR) includes one of the following: sending a first SR when at least two first events are determined to be a second event; or sending at least two second SRs corresponding to the at least two first events while maintaining at least two first events.

[0038] In the above embodiments, when at least two first events are merged into one second event, only one first SR can be reported, thereby saving uplink resources. Alternatively, while maintaining at least two first events, multiple second SRs can be sent, with one second SR corresponding to one first event; this allows for sending corresponding second SRs for different triggering events, which is beneficial for obtaining appropriate resources for sending first information and improving the efficiency of obtaining resources for sending first information.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, at least two first events occur in the same entity, and the resource requested by the first SR is: the resource of any one of the at least two first events in the entity; at least two first events occur in the same entity, and the resource requested by the first SR is: the resource with the highest priority among the at least two first events in the entity; at least two first events occur in at least two entities, and the resource requested by the first SR is: the resource of any one of the first events in any one of the at least two entities; at least two first events occur in at least two entities, and the resource requested by the first SR is: the resource of any one of the first events in the entity with the highest priority among the at least two entities, or the resource with the highest priority among the first events in the entity with the highest priority among the at least two entities.

[0040] In the above embodiments, the resource requested by the SR can be determined when at least two first events occur in the same entity or different entities; thus, by defining multiple resource allocation methods, the flexibility and rationality of resource allocation can be improved.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the entity is one of the following: logical channel (LCH); logical channel group (LCG).

[0042] In the above embodiments, limiting resource request objects to the level of logical channels or logical channel groups enables more precise management of resource allocation and improves system management efficiency.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: canceling the other second SRs among the at least two second SRs except the second SR that requested the resource, if any one of the at least two second SRs requests a resource.

[0044] In the above embodiments, when multiple scheduling requests are issued simultaneously, scheduling requests that have not obtained resources can be cancelled, which can effectively avoid resource waste and improve the efficiency and accuracy of resource allocation.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is also used to indicate at least one of the following: at least two first events are triggered; the event types of at least two first events.

[0046] In the above embodiments, by indicating the event trigger and event type in the first information, the base station can know the reason for the trigger and the event type, thereby improving the accuracy of the base station's resource allocation.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, sending the first information includes: sending a Media Access Control Element (MAC CE), wherein the MAC CE includes the first information.

[0048] In the above embodiments, the first information can be sent via MAC CE without adding extra signaling, thus reducing signaling overhead. Furthermore, reporting via a unified format through MAC CE can be achieved.

[0049] Secondly, embodiments of this disclosure propose an information processing method executed by a network device, comprising: receiving first information, wherein the first information is sent by a terminal upon detecting the triggering of at least two first events; the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; and the first event is a BSR event or a DSR event.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the BSR event includes at least one of the following: a regular BSR event, a filling BSR event, a retransmission BSR event, and a periodic BSR event; at least two first events, including one of the following: a regular BSR event and a DSR event; a filling BSR event and a DSR event; a retransmission BSR event and a DSR event; a periodic BSR event and a DSR event.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a scheduling request (SR), wherein the SR is used to request a resource for sending first information.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, receiving a scheduling request (SR) includes one of the following: receiving a first SR, wherein the first SR is sent by the terminal when at least two first events are determined to be a second event; or receiving at least two second SRs, wherein the at least two second SRs are sent by the terminal while maintaining at least two first events.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, at least two first events occur in the same entity, and the resource requested by the first SR is: the resource of any one of the at least two first events in the entity; at least two first events occur in the same entity, and the resource requested by the first SR is: the resource with the highest priority among the at least two first events in the entity; at least two first events occur in at least two entities, and the resource requested by the first SR is: the resource of any one of the first events in any one of the at least two entities; at least two first events occur in at least two entities, and the resource requested by the first SR is: the resource of any one of the first events in the entity with the highest priority among the at least two entities, or the resource with the highest priority among the first events in the entity with the highest priority among the at least two entities.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the entity is one of the following: logical channel (LCH); logical channel group (LCG).

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is also used to indicate at least one of the following: at least two first events are triggered; the event types of at least two first events.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, receiving the first information includes: receiving a MAC CE, wherein the MAC CE includes the first information.

[0057] Thirdly, embodiments of this disclosure propose an information processing method executed by a communication system, the communication system including a terminal and a network device, the method including: the terminal sending first information to the network device when it detects that at least two first events are triggered, wherein the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; the first events are BSR events or DSR events.

[0058] Fourthly, embodiments of this disclosure provide a terminal, including: a first transceiver module configured to send first information upon detecting at least two first events, wherein the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; and the first events are BSR events or DSR events.

[0059] Fifthly, embodiments of this disclosure provide a network device, including: a second transceiver module configured to receive first information, wherein the first information is sent by a terminal upon detecting the triggering of at least two first events; the first information is used to at least indicate the amount of data associated with a second event; wherein the second event is determined based on at least two first events; the first event is a BSR event or a DSR event.

[0060] In a sixth aspect, embodiments of this disclosure provide a communication device for performing implementations such as the first aspect, the second aspect, or an optional implementation of the first and second aspects.

[0061] In a seventh aspect, embodiments of this disclosure provide a communication system, including: a terminal and a network device; wherein the terminal is configured to perform the method described in the optional implementation of the first aspect, and the network device is configured to perform the method described in the optional implementation of the second aspect.

[0062] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect, the second aspect, or an optional implementation of the first and second aspects.

[0063] In a ninth aspect, embodiments of this disclosure provide a program product including at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the method described as in the first aspect, the second aspect, or an optional implementation of the first and second aspects.

[0064] In a tenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the information processing method as described in the first aspect, the second aspect, or an optional implementation of the first and second aspects.

[0065] Eleventhly, embodiments of this disclosure provide a chip or chip system including processing circuitry configured to perform the methods described according to the first aspect, the second aspect, or alternative implementations of the first and second aspects above.

[0066] It is understood that the aforementioned communication devices (such as terminals, network devices, etc.), communication systems, storage media, and program products are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0067] This disclosure provides an information processing method, a communication device, a communication system, and a storage medium. In some embodiments, the terms "information processing method" and "information processing method" may be used interchangeably.

[0068] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually utilized. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0069] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0070] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0071] In the embodiments disclosed herein, "multiple" refers to two or more.

[0072] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0073] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0074] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0075] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0076] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0077] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0078] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0079] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0080] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0081] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0082] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0083] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

[0084] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0085] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0086] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0087] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0088] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0089] Figure 1A This is a schematic diagram illustrating the architecture of a communication system 100 according to an embodiment of this disclosure. Figure 1A As shown, the communication system 100 includes: terminal 101 and network device 102.

[0090] In some embodiments, network device 102 may include at least one of an access network device and a core network device.

[0091] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0092] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

[0093] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0094] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0095] In some embodiments, the core network equipment may be a single device, multiple devices, or a group of devices. The device may be virtual or physical. The core network includes, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and 6G Core Network (6GCN).

[0096] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.

[0097] The following embodiments of this disclosure can be applied to Figure 1A The communication system 100 shown, or a part thereof, but not limited to it. Figure 1A The entities shown are illustrative; a communication system may include... Figure 1A All or part of the main body, or may include Figure 1A Other entities besides the main body, the number and form of each entity are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is illustrative, the entities can be unconnected or connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0098] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Futuregeneration Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0099] In some embodiments, a Buffer Status Report (BSR) should be triggered if any of the following events occur in the active cell group:

[0100] (1) Uplink data belonging to an LCH of an LCG becomes available to the Media Access Control (MAC) entity; and meets either of the following conditions: the priority of the LCH to which the uplink data belongs is higher than the priority of any other LCH in any LCG (containing available uplink data); or, none of the LCHs belonging to the LCG contain any available UL data. This type of BSR is called a "Regular BSR".

[0101] (2) When allocating uplink resources, the number of padding bits is greater than or equal to the size of the Buffer Status Report (BSR) MAC control element (CE) and its subheader. This type of BSR is called a "Padding BSR".

[0102] (3) The retxBSR timer expires, and at least one of the LCHs belonging to the LCG contains UL data. This type of BSR is called a "Regular BSR".

[0103] (4) The periodicBSR timer expires. The BSR in this case is called a "periodicBSR".

[0104] That is, there are regular BSRs (new data arrival or higher priority logical channel arrival), periodic BSRs, and padding BSRs. Periodic BSRs time out, and periodic transmissions are performed. If no authorization is received for an extended period, repeated transmissions can be performed.

[0105] In some embodiments, a Delay Status Report (DSR) is introduced. The basic idea is as follows: the terminal can report a DSR, which carries delay information. For example, if uplink data has not been scheduled for a long time, the remaining time of the data packet may be less than a certain threshold (e.g., a set threshold). The remaining time of the data packet is the time until the packet is dropped, which can be determined based on the PDCP drop timer. The DSR is set to the minimum value of data or untransmitted data in the LCG. Furthermore, the DSR carries data that requires urgent scheduling.

[0106] In some embodiments, a Delay Status Report (DSR) or Delay Status Reporting is used to provide the Service gNB with the delay status of the LCG. This delay status includes the remaining time and the total amount of delay-critical UL data for the LCG, where the remaining time is the minimum remaining value of the PDCP discard timer associated with the Service Data Unit (SDU).

[0107] In some embodiments, the triggering condition for a DSR may be: if the minimum remaining value of the running Packet Data Convergence Protocol discard timers in all Packet Data Convergence Protocol Service Data Units (PDCP SDUs) buffered for the logical channel that have not yet been transmitted in any Media Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in the Data Status Report Media Access Control Control Element (DSR MAC CE) is lower than the remaining time threshold of the logical channel group (LCG); and 1> if the logical channel has no pending Data Status Reports (DSRs): 2> trigger the Data Status Report (DSR) for the logical channel.

[0108] In some embodiments, the format of the DSR report is as follows: Figure 1B As shown; where DSR includes: LCG field, BT field, R field, and Remaining Time and Buffer Size fields. The Remaining Time and Buffer Size fields can also be: Remaining Time field and Buffer Size field. The LCG field includes LCG0 to LCG7; the BT field includes BT1, ..., BTm; the Remaining Time field includes Remaining Time 1, ..., Remaining Time m; the Buffer Size field includes Buffer Size 1, ..., Buffer Size m; m is an integer greater than 0. Figure 1B Oct 1, Oct 2, Oct 3, ... Oct 2m and Oct 2m+1 in the code can all indicate length. Oct is an abbreviation for octal, and each Oct represents 8 bits, or 1 byte.

[0109] The LCG field indicates whether to report the remaining time and cache size fields in the LCG; for example, if the LCG field value is 1, it indicates to report, or if the LCG field value is 0, it indicates not to report.

[0110] Remaining Time Field: Represents the minimum remaining value of the PDCP discard timer. This remaining time field can be 6 bits long; the value 'r' in this field represents the remaining time in the range (r, r+1) milliseconds. In other words, the remaining time field carries the shortest remaining time for the data.

[0111] The BT field indicates which buffer size calculation table to use; for example, a BT field value of 1 indicates the use of the second buffer size calculation table, or a BT field value of 0 indicates the use of the first buffer size calculation table.

[0112] The remaining time, BT, and cache size fields of an LCG are reported in two consecutive octets. These three fields for different LCGs are included in the DSR MAC CE in ascending order according to LCGi; i is an integer. For each LCG, the following three fields are reported: remaining time, BT, and cache size.

[0113] The R domain is reserved space.

[0114] In some embodiments, the DSR needs to be enhanced, meaning that for an LCG, it will carry multiple or at least one set of Remaining Time and Buffer Size fields, thus introducing a second type of DSR to distinguish it from the original first type of DSR. The first type of DSR only carries one set of Remaining Time and Buffer Size fields.

[0115] That is, the DSR has been enhanced to report multiple sets of remaining time and cache size fields of the LCG.

[0116] For DSR, cached (or buffered) data is divided into multiple parts based on multiple reporting time thresholds configured for LCG. For each part where BS>0, DSR indicates the following information: the cache size of the data in each part; and the minimum remaining time corresponding to the cached PDCP SDU in each part.

[0117] It is evident that current BSR and DSR reporting are completely separate, as their triggering conditions differ. One is triggered based on the arrival of high-priority data, while the other is triggered due to the urgency of the data. According to the latest 6G meeting minutes, we will soon study a unified BSR and DSR reporting system. Therefore, the terminal behavior when both conditions are triggered in parallel has not yet been discussed. Thus, it is necessary to consider the handling of concurrent events when multiple triggering conditions are met.

[0118] In some embodiments, the UE can be a terminal, or the terminal can be a UE. Remaining time can be replaced with remaining duration. The cache size field can be a buffer size field; cache can be replaced with buffer, or buffer can be replaced with cache.

[0119] like Figure 2A This is an interactive schematic diagram illustrating an information processing method according to an embodiment of this disclosure. For example... Figure 2A As shown, this disclosure relates to an information processing method for a communication system 100, the method comprising:

[0120] Step S2101: The terminal detects at least two first event triggers. In this embodiment of the disclosure, "at least two" means two or more. For example, the terminal detects two first event triggers. For example, the terminal detects more than two first event triggers.

[0121] Optionally, the terminal detects that at least two first events are triggered in parallel. Here, "at least two first events triggered in parallel" can mean that the triggering of at least two first events occurs in parallel, or that at least two first events are triggered in parallel.

[0122] Optionally, the terminal detects that at least two first events are triggered simultaneously.

[0123] Optionally, the name of the first event is not limited; it may be, for example, a triggering event.

[0124] Optionally, the first event includes at least one of the following: a BSR event, a DSR event. Here, a BSR event can be replaced by a BSR event or a BSR triggering event, etc.; a DSR event can be replaced by a DSR event or a DSR triggering event, etc.

[0125] Optionally, the first event can be extended to an enhanced event of BSR or DSR. For example, the first event could be an event triggered by detecting an increase or change in the buffer size, such as a reporting event. For example, the first event could be named a new BSR event X, etc.

[0126] Optionally, the first event can be extended to an enhanced event of BSR or DSR. For example, the first event could be a report triggered by detecting significant data in the buffer size. For example, the first event could be a newly named BSR trigger event Y.

[0127] Optionally, the first event can also be extended to events beyond the BSR or DSR. For example, the first event could be the detection of other events that need to be reported.

[0128] For example, an event in a BSR can refer to: an event related to a BSR, an event that triggers a BSR, or a triggering event of a BSR, etc.

[0129] For example, an event for a DSR can refer to: an event related to a DSR, an event that triggers a DSR, or a triggering event for a DSR, etc.

[0130] For example, a BSR may include at least one of the following: a regular BSR, a padding BSR, a retransmission BSR, or a periodic BSR.

[0131] For example, a BSR can be an extended BSR, an enhanced BSR, a predictive BSR, or a BSR in a predetermined format, etc.

[0132] For example, a DSR can be an extended DSR, an enhanced DSR, a predictive DSR, or a DSR in a predetermined format, etc.

[0133] For example, BSR events may include at least one of the following: regular BSR events, populate BSR events, retransmit BSR events, and periodic BSR events.

[0134] Optionally, at least two first events may include one of the following: a regular BSR event and a DSR event, a BSR filling event and a DSR event, a retransmission BSR event and a DSR event, or a periodic BSR event and a DSR event. For example, the triggering of at least two first events may be the parallel triggering of regular BSR events and DSR events. Here, the protocol may specify the parallel occurrence of regular BSR and DSR events, thus facilitating understanding the reason for event triggering.

[0135] For example, the triggering of at least two first events can be the parallel triggering of the BSR filling event and the DSR event. Here, when the terminal triggers the DSR, because there are still resources available, the parallel occurrence of the BSR filling and the DSR can be triggered.

[0136] For example, the triggering of at least two first events can be the parallel triggering of the BSR retransmission event and the DSR event. Here, when the terminal triggers the DSR, the BSR retransmission timer expires, thus the parallel occurrence of the BSR retransmission and the DSR can be triggered.

[0137] For example, the triggering of at least two first events can be the parallel triggering of a periodic BSR event and a DSR event. Here, when the terminal triggers the DSR, the periodic trigger timer of the BSR expires, thus allowing the parallel triggering of the periodic BSR and DSR.

[0138] In some embodiments, the protocol can specify which first events can occur concurrently and which first events are not allowed to occur concurrently. Here, concurrent occurrence can be replaced with parallel occurrence.

[0139] Optionally, the protocol can specify which first events are not allowed to occur concurrently. This could involve retaining one higher-priority first event while discarding or canceling the other, or preventing the other first event from triggering at all. This reduces the impact of lower-priority first events on higher-priority first events.

[0140] Optionally, the concurrency of the first event can be: the triggering of the new BSR triggering event X and the triggering of the DSR triggering event occur in parallel.

[0141] Optionally, the first event can be the concurrent triggering of two events: BSR retransmission and DSR reporting. For example, when DSR is triggered, the BSR retransmission timer expires, thus triggering concurrent BSR and DSR retransmissions.

[0142] Optionally, the first event can be the concurrent triggering of two events: the periodic BSR and the DSR reporting. For example, when the DSR is triggered, the periodic trigger timer of the BSR expires, thus triggering the periodic BSR and DSR concurrently.

[0143] Optionally, disallowing concurrency of the first event can prevent the padding BSR and DSR reporting events from occurring in parallel. This could be achieved by specifying in the protocol that the padding BSR is not sent when the DSR is sent; since the padding BSR is not critical and sending it would increase the uplink payload, resulting in poor uplink coverage. In other words, the protocol stipulates that the DSR and padding BSR cannot occur simultaneously.

[0144] Optionally, the concurrency of the first event is not allowed, which means that the retransmission of the BSR and the DSR reporting cannot occur in parallel. For example, the protocol stipulates that the DSR is not sent when the retransmission of the BSR is sent; because the link has deteriorated at this time, it is best not to send the DSR, as it is important information. Therefore, if the timer for the retransmission of the BSR times out, the retransmission of the BSR should not be triggered.

[0145] Optionally, the concurrency of the first event cannot be allowed to trigger periodic BSR and DSR reporting; these two events cannot occur in parallel. This is because periodic BSR is not critical and does not need to be sent; sending it would increase the uplink payload, causing a deterioration in uplink coverage. In other words, the protocol stipulates that DSR and periodic BSR cannot occur simultaneously.

[0146] Step S2102: The terminal performs the first operation.

[0147] In some embodiments, the terminal performing the first operation includes one of the following: determining a second event based on at least two first events; maintaining at least two first events.

[0148] In some embodiments, if the terminal detects at least two first events, it determines a second event based on the at least two first events. Optionally, if the terminal detects at least two first events, it merges the at least two first events into a single second event.

[0149] In some embodiments, the terminal determines a second event when at least two first events include a second type of first event and a third type of first event; wherein the data associated with the second type of first event and the data associated with the third type of first event are not associated.

[0150] Optionally, if the terminal detects at least two first events, these two first events can be merged into a new event (i.e., a second event); for example, data associated with each of the first events can be merged into data associated with the second event. For instance, if the terminal detects an event for important data and an event for urgent data, then the important data and the urgent data can be used as the data for the second event.

[0151] In some embodiments, the terminal determines one of the first events of a first type as the second event, and cancels the other events of the at least two first events except for the first event of the first type.

[0152] Optionally, if the terminal detects two first events, it may retain one first event and / or cancel the other; here, the retained first event is the second event. For example, if the terminal detects that an event to fill the BSR and an event to trigger the DSR are triggered in parallel, it may retain the DSR event triggering and cancel the BSR event triggering. Similarly, if the terminal detects that an event to retransmit the BSR and an event to trigger the DSR are triggered in parallel, it may retain the BSR event triggering and cancel the DSR event triggering.

[0153] In some embodiments, the terminal determines a second event when at least two first events include a second type of first event and a third type of first event, wherein the data associated with the second type of first event and the data associated with the third type of first event are associated.

[0154] Optionally, the existence of a relationship can mean either an inclusion relationship or redundancy. For example, the existence of a relationship between the data associated with the second type of first event and the data associated with the third type of first event can mean either that the data associated with the second type of first event and the data associated with the third type of first event have an inclusion relationship, or that the data associated with the second type of first event and the data associated with the third type of first event are redundant.

[0155] Optionally, the correlation can be that the content of one first event is already reflected in the content reported by another first event. For example, the data associated with BSR and the data associated with DSR have a certain correlation. For instance, if a regular BSR and DSR are detected, but the data reported by DSR already includes the data associated with the regular BSR (because the data associated with DSR MAC CE is urgent data, while the regular BSR is triggered by data with a higher priority, therefore it includes the data with the higher priority, or all the data currently buffered by the terminal. That is, although the classification dimensions of the data associated with the two are different, the data of the two are related, such as the data associated with one being a subset of the data associated with the other. For example, urgent data also includes all data, that is, all the data in the current terminal buffer is urgent), then the triggering of this event (regular BSR) is cancelled.

[0156] Optionally, the two first events detected by the terminal include a second type of first event and a third type of first event. If the data associated with the second type of first event includes the data associated with the third type of first event, the second type of first event is determined to be the second event. For example, if the content (or data) reported by one event is already reflected in the content (or data) reported by another event, such as if regular BSR and DSR are detected, and the data reported by DSR already includes the data reported by regular BSR (e.g., urgent data already includes high-priority data and some low-priority data, i.e., all data is urgent), then reporting can be based on DSR, and / or regular BSR can be canceled.

[0157] In some embodiments, if the terminal detects at least two first events, it maintains at least two first events. Optionally, maintaining at least two first events may mean maintaining at least two independent first events.

[0158] Step S2103: The terminal sends an SR to the network device.

[0159] In some embodiments, the network device receives a scheduling request (SR) sent by the terminal.

[0160] In some embodiments, the terminal sends an SR upon detecting at least two first events.

[0161] In some embodiments, the terminal sends an SR when it needs to use a request SR.

[0162] Optionally, sending an SR by the terminal can mean that the terminal initiates an SR event or an SR.

[0163] Optionally, SR is used to request the resource to send the first message. Here, the resource can be an SR resource.

[0164] Optionally, the SR may include a first SR or a second SR. For example, the terminal sending an SR may include: the terminal sending a first SR; or, the terminal sending at least two second SRs, one second SR corresponding to one first event.

[0165] In some embodiments, the terminal sends a first SR when at least two first events are determined to be a second event. For example, when the terminal detects two first events, it merges the two first events into a second event and sends the first SR. Optionally, even if at least two events are triggered, an SR event is still initiated to reduce conflicts during SR initiation. Alternatively, merging at least two triggering events into a single triggering event also results in only one SR event being initiated, further reducing conflicts during SR initiation.

[0166] Optionally, at least two first events occur in the same entity, and the resource requested by the first SR is the resource of any one of the at least two first events in the entity.

[0167] For example, if a terminal detects that at least two first events are sent to the same entity, and the terminal initiates a first SR, then the resource used (e.g., SR resource) can be any one of the resources (e.g., SR resources) configured for use by the at least two first events within the entity. The selection method can be to arbitrarily choose a resource used by the first event.

[0168] Optionally, at least two first events occur in the same entity, and the resource requested by the first SR is the resource with the highest priority among the at least two first events in the entity.

[0169] For example, if a terminal detects that at least two first events are sent in the same entity and the terminal initiates a first SR, then the resource used (e.g., SR resource) can be the highest priority resource (e.g., SR resource) among the resources (e.g., SR resources) configured to be used for the at least two first events in the entity.

[0170] For example, if LCH1 triggers a regular BSR and DSR, and if SR is required, the terminal initiates a first SR event, using either the resources used by the regular BSR (e.g., SR resources) or the resources used by the DSR (e.g., SR resources).

[0171] Optionally, at least two first events occur in at least two entities, and the resource requested by the first SR is the resource of any one of the first events in any one of the at least two entities.

[0172] For example, if a terminal detects that at least two first events are sent in different entities and the terminal initiates a first SR, then the resource used (e.g., SR resource) can be any one of the resources (e.g., SR resources) configured for use by at least two first events in any of the different entities.

[0173] Optionally, at least two first events occur in at least two entities, and the resource requested by the first SR is: the resource of any one of the first events in the entity with the highest priority among the at least two entities, or the resource with the highest priority of the first event in the entity with the highest priority among the at least two entities.

[0174] For example, if a terminal detects that at least two first events are sent in different entities and the terminal initiates a first SR, the resource used (e.g., SR resource) can be: any one of the resources (e.g., SR resources) configured for use in the entity with the highest priority among the different entities for at least two first events, or the highest priority resource (e.g., SR resource) among the resources (e.g., SR resources) configured for use in the entity with the highest priority among the different entities for at least two first events.

[0175] For example, if LCH1 triggers a regular BSR and LCH2 triggers a DSR, and if SR needs to be used, the terminal initiates a first SR event. The resource (SR) used can be the resource configured to be used by the LCH with the highest priority among LCH1 and LCH2 (e.g., SR resource).

[0176] Optionally, the entity is one of the following: Logical Channel (LCH) or Logical Channel Group (LCG).

[0177] In some embodiments, while maintaining at least two first events, the terminal sends at least two second SRs corresponding to the at least two first events. Here, the terminal sends one second SR for each of the at least two first events.

[0178] In some embodiments, if the terminal requests a resource in any one of the at least two second SRs, it cancels the other two second SRs besides the one that requested the resource.

[0179] For example, if LCH1 triggers a regular BSR and LCH2 triggers a DSR, the terminal initiates a second SR event corresponding to the regular BSR and a second SR event corresponding to the DSR; if any second SR requests a resource (e.g., an SR resource), the terminal uses the requested resource (e.g., the SR) to send the first message and cancels the other second SRs.

[0180] For example, if an authorization is obtained through an SR (e.g., a second SR), the buffer size is assembled into the MAC PDU MAC CE via a "unified report," or the related data is transmitted. Then, all related BSR and DSR triggering events included in the unified report are cleared or canceled. In contrast to the existing independent BSR and DSR reporting mechanism, where grants for both are obtained separately from the network via the SR, BSR-related data can only be reported in the BSR MAC CE. Therefore, BSR cancellation depends on whether the BSR MAC CE is reported. The same applies to DSR. However, with the unified reporting mechanism, even if both BSR and DSR events are triggered, once the SR obtains the authorization and the buffer size is assembled into the MAC PDU MAC CE via a "unified report," or the related data is transmitted, all related BSR and DSR triggering events included in the unified report are cleared or canceled.

[0181] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomously implementing, among other meanings.

[0182] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0183] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "bit", and "data" can be used interchangeably.

[0184] In some embodiments, terms such as "certain", "preset", "specified", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "specified A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, specified A, a certain A, any A, or first A, but are not limited thereto.

[0185] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0186] Step S2104: The terminal sends the first information to the network device.

[0187] In some embodiments, the network device receives first information sent by the terminal.

[0188] Optionally, the first information is used to at least indicate the amount of data associated with the second event. Here, the second event is determined based on at least two first events detected by the terminal.

[0189] Optionally, the first information is used to indicate at least one of the following: at least two first events are triggered; the event types of at least two first events.

[0190] Optionally, the first information is used to indicate the reason for the buffer reporting in the terminal's uniform format. For example, the reason could be that a BSR event and a DSR event are detected in parallel (e.g., at least two first events are triggered).

[0191] Optionally, the name of the first information is not limited, and it may be, for example, cache reporting information or DSR and / or BSR data volume reporting.

[0192] In some alternative embodiments, the terminal sends second information to the network device. Accordingly, the network device receives the second information sent by the terminal.

[0193] Optionally, the second information is used to indicate that at least two first events have been triggered.

[0194] Optionally, the name of the second piece of information is not limited.

[0195] In some embodiments, if at least two first events occur on the same entity, the two first events are combined into a single message reported to the network. For example, the triggering events of the BSR and DSR are reported to the network using a single MAC CE, instead of using separate MAC CEs for each BSR and DSR triggering event. This saves uplink resources.

[0196] In some embodiments, the terminal sends first information based on the resources requested by the first SR. Optionally, if the terminal detects at least two first events, it determines the at least two first events as a second event and sends the first SR; the terminal then sends the first information based on the resources requested by the first SR.

[0197] In some embodiments, the terminal sends first information based on the resources requested by the second SR. Optionally, if the terminal detects at least two first events, it maintains at least two first events and sends at least two second SRs corresponding to the at least two first events; if the terminal requests resources in any one of the at least two second SRs, it sends first information based on the resources requested by the second SR.

[0198] In some embodiments, the terminal sends a MAC CE to the network device, wherein the MAC CE includes first information.

[0199] In some embodiments, the network device receives a MAC CE sent by the terminal, wherein the MAC CE includes first information.

[0200] Optionally, MAC CE includes at least one of the following: a first field, a second field, a third field, a fourth field, a fifth field, a sixth field, and a seventh field.

[0201] For example, the first field is used to indicate an entity.

[0202] For example, the second field is used to indicate the event type.

[0203] For example, the second field is used to indicate at least one of the following: high-priority data or triggering a regular BSR; periodic BSR triggering; detecting delayed critical data or triggering a DSR; detecting burst termination; predicting data volume; detecting other events (e.g., secondary cell beam failure recovery).

[0204] For example, the third field is used to indicate the amount of data.

[0205] For example, the third field is used to indicate at least one of the following: buffer size, buffer size level and its attributes.

[0206] For example, the third field is used to indicate at least one of the following: current buffer size, predicted buffer size, critical buffer size, and delayed critical buffer size.

[0207] For example, the fourth field is used to indicate the remaining time and / or the remaining time level.

[0208] For example, the fifth field is used to indicate the time to the next outbreak and / or the time level to the next outbreak.

[0209] For example, the sixth field is used to indicate the importance level.

[0210] For example, the seventh field is used to indicate the dependency level.

[0211] Optionally, the MAC CE includes a predetermined field; when the predetermined field consists of different bits or code points, it is used to indicate different event triggers. Here, the predetermined field can be the second field mentioned above, the event type field, or any other field.

[0212] For example, when the predefined field is "00", it indicates the amount of data reported in reserved or traditional BSR mode (at this time, only the buffer size field is valid, i.e., only the buffer size exists). When the predefined field is "01", only the buffer status is reported (the buffer size field is valid, the delay field is invalid or filled with zero); for example, for the corresponding regular / periodic BSR. When the predefined field is "10", this is a combined status report (at this time, both the buffer size field and the delay field are valid. The buffer size can report multiple fields at this time. For example, it includes a buffer indicator field, such as 1000 bits, i.e., all data, and another buffer indicator field, such as 100 bits, i.e., urgent data; at this time, for this other buffer indicator field, a delay field is also effective, i.e., indicating the urgency); for example, for simultaneous triggering or network configuration. When the predefined field is "11", the latency status report is enhanced (the cache size field may report a subset, and the latency field is valid. For example, it may include a buffer indicator field, such as 100 bits, which is urgent data. In this case, a latency field is also effective for this buffer indicator field, indicating the urgency level); for example, it corresponds to DSR triggering.

[0213] Optionally, the following is a reporting method for the MAC CE unified format:

[0214] Unified Status Reporting MAC CE:

[0215] All events generate the same type of enhanced MAC CE. Its fields may include:

[0216] LCH / LCG;

[0217] Event type;

[0218] - Detect high-priority data or trigger a regular BSR;

[0219] - Periodic BSR trigger;

[0220] - Detecting delayed critical data or triggering DSR;

[0221] -Detection interruption ended;

[0222] -Predicted data volume;

[0223] - Detect other events (e.g., secondary cell beam failure recovery);

[0224] Note: Multiple events can be reported. The terminal can report multiple triggered events simultaneously. For example, it can detect 1000 bits of all data plus 100 bits of emergency data.

[0225] Buffer size / Buffer size levels and their attributes

[0226] - Current buffer size;

[0227] - The predicted buffer size; for example, the estimated amount of data for the next data burst.

[0228] -Important buffer size;

[0229] - Delay critical buffer size;

[0230] Remaining time / Remaining time level;

[0231] The timeframe until the next emergency / The time level until the next emergency;

[0232] Importance level;

[0233] Dependency level (e.g., which data are highly correlated and require high synchronization; which data are less correlated and only require low synchronization).

[0234] In the above embodiments, based on the "event type" field, the network device can know which triggering event the amount of buffer data reported by the terminal is associated with, that is, obtain the attributes of this data. For example, if the terminal reports a 1000-bit buffer report and informs the network that this is a regular BSR trigger, then the network knows that this buffer size represents either high-priority data from the terminal or all data in the current buffer. If the terminal reports a 100-bit buffer report and informs the network that this is a DSR trigger, then the network knows that this buffer size represents the amount of urgent data detected by the terminal.

[0235] When reporting the size of the buffer area or the buffer size level, the data attributes are also reported, which makes it easier for the base station to know more details about the data cached by the terminal.

[0236] Besides the UE explicitly indicating the triggering event to represent the data attributes, an implicit method can also be used. For example, different code points can be used to indicate whether data was reported under a certain triggering event.

[0237] The information processing method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2104. For example, step S2101 may be implemented as an independent embodiment; step S2102 may be implemented as an independent embodiment; step S2103 may be implemented as an independent embodiment; step S2104 may be implemented as an independent embodiment; a combination of steps S2101 and S2104 may be implemented as an independent embodiment; a combination of steps S2102 and S2103 may be implemented as an independent embodiment; a combination of steps S2101, S2102, and S2104 may be implemented as an independent embodiment; a combination of steps S2101 to S2104 may be implemented as an independent embodiment.

[0238] In some embodiments, steps S2102 and S2103 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0239] In some embodiments, step S2103 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0240] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0241] like Figure 2B This is an interactive schematic diagram illustrating an information processing method according to an embodiment of this disclosure. For example... Figure 2B As shown, this disclosure relates to an information processing method for a communication system 100, the method comprising:

[0242] In step S2201, the terminal detects that at least two first events have been triggered.

[0243] For optional implementations of step S2201, please refer to [link / reference]. Figure 2A Optional implementation methods in step S2101, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0244] In step S2202, the terminal determines a second event based on at least two first events.

[0245] For optional implementations of step S2202, please refer to [link / reference]. Figure 2A Optional implementation methods in step S2102, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0246] In step S2203, the terminal sends a first SR to the network device.

[0247] For optional implementations of step S2203, please refer to [link / reference]. Figure 2A Optional implementation methods in step S2103, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0248] Step S2204: The terminal sends the first information to the network device.

[0249] For optional implementations of step S2204, please refer to [link / reference]. Figure 2A Optional implementation methods in step S2104, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0250] The information processing method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2204. For example, step S2201 may be implemented as an independent embodiment; step S2202 may be implemented as an independent embodiment; step S2203 may be implemented as an independent embodiment; step S2204 may be implemented as an independent embodiment; a combination of steps S2201 and S2204 may be implemented as an independent embodiment; a combination of steps S2202 and S2203 may be implemented as an independent embodiment; a combination of steps S2201, S2202, and S2204 may be implemented as an independent embodiment; a combination of steps S2201 to S2204 may be implemented as an independent embodiment.

[0251] In some embodiments, steps S2202 and S2203 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0252] In some embodiments, step S2203 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0253] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0254] like Figure 2C This is an interactive schematic diagram illustrating an information processing method according to an embodiment of this disclosure. For example... Figure 2C As shown, this disclosure relates to an information processing method for a communication system 100, the method comprising:

[0255] Step S2301: The terminal detects that at least two first events have been triggered.

[0256] For optional implementations of step S2301, please refer to [link / reference]. Figure 2A Optional implementation methods in step S2101, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0257] In step S2302, the terminal maintains at least two first events.

[0258] For optional implementations of step S2302, please refer to [link / reference]. Figure 2A Optional implementation methods in step S2102, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0259] In step S2303, the terminal sends at least two second SRs corresponding to at least two first events to the network device.

[0260] For optional implementations of step S2303, please refer to [link / reference]. Figure 2A Optional implementation methods in step S2103, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0261] Optionally, before sending the first information to the network device, the terminal may further include: determining at least two first events as a second event.

[0262] Step S2304: The terminal sends the first information to the network device.

[0263] For optional implementations of step S2304, please refer to [link / reference]. Figure 2A Optional implementation methods in step S2104, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0264] The information processing method involved in the embodiments of this disclosure may include at least one of steps S2301 to S2304. For example, step S2301 may be implemented as an independent embodiment; step S2302 may be implemented as an independent embodiment; step S2303 may be implemented as an independent embodiment; step S2304 may be implemented as an independent embodiment; a combination of steps S2301 and S2304 may be implemented as an independent embodiment; a combination of steps S2302 and S2303 may be implemented as an independent embodiment; a combination of steps S2301, S2302, and S2304 may be implemented as an independent embodiment; a combination of steps S2301 to S2304 may be implemented as an independent embodiment.

[0265] In some embodiments, steps S2302 and S2303 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0266] In some embodiments, step S2303 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0267] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0268] Figure 3 This is an interactive schematic diagram illustrating an information processing method according to an embodiment of this disclosure. For example... Figure 3 As shown, this disclosure relates to an information processing method for a communication system 100, the method comprising one of the following steps:

[0269] In step S3101, if the terminal detects that at least two first events have been triggered, it sends first information to the network device, wherein the first information is used to at least indicate the amount of data associated with the second event. Optionally, the second event is determined based on at least two first events; the first events are BSR events or DSR events.

[0270] For optional implementations of step S3101, please refer to [link / reference]. Figure 2A Optional implementation methods in step S2103, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0271] In some embodiments, the BSR events include at least one of the following: regular BSR events, filling BSR events, retransmission BSR events, and periodic BSR events; and at least two first events, including one of the following: regular BSR events and DSR events; filling BSR events and DSR events; retransmission BSR events and DSR events; periodic BSR events and DSR events.

[0272] In some embodiments, before the terminal sends the first information, it further includes one of the following: the terminal determines a second event based on at least two first events; the terminal maintains at least two first events.

[0273] In some embodiments, the terminal determines a second event based on at least two first events, including one of the following: the terminal determines one of the first events of a first type as the second event, and cancels other events in the at least two first events except for the first type of first event; the terminal determines the second event when the at least two first events include a second type of first event and a third type of first event, wherein the data associated with the second type of first event and the data associated with the third type of first event are associated, or the data associated with the second type of first event and the data associated with the third type of first event are not associated.

[0274] In some embodiments, the method further includes: the terminal sending an SR to the network device, wherein the SR is used to request resources for sending first information.

[0275] In some embodiments, the terminal sends an SR, including one of the following: sending a first SR when at least two first events are determined to be a second event; or sending at least two second SRs corresponding to the at least two first events while maintaining at least two first events.

[0276] In some embodiments, if at least two first events occur in the same entity, the resource requested by the first SR is: the resource of any one of the at least two first events in the entity; if at least two first events occur in the same entity, the resource requested by the first SR is: the resource with the highest priority among the at least two first events in the entity; if at least two first events occur in at least two entities, the resource requested by the first SR is: the resource of any one of the first events in any one of the at least two entities; if at least two first events occur in at least two entities, the resource requested by the first SR is: the resource of any one of the first events in the entity with the highest priority among the at least two entities, or the resource with the highest priority among the first events in the entity with the highest priority among the at least two entities.

[0277] In some embodiments, the entity is one of the following: a logical channel; a logical channel group.

[0278] In some embodiments, the method further includes: if the terminal requests a resource in any one of the at least two second SRs, canceling the other second SRs besides the one that requested the resource.

[0279] In some embodiments, the first information is also used to indicate at least one of the following: at least two first events are triggered; at least two first event types.

[0280] In some embodiments, the terminal sends first information to the network device, including: the terminal sends a MACCE to the network device, wherein the MACCE includes the first information.

[0281] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0282] In this embodiment of the disclosure, a unified format buffer reporting mechanism is introduced into the communication system (e.g., 6G or other network systems).

[0283] In some embodiments, a scheme for a terminal to process multiple concurrent triggering events is protected.

[0284] Optionally, the triggering event can be triggered by the terminal for at least one of the following: regular BSR, periodic BSR, retransmission BSR, detection of delayed urgent data, and DSR.

[0285] Optionally, the triggering event can also be extended to enhanced events of BSR or DSR. For example, a report can be triggered when an increase or change in the buffer size is detected. For instance, it can be named a new BSR triggering event X.

[0286] Optionally, the triggering event can also be extended to enhanced events of BSR or DSR. For example, a report could be triggered by detecting important data in the buffer size. For instance, a new BSR triggering event could be named Y.

[0287] Optionally, the concurrent triggering of events can be the parallel occurrence of the triggering of at least two of the above events.

[0288] Optionally, the triggering event can also be extended to events beyond BSR or DSR. For example, if other events are detected, they need to be reported. This article uses concurrent events of BSR and DSR as an example.

[0289] Optionally, the protocol can specify which events can occur concurrently and which events are not allowed to occur concurrently.

[0290] Optionally, the protocol can specify which events are not allowed to occur concurrently. This could involve retaining one higher-priority event while discarding or canceling the other's triggering event, or preventing the other event from triggering at all. This reduces the impact of lower-priority events on higher-priority events.

[0291] Optionally, the concurrent triggering of events can be achieved by having both BSR and DSR reporting events occur in parallel.

[0292] Optionally, the concurrent triggering of events can be achieved by the simultaneous occurrence of two events: regular BSR and DSR reporting. This could be a protocol that only allows this type of concurrent scenario, while other concurrent scenarios are not permitted by the protocol; this allows the base station to easily understand the reason for the event triggering.

[0293] Optionally, the concurrent triggering of events can be: the triggering of the new BSR triggering event X and the triggering of the DSR triggering event occur in parallel.

[0294] Optionally, the concurrent triggering of events can allow the triggering of both the BSR filling and DSR reporting events to occur in parallel. For example, when sending a DSR, since resources are still available, concurrent triggering of the BSR filling and DSR reporting events can be initiated.

[0295] Optionally, the concurrent triggering of events can be achieved by triggering both the BSR retransmission and DSR reporting events in parallel. For example, when the DSR is triggered, the BSR retransmission timer may expire, thus enabling concurrent triggering of both the BSR and DSR retransmission events.

[0296] Optionally, the concurrent triggering of events can be achieved by the concurrent triggering of two events: the periodic BSR and the DSR reporting event. For example, when the DSR is triggered, the periodic triggering timer of the BSR happens to expire, thus enabling concurrent triggering of both the periodic BSR and DSR.

[0297] Optionally, disallowing concurrent event triggering can prevent the padding BSR and DSR reporting events from occurring in parallel. This could be achieved by specifying in the protocol that the padding BSR is not sent when the DSR is sent; since the padding BSR is not critical and sending it would increase the uplink payload, leading to poor uplink coverage. In other words, the protocol stipulates that the DSR and padding BSR cannot occur simultaneously.

[0298] Optionally, disallowing concurrent event triggering can prevent the retransmission of the BSR and the DSR reporting from occurring simultaneously. As one implementation, the protocol stipulates that the DSR should not be sent when the retransmission of the BSR is being sent; this is because the link has deteriorated at this point, and it's best not to send the DSR, as it contains important information. Therefore, if the timer for the retransmission of the BSR times out, the retransmission of the BSR should not be triggered.

[0299] Optionally, concurrent event triggering can be prevented for periodic BSR and DSR reporting events, meaning these two events cannot occur in parallel. This is because periodic BSRs are not critical and do not need to be sent; sending them would increase the uplink payload, causing a deterioration in uplink coverage. In other words, the protocol stipulates that DSRs and periodic BSRs cannot occur simultaneously.

[0300] In some embodiments, if concurrent events occur on the same entity (e.g., the same logical channel), the terminal behavior may be at least one of the following:

[0301] (1) Merge into one triggering event or maintain two independent events.

[0302] (2) If information needs to be reported to the network, it should be merged into a single message and reported to the network. For example, the triggering events of BSR and DSR should be reported to the network using a single MAC CE, instead of using separate MAC CEs for each event. This saves uplink resources.

[0303] (3) If an SR (Schedule Request) is required, an SR event is initiated.

[0304] Therefore, even if two events are triggered, only one SR event is initiated, which helps reduce conflicts during the SR initiation process. Alternatively, at least two triggering events can be merged into one triggering event, which also only initiates one SR event, further reducing conflicts during the SR initiation process.

[0305] Optionally, since an SR reporting event is initiated, the SR resource used can be one of the SR resources configured for use in multiple events within this entity (logical channel). The selection method can be arbitrary.

[0306] Optionally, since an SR reporting event is initiated, the SR resource used can be the highest priority SR resource among the SR resources configured for use in multiple events within this entity (logical channel).

[0307] Example 1: If LCH1 triggers both regular BSR and DSR (i.e., simultaneously detecting high-priority data and urgent dispatch data), an event is triggered, which simply reports a MAC CE to the network. If SR is required, an SR reporting event is initiated, and the SR resource used can be the SR resource configured for DSR and / or BSR.

[0308] Here, it can be defined that once a grant is obtained through the SR, and this buffer size is assembled into the MAC PDU MAC CE via a "unified report" or the relevant data is transmitted, all related BSR and DSR triggering events that are included in it are cleared or canceled. Compared to the existing independent reporting mechanism for BSR and DSR, where grants for both are obtained separately from the network through the SR, BSR-related data can only be reported in the BSR MAC CE. Therefore, canceling a BSR depends on whether the BSR MAC CE has been reported. The same applies to DSR. However, with the unified reporting mechanism, even if both BSR and DSR events are triggered, once the SR obtains the grant and this buffer size is assembled into the MAC PDU MAC CE via a "unified report" or the relevant data is transmitted, all related BSR and DSR triggering events that are included in it are cleared or canceled.

[0309] In some embodiments, if concurrent events occur on different entities (e.g., different logical channels), the terminal behavior may be at least one of the following:

[0310] Method 1: (1) Merge into one trigger event. (2) If information needs to be reported to the network, merge into one message and report to the network.

[0311] Optionally, since it is merged into a single triggering event, an SR (Schedule Request) event is initiated if an SR is required.

[0312] Optionally, since an SR reporting event is initiated, the SR resource used can be one of the SR resources configured for use in multiple concurrent events across multiple entities (logical channels). The selection method can be arbitrary.

[0313] Optionally, since an SR reporting event is initiated, the SR resource used can be the SR resource configured for the entity with the highest priority (logical channel) among multiple entities. For example, if multiple LCHs trigger the event, the SR resource configured for the logical channel with the highest priority is used.

[0314] Example 2: If LCH1 triggers a regular BSR and LCH2 triggers a DSR, meaning both high-priority data and urgent dispatch data are detected simultaneously, then an event is triggered, which simply reports one MAC CE to the network. If SR is required, then an SR reporting event is initiated, and the SR resources used can be the SR resources configured for the highest priority logical channel between LCH1 and LCH2.

[0315] Method 2: (1) Maintain independent triggering events (i.e., BSR and DSR triggers can trigger SR separately), but use a unified reporting format when reporting. (2) If information needs to be reported to the network, merge it into one message (MAC CE) and report it to the network.

[0316] Optionally, since they are different triggering events, LCH1 and LCH2 will both use their respective SR configurations to initiate SR requests.

[0317] Optionally, if any SR requests a granted resource that causes this unified MACCE to be reported, then the other SRs are removed from pending status.

[0318] Here, it can be defined that once a grant is obtained through the SR, and this buffer size is assembled into the MAC PDU MAC CE via a "unified report" or the relevant data is transmitted, all related BSR and DSR triggering events that are already included in it are cleared or canceled. Compared to the existing independent reporting mechanism for BSR and DSR, where grants for both are obtained separately from the network through the SR, BSR-related data can only be reported in the BSR MAC CE. Therefore, canceling a BSR depends on whether the BSR MAC CE has been reported. The same applies to DSR. However, with the unified reporting mechanism, even if both BSR and DSR events are triggered, once the SR obtains the grant and this buffer size is assembled into the MAC PDU MAC CE via a "unified report" or the relevant data is transmitted, all related BSR and DSR triggering events that are already included in it are cleared or canceled.

[0319] In some embodiments, the above multiple concurrent events are merged into a single triggering event, which may include one of the following:

[0320] (1) A new event is formed, such as the triggering of a regular BSR+DSR, which can be combined into an event that detects both important data and urgent data. For example, data A is detected as important data, and data B is detected as urgent data. A and B can be different data or the same data with two characteristics.

[0321] The following is an example where the data has two characteristics simultaneously:

[0322] A combined BSR should be triggered if any of the following events occur in the active cell group: for a logical channel belonging to an LCG, when uplink UL data becomes available for a MAC entity and is delay-critical data; and at least one of the following conditions is met: the UL data belongs to a logical channel with a higher priority than any logical channel that contains available UL data belonging to another LCG; or, no logical channel belonging to an LCG contains any available UL data.

[0323] (2) Retain one event, and drop or cancel the triggering of the other. For example, in the BSR+DSR filling trigger, only the DSR trigger event is retained, and the BSR filling is dropped. For example, in the BSR+DSR retransmission trigger, only the BSR retransmission trigger event is retained, and the DSR is dropped.

[0324] (3) If the content reported by one event is already reflected in the content reported by another event, such as the data associated with BSR and the data associated with DSR having a certain correlation. For example, if a regular BSR and DSR are detected, but the data reported by DSR already includes the data associated with the regular BSR (because the data associated with DSR MAC CE is urgent data, while the regular BSR is triggered by data with a higher priority, so it includes data with a higher priority, or all the data currently buffered by the terminal. That is, although the classification dimensions of the data associated with the two are different, the data of the two are related, such as the data associated with one being a subset of the data associated with the other. For example, urgent data also includes all data, that is, all the data in the current terminal buffer is urgent), then the event (regular BSR) is canceled from triggering.

[0325] Here, it can be defined that once a grant is obtained through the SR, and this buffer size is assembled into the MAC PDU MAC CE via a "unified report" or the relevant data is transmitted, all related BSR and DSR triggering events that are already included in it are cleared or canceled. Compared to the existing independent reporting mechanism for BSR and DSR, where grants for both are obtained separately from the network through the SR, BSR-related data can only be reported in the BSR MAC CE. Therefore, canceling a BSR depends on whether the BSR MAC CE has been reported. The same applies to DSR. However, with the unified reporting mechanism, even if both BSR and DSR events are triggered, once the SR obtains the grant and this buffer size is assembled into the MAC PDU MAC CE via a "unified report" or the relevant data is transmitted, all related BSR and DSR triggering events that are already included in it are cleared or canceled.

[0326] In some embodiments, the terminal's report may indicate the occurrence of multiple triggering events.

[0327] In some embodiments, the following is a reporting method for the MAC CE unified format:

[0328] Unified Status Reporting MAC CE:

[0329] All events generate the same type of enhanced MAC CE. Its fields may include:

[0330] LCH / LCG;

[0331] Event type;

[0332] - Detect high-priority data or trigger a regular BSR;

[0333] - Periodic BSR trigger;

[0334] - Detecting delayed critical data or triggering DSR;

[0335] -Detection interruption ended;

[0336] -Predicted data volume;

[0337] - Detect other events (e.g., secondary cell beam failure recovery);

[0338] In this way, network devices can know which triggering event the amount of buffered data reported by the terminal is associated with, i.e., they can obtain the attributes of this data. For example, if the terminal reports a 1000-bit buffered report and informs the network that this is a regular BSR trigger, then the network knows that this buffered amount represents either high-priority data from the terminal or the entire current buffer. If the terminal reports a 100-bit buffered report and informs the network that this is a DSR trigger, then the network device knows that this buffered amount represents the terminal detecting this much urgent data.

[0339] Note: Multiple events can be reported. The terminal can report multiple triggered events simultaneously. For example, it can detect 1000 bits of all data plus 100 bits of emergency data.

[0340] Buffer size / buffer size level and its attributes.

[0341] - Current buffer size;

[0342] - The predicted buffer size; for example, the estimated amount of data for the next data burst.

[0343] -Important buffer size;

[0344] - Delay critical buffer size;

[0345] Remaining time / Remaining time level;

[0346] The timeframe until the next emergency / The time level until the next emergency;

[0347] Importance level;

[0348] Dependency level (e.g., which data are highly correlated and require high synchronization; which data are less correlated and only require low synchronization).

[0349] Therefore, when reporting the size of the buffer area or the buffer size level, the attributes of the data are also reported, so that the base station can know more details about the data cached by the terminal.

[0350] Besides the UE explicitly indicating the triggering event to represent the data attributes, an implicit method can also be used. For example, different code points can be used to indicate whether data was reported under a certain triggering event.

[0351] In some embodiments, when the event type field is "00", it indicates the amount of data reported in reserved or traditional BSR modes (in this case, only the buffer size field is valid, i.e., only the buffer size exists). When the event type field is "01", only the buffer status is reported (the buffer size field is valid, the delay field is invalid or filled with zero); for example, for regular / periodic BSRs. When the event type field is "10", it is a combined status report (in this case, both the buffer size field and the delay field are valid. The buffer size can report multiple fields. For example, it includes a buffer indication field, such as 1000 bits, i.e., all data, and another buffer indication field, such as 100 bits, i.e., urgent data; for this other buffer indication field, a delay field is also effective, i.e., indicating the urgency); for example, for simultaneous triggering or network configuration. When the event type field is "11", the latency status report is enhanced (the buffer size field may report a subset, and the latency field is valid. For example, it may include a buffer indicator field, such as 100 bits, which indicates urgent data. In this case, a latency field is also effective for this buffer indicator field, indicating the urgency level); for example, it corresponds to a DSR trigger.

[0352] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0353] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, or a core network device) in any of the above methods.

[0354] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an Application-Specific Integrated Circuit (ASIC), and the functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0355] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0356] Figure 4A This is a schematic diagram of the structure of the terminal 4100 provided in an embodiment of this disclosure. Figure 4A As shown, terminal 4100 includes at least one of a first sending module 4101 and a first processing module 4102. In some embodiments, the first sending module 4101 is used to send first information. Optionally, the first sending module 4101 is used to perform at least one of the processing steps performed by terminal 4100 in any of the above methods (e.g., steps S2101 and / or S2103 and S2104, but not limited thereto), which will not be described in detail here. In some embodiments, the first processing module 4102 is used to determine DSR. Optionally, the first processing module 4102 is used to perform at least one of the processing steps performed by terminal 4100 in any of the above methods (e.g., steps S2102, but not limited thereto), which will not be described in detail here.

[0357] Figure 4B This is a schematic diagram of the structure of the network device 4200 provided in an embodiment of this disclosure. For example... Figure 4BAs shown, network device 4200 includes a second transceiver module 4201. In some embodiments, the second transceiver module 4201 is used to receive first information. Optionally, the second transceiver module 4201 is used to perform at least one of the sending and / or receiving steps performed by network device 4200 in any of the above methods (e.g., steps S2101 and / or steps S2103 and S2104, but not limited thereto), which will not be elaborated here. In some embodiments, network device 4200 may include a second processing module.

[0358] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver. For example, the first transceiver module described above includes a first transmitting module and / or a first receiving module. For example, the second transceiver module described above includes a second transmitting module and / or a second receiving module.

[0359] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0360] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0361] Figure 5A This is a schematic diagram of the structure of the communication device 5100 proposed in this embodiment. The communication device 5100 can be a network device (e.g., an access network device (e.g., a base station), a core network device), a terminal (e.g., a user equipment), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0362] like Figure 5AAs shown, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0363] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101 and / or steps S2103 and S2104, but not limited thereto), and the processor 5101 performs at least one of other steps (e.g., step S2102). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0364] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.

[0365] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may vary. Figure 5A The limitations. The communication device may be a standalone device or part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0366] Figure 5B This is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to... Figure 5B The diagram shown is a schematic representation of the structure of chip 5200, but it is not limited to this.

[0367] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0368] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0369] In some embodiments, the interface circuit 5202 performs at least one of the communication steps (S2101 and / or steps S2103 and S2104) in the above-described method, such as sending and / or receiving. For example, the interface circuit 5202 performing the communication steps in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., step S2102).

[0370] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0371] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0372] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0373] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. An information processing method, characterized in that, Executed by the terminal, including: If at least two first events are detected, a first message is sent, wherein the first message is used to at least indicate the amount of data associated with the second event; The second event is determined based on the at least two first events; the first event is either a Cache Status Report (BSR) event or a Delay Status Report (DSR) event.

2. The method according to claim 1, characterized in that, The events of the BSR include at least one of the following: events of a regular BSR, events of a filler BSR, events of a retransmission BSR, and events of a periodic BSR. The at least two first events include one of the following: The events of the regular BSR and the events of the DSR; The events that fill the BSR and the events that fill the DSR; The events for retransmitting the BSR and the events for the DSR; The events of the periodic BSR and the events of the DSR.

3. The method according to claim 1 or 2, characterized in that, Before sending the first information, one of the following is also included: Based on the at least two first events, determine one second event; Maintain the at least two first events.

4. The method according to claim 3, characterized in that, The determination of a second event based on the at least two first events includes one of the following: One of the at least two first events of the first type is identified as the second event, and the other events of the at least two first events other than the first event of the first type are cancelled; In the case where the at least two first events include a second type of first event and a third type of first event, the second event is determined, wherein the data associated with the second type of first event and the data associated with the third type of first event are associated, or the data associated with the second type of first event and the data associated with the third type of first event are not associated.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Send a scheduling request SR, wherein the SR is used to request the resource to send the first information.

6. The method according to claim 5, characterized in that, The sending scheduling request (SR) includes one of the following: If the at least two first events are determined to be one second event, a first SR is sent; While maintaining the at least two first events, at least two second SRs corresponding to the at least two first events are sent.

7. The method according to claim 6, characterized in that, The at least two first events occur in the same entity, and the resource requested by the first SR is: the resource of any one of the at least two first events in the entity; The at least two first events occur in the same entity, and the resource requested by the first SR is the resource with the highest priority among the at least two first events in the entity; The at least two first events occur in at least two entities, and the resource requested by the first SR is: the resource of any one of the first events in any one of the at least two entities; The at least two first events occur in at least two entities, and the resource requested by the first SR is: the resource of any one of the first events in the highest priority entity among the at least two entities, or the resource with the highest priority of the first event in the highest priority entity among the at least two entities.

8. The method according to claim 7, characterized in that, The entity is one of the following: Logical Channel (LCH); Logical Channel Group (LCG) 9. The method according to claim 6, characterized in that, The method further includes: If any one of the at least two second SRs requests a resource, cancel the other two second SRs except the one that requested the resource.

10. The method according to any one of claims 1 to 9, characterized in that, The first information is also used to indicate at least one of the following: The at least two first events are triggered; The event type of the at least two first events.

11. The method according to any one of claims 1 to 10, characterized in that, The sending of the first information includes: Send a Media Access Control Unit (MAC CE), wherein the MAC CE includes the first information.

12. An information processing method, characterized in that, Performed by network devices, including: Receive first information, wherein the first information is sent by the terminal upon detecting at least two first events; the first information is used to at least indicate the amount of data associated with the second event; The second event is determined based on the at least two first events; the first event is either a Cache Status Report (BSR) event or a Delay Status Report (DSR) event.

13. The method according to claim 12, characterized in that, The events of the BSR include at least one of the following: events of a regular BSR, events of a filler BSR, events of a retransmission BSR, and events of a periodic BSR. The at least two first events include one of the following: The events of the regular BSR and the events of the DSR; The events that fill the BSR and the events that fill the DSR; The events for retransmitting the BSR and the events for the DSR; The events of the periodic BSR and the events of the DSR.

14. The method according to claim 12 or 13, characterized in that, The method further includes: Receive a scheduling request SR, wherein the SR is used to request the resource to send the first information.

15. The method according to claim 14, characterized in that, The received scheduling request (SR) includes one of the following: Receive a first SR, wherein the first SR is sent by the terminal when it determines that the at least two first events are a second event; Receive at least two second SRs, wherein the at least two second SRs are sent by the terminal while maintaining the at least two first events.

16. The method according to claim 15, characterized in that, The at least two first events occur in the same entity, and the resource requested by the first SR is: the resource of any one of the at least two first events in the entity; The at least two first events occur in the same entity, and the resource requested by the first SR is the resource with the highest priority among the at least two first events in the entity; The at least two first events occur in at least two entities, and the resource requested by the first SR is: the resource of any one of the first events in any one of the at least two entities; The at least two first events occur in at least two entities, and the resource requested by the first SR is: the resource of any one of the first events in the highest priority entity among the at least two entities, or the resource with the highest priority of the first event in the highest priority entity among the at least two entities.

17. The method according to claim 16, characterized in that, The entity is one of the following: Logical Channel (LCH); Logical Channel Group (LCG) 18. The method according to any one of claims 12 to 17, characterized in that, The first information is also used to indicate at least one of the following: The at least two first events are triggered; The event type of the at least two first events.

19. The method according to any one of claims 12 to 18, characterized in that, The receiving of the first information includes: Receive Media Access Control Unit (MAC CE), wherein the MAC CE includes the first information.

20. An information processing method, characterized in that, Performed by a communication system, which includes a terminal and network equipment, the method includes: When the terminal detects that at least two first events have been triggered, it sends first information to the network device, wherein the first information is used to at least indicate the amount of data associated with the second event; The second event is determined based on the at least two first events; the first event is either a Cache Status Report (BSR) event or a Delay Status Report (DSR) event.

21. A communication device, characterized in that, The communication device is used to perform the information processing method according to any one of claims 1 to 11 or claims 12 to 19.

22. A communication system, characterized in that, include: A terminal and a network device; wherein the terminal is configured to implement the information processing method according to any one of claims 1 to 11, and the network device is configured to implement the information processing method according to any one of claims 12 to 19.

23. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the information processing method as described in any one of claims 1 to 11 or claims 12 to 19.

24. A computer program product, comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by a communication device, it implements the information processing method according to any one of claims 1 to 11 or claims 12 to 19.

Images