Delay status reporting method, terminal, and storage medium

Abstract

Embodiments of the present disclosure provide a delay status reporting (DSR) method, a terminal, and a storage medium. The method is executed by the terminal. The method comprises: determining a first entity from a radio resource control (RLC) entity and / or a media access control (MAC) entity associated with a packet data convergence protocol (PDCP) entity, wherein the first entity comprises the RLC entity and / or the MAC entity; and the first entity is used for triggering DSR on the basis of remaining time. The present disclosure can implement a communication mechanism suitable for incorporating the DSR.

Description

Delay status reporting method, terminal and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a delay status reporting method, a terminal, and a storage medium. Background Art

[0002] In the field of communications technology, the network has introduced a Delay Status Reporting (DSR) mechanism to monitor the status of data packets to be transmitted. Terminals use DSR to report data transmission delay information to the network.

[0003] Summary of the Invention

[0004] After the introduction of DSR, how to trigger DSR becomes a question that needs to be considered.

[0005] Embodiments of the present disclosure provide a delay status reporting method, a terminal, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a delay status reporting method is provided, the method being executed by a terminal, the method including:

[0007] Determine a first entity from a radio resource control RLC entity and / or a medium access control MAC entity associated with a packet data convergence protocol PDCP entity;

[0008] The first entity includes: an RLC entity and / or a MAC entity; the first entity is used to trigger a delay status report DSR based on the remaining time.

[0009] According to a second aspect of an embodiment of the present disclosure, a terminal is provided, comprising:

[0010] The processing module is configured to:

[0011] Determine a first entity from a radio resource control RLC entity and / or a medium access control MAC entity associated with a packet data convergence protocol PDCP entity;

[0012] The first entity includes: an RLC entity and / or a MAC entity; the first entity is used to trigger a delay status report DSR based on the remaining time.

[0013] According to a third aspect of an embodiment of the present disclosure, a terminal is provided, wherein the terminal includes:

[0014] memory, including executable instructions;

[0015] one or more processors;

[0016] When the executable instructions are executed by the processor, the communication device executes the communication method provided in the first aspect.

[0017] According to a fourth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the communication method provided by the first aspect.

[0018] The technical solution provided by the embodiments of the present disclosure can implement a communication mechanism that is suitable for introducing DSR.

[0019] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0021] FIG1a is a schematic diagram showing an architecture of a communication system according to an exemplary embodiment;

[0022] FIG2a is a schematic flow chart showing a method for reporting a delay status according to an exemplary embodiment;

[0023] FIG3a is a schematic flow chart showing a method for reporting a delay status according to an exemplary embodiment;

[0024] FIG3 b is a schematic flow chart showing a method for reporting a delay status according to an exemplary embodiment;

[0025] FIG4a is a schematic flow chart showing a method for reporting a delay status according to an exemplary embodiment;

[0026] FIG5a is a schematic flow chart showing a method for reporting a delay status according to an exemplary embodiment;

[0027] FIG6a is a schematic structural diagram of a network device according to an exemplary embodiment;

[0028] FIG6b is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0029] FIG7a is a schematic structural diagram of a UE according to an exemplary embodiment;

[0030] Fig. 7b is a schematic structural diagram of a communication device according to an exemplary embodiment. DETAILED DESCRIPTION

[0031] Embodiments of the present disclosure provide a delay status reporting method, a terminal, and a storage medium.

[0032] In a first aspect, an embodiment of the present disclosure provides a method for reporting a delay status, the method being executed by a terminal, the method including:

[0033] Determine a first entity from a Radio Resource Control RLC entity and / or a Media Access Control MAC entity associated with a Packet Data Convergence Protocol PDCP entity, where the first entity includes: an RLC entity and / or a MAC entity;

[0034] The first entity is used to trigger a delay status report DSR based on the remaining time.

[0035] In the above embodiment, the first entity can be determined from the radio resource control RLC entity and / or the media access control MAC entity associated with the packet data convergence protocol PDCP entity. Compared with the problem of unclear first entity, the DSR mechanism is improved and made more reliable.

[0036] In combination with the embodiments of the first aspect above, in some embodiments, the PDCP entity is associated with a first type of RLC entity and / or a second type of RLC entity; the PDCP-associated MAC entity includes a first type of MAC entity associated with the first type of RLC entity and / or a second type of MAC entity associated with the second type of RLC entity.

[0037] In the above embodiment, the PDCP entity may be associated with different types of RLC entities, and the PDCP entity may be associated with different types of MAC entities.

[0038] In combination with the embodiments of the first aspect above, in some embodiments, determining the first entity from a radio resource control RLC entity and / or a media access control MAC entity associated with a packet data convergence protocol PDCP entity includes one of the following:

[0039] The first entity is determined from RLC entities and / or MAC entities associated with the PDCP entity based on protocol rules or network configuration.

[0040] In the above embodiment, the first entity can be determined from the RLC entity and / or MAC entity associated with the PDCP entity based on protocol rule information or network configuration information, and the determination method is more flexible.

[0041] In combination with the embodiment of the first aspect above, in some embodiments, determining the first entity from the RLC entity and / or MAC entity associated with the PDCP entity based on protocol rule information or network configuration information includes:

[0042] Determine that the PDCP entity sends first information to an RLC entity and / or a MAC entity associated with the PDCP entity, and determine the first entity from the RLC entity and / or the MAC entity associated with the PDCP entity;

[0043] The first information indicates the triggering of BSR and / or the amount of BSR-associated data.

[0044] In the above embodiment, the timing of determining the first entity from the RLC entity and / or MAC entity associated with the PDCP entity based on protocol rule information or network configuration information is clarified, and the determination mechanism is improved.

[0045] In combination with the embodiment of the first aspect above, in some embodiments, the method further includes:

[0046] Based on a protocol rule or a network configuration, the PDCP entity sends second information to the first entity;

[0047] The first entity includes the first type MAC entity and / or the second type MAC entity; the second information is used to indicate the triggering of DSR and / or the amount of DSR-associated data.

[0048] In the above embodiment, the manner in which the PDCP entity sends the second information to the first entity is clarified, and the sending mechanism is improved.

[0049] In combination with the embodiments of the first aspect above, in some embodiments, determining the first entity from the RLC entity and / or MAC entity associated with the PDCP entity includes one of the following:

[0050] Determining PDCP packet duplication as radio bearer RB activation, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type MAC entity and the second type MAC entity;

[0051] Determining that a split secondary radio resource control RLC entity has been configured and the amount of transmitted data is greater than or equal to a quantity threshold, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type MAC entity and the second type MAC entity;

[0052] Determining that a split secondary radio resource control RLC entity has been configured and the amount of transmitted data is less than a quantity threshold, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type of MAC entity;

[0053] Determining that the sending PDCP entity is associated with a DAPS bearer and does not initiate uplink data conversion, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type MAC entity;

[0054] Determining that a sending PDCP entity is associated with a DAPS bearer and has initiated uplink data conversion, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the second-type MAC entity;

[0055] Determining PDCP packet duplication as radio bearer RB activation, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type RLC entity and the second type RLC entity;

[0056] Determining that a split secondary radio resource control RLC entity has been configured and the amount of transmitted data is greater than or equal to a quantity threshold, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type RLC entity and the second type RLC entity;

[0057] Determining that a split secondary radio resource control RLC entity has been configured and that the amount of transmitted data is less than a quantity threshold, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type of RLC entity;

[0058] Determining that the sending PDCP entity is associated with a DAPS bearer and does not initiate uplink data conversion, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type of RLC entity;

[0059] Determine that the sending PDCP entity is associated with the DAPS bearer and has initiated uplink data conversion, and determine the first entity from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the second type RLC entity.

[0060] In the above embodiment, the first entity may be determined in different ways in different scenarios, and the determination method may be more flexible.

[0061] In a second aspect, an embodiment of the present disclosure provides a terminal, the terminal including:

[0062] The processing module is configured to:

[0063] Determine a first entity from a radio resource control RLC entity and / or a medium access control MAC entity associated with a packet data convergence protocol PDCP entity;

[0064] The first entity includes: an RLC entity and / or a MAC entity; the first entity is used to trigger a delay status report DSR based on the remaining time.

[0065] In a third aspect, an embodiment of the present disclosure provides a terminal, the terminal including:

[0066] memory, including executable instructions;

[0067] one or more processors;

[0068] When the executable instructions are executed by the processor, the terminal executes the communication method described in the optional implementation manner of the first aspect.

[0069] In a fourth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, which, when executed on a communication device, enable the communication device to execute the communication method described in the optional implementation manner of the first aspect.

[0070] In a fifth aspect, an embodiment of the present disclosure provides a program product, which, when executed by a communication device, enables the communication device to execute the communication method described in the optional implementation manner of the first aspect.

[0071] In a sixth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the communication method described in the optional implementation manner of the first aspect.

[0072] It is understandable that the above-mentioned terminal, storage medium, program product, and computer program are all used to execute the method provided by the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method and will not be repeated here.

[0073] The embodiments of the present disclosure provide a delay status reporting method, a terminal, and a storage medium. In some embodiments, the terms communication method, information processing method, information transmission method, etc. can be used interchangeably.

[0074] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0075] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0076] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0077] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0078] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0079] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0080] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," or "in one case A, in another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, and C.

[0081] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0082] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0083] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0084] In some embodiments, terms such as "...", "determine...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0085] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "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" can be replaced with each other.

[0086] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0087] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0088] 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", "bandwidth part (BWP)" and the like may be used interchangeably.

[0089] 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 subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0090] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0091] 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, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0092] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

[0094] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0095] FIG1a is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0096] As shown in FIG. 1 a , a communication system 100 includes a terminal 101 and a network device 102 .

[0097] In some embodiments, the network device 102 may be an access network device or a core network device.

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

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

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

[0101] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0102] In some embodiments, the core network device may be a single device including a first network element, or may be a plurality of devices or a group of devices, each including a first network element. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0103] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0104] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1a, or a portion thereof, but are not limited thereto. The entities shown in FIG1a are illustrative only. The communication system may include all or a portion of the entities shown in FIG1a, or may include other entities other than those shown in FIG1a. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0105] The embodiments of the present disclosure 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), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0106] In some embodiments, driven by the increasing demand for speed, latency, high-speed mobility, and energy efficiency, coupled with the increasing diversity and complexity of future services, fifth-generation mobile communication technology (5G) has been introduced. The primary application scenarios for 5G are: enhanced mobile ultra-broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine-type communications (mMTC). eMBB continues to focus on providing users with multimedia content, services, and data, and demand for it is growing rapidly. Furthermore, since eMBB can be deployed in diverse scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary significantly, making a blanket statement impossible. Detailed analysis is required based on specific deployment scenarios. Typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), and traffic safety. mMTC's key features include high connection density, low data volumes, latency-insensitive services, low module costs, and a long service life.

[0107] In multimodal services, data usually consists of multiple quality of service (QoS) flows, and the corresponding business volume is very large. Multimodal service flows need to meet certain latency requirements during transmission, especially some data flows need to arrive at the server for decoding at the same time. The delay of any one of the data flows will cause the joint decoding of multiple data flows to fail. However, network scheduling is dynamic. Therefore, in some cases, even if some data flows belong to low-priority logical channels, if some data packets have not been scheduled for a long time, a buffer status report (BSR) needs to be sent to notify the network as soon as possible. However, according to the relevant mechanism, a BSR can only be sent when high-priority logical channel data arrives, which cannot meet the needs of emergency scheduling. Therefore, it is necessary to consider optimizing emergency scheduling in multimodal services.

[0108] In some embodiments, a Delay Status Report (DSR) is introduced. Specifically, a terminal can report a DSR, which carries information related to data transmission delay. For example, information indicating that the remaining time of an uplink data packet is less than a certain threshold due to long-term unscheduled uplink data. The remaining time of a data packet is the time until the packet is discarded. For example, this remaining time can be determined based on the discard timer of the Packet Data Convergence Protocol (PDCP).

[0109] In some embodiments, threshold-based DSR reporting is supported. For example, a DSR report is triggered when the residual delay of a packet data unit (PDU) or a set of PDUs falls below a network-configured threshold. For example, the threshold can be configured at the granularity of a logical channel group (LCG).

[0110] In some embodiments, the PDCP discard timer for a PDU set supports the instance where the PDUs of the PDU set arrive at different times.

[0111] In some embodiments, the network can configure whether the terminal triggers a delay status report, for example, by setting some thresholds for each LCG.

[0112] In some embodiments, when the terminal triggers reporting of delay information for one LCG, the terminal also reports a buffer status associated with the remaining time.

[0113] In some embodiments, the Delay Status Report (DSR) procedure is used to provide the delay status of uplink (UL) data to the serving base station (gNB). The delay status includes the remaining time for the UL data, which is based on the value of the PDCP discard timer associated with the first symbol of the Physical Uplink Shared Channel (PUSCH) transmission in which the DSR is sent, and the amount of data associated with the reported remaining time.

[0114] In some embodiments, the Radio Resource Control (RRC) controls the DSR operation by configuring the following parameters: remainingTimeThreshold, where remainingTimeThreshold is the threshold of the remaining time of UL data configured to trigger the DSR of the logical channel group (LCG).

[0115] In some embodiments, when the remaining time of a PDU in an LCG (if configured for DSR) becomes shorter than its associated remainingTimeThreshold, the Media Access Control (MAC) entity triggers DSR.

[0116] In some embodiments, if the MAC entity finds that the remaining time of a data packet is less than a threshold, it will trigger a DSR report. For scenarios such as packet duplication and split bearer, because a PDCP entity will be associated with multiple MAC entities, for example, in the packet duplication scenario, because the PDCP entity corresponds to two MAC entities (the MAC entity associated with the primary RLC entity and the MAC entity associated with the secondary RLC entity), then for the primary MAC entity and the secondary MAC entity, which MAC entity triggers the operation is a question that needs to be considered.

[0117] FIG2a is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2a, the present disclosure embodiment relates to a communication method for a communication system 100, the method comprising:

[0118] Step S2101: The terminal determines the first entity.

[0119] In some embodiments, the first entity includes: an RLC entity and / or a MAC entity.

[0120] In some embodiments, the first entity is determined from a Radio Link Control (RLC) entity and / or a Medium Access Control (MAC) entity associated with a Packet Data Convergence Protocol (PDCP) entity.

[0121] In some embodiments, the first entity is configured to trigger a delay status report DSR based on the remaining time.

[0122] In some embodiments, the remaining time is the time until a data packet to be transmitted in the logical channel is discarded.

[0123] In some embodiments, the remaining time is the time until a data packet to be transmitted in the logical channel group is discarded.

[0124] In some embodiments, the remaining time is the time until the set of data packets to be transmitted in the logical channel is discarded.

[0125] In some embodiments, the remaining time is the time until the set of data packets to be transmitted in the logical channel group is discarded.

[0126] In some embodiments, PDCP replication is determined to be radio bearer (RB) activation, and the PDCP entity is associated with a first type of RLC entity and / or a second type of RLC entity; the PDCP-associated MAC entity includes a first type of MAC entity associated with the first type of RLC entity and / or a second type of MAC entity associated with the second type of RLC entity.

[0127] In some embodiments, the first type of RLC entity is a master RLC entity; the second type of RLC entity is an entity other than the master RLC entity activated by PDCP packet copying.

[0128] In some embodiments, a configured split-assisted radio resource control RLC entity is determined, and the PDCP entity is associated with a first type of RLC entity and / or a second type of RLC entity; the PDCP-associated MAC entity includes a first type of MAC entity associated with the first type of RLC entity and / or a second type of MAC entity associated with the second type of RLC entity.

[0129] In some embodiments, the first type of RLC entity is a primary RLC entity; the second type of RLC entity is a secondary RLC entity.

[0130] In some embodiments, it is determined that the sending PDCP entity is associated with a dual-activation protocol stack (DAPS) bearer, and the PDCP entity is associated with a first type of RLC entity and / or a second type of RLC entity; the PDCP-associated MAC entity includes a first type of MAC entity associated with the first type of RLC entity and / or a second type of MAC entity associated with the second type of RLC entity.

[0131] In some embodiments, the first type of MAC entity is a MAC entity associated with a source cell; the second type of MAC entity is a MAC entity associated with a target cell.

[0132] In some embodiments, the first entity is determined from RLC entities and / or MAC entities associated with the PDCP entity based on protocol rule information.

[0133] In some embodiments, the first entity is determined from RLC entities and / or MAC entities associated with the PDCP entity based on network configuration information.

[0134] In some embodiments, based on protocol rule information, it is determined that the PDCP entity sends first information to the RLC entity and / or MAC entity associated with the PDCP entity, and the first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity.

[0135] In some embodiments, based on network configuration information, it is determined that the PDCP entity sends first information to the RLC entity and / or MAC entity associated with the PDCP entity, and the first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity.

[0136] In some embodiments, the first information indicates a triggering buffer status report (BSR) BSR and / or a BSR-associated data volume.

[0137] In some embodiments, the associated data volume is the data volume corresponding to the data packets to be transmitted whose statistical remaining time is less than or equal to a time threshold.

[0138] In some embodiments, based on the protocol rule information, the PDCP entity sends second information to the first entity.

[0139] In some embodiments, based on network configuration information, the PDCP entity sends second information to the first entity.

[0140] In some embodiments, the first entity includes the first type MAC entity and / or the second type MAC entity.

[0141] In some embodiments, the second information is used to indicate triggering of DSR and / or amount of DSR-associated data.

[0142] In some embodiments, based on protocol rule information, the PDCP entity sends third information to the first entity.

[0143] In some embodiments, based on network configuration information, the PDCP entity sends third information to the first entity.

[0144] In some embodiments, the first entity includes the first type RLC entity and / or the second type RLC entity.

[0145] In some embodiments, the third information is used to indicate the triggering of DSR and / or the amount of DSR-associated data.

[0146] In some embodiments, an RLC entity and / or MAC entity associated with the PDCP entity is determined based on protocol rule information.

[0147] In some embodiments, PDCP packet replication is determined as wireless bearer RB activation, and the first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type MAC entity and the second type MAC entity.

[0148] In some embodiments, it is determined that a split-assisted radio resource control RLC entity has been configured and the amount of transmitted data is greater than or equal to a quantity threshold, and the first entity is determined from the RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type MAC entity and the second type MAC entity.

[0149] In some embodiments, it is determined that a split auxiliary radio resource control RLC entity has been configured and the amount of transmitted data is less than a quantity threshold, and the first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type MAC entity.

[0150] In some embodiments, it is determined that the sending PDCP entity is associated with a DAPS bearer and no uplink data conversion is initiated, and the first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type MAC entity.

[0151] In some embodiments, it is determined that the sending PDCP entity is associated with a DAPS bearer and has initiated uplink data conversion, and the first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the second type MAC entity.

[0152] In some embodiments, PDCP packet replication is determined as radio bearer RB activation, and the first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type RLC entity and the second type RLC entity.

[0153] In some embodiments, it is determined that a split auxiliary radio resource control RLC entity has been configured and the amount of transmitted data is greater than or equal to a quantity threshold, and the first entity is determined from the RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type RLC entity and the second type RLC entity.

[0154] In some embodiments, it is determined that a split secondary radio resource control RLC entity has been configured and the amount of transmitted data is less than a quantity threshold, and the first entity is determined from the RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type of RLC entity.

[0155] In some embodiments, it is determined that the sending PDCP entity is associated with a DAPS bearer and no uplink data conversion is initiated, and the first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type RLC entity.

[0156] In some embodiments, it is determined that the sending PDCP entity is associated with a DAPS bearer and has initiated uplink data conversion, and the first entity is determined from the RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the second type RLC entity.

[0157] Step S2102: The terminal triggers DSR.

[0158] In some embodiments, the first entity of the terminal triggers DSR.

[0159] In some embodiments, the first entity of the terminal is an entity determined from a Radio Resource Control RLC entity and / or a Medium Access Control MAC entity associated with a Packet Data Convergence Protocol PDCP entity.

[0160] In some embodiments, the term "information" can be interchangeable with terms such as "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "field", and "data".

[0161] In some embodiments, the term "send" can be interchanged with terms such as "transmit", "report", and "transmit".

[0162] The information indication method involved in the embodiment of the present disclosure may include at least one of step S2101 to step S2102. For example, step S2101 may be implemented as an independent embodiment, and step S2102 may be implemented as an independent embodiment, but is not limited thereto.

[0163] Figure 3a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3a, the embodiment of the present disclosure relates to a communication method, which is executed by a terminal. The method includes:

[0164] Step S3101: Determine the first entity.

[0165] In some embodiments, the optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0166] Step S3102: Trigger DSR.

[0167] In some embodiments, the optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0168] The information indication method involved in the embodiment of the present disclosure may include at least one of step S3101 to step S3102. For example, step S3101 may be implemented as an independent embodiment, and step S3102 may be implemented as an independent embodiment, but is not limited thereto.

[0169] Figure 3b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3b, the embodiment of the present disclosure relates to a communication method, which is executed by a terminal and includes:

[0170] Step S3201: Determine a first entity from a Radio Resource Control RLC entity and / or a Medium Access Control MAC entity associated with a Packet Data Convergence Protocol PDCP entity.

[0171] In some embodiments, the first entity includes: an RLC entity and / or a MAC entity; the first entity is used to trigger a delay status report DSR based on a remaining time; the remaining time is the time from when a data packet to be transmitted in a logical channel is discarded.

[0172] In some embodiments, the optional implementation of step S3201 can refer to the optional implementation of step S2101 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0173] In some embodiments, the PDCP entity is associated with a first type RLC entity and / or a second type RLC entity; the PDCP-associated MAC entity includes a first type MAC entity associated with the first type RLC and / or a second type MAC entity associated with the second type RLC entity.

[0174] In some embodiments, determining the first entity from a Radio Resource Control RLC entity and / or a Medium Access Control MAC entity associated with a Packet Data Convergence Protocol PDCP entity includes:

[0175] The first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity based on protocol rule information or network configuration information.

[0176] In some embodiments, determining the first entity from an RLC entity and / or a MAC entity associated with the PDCP entity based on protocol rule information or network configuration information includes:

[0177] Determine that the PDCP entity sends first information to an RLC entity and / or a MAC entity associated with the PDCP entity, and determine the first entity from the RLC entity and / or the MAC entity associated with the PDCP entity;

[0178] The first information indicates the triggering of BSR and / or the amount of BSR-associated data.

[0179] In some embodiments, the method further comprises:

[0180] Based on protocol rule information or network configuration information, the PDCP entity sends second information to the first entity;

[0181] The first entity includes the first type MAC entity and / or the second type MAC entity; the second information is used to indicate the triggering of DSR and / or the amount of DSR-associated data.

[0182] In some embodiments, the method further comprises:

[0183] Based on the protocol rule information or the network configuration information, the PDCP entity sends third information to the first entity;

[0184] The first entity includes the first type RLC entity and / or the second type RLC entity; the third information is used to indicate the triggering of DSR and / or the amount of DSR-associated data.

[0185] In some embodiments, determining the first entity from an RLC entity and / or a MAC entity associated with the PDCP entity includes one of the following:

[0186] Determining PDCP packet duplication as radio bearer RB activation, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type MAC entity and the second type MAC entity;

[0187] Determining that a split secondary radio resource control RLC entity has been configured and the amount of transmitted data is greater than or equal to a quantity threshold, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type MAC entity and the second type MAC entity;

[0188] Determining that a split secondary radio resource control RLC entity has been configured and the amount of transmitted data is less than a quantity threshold, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type of MAC entity;

[0189] Determining that the sending PDCP entity is associated with a DAPS bearer and does not initiate uplink data conversion, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type MAC entity;

[0190] Determining that a sending PDCP entity is associated with a DAPS bearer and has initiated uplink data conversion, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the second-type MAC entity;

[0191] Determining PDCP packet duplication as radio bearer RB activation, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type RLC entity and the second type RLC entity;

[0192] Determining that a split secondary radio resource control RLC entity has been configured and the amount of transmitted data is greater than or equal to a quantity threshold, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type RLC entity and the second type RLC entity;

[0193] Determining that a split secondary radio resource control RLC entity has been configured and that the amount of transmitted data is less than a quantity threshold, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type of RLC entity;

[0194] Determining that the sending PDCP entity is associated with a DAPS bearer and does not initiate uplink data conversion, and determining the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type of RLC entity;

[0195] Determine that the sending PDCP entity is associated with the DAPS bearer and has initiated uplink data conversion, and determine the first entity from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the second type RLC entity.

[0196] Figure 4a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 4a, the present disclosure embodiment relates to a communication method, which is executed by a network device. The method includes:

[0197] Step S4101: Get DSR information.

[0198] In some embodiments, after executing DSR, the terminal receives DSR information sent by the terminal.

[0199] In some embodiments, the optional implementation of step S4101 can refer to the optional implementation of step S2102 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0200] Figure 5a is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 5a, the embodiment of the present disclosure relates to a communication method, which is used in a communication system 100. The method includes one of the following steps:

[0201] Step S5101: The terminal sends DSR information to the network device.

[0202] The optional implementation of step S5101 can refer to the optional implementation of steps S2101 to S2102 in Figure 2a, and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0203] In some embodiments, the above method may include the methods of the above-mentioned communication system side, terminal side, access network equipment side, core network equipment side, etc., which will not be repeated here.

[0204] In some embodiments, a solution for Delay Status Reporting (DSR) when PDCP is associated with multiple Radio Link Control (RLC) entities is provided.

[0205] In some embodiments, the terminal detects that a specific data packet or a set of data packets exists in a logical channel or a logical channel group, and the remaining time of the data packet is less than a predetermined threshold.

[0206] In some embodiments, since the statistics (or calculation) of the remaining duration of the data packet is performed at the PDCP layer, when PDCP detects that there is a specific data packet or a set of data packets in a logical channel or a logical channel group, and its remaining time is less than a predetermined threshold, it will notify the lower-layer entity. For example, the PDCP entity will notify the MAC entity to execute the DSR triggering or the size of the related data triggered by the DSR; or because some data packets have been sent to the RLC entity, PDCP needs to notify the RLC, execute the DSR triggering through the RLC entity, and then count (determine) the RLC entity through the RLC entity, and then execute the DSR through the MAC.

[0207] Here, PDCP will count the size of relevant data triggered by some DSRs; RLC will also count the size of relevant data triggered by some DSRs; MAC will implement unified DSR reporting settings.

[0208] In some embodiments, PDCP is associated with multiple RLC entities and / or MAC entities, including at least one of the following cases:

[0209] Case A: Packet replication scenario, where PDCP packet replication is activated for the RB. In this case, PDCP is associated with the primary RLC (corresponding to the first-type RLC entity) and MAC entity (the MAC entity associated with the primary RLC entity, corresponding to the first-type MAC entity); the secondary RLC (corresponding to the second-type RLC entity) and MAC entity (the MAC entity associated with an RLC entity other than the primary RLC entity activated for PDCP packet replication, corresponding to the second-type MAC entity).

[0210] Case B: Split bearer scenario, where a split secondary RLC entity is configured. In this case, PDCP is associated with the primary RLC (corresponding to the first type of RLC entity) and the MAC entity (the MAC entity associated with the primary RLC entity, corresponding to the first type of MAC entity); and the secondary RLC (corresponding to the second type of RLC entity) and the MAC entity (the MAC entity associated with the split secondary RLC entity, corresponding to the second type of MAC entity).

[0211] Case C: DAPS scenario, where the sending PDCP entity is associated with the DAPS bearer. In this case, the PDCP is associated with the first RLC (corresponding to the first-type RLC entity) and MAC entity (the MAC entity associated with the source cell, corresponding to the first-type MAC entity); and the second RLC (corresponding to the second-type RLC entity) and MAC entity (the MAC entity associated with the target cell, corresponding to the second-type MAC entity).

[0212] In some embodiments, based on protocol agreement or network configuration, the PDCP layer selects the target RLC entity / MAC entity for DSR reporting trigger or DSR-triggered related data volume, i.e., notifies the target entity of the DSR reporting trigger or DSR-triggered related data volume.

[0213] In some embodiments, for network configuration scenarios, the network notifies PDCP. When PDCP detects that there is a specific data packet or a set of data packets in a logical channel or a logical channel group, and its remaining time is less than a predetermined threshold, it notifies a designated lower-layer entity (target MAC entity and / or target RLC entity), for example, notifying the MAC entity to execute the DSR trigger or the size of the relevant data triggered by the DSR; or notifying the target RLC entity of the DSR trigger, and then the RLC entity counts (determines) the relevant data volume triggered by the DSR, and then executes the DSR through the MAC.

[0214] The designated lower layer entity, i.e., the target entity notifying the DSR reporting trigger or the amount of data related to the DSR trigger, may be a designated first RLC and / or MAC entity or a designated second RLC or MAC entity. Here, the lower layer entity may be a lower layer protocol stack of a protocol stack.

[0215] In some embodiments, the target MAC entity may be both a first type MAC entity and a second type MAC entity.

[0216] In some embodiments, the target RLC entity may be both a first-type RLC entity and a second-type RLC entity.

[0217] In some embodiments, when PDCP indicates DSR triggering and / or DSR-associated data volume to the MAC entity, the PDCP layer selects the MAC entity for DSR reporting based on protocol agreement or network configuration.

[0218] In some embodiments, the DSR-associated data volume is the data volume for which the remaining time of the data packet calculated by the PDCP layer is less than a threshold.

[0219] In some embodiments, the network may configure the PDCP layer to indicate a DSR trigger and / or DSR-associated data amount to the target MAC entity.

[0220] In some embodiments, the target MAC entity may be the first MAC entity or the second MAC entity.

[0221] In some embodiments, the target MAC entity may be both the first MAC entity and the second MAC entity.

[0222] In some embodiments, according to relevant protocols, the PDCP layer indicates a BSR trigger and / or a BSR-associated data amount to a target MAC entity and / or a target RLC entity. The target MAC entity and / or the target RLC entity that sends the indication of the BSR trigger and / or the BSR-associated data amount may also serve as the target MAC entity and / or the target RLC entity that sends the indication of the DSR trigger and / or the DSR-associated data amount.

[0223] In some embodiments, according to relevant protocols, the PDCP layer indicates a BSR trigger and / or BSR-associated data amount to a target MAC entity. The target MAC entity that sends the indication of the BSR trigger and / or BSR-associated data amount can also serve as the target MAC entity that sends the indication of the DSR trigger and / or DSR-associated data amount. At this time, the RLC entity associated with the target MAC entity that indicates the BSR trigger and / or BSR-associated data amount can also serve as the target RLC entity that sends the indication of the DSR trigger and / or DSR-associated data amount.

[0224] In some embodiments, based on relevant protocols, the PDCP layer sends downlink data to a target MAC entity and / or a target RLC entity. The target MAC entity and / or the target RLC entity that sent the downlink data may also serve as the target MAC entity and / or the target RLC entity that sends an indication of a DSR trigger and / or a DSR-associated data amount.

[0225] In some embodiments, in a packet duplication scenario (corresponding to case A above), PDCP will indicate the DSR trigger and / or DSR associated data volume to the target MAC entity; at this time, the target MAC entity is the MAC entity associated with the first RLC (for example, the MAC entity associated with the primary RLC entity) and the MAC entity associated with the second RLC (for example, the MAC entity associated with the RLC entity other than the primary RLC entity activated for PDCP duplication).

[0226] In some embodiments, in a split bearer scenario (corresponding to case B above), if the amount of data to be transmitted is greater than or equal to a threshold (e.g., ul-DataSplitThreshold), the PDCP will indicate the DSR trigger and / or the amount of DSR-associated data to the target MAC entity; at this time, the target MAC entity is the MAC entity associated with the first RLC (e.g., the MAC entity associated with the primary RLC entity) and the MAC entity associated with the second RLC (e.g., the MAC entity associated with the split secondary RLC entity); otherwise, the PDCP will indicate the DSR trigger and / or the amount of DSR-associated data to the target MAC entity; at this time, the target MAC entity is the MAC entity associated with the first RLC (e.g., the MAC entity associated with the primary RLC entity).

[0227] In some embodiments, in the DAPS scenario (corresponding to case C above), if uplink data switching has not been initiated, PDCP will indicate the DSR trigger and / or DSR associated data volume to the target MAC entity; at this time, the target MAC entity is the MAC entity associated with the first RLC (for example, the MAC entity associated with the source cell); if uplink data switching has been initiated, PDCP will indicate the DSR trigger and / or DSR associated data volume to the target MAC entity; at this time, the target MAC entity is the MAC entity associated with the second RLC (for example, the MAC entity associated with the target cell).

[0228] Example 1:

[0229] If the (sending) PDCP entity is associated with at least two RLC entities, then when indicating to the MAC entity for BSR triggering and buffer size calculation, the (sending) PDCP entity also determines the MAC entity as the target MAC entity for notifying the DSR triggering and / or DSR associated data amount, and / or the (sending) PDCP entity also determines the RLC entity associated with the MAC entity as the target RLC entity for notifying the DSR triggering and / or DSR associated data amount.

[0230] Example 2:

[0231] If the transmitting PDCP entity is associated with at least two RLC entities, when indicating to the MAC entity the amount of PDCP data used for BSR triggering and buffer size calculation, and / or DSR triggering and buffer size calculation, the transmitting PDCP entity shall:

[0232] If PDCP duplication is activated for RB:

[0233] In some embodiments, indicating the amount of PDCP data to a MAC entity associated with a primary RLC entity, and indicating to the MAC entity whether a triggering of a DSR is detected and / or the size of the amount of data associated with the DSR triggering and / or the amount of delay-critical PDCP data;

[0234] In some embodiments, indicating to a MAC entity associated with an RLC entity other than a primary RLC entity activated for PDCP duplication an amount of PDCP data excluding PDCP control PDUs, and indicating to the MAC entity whether a triggering of a DSR is detected and / or a size of the amount of data associated with the DSR triggering and / or an amount of delay-critical PDCP data;

[0235] In some embodiments, the triggering of DSR or the size of the data amount related to the DSR triggering is not indicated to the MAC entity associated with the RLC entity disabled (or deactivated) for PDCP duplication, or the PDCP data amount is indicated as 0.

[0236] For RB, for split bearer:

[0237] In some embodiments, if a split secondary RLC entity is configured, if the total amount of data waiting for initial transmission and the amount of PDCP data in the primary RLC entity and the split secondary RLC entity is equal to or greater than ul-DataSplitThreshold:

[0238] Indicating the PDCP data volume to a MAC entity associated with the primary RLC entity and a MAC entity associated with the split secondary RLC entity, and indicating to the MAC entity whether a DSR triggering is detected and / or a size of the data volume associated with the DSR triggering and / or a delay-critical PDCP data volume;

[0239] Indicating a PDCP data volume of 0 to MAC entities associated with RLC entities other than the primary RLC entity and the split secondary RLC entity, or not indicating a DSR trigger and / or a DSR trigger-related data volume size and / or a delay-critical PDCP data volume to a MAC entity associated with an RLC entity deactivated for PDCP duplication;

[0240] Otherwise (if the total amount of data is equal to or greater than ul-DataSplitThreshold is not satisfied):

[0241] In some embodiments, indicating the amount of PDCP data to a MAC entity associated with a primary RLC entity, and indicating to the MAC entity whether a triggering of a DSR is detected and / or the size of the amount of data associated with the DSR triggering and / or the amount of delay-critical PDCP data;

[0242] Otherwise, if the sending PDCP entity is associated with a DAPS bearer:

[0243] If no uplink data exchange is requested:

[0244] In some embodiments, indicating the amount of PDCP data to a MAC entity associated with the source cell, and indicating to the MAC entity whether a triggering of a DSR is detected and / or the size of the amount of data associated with the DSR triggering and / or the amount of delay-critical PDCP data;

[0245] Otherwise (uplink data exchange is requested),

[0246] In some embodiments, indicating to a MAC entity associated with a target cell a PDCP data volume excluding PDCP control PDUs of interspersed ROHC feedback associated with a source cell, and indicating to the MAC entity whether a triggering of a DSR is detected and / or a size of the data volume associated with the DSR triggering and / or a delay-critical PDCP data volume;

[0247] In some embodiments, indicating to a MAC entity associated with a source cell a PDCP data amount of a PDCP control PDU for interspersed robust header compression (ROHC) feedback associated with the source cell;

[0248] Otherwise (i.e. not the above packet replication, split bearer or DAPS scenario),

[0249] In some embodiments, indicating the amount of PDCP data to a MAC entity associated with a primary RLC entity, and indicating to the MAC entity whether a triggering of a DSR is detected and / or the size of the amount of data associated with the DSR triggering and / or the amount of delay-critical PDCP data;

[0250] In some embodiments, the PDCP data volume is indicated as 0 to a MAC entity associated with an RLC entity other than the primary RLC entity, or the triggering of DSR and / or the size of the related data volume triggered by DSR and / or the delay-critical PDCP data volume are not indicated to the MAC entity associated with an RLC entity other than the primary RLC entity.

[0251] Note: In the above embodiment 2, the sending PDCP entity determines the MAC entity as the target MAC entity for notifying the DSR trigger and / or DSR associated data volume (corresponding to the first entity in the present disclosure), and at the same time, the sending PDCP entity also determines the RLC entity associated with the MAC entity as the target RLC entity for notifying the DSR trigger and / or DSR associated data volume (corresponding to the first entity in the present disclosure).

[0252] The embodiments of the present disclosure also provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device or a core network device) in any of the above methods.

[0253] It should be understood that the division of the various units or modules in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0254] In the embodiments of the present disclosure, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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 to implement the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.

[0255] Figure 6a is a schematic diagram of the structure of a network device provided in an embodiment of the present disclosure. As shown in Figure 6a, network device 6100 includes: a transceiver module 6101 and a processing module 6102; the transceiver module 6101 is configured to send and receive information; and the processing module 6102 is configured to perform operations. Optionally, the transceiver module 6101 is used to perform the steps related to information transmission and reception performed by the network device 6100 in any of the above communication methods, which are not further described here. Optionally, the processing module 6102 is used to perform the steps related to information processing performed by the network device in any of the above communication methods, which are not further described here.

[0256] Figure 6b is a schematic diagram of the structure of a terminal provided by an embodiment of the present disclosure. As shown in Figure 6b, terminal 6200 includes: a transceiver module 6201 and a processing module 6202; the transceiver module 6201 is configured to send and receive information; and the processing module 6202 is configured to perform operations. Optionally, transceiver module 6201 is used to perform the steps related to information transmission and reception performed by terminal 6200 in any of the above communication methods, which are not further described here. Optionally, processing module 6202 is used to perform the steps related to information processing performed by the terminal in any of the above communication methods, which are not further described here.

[0257] Figure 7a is a schematic diagram of the structure of a communication device 8100 provided in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device or a core network device), a terminal (e.g., a user device), a chip, a chip system, or a processor that supports a network device in implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal in implementing any of the above information indication methods. Communication device 8100 can be used to implement the information indication method described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0258] As shown in Figure 7a, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 8101 is used to call instructions to enable the communication device 8100 to execute any of the above communication methods.

[0259] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0260] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above method are performed by the transceiver 8103, and the other steps are performed by the processor 8101.

[0261] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0262] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0263] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 7a. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0264] FIG7 b is a schematic diagram of the structure of a chip 8200 provided in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG7 b , but the present disclosure is not limited thereto.

[0265] The chip 8200 includes one or more processors 8201 , and the processor 8201 is used to call instructions so that the chip 8200 executes any of the above communication methods.

[0266] In some embodiments, chip 8200 further includes one or more interface circuits 8202, which are connected to memory 8203. Interface circuit 8202 can be used to receive signals from memory 8203 or other devices, and can be used to send signals to memory 8203 or other devices. For example, interface circuit 8202 can read instructions stored in memory 8203 and send the instructions to processor 8201. Optionally, the terms interface circuit, interface, transceiver pin, and transceiver are interchangeable.

[0267] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0268] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute 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 may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

[0269] The present disclosure further provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above communication methods. Optionally, the program product is a computer program product.

[0270] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above communication methods.

[0271] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0272] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A delay status reporting method, characterized in that: The method is executed by a terminal, and includes: Determine a first entity from a radio resource control RLC entity and / or a media access control MAC entity associated with a packet data convergence protocol PDCP entity; The first entity includes: an RLC entity and / or a MAC entity; the first entity is used to trigger a delay status report DSR based on the remaining time.

2. The method according to claim 1, characterized in that The PDCP entity is associated with a first type of RLC entity and / or a second type of RLC entity; the MAC entity associated with the PDCP includes a first type of MAC entity associated with the first type of RLC and / or a second type of MAC entity associated with the second type of RLC entity.

3. The method according to claim 2, characterized in that The determining of the first entity from a radio resource control RLC entity and / or a media access control MAC entity associated with a packet data convergence protocol PDCP entity comprises: The first entity is determined from the RLC entity and / or MAC entity associated with the PDCP entity based on protocol rule information or network configuration information.

4. The method according to claim 3, characterized in that The determining the first entity from the RLC entity and / or the MAC entity associated with the PDCP entity based on the protocol rule information or the network configuration information includes: Determine that the PDCP entity sends first information to an RLC entity and / or a MAC entity associated with the PDCP entity, and determine the first entity from the RLC entity and / or the MAC entity associated with the PDCP entity; The first information indicates a triggered buffer status report BSR and / or a BSR-associated data volume.

5. The method according to claim 3, characterized in that: The method further comprises: Based on the protocol rule information or the network configuration information, the PDCP entity sends second information to the first entity; The first entity includes the first type MAC entity and / or the second type MAC entity; the second information is used to indicate the amount of triggered DSR and / or DSR associated data.

6. The method according to claim 3, characterized in that The method further comprises: Based on the protocol rule information or the network configuration information, the PDCP entity sends third information to the first entity; The first entity includes the first type of RLC entity and / or the second type of RLC entity; the third information is used to indicate the triggering of DSR and / or the amount of DSR-associated data.

7. The method according to claim 4, characterized in that The determining the first entity from the RLC entity and / or the MAC entity associated with the PDCP entity comprises one of the following: Determine that the PDCP packet duplication is a radio bearer RB activation, and determine the first entity from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type MAC entity and the second type MAC entity; Determine that a split auxiliary radio resource control RLC entity has been configured and the amount of transmitted data is greater than or equal to a quantity threshold, and determine the first entity from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type MAC entity and the second type MAC entity; Determine that a split auxiliary radio resource control RLC entity has been configured and the amount of transmitted data is less than a quantity threshold, and determine the first entity from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type of MAC entity; Determine that the sending PDCP entity is associated with the DAPS bearer and does not initiate uplink data conversion, and determine the first entity from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type of MAC entity; Determine that the sending PDCP entity is associated with the DAPS bearer and has initiated uplink data conversion, and determine the first entity from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the second type MAC entity; Determine that the PDCP packet duplication is a radio bearer RB activation, and determine the first entity from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type of RLC entity and the second type of RLC entity; Determine that a split auxiliary radio resource control RLC entity has been configured and the amount of transmission data is greater than or equal to a quantity threshold, and determine the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type of RLC entity and the second type of RLC entity; Determine that a split auxiliary radio resource control RLC entity has been configured and the amount of transmitted data is less than a quantity threshold, and determine the first entity from RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the first type of RLC entity; Determine that the sending PDCP entity is associated with the DAPS bearer and does not initiate uplink data conversion, and determine the first entity from the RLC entity and / or MAC entity associated with the PDCP entity; wherein the first entity is the first type of RLC entity; Determine that the sending PDCP entity is associated with the DAPS bearer and has initiated uplink data conversion, and determine the first entity from the RLC entities and / or MAC entities associated with the PDCP entity; wherein the first entity is the second type of RLC entity.

8. A terminal, characterized in that: The terminal comprises: The processing module is configured as follows: Determine a first entity from a radio resource control RLC entity and / or a media access control MAC entity associated with a packet data convergence protocol PDCP entity; The first entity includes: an RLC entity and / or a MAC entity; the first entity is used to trigger a delay status report DSR based on the remaining time.

9. A terminal, characterized in that: The terminal comprises: memory, including executable instructions; one or more processors; When the executable instructions are executed by the processor, the terminal executes the method according to any one of claims 1 to 7.

10. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the method according to any one of claims 1 to 7.

Images