Communication method and apparatus

Abstract

The present application relates to the field of communications, and provides a communication method and apparatus. The communication method comprises: a sending end obtaining a first transmission resource corresponding to a service data unit by means of a media access control entity; determining, by means of the media access control entity and on the basis of a time domain resource comprised in the first transmission resource, a first time for generating a protocol data unit, wherein the protocol data unit comprises at least one service data unit; and sending the protocol data unit generated by the media access control entity on the basis of the first time. A first time for generating a protocol data unit to be first transmitted is enabled to be advanced; and because a service data unit used by a protocol data unit packed earlier has a relatively smaller sequence number, a service data unit having a relatively small sequence number is first transmitted, so that a sending window of the sending end can be updated in a timely manner, and transmission of a new service data unit can be started, thereby reducing the transmission delay.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202510207352.2, filed with the State Intellectual Property Office of China on February 24, 2025, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology

[0003] In communication systems, the generation and transmission of protocol data units (PDUs) are crucial for achieving efficient and stable data communication.

[0004] Starting from the network layer at the sender, data is encapsulated into PDUs and then transmitted to the data link layer. At the Packet Data Convergence Protocol (PDCP) sublayer of the data link layer, the PDCP entity performs header compression, encryption, and other operations to generate a PDCP PDU. Next, the PDCP PDU flows to the radio link control (RLC) layer. Here, each PDCP PDU is considered a radio link control service data unit (SDU). The RLC entity adds an RLC header to the RLC SDU, and then, based on transmission resource information from the media access control (MAC) layer, segments some RLC SDUs to ultimately generate an RLC PDU. Subsequently, the RLC PDU enters the MAC layer and is treated as a MAC SDU. The MAC layer, based on transmission resource factors, multiplexes one or more MAC SDUs into a single MAC PDU. Finally, the generated MAC PDU can be sent to the receiver.

[0005] MAC PDU transmission enables end-to-end data delivery. Considering the complex and ever-changing wireless environment, with frequent occurrences of signal fading and interference, each layer has developed processing mechanisms to improve the stability of PDU transmission, such as the RLC retransmission mechanism.

[0006] Currently, the transmission latency of MAC PDUs needs to be reduced. Summary of the Invention

[0007] This application provides a communication method and apparatus for reducing the transmission latency of MAC PDUs.

[0008] To achieve the above objectives, this application adopts the following technical solution:

[0009] Firstly, a communication method is provided, which is applied to a transmitting end. The transmitting end can be a terminal or a network device. The executing entity of the method can be the transmitting end, a component or device applied to the transmitting end (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or part of the transmitting end's functions. The communication method includes: a media access control entity acquiring a first transmission resource corresponding to a service data unit; the media access control entity determining a first time for generating a protocol data unit based on time-domain resources included in the first transmission resource, the protocol data unit including at least one service data unit; and transmitting the protocol data unit generated by the media access control entity based on the first time.

[0010] In the first aspect, the MAC entity of the sending end determines the first time to generate the protocol data unit based on the time domain resources included in the first transmission resource. This allows the first time of generating the protocol data unit to be transmitted earlier to be advanced. Since the sequence number of the service data unit used by the protocol data unit that is packetized first is smaller, the service data unit with the smaller sequence number is transmitted first. This allows the sending window of the sending end to be updated in a timely manner and start the transmission of new service data units, thereby reducing transmission latency.

[0011] In one possible design, the media access control entity determines the first time for generating the protocol data unit based on the time-domain resources included in the first transmission resources, including: the media access control entity determines the first time based on the time-domain resources included in the first transmission resources and a minimum processing time, wherein the minimum processing time is the time between receiving the physical downlink control channel and transmitting the physical uplink shared channel.

[0012] Optionally, the interval between the first time and the time-domain resources included in the first transmission resource is the minimum processing time, and the first time is before the time-domain resources included in the first transmission resource.

[0013] In this design, the sending end can determine the first time by combining the minimum processing time, thereby improving the accuracy of the determined first time.

[0014] In one possible design, at least one service data unit corresponds to the same logical channel priority.

[0015] In this design, at least one service data unit in the protocol data unit corresponds to the same logical channel priority, so that service data units of equal importance can be grouped together in the protocol data unit. This avoids frequent scheduling and packetization operations caused by processing data with different priorities one by one, reduces processing overhead, improves the encapsulation efficiency of data from the logical channel to the transmission channel, and enables data to be ready for transmission more quickly.

[0016] In one possible design, the method may further include: receiving first information indicating that at least one service data unit corresponds to the same logical channel priority.

[0017] In this design, the receiving end can actively instruct the sending end that the logical channel priorities of service data units in the protocol data unit are the same. This means that the network can precisely control the priority strategy of data transmission. The network can flexibly decide which service data units are processed with the same priority based on real-time network conditions, service requirements, and other factors, thereby better managing network resources and ensuring the quality of service for critical services.

[0018] In one possible design, at least one service data unit corresponds to the same logical channel group.

[0019] In this design, at least one service data unit in the protocol data unit corresponds to the same logical channel group. This allows service data units with similar characteristics or requirements to be grouped together in the protocol data unit, reducing the number of packetizations and overhead. For example, voice service data units with high real-time requirements can be grouped together to reduce scheduling delays, enable fast transmission, avoid waiting time caused by mixing data with different requirements, and improve overall transmission efficiency.

[0020] In one possible design, the method further includes receiving second information indicating that at least one service data unit corresponds to the same logical channel group.

[0021] In this design, the receiving end can actively instruct the sending end that the logical channel groups of the service data units in the protocol data units are the same, meaning the network can precisely control the priority strategy of data transmission. The network can flexibly decide which service data units to process simultaneously based on real-time network conditions, service demands, and other factors, thereby better managing network resources and ensuring the quality of service for critical services.

[0022] Secondly, a communication method is provided, which is applied to a receiving end. The receiving end can be a terminal or a network device. The executing entity of the method can be the receiving end, a component or device applied to the receiving end (such as a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the receiving end. The communication method includes: sending a first transmission resource corresponding to a service data unit; and receiving a protocol data unit, wherein the protocol data unit is a protocol data unit generated according to a first time, the first time being a time determined according to the first transmission resource, and the protocol data unit includes at least one service data unit.

[0023] In the second aspect, the MAC entity at the sending end determines the first time to generate the protocol data unit based on the time domain resources included in the first transmission resources. This allows the first time of generating the protocol data unit to be transmitted earlier to be advanced. Since the sequence number of the service data unit used by the protocol data unit that is packetized first is smaller, the service data unit with the smaller sequence number is transmitted first. This allows the sending window of the sending end to be updated in a timely manner and start the transmission of new service data units, thereby reducing transmission latency.

[0024] In one possible design, at least one service data unit corresponds to the same logical channel priority.

[0025] In this design, at least one service data unit in the protocol data unit corresponds to the same logical channel priority, so that service data units of equal importance can be grouped together in the protocol data unit. This avoids frequent scheduling and packetization operations caused by processing data with different priorities one by one, reduces processing overhead, improves the encapsulation efficiency of data from the logical channel to the transmission channel, and enables data to be ready for transmission more quickly.

[0026] In one possible design, the method further includes: sending first information indicating that at least one serving data unit corresponds to the same logical channel priority.

[0027] In this design, the receiving end can actively instruct the sending end that the logical channel priorities of service data units in the protocol data unit are the same. This means that the network can precisely control the priority strategy of data transmission. The network can flexibly decide which service data units are processed with the same priority based on real-time network conditions, service requirements, and other factors, thereby better managing network resources and ensuring the quality of service for critical services.

[0028] In one possible design, at least one service data unit corresponds to the same logical channel group.

[0029] In this design, at least one service data unit in the protocol data unit corresponds to the same logical channel group. This allows service data units with similar characteristics or requirements to be grouped together in the protocol data unit, reducing the number of packetizations and overhead. For example, voice service data units with high real-time requirements can be grouped together to reduce scheduling delays, enable fast transmission, avoid waiting time caused by mixing data with different requirements, and improve overall transmission efficiency.

[0030] In one possible design, the method further includes: sending second information to indicate that at least one service data unit corresponds to the same logical channel group.

[0031] In this design, the receiving end can actively instruct the sending end that the logical channel groups of the service data units in the protocol data units are the same, meaning the network can precisely control the priority strategy of data transmission. The network can flexibly decide which service data units to process simultaneously based on real-time network conditions, service demands, and other factors, thereby better managing network resources and ensuring the quality of service for critical services.

[0032] Thirdly, a communication method is provided, which is applied to a transmitting end. The transmitting end can be a terminal or a network device. The executing entity of the method can be the transmitting end, a component or device applied to the transmitting end (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the transmitting end's functions. The communication method includes: a media access control entity determining that a protocol data unit meets the following first condition: a first difference between the sequence number corresponding to the protocol data unit and the lower bound of the sequence number of the media access control entity's transmission window is less than a first threshold; sending a first request for a first retransmission resource for the protocol data unit; and receiving resource indication information for indicating the first retransmission resource.

[0033] In the third aspect, when the MAC entity of the sending end determines, based on the first condition, that the protocol data unit is a protocol data unit that needs to be retransmitted and is close to the lower boundary of the sending window, it promptly requests the first retransmission resource of the protocol data unit from the receiving end so as to initiate the retransmission of the protocol data unit in a timely manner, so that the protocol data unit can be successfully transmitted as soon as possible, thereby updating the sending window in a timely manner and starting the subsequent transmission of protocol data units, reducing transmission delay.

[0034] In one possible design, before sending the first request, the method further includes: receiving third information at a second time for indicating a second retransmission resource of a protocol data unit; the first condition further includes: a first interval between the second time and a time-domain resource in the second retransmission resource is greater than a second threshold.

[0035] In this design, a new optional first condition is introduced to ensure that when the time-domain resource in the second retransmission resource is later, the sender will send the first retransmission resource for requesting the protocol data unit to the receiver, thus saving transmission resources.

[0036] In one possible design, the first request is also used to indicate the expected retransmission time of the protocol data unit.

[0037] In this design, the sending end indicates the expected retransmission time of the protocol data unit through the first request, which allows the receiving end to accurately understand the sending end's retransmission time requirements.

[0038] In one possible design, the first request includes: the desired retransmission time offset relative to the second time; or, the desired retransmission time offset relative to the time-domain resources in the second retransmission resource.

[0039] This design incorporates multiple possible methods to indicate the desired retransmission time. The sending end can select the most suitable method to indicate the desired retransmission time based on factors such as information availability, resulting in a high degree of system flexibility.

[0040] In one possible design, the first request is carried in the physical uplink control channel, or the first request is carried in the physical uplink shared channel.

[0041] Fourthly, a communication method is provided, which is applied to a receiving end. The receiving end can be a terminal or a network device. The executing entity of the method can be the receiving end, a component or device applied to the receiving end (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the receiving end. The communication method includes: receiving a first request for requesting a first retransmission resource for a protocol data unit; and sending resource indication information for indicating the first retransmission resource.

[0042] In the fourth aspect, when the sending end requests the first retransmission resource of the protocol data unit from the receiving end through the first request, the receiving end is able to The feedback indicates the resource indication information of the first retransmission resource so as to promptly initiate the retransmission of the protocol data unit, enabling the protocol data unit to be transmitted successfully as soon as possible. This allows for timely updating of the sending window and the commencement of subsequent protocol data unit transmissions, thereby reducing transmission latency.

[0043] In one possible design, before receiving the first request, the method further includes: sending third information at a second time to indicate a second retransmission resource of the protocol data unit, wherein the time domain resource of the first retransmission resource is earlier than the time domain resource of the second retransmission resource.

[0044] In this design, the time domain resources of the first retransmission resource are earlier than those of the second retransmission resource, enabling timely initiation of retransmission of protocol data units.

[0045] In one possible design, the first request is also used to indicate the expected retransmission time of the protocol data unit.

[0046] In this design, the sending end indicates the expected retransmission time of the protocol data unit through the first request, which allows the receiving end to accurately understand the sending end's retransmission time requirements.

[0047] In one possible design, the first request includes: the desired retransmission time offset relative to the second time; or, the desired retransmission time offset relative to the time-domain resources in the second retransmission resource.

[0048] This design incorporates multiple possible methods to indicate the desired retransmission time. The sending end can select the most suitable method to indicate the desired retransmission time based on factors such as information availability, resulting in a high degree of system flexibility.

[0049] Fifthly, a communication apparatus is provided for implementing the method described in any one of the first to fourth aspects. For example, the communication apparatus may be a transmitting end as described in the first aspect, or a device included in the transmitting end, such as a chip or chip system. When the device is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0050] The communication device includes modules, units, or means corresponding to the implementation method. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the function.

[0051] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations. The transceiver module, also called a transceiver unit, is used to implement the sending and / or receiving functions in any of the above aspects and any possible implementations. The transceiver module may consist of transceiver circuitry, a transceiver, a transceiver unit, or a communication interface.

[0052] In some possible designs, the transceiver module includes a sending module and / or a receiving module, which are used to implement the sending or receiving functions in any of the above aspects and any possible implementations.

[0053] A sixth aspect provides a communication device, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute computer programs or instructions to cause the communication device to perform the methods described in any aspect. For example, the communication device may be a transmitting end as described in the first aspect, or a device included in the transmitting end, such as a chip or chip system. When the device is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0054] A seventh aspect provides a communication device comprising: at least one processor; said processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the method described in any aspect. The memory may be coupled to the processor, or the memory may exist independently of the processor; for example, the memory and the processor may be two separate modules. The memory may be located outside or within the communication device.

[0055] The communication device is used to implement the method described in any of the first to fourth aspects. For example, the communication device can be a transmitting end as described in the first aspect, or a device included in the transmitting end, such as a chip or chip system. When the device is a chip system, it can be composed of chips or can include chips and other discrete components.

[0056] Eighthly, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in either aspect.

[0057] In a ninth aspect, a computer program product containing instructions is provided that, when run on a communication device, enables the communication device to perform the method described in either aspect.

[0058] In a tenth aspect, a communication device is provided, configured to cause the communication device to perform the method described in any one aspect.

[0059] Eleventhly, a communication system is provided, which includes the transmitting end and receiving end described in the preceding aspects.

[0060] It is understandable that when the communication device provided in any of the fifth to seventh aspects is a chip, the sending action / function of the communication device can be understood as outputting information, and the receiving action / function of the communication device can be understood as inputting information.

[0061] The technical effects of any of the design methods in aspects five through eleven can be found in the technical effects of different design methods in aspects one through four, and will not be repeated here. Attached Figure Description

[0062] Figure 1 illustrates a data transmission process provided in an embodiment of this application.

[0063] Figure 2 is a schematic diagram of a sending window provided in an embodiment of this application;

[0064] Figure 3 is a schematic diagram of a logical channel variable Bj update scenario provided in an embodiment of this application;

[0065] Figures 4-6 are schematic diagrams of resource allocation scenarios for logical channels provided in the embodiments of this application;

[0066] Figure 7 is a schematic diagram of the serial numbering scenario of PDU under different entities provided in the embodiments of this application;

[0067] Figure 8 is a schematic diagram of an SDU segmentation process provided in an embodiment of this application;

[0068] Figure 9 is a schematic diagram of a data conversion scenario provided in an embodiment of this application;

[0069] Figure 10 is a schematic diagram of a PDU packaging scenario provided in an embodiment of this application;

[0070] Figures 11-13 are schematic diagrams of the architecture of the communication system provided in the embodiments of this application;

[0071] Figure 14 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0072] Figures 15 and 16 are schematic diagrams illustrating the time relationship of PDU transmission resources provided in the embodiments of this application;

[0073] Figure 17 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0074] Figure 18 is a schematic diagram of a sending window provided in an embodiment of this application;

[0075] Figure 19 is a schematic diagram of the time relationship of another PDU transmission resource provided in an embodiment of this application;

[0076] Figure 20 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0077] Figure 21 is a schematic diagram of the time relationship of another PDU transmission resource provided in an embodiment of this application;

[0078] Figures 22 and 23 are schematic diagrams of the communication device provided in the embodiments of this application. Detailed Implementation

[0079] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0080] Before introducing the embodiments of this application, some terms involved in the embodiments of this application will be explained.

[0081] 1. SDU:

[0082] In a communication protocol, an SDU is a data unit passed from an upper layer to a lower layer. It contains application data or control information that needs to be processed and transmitted by that layer. Its size and format are usually specified by the upper layer protocol. The lower layer processes the SDU according to its own functions and the requirements of the lower layer, such as segmentation and encryption, and then passes it to the lower layer. Different protocol layers have different SDUs, such as RLC SDU of the radio link control (RLC) layer and MAC SDU of the media access control (MAC) layer.

[0083] 2. PDU:

[0084] A PDU is a data unit with a specific format and function, formed by encapsulating and processing data at each layer of a communication protocol to achieve data transmission and communication. It typically contains protocol control information for the current layer, as well as SDUs or processed SDU fragments from higher layers. The format and content of a PDU are defined by the corresponding protocol. Different protocol layers have different types of PDUs, such as IP datagrams at the network layer and frames at the data link layer. PDUs are transmitted and processed between layers. Each layer performs decapsulation, processing, or recapsulation operations on the PDU according to protocol requirements to ensure correct data transmission and communication within the network.

[0085] 3. In the new radio (NR) standard, there is a retransmission mechanism based on three layers of protocols: Media Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP).

[0086] MAC retransmission: The Hybrid Automatic Repeat Request (HARQ) mechanism at the MAC layer is a commonly used retransmission method. The receiver immediately feeds back to the sender with the result of successful or failed transmission to achieve fast retransmission. However, when the maximum number of MAC retransmissions is reached, HARQ will abandon MAC retransmission. For some data services in ultra-reliable low-latency communication (URLLC) scenarios, the HARQ mechanism cannot meet the requirements. To reduce the HARQ feedback error rate, more feedback signaling is needed. Since HARQ feedback transmission is very frequent, this will cause significant control signaling overhead.

[0087] RLC Retransmission: The Automatic Repeat Request (ARQ) mechanism at the RLC layer complements the MAC layer's retransmission mechanism. Compared to the HARQ mechanism, the RLC layer transmits retransmission feedback status reports at a lower frequency, requiring relatively less overhead to achieve a lower feedback error rate. Therefore, combining the MAC layer's HARQ with the RLC layer's ARQ can meet the data transmission needs of different application scenarios.

[0088] Figure 1 illustrates the data transmission process when HARQ at the MAC layer and ARQ at the RLC layer are combined:

[0089] (1) Sending data: The data is first delivered to the MAC entity of the sender through the RLC entity of the sender.

[0090] (2) HARQ processing: At the MAC layer, data is processed by the HARQ mechanism. The HARQ mechanism operates based on the receiver's real-time feedback of transmission success or failure. If a transmission error occurs, the receiver sends a HARQ retransmission request, and the sender performs another MAC layer retransmission based on the HARQ feedback result; if the receiver's MAC entity considers the transmission correct or exceeds the maximum number of retransmissions, the data undergoes further retransmission processing through the receiver's RLC layer ARQ mechanism.

[0091] (3) ARQ processing: The RLC layer of the receiving end determines whether the data has been received. If no data is received, the RLC entity of the receiving end initiates an ARQ retransmission request. After receiving the ARQ retransmission request, the RLC entity of the sending end retransmits the data.

[0092] In this process, the HARQ mechanism of the MAC layer enables fast retransmission through rapid feedback from the receiver, while the ARQ mechanism of the RLC layer serves as a supplement. The combination of the two can meet the data transmission needs of different application scenarios.

[0093] PDCP retransmission: PDCP layer retransmission is mainly used in scenarios where user equipment (UE) hands over cells across 5G base stations (next generation node B, gNodeB). During the handover process, the relevant configurations and caches of lower-layer protocols such as RLC and MAC layers are cleared, but the PDCP layer is not. Therefore, the PDCP layer retransmission function ensures that data is not lost during the handover.

[0094] 4. The three transmission modes of the RLC layer:

[0095] (1) Transparent mode (TM): In transparent mode, the RLC layer does not make any changes to the data packet and directly passes the data packet to the adjacent layer. In this mode, there are no RLC layer segmentation, header addition / removal, or retransmission operations, corresponding to system messages, paging messages, MSG2-4, etc.

[0096] (2) Unacknowledged mode (UM): In unacknowledged mode, the RLC layer segments the data packets but does not support retransmission. It is suitable for the transmission of voice services (VoNR) or other time-sensitive services based on 5G New Radio.

[0097] (3) Acknowledged Mode (AM): Acknowledged mode is a reliable transmission mode that supports operations such as segmentation, reassembly, and ARQ retransmission. This mode ensures that every data packet transmitted over the air interface is correctly received by the other end, achieving zero packet loss over the air interface. It is suitable for error-sensitive and latency-tolerant non-real-time applications, such as web browsing, file transfer protocol download (FTP) downloads, and signaling transmission.

[0098] 5. ARQ mechanism and transmit / receive window of RLC layer:

[0099] The ARQ mechanism of the RLC layer is supported in Acknowledgment Mode (AM). One RLC entity corresponds to one logical channel. The RLC transmitting entity receives PDCP PDUs from the PDCP entity, and one PDCP PDU corresponds to one RLC SDU. If the transmission opportunity indicated by the MAC layer to the RLC layer cannot carry a complete RLC SDU, an RLC SDU can be segmented into multiple RLC PDUs.

[0100] In the RLC layer transmission process of 5G communication, the RLC sending entity maintains a sending window. The sending window only slides upwards when it receives a successful reception acknowledgment from the peer, signifying that the sending entity has successfully obtained the acknowledgment and confirmed that the previously sent data has been correctly received. Based on this, the sending entity can remove the acknowledged data from the sending window and prepare to send new data, thereby effectively improving the efficiency and reliability of data transmission.

[0101] Meanwhile, the RLC receiving entity also maintains a receiving window. The receiving window only slides upwards when a complete RLC SDU is successfully received. If the RLC receiving entity receives an erroneous RLC PDU, it needs to notify the RLC sending entity to retransmit via a status report. The upward sliding of the receiving window indicates that the receiving entity has successfully received and processed the complete RLC SDU. This allows the receiving entity to update its receiving status promptly, preparing for the reception of new SDUs, and also ensures that data is received and processed in order, effectively avoiding duplicate reception and out-of-order issues.

[0102] The sending window and the receiving window are the same size. This size can be represented by the parameter AM_Window_Size, which determines the amount of data that the sender can send without receiving an acknowledgment.

[0103] For example, the sending window can be as shown in Figure 2. The sending window is maintained by the RLC sending entity, and its main function is to manage data to be sent and data that has been sent but not yet acknowledged. The sending window contains multiple positions identified by sequence numbers (SNs), each SN corresponding to a different RLC PDU. In this example, the SN values ​​involved in the system range from n-5 to n+5, while the SN range covered by the sending window is from n-2 to n+3. The following details the PDU status corresponding to different SN ranges and the operating rules of the sending window:

[0104] When the SN is in the range of n-5 to n-4, the RLC PDU corresponding to the SN in this range indicates that it has been successfully sent to the receiving end and has received an acknowledgment from the receiver. This means that the receiver has accurately received and processed the data, and the sender can consider that the transmission process of this part of the data has been successfully completed.

[0105] When the sender's register (SN) is in the interval n-2 to n, the RLC PDUs corresponding to SNs within this interval have been sent to the receiver, but no acknowledgment has been received. In this case, the sender needs to continuously wait for acknowledgment messages from the receiver to determine whether these PDUs have been correctly received. At this time, the lower bound of the sending window is located at SN = n-2, which defines the starting boundary of the data to be acknowledged in the sending window. Once acknowledgment messages are subsequently received from the receiver for the PDUs corresponding to SNs in the interval n-2 to n, it indicates that these PDUs have been successfully received by the receiver, and the sending window will move upward according to the protocol rules to include new data to be sent.

[0106] When the SN is in the range of n+1 to n+3, the RLC PDU corresponding to the SN in this range has not yet been generated or has been generated but has not yet been sent.

[0107] The receiving window also has similar functions to the sending window. For details, please refer to the relevant technologies.

[0108] 6. Logical Channel Prioritization (LCP):

[0109] Logical Channel Multiplexing (LCP) can rationally schedule data transmission and allocate resources based on the importance and demand of logical channels, thereby optimizing system performance and meeting service requirements. LCP is also known as Logical Channel Multiplexing.

[0110] For example, for services that are sensitive to latency and have high reliability requirements, such as voice calls and video conferencing, these services can be given priority in resource acquisition and transmission to reduce latency and packet loss, ensuring smooth and stable communication; and / or, wireless resources can be rationally allocated according to the service characteristics and data volume of different logical channels to avoid waste, improve system resource utilization efficiency, and support more services and users.

[0111] In some possible implementations, the MAC layer can evaluate and classify logical channels based on service type, quality of service (QoS) requirements, data volume, etc., and assign different priorities, such as high priority for voice service channels and low priority for data download channels. At each transmission opportunity, the logical channels are sorted based on the above priorities, data backlog, last transmission time, and other factors. According to the sorting results, available resources, logical channel bandwidth requirements, transmission formats, etc., resources are allocated to each logical channel in sequence, allowing high-priority channels to transmit first. This flexibly and efficiently utilizes limited wireless resources, provides differentiated services for different services, and improves user experience and overall system performance.

[0112] It is understood that the above LCP process is an exemplary introduction, and other implementation methods are possible based on technological evolution, without limitation.

[0113] Logical channel multiplexing refers to encapsulating or multiplexing multiple logical channel MAC SDUs into a single MAC PDU. The following is an exemplary description of the logical channel multiplexing process at the MAC layer:

[0114] Step S1: Fill the token bucket with water.

[0115] Function: The token bucket filling mechanism is mainly used to control the size of the MAC SDU that can be added each time, achieving effective management of data transmission traffic. Within the token bucket filling mechanism, the variable Bj represents the number of available tokens in the token bucket; in other words, Bj records the remaining number of tokens in the token bucket. Each logical channel can correspond to one Bj.

[0116] As shown in Figure 3, the logical channel variable Bj can be updated before the logical channel prioritization (LCP) procedure. Updating Bj involves possible parameters such as the prioritized bit rate (PBR) and the bucket size duration (BSD). For example, the value of Bj increases by PBR × T, where T represents the time interval between the last increase in Bj and the current operation, and the upper limit of Bj's value is PBR × BSD. The specific timing of increasing Bj depends on the user equipment (UE) implementation; for example, it can be done before the LCP procedure. Furthermore, after obtaining an uplink grant (UL grant), the logical channel's corresponding Bj can be incremented. In this paper, UL grant represents uplink transmission resources.

[0117] Step S2: Select the logical channel.

[0118] Based on the configuration parameters of the logical channels and the information associated with the UL grant, the logical channels that can be selected for multiplexing are determined. During this process, logical channels that match the UL grant are eligible for multiplexing.

[0119] A UL grant indicates resource information available for uplink transmission, such as the location, duration, or available transmit power of a time-frequency resource block. A logical channel matched with a UL grant is one that can satisfy the resource information specified in the UL grant. For example, if a UL grant allocates a specific time interval and frequency bandwidth, and the data volume and transmission rate requirements of a logical channel can be completed within the allocated time-frequency resources, then that logical channel may match the UL grant. If the data volume of a logical channel is too large, exceeding the resource carrying capacity allocated by the UL grant, then it is not a match.

[0120] Step S3: Allocate resources to the logical channel

[0121] The available logical channels can be sorted according to a pre-set priority. The pre-set priority can also be a pre-configured priority.

[0122] For logical channel j, before multiplexing each MAC SDU, the value of Bj must be checked. If Bj > 0, the MAC SDU meets the multiplexing condition and can be multiplexed. For example, as shown in Figure 4, for logical channel j, there are initially three MAC SDUs (SDU 1, SDU 2, SDU 3) and an initial value of Bj. When determining whether to multiplex SDU 1, since Bj > 0, SDU 1 meets the condition and is multiplexed, and after multiplexing, Bj becomes Bj - SDU 1. Next, when determining whether to multiplex SDU 2, since Bj - SDU 1 > 0, SDU 2 also meets the condition and is multiplexed, and Bj becomes Bj - SDU 1 - SDU 2. When determining whether to multiplex SDU 3, since Bj - SDU 1 - SDU 2 < 0, SDU 3 does not meet the condition and cannot be multiplexed.

[0123] Furthermore, if the remaining transmission resources cannot fully accommodate the MAC SDU, indicating insufficient resources, the RLC SDU corresponding to the MAC SDU can be segmented. As shown in Figures 5 and 6, SDU2 in logical channel 3 is segmented.

[0124] Figure 5 illustrates the relationship and processing method between RLC SDU and UL grant. In the scenario shown in Figure 5(a), the RLC SDU is smaller than the UL grant and can be fully included in the transmission resources; in the scenario shown in Figure 5(b), the RLC SDU is larger than the UL grant and needs to be transmitted in segments due to insufficient resources.

[0125] After successfully reusing the MAC SDU, subtract the actual size of the MAC SDU placed into the transmission resources from Bj.

[0126] Figure 6 illustrates the multiplexing relationship between multiple logical channels (Logical Channel 1, Logical Channel 2, and Logical Channel 3) and the UL grant, as well as the transmission of SDUs. In this scenario, multiple SDUs are multiplexed and transmitted through different logical channels. SDU2 in Logical Channel 3 exhibits segmentation. This is because, within the resource allocation range of the UL grant, Logical Channel 3 is the last channel to be multiplexed, and SDU2 is the last SDU in that logical channel. When the available resources of Logical Channel 3 are insufficient to completely transmit SDU2, it is segmented.

[0127] In one example, if the Priority Bit Rate (PBR) of a logical channel is infinite, this means that the number of available tokens Bj in the token bucket corresponding to that logical channel is infinite. In this case, all MAC SDUs corresponding to that logical channel can be directly placed into the transmission resources without comparing or judging Bj.

[0128] 7. Numbering rules for the sequence number (SN) of the SDU of an RLC entity:

[0129] The SDU numbering system is a mechanism established by the RLC entity in the communication protocol stack to ensure the orderly transmission, accurate identification, and reassembly of service data units. While the SDU numbering rules differ across layers, they follow some general principles:

[0130] The RLC entity assigns serial numbers (SNs) to SDUs received in the order they are received. For example, the SDUs received earlier are assigned smaller SNs, and those received later are assigned larger SNs, thus establishing an ordered numbering sequence for easier data management and processing.

[0131] Each SDU is assigned a unique SN number to ensure accurate identification and differentiation during data transmission, avoid number confusion, and guarantee data accuracy and integrity.

[0132] The serial number (SN) has a specific range of values, depending on the protocol and system design, and may be represented by binary numbers of different lengths, such as 8 bits, 16 bits, or 32 bits. When the number reaches the maximum value of the range, it may be reassigned starting from the minimum value, i.e., the number is used cyclically. However, this must be combined with other mechanisms (such as timestamps and window mechanisms) to avoid conflicts with the number of previously transmitted data.

[0133] SN, SDU, and PDU have the following relationship:

[0134] If the SDU is not segmented, one SDU corresponds to one PDU. The SN number of the SDU is directly used as the number of the corresponding PDU. The receiver uses this number to identify and process the SDU data carried by the PDU.

[0135] When an SDU is segmented, multiple segments may be encapsulated into different PDUs. However, all segments belonging to the same SDU have the same SN number in their respective PDUs, which makes it easy for the receiver to correctly combine the segments based on the same number and restore the complete SDU.

[0136] As shown in Figure 7, the PDUs and their corresponding SN numbers under three RLC entities (Entity 1, Entity 2, and Entity 3) are displayed. Each cell represents a PDU, where SN represents the serial number.

[0137] Entity 1: The SN numbers of the PDUs from bottom to top are 0, 1, 2, 3, and 4. In addition to the SN number, an SG is also marked. For example, two PDUs with SN=2 have SGs of 1 and 2 respectively. This indicates that the corresponding SDUs are segmented, with segments of the same SDU encapsulated in different PDUs. They share the same SN number and are further distinguished by the SG. The receiver can combine these segments based on the shared SN number to reconstruct the complete SDU. Without segmentation, each SDU corresponds to one PDU, and the SN number directly serves as the PDU number. The receiver uses this number to identify and process the SDU data carried by the PDU.

[0138] Entity 2: Some PDUs, in addition to having a serial number (SN), also have an SG (SG designation). For example, there are two PDUs with SN=3, and their SGs are 1 and 2 respectively.

[0139] Entity 3: The SN numbers of PDUs from bottom to top are 0, 1, 2, 3, 4, and 5. Similarly, there may be cases where the SDU is not segmented or is segmented. If it is not segmented, the SN number is directly used as the PDU number; if it is segmented, the SN numbers of the segments of the same SDU are the same in different PDUs, which makes it easier for the receiver to restore the data.

[0140] When numbering SNs at the RLC layer, the RLC entity assigns SNs to RLC SDUs in the order they are received. All RLC PDUs of each RLC SDU share the same SN, and different segments are further distinguished using a segment index (SG) to achieve reliable data transmission and reassembly.

[0141] 8. Detailed process of RLC segmentation:

[0142] At the RLC entity-based granularity, MAC determines transmission opportunities, and RLC segments the data, as follows:

[0143] Step S0: Each RLC entity receives a PDU from a PDCP entity. Each PDCP entity may correspond to one or more logical channels, and each RLC entity corresponds to one logical channel (LC: logical channel). Each PDCP PDU corresponds to one RLC SDU, each RLC SDU corresponds to one logical channel, and multiple RLC SDUs exist within a single logical channel. As shown in Figure 8, the SDU segmentation process may include:

[0144] The RLC entity first acquires the RLC SDU and pre-generates a header, then places it into the logical channel. Next, the MAC entity acquires transmission resources, determines the size of the RLC SDU that can be transmitted within the logical channel during logical channel multiplexing, and notifies the RLC entity of this information. Based on this, the RLC entity determines whether the RLC SDU needs to be segmented. If no segmentation is needed, one RLC PDU corresponds to one RLC SDU. If segmentation is needed, one RLC SDU will contain multiple segments, and one RLC PDU corresponds to one RLC SDU segment. Then, the RLC entity updates the RLC header of the segmented PDU and submits the RLC PDU to the MAC entity. Finally, the MAC entity receives the RLC PDU, adds the MAC layer header, and generates a MAC PDU. This process demonstrates the cooperation between the two layers in data transmission processing to ensure that data is effectively transmitted by adapting to transmission resources.

[0145] It should be noted that in retransmission scenarios, if there is a mismatch between the resource size and the size of the retransmitted data, a further segmentation operation can be performed, and the SN number remains unchanged at this time.

[0146] For example, Figure 9 illustrates a data conversion scenario. More specifically, this scenario demonstrates the data processing flow from the PDCP (Packet Data Convergence Protocol) layer to the MAC (Media Access Control) layer, as well as the relationships between entities at each layer and logical channels and data units, as detailed below:

[0147] The PDCP layer contains three PDCP entities (PDCP Entity1, PDCP Entity2, and PDCP Entity3). Each PDCP entity corresponds to one or more logical channels (LCs), such as PDCP Entity1 corresponding to LC1, PDCP Entity2 corresponding to LC2, and PDCP Entity3 corresponding to LC3 and LC4. Each logical channel has a corresponding PDCP PDU (Packet Convergence Protocol Data Unit).

[0148] In the RLC layer, there are four RLC entities (RLC Entity1, RLC Entity2, RLC Entity3, and RLC entity4). Each RLC entity corresponds to a logical channel; for example, RLC Entity1 corresponds to LC1, RLC Entity2 to LC2, RLC Entity3 to LC3, and RLC entity4 to LC4. Each PDCP PDU corresponds to an RLC SDU (Radio Link Control Service Data Unit). In Figure 9, each RLC SDU under a logical channel has an initial sequence number (SN=1). Some RLC SDUs do not need to be segmented, such as the RLC SDUs in LC1, LC3, and LC4, which directly correspond to one RLC PDU. However, the RLC SDU in LC2 needs to be segmented into two segments, SG1 and SG2, with each segment corresponding to one RLC PDU.

[0149] In the MAC layer, the RLC PDU is received from the RLC layer and treated as a MAC SDU (Media Access Control Service Data Unit). The MAC layer processes these MAC SDUs, adding MAC header information, etc., to generate MAC PDUs and assigns them HARQ numbers, such as MAC PDU HARQ#1, MAC PDU HARQ#2, and MAC PDU HARQ#3, for subsequent data transmission and retransmission control operations.

[0150] 9. MAC entity:

[0151] The MAC entity is a crucial management module at the MAC layer, possessing multiple functions, described below: It maps logical channels to transport channels; multiplexes MAC SDUs from one or more logical channels for transmission to the physical layer via the transport channel, while demultiplexing MAC SDUs from data transmitted from the physical layer via the transport channel to one or more logical channels; it reports scheduling information, providing feedback to the network with scheduling-related information; it performs error correction using a hybrid automatic repeat request mechanism to improve data transmission reliability; it prioritizes logical channels and handles the priority of overlapping resources among individual user equipment to avoid resource conflicts; furthermore, it selects radio resources based on channel conditions and service requirements to improve resource utilization and transmission quality.

[0152] As described in the background section, when the MAC layer performs multiplexing and packet assembly, it can begin packet assembly as soon as it receives the newly transmitted UL grant (uplink grant), and there is no strict time limit for packet assembly. During the packet assembly process, the SN (Sequence Number) of the MAC SDU (Media Access Control Service Data Unit) within the MAC PDU (Media Access Control Protocol Data Unit) is determined. However, this can lead to a situation where the SN number of the MAC SDU assembled earlier is smaller, but because its corresponding UL grant is later in the time domain, the MAC SDU with the smaller SN number may be sent later.

[0153] Taking Figure 10 as an example, assume that the MAC layer assembles three packets in chronological order: MAC PDU1, MAC PDU2, and MAC PDU3, and that these three packets all correspond to the same logical channel MAC SDU. MAC PDU1 contains the MAC SDU with SN=1 and the first segment of the MAC SDU with SN=2; MAC PDU2 contains the second segment of the MAC SDU with SN=2 and the MAC SDU with SN=3; and MAC PDU3 contains the MAC SDU with SN=4. However, the chronological order of the UL resources corresponding to MAC PDU1, MAC PDU2, and MAC PDU3 is MAC PDU3, MAC PDU2, MAC PDU1. That is, the packet assembled earlier (such as MAC PDU1) has a smaller SN number but is sent later, thus increasing the latency.

[0154] Furthermore, the channel state corresponding to the transmission resources of each MAC PDU is different, which means that the number of retransmissions required may also differ. As a result, a MAC SDU with a smaller SN number may be received later than a MAC SDU with a larger SN number.

[0155] In the ARQ mechanism, both the sending and receiving windows are updated in ascending order of the serial number (SN). Even if a MAC SDU with a larger SN is received first, the sending and receiving windows cannot be updated before the MAC SDU with the smaller SN is received, preventing the timely initiation of subsequent MAC SDU transmissions and thus increasing MAC SDU transmission latency.

[0156] To address the aforementioned technical problems, this application provides a communication method. The method provided in this application is described below with reference to the accompanying drawings.

[0157] The communication method provided in this application can be applied to various communication systems, such as Long Term Evolution (LTE) systems, 5G mobile communication systems, Wireless Fidelity (WiFi) systems, future communication systems, or systems integrating multiple communication systems. This application does not limit the application to these systems. 5G can also be referred to as NR.

[0158] The communication method provided in this application can be applied to various communication scenarios, such as one or more of the following communication scenarios: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), machine type communication (MTC), massive machine type communications (mMTC), device to device (D2D), vehicle to everything (V2X), vehicle to vehicle (V2V), and Internet of Things (IoT).

[0159] To facilitate understanding of the embodiments of this application, the application scenario used in this application will be described using the communication system architecture shown in Figure 11 as an example. Figure 11 is a schematic diagram illustrating a possible, non-limiting system. As shown in Figure 11, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 11, collectively referred to as 110) and at least one terminal (120a-120j in Figure 11, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 11). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is connected to core network 200 wirelessly or via wired connection. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device that integrates core network logical functions and radio access network logical functions.

[0160] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0161] RAN node 110, sometimes also referred to as access network equipment, network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 11 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 11 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0162] In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 11, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node can also be configured with program instructions for performing corresponding communication functions, as well as corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node's functions.

[0163] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0164] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0165] In this embodiment, the form of the RAN node is not limited. The device used to implement the function of the RAN node can be the RAN node itself; or it can be a device that supports the RAN node in implementing this function, such as a chip system. The device can be installed in the RAN node or used in conjunction with the RAN node.

[0166] A terminal can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, transportation vehicles with wireless communication capabilities, communication modules, etc. The embodiments of this application do not limit the device form of the terminal. A terminal typically contains a communication module, circuit, or chip that performs the corresponding communication function. The terminal can also be configured with program instructions for performing the corresponding communication function.

[0167] The embodiments of this application do not limit the device form of the terminal. The device used to implement the functions of the terminal can be the terminal itself; it can also be a device that supports the terminal in implementing the functions, such as a chip system. The device can be installed in the terminal or used in conjunction with the terminal. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices. All or part of the functions of the terminal in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0168] In one embodiment, AI nodes may also be introduced into the wireless network to support artificial intelligence (AI) technology.

[0169] AI nodes can be deployed in one of the following locations within the communication system: access network nodes (RAN nodes), terminal devices, or core network devices. Alternatively, AI nodes can be deployed independently, for example, in a location other than any of the aforementioned devices, such as in the host or cloud server of an over-the-top (OTT) system. AI nodes can communicate with other devices in the communication system, which can be, for example, one of the following: network devices, terminal devices, or core network elements.

[0170] It is understood that this application does not limit the number of AI nodes. For example, when there are multiple AI nodes, they can be divided based on function, such as different AI nodes being responsible for different functions.

[0171] It can also be understood that AI nodes can be independent devices, or they can be integrated into the same device to achieve different functions. Alternatively, they can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). This application does not limit the specific form of the aforementioned AI nodes.

[0172] AI nodes can be AI network elements or AI modules.

[0173] The preceding text has introduced the communication system applicable to the embodiments of this application from a macro-architectural perspective. To help deepen the understanding of this system in a practical application environment, the following will provide a more specific explanation of the communication system through several examples. It should be noted that the communication system examples listed below are for illustrative purposes and are intended to provide an intuitive understanding. The actual application scope of this application is far greater than this, and it is also compatible and adaptable to other types of communication systems, and is not limited thereto.

[0174] For example, Figure 12 is a schematic diagram of a possible application framework in a communication system. As shown in Figure 12, network elements in the communication system are connected through interfaces (e.g., NG, Xn) or air interfaces. These network element nodes, such as core network equipment, access network nodes (RAN nodes), terminals, or one or more devices in operations administration and maintenance (OAM), are equipped with one or more AI modules (only one is shown in Figure 12 for clarity). The access network node can be a single RAN node or can include multiple RAN nodes, for example, including CU and DU. The CU and / or DU can also be equipped with one or more AI modules. The CU can also be split into CU-CP and CU-UP, and one or more AI modules are installed in the CU-CP and / or CU-UP.

[0175] AI modules are used to implement corresponding AI functions. AI modules deployed in different network elements can be the same or different. The models of AI modules can achieve different functions depending on the parameter configurations. The models of AI modules can be configured based on one or more of the following parameters: structural parameters (e.g., at least one of the following: number of neural network layers, neural network width, inter-layer connections, neuron weights, neuron activation function, or biases in the activation function), input parameters (e.g., the type and / or dimension of the input parameters), or output parameters (e.g., the type and / or dimension of the output parameters). The biases in the activation function can also be referred to as the biases of the neural network.

[0176] In another example, Figure 13 illustrates a different possible application framework in a communication system. As shown in Figure 13, the communication system includes a RAN intelligent controller (RIC). For example, the RIC can be the aforementioned AI module, used to implement AI-related functions. RICs include near-real-time RICs (near-RT RICs) and non-real-time RICs (non-RT RICs). Non-real-time RICs primarily process non-real-time information, such as data that is not sensitive to latency, with latency in the order of seconds. Real-time RICs primarily process near-real-time information, such as data that is relatively sensitive to latency, with latency in the order of tens of milliseconds.

[0177] Near real-time (NRT) RICs are used for model training and inference. For example, they are used to train AI models and then use those models for inference. NRT RICs can obtain network-side and / or terminal-side information from RAN nodes (e.g., CUs, CU-CPs, CU-UPs, DUs, and / or RUs) and / or terminals. This information can be used as training data or inference data. NRT RICs can deliver inference results to RAN nodes and / or terminals. Inference results can be exchanged between CUs and DUs, and / or between DUs and RUs. For example, a NRT RIC delivers an inference result to a DU, which then forwards it to an RU.

[0178] Non-real-time RICs are also used for model training and inference. For example, they are used to train AI models and then use those models for inference. Non-real-time RICs can obtain network-side and / or terminal-side information from RAN nodes (e.g., CUs, CU-CPs, CU-UPs, DUs, and / or RUs) and / or terminals. This information can be used as training data or inference data, and the inference results can be delivered to RAN nodes and / or terminals. Inference results can be exchanged between CUs and DUs, and / or between DUs and RUs; for example, a non-real-time RIC delivers inference results to a DU, which then forwards them to an RU.

[0179] Near real-time RICs and non-real-time RICs can also be configured as separate network elements. Near real-time RICs and non-real-time RICs can also be part of other devices. For example, near real-time RICs can be set in RAN nodes (e.g., CU, DU), while non-real-time RICs can be set in OAM, cloud servers, core network devices, or other network devices.

[0180] In conjunction with the above-described communication system, this application provides a communication method in which the MAC entity of the sending end determines the first time for generating protocol data units based on the time-domain resources included in the first transmission resources. This allows the first time for generating protocol data units that will be transmitted earlier to be advanced. Since the sequence number of the service data unit used by the protocol data unit that is packetized first is smaller, the service data unit with the smaller sequence number is transmitted first. This enables the sending window of the sending end to be updated in a timely manner and start the transmission of new service data units, thereby reducing transmission latency.

[0181] It should be noted that "sending information" in this application can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "network device sending information" can be understood as a network device sending information to another device (such as a terminal), or it can be understood as logical module 1 in the network device sending information to logical module 2 in the network device.

[0182] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "network device receiving information" can be understood as a network device receiving information from another device (such as a terminal), or it can be understood as logical module 1 in the network device receiving information from logical module 2 in the network device.

[0183] In this application, phrases such as "sending information to... (e.g., a terminal)" or related illustrations in the accompanying drawings can be understood as indicating that the destination of the information is a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a terminal)," "receiving information from... (e.g., a terminal)," or "receiving information sent by (e.g., a terminal)," or related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0184] In the following embodiments of this application, the message names between network elements, the names of parameters, or the names of information are just examples. Other names may be used in other embodiments, and the communication method provided in this application does not specifically limit them.

[0185] It is understood that in the embodiments of this application, each network element may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also execute other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessary to execute all the operations in the embodiments of this application.

[0186] It is understood that this application uses terminal devices and network devices as examples to illustrate the execution of the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the terminal device in this application can also be executed by a module applied to the terminal device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that can implement all or part of the functions of the terminal device; the method executed by the terminal in this application can also be implemented by the communication / processing module in the terminal or the circuit or chip in the terminal responsible for communication / processing functions (such as a modem chip (also known as a baseband chip), or a SoC chip / SIP chip containing a modem core, or a GPU / AI processor / ASIC).

[0187] The methods executed by the network device in this application can also be executed by a module (e.g., a chip, chip system, or processor) applied to the network device, or by a logical node, logical module, or software that can implement all or part of the functions of the network device. The embodiments of this application do not specifically limit this.

[0188] Figure 14 shows a flowchart of the communication method provided in an embodiment of this application. In this communication method, the sending end can be a terminal or a network device in the above-mentioned communication system. The above communication method will be described below with the sending end being a terminal and the receiving end being a network device as an example. For the scenario where the sending end is a network device and the receiving end is a terminal, please refer to the following text. As shown in Figure 14, the method may include the following steps:

[0189] S110, the terminal's MAC entity acquires the first transmission resource corresponding to the service data unit.

[0190] Here, the MAC entity refers to the MAC entity of the terminal (sender). The first transmission resource corresponding to the service data unit refers to the first transmission resource used to transmit the service data unit. When the MAC entity acquires the first transmission resource, it determines which service data units can be carried or transmitted by the first transmission resource according to the logical channel multiplexing process. Which service data units have not yet been allocated transmission resources are identified; these service data units without allocated transmission resources correspond to the first transmission resource.

[0191] The first transmission resource may include time-domain resources and frequency-domain resources. If the sending end is a terminal, the aforementioned first transmission resource may be a transmission resource indicated to the terminal by the network device. For example, the first transmission resource may be a UL grant indicated to the terminal by the network device. Each UL grant indicated by the network device may correspond to one or more service data units, that is, it is used to transmit or carry one or more service data units. The UL grant indicates in which time and frequency domains the terminal performs uplink data transmission. The specific content of the UL grant can be found in the description of related technologies.

[0192] For example, a UL grant can be carried in signaling such as downlink control information (DCI) or medium access control-control element (MAC CE). For instance, after a network device indicates a UL grant to a terminal device via DCI, the terminal device's physical layer obtains the UL grant and then submits it to the terminal device's MAC layer. The terminal device's MAC entity can then acquire the first transmission resource.

[0193] S120, the terminal's MAC entity determines the first time to generate the protocol data unit based on the time domain resources included in the first transmission resources.

[0194] The protocol data unit includes at least one service data unit.

[0195] The time-domain resources included in the first transmission resource indicate the time at which the terminal transmits data. Taking the first transmission resource as a UL grant as an example, the time-domain resources included in the first transmission are determined by the K2 value in the UL grant. The K2 value is indicated by the downlink control information carrying the UL grant. The K2 value represents the interval between the time when the downlink control information carrying the UL grant is transmitted and the time when the physical uplink shared channel is scheduled, in units of slots. This interval is the timing relationship between uplink data scheduling and data transmission, that is, the time from when the terminal receives the DCI (downlink control information) corresponding to the UL grant to the time when it starts transmitting data on the physical uplink shared channel indicated by the UL grant.

[0196] In other words, the time TPDU for the terminal to transmit data (e.g., the PDU in step S130 below) on the Physical Uplink Shared Channel is equal to K2 + the time TUL grant for the terminal to receive the UL grant. The first time can be the aforementioned TPDU. If the UL grant is carried on the DCI, the time of receiving the DCI can be considered as the time of receiving the UL grant. The UL grant can also be determined in other ways, such as through pre-configuration, where the network device pre-configures the first transmission resource corresponding to the UL grant to the terminal device. The first transmission resource also includes frequency domain resources, which can be indicated by the downlink control information carrying the UL grant or determined through pre-configuration.

[0197] In one possible interpretation, the time in the embodiments of this application (e.g., first time, second time, etc.) can also be referred to as moment.

[0198] The first transmission resource acquired by the MAC entity may include multiple UL grants sent at different times. Alternatively, the MAC entity may acquire multiple first transmission resources, each corresponding to one UL grant. For example, as shown in Figure 15, assume two first transmission resources correspond to UL grant1 and UL grant2, respectively. The K2 values ​​corresponding to UL grant1 and UL grant2 are K2-1 and K2-2, respectively. The reception time of the DCI corresponding to UL grant1 is T1, and the reception time of the DCI corresponding to UL grant2 is T2, where T2 is later than T1. That is, the MAC entity acquires UL grant1 first, then UL grant2. However, time-domain resource 1 corresponding to UL grant1 may be later than time-domain resource 2 corresponding to UL grant1. Since UL grant1 is acquired first, when assembling PDUs, PDU1 corresponding to UL grant1 is assembled first, followed by PDU2 corresponding to UL grant2. In other words, the time for generating PDU1 is earlier than the time for generating PDU2.

[0199] Understandably, a DCI can direct one or more UL grants without limitation.

[0200] As mentioned earlier, in the traditional method of generating SDU SNs when assembling PDUs (referred to as Method 1), the SN of the packaged product is ranked first. For example, in this case, PDU1 corresponding to UL grant1 includes SDUs with SN=1, SN=2, and SN=3. Then, after obtaining UL grant2, PDU2 corresponding to UL grant2 includes SDUs with SN=4, SN=5, and SN=6.

[0201] The SN determined based on step S120 of this application (referred to as method two) is determined based on the time-domain resources included in the first transmission resource. When determining the SN, the order in which PDUs are sent is considered. Since time-domain resource 1 corresponding to UL grant1 is later than time-domain resource 2 corresponding to UL grant2, PDU2 corresponding to UL grant2 is first packaged, including SDUs with SN=1, SN=2, and SN=3. Then, PDU1 corresponding to UL grant1 is packaged, including SDUs with SN=4, SN=5, and SN=6. That is, the time of generating PDU1 is later than the time of generating PDU2.

[0202] It is understandable that the above example uses two PDUs as an example to illustrate the communication method principle of this application. Depending on the specific implementation, there may be more PDUs, and there is no limitation.

[0203] One protocol data unit may correspond to one or more transport blocks, and this invention does not impose specific limitations.

[0204] One possible interpretation, based on the comparison of the two examples above, shows that the service data unit (and the SN of the service data unit) used when assembling the protocol data unit also changes due to the change in the protocol data unit generation time. That is, in the embodiments of this application, step S130 can also be interpreted as: the MAC entity of the terminal device determines the service data unit corresponding to the protocol data unit according to the time domain resources included in the first transmission resources, or the MAC entity of the terminal device determines the service data unit corresponding to the protocol data unit according to the time domain resources included in the first transmission resources, and determines the sequence number of the service data unit.

[0205] S130, the terminal device sends a protocol data unit generated in the first moment to the network device, and the network device receives the protocol data unit from the terminal.

[0206] Once the terminal determines the first time, the MAC entity can generate a protocol data unit based on the first time, and then the terminal can send the protocol data unit based on the first transmission resource.

[0207] For example, continuing with the example of step S120 above, in mode one, when sending PDU, PDU2 is sent first and then PDU1 is sent. In this case, SDUs with SN=4, SN=5 and SN=6 arrive at the network device first, and SDUs with SN=1, SN=2 and SN=3 arrive at the network device later. At this time, the delayed arrival of SDUs with SN=1, SN=2 and SN=3 will cause a delay in updating the sending window, resulting in an increase in transmission delay.

[0208] In the second method of this application, when sending PDU, PDU2 is sent first and then PDU1, so that the SDU of the smaller SN arrives at the network device first, reducing transmission delay.

[0209] In this embodiment, the MAC entity of the terminal determines the first time to generate the protocol data unit based on the time domain resources included in the first transmission resources. This allows the first time of generating the protocol data unit to be transmitted earlier to be advanced. Since the sequence number of the service data unit used by the protocol data unit that is packetized first is smaller, the service data unit with the smaller sequence number is transmitted first. This enables the terminal's sending window to be updated in a timely manner and start the transmission of new service data units, thereby reducing transmission latency.

[0210] In one embodiment, S120 (the MAC entity of the terminal determines the first time for generating the protocol data unit based on the time-domain resources included in the first transmission resources) may further include:

[0211] The terminal's MAC entity determines the first time based on the time-domain resources included in the first transmission resources and the minimum processing time.

[0212] The minimum processing time is the time between receiving the physical downlink control channel and transmitting the physical uplink shared channel as configured in the protocol. The minimum processing time covers the entire process of receiving the signal, processing the signal, and generating the response. As shown in Figure 16, this will be explained in conjunction with the relevant information of UL grant1 in the example of Figure 15. The time-domain resource T included in the first transmission resource... PDU Reduce the minimum processing time T forward. p And the determined time T L This is close to the actual time it takes to generate a PDU. Therefore, it can be based on T. L Determine the immediate time. For example, T can be... L This is directly defined as the first time. In other words, the first time and the first transmission resources include the time-domain resources (T). PDU The interval between T and T is the minimum processing time, which can be expressed as: T L =T PDU -T p .

[0213] Of course, considering the minor differences and special needs that may exist in various practical application scenarios, it is also possible to choose T. L Based on this, minor adjustments are made to obtain a "first-time" result that better reflects the current situation, without any restrictions.

[0214] In this embodiment of the application, the terminal can determine the first time by combining the minimum processing time, thereby improving the accuracy of the determined first time.

[0215] In one embodiment, at least one service data unit in the protocol data unit corresponds to the same logical channel priority.

[0216] As described earlier in the MAC layer logical channel multiplexing process, the logical channel priority is the "pre-set priority" mentioned earlier. For details on setting logical channel priorities, please refer to relevant technical specifications. For example, logical channel priorities are determined by multiple factors. From a service type perspective, voice calls have extremely high real-time requirements, and video streams require stable bandwidth; both have higher priority than data download services. In terms of service quality, services with high latency and bandwidth requirements and low error rate requirements, such as autonomous driving and high-definition live streaming data transmission, have higher logical channel priority.

[0217] It is understood that, in one embodiment, there may be no restriction on the service data unit when assembling PDUs, that is, SDUs from all logical channels can be packaged.

[0218] In this embodiment, at least one service data unit in the protocol data unit corresponds to the same logical channel priority, so that service data units of equal importance can be grouped together in the protocol data unit. This avoids frequent scheduling and packetization operations caused by processing data with different priorities one by one, reduces processing overhead, improves the encapsulation efficiency of data from the logical channel to the transmission channel, and enables data to be ready for transmission more quickly.

[0219] The service data units in the aforementioned protocol data units correspond to the same logical channel priority, which can be indicated to the terminal by the network device. That is, in one embodiment, the method may further include:

[0220] S140, the network device sends the first information to the terminal, and the corresponding terminal receives the first information from the network device.

[0221] The first information is used to indicate that at least one service data unit in the protocol data unit corresponds to the same logical channel priority.

[0222] The content of the first information can be flexibly configured. For example, the first information can be index information pre-defined by the network device and the terminal, which corresponds to "at least one service data unit in the protocol data unit corresponds to the same logical channel priority." For example, the index information can be 1. Once the network device sends "1" to the terminal, the terminal can clearly understand that "at least one service data unit in the protocol data unit corresponds to the same logical channel priority." This can effectively reduce channel occupancy, improve the overall efficiency of data transmission, and enable more service data to be transmitted simultaneously.

[0223] Alternatively, the first piece of information can be directly stated as "at least one serving data unit in the protocol data unit corresponds to the same logical channel priority." The terminal does not need to interpret the index, avoiding misunderstandings caused by incorrect or ambiguous index correspondences. This ensures that the terminal accurately receives instructions from the network device, thereby precisely executing the corresponding data processing operations and guaranteeing the accuracy of data transmission and processing.

[0224] Optionally, the first information may also indicate the effective time of the above-mentioned protocol data unit packetization method. This ensures that the terminal assembles PDUs according to the above packetization method within the effective time.

[0225] In this embodiment, the network device can proactively instruct that the logical channel priorities of service data units in the terminal protocol data unit are the same, meaning that the network can precisely control the priority strategy of data transmission. The network can flexibly decide which service data units are processed with the same priority based on real-time network conditions, service requirements, and other factors, thereby better managing network resources and ensuring the quality of service for critical services.

[0226] In one embodiment, at least one service data unit in the protocol data unit corresponds to the same logical channel group.

[0227] In the MAC layer logical channel multiplexing process, logical channel groups are collections of logical channels with similar characteristics or requirements. These characteristics include service type, quality of service requirements, etc. For example, logical channels related to voice calls with high real-time requirements are grouped together, while logical channels related to video streaming with high bandwidth requirements are grouped together. By dividing logical channel groups, the network can manage and allocate resources more efficiently and adopt targeted scheduling strategies for different groups. For example, prioritizing the real-time performance of voice groups and allocating appropriate bandwidth to video groups helps improve overall system performance and quality of service.

[0228] In this embodiment, at least one service data unit in the protocol data unit corresponds to the same logical channel group, enabling service data units with similar characteristics or requirements to be grouped together in the protocol data unit, reducing the number of packetizations and overhead. For example, voice service data units with high real-time requirements can be grouped together to reduce scheduling delays, enable fast transmission, avoid waiting time caused by mixing data with different requirements, and improve overall transmission efficiency.

[0229] The service data units in the aforementioned protocol data units correspond to the same logical channel priority, which can be indicated to the terminal by the network device. That is, in one embodiment, the method further includes:

[0230] S150, the network device sends the second information to the terminal, and the corresponding terminal receives the second information from the network device.

[0231] The second information is used to indicate that at least one service data unit in the protocol data unit corresponds to the same logical channel group.

[0232] The content of the second information can be flexibly configured. For example, the second information can include the identifier (ID) of the logical channel group. Based on the identifier of the logical channel group, the terminal can clearly and accurately distinguish different logical channel groups, quickly and accurately identifying the logical channel group of the packet.

[0233] For example, the second information could be index information pre-defined by the network device and the terminal, which corresponds to "at least one service data unit in the protocol data unit corresponds to the same logical channel group." For instance, this index information could be 0. Once the network device sends "0" to the terminal, the terminal can clearly understand that "at least one service data unit in the protocol data unit corresponds to the same logical channel group." This effectively reduces channel occupancy, improves the overall efficiency of data transmission, and allows more service data to be transmitted simultaneously.

[0234] Alternatively, the second piece of information can be directly stated as "at least one service data unit in the protocol data unit corresponds to the same logical channel group." The terminal does not need to interpret the index, avoiding misunderstandings caused by incorrect or ambiguous index correspondences. This ensures that the terminal accurately receives instructions from the network device, thereby precisely executing the corresponding data processing operations and guaranteeing the accuracy of data transmission and processing.

[0235] Optionally, the second information can also indicate the effective time of the above-mentioned protocol data unit packetization method. This ensures that the terminal assembles PDUs according to the above-mentioned packetization method within the effective time.

[0236] In this embodiment, the network device can proactively instruct that the logical channel groups of the service data units in the terminal protocol data unit are the same, meaning that the network can precisely control the priority strategy of data transmission. The network can flexibly decide which service data units to process simultaneously based on real-time network conditions, service demands, and other factors, thereby better managing network resources and ensuring the quality of service for critical services.

[0237] In summary, the communication method described in this application starts from the improved PDU packet assembly stage. The MAC entity of the terminal determines the first time to generate the protocol data unit based on the time domain resources included in the first transmission resources. This allows the first time of generating the protocol data unit to be transmitted earlier to be advanced. Since the sequence number of the service data unit used by the protocol data unit that is packetized first is smaller, the service data unit with the smaller sequence number is transmitted first. This allows the terminal's transmission window to be updated in a timely manner, and the transmission of new service data units to begin, thereby reducing transmission latency.

[0238] This application also designs a communication method based on an improved PDU retransmission process. Figure 17 shows a flowchart of the communication method provided in an embodiment of this application. Similar to the communication method shown in Figure 17 above, in this communication method, the sending end can be a terminal or a network device in the above-mentioned communication system. The following description uses the example of the sending end being a terminal and the receiving end being a network device. For the scenario where the sending end is a network device and the receiving end is a terminal, please refer to the following text. As shown in Figure 17, the method may include the following steps:

[0239] S210, the terminal's MAC entity determines that the protocol data unit meets the first condition.

[0240] This protocol data unit refers to a protocol data unit that failed to be transmitted. Alternatively, this protocol data unit can also be interpreted as a protocol data unit that needs to be retransmitted.

[0241] The first condition includes: the first difference between the sequence number corresponding to the protocol data unit and the lower bound of the sequence number of the MAC entity's sending window is less than a first threshold. As mentioned earlier, the prerequisite for updating the sending window is that the PDU at the lower bound of the sending window has completed transmission. If the first difference between the sequence number corresponding to the protocol data unit and the lower bound of the sequence number of the MAC entity's sending window is less than the first threshold, it indicates that the SN of the SDU corresponding to the protocol data unit is close to the lower bound of the sequence number of the sending window. The first threshold can be set flexibly. The protocol data unit may include multiple service data units, and therefore may correspond to multiple sequence numbers. The first difference can be determined by any sequence number corresponding to the protocol data unit, such as the maximum sequence number, minimum sequence number, average sequence number, etc., and this invention does not impose specific limitations.

[0242] In one example, as shown in Figure 18, assuming the first threshold is set to 3, PDU1 includes SDUs with SN=1, SN=2, and SN=3, and PDU2 includes SDUs with SN=4, SN=5, and SN=6. The lower bound of the sending window is at SN=0. If PDU1 fails to transmit and needs to be retransmitted, and the difference between any of SN=1, SN=2, and SN=3 and SN=0 is less than 2 (e.g., SN=1), then PDU1 is considered to meet the first condition. However, for PDU2, if the difference between the minimum SN value SN=4 and SN=0 is not less than 2, then PDU2 is considered not to meet the first condition.

[0243] It is understandable that the above example is an illustration of whether a PDU meets the first condition. In specific implementations, based on implementation requirements, there may be other first threshold settings and other PDU compositions, without restriction.

[0244] S220, the terminal sends a first request to the network device, and the corresponding network device accepts the first request from the network device.

[0245] When the terminal's MAC entity determines that the protocol data unit meets the first condition, it means that failure to retransmit the protocol data unit in a timely manner may result in the transmission window not being updated in time. Therefore, the terminal immediately sends a first retransmission resource request to the network device to request the protocol data unit. In one possible interpretation, the first request can also be called a retransmission resource update request.

[0246] Optionally, the first request can be carried in multiple uplink channels. For example, the first request can be carried in the physical uplink control channel, or the first request can be carried in the physical uplink shared channel.

[0247] S230, the network device sends resource indication information to the terminal, and the corresponding terminal receives the resource indication information from the network device.

[0248] The resource indication information is used to indicate the aforementioned first retransmission resource.

[0249] For example, as shown in Figure 19, before step S210, the terminal sent PDU1 to the network device twice, but both transmissions failed. PDU2 was successfully transmitted between the two PDU1 transmissions. After the second PDU1 transmission, based on step S210, it was determined that the current PDU1 met the first condition, and at this point, the first request was sent.

[0250] Optionally, the method may further include:

[0251] S240, the terminal sends a protocol data unit to the network device according to the first retransmission resource, and the network device receives the protocol data unit from the terminal.

[0252] In this embodiment, when the terminal's MAC entity determines, based on the first condition, that the protocol data unit is a protocol data unit that needs to be retransmitted and is close to the lower bound of the sending window, it promptly requests the first retransmission resource of the protocol data unit from the network device so as to initiate the retransmission of the protocol data unit in a timely manner, so that the protocol data unit can be successfully transmitted as soon as possible, thereby enabling the sending window to be updated in a timely manner and the subsequent transmission of protocol data units to begin, reducing transmission latency.

[0253] In one embodiment, prior to step S220, the method may further include:

[0254] S250, the network device sends third information to the terminal, and correspondingly, the terminal receives the third information from the network device at a second time.

[0255] The third information is used to indicate the second retransmission resource for the protocol data unit. For example, this third information is conveyed through signaling such as DCI, MAC CE, etc.

[0256] As shown in Figure 19, since the determination of the second retransmission resource is a network implementation, the time-domain resource Td indicated by the second retransmission resource may be later. In other words, the time-domain resource Td indicated by the second retransmission resource may be later than the time-domain resource of the first retransmission resource.

[0257] As mentioned earlier, determining the time corresponding to the second retransmission resource and the transmission time corresponding to the third information carrying the second retransmission resource falls within the scope of network device implementation. Therefore, it's possible that the time-domain resource in the second retransmission resource is later. However, this possibility is not absolute; it's also possible that the time-domain resource in the second retransmission resource is earlier. In this case, the terminal has no need to request the first retransmission resource again. Therefore, the design of the first condition can also incorporate consideration of the second retransmission resource. That is, the first condition can also include: the first interval between the second time and the time corresponding to the time-domain resource in the second retransmission resource is greater than a second threshold. Whether the time-domain resource in the second retransmission resource is later can be determined by determining the size of the first interval between the second time and the time-domain resource in the second retransmission resource; that is, the first condition is set to the first interval being greater than the second threshold. The time corresponding to the time-domain resource in the second retransmission resource can be the start time, end time, or some intermediate time corresponding to the time-domain resource in the second retransmission resource.

[0258] In this embodiment of the application, the aforementioned time-domain resources may include multiple symbols or time slots, and are not limited thereto.

[0259] In this embodiment of the application, a new optional content for the first condition is introduced to ensure that when the time domain resource in the second retransmission resource is later, the terminal sends the first retransmission resource for requesting the protocol data unit to the network device, thereby saving transmission resources.

[0260] In one embodiment, the first request is also used to indicate the expected retransmission time of the protocol data unit.

[0261] The terminal can also request the desired retransmission time of the protocol data unit from the network device through the first request. When configuring the first retransmission resource, the network device can indicate the first retransmission resource based on the desired retransmission time.

[0262] In this embodiment of the application, the terminal can accurately understand the terminal's retransmission time requirement by indicating the expected retransmission time of the protocol data unit through the first request.

[0263] Optionally, the first request may indicate the desired retransmission time by carrying the following: the offset of the desired retransmission time relative to the time of the last transmission of the protocol data unit, or the offset of the desired retransmission time relative to the second time; or the offset of the desired retransmission time relative to the time domain resources in the second retransmission resource.

[0264] In this embodiment, multiple possible methods for indicating the desired retransmission time are provided. The terminal can select the most suitable method to indicate the desired retransmission time based on factors such as information availability, resulting in high system flexibility.

[0265] In one embodiment, the first request is carried in the physical uplink control channel, or the first request is carried in the physical uplink shared channel.

[0266] It is understood that, based on implementation requirements, the communication methods shown in Figure 14 and Figure 17 of this application can be used in combination without limitation.

[0267] In this embodiment of the application, from the perspective of improving the PDU retransmission process, when the terminal's MAC entity determines, based on the first condition, that the protocol data unit is a protocol data unit that needs to be retransmitted and is close to the lower boundary of the sending window, it promptly requests the first retransmission resource of the protocol data unit from the network device so as to initiate the retransmission of the protocol data unit in a timely manner, so that the protocol data unit can be successfully transmitted as soon as possible, thereby enabling the sending window to be updated in a timely manner and the subsequent protocol data unit transmission to begin, reducing transmission latency.

[0268] To improve PDU retransmission in downlink scenarios, this application also provides a communication method. Figure 20 shows a flowchart of the communication method provided in this application. In this communication method, the sending end is a network device in the aforementioned communication system, and the receiving end is a terminal. As shown in Figure 20, the method may include the following steps:

[0269] S310, the terminal's MAC entity determines that the number of protocol data unit transmissions exceeds the transmission threshold.

[0270] This protocol data unit refers to a protocol data unit that failed to be transmitted. Alternatively, this protocol data unit can also be interpreted as a protocol data unit that needs to be retransmitted.

[0271] For example, as shown in Figure 21, suppose PDU1 sends first, but the first transmission fails. PDU2 then sends, but the first transmission succeeds. PDU1 retransmits, and the second transmission also fails. A third transmission is then attempted, and the third also fails. Assuming the retransmission threshold is 2, PDU1's current retransmission count has exceeded the threshold. At this point, a fast retransmission request can be triggered.

[0272] S320: The terminal sends a first retransmission request to the network device, and the corresponding network device receives the first retransmission request from the terminal.

[0273] The first retransmission request mentioned here can also be called a fast retransmission request. Its core function is to request the network device to update the retransmission resources, that is, to request new third retransmission resources, and to hope that the retransmission resources scheduled by the network device can be as advanced as possible in the time domain. This is because retransmission resources that are advanced in the time domain help data to be retransmitted more quickly, thereby effectively reducing data transmission latency and improving data transmission efficiency and quality.

[0274] S330: The network device sends the fourth information to the terminal, and the terminal receives the fourth information from the network device.

[0275] The fourth piece of information is used to indicate the third retransmission resource of the protocol data unit. For example, the third retransmission resource can be carried by signaling such as DCI or MAC CE.

[0276] S340, the network device sends protocol data units to the terminal based on the third multiplex resource, and the corresponding terminal receives protocol data units from the terminal based on the third multiplex resource.

[0277] In this embodiment, after the terminal's MAC entity determines that the number of times the protocol data unit has been transmitted exceeds the transmission threshold, it promptly requests a fast retransmission of the protocol data unit, which can reduce the impact of HARQ out-of-order transmission and thus reduce transmission latency.

[0278] In one embodiment, the first retransmission request may include a retransmission request flag. Once the network device successfully receives the retransmission request flag, it can quickly and clearly know that retransmission resources, configured as early as possible in the time domain, need to be provided to the terminal. This method of conveying specific requests through flags is simple and efficient, helping the network device to accurately understand the terminal's needs.

[0279] Furthermore, there are several flexible options for sending the first retransmission request. One common option is to send the first retransmission request together with the previous Hybrid Automatic Repeat Request (HARQ). This combined sending method can optimize the communication process to some extent, reduce signaling overhead, and improve the utilization efficiency of communication resources. Because each request requires a certain amount of communication resources during actual communication, merging related requests can reduce resource consumption without affecting functionality.

[0280] Regarding the effective time period of the first retransmission request, there are also various optional configuration methods, which fully consider different application scenarios and needs:

[0281] Method 1: Protocol configuration.

[0282] This means that during the design phase of the communication system, the effective time period of the first retransmission request is clearly defined according to the established communication protocol. This approach offers high stability and standardization, ensuring that all devices conforming to the protocol operate according to uniform rules. It is suitable for scenarios with strict requirements on communication processes and a high degree of standardization. For example, network devices configure the effective or activation time of the first retransmission request, along with corresponding transmission or retransmission thresholds, for terminal devices. If the number of transmissions or retransmissions exceeds the threshold within the configured effective or activation time, the terminal device sends the first retransmission request.

[0283] Method 2: The network device indicates the effective period of the fast retransmission request.

[0284] Network devices act as managers in the entire communication system, comprehensively considering factors such as the overall system load, the service needs of each terminal, and the current channel conditions. Based on these comprehensive considerations, network devices explicitly indicate the effective period of fast retransmission requests to the terminals. This approach allows network devices to flexibly adjust the effective period according to actual conditions, thereby achieving optimized allocation and efficient utilization of network resources.

[0285] Method 3: The terminal actively requests the above-mentioned effective time period from the network device.

[0286] During operation, the terminal autonomously determines and requests the effective time period of the first retransmission request from the network device based on the real-time needs of its running applications, the current network environment, and its own sensitivity to data transmission latency. This approach fully reflects the terminal's autonomy and personalization, better meeting the diverse needs of different terminals in different scenarios. For example, for video call applications with extremely high real-time requirements, the terminal may request a shorter and more precise effective time period to ensure timely retransmission of video data and maintain smooth call quality.

[0287] In one embodiment, prior to step S330, the method may further include:

[0288] S350: The terminal sends a fast retransmission request to the network device, and the network device receives the fast retransmission request from the terminal.

[0289] The retransmission request information indicates the desired retransmission time for the terminal. For example, the retransmission request information may include any of the following:

[0290] The expected retransmission time offset from the time-domain resources of the previous protocol data unit: During communication, the time-domain resources of the previous protocol data unit's transmission resources are an important reference point. By calculating the expected retransmission time offset from this time-domain resource, the terminal can clearly inform the network device when it expects to retransmit. The advantage of this approach is that it closely integrates previous data transmission information, determining the retransmission timing based on the existing transmission time frame. This helps the network device perform resource scheduling within a familiar timeframe, making the retransmission operation more consistent and rational.

[0291] Offset from the current HARQ feedback time: Hybrid Automatic Repeat Request (HARQ) feedback is a crucial step in the terminal reporting data reception status to the network device. Using the current HARQ feedback time as a baseline, setting an offset from that time indicates the expected retransmission time, offering strong real-time performance and specificity. Because HARQ feedback directly reflects the terminal's current data reception status, determining the retransmission time based on this allows the network device to allocate retransmission resources to the terminal promptly and accurately according to the latest communication status, effectively improving data transmission success rates.

[0292] Offset to the fast retransmission request time sent in step S320: Using the fast retransmission request time sent in step S320 as a reference, an offset is set to determine the expected retransmission time, providing the terminal with a flexible indication method based on its own request history. This method is suitable for scenarios with specific requirements for retransmission time and that depend on previous request time intervals. For example, in some services with high requirements for the continuity and order of data transmission, the terminal can accurately plan the expected time of the next retransmission based on previous request times, ensuring that data is transmitted according to a specific rhythm and order.

[0293] Optionally, the fast retransmission request message can be reused from the most recent PUCCH or PUSCH.

[0294] In summary, the embodiments of this application design various communication methods to reduce PDU transmission latency. In one communication method, the MAC entity of the terminal determines the first time for generating protocol data units based on the time-domain resources included in the first transmission resources. This allows the first time of generating protocol data units that will be transmitted earlier to be advanced. Since the sequence number of the service data unit used by the protocol data unit that is packetized earlier is smaller, the service data unit with the smaller sequence number is transmitted first. This enables the terminal's transmission window to be updated in a timely manner, allowing the transmission of new service data units to begin, thus reducing transmission latency.

[0295] In another communication method, when the terminal's MAC entity determines, based on the first condition, that the protocol data unit is a protocol data unit that needs to be retransmitted and is close to the lower bound of the transmission window, it promptly requests the first retransmission resource of the protocol data unit from the network device so as to initiate the retransmission of the protocol data unit in a timely manner, so that the protocol data unit can be transmitted successfully as soon as possible, thereby updating the transmission window in a timely manner and starting the transmission of subsequent protocol data units, reducing transmission latency.

[0296] In another communication method, when the terminal's MAC entity determines that the number of times the protocol data unit has been transmitted exceeds the transmission threshold, it promptly requests a fast retransmission of the protocol data unit, which can reduce the impact of HARQ out-of-order transmission and thus reduce transmission latency.

[0297] The communication methods described in this application can be used in combination or individually, without limitation.

[0298] It is understood that the communication method provided in this application embodiment does not limit the applicable communication system. For example, the communication method provided in this application embodiment can be applied to an O-RAN communication system. Based on the functional design of O-DU / O-CU / O-RU in the O-RAN communication system, the steps executed by the network device in the communication method provided in this application embodiment can be flexibly implemented by one or more of O-DU / O-CU / O-RU, without limitation.

[0299] In another embodiment, the communication method proposed in this application is also applicable to a chip system. Specifically, the chip system on the network side and / or the terminal side is provided with a memory unit for storing the corresponding information for implementing the communication method of this application. Based on the corresponding information, the processor, in conjunction with a radio frequency / antenna module with transceiver functions, interacts with the other side to implement the communication method of this application.

[0300] The foregoing mainly describes the solution provided by the embodiments of this application from the perspective of the execution logic of each step. It is understood that each node, such as a network device, includes the hardware structure and / or software module corresponding to each function in order to achieve the above functions. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein, the method of the embodiments of this application can be implemented in hardware, software, or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0301] This application embodiment can divide the network device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0302] Figure 22 illustrates a possible exemplary block diagram of the communication device involved in the embodiments of this application. As shown in Figure 22, the communication device 900 may include modules or units for implementing the methods described above. In one possible design, the communication device 900 includes a processing unit 902 and a communication unit 903. Optionally, the communication device 900 may further include a storage unit 901 for storing device program code and / or data.

[0303] The communication device 900 can be a terminal-side device in the above embodiments, such as a terminal or a communication module in a terminal, or a circuit or chip in a terminal that is responsible for communication functions.

[0304] For example, in one embodiment, the processing unit 902 is configured to: obtain a first transmission resource corresponding to a service data unit through a media access control entity; and determine a first time for generating a protocol data unit based on the time domain resources included in the first transmission resource through the media access control entity, wherein the protocol data unit includes at least one service data unit.

[0305] The communication unit 903 is used to: send protocol data units generated by the media access control entity in the first time.

[0306] In one possible design, when the communication device 900 is a terminal or a communication module within a terminal, the function of the processing unit 902 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The function of the communication unit 903 can be implemented by transceiver circuitry.

[0307] In one possible design, when the communication device 900 is a circuit or chip in a terminal responsible for communication functions, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 902 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 903 can be implemented by an interface circuit or data transceiver circuit on the aforementioned chip.

[0308] In one possible design, when the communication device 900 is a terminal or a processing module within a terminal, the functionality of the processing unit 902 can be implemented by one or more processors. Specifically, the processor may include a GPU, or a system-on-a-chip (SoC) or SIP chip containing a GPU. Alternatively, the processor may include an AI processor, or a SoC or SIP chip containing an AI processor. Or, the processor may include an ASIC, or a SoC or SIP chip containing an ASIC. The functionality of the communication unit 903 can be implemented by transceiver circuitry.

[0309] In one possible design, when the communication device 900 is a circuit or chip in a terminal responsible for processing functions, such as a GPU or a system-on-a-chip (SoC) or SIP chip containing a GPU, an AI processor or a SoC or SIP chip containing an AI processor, or an ASIC or a SoC or SIP chip containing an ASIC, the function of the processing unit 902 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 903 can be implemented by interface circuitry or data transceiver circuitry on the aforementioned chip.

[0310] The communication device 900 can be a network device as described in the above embodiments. For example, in one embodiment, the communication unit 903 is used to: send a first transmission resource corresponding to a service data unit; and receive a protocol data unit, wherein the protocol data unit is a protocol data unit generated according to a first time, the first time being a time determined according to the first transmission resource, and the protocol data unit includes at least one service data unit.

[0311] It is understood that the division of units in the above-described device is merely a logical functional division. One function can correspond to one functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated onto a single physical entity, or distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for specific applications, but such implementations should not be considered beyond the scope of this application.

[0312] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0313] In one example, storage unit 901 may include random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory and / or registers, etc.

[0314] Referring to Figure 23, which exemplarily illustrates a possible structural schematic of a communication device, it is understood that the communication device 700 includes means of necessary forms, such as modules, units, elements, circuits, or interfaces, appropriately configured together to execute this solution. The communication device 700 can be a receiving end or a transmitting end as described in the above method embodiments, used to implement the methods described in the above method embodiments. The communication device 700 includes one or more processors 701. The processor 701 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, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[0315] Optionally, in one design, the processor 701 may include a program 703 (sometimes also referred to as code or instructions) that can be executed on the processor 701 to cause the communication device 700 to perform the methods described in the above embodiments. In yet another possible design, the communication device 700 includes circuitry (not shown in FIG23) for implementing the signal processing functions in the above embodiments.

[0316] Optionally, the communication device 700 may include one or more memories 702 storing a program 704 (sometimes referred to as code or instructions), which can be run on the processor 701 to cause the communication device 700 to perform the methods described in the above method embodiments.

[0317] Optionally, the processor 701 and / or memory 702 may include AI modules 707 and 708, which are used to implement AI-related functions. The AI ​​modules can be implemented through software, hardware, or a combination of both. For example, the AI ​​module may include a RIC module. For example, the AI ​​module may be a near real-time RIC or a non-real-time RIC.

[0318] Optionally, the processor 701 and / or memory 702 may also store data. The processor and memory may be configured separately or integrated together.

[0319] Optionally, the communication device 700 may further include a transceiver 705 and / or an antenna 706. The processor 701, sometimes referred to as a processing unit, controls the communication device. The transceiver 705, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to realize the transmission and reception functions of the communication device through the antenna 706.

[0320] This application also provides a communication system, which may include a terminal and a network device. The terminal and network device may have the functions of the aforementioned communication device.

[0321] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be a terminal device of any of the foregoing embodiments, such as an internal storage unit including a data sending end and / or a data receiving end, such as a hard disk or memory of the terminal device. The computer-readable storage medium can also be an external storage device of the terminal device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal device. Further, the computer-readable storage medium can include both the internal storage unit and the external storage device of the terminal device. The computer-readable storage medium is used to store the computer program and other programs and data required by the terminal device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0322] This application also provides computer instructions. All or part of the processes in the above method embodiments can be executed by computer instructions to instruct related hardware (such as computers, processors, network devices, and terminals). The program can be stored in the aforementioned computer-readable storage medium.

[0323] This application also provides a computer program product that, when run on a computer, causes the above-described method embodiments to be executed.

[0324] This application also provides a chip system. The chip system may be composed of chips or may include chips and other discrete devices, without limitation. The chip system includes a processor and a transceiver. All or part of the processes in the above method embodiments can be completed by this chip system, such as the chip system being used to implement the functions performed by the network devices or terminals in the above method embodiments.

[0325] In one possible design, the chip system further includes a memory for storing program instructions and / or data. When the chip system is running, the processor executes the program instructions stored in the memory to enable the chip system to perform the functions performed by the network device or terminal in the above method embodiments.

[0326] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0327] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store instructions and / or data.

[0328] It should be noted that the terms "first" and "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0329] It should be understood that in the embodiments of this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three or more, and "and / or" is used to describe the association relationship of related objects, indicating that there can be three relationships. For example, "A and / or B" can represent: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple. It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A. For example, B can be determined based on A. It should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information. Furthermore, the term "connection" in the embodiments of this application refers to various connection methods, such as direct or indirect connections, to achieve communication between devices; the embodiments of this application do not impose any limitations on this.

[0330] Unless otherwise specified, the term "transmission" in the embodiments of this application refers to bidirectional transmission, encompassing the actions of sending and / or receiving. Specifically, "transmission" in the embodiments of this application includes sending data, receiving data, or both sending and receiving data. In other words, data transmission here includes uplink and / or downlink data transmission. Data may include channels and / or signals; uplink data transmission refers to uplink channel and / or uplink signal transmission, and downlink data transmission refers to downlink channel and / or downlink signal transmission. The terms "network" and "system" in the embodiments of this application refer to the same concept; a communication system is a communication network.

[0331] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0332] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0333] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0334] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device, such as a microcontroller, chip, or processor, to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0335] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0336] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0337] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0338] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0339] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

[0340] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method characterized by comprising: The method includes: The media access control entity acquires the first transmission resource corresponding to the service data unit; The media access control entity determines the first time for generating the protocol data unit based on the time-domain resources included in the first transmission resource, and the protocol data unit includes at least one service data unit. The media access control entity sends the protocol data unit generated based on the first time.

2. The method of claim 1, wherein, The media access control entity determines the first time for generating the protocol data unit based on the time-domain resources included in the first transmission resource, including: The media access control entity determines the first time based on the time-domain resources included in the first transmission resources and the minimum processing time, wherein the minimum processing time is the time between receiving the physical downlink control channel and transmitting the physical uplink shared channel.

3. The method of claim 2, wherein, The interval between the first time and the time-domain resources included in the first transmission resource is the minimum processing time, and the first time is before the time-domain resources included in the first transmission resource.

4. The method according to any one of claims 1 to 3, characterized in that, The at least one service data unit corresponds to the same logical channel priority.

5. The method of claim 4, wherein, The method further includes: Receive first information, wherein the first information is used to indicate that the at least one service data unit corresponds to the same logical channel priority.

6. The method according to any one of claims 1 to 5, characterized in that, The at least one service data unit corresponds to the same logical channel group.

7. The method according to claim 6, characterized in that, The method further includes: Receive second information, wherein the second information is used to indicate that the at least one service data unit corresponds to the same logical channel group.

8. A communication method characterized by comprising: The method includes: The first transmission resource corresponding to the sending service data unit; A protocol data unit is received, wherein the protocol data unit is a protocol data unit generated according to a first time, the first time being a time determined according to the first transmission resource, and the protocol data unit includes at least one of the service data units.

9. The method of claim 8, wherein, The at least one service data unit corresponds to the same logical channel priority.

10. The method of claim 9, wherein, The method further includes: Send a first message, wherein the first message is used to indicate that the at least one service data unit corresponds to the same logical channel priority.

11. The method according to any one of claims 8-10, characterized in that, The at least one service data unit corresponds to the same logical channel group.

12. The method of claim 11, wherein, The method further includes: Send a second message, wherein the second message is used to indicate that the at least one service data unit corresponds to the same logical channel group.

13. A method of communication, comprising: include: The media access control entity determines that the protocol data unit meets a first condition, wherein the first condition includes: a first difference between the sequence number corresponding to the protocol data unit and the lower bound of the sequence number of the transmission window of the media access control entity is less than a first threshold; Send a first request, the first request being used to request a first retransmission resource for the protocol data unit; Receive resource indication information, wherein the resource indication information is used to indicate the first retransmission resource.

14. The method according to claim 13, characterized in that, Before sending the first request, the method further includes: A third message is received at a second time, wherein the third message is used to indicate the second retransmission resource of the protocol data unit; The first condition further includes: the first interval between the second time and the time-domain resources in the second retransmission resource is greater than the second threshold.

15. The method according to claim 14, characterized in that, The first request is also used to indicate the expected retransmission time of the protocol data unit.

16. The method according to claim 15, characterized in that, The first request includes: The offset of the expected retransmission time relative to the second time; Alternatively, the desired retransmission time is offset relative to the time-domain resources in the second retransmission resource.

17. The method according to any one of claims 13-16, characterized in that, The first request is carried in the physical uplink control channel, or the first request is carried in the physical uplink shared channel.

18. A communication device, characterized in that, Includes a module that performs the method as described in any one of claims 1-17.

19. A communication device, characterized in that, The communication device includes a processor for supporting the communication device in performing the method as described in any one of claims 1-17.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed, cause the method described in any one of claims 1-17 to be performed.

21. A computer program product, characterized in that, When it is run on a computer, it causes the method described in any one of claims 1-17 to be performed.

22. A chip, characterized in that, The chip includes a processor for supporting the chip in performing the method as described in any one of claims 1-17.

Images