Data transmission methods, apparatuses, devices and storage medium

Abstract

The present application belongs to the technical field of mobile communications. Disclosed are data transmission methods, apparatuses, devices and a storage medium. A method comprises: multiplexing at least two subunits into a same data unit, and / or transmitting the at least two subunits by means of the same data unit. The present application enables data of subunits corresponding to different services to be transmitted by means of a same data unit, thereby reducing scheduling signaling overheads and reducing transmission delay.

Description

Data transmission methods, apparatus, equipment and storage media Technical Field

[0001] This application relates to the field of mobile communication technology, and in particular to a data transmission method, apparatus, device and storage medium. Background Technology

[0002] In the future, a single communication device may support multiple services simultaneously, with different services having different performance requirements, such as different latency requirements and different reliability requirements.

[0003] Further discussion and research are needed regarding the data transmission implementation of communication devices. Summary of the Invention

[0004] This application provides a data transmission method, apparatus, device, and storage medium. The technical solution is as follows:

[0005] According to one aspect of this application, a data transmission method is provided, the method being performed by a first communication device, the method comprising:

[0006] Multiplexing at least two sub-units to the same data unit, and / or transmitting the at least two sub-units through the same data unit.

[0007] According to another aspect of this application, a data transmission method is provided, the method being performed by a second communication device, the method comprising:

[0008] A receiving data unit, wherein at least two sub-units are multiplexed in the data unit, or wherein the at least two sub-units are transmitted through the data unit.

[0009] According to another aspect of this application, a first device is provided, the first device comprising:

[0010] A transmitting module is used to multiplex at least two sub-units into the same data unit, and / or to transmit the at least two sub-units through the same data unit.

[0011] According to another aspect of this application, a second device is provided, the second device comprising:

[0012] A receiving module is used to receive a data unit, wherein the data unit multiplexes at least two sub-units, or the at least two sub-units are transmitted through the data unit.

[0013] According to another aspect of this application, a first communication device is provided, the first communication device comprising: a processor; a transceiver connected to the processor; wherein the transceiver is configured to multiplex at least two sub-units to the same data unit, and / or transmit the at least two sub-units through the same data unit.

[0014] According to another aspect of this application, a second communication device is provided, the second communication device comprising: a processor; a transceiver connected to the processor; wherein the transceiver is configured to receive a data unit, the data unit multiplexing at least two sub-units, or the at least two sub-units transmitting data through the data unit.

[0015] According to another aspect of this application, a computer-readable storage medium is provided, wherein a computer program is stored therein, the computer program being executed by a processor to implement the above-described data transmission method.

[0016] According to another aspect of this application, a chip is provided, the chip including programmable logic circuitry and / or program instructions, which, when the chip is operated on a communication device, are used to multiplex at least two sub-units to the same data unit, and / or to transmit the at least two sub-units through the same data unit.

[0017] According to another aspect of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium; a processor of a communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the communication device to implement the above-described data transmission method.

[0018] According to another aspect of this application, a computer program is provided, which is executed by the processor of a communication device to implement the above-described data transmission method.

[0019] The technical solutions provided in this application have at least the following beneficial effects:

[0020] By multiplexing at least two sub-units into the same data unit, and / or transmitting at least two sub-units through the same data unit, it is possible to carry data from sub-units corresponding to different services through the same data unit, thereby reducing scheduling signaling overhead and transmission latency. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 is a schematic diagram of the system architecture of a communication system provided in an exemplary embodiment of this application;

[0023] Figure 2 is a flowchart of a data transmission method provided in an exemplary embodiment of this application;

[0024] Figure 3 is a flowchart of a data transmission method provided in an exemplary embodiment of this application;

[0025] Figure 4 is a flowchart of a data transmission method provided in an exemplary embodiment of this application;

[0026] Figure 5 is a flowchart of a PUSCH transmission method provided in an exemplary embodiment of this application;

[0027] Figure 6 is a schematic diagram of a DCI provided in an exemplary embodiment of this application;

[0028] Figure 7 is a schematic diagram of SDU segmentation provided in an exemplary embodiment of this application;

[0029] Figure 8 is a schematic diagram of adding padding bits provided in an exemplary embodiment of this application;

[0030] Figure 9 is a flowchart of a method for determining the size of a sub-unit provided in an exemplary embodiment of this application;

[0031] Figure 10 is a schematic diagram of a sub-unit provided in an exemplary embodiment of this application;

[0032] Figure 11 is a block diagram of a first apparatus provided in an exemplary embodiment of this application;

[0033] Figure 12 is a block diagram of a second apparatus provided in an exemplary embodiment of this application;

[0034] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail here, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims. All other embodiments obtained by those skilled in the art without inventive effort in relation to the embodiments of this application are within the scope of protection of this application. The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The singular forms “a,” “the,” and “the” used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more associated listed items. It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word “if” as used herein may be interpreted as “when”, “when”, or “in response to determination”.

[0036] The technical solutions described in some embodiments of this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS) system, Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN) system, and Wireless Fidelity (WCDMA) system. It can be used with Fidelity (WiFi) systems, 5th generation mobile communication technology (5G) systems, cellular IoT systems, cellular passive IoT systems, and can also be used with subsequent evolution systems of 5G NR systems, as well as 6th generation mobile communication technology (6G) systems and subsequent evolution systems.

[0037] It should be understood that in some embodiments of this application, "5G" may also be referred to as "5G NR" or "NR".

[0038] It should be understood that in the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0039] An introduction to downlink data transmission:

[0040] Communication systems typically support the following two downlink data transmission methods:

[0041] 1. Terminal devices receive downlink control signaling from network devices and receive downlink data transmission based on the parameters in the downlink control signaling. This scheduling method is usually called dynamic scheduling. The advantage of dynamic scheduling is that the scheduler can determine the transmission parameters based on real-time traffic volume and physical channel conditions, resulting in high transmission efficiency. Terminal devices first receive downlink control signaling and then receive downlink data channels or transmit uplink data channels based on the parameters indicated in the downlink control signaling. However, terminal devices need to perform blind detection on the downlink control signaling, which increases reception complexity. Furthermore, the processing delay at the receiving end includes both demodulating the downlink control signaling and demodulating the downlink data.

[0042] 2. The terminal device receives higher-layer signaling (e.g., Radio Resource Control (RRC) signaling) from the network device and receives downlink data transmission based on the parameters in this higher-layer signaling. This method is called semi-persistent scheduling (SPS) in LTE and NR systems. For data that arrives periodically and has a constant traffic volume, under stable transmission conditions (e.g., no rapid movement), using semi-persistent scheduling can reduce the overhead of downlink control signaling in the system and simplify the receiving process at the receiver.

[0043] An introduction to extended reality (XR) / ultra-reliable low-latency communications (URLLC):

[0044] Communication systems have various service transmission requirements, such as XR, URLLC, enhanced mobile broadband (eMBB), and massive machine-type communication (mMTC).

[0045] URLLC services require high reliability and low latency transmission. XR services also have similar requirements, but there are some differences between them.

[0046] The current project research covers technologies including Augmented Reality (AR), Virtual Reality (VR), and Cloud Gaming (CG). A major service of XR / CG is video streaming, whose arrival rate can be measured in frames per second (fps), for example, 30fps, 60fps, 90fps, and 120fps, corresponding to video stream periods of {33.33ms, 16.67ms, 11.11ms, and 8.33ms}. Furthermore, XR also has requirements regarding transmission latency.

[0047] In the future, for example in 6G systems, a single terminal device will support multiple services simultaneously. These services have different performance requirements, such as latency and reliability. Transmitting data from services with different performance requirements through separate physical channels would result in significant scheduling and signaling overhead. Furthermore, if multiple physical channels cannot be transmitted simultaneously (i.e., time-division multiplexing), transmission latency would increase. If data from multiple services are encoded together and retransmitted using Hybrid Automatic Repeat Request (HARQ), network devices may schedule services based on high reliability, leading to low overall system transmission efficiency.

[0048] For XR services, it is permissible to decode a subset of PDUs from a Protocol Data Unit Set (PDU Set). This means that in some cases, receiving a portion of the PDUs in the PDU Set is sufficient to obtain the data. However, when a Transport Block (TB) / Code Block Group (CBG) contains multiple Radio Link Control (RLC) Service Data Units (SDUs) with different requirements, inefficiency arises: if partial data packets are allowed to decode the complete data packet, redundant transmission occurs. In other words, receiving only a portion of the PDUs in the PDU Set is sufficient; the remaining PDUs do not need to be redundantly transmitted. Furthermore, when an SDU can be segmented into multiple parts and transmitted through different TBs / Code Blocks (CBs) / CBGs, significant latency occurs: if the data packet is segmented and different segments are transmitted using different units, the receiving end must wait for the remaining data packets after receiving only a portion of the segmented data packets.

[0049] The method provided in this application, by multiplexing at least two sub-units into the same data unit, and / or transmitting at least two sub-units through the same data unit, enables the transmission of data from sub-units corresponding to different services through the same data unit, thereby reducing scheduling signaling overhead and transmission latency. When supporting the recovery of overall data from partial data, by reducing the segmentation of data packets, the receiving end can recover the overall data information upon receiving partial data packets, thus avoiding latency and reducing redundant transmission.

[0050] Figure 1 is a schematic diagram of the system architecture of a communication system 100 provided in an exemplary embodiment of this application. The system architecture may include: a terminal device 10, an access network device 20, and a core network device 30.

[0051] Terminal equipment 10 can refer to UE (User Equipment), access terminal equipment, user unit, user station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, wireless communication equipment, user agent, or user device. Optionally, terminal equipment can also be a cellular phone, cordless phone, SIP (Session Initiation Protocol) phone, WLL (Wireless Local Loop) station, PDA (Personal Digital Assistant), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal equipment in 5GS (5th Generation System), or terminal equipment in the future evolved PLMN (Public Land Mobile Network), etc., and this application embodiment is not limited thereto. For ease of description, the devices mentioned above are collectively referred to as terminal equipment.

[0052] It should be noted that there are usually multiple terminal devices 10, and one or more terminal devices 10 can be distributed within the cell managed by each access network device 20. Furthermore, one or more terminal devices 10 can also be distributed outside the cell managed by the access network device 20. Different terminal devices 10 can communicate with each other via sidelinks.

[0053] Access network device 20 is a device deployed in an access network to provide wireless communication functionality to terminal device 10. Access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the name of the device with access network device functionality may differ; for example, in a 5G NR system, it is called gNodeB or gNB. As communication technologies evolve, the name "access network device" may change. For ease of description, in this embodiment, the aforementioned devices providing wireless communication functionality to terminal device 10 are collectively referred to as access network devices. Optionally, a communication relationship can be established between terminal device 10 and core network device 30 through access network device 20. For example, in a Long Term Evolution (LTE) system, access network device 20 may be one or more eNodeBs within an EUTRAN (Evolved Universal Terrestrial Radio Access Network) or EUTRAN; in a 5G NR system, access network device 20 may be one or more gNBs within an RAN (Radio Access Network).

[0054] The core network equipment 30 primarily functions to provide user connectivity, manage users, and bear services, serving as an interface to external networks. For example, core network equipment in a 5G NR system may include AMF (Access and Mobility Management Function) entities, UPF (User Plane Function) entities, and SMF (Session Management Function) entities. Access network equipment 20 and core network equipment 30 can be collectively referred to as network equipment.

[0055] In one example, access network device 20 and core network device 30 communicate with each other via some over-the-air technology, such as the NG interface in a 5G NR system. Access network device 20 and terminal device 10 communicate with each other via some over-the-air technology, such as the Uu interface. Terminal devices 10 communicate with each other via some over-the-air technology, such as the PC5 interface.

[0056] Figure 2 is a flowchart of a data transmission method provided in an exemplary embodiment of this application. The method can be performed by a first communication device. The first communication device can be a terminal device. In other embodiments, the first communication device can be a network device (such as a base station). In implementation, the method can be performed by a Medium Access Control (MAC) entity, for example, by a first MAC entity of the first communication device. The method includes:

[0057] Step 202: Multiplex at least two sub-units to the same data unit, and / or transmit at least two sub-units through the same data unit.

[0058] At least two sub-units are multiplexed into the same data unit. This can also be understood as at least two sub-units being packetized or packaged into the same data unit, or as data corresponding to at least two sub-units being carried or transmitted through the same data unit, or as PDUs (such as MAC PDUs) corresponding to at least two sub-units being carried or transmitted through the same data unit. The data unit includes at least two sub-units, or it can be understood that the data unit includes multiple sub-units. In some embodiments, at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to the same service or logical channel or information. In some embodiments, the data unit corresponds to uplink data or uplink transmission. In other embodiments, the data unit corresponds to downlink data or downlink transmission.

[0059] In some embodiments, one of the at least two sub-units is one of a Transport Block (TB), Code Block (CB), Code Block Group (CBG), Sub-Data Channel, Hybrid Automatic Repeat Request (HARQ) process, HARQ sub-process, and Code Word (CW). The Sub-Data Channel can be either a Sub-Physical Uplink Shared Channel (PUSCH) or a Sub-Physical Downlink Shared Channel (PDSCH). A sub-unit being a HARQ process can be understood as the sub-unit transmitting data or information for the HARQ process; a sub-unit being a HARQ sub-process can be understood as the sub-unit transmitting data or information for the HARQ sub-process.

[0060] In some embodiments, the data unit is one of Dynamic Grant (DG) resources, Configured Grant (CG) resources, PUSCH, CW, TB, data channel, and HARQ process. A data unit being a HARQ process can be understood as the data or information transmitted by the data unit for the HARQ process. The data channel can be PDSCH. In some embodiments, the data unit is configured by resource configuration information or scheduled by scheduling information. In some embodiments, the resource configuration information or scheduling information is also used to indicate one or more of the following: the number of at least two sub-units, the data volume or size of the data unit, and the data volume or size of each sub-unit. The data volume or size can be explicitly indicated or implicitly indicated, for example, through a Modulation and Coding Scheme (MCS), and the resource location and / or the number of resources. In some embodiments, the resource configuration information or scheduling information further includes first information, which is used to indicate one or more of the following: whether to perform packet segmentation or determine the size of sub-units based on packet (packet boundary), whether to allow non-uniform segmentation, whether to allow reporting segmentation information, whether to allow adding padding information to sub-units, and whether to allow reporting padding information. For segmentation and padding, please refer to the relevant content below.

[0061] In some embodiments, all or some of the sub-units in at least two sub-units have attributes. The attributes of a sub-unit are equivalent to / can be replaced by the features of the sub-unit. In some embodiments, at least two sub-units have the same attribute, for example, each sub-unit in at least two sub-units has the same attribute; or, at least two sub-units have different attributes, for example, each sub-unit in at least two sub-units has different attributes; or, some sub-units in at least two sub-units have the same attribute, and sub-units other than those some sub-units have different attributes, for example, at least two sub-units contain sub-units with the same attribute and sub-units with different attributes.

[0062] In some embodiments, the attributes of a sub-unit include one or more of the following: sub-unit identifier; sub-unit sorting; sub-unit index; sub-unit priority; reliable transmission requirement corresponding to the sub-unit; priority transmission requirement corresponding to the sub-unit; importance corresponding to the sub-unit; data transmission type corresponding to the sub-unit; bit error rate guaranteed by the sub-unit; decoding method corresponding to the sub-unit; reporting method corresponding to the sub-unit; segmentation method corresponding to the sub-unit; and padding method corresponding to the sub-unit. In some embodiments, the data transmission type corresponding to the sub-unit includes one or more of the following: delay-critical data, delay-reported data, and data volume using additional logical channel (LCH) priority. In some embodiments, the decoding method corresponding to the sub-unit includes the decoding or generation method of the HARQ process, such as the decoding or generation method of the PUCCH HARQ process. In some embodiments, the reporting method corresponding to the sub-unit includes whether segmentation information reporting is allowed and / or whether padding information reporting is allowed. In some embodiments, the segmentation method corresponding to the subunit includes whether to perform packet segmentation based on the data packet (data packet boundary), whether to determine the size of the subunit based on the data packet (data packet boundary), and whether to allow one or more of the following: non-uniform segmentation. In some embodiments, the padding method corresponding to the subunit includes whether to allow adding padding information to the subunit. For segmentation and padding, please refer to the relevant content below.

[0063] Reuse of sub-units:

[0064] In some embodiments, the first communication device multiplexes different LCHs or different service data into different sub-units of at least two sub-units, or transmits different LCHs or different service data through different sub-units of at least two sub-units. It should be noted that multiplexing an LCH into a sub-unit can be understood as mapping an LCH to a sub-unit, or multiplexing an LCH into a sub-unit can be understood as mapping, multiplexing, or carrying LCH data into a sub-unit; multiplexing service data into a sub-unit can be understood as mapping or carrying service data into a sub-unit.

[0065] In some embodiments, the first communication device may also multiplex different LCHs or different service data into the same sub-unit in at least two sub-units, or transmit different LCHs or different service data through the same sub-unit in at least two sub-units.

[0066] In some embodiments, the first communication device multiplexes different LCHs to different sub-units of at least two sub-units according to a first mapping relationship; or, multiplexes different service data to different sub-units of at least two sub-units according to a second mapping relationship; or, transmits different LCHs through different sub-units of at least two sub-units according to the first mapping relationship; or, transmits different service data through different sub-units of at least two sub-units according to the second mapping relationship. The first mapping relationship includes a mapping relationship and / or mapping restrictions between at least one LCH and at least one sub-unit, and the second mapping relationship includes a mapping relationship and / or mapping restrictions between at least one service data and at least one sub-unit. In some embodiments, the first mapping relationship is used to configure, indicate, or allow mapping different LCHs to different sub-units. The second mapping relationship is used to configure, indicate, or allow mapping different service data to different sub-units.

[0067] In some embodiments, the first communication device may also multiplex different LCHs to the same sub-unit in at least two sub-units according to a first mapping relationship; or, multiplex different service data to the same sub-unit in at least two sub-units according to a second mapping relationship; or, transmit different LCHs through the same sub-unit in at least two sub-units according to the first mapping relationship; or, transmit different service data through the same sub-unit in at least two sub-units according to the second mapping relationship. The scenario is that, based on the first mapping relationship or the second mapping relationship, the LCH or service data meets the condition of being mapped or multiplexed to the same sub-unit.

[0068] In some embodiments, the first mapping relationship includes a mapping relationship between at least one first parameter of the LCH and at least one second parameter of a subunit. The first parameter includes at least one of the following: LCH identifier, LCH index, LCH sequence number (Identity Document, ID), LCH priority, LCH prioritized bit rate (PBR), LCH corresponding service, LCH corresponding reliable transmission requirement, LCH corresponding priority transmission requirement, whether the LCH contains delay-sensitive data, whether the LCH contains delay reporting data, whether the LCH uses additional LCH priority, LCH corresponding importance, whether the LCH requires a preset (specific) decoding method, and whether the LCH data packets do not support or allow segmented transmission. The second parameter includes at least one of the following: subunit identifier, subunit order, subunit index, subunit priority, subunit corresponding reliable transmission requirement, subunit corresponding priority transmission requirement, subunit corresponding importance, subunit corresponding data transmission type, subunit guaranteed bit error rate, subunit corresponding decoding method, subunit corresponding reporting method, subunit corresponding segmentation method, and subunit corresponding padding method. In some embodiments, the data transmission type corresponding to the subunit includes one or more of the following: transmission delay sensitive data, transmission delay reporting data, and data volume using additional LCH priority. In some embodiments, the decoding method corresponding to the subunit includes the decoding or generation method of the HARQ process, such as the decoding or generation method of the PUCCH HARQ process. In some embodiments, the reporting method corresponding to the subunit includes whether to allow reporting segmentation information and / or whether to allow reporting padding information. In some embodiments, the segmentation method corresponding to the subunit includes one or more of the following: whether to perform packet segmentation based on packet (packet boundary), whether to determine the size of the subunit based on packet (packet boundary), and whether to allow non-uniform segmentation. In some embodiments, the padding addition method corresponding to the subunit includes whether to allow adding padding information to the subunit. In some embodiments, the first parameter is equivalent to / can be replaced with LCH information, and the second parameter is equivalent to / can be replaced with subunit information.

[0069] In some embodiments, the second mapping relationship includes a mapping relationship between a third parameter of at least one service data and a second parameter of at least one sub-unit. The third parameter includes at least one of the following: service data identifier, service data index, service data ID, service data priority, service data PBR, service corresponding to the service data, reliable transmission requirement corresponding to the service data, priority transmission requirement corresponding to the service data, whether the service data contains latency-sensitive data, whether the service data contains latency-reporting data, whether the service data uses additional service data priority, importance corresponding to the service data, whether the service data requires a preset (specific) decoding method, and whether the data packet of the service data does not support or is not allowed to be segmented. The second parameter includes at least one of the following: sub-unit identifier, sub-unit sorting, sub-unit index, sub-unit priority, reliable transmission requirement corresponding to the sub-unit, priority transmission requirement corresponding to the sub-unit, importance corresponding to the sub-unit, data transmission type corresponding to the sub-unit, bit error rate guaranteed by the sub-unit, decoding method corresponding to the sub-unit, reporting method corresponding to the sub-unit, segmentation method corresponding to the sub-unit, and padding addition method corresponding to the sub-unit. In some embodiments, the third parameter is equivalent to / can be replaced with service data information, and the second parameter is equivalent to / can be replaced with sub-unit information.

[0070] In some embodiments, the first mapping relationship and / or the second mapping relationship are configured by RRC signaling or indicated by Downlink Control Information (DCI). In some embodiments, the above mapping relationships and mapping restrictions are equivalent to / can be replaced by association relationships.

[0071] In some embodiments, the first mapping relationship and / or the second mapping relationship are jointly indicated by RRC signaling and DCI. If the first mapping relationship and / or the second mapping relationship are jointly indicated by RRC and DCI, the first communication device follows the information configured by the RRC signaling, or follows the information indicated by the DCI, or follows the latest indication information. Alternatively, the initial first mapping relationship and / or the second mapping relationship is configured by RRC signaling, and the changed first mapping relationship and / or the second mapping relationship is indicated by DCI.

[0072] In some embodiments, the first communication device maps LCHs with existing or configured first mapping relationships to sub-units indicated by the first mapping relationship, such as mapping to sub-units that match the LCH; or, multiplexes LCHs with existing or configured first mapping relationships to sub-units indicated by the first mapping relationship, such as multiplexing to sub-units that match the LCH; or, preferentially maps LCHs with existing or configured first mapping relationships to sub-units indicated by the first mapping relationship, such as preferentially mapping to sub-units that match the LCH; or, preferentially multiplexes LCHs with existing or configured first mapping relationships to sub-units indicated by the first mapping relationship, such as preferentially multiplexing to sub-units that match the LCH. In some embodiments, if there are remaining resources in a sub-unit, further, padding bits can be added to the remaining resources, or data or information of other LCHs that do not match the sub-unit can be mapped. In some embodiments, the first communication device maps service data with or configured with a second mapping relationship to the sub-unit indicated by the second mapping relationship, for example, mapping it to a sub-unit that matches the service data; or, multiplexes service data with or configured with a second mapping relationship to the sub-unit indicated by the second mapping relationship, for example, multiplexing it to a sub-unit that matches the service data; or, preferentially maps service data with or configured with a second mapping relationship to the sub-unit indicated by the second mapping relationship, for example, preferentially mapping it to a sub-unit that matches the service data; or, preferentially multiplexes service data with or configured with a second mapping relationship to the sub-unit indicated by the second mapping relationship, for example, preferentially multiplexing it to a sub-unit that matches the service data. In some embodiments, if there are remaining resources in the sub-unit, further, padding bits can be added to the remaining resources, or other service data that does not match the sub-unit can be mapped.

[0073] In some embodiments, the first LCH does not support reuse in sub-units with a first attribute; or, the first LCH supports reuse in sub-units without a first attribute; or, the first LCH does not support priority reuse in sub-units with a first attribute; or, the first LCH supports reuse in any sub-unit. The first LCH includes LCHs that do not exist or are not configured with a first mapping relationship, and the first attribute includes one or more attributes corresponding to the sub-unit. For example, a sub-unit with a first attribute can be understood as a sub-unit with any one or more attributes, or a sub-unit with only the first attribute. A sub-unit without a first attribute can be understood as a sub-unit without any attributes. For example, if an LCH does not exist or is not configured with a first mapping relationship, the LCH cannot be reused in any sub-unit with an attribute, or it can or can only be reused in a sub-unit without an attribute, or it cannot be preferentially reused in any sub-unit with an attribute; or it can be reused in any sub-unit (which may or may not have an attribute), or it can be reused in a sub-unit where there are remaining resources if there are resources in the sub-unit with the attribute.

[0074] In some embodiments, the first service data does not support reuse in sub-units with a first attribute; or, the first service data supports reuse in sub-units without a first attribute; or, the first service data does not support preferential reuse in sub-units with a first attribute; or, the first service data supports reuse in any sub-unit. The first service data includes service data that does not exist or has not been configured with a second mapping relationship, and the first attribute includes one or more attributes corresponding to the sub-unit.

[0075] In some embodiments, the second LCH does not support reuse in sub-units with a second attribute; or, the second LCH supports reuse in sub-units without a second attribute; or, the second LCH does not support preferential reuse in sub-units with a second attribute. The second LCH has or is configured with a first mapping relationship, and the first mapping relationship indicates that the set of sub-units corresponding to the second LCH is 0. The second attribute includes one or more attributes corresponding to the sub-unit. For example, a sub-unit with a second attribute can be understood as a sub-unit with any one or more attributes, or a sub-unit with a second attribute. A sub-unit without a second attribute can be understood as a sub-unit without any attributes. The set of sub-units corresponding to the second LCH includes sub-units that support reuse or mapping of the second LCH; the set of sub-units may be called a configuration set. For example, if the LCH has or is configured with a first mapping relationship, but the configuration set is 0, then the LCH cannot be reused in any sub-unit with an attribute, or it can or can only be reused in a sub-unit without an attribute, or it cannot be preferentially reused in any sub-unit with an attribute, or it can only be reused in a sub-unit with an attribute if there are remaining resources.

[0076] In some embodiments, the second service data does not support multiplexing in sub-units with a second attribute; or, the second service data supports multiplexing in sub-units without a second attribute; or, the second service data does not support preferential multiplexing in sub-units with a second attribute. The second service data has or is configured with a second mapping relationship, and the second mapping relationship indicates that the set of sub-units corresponding to the second service data is 0. The set of sub-units corresponding to the second service data includes sub-units that support multiplexing or mapping the second service data.

[0077] In some embodiments, sub-units with different attributes carry different LCHs or service data; or, sub-units with different attributes preferentially carry different LCHs or service data. In some embodiments, sub-units with the same attributes carry the same LCHs or service data; or, sub-units with the same attributes preferentially carry the same LCHs or service data. In some embodiments, sub-units with different attributes carry different characteristics of LCHs or service data; or, sub-units with different attributes preferentially carry different characteristics of LCHs or service data. In some embodiments, sub-units with the same attributes carry the same characteristics of LCHs or service data; or, sub-units with the same attributes preferentially carry the same characteristics of LCHs or service data. For example, TB1, TB2, and TB3 are multiplexed in one PUSCH or codeword, and the priorities of TB1, TB2, and TB3 are 1, 1, and 2, respectively. For example, CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 are multiplexed in one PUSCH or codeword, with priorities of CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 being 1, 1, and 2, respectively.

[0078] For example, TB1, TB2, and TB3 are multiplexed into a single PUSCH or codeword. The priorities of TB1, TB2, and TB3 are 1, 1, and 2, respectively. The priorities of LCH1 and LCH2 are 1 and 2, respectively. Therefore, LCH1 is multiplexed into either TB1 or TB2, and LCH2 is multiplexed into TB3. For example, TB1, TB2, and TB3 are multiplexed into a single PUSCH or codeword. The reliability of TB1, TB2, and TB3 is 1, 1, and 2, respectively. LCH1 is associated with reliability 1, and LCH2 is associated with reliability 2. Therefore, LCH1 is multiplexed into either TB1 or TB2, and LCH2 is multiplexed into TB3. For example, TB1, TB2, and TB3 are multiplexed into a single PUSCH or codeword. The indices of TB1, TB2, and TB3 are 1, 2, and 3, respectively. The priorities of LCH1 and LCH2 are 1 and 2, respectively. Therefore, LCH1 is multiplexed into either TB1 or TB2, and LCH2 is multiplexed into TB3. For example, TB1, TB2, and TB3 are multiplexed into a single PUSCH or codeword. The indices of TB1, TB2, and TB3 are 1, 2, and 3, respectively. LCH1 is associated with TB1, and LCH2 is associated with TB2. Therefore, LCH1 is multiplexed to either TB1 or TB2, and LCH2 is multiplexed to TB3.

[0079] For example, CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 are multiplexed into a single PUSCH or codeword. The priorities of CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 are 1, 1, and 2, respectively. The priorities of LCH1 and LCH2 are 1 and 2, respectively. Therefore, LCH1 is multiplexed to either CB1 / CBG1 or CB2 / CBG2, and LCH2 is multiplexed to CB3 / CBG3. Alternatively, CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 are multiplexed into a single PUSCH or codeword. The reliability of CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 is 1, 1, and 2, respectively. LCH1 is associated with reliability 1, and LCH2 is associated with reliability 2. Therefore, LCH1 is multiplexed to either CB1 / CBG1 or CB2 / CBG2, and LCH2 is multiplexed to CB3 / CBG3. For example, CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 are multiplexed into a single PUSCH or codeword. The indices of CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 are 1, 2, and 3, respectively. The priorities of LCH1 and LCH2 are 1 and 2, respectively. Therefore, LCH1 is multiplexed to either CB1 / CBG1 or CB2 / CBG2, and LCH2 is multiplexed to CB3 / CBG3. For example, CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 are multiplexed into a single PUSCH or codeword. The indices of CB1 / CBG1, CB2 / CBG2, and CB3 / CBG3 are 1, 2, and 3, respectively. LCH1 is associated with CB1 / CBG1, and LCH2 is associated with CB3 / CBG3. Therefore, LCH1 is multiplexed to either CB1 / CBG1 or CB2 / CBG2, and LCH2 is multiplexed to CB3 / CBG3.

[0080] Segmentation for data packets / subunits:

[0081] In some embodiments, the first communication device reduces segmentation processing of data packets corresponding to sub-units. This can involve two scenarios: one is reducing segmentation processing of data packets corresponding to sub-units during the process of multiplexing / mapping / carrying them to sub-units to avoid segmentation of the data packets carried by the sub-units; the other is reducing segmentation processing of data packets carried by sub-units during the process of multiplexing / mapping / carrying them to data units to avoid segmentation of the data packets carried by the sub-units. In some embodiments, the data packets corresponding to sub-units include data packets that are allowed to carry or support carrying or multiplexing or support multiplexing or are determined to carry or multiplexed in the sub-unit, which are equivalent to SDUs and / or RLC SDUs and / or Packet Data Convergence Protocol (PDCP) SDUs and / or MAC SDUs. In some embodiments, segmentation processing of data packets corresponding to sub-units can also be understood as segmentation processing of sub-units, such as segmentation processing of TB, CB, and CBG. In other embodiments, the data packet segmentation processing corresponding to the sub-unit is a different process than the sub-unit segmentation processing, as detailed below. In some embodiments, the sub-unit segmentation can be uniform or non-uniform. For example, TB segments can be non-uniform or uniform. CB or CBG segments can be non-uniform.

[0082] In some embodiments, when a data unit corresponds to a downlink (DL) transmission, for each sub-unit, the second communication device may indicate at least one of the following: segmentation rules, segment boundaries, number of segments, payload, and size. For example, payload or size may be indicated.

[0083] In some embodiments, when a data unit corresponds to an uplink (UL) transmission, for each sub-unit, the second communication device may indicate at least one of the following: segmentation rules, segment boundaries, number of segments, payload, size, MCS, and number of available resource blocks (RBs); and / or, for a data unit, the second communication device may indicate at least one of the following: payload, size, MCS, and number of available RBs. For example, indicating the size of a data unit and indicating the segmentation rules. For example, indicating the size of a data unit and indicating the segmentation rules. For example, indicating the size of a data unit and indicating the number of segments. For example, indicating the size of a data unit and indicating the size of each sub-unit. For example, indicating the segmentation rules for each sub-unit, indicating the size of each sub-unit, and indicating the number of sub-units. For example, indicating the size of each sub-unit and indicating the number of sub-units.

[0084] (1) In some embodiments, the first communication device segments the data packets corresponding to all or some of the sub-units in at least two sub-units based on data packet boundaries, and / or determines the data packets carried or multiplexed by all or some of the sub-units in at least two sub-units based on data packet boundaries, and / or segments or divides all or some of the sub-units in at least two sub-units based on data packet boundaries, and / or the first communication device determines the data packet boundary or determines the sub-units to which one or more data packets are multiplexed based on the boundaries of all or some of the sub-units in at least two sub-units. The data packet boundary includes the boundary of the data packet corresponding to the sub-unit, and can also be understood as the size of the data packet. In some embodiments, the data packet boundary is used to avoid the data packets carried by all or some of the sub-units being segmented.

[0085] It should be noted that, for scenarios where the data packets corresponding to a subunit are multiplexed into subunits, the above four methods can be equivalent. For scenarios where subunits are multiplexed into data units, the above-mentioned "segmenting or dividing all or part of the subunits in at least two subunits based on data packet boundaries" is involved.

[0086] In some embodiments, during the process of multiplexing data packets corresponding to a subunit to the subunit, such as during the process of segmenting data packets corresponding to all or part of the subunits in at least two subunits based on data packet boundaries, the first communication device determines the boundary of the subunit as the boundary of the subunit for multiplexing one or more corresponding data packets, or as the boundary of one or more corresponding data packets, that is, a data packet can only be placed in one subunit. In some embodiments, during the process of multiplexing data packets corresponding to a subunit to the subunit, after the first communication device multiplexes the i-th data packet corresponding to the subunit to the subunit, if the boundary of the (i+1)-th data packet exceeds the boundary of the subunit, for example, the size of the (i+1)-th data packet is greater than the remaining space of the subunit, then the first communication device will not multiplex the (i+1)-th data packet to the subunit. Here, i is a positive integer. In this case, the first communication device can multiplex data packets other than the (i+1)-th data packet to the subunit, or multiplex a portion of data packets other than the (i+1)-th data packet to the subunit.

[0087] In some embodiments, during the process of multiplexing a subunit to a data unit, such as during the segmentation or division of all or part of the subunits in at least two subunits based on data packet boundaries, the first communication device segments or divides the subunits according to the data packet boundaries of the data packets carried by the subunits, to ensure that the position of the subunit segmentation or division is aligned with or consistent with the data packet boundaries of the data packets carried by the subunits. In some embodiments, the data packet includes an SDU or an SDU segment. In some embodiments, the SDU includes one or more of RLC SDU, PDCP SDU, and MAC SDU. SDU segmentation is obtained by segmenting, dividing, or dividing the SDU. In some embodiments, the data packet boundary is the boundary of the SDU or the boundary of the SDU segment. The boundary of the SDU segment is the boundary of the segment obtained by segmenting, dividing, or dividing the SDU. For example, if a subunit carries data packet 1 and data packet 2, during the process of segmenting or dividing the subunit, the first communication device will segment or divide the subunit according to the data packet boundaries of data packet 1 and / or data packet 2 to avoid the data packets carried by the subunit being divided due to the segmentation or division of the subunit.

[0088] In some embodiments, all or part of the subunits in at least two subunits are obtained by segmenting based on data packet boundaries. By segmenting according to data packet boundaries during the process of obtaining subunits, packet fragmentation can be avoided. In some embodiments, the data packet boundary is the boundary of the SDU or the boundary of an SDU segment.

[0089] In some embodiments, the first communication device segments data packets corresponding to sub-units with the same attributes in at least two sub-units based on data packet boundaries, and / or determines data packets carried or multiplexed by sub-units with the same attributes in at least two sub-units based on data packet boundaries, and / or segments or divides sub-units with the same attributes in at least two sub-units based on data packet boundaries, and / or determines data packet boundaries or determines sub-units to which one or more data packets are multiplexed based on the boundaries of sub-units with the same attributes in at least two sub-units.

[0090] In some embodiments, the first communication device segments the data packets corresponding to the first X sub-units in at least two sub-units based on data packet boundaries, and / or determines the data packets carried or multiplexed by the first X sub-units in at least two sub-units based on data packet boundaries, and / or segments or divides the first X sub-units in at least two sub-units based on data packet boundaries, and / or determines the data packet boundaries or determines the sub-units to which one or more data packets are multiplexed based on the boundaries of the first X sub-units in at least two sub-units. Here, X is a positive integer. X can be configured, indicated, or predefined by the communication protocol; for example, X is N-1, where N is the total number of sub-units in the at least two sub-units.

[0091] In some embodiments, the first communication device adds padding bits to all or some of the sub-units in at least two sub-units. Padding bits are equivalent to padding. In some embodiments, padding bits are used to prevent the data packets carried by all or some of the sub-units from being segmented.

[0092] In some embodiments, the first communication device sends padding information carried by at least two sub-units. For example, the first communication device sends the aforementioned information to the second communication device. This information is sent via MAC CE, but can also be replaced by Uplink Control Information (UCI), PUCCH, or RRC signaling.

[0093] For specific methods of filling in and / or reporting, please refer to (3) below.

[0094] (2) In some embodiments, the first communication device determines the size information of all or part of the sub-units in at least two sub-units based on the data packet boundary, and / or determines the amount of data carried by all or part of the sub-units in at least two sub-units based on the data packet boundary. The data packet boundary includes the boundary of the data packet corresponding to the sub-unit. In some embodiments, the data packet boundary is used to prevent the data packets carried by all or part of the sub-units from being segmented.

[0095] In some embodiments, the first communication device determines, based on packet boundaries, all or part of the data packets carried or multiplexed by at least two sub-units, thereby determining the size information of the sub-unit and / or the amount of data carried by the sub-unit based on the data packets carried or multiplexed by the sub-unit. The process of determining the data packets carried or multiplexed by the sub-unit can be found in the relevant content of this embodiment, and will not be elaborated upon here.

[0096] In some embodiments, the first communication device determines the size information of sub-units with the same attributes in at least two sub-units based on the packet boundary, and / or determines the amount of data carried by the sub-units with the same attributes in at least two sub-units based on the packet boundary.

[0097] In some embodiments, the first communication device determines the size information of the first Y sub-units in at least two sub-units based on the packet boundary, and / or determines the amount of data carried by the first Y sub-units in at least two sub-units based on the packet boundary, where Y is a positive integer. Y can be configured, indicated, or predefined by the communication protocol. X and Y can be the same or different.

[0098] In some embodiments, the first communication device sends segmentation information of data packets carried by at least two sub-units, and / or sends information on the amount of data carried by at least two sub-units, and / or sends information on the size of at least two sub-units. For example, the first communication device sends the above information to a second communication device. In some embodiments, the segmentation information is used to indicate how the data packets corresponding to all or some of the sub-units in the at least two sub-units are segmented. In some embodiments, the above information is sent via a MAC control element (CE). In some embodiments, the MAC CE can be used to indicate whether each sub-unit performs non-uniform segmentation to ensure that the data packet boundary is not segmented by the sub-unit boundary. The MAC CE can carry the index of each sub-unit and information on how the sub-unit corresponding to the index is segmented. Alternatively, the MAC CE can carry a sub-unit bitmap to indicate whether non-uniform segmentation is performed based on the position of the bitmap for each sub-unit. In some embodiments, the MAC CE is used to indicate the size and / or segmentation information of each sub-unit to ensure that the data packet boundary is not segmented by the sub-unit boundary. The MAC CE can carry an index of each sub-cell and the size and / or segmentation information of the corresponding sub-cell. Alternatively, the MAC CE can carry a sub-cell bitmap, indicating the size and / or segmentation information of the sub-cell based on the position of the bitmap for each sub-cell. In some embodiments, the MAC CE described above can also be replaced with Uplink Control Information (UCI), PUCCH, or RRC signaling.

[0099] In some embodiments, the second communication device indicates or configures the payload (P) of the data unit. The first communication device determines the size of each sub-unit and reports the sub-unit size information via the MAC CE. Each sub-unit carries a complete data packet without data packet fragmentation due to sub-unit size limitations (i.e., causing a data packet to be placed in different sub-units). The sum of the sub-unit sizes of each sub-unit is less than or equal to P. That is, the data volume of at least two sub-units is less than or equal to the data volume of the data unit; or, the size of at least two sub-units is less than or equal to the size of the data unit. In some embodiments, the size of the sub-unit can be determined by the MAC entity and / or physical (PHY) layer.

[0100] (3) In some embodiments, the first communication device adds padding bits to all or some of the sub-units in at least two sub-units. Padding bits are equivalent to padding. In some embodiments, padding bits are used to prevent the data packets carried by all or some of the sub-units from being segmented.

[0101] In some embodiments, during the process of multiplexing data packets corresponding to a subunit to the subunit, after the first communication device multiplexes the i-th data packet corresponding to the subunit to the subunit, if the boundary of the (i+1)-th data packet exceeds the boundary of the subunit (for example, the size of the (i+1)-th data packet is greater than the remaining space of the subunit), the first communication device adds padding bits to the remaining space of the subunit to avoid the (i+1)-th data packet being segmented due to multiplexing it to the subunit. In this case, the first communication device can multiplex data packets other than the (i+1)-th data packet to the subunit, or multiplex a portion of the data packets other than the (i+1)-th data packet to the subunit.

[0102] In some embodiments, the first communication device adds padding bits to the first sub-unit based on the amount of data corresponding to the first sub-unit among at least two sub-units; or, based on the size of the first sub-unit among at least two sub-units. The amount of data corresponding to the first sub-unit is determined by the first communication device or by the second communication device, and the size of the first sub-unit is determined by the first communication device or by the second communication device. For example, the first communication device may determine, configure, or indicate the amount of data corresponding to each sub-unit or the size of each sub-unit, such as TB size (TBS), CB size, or CBG size. The second communication device may determine, configure, or indicate the amount of data corresponding to each sub-unit or the size of each sub-unit, such as TBS, CB size, or CBG size. The amount of data or the size corresponding to each sub-unit may be explicitly indicated or implicitly indicated; the indication method can be referred to the relevant content above and will not be repeated here.

[0103] In some embodiments, the amount of data corresponding to the sub-unit determined, configured, or indicated by the first communication device is less than or equal to the amount of data corresponding to the sub-unit determined, configured, or indicated by the second communication device, or the size of the sub-unit determined, configured, or indicated by the first communication device is less than or equal to the size of the sub-unit determined, configured, or indicated by the second communication device.

[0104] In some embodiments, when the first data amount corresponding to the first subunit is less than the second data amount corresponding to the first subunit, the first communication device adds padding bits to the first subunit; or, when the first size corresponding to the first subunit is less than the second size corresponding to the first subunit, the first communication device adds padding bits to the first subunit. The first data amount is determined by the first communication device, and the second data amount is determined by the second communication device; or, the first data amount is the data amount or sum of data amounts that are allowed to carry or support carrying or multiplexing or multiplexing data packets in the first subunit, or the data amount or sum of data amounts that are allowed to carry or support carrying or multiplexing ...

[0105] For example, the first communication device assembles packets for each sub-unit. If the size of the sub-unit does not match the size of the complete data packet (including the header), then the complete data packet cannot be placed in the sub-unit; instead, padding bits are added to the remaining bit positions of the sub-unit. For instance, if the size of the sub-unit is less than or equal to the total size of the reusable data packet, padding bits are added to the sub-unit to avoid data packet fragmentation.

[0106] In some embodiments, the first communication device adds padding bits to all or some of the first Z sub-units in at least two sub-units, where Z is a positive integer. Z can be configured, indicated, or predefined by the communication protocol. X and Y can be the same as Z, partially the same, or different.

[0107] In some embodiments, the first communication device sends padding information, such as sending padding information to the second communication device. In some embodiments, the padding information is used to indicate whether padding bits are added to the sub-unit and / or the bit length (size) of the added padding bits, to ensure that the data packet boundary is not segmented by the sub-unit boundary. In some embodiments, the padding information is sent via a MAC CE, for example, when the data unit corresponds to uplink (UL) transmission. In some embodiments, a MAC CE can correspond to padding information for one sub-unit or to padding information for each sub-unit. For example, a MAC CE can correspond to a sub-unit identifier, a sub-unit list, or a sub-unit bitmap. In some embodiments, when a MAC CE corresponds to one sub-unit, the first communication device can send (carry) multiple MAC CEs when sending padding information, with each MAC CE corresponding to a different sub-unit. For example, a MAC CE can carry the index of each sub-unit and the padding information of the sub-unit corresponding to that index. Alternatively, the MAC CE can carry a sub-cell bitmap, indicating padding information for the position of the bitmap for each sub-cell. In some embodiments, the MAC CE described above can also be replaced with UCI, PUCCH, or RRC signaling.

[0108] For example, the second communication device implicitly or explicitly indicates the size of each sub-unit. When the first communication device assembles packets for each sub-unit, it multiplexes the data packets within the sub-unit. If the remaining space in the sub-unit is insufficient to carry the complete next data packet, it adds padding bits to the remaining space. The first communication device notifies the second communication device of the padding bit information.

[0109] In some embodiments, the first communication device performs packet assembly, invokes a multiplexing packet assembly entity, or generates a MAC PDU for each sub-unit.

[0110] In summary, the method provided in this embodiment, by multiplexing at least two sub-units into the same data unit and / or transmitting at least two sub-units through the same data unit, enables the carrying of data from sub-units corresponding to different services through the same data unit, thereby reducing scheduling signaling overhead and transmission latency.

[0111] The method provided in this embodiment also reduces the segmentation of data packets by processing each sub-unit individually when supporting the recovery of the whole data from partial data. This allows the receiving end to recover the whole data information by receiving partial data packets, thereby avoiding delays and reducing redundant transmission.

[0112] Figure 3 is a flowchart of a data transmission method provided in an exemplary embodiment of this application. The method can be executed by a second communication device. The second communication device can be a network device. In other embodiments, the second communication device can be a terminal device. In implementation, the method can be executed by a MAC entity, for example, by a second MAC entity of the second communication device. The method includes:

[0113] Step 302: Receive a data unit, wherein the data unit multiplexes at least two sub-units, or at least two sub-units are transmitted through the data unit.

[0114] At least two sub-units are multiplexed into the same data unit. This can also be understood as at least two sub-units being packetized or packaged into the same data unit, or as data corresponding to at least two sub-units being carried or transmitted through the same data unit, or as PDUs (such as MAC PDUs) corresponding to at least two sub-units being carried or transmitted through the same data unit. The data unit includes at least two sub-units, or it can be understood that the data unit includes multiple sub-units. In some embodiments, at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to the same service or logical channel or information. In some embodiments, the data unit corresponds to uplink data or uplink transmission. In other embodiments, the data unit corresponds to downlink data or downlink transmission.

[0115] In some embodiments, one of the at least two sub-units is one of TB, CB, CBG, sub-data channel, HARQ process, HARQ sub-process, and CW. In some embodiments, the data unit is one of DG resource, CG resource, PUSCH, CW, TB, data channel, and HARQ process.

[0116] In some embodiments, all or some of the subunits in at least two subunits have attributes. The attributes of a subunit are equivalent to / can be replaced by the features of the subunit. In some embodiments, at least two subunits have the same attribute; or, at least two subunits have different attributes; or, some subunits in at least two subunits have the same attribute, and the subunits other than those have different attributes. In some embodiments, the attributes of a subunit include one or more of the following: subunit identifier; subunit order; subunit index; subunit priority; reliable transmission requirement corresponding to the subunit; priority transmission requirement corresponding to the subunit; importance corresponding to the subunit; data transmission type corresponding to the subunit; guaranteed bit error rate of the subunit; decoding method corresponding to the subunit; reporting method corresponding to the subunit; segmentation method corresponding to the subunit; padding and addition method corresponding to the subunit.

[0117] It should be noted that the description of data units and sub-units can be found in other embodiments of this application, and will not be repeated here.

[0118] In some embodiments, different sub-units within at least two sub-units multiplex different LCHs or different service data, or, different sub-units within at least two sub-units are used to transmit different LCHs or different service data. In some embodiments, identical sub-units within at least two sub-units multiplex different LCHs or different service data, or, identical sub-units within at least two sub-units are used to transmit different LCHs or different service data. In some embodiments, different LCHs are multiplexed to different sub-units within at least two sub-units based on a first mapping relationship; or, different service data are multiplexed to different sub-units within at least two sub-units based on a second mapping relationship. The first mapping relationship includes a mapping relationship and / or mapping restrictions between at least one LCH and at least one sub-unit, and the second mapping relationship includes a mapping relationship and / or mapping restrictions between at least one service data and at least one sub-unit.

[0119] In some embodiments, sub-units with different attributes carry different LCH or service data; or, sub-units with different attributes preferentially carry different LCH or service data. In some embodiments, sub-units with the same attributes carry the same LCH or service data; or, sub-units with the same attributes preferentially carry the same LCH or service data. In some embodiments, sub-units with different attributes carry different characteristics of LCH or service data; or, sub-units with different attributes preferentially carry different characteristics of LCH or service data. In some embodiments, sub-units with the same attributes carry the same characteristics of LCH or service data; or, sub-units with the same attributes preferentially carry the same characteristics of LCH or service data.

[0120] It should be noted that for the introduction of sub-unit multiplexing of LCH / service data, please refer to the relevant content in other embodiments of this application, and will not be repeated here.

[0121] In some embodiments, data packets corresponding to all or some of the sub-units in at least two sub-units are segmented based on data packet boundaries, and / or, data packets carried or multiplexed by all or some of the sub-units in at least two sub-units are determined based on data packet boundaries, and / or, all or some of the sub-units in at least two sub-units are segmented or divided based on data packet boundaries, and / or, data packet boundaries or the sub-units to which one or more data packets are multiplexed are determined based on the boundaries of all or some of the sub-units in at least two sub-units. In some embodiments, data packet boundaries are used to prevent data packets carried by all or some of the sub-units from being segmented.

[0122] In some embodiments, the size information of all or some of the sub-units in at least two sub-units is determined based on packet boundaries, and / or, the information on the amount of data carried by all or some of the sub-units in at least two sub-units is determined based on packet boundaries. In some embodiments, packet boundaries are used to prevent the data packets carried by all or some of the sub-units from being segmented.

[0123] In some embodiments, the second communication device receives segmentation information of data packets carried by at least two sub-units, and / or receives information on the amount of data carried by at least two sub-units, and / or receives size information of at least two sub-units.

[0124] In some embodiments, padding bits are added to all or some of the sub-units in at least two sub-units. In some embodiments, the padding bits are used to prevent the data packets carried by all or some of the sub-units from being segmented. In some embodiments, a second communication device receives padding information for the padding bits.

[0125] It should be noted that for an introduction to data packet segmentation, please refer to the relevant content in other embodiments of this application, and will not be repeated here.

[0126] In summary, the method provided in this embodiment, by multiplexing at least two sub-units into the same data unit and / or transmitting at least two sub-units through the same data unit, enables the carrying of data from sub-units corresponding to different services through the same data unit, thereby reducing scheduling signaling overhead and transmission latency.

[0127] The method provided in this embodiment also reduces the segmentation of data packets by processing each sub-unit individually when supporting the recovery of the whole data from partial data. This allows the receiving end to recover the whole data information by receiving partial data packets, thereby avoiding delays and reducing redundant transmission.

[0128] Figure 4 is a flowchart of a data transmission method provided in an exemplary embodiment of this application. This method can be used in the system shown in Figure 1. The method includes:

[0129] Step 402: The first communication device multiplexes at least two sub-units into the same data unit.

[0130] At least two sub-units are multiplexed into the same data unit. This can also be understood as at least two sub-units being packetized or packaged into the same data unit, or as data corresponding to at least two sub-units being carried or transmitted through the same data unit, or as PDUs (such as MAC PDUs) corresponding to at least two sub-units being carried or transmitted through the same data unit. The data unit includes at least two sub-units, or it can be understood that the data unit includes multiple sub-units. In some embodiments, at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to the same service or logical channel or information. In some embodiments, the data unit corresponds to uplink data or uplink transmission. In other embodiments, the data unit corresponds to downlink data or downlink transmission.

[0131] In some embodiments, one of the at least two sub-units is one of TB, CB, CBG, sub-data channel, HARQ process, HARQ sub-process, and CW. In some embodiments, the data unit is one of DG resource, CG resource, PUSCH, CW, TB, data channel, and HARQ process.

[0132] In some embodiments, all or some of the subunits in at least two subunits have attributes. The attributes of a subunit are equivalent to / can be replaced by the features of the subunit. In some embodiments, at least two subunits have the same attribute; or, at least two subunits have different attributes; or, some subunits in at least two subunits have the same attribute, and the subunits other than those have different attributes. In some embodiments, the attributes of a subunit include one or more of the following: subunit identifier; subunit order; subunit index; subunit priority; reliable transmission requirement corresponding to the subunit; priority transmission requirement corresponding to the subunit; importance corresponding to the subunit; data transmission type corresponding to the subunit; guaranteed bit error rate of the subunit; decoding method corresponding to the subunit; reporting method corresponding to the subunit; segmentation method corresponding to the subunit; padding and addition method corresponding to the subunit.

[0133] It should be noted that the description of data units and sub-units can be found in other embodiments of this application, and will not be repeated here.

[0134] In some embodiments, the first communication device multiplexes different LCHs or different service data into different sub-units of at least two sub-units, or transmits different LCHs or different service data through different sub-units of at least two sub-units. In some embodiments, the first communication device may also multiplex different LCHs or different service data into the same sub-unit of at least two sub-units, or transmit different LCHs or different service data through the same sub-unit of at least two sub-units.

[0135] In some embodiments, the first communication device multiplexes different LCHs to different sub-units of at least two sub-units according to a first mapping relationship; or, multiplexes different service data to different sub-units of at least two sub-units according to a second mapping relationship; or, transmits different LCHs through different sub-units of at least two sub-units according to the first mapping relationship; or, transmits different service data through different sub-units of at least two sub-units according to the second mapping relationship. The first mapping relationship includes a mapping relationship and / or mapping restrictions between at least one LCH and at least one sub-unit, and the second mapping relationship includes a mapping relationship and / or mapping restrictions between at least one service data and at least one sub-unit.

[0136] In some embodiments, sub-units with different attributes carry different LCH or service data; or, sub-units with different attributes preferentially carry different LCH or service data. In some embodiments, sub-units with the same attributes carry the same LCH or service data; or, sub-units with the same attributes preferentially carry the same LCH or service data. In some embodiments, sub-units with different attributes carry different characteristics of LCH or service data; or, sub-units with different attributes preferentially carry different characteristics of LCH or service data. In some embodiments, sub-units with the same attributes carry the same characteristics of LCH or service data; or, sub-units with the same attributes preferentially carry the same characteristics of LCH or service data.

[0137] It should be noted that for the introduction of sub-unit multiplexing of LCH / service data, please refer to the relevant content in other embodiments of this application, and will not be repeated here.

[0138] In some embodiments, the first communication device segments data packets corresponding to all or some of the sub-units in at least two sub-units based on data packet boundaries, and / or determines data packets carried or multiplexed by all or some of the sub-units in at least two sub-units based on data packet boundaries, and / or segments or divides all or some of the sub-units in at least two sub-units based on data packet boundaries, and / or determines data packet boundaries or determines sub-units where one or more data packets are multiplexed based on the boundaries of all or some of the sub-units in at least two sub-units. In some embodiments, data packet boundaries are used to prevent data packets carried by all or some sub-units from being segmented.

[0139] In some embodiments, the first communication device determines the size information of all or some of the sub-units in at least two sub-units based on the packet boundary, and / or determines the amount of data carried by all or some of the sub-units in at least two sub-units based on the packet boundary. In some embodiments, the packet boundary is used to prevent the data packets carried by all or some of the sub-units from being segmented.

[0140] In some embodiments, the first communication device sends segmentation information of data packets carried by at least two sub-units, and / or sends information on the amount of data carried by at least two sub-units, and / or sends size information of at least two sub-units.

[0141] In some embodiments, the first communication device adds padding bits to all or some of the sub-units in at least two sub-units. In some embodiments, the padding bits are used to prevent the data packets carried by all or some of the sub-units from being segmented. In some embodiments, the first communication device sends padding information, for example, to a second communication device.

[0142] It should be noted that for an introduction to data packet segmentation, please refer to the relevant content in other embodiments of this application, and will not be repeated here.

[0143] Step 404: The first communication device sends a data unit to the second communication device.

[0144] By multiplexing at least two sub-units into the same data unit, the first communication device can obtain a completed data unit packet, thereby sending the data unit to the second communication device. In some embodiments, the first communication device can transmit / retransmit the data unit to the second communication device, or it can transmit / retransmit sub-units of the data unit to the second communication device; this application does not limit this.

[0145] In this embodiment, steps 402 and 404 are optional. In different embodiments, one of these steps may be omitted or substituted.

[0146] Step 402 can be implemented as a standalone embodiment, such as a data packet assembly method on the first communication device side. Step 404 can be implemented as a standalone embodiment, such as a data transmission method on the first communication device side or a data reception method on the second communication device side.

[0147] In summary, the method provided in this embodiment, by multiplexing at least two sub-units into the same data unit and / or transmitting at least two sub-units through the same data unit, enables the carrying of data from sub-units corresponding to different services through the same data unit, thereby reducing scheduling signaling overhead and transmission latency.

[0148] The method provided in this embodiment also reduces the segmentation of data packets by processing each sub-unit individually when supporting the recovery of the whole data from partial data. This allows the receiving end to recover the whole data information by receiving partial data packets, thereby avoiding delays and reducing redundant transmission.

[0149] It should be noted that the order of the method steps provided in the embodiments of this application can be appropriately adjusted, and the steps can be added or removed as appropriate. Furthermore, different steps can be freely combined to form new embodiments. Any variations that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application, and therefore will not be elaborated further. In addition, the order of the different situations described above does not have a preferred meaning, but is only for ease of description.

[0150] It should be noted that the method provided in this application can be used for at least one of uplink transmission, downlink transmission and sidelink transmission, and is not limited to the scenarios listed above.

[0151] Taking the method provided in this application for transmitting PUSCH as an example, Figure 5 is a flowchart of a PUSCH transmission method provided in an exemplary embodiment of this application. As shown in Figure 5, the method includes:

[0152] Step 502: The network device sends DCI to the terminal device.

[0153] DCI is used to indicate a first mapping relationship. In some embodiments, the first mapping relationship includes a mapping relationship between a first parameter of at least one LCH and a second parameter of at least one subunit.

[0154] Of course, in other cases, the first relationship can also be indicated by RRC configuration or other signaling.

[0155] In some embodiments, the first parameter includes at least one of the following: LCH identifier, LCH index, LCH ID, LCH priority, LCH PBR, LCH corresponding service, LCH corresponding reliable transmission requirement, LCH corresponding priority transmission requirement, whether the LCH contains delay-sensitive data, whether the LCH contains delay report data, whether the LCH uses additional LCH priority, LCH corresponding importance, whether the LCH requires a preset (specific) decoding method, and whether the LCH data packets do not support or allow segmented transmission. The second parameter includes at least one of the following: sub-unit identifier, sub-unit sorting, sub-unit index, sub-unit priority, sub-unit corresponding reliable transmission requirement, sub-unit corresponding priority transmission requirement, sub-unit corresponding importance, sub-unit corresponding data transmission type, sub-unit guaranteed bit error rate, sub-unit corresponding decoding method, sub-unit corresponding reporting method, sub-unit corresponding segmentation method, and sub-unit corresponding padding method.

[0156] For example, Figure 6 is a schematic diagram of a DCI provided in an exemplary embodiment of this application. As shown in Figure 6, DCI 601 indicates that sub-unit priority 1 is associated with LCH priority 1, and sub-unit priority 2 is associated with LCH priority 2. The priorities of sub-unit 1, sub-unit 2, and sub-unit 3 are 1, 1, and 2, respectively. The priorities of LCH1, LCH2, and LCH3 are 1, 2, and 2, respectively. Then LCH1 can be reused to sub-unit 1 or sub-unit 2, and LCH2 and LCH3 can be reused to sub-unit 3.

[0157] Step 504: The terminal device multiplexes at least two sub-units into the same data unit.

[0158] In this embodiment, the data unit can be a PUSCH. During the process of multiplexing at least two sub-units into the same data unit, the terminal device determines the sub-units of each LCH multiplexing according to the first mapping relationship.

[0159] Based on the mapping relationship between at least two sub-units and LCH determined in the above manner, in the process of multiplexing LCH to at least two sub-units, the terminal device may segment the SDU corresponding to all or part of the sub-units in the at least two sub-units based on the SDU boundary, and / or add padding bits to all or part of the sub-units in the at least two sub-units.

[0160] For example, Figure 7 is a schematic diagram of SDU segmentation provided in an exemplary embodiment of this application. As shown in Figure 7, the data size of SDU1 corresponding to LCH2 is 5 bits, the data size of SDU2 corresponding to LCH3 is 3 bits, and the size of sub-unit 3 is 7 bits. During the process of multiplexing LCHs in sub-units, if SDU2 is multiplexed to sub-unit 3, it will cause SDU2 to be segmented. For example, 2 bits of SDU2 data may be multiplexed to sub-unit 3, and the remaining 1 bit of SDU2 data may be multiplexed to other sub-units. In this case, the terminal device will not multiplex SDU2 to sub-unit 3, thus avoiding the segmentation of SDU2.

[0161] For example, Figure 8 is a schematic diagram of adding padding bits according to an exemplary embodiment of this application. As shown in Figure 8, the data size of SDU1 corresponding to LCH2 is 5 bits, the data size of SDU2 corresponding to LCH3 is 3 bits, and the size of sub-unit 3 is 7 bits. During the multiplexing of LCHs within sub-units, if SDU2 is multiplexed to sub-unit 3, it will cause SDU2 to be split. For example, 2 bits of SDU2 data may be multiplexed to sub-unit 3, and the remaining 1 bit of SDU2 data may be multiplexed to other sub-units. In this case, the terminal device will add padding bits to the remaining 2 bits after SDU1 is multiplexed in sub-unit 3 to prevent SDU2 from being multiplexed to sub-unit 3 and thus causing SDU2 to be split.

[0162] Step 506: The terminal device sends a PUSCH to the network device.

[0163] The first communication device can generate a MAC PDU for each sub-unit by multiplexing the LCH in at least two sub-units, and use this to determine the PUSCH data. After determining the PUSCH data, the terminal device will send the PUSCH to the network device according to the transmission resources corresponding to the PUSCH.

[0164] It should be noted that the above content in this embodiment is only used to illustrate the method provided in this application and is not intended to limit the method provided in this application.

[0165] In summary, the method provided in this embodiment, by multiplexing at least two sub-units into the same data unit and / or transmitting at least two sub-units through the same data unit, enables the carrying of data from sub-units corresponding to different services through the same data unit, thereby reducing scheduling signaling overhead and transmission latency.

[0166] The method provided in this embodiment also reduces the segmentation of data packets by processing each sub-unit individually when supporting the recovery of the whole data from partial data. This allows the receiving end to recover the whole data information by receiving partial data packets, thereby avoiding delays and reducing redundant transmission.

[0167] Taking the method provided in this application for determining the size of a sub-cell as an example, Figure 9 is a flowchart of a method for determining the size of a sub-cell provided in an exemplary embodiment of this application. As shown in Figure 9, the method includes:

[0168] Step 902: The network device sends DCI to the terminal device.

[0169] DCI is used to indicate a first mapping relationship. In some embodiments, the first mapping relationship includes a mapping relationship between a first parameter of at least one LCH and a second parameter of at least one subunit. Of course, in other cases, RRC configuration or other signaling can also be used to indicate the first relationship.

[0170] Step 904: The terminal device determines the sub-unit size based on the SDU size.

[0171] In determining the size of all or part of the sub-units in at least two sub-units, for example, in determining the size of each sub-unit in at least two sub-units, the terminal device determines the sub-units for each LCH multiplexed according to the first mapping relationship. Thus, the sub-unit size is determined based on the SDU size corresponding to the LCH multiplexed in the sub-unit. For the multiplexing of LCHs and the segmentation of SDUs / sub-units involved in this process, please refer to the relevant content in other embodiments of this application. It will not be elaborated upon here.

[0172] For example, FIG10 is a schematic diagram of a sub-unit provided in an exemplary embodiment of this application. As shown in FIG10, the terminal device determines that LCH1, LCH2 and LCH3 are multiplexed in sub-unit 1, with LCH1 corresponding to SDU1, LCH2 corresponding to SDU2, and LCH3 corresponding to SDU3. SDU1 has a size of 5 bits, SDU2 has a size of 3 bits, and SDU3 has a size of 3 bits. In this case, the terminal device determines that the size of sub-unit 1 is 11 bits.

[0173] Step 906: The terminal device sends the sub-cell size to the network device.

[0174] After determining the size of a sub-unit, the terminal device will report the sub-unit size to the network device. For example, it can report the size for all sub-units or for different sub-units.

[0175] It should be noted that the above content in this embodiment is only used to illustrate the method provided by this application and is not intended to limit the method provided by this application. Step 906 may be an optional step.

[0176] In summary, the method provided in this embodiment, by determining the size of the sub-unit, enables the multiplexing of at least two sub-units into the same data unit, and / or the transmission of at least two sub-units through the same data unit. This allows the same data unit to carry data from sub-units corresponding to different services, thereby reducing scheduling signaling overhead and transmission latency.

[0177] The method provided in this application embodiment can include the following two implementation methods:

[0178] 1. Multiple TBs can be reused on a single resource, codeword, or HARQ process;

[0179] 2. Multiple CB / CBGs correspond to one resource, one codeword, one TB, or one HARQ process. Furthermore, CB / CBG segmentation is performed / determined based on packet / SDU boundaries.

[0180] In cases where multiple units (sub-units, such as TB, CB, or CBG) reuse a single resource, codeword, HARQ process, or TB.

[0181] The following may include at least one of the following:

[0182] ● Different services or LCHs are multiplexed into different units.

[0183] ■Optionally, the unit has attributes or characteristics.

[0184] ■Optionally, different services / LCHs can be mapped to different units (such as TB, CW, CB, or CBG).

[0185] ■Optionally, specifically, mapping restrictions or mapping relationships between LCH and units can be introduced, or mapping restrictions or mapping relationships between services and units.

[0186] ◆For example, the mapping relationship can be a mapping configuration or restriction between LCH and cell information.

[0187] ●LCH may include at least one of the following: identifier, index, ID, priority, PBR, corresponding service, corresponding reliable transmission requirement, corresponding priority transmission requirement, and corresponding importance.

[0188] ● Unit information may include at least one of the following: identifier, sorting, index, priority, corresponding reliable transmission requirement, corresponding priority transmission requirement, corresponding importance, guaranteed bit error rate, etc.

[0189] ◆For example: An LCH that has a mapping constraint or mapping relationship between an LCH and a cell can be mapped, reused, preferentially mapped, or preferentially reused to a cell that matches the mapping relationship.

[0190] ◆For example, if the LCH is not configured with mapping restrictions or mapping relationships between the LCH and the cell, the LCH cannot be reused in any cell with an attribute, or can only be reused in cells without an attribute, or cannot be preferentially reused in any cell with an attribute; or, it can be reused in any cell (which may or may not have an attribute).

[0191] ◆For example, if there is a mapping restriction or mapping relationship configuration between LCH and cell, but the configuration set is 0, then the LCH cannot be reused in any cell with an attribute, or can only be reused in cells without an attribute, or cannot be preferentially reused in any cell with an attribute.

[0192] ● Each unit has its own attributes / characteristics.

[0193] ■ Different units may have the same or different attributes / characteristics.

[0194] ■ The unit has an identifier or attribute or feature. Specifically, it can be at least one of the following: identifier, sorting, index, priority, corresponding reliable transmission requirement, corresponding priority transmission requirement, corresponding importance, and guaranteed bit error rate.

[0195] ■Optionally, units with different identifiers, attributes, or characteristics may carry different LCHs or services, or the LCHs or services that are preferentially carried may be different.

[0196] ■Optionally, units with the same identifier, attribute, or characteristic may carry the same LCH or service, or the LCH or service that is preferentially carried may be the same.

[0197] ● For units with the same attributes / features, reduce segmentation processing, or segment based on packet boundaries.

[0198] ■ Perform TB / CB / CBG segmentation, and / or perform TB / CB / CBG segmentation based on packet boundaries, and / or send segmentation information to the peer entity.

[0199] ◆TB segments can be non-uniform or uniform.

[0200] ◆The CB / CBG segment is non-uniform.

[0201] ◆Optionally, the base station determines / configures / indicates the total size of all the units, such as TBS, CB size, CBG size, etc.

[0202] ◆Optionally, the UE determines / configures / indicates information for each unit, such as size (e.g., TBS, CB size, CBG size, etc.), and TB / CB / CBG segmentation (to avoid SDU / data packets being segmented).

[0203] ◆Optionally, at least the first X units of the plurality of units are targeted to avoid SDU segmentation. Optionally, X can be configurable, indicated, or predefined (e.g., N-1, where N is the total number of units).

[0204] ◆For example, the sum of the sizes of each unit determined by the UE is less than or equal to the total size of all units determined / configured / indicated by the base station. Further, if it is less, padding can be added.

[0205] ◆For example, in UL transmission, the padding information is sent to the peer entity via MAC CE.

[0206] ◆Optionally, the MAC CE can be for a single unit or for each unit (e.g., provided for a unit identifier, for a unit list, or for a unit bitmap). Optionally, if it is for a single unit, it can carry multiple MAC CE information, each corresponding to a different unit.

[0207] ■ Perform TB / CB / CBG segmentation or existing uniform CB / CBG segmentation, and / or, perform TB / CB / CBG segmentation based on packet boundaries, and / or, padding when performing TB / CB / CBG segmentation based on packet boundaries, and / or, send padding information to the peer entity.

[0208] ◆TB segments can be non-uniform or uniform.

[0209] ◆The CB / CBG segment is uniform.

[0210] ◆Optionally, the base station determines / configures / indicates the size of each cell, such as TBS, CB size, CBG size, etc.

[0211] ◆Optionally, padding bits are added for at least the first X cells of the plurality of cells to avoid SDU segmentation. Optionally, X can be configurable, indicated, or predefined (e.g., N-1, where N is the total number of cells).

[0212] ◆For example, the padding information can be whether padding has been added, and the bit length of the added padding.

[0213] ◆Optionally, the sent filling information can be for each unit.

[0214] ◆For example, in UL transmission, the padding information is sent to the peer entity via MAC CE.

[0215] ◆Optionally, the MAC CE can be for a single unit or for each unit (e.g., provided for a unit identifier, for a unit list, or for a unit bitmap). Optionally, if it is for a single unit, it can carry multiple MAC CE information, each corresponding to a different unit.

[0216] Example 1: (Multiple TBs reused into one resource or one codeword)

[0217] 1. The UE obtains resource configuration or scheduling information. Specifically, this includes at least one of the following:

[0218] a) The resources mentioned can be DG resources or CG resources.

[0219] b) The resource is a PUSCH resource or a PDSCH resource.

[0220] c) The resources described can support or reuse multiple TBs.

[0221] d) The resource corresponds to one or more codewords.

[0222] e) A codeword can carry or reuse multiple TBs.

[0223] f) Optionally, the resources or TB in this embodiment can also be replaced by HARQ processes.

[0224] g) The information may further include: the number of TBs, and / or the size of the resources or codewords, and / or the size of each TB. Optionally, the size may be an explicit indication or an implicit indication (such as MCS + resource location / number).

[0225] h) The information may also include first information, which is used to indicate whether to execute TB segment based on SDU (or determine the size of each TB), whether to allow Non-Uniform TB segmentation, and whether to allow / enable UE to report segment information.

[0226] i) Each TB may have its own index, attribute, or feature. Specifically, it may include at least one of the following:

[0227] i. Different TBs have the same or different attributes / characteristics.

[0228] ii.TB has an identifier or attribute or characteristic. Specifically, it can be at least one of the following: identifier, sorting, index, priority, corresponding reliable transmission requirement, corresponding priority transmission requirement, corresponding importance, and guaranteed bit error rate.

[0229] iii. Optionally, units with different identifiers, attributes, or characteristics may carry different LCHs or services, or the LCHs or services they preferentially carry may be different.

[0230] iv. Optionally, units with the same identifier, attribute, or characteristic may carry the same LCH or service, or the LCH or service that is preferentially carried may be the same.

[0231] v. For example, TB1, TB2, TB3 are multiplexed in a PUSCH or codeword, with priority 1, 1, 2 for TB1, 2, 3.

[0232] 2. The UE obtains the association, mapping relationship, or mapping restriction between the LCH and TB / CW. This includes at least one of the following:

[0233] a) Optional, 1 and 2 above have no order.

[0234] b) Optional, the association between LCH and TB / CW, or, mapping relationship, or, mapping restriction, configured via RRC, or indicated by DCI, or, predefined.

[0235] c) The association, mapping relationship, or mapping restriction, configuration, indication, or permission between the LCH and TB / CW, or different services / LCHs are mapped to different units (such as TB, CW).

[0236] d) Optionally, the mapping restrictions or mapping relationship between LCH and TB / CW can also be replaced by the mapping restrictions or mapping relationship between the service and TB / CW.

[0237] i.LCH may include at least one of the following: identifier, index, ID, priority, PBR, corresponding service, corresponding reliable transmission requirement, corresponding priority transmission requirement, and corresponding importance.

[0238] ii.TB / CW information may include at least one of the following: identifier, sorting, index, priority, corresponding reliable transmission requirement, corresponding priority transmission requirement, corresponding importance, guaranteed bit error rate, etc.

[0239] iii. For example: LCHs that have or are configured with mapping restrictions or mapping relationships between LCHs and TBs / CWs can be mapped, reused, preferentially mapped, or preferentially reused to TBs / CWs that match the mapping relationship.

[0240] iv. For example, if the LCH is not configured with mapping restrictions or mapping relationships between the LCH and the TB / CW, the LCH cannot be reused in any TB / CW with attributes, or can only be reused in TB / CW without attributes, or cannot be preferentially reused in any unit with attributes; or, it can be reused in any TB / CW (which may or may not have attributes).

[0241] v. For example, if there is a mapping constraint or mapping relationship configuration between LCH and TB / CW, but the configuration set is 0, then the LCH cannot be reused in any TB / CW with the attribute, or can only be reused in TB / CW without the attribute, or cannot be preferentially reused in any TB / CW with the attribute.

[0242] vi. For example, TB1, TB2, and TB3 are multiplexed in a single PUSCH or codeword, with priorities 1, 1, and 2 for TB1, 2, and priorities 1 and 2 for LCH1 and 2. In this case, LCH1 is multiplexed to TB1 / 2, and LCH2 is multiplexed to TB3.

[0243] vii. For example, TB1, TB2, and TB3 are multiplexed in a PUSCH or codeword, with TB1, 2, and 3 having reliability values ​​of 1, 1, and 2, respectively. LCH1 is associated with reliability 1, and LCH2 is associated with reliability 2. In this case, LCH1 is multiplexed to TB1 / 2, and LCH2 is multiplexed to TB3.

[0244] viii. For example, TB1, TB2, and TB3 are multiplexed in one PUSCH or codeword, with indices 1, 2, and 3 for TB1, 2, and 3 respectively. LCH1 and LCH2 have priorities of 1 and 2, respectively. In this case, LCH1 is multiplexed to TB1 / 2, and LCH2 is multiplexed to TB3.

[0245] ix. For example, TB1, TB2, and TB3 are multiplexed in a single PUSCH or codeword, with indices 1, 2, and 3 for TB1, 2, and 3 respectively. LCH1 is associated with TB1, and LCH2 is associated with TB2. In this case, LCH1 is multiplexed to TB1 / 2, and LCH2 is multiplexed to TB3.

[0246] 3. The UE performs packet assembly, or invokes the multiplexing packet entity, or generates a MAC PDU. Specifically, this includes at least one of the following:

[0247] a) The UE obtains TB information.

[0248] b) The UE performs packet assembly for each TB, or calls the multiplexed packet entity, or generates a MAC PDU.

[0249] c) Based on the above mapping restrictions, the UE configures to multiplex different LCHs / services in different TBs.

[0250] i. The same LCH / service is mapped to the same attribute / feature TB, or, the same attribute / feature TB is preferred for mapping;

[0251] ii. Different LCH / services are mapped to different attribute / feature TBs, or, priority is given to mapping to different attribute / feature TBs.

[0252] d) For units with the same attributes / features, the UE reduces segmentation processing or segments based on packet boundaries.

[0253] i. Perform TB segmentation, and / or perform TB segmentation based on packet boundaries, and / or send segmentation information to the peer entity.

[0254] 1. Optionally, the base station determines / configures / indicates the total size of all TBs, such as TBS. Optionally, the size can be explicitly indicated or implicitly indicated (e.g., MCS + resource location / number).

[0255] 2. Optionally, the UE determines / configures / indicates information for each TB, such as size (e.g., TBS), and TB segmentation (to avoid SDU / data packets being segmented).

[0256] 3. Optionally, at least the first X TBs of the plurality of TBs are used to avoid SDU segmentation. Optionally, X can be configurable, indicated, or predefined (e.g., N-1, where N is the total number of the cells).

[0257] 4. For example, the sum of the sizes of each TB determined by the UE is less than or equal to the total size of all TBs determined / configured / indicated by the base station. Further, if it is less, padding can be added.

[0258] 5. For example, in the case of UL transmission, the segmented information is sent to the peer entity (such as a base station) via MAC CE.

[0259] 6. Optionally, the MAC CE can be for a single TB or for each TB (e.g., provided for a TB identifier, for a TB list, or for a TB bitmap). Optionally, if it is for a single TB, it can carry multiple MAC CE information, each corresponding to a different TB.

[0260] 7. For example: The first MAC CE is used to indicate whether non-uniform TB segmentation is performed for each TB, to ensure that the SDU boundary is not split by the TB boundary. The MAC CE can carry the index of each TB and the corresponding segmentation information. Alternatively, the MAC CE can carry the TB bitmap, indicating whether non-uniform segmentation is performed for the position of the bitmap of each TB.

[0261] 8. For example, a first MAC CE indicates the size (and / or, how it is segmented) of each TB, ensuring that SDU boundaries are not fragmented by TB boundaries. The MAC CE may carry the index of each TB and the corresponding TB size / segmentation information. Alternatively, the MAC CE may carry a TB bitmap, indicating the TB size / segmentation information for the position of the bitmap for each TB.

[0262] 9. Optionally, the above MAC CE can also be replaced by UCI / PUCCH / RRC signaling.

[0263] 10. For example: Base station indicates or configures payload (P). The UE determines the TBS for each TB and reports the TBS information via the MAC CE. Each TB carries a complete SDU, without SDU segmentation due to TB size limitations (i.e., causing one SDU to be placed in different TBs). The sum of the TBS for each TB is <= P. Optionally, the UE is a MAC entity. Optionally, the TBS determination can be made by the MAC and / or PHY.

[0264] ii. Perform TB segmentation, and / or send padding information to the peer entity.

[0265] 1. Optionally, the base station determines / configures / indicates the size of each TB, such as TBS. Optionally, the size can be an explicit indication or an implicit indication (such as MCS + resource location / number).

[0266] 2. For example, the UE determines that for each TB packet, if the TBsize cannot match the complete SDU size (including the header), then a complete SDU information cannot be placed in the TB. Only padding can be added to the remaining bit positions (i.e., TBsize <= the total size of the SDU that can be placed. When it is less than that, padding is added to the TB to avoid SDU segmentation).

[0267] 3. Optionally, at least the first X TBs of the plurality of TBs are used to avoid SDU segmentation. Optionally, X can be configurable, indicated, or predefined (e.g., N-1, where N is the total number of the cells).

[0268] 4. For example, in UL transmission, the padding information is sent to the peer entity (such as a base station) via MAC CE.

[0269] 5. Optionally, the MAC CE can be for a single unit or for each unit (e.g., provided for a TB identifier, for a TB list, or for a TB bitmap). Optionally, if it is for a single TB, it can carry multiple MAC CE information, each corresponding to a different TB.

[0270] 6. For example, the first MAC CE is used to indicate whether padding (and / or the size of the added padding bits) is added to each TB, to ensure that the SDU boundary is not split by the TB boundary. The MAC CE can carry the index of each TB and the corresponding padding information. Alternatively, the MAC CE can carry the TB bitmap, indicating the padding information for the position of the bitmap for each TB.

[0271] 7. Optionally, the above MAC CE can also be replaced by UCI / PUCCH / RRC signaling.

[0272] 8. For example, the base station implicitly / explicitly represents the TBS for each TB. When the UE assembles packets for each TB, it multiplexes the SDU within the TB. If there is insufficient remaining space to hold the complete next SDU, padding bits are added to the remaining space. The UE notifies the network of this padding addition information. Optionally, the padding is added to avoid SDU segments appearing in at least the first few TBs.

[0273] Extended: For DL: Base stations can explicitly or implicitly indicate TBS for each TB / CW.

[0274] Beneficial effects: Each TB can be processed independently, allowing the entire data information to be recovered upon receiving partial data, avoiding latency and reducing redundant transmission. Compared to Example 2, it better reuses existing protocols / mechanisms.

[0275] Example 2: Multiple CBs / CBGs correspond to one resource, one codeword, one TB, or one HARQ process. Furthermore, CB / CBG segmentation is performed / determined based on packet / SDU boundaries.

[0276] 1. The UE obtains resource configuration or scheduling information. Specifically, this includes at least one of the following:

[0277] a) The resources mentioned can be DG resources or CG resources.

[0278] b) The resource is a PUSCH resource or a PDSCH resource.

[0279] c) The resources described can support or reuse multiple CB / CBGs.

[0280] d) The resource corresponds to a codeword.

[0281] e) A codeword can carry or reuse multiple CB / CBGs.

[0282] f) Optionally, the resources or codewords in this embodiment can also be replaced with HARQ processes or TB.

[0283] g) The information may further include: the number of CBs / CBGs, and / or, the size of the resource or codeword, and / or, the size of the TB, and / or, the size of each CB / CBG. Optionally, the size may be an explicit indication or an implicit indication (such as MCS + resource location / number).

[0284] h) The information may also include first information, which is used to indicate whether to execute a TB segment based on the SDU (or determine the size of each CB / CBG), whether to allow non-Uniform CB / CBG segments, and whether to allow / enable UE to report segment information.

[0285] i) Each CB / CBG may have its own index, attribute, or feature. Specifically, it may include at least one of the following:

[0286] i. Different CBs / CBGs may have the same or different attributes / features.

[0287] ii. CB / CBG has an identifier, attribute, or characteristic. Specifically, it can be at least one of the following: identifier, sorting, index, priority, corresponding reliable transmission requirement, corresponding priority transmission requirement, corresponding importance, and guaranteed bit error rate.

[0288] iii. Optionally, CB / CBGs with different identifiers, attributes, or characteristics may carry different LCHs or services, or the LCHs or services they preferentially carry may be different.

[0289] iv. Optionally, CB / CBGs with the same identifier, attributes, or characteristics may carry the same LCH or services, or the LCH or services that are preferentially carried may be the same.

[0290] v. For example, CB1 / CBG1, CB2 / CBG2, CB3 / CBG3 are multiplexed in a PUSCH or codeword, with CB / CBG1, 2, 3 having priorities of 1, 1, 2.

[0291] 2. The UE obtains the association, mapping relationship, or mapping restriction between the LCH and CB / CBG. This includes at least one of the following:

[0292] a) Optional, there is no order between 1 and 2 above.

[0293] b) Optional, the association between LCH and CB / CBG, or the mapping relationship, or the mapping restriction, configured via RRC, or indicated by DCI, or predefined.

[0294] c) The association, mapping relationship, or mapping restriction, configuration, indication, or permission between the LCH and CB / CBG, whereby different services / LCH are mapped to different units (such as CB / CBG).

[0295] d) Optionally, the mapping restrictions or mapping relationships between LCH and CB / CBG can also be replaced with the mapping restrictions or mapping relationships between services and CB / CBG.

[0296] i.LCH may include at least one of the following: identifier, index, ID, priority, PBR, corresponding service, corresponding reliable transmission requirement, corresponding priority transmission requirement, and corresponding importance.

[0297] ii. CB / CBG information may include at least one of the following: identifier, sorting, index, priority, corresponding reliable transmission requirement, corresponding priority transmission requirement, corresponding importance, guaranteed bit error rate, etc.

[0298] iii. For example: an LCH that has a mapping constraint or mapping relationship between an LCH and a CB / CBG, can be mapped, reused, preferentially mapped, or preferentially reused to a CB / CBG that matches the mapping relationship.

[0299] iv. For example, if the LCH is not configured with mapping restrictions or mapping relationships between the LCH and CB / CBG, the LCH cannot be reused in any CB / CBG that has attributes, or it can only be reused in CB / CBG that does not have attributes, or it cannot be preferentially reused in any unit that has attributes; or it can be reused in any CB / CBG (which may or may not have attributes).

[0300] v. For example, if there is a mapping constraint or mapping relationship configuration between LCH and CB / CBG, but the configuration set is 0, then the LCH cannot be reused in any CB / CBG with the attribute, or can only be reused in CB / CBG without the attribute, or cannot be preferentially reused in any CB / CBG with the attribute.

[0301] vi. For example, CB / CBG1, CB / CBG2, and CB / CBG3 are multiplexed into a single PUSCH or codeword, with priorities of CB / CBG1, 2, and 3 being 1, 1, and 2, respectively. LCH1 and LCH2 have priorities of 1 and 2, respectively. In this case, LCH1 is multiplexed into CB / CBG1 / 2, and LCH2 is multiplexed into CB / CBG3.

[0302] vii. For example, CB / CBG1, CB / CBG2, and CB / CBG3 are multiplexed in a PUSCH or codeword, with CB / CBG1, 2, and 3 having reliability values ​​of 1, 1, and 2, respectively. LCH1 is associated with reliability 1, and LCH2 is associated with reliability 2. In this case, LCH1 is multiplexed to CB / CBG1 / 2, and LCH2 is multiplexed to CB / CBG3.

[0303] viii. For example, CB / CBG1, CB / CBG2, and CB / CBG3 are multiplexed into a single PUSCH or codeword, with CB / CBG1, 2, and 3 having indices of 1, 2, and 3. LCH1 and 2 have priorities of 1 and 2, respectively. In this case, LCH1 is multiplexed into CB / CBG1 / 2, and LCH2 is multiplexed into CB / CBG3.

[0304] ix. For example, CB / CBG1, CB / CBG2, and CB / CBG3 are multiplexed in a single PUSCH or codeword, with CB / CBG1.2.3 indexed as 1, 2, and 3. LCH1 is associated with CB / CBG1, and LCH2 is associated with CB / CBG2. In this case, LCH1 is multiplexed to CB / CBG1 / 2, and LCH2 is multiplexed to CB / CBG3.

[0305] 3. The UE performs packet assembly, or invokes the multiplexing packet entity, or generates a MAC PDU. Specifically, this includes at least one of the following:

[0306] a) The UE obtains TB information and / or CB / CBG information.

[0307] b) The UE performs packet assembly for each TB, or calls the multiplexed packet entity, or generates a MAC PDU.

[0308] i. Mapping of the same LCH / service to the same attribute / feature CB / CBG, or, preferentially mapping to the same attribute / feature CB / CBG.

[0309] ii. Different LCH / services are mapped to different attributes / features CB / CBG, or, preferentially mapped to different attributes / features TB.

[0310] c) The UE performs CB / CBG segmentation. Specifically, this includes at least one of the following:

[0311] i. For units with the same attributes / features, reduce segmentation processing, or segment based on packet boundaries.

[0312] ii. The CB / CBG segment can be executed in the MAC or in the PHY.

[0313] iii. Perform CB / CBG segmentation, and / or perform TB segmentation based on packet boundaries, and / or send segmentation information to the peer entity.

[0314] √The above refers to the non-uniform CB / CBG segment.

[0315] √Optional, the base station determines / configures / indicates the total size of all TBs, such as TBS, etc.

[0316] √Optional, the UE determines / configures / indicates information for each CB / CBG, such as size (e.g., CB / CBG size), and CB / CBG segmentation (to avoid SDU / data packets being segmented).

[0317] √ For example, when the UE performs CB / CBG segmentation, the boundary of the CB is defined as the boundary of one or more SDUs, meaning that an SDU can only be placed in one CB.

[0318] √Optionally, at least the first X CB / CBGs of the plurality of CB / CBGs are targeted to avoid SDU segmentation. Optionally, X can be configurable, indicated, or predefined (e.g., N-1, where N is the total number of units).

[0319] √ For example, the sum of the sizes of each CB / CBG determined by the UE is less than or equal to the total size of the TB determined / configured / indicated by the base station. Further, if it is less, padding can be added.

[0320] √ For example, in UL transmission, the segmented information is sent to the peer entity (such as a base station) via MAC CE.

[0321] √Optionally, the MAC CE can be for a single CB / CBG or for each CB / CBG (e.g., provided for a CB / CBG identifier, for a CB / CBG list, or for a CB / CBG bitmap). Optionally, if it is for a single CB / CBG, it can carry multiple MAC CE information, each corresponding to a different CB / CBG.

[0322] √ For example: The first MAC CE is used to indicate whether each CB / CBG should undergo non-uniform CB / CBG segmentation, ensuring that the SDU boundary is not split by the CB / CBG boundary. The MAC CE can carry the index of each CB / CBG and the corresponding segmentation information. Alternatively, the MAC CE can carry a CB / CBG bitmap, indicating whether non-uniform segmentation is performed for the position of the bitmap of each CB / CBG.

[0323] √ For example, the first MAC CE is used to indicate the size (and / or, how it is segmented) of each CB / CBG, to ensure that the SDU boundary is not segmented by the CB / CBG boundary. The MAC CE can carry the index of each CB / CBG and the corresponding CB / CBG size / segmentation information. Alternatively, the MAC CE can carry a CB / CBG bitmap, indicating the CB / CBG size / segmentation information for the position of the bitmap for each CB / CBG.

[0324] √Optionally, the above MAC CE can also be replaced by UCI / PUCCH / RRC signaling.

[0325] √ For example: The base station indicates or configures the payload (P) of TB. The UE determines the size of each CB / CBG and reports the size information via the MAC CE. Each CB / CBG carries a complete SDU, without SDU segmentation due to CB / CBG size limitations (i.e., causing one SDU to be placed in different CB / CBGs). The sum of the sizes of each CB / CBG is <= P. Optionally, the UE is a MAC entity or a PHY entity. Optionally, the CB / CB size can be determined by the MAC and / or PHY.

[0326] iv. Perform uniform / existing CB / CBG segmentation, and / or send padding information to the peer entity.

[0327] √Optional, base station determines / configures / indicates the size of TB, such as TBS, etc.

[0328] √UE determines the division, size, etc. of each CB / CBG according to existing rules or formulas.

[0329] √ For example, when the UE executes a CB / CBG segment, if the CB / CBG size cannot match the complete SDU size (including the header), then a complete SDU information cannot be placed in the CB / CBG. Padding can only be added to the remaining bit positions (i.e., CB / CBG size <= the total size of the SDU that can be placed. When it is less than that, padding is added to the CB / CBG to avoid SDU segmentation).

[0330] √Optionally, at least the first X CB / CBGs of the plurality of CB / CBGs are targeted to avoid SDU segmentation. Optionally, X can be configurable, indicated, or predefined (e.g., N-1, where N is the total number of units).

[0331] √ For example, in UL transmission, the padding information is sent to the peer entity (such as a base station) via MAC CE.

[0332] √Optionally, the MAC CE can be for a single CB / CBG or for each CB / CBG (e.g., provided for a CB / CBG identifier, for a CB / CBG list, or for a CB / CBG bitmap). Optionally, if it is for a single CB / CBG, it can carry multiple MAC CE information, each corresponding to a different CB / CBG.

[0333] √ For example, the first MAC CE is used to indicate whether padding (and / or the size of the added padding bits) is added to each CB / CBG, to ensure that the SDU boundary is not segmented by the CB / CBG boundary. The MAC CE can carry the index of each CB / CBG and the corresponding padding information. Alternatively, the MAC CE can carry the CB / CBG bitmap, indicating the padding information for the position of the bitmap of each CB / CBG.

[0334] √Optionally, the above MAC CE can also be replaced by UCI / PUCCH / RRC signaling.

[0335] √ For example, the base station implicitly / explicitly represents the TBS of a TB. When the UE assembles packets for a TB, it multiplexes the SDU within the TB. The UE executes CB / CBG segmentation; if there is insufficient remaining space in each CB / CBG to hold the complete next SDU, padding bits are added to the remaining space. The UE notifies the network of this padding addition information. Optionally, the padding is added to avoid SDU segments appearing in at least the first few CB / CBGs.

[0336] d) Based on the above mapping restrictions, the UE configures to multiplex different LCHs / services in different CBs / CBGs.

[0337] Extended: For DL, for each CB / CBG, the base station can indicate the segmentation rules, segment boundaries, or payload (size).

[0338] Beneficial effects: It enables each CB / CBG to be processed independently, allowing the overall data information to be recovered upon receiving partial data, avoiding latency and reducing redundant transmission.

[0339] As can be seen from the foregoing text of this application, the method provided in this application achieves the following:

[0340] Direction 1: Multiple TBs multiplexed in one codeword.

[0341] • Allow different LCH maps to different TBs which are multiplexed in one codeword.

[0342] • Introduce LCH to TB / CW mapping restriction.

[0343] • For more than one TB with the same attribute (e.g., priority), avoid packet / RLC SDU segmentation.

[0344] • For DL: Network (NW) implicitly / explicitly indicates the size per TB.

[0345] This indicates TBs of each TB.

[0346] • For UL:

[0347] • Method 1: NW indicates total payload (P). The UE determines the size of each TB and reports the TB size information via UCI / MAC CE, where the sum of the TB sizes is less than or equal to P.

[0348] The UE can be either a MAC or a PHY (interacting with SDU boundary information).

[0349] • Method 2: NW implicitly / explicitly indicates the size of each TB, and padding bits are added to avoid SDU segmentation, at least for the first few TBs.

[0350] Direction 2: CB / CBG segmentation based on the boundary of SDU.

[0351] • Allow different LCH maps to different CB / CBG which are associated with one codeword.

[0352] • Introduce LCH to CB / CBG mapping restriction.

[0353] • Non-uniform CB / CBG segmentation.

[0354] • For more than one CB / CBG with the same attribute (e.g., priority), avoid packet / RLC SDU segmentation.

[0355] • For DL: NW indicates the segmentation strategy or the boundary / payload of each CB / CBG.

[0356] • For UL:

[0357] • Method 1: NW indicates TBS. The UE decides the CB / CBG segmentation and reports the segmentation result via UCI / MAC CE.

[0358] The UE can be either a MAC or a PHY (interacting with SDU boundary information).

[0359] • Method 2: No enchantment on PHY CB / CBG segmentation. Padding bit is added to avoid SDU segmentation, at least for the first few CB / CBGs.

[0360] It should be noted that some LCHs currently allow or support Automatic Repeat Request (ARQ) transmission, while others do not allow or support ARQ transmission. The method provided in this application can also be used in cases where ARQ transmission is disabled, ARQ transmission is no longer supported, or HARQ and ARQ are aggregated.

[0361] In addition, this application also provides the following:

[0362] Regarding network energy saving scenarios (NES) in R19, there are some legacy issues:

[0363] Question 1: Some companies have observed that Msg2 transmitted by the NES cell may include a SIB1 request ACK for the NES UE and RAR feedbacks for other UEs in this NES cell, because the RO for the SIB1 request can be shared with other RA uses. Since the NES UE lacks preamble information for other RA uses, and because the TotalNumberOfRA preamble is not included in the UL-WUS configuration, the NES UE may not know how to decode the SIB1 request ACK in the MAC PDU.

[0364] The simplest way to resolve this issue is to include TotalNumberOfRA preambles in the WUS configuration.

[0365] Recommendation 1: If R2 tends to solve the issue of RAR handling when an RO for SIB1 request is shared with other RA usages, contain TotalNumberOfRA-preambles into the WUS configuration.

[0366] Furthermore, the MAC PDU carrying the MAC RAR(s), or the MAC PDU corresponding to the msg2 message, may carry one or more response messages for system information requests (or, in other words, only RAPID MAC sub-PDUs). If the MAC PDU carrying the MAC RAR(s), or the MAC PDU corresponding to the msg2 message, carries one response message for a system information request (or, in other words, only RAPID MAC sub-PDUs), then the response message or MAC sub-PDU is for an OSI request or for a SIB1 request. If the MAC PDU carrying the MAC RAR(s), or the MAC PDU corresponding to the msg2 message, carries multiple response messages for system information requests (or, in other words, only RAPID MAC sub-PDUs), then the response message or MAC sub-PDU is for both OSI and SIB1 requests. For scenarios that carry multiple response messages for system information requests (or, in other words, only RAPID MAC sub-PDUs), typically, it can carry two response messages for system information requests (or, in other words, only RAPID MAC sub-PDUs).

[0367] Question 2: Some companies have mentioned that RAN1 has not yet decided whether all SSBs will be configured with OD-SIB1 RA resources. If not, reusing the legacy SSB selection procedure (i.e., selecting any SSB) is not applicable.

[0368] Existing agreements:

[0369] 1> Otherwise (i.e., for contention-based random access preamble selection):

[0370] 2> If at least one of the SSBs with SS-RSRP above rsrp-ThresholdSSB is available:

[0371] 3> Select an SSB with SS-RSRP above rsrp-ThresholdSSB.

[0372] 2> Otherwise:

[0373] 3> Select any SSB.

[0374] We understand this issue, but we recommend restricting the network configuration to minimize the specification impact, meaning the UE does not expect an SSB to exist without the corresponding WUS configuration.

[0375] Recommendation 2: Reuse the legacy SSB selection procedure in the MAC specification, i.e., the UE does not expect an SSB to exist without a corresponding WUS configuration.

[0376] Question 3: How does SUL co-exist with the OD-SIB1 request procedure? Traditionally, the UE needs to select either SUL or NUL during the RA procedure initialization.

[0377] Existing agreements:

[0378] 1> If the RSRP of the downlink pathloss reference is less than the RSRP threshold SSB-SUL:

[0379] 2> Select the SUL carrier for performing the Random Access procedure;

[0380] 2> Set the PCMAX to PCMAX,f,c of the SUL carrier.

[0381] 1> Otherwise:

[0382] 2> Select the NUL carrier for performing the random access procedure;

[0383] 2> Set the PCMAX to PCMAX,f,c of the NUL carrier.

[0384] Since RAN1 has agreed that SupplementaryUL is not included in the UL-WUS configuration, and the current RRC running CR does not include rsrp-ThresholdSSB-SUL, the UE should always select NUL when requesting SIB1 for an NES cell, assuming the network would not configure SUL for the NES cell with OD-SIB1 feature.

[0385] Recommendation 3: For OD-SIB1:

[0386] Alt1: No specific handling for SUL is needed, i.e., the existing SUL / NUL selection process is followed (i.e., if there is a WUS configuration for this NES cell, when the UE performs RACH to obtain SIB1 in this cell, the UE follows the existing SUL / NUL selection process).

[0387] Alt2: The UE always selects NUL, or the UE ignores the above SUL / NUL selection process (i.e., if there is a WUS configuration for this NES cell, when the UE performs RACH in this cell, the UE always selects NUL, or the UE ignores the above SUL / NUL selection process).

[0388] Alt3: When the UE requests SIB1 in this NES cell, the UE always selects NUL, or the UE ignores the above SUL / NUL selection process (that is, if there is a WUS configuration for this NES cell, when the UE performs the RACH request SIB1 in this cell, the UE always selects NUL, or the UE ignores the above SUL / NUL selection process). In other cases, the above SUL / NUL selection process is performed.

[0389] In addition, this application also provides the following:

[0390] For DSR (Delay Status Report), assume that DSR triggering / reporting parameters are configured for a MAC entity or a UE, or that DSR triggering / reporting parameters are configured for multiple LCGs of a MAC entity or a UE. The DSR triggering / reporting parameters include DSR triggering thresholds (such as remainingTimeThreshold) and / or DSR reporting thresholds (such as dsr-ReportingThreList). For example, if a DSR triggering threshold is configured for the first part of the multiple LCGs (but no reporting threshold is configured), and both a DSR triggering threshold and a DSR reporting threshold are configured for the second part of the LCGs, and if the UE needs to generate or report an enhanced DSR MAC CE or a Multiple Entry DSR MAC CE, then:

[0391] 1) The DSR trigger threshold of the first LCG is also the DSR reporting threshold of that first LCG, or the DSR reporting threshold of the first LCG is assigned the value of the DSR trigger threshold of that first LCG; and / or,

[0392] 2) It is assumed that the first part of the LCG also has a DSR reporting threshold configured. Specifically, the reporting threshold list includes a DSR reporting threshold, and / or, the DSR reporting threshold of the first part of the LCG is the value of the DSR trigger threshold of that first part of the LCG; and / or,

[0393] 3) For at least one LCH / PDCP / RLC corresponding to the first part LCG, each of the at least one LCH / PDCP / RLC is considered, when calculating the amount of data carried in the DSR report, to have its delay-critical data amount as the delay-reporting data amount, or its delay-reporting data amount is calculated based on the DSR trigger threshold of the first part LCG, or its delay-reporting data amount is calculated based on the DSR trigger threshold assigned to the first part LCG.

[0394] For example, a UE has LCG1 and LCG2. LCG1 has a DSR trigger threshold 1 (e.g., value1), and LCG2 has a DSR trigger threshold 2 and a DSR reporting threshold 3. LCG1 contains LCH1 and LCH2, and LCG2 contains LCH3 and LCH4. If LCG1 / LCH1 triggers DSR reporting and / or LCG2 / LCH3 triggers DSR reporting, or if there are pending DSRs in LCG1 / LCH1 and / or LCG2 / LCH3, then enhanced DSR MAC CE reporting is used, or Multiple Entry DSR MAC CE reporting is used. In this case, it is assumed that the DSR reporting threshold of LCG1 is configured, or that the DSR reporting threshold is DSR trigger threshold 1 (e.g., value1); and / or, the amount of data reported by LCG1 / LCH1 (i.e., delay-critical data amount, or delay-reporting data amount) is calculated based on this DSR reporting threshold.

[0395] In some cases, if an LCG or its LCH triggers a DSR, such as in case 1 (where an LCH of the LCG does not have delayed-reporting data but has non-delay-reporting data), then for that LCH:

[0396] Alt1: The amount of data that does not include non-delay reporting data when calculating the amount of delay-reporting data for this LCH, or the amount of data that does not include non-delay reporting data when reporting the amount of delay-reporting data for this LCH, or the delay status information of this LCH is not reported, or the delay status information / data amount of non-delay reporting data for this LCH is only reported or calculated when delay-reporting data exists for an LCH.

[0397] Alt2: Calculate or report the delay status information / data volume information of the LCH, and / or report or calculate the data volume of non-delay reporting data through a specific reporting portion of the LCH or LCG. The specific reporting section includes one of the following: the first configured DSR reporting section, the first actually reported DSR reporting section, the last configured DSR reporting section, the last actually reported DSR reporting section, the earliest configured DSR reporting section, the earliest reported DSR reporting section, the latest configured DSR reporting section, the latest reported DSR reporting section, the last reported DSR reporting section, the section corresponding to the first configured DSR reporting threshold, the section corresponding to the first actually reported DSR reporting threshold, the section corresponding to the last configured DSR reporting threshold, the section corresponding to the last actually reported DSR reporting threshold, the section corresponding to the earliest configured DSR reporting threshold, the section corresponding to the earliest reported DSR reporting threshold, the section corresponding to the latest configured DSR reporting threshold, and the section corresponding to the last reported DSR reporting threshold.

[0398] In other cases, if an LCG or its LCH triggers a DSR, such as case 2 (where an LCH2 of the LCG triggers a DSR, or an LCH2 of the LCG needs to report delay status information, and there exists another LCH, recorded as LCH1, whose LCH priority is higher than LCH2, and LCH1 has not triggered a DSR and / or has no delay-reporting data. Further, if an LCH2 is associated with the LCG, and the LCH priority of LCH3 is lower than both LCH1 and LCH2. LCH3 may or may not report delay status information), then for that LCH1:

[0399] Alt1: When calculating the delay-reporting data volume of this LCG, the data volume of LCH1's data is not included; or, the delay status information of this LCH1 is not reported; or, the delay status information / data volume of this LCH's data is only reported or calculated when there is delay-reporting data for this LCH1.

[0400] Alt2: Calculate or report the delay status information / data volume information of LCH1, and / or report or calculate the data volume of LCH1 through a specific reporting portion of this LCG. The specific reporting portion includes one of the following: the first configured DSR reporting portion, the first actually reported DSR reporting portion, the last configured DSR reporting portion, the last actually reported DSR reporting portion, the earliest configured DSR reporting portion, the earliest reported DSR reporting portion, the latest configured DSR reporting portion, the latest reported DSR reporting portion, the portion corresponding to the first configured DSR reporting threshold, the portion corresponding to the first actually reported DSR reporting threshold, the portion corresponding to the last configured DSR reporting threshold, the portion corresponding to the last actually reported DSR reporting threshold, the portion corresponding to the earliest configured DSR reporting threshold, the portion corresponding to the earliest reported DSR reporting threshold, the portion corresponding to the latest configured DSR reporting threshold, and the portion corresponding to the latest reported DSR reporting threshold.

[0401] Alt3: Calculates or reports the delay status information / data volume information of LCH1, and / or reports or calculates the data volume of LCH1 through a specific reporting portion of LCH2 of the LCG. The specific reporting portion includes one of the following: the first configured DSR reporting portion, the first actually reported DSR reporting portion, the last configured DSR reporting portion, the last actually reported DSR reporting portion, the earliest configured DSR reporting portion, the earliest reported DSR reporting portion, the latest configured DSR reporting portion, the last reported DSR reporting portion, the portion corresponding to the first configured DSR reporting threshold, the portion corresponding to the first actually reported DSR reporting threshold, the portion corresponding to the last configured DSR reporting threshold, the portion corresponding to the last actually reported DSR reporting threshold, the portion corresponding to the earliest configured DSR reporting threshold, the portion corresponding to the earliest reported DSR reporting threshold, the portion corresponding to the latest configured DSR reporting threshold, and the portion corresponding to the last reported DSR reporting threshold.

[0402] Figure 11 is a block diagram of a first device provided in an exemplary embodiment of this application. The device can be implemented as a first communication device, or as part of a first communication device, through software, hardware, or a combination of both. The device includes a transmitting module 1101 and a processing module 1102.

[0403] The transmitting module 1101 is used to multiplex at least two sub-units into the same data unit, and / or to transmit at least two sub-units through the same data unit.

[0404] At least two sub-units are multiplexed into the same data unit. This can also be understood as at least two sub-units being packetized or packaged into the same data unit, or as data corresponding to at least two sub-units being carried or transmitted through the same data unit, or as PDUs (such as MAC PDUs) corresponding to at least two sub-units being carried or transmitted through the same data unit. The data unit includes at least two sub-units, or it can be understood that the data unit includes multiple sub-units. In some embodiments, at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to the same service or logical channel or information. In some embodiments, the data unit corresponds to uplink data or uplink transmission. In other embodiments, the data unit corresponds to downlink data or downlink transmission.

[0405] In some embodiments, one of the at least two sub-units is one of TB, CB, CBG, sub-data channel, HARQ process, HARQ sub-process, and CW. In some embodiments, the data unit is one of DG resource, CG resource, PUSCH, CW, TB, data channel, and HARQ process.

[0406] In some embodiments, all or some of the subunits in at least two subunits have attributes. The attributes of a subunit are equivalent to / can be replaced by the features of the subunit. In some embodiments, at least two subunits have the same attribute; or, at least two subunits have different attributes; or, some subunits in at least two subunits have the same attribute, and the subunits other than those have different attributes. In some embodiments, the attributes of a subunit include one or more of the following: subunit identifier; subunit order; subunit index; subunit priority; reliable transmission requirement corresponding to the subunit; priority transmission requirement corresponding to the subunit; importance corresponding to the subunit; data transmission type corresponding to the subunit; guaranteed bit error rate of the subunit; decoding method corresponding to the subunit; reporting method corresponding to the subunit; segmentation method corresponding to the subunit; padding and addition method corresponding to the subunit.

[0407] It should be noted that the description of data units and sub-units can be found in other embodiments of this application, and will not be repeated here.

[0408] In some embodiments, processing module 1102 is configured to multiplex different LCHs or different service data into different sub-units of at least two sub-units, or to transmit different LCHs or different service data through different sub-units of at least two sub-units. In some embodiments, processing module 1102 is configured to multiplex different LCHs or different service data into the same sub-unit of at least two sub-units, or to transmit different LCHs or different service data through the same sub-unit of at least two sub-units. In some embodiments, processing module 1102 is configured to multiplex different LCHs into different sub-units of at least two sub-units according to a first mapping relationship; or, multiplex different service data into different sub-units of at least two sub-units according to a second mapping relationship; or, transmit different LCHs through different sub-units of at least two sub-units according to the first mapping relationship; or, transmit different service data through different sub-units of at least two sub-units according to the second mapping relationship. The first mapping relationship includes a mapping relationship and / or mapping restrictions between at least one LCH and at least one sub-unit, and the second mapping relationship includes a mapping relationship and / or mapping restrictions between at least one service data and at least one sub-unit.

[0409] In some embodiments, sub-units with different attributes carry different LCH or service data; or, sub-units with different attributes preferentially carry different LCH or service data. In some embodiments, sub-units with the same attributes carry the same LCH or service data; or, sub-units with the same attributes preferentially carry the same LCH or service data. In some embodiments, sub-units with different attributes carry different characteristics of LCH or service data; or, sub-units with different attributes preferentially carry different characteristics of LCH or service data. In some embodiments, sub-units with the same attributes carry the same characteristics of LCH or service data; or, sub-units with the same attributes preferentially carry the same characteristics of LCH or service data.

[0410] It should be noted that for the introduction of sub-unit multiplexing of LCH / service data, please refer to the relevant content in other embodiments of this application, and will not be repeated here.

[0411] In some embodiments, the processing module 1102 is configured to segment data packets corresponding to all or some of the sub-units in at least two sub-units based on data packet boundaries, and / or determine data packets carried or multiplexed by all or some of the sub-units in at least two sub-units based on data packet boundaries, and / or segment or divide all or some of the sub-units in at least two sub-units based on data packet boundaries, and / or determine data packet boundaries or determine sub-units to which one or more data packets are multiplexed based on the boundaries of all or some of the sub-units in at least two sub-units. In some embodiments, data packet boundaries are used to prevent data packets carried by all or some of the sub-units from being segmented.

[0412] In some embodiments, the processing module 1102 is configured to determine the size information of all or part of the sub-units in at least two sub-units based on the packet boundary, and / or to determine the amount of data carried by all or part of the sub-units in at least two sub-units based on the packet boundary. In some embodiments, the packet boundary is used to prevent the data packets carried by all or part of the sub-units from being segmented.

[0413] In some embodiments, the sending module 1101 is used to send segmentation information of data packets carried by at least two sub-units, and / or send information on the amount of data carried by at least two sub-units, and / or send size information of at least two sub-units.

[0414] In some embodiments, processing module 1102 is configured to add padding bits to all or some of the sub-units in at least two sub-units. In some embodiments, the padding bits are used to prevent the data packets carried by all or some of the sub-units from being segmented. In some embodiments, sending module 1101 is configured to send padding information of the padding bits, for example, to send padding information of the padding bits to a second communication device.

[0415] It should be noted that for an introduction to data packet segmentation, please refer to the relevant content in other embodiments of this application, and will not be repeated here.

[0416] Figure 12 is a block diagram of a second device provided in an exemplary embodiment of this application. The device can be implemented as a second communication device, or as part of a second communication device, by software or hardware or a combination of both. The device includes a receiving module 1201.

[0417] The receiving module 1201 is used to receive a data unit, wherein the data unit multiplexes at least two sub-units, or at least two sub-units are transmitted through the data unit.

[0418] At least two sub-units are multiplexed into the same data unit. This can also be understood as at least two sub-units being packetized or packaged into the same data unit, or as data corresponding to at least two sub-units being carried or transmitted through the same data unit, or as PDUs (such as MAC PDUs) corresponding to at least two sub-units being carried or transmitted through the same data unit. The data unit includes at least two sub-units, or it can be understood that the data unit includes multiple sub-units. In some embodiments, at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to different services or logical channels or information. In some embodiments, some sub-units within the at least two sub-units correspond to the same service or logical channel or information. In some embodiments, the data unit corresponds to uplink data or uplink transmission. In other embodiments, the data unit corresponds to downlink data or downlink transmission.

[0419] In some embodiments, one of the at least two sub-units is one of TB, CB, CBG, sub-data channel, HARQ process, HARQ sub-process, and CW. In some embodiments, the data unit is one of DG resource, CG resource, PUSCH, CW, TB, data channel, and HARQ process.

[0420] In some embodiments, all or some of the subunits in at least two subunits have attributes. The attributes of a subunit are equivalent to / can be replaced by the features of the subunit. In some embodiments, at least two subunits have the same attribute; or, at least two subunits have different attributes; or, some subunits in at least two subunits have the same attribute, and the subunits other than those have different attributes. In some embodiments, the attributes of a subunit include one or more of the following: subunit identifier; subunit order; subunit index; subunit priority; reliable transmission requirement corresponding to the subunit; priority transmission requirement corresponding to the subunit; importance corresponding to the subunit; data transmission type corresponding to the subunit; guaranteed bit error rate of the subunit; decoding method corresponding to the subunit; reporting method corresponding to the subunit; segmentation method corresponding to the subunit; padding and addition method corresponding to the subunit.

[0421] It should be noted that the description of data units and sub-units can be found in other embodiments of this application, and will not be repeated here.

[0422] In some embodiments, different sub-units within at least two sub-units multiplex different LCHs or different service data, or, different sub-units within at least two sub-units are used to transmit different LCHs or different service data. In some embodiments, identical sub-units within at least two sub-units multiplex different LCHs or different service data, or, identical sub-units within at least two sub-units are used to transmit different LCHs or different service data. In some embodiments, different LCHs are multiplexed to different sub-units within at least two sub-units based on a first mapping relationship; or, different service data are multiplexed to different sub-units within at least two sub-units based on a second mapping relationship. The first mapping relationship includes a mapping relationship and / or mapping restrictions between at least one LCH and at least one sub-unit, and the second mapping relationship includes a mapping relationship and / or mapping restrictions between at least one service data and at least one sub-unit.

[0423] In some embodiments, sub-units with different attributes carry different LCH or service data; or, sub-units with different attributes preferentially carry different LCH or service data. In some embodiments, sub-units with the same attributes carry the same LCH or service data; or, sub-units with the same attributes preferentially carry the same LCH or service data. In some embodiments, sub-units with different attributes carry different characteristics of LCH or service data; or, sub-units with different attributes preferentially carry different characteristics of LCH or service data. In some embodiments, sub-units with the same attributes carry the same characteristics of LCH or service data; or, sub-units with the same attributes preferentially carry the same characteristics of LCH or service data.

[0424] It should be noted that for the introduction of sub-unit multiplexing of LCH / service data, please refer to the relevant content in other embodiments of this application, and will not be repeated here.

[0425] In some embodiments, data packets corresponding to all or some of the sub-units in at least two sub-units are segmented based on data packet boundaries, and / or, data packets carried or multiplexed by all or some of the sub-units in at least two sub-units are determined based on data packet boundaries, and / or, all or some of the sub-units in at least two sub-units are segmented or divided based on data packet boundaries, and / or, data packet boundaries or the sub-units to which one or more data packets are multiplexed are determined based on the boundaries of all or some of the sub-units in at least two sub-units. In some embodiments, data packet boundaries are used to prevent data packets carried by all or some of the sub-units from being segmented.

[0426] In some embodiments, the size information of all or some of the sub-units in at least two sub-units is determined based on packet boundaries, and / or, the information on the amount of data carried by all or some of the sub-units in at least two sub-units is determined based on packet boundaries. In some embodiments, packet boundaries are used to prevent the data packets carried by all or some of the sub-units from being segmented.

[0427] In some embodiments, the receiving module 1201 is configured to receive segmentation information of data packets carried by at least two sub-units, and / or receive information on the amount of data carried by at least two sub-units, and / or receive size information of at least two sub-units.

[0428] In some embodiments, padding bits are added to all or some of the sub-units in at least two sub-units. In some embodiments, the padding bits are used to prevent the data packets carried by all or some sub-units from being segmented. In some embodiments, the receiving module 1201 is used to receive padding information of the padding bits.

[0429] It should be noted that for an introduction to data packet segmentation, please refer to the relevant content in other embodiments of this application, and will not be repeated here.

[0430] It should be noted that the device provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0431] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0432] Figure 13 is a schematic diagram of the structure of a communication device (terminal device or network device) provided in an embodiment of this application. The communication device may include: a processor 1301, a receiver 1302, a transmitter 1303, a memory 1304, and a bus 1305.

[0433] The processor 1301 includes one or more processing cores. The processor 1301 executes various functional applications and information processing by running software programs and modules.

[0434] The receiver 1302 and the transmitter 1303 can be implemented as a transceiver 1306, which can be a communication chip.

[0435] The memory 1304 is connected to the processor 1301 via a bus 1305. The memory 1304 can be used to store computer programs, and the processor 1301 can be used to execute the computer programs to implement the various steps performed by the second communication device or terminal in the above method embodiments.

[0436] Furthermore, the memory 1304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technologies, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices.

[0437] In some embodiments, when the communication device is implemented as a first communication device, the transmitter 1303 is used to multiplex at least two sub-units to the same data unit, and / or to transmit the at least two sub-units through the same data unit. The transmitter 1303 can also be used to perform other processing-related steps performed by the first communication device in the above embodiments. The receiver 1302 can be used to perform reception-related steps performed by the first communication device in the above embodiments. The processor 1301 can be used to perform processing-related steps performed by the first communication device in the above embodiments.

[0438] In some embodiments, when the communication device is implemented as a second communication device, the receiver 1302 is used to receive a data unit, wherein the data unit multiplexes at least two sub-units, or the at least two sub-units are transmitted through the data unit. The receiver 1302 can also be used to perform other reception-related steps performed by the second communication device in the above embodiments. The transmitter 1303 is used to perform transmission-related steps performed by the second communication device in the above embodiments. The processor 1301 can be used to perform processing-related steps performed by the second communication device in the above embodiments.

[0439] This application also provides a computer-readable storage medium storing a computer program. The computer program is executed by a first communication device to multiplex at least two sub-units into the same data unit, and / or transmit the at least two sub-units through the same data unit. It also implements other steps performed by the first communication device in the above embodiments. Alternatively, the computer program is executed by a second communication device to receive a data unit, where the data unit multiplexes at least two sub-units, or transmit the at least two sub-units through the data unit. It also implements other steps performed by the second communication device in the above embodiments.

[0440] In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0441] This application also provides a chip, which includes programmable logic circuitry and / or program instructions. When the chip operates on a first communication device, it is used to multiplex at least two sub-units into the same data unit, and / or transmit the at least two sub-units through the same data unit. It is also used to perform other steps executed by the first communication device in the above embodiments. And / or, when the chip operates on a second communication device, it is used to receive a data unit, wherein the data unit multiplexes at least two sub-units, or the at least two sub-units transmit through the data unit. It is also used to perform other steps executed by the second communication device in the above embodiments.

[0442] This application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the communication device reads and executes the computer instructions from the computer-readable storage medium to implement the various steps in the above-described data transmission method.

[0443] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0444] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A data transmission method, characterized by, The method is performed by a first communication device, and the method includes: Multiplexing at least two sub-units to the same data unit, and / or transmitting the at least two sub-units through the same data unit.

2. The method of claim 1, wherein, The method further includes: Based on the data packet boundary, segment the data packets corresponding to all or some of the sub-units in the at least two sub-units, and / or, based on the data packet boundary, determine the data packets carried or multiplexed by all or some of the sub-units in the at least two sub-units, and / or, based on the data packet boundary, segment or divide all or some of the sub-units in the at least two sub-units, and / or, based on the boundary of all or some of the sub-units in the at least two sub-units, determine the data packet boundary or determine the sub-units to which one or more data packets are multiplexed.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The size information of all or some of the sub-units in the at least two sub-units is determined based on the data packet boundary, and / or the amount of data carried by all or some of the sub-units in the at least two sub-units is determined based on the data packet boundary.

4. The method according to claim 2 or 3, characterized in that, The data packet boundary is used to prevent the data packets carried by all or part of the sub-units from being segmented.

5. The method of claim 2, wherein, The steps of segmenting data packets corresponding to all or some of the at least two sub-units based on data packet boundaries, and / or determining data packets carried or multiplexed by all or some of the at least two sub-units based on data packet boundaries, and / or segmenting or dividing all or some of the at least two sub-units based on data packet boundaries, and / or determining data packet boundaries or determining one or more data packets multiplexed sub-units based on the boundaries of all or some of the at least two sub-units, include: Based on the data packet boundary, segment the data packets corresponding to the sub-units with the same attributes in the at least two sub-units, and / or, based on the data packet boundary, determine the data packets carried or multiplexed by the sub-units with the same attributes in the at least two sub-units, and / or, based on the data packet boundary, segment or divide the sub-units with the same attributes in the at least two sub-units, and / or, based on the boundary of the sub-units with the same attributes in the at least two sub-units, determine the data packet boundary or determine the sub-units to which one or more data packets are multiplexed.

6. The method of claim 2, wherein, The steps of segmenting data packets corresponding to all or some of the at least two sub-units based on data packet boundaries, and / or determining data packets carried or multiplexed by all or some of the at least two sub-units based on data packet boundaries, and / or segmenting or dividing all or some of the at least two sub-units based on data packet boundaries, and / or determining data packet boundaries or determining one or more data packets multiplexed sub-units based on the boundaries of all or some of the at least two sub-units, include: Based on the data packet boundary, segment the data packets corresponding to the first X sub-units in the at least two sub-units, and / or, based on the data packet boundary, determine the data packets carried or multiplexed by the first X sub-units in the at least two sub-units, and / or, based on the data packet boundary, segment or divide the first X sub-units in the at least two sub-units, and / or, based on the boundary of the first X sub-units in the at least two sub-units, determine the data packet boundary or determine the sub-units in which one or more data packets are multiplexed, where X is a positive integer.

7. The method of claim 3, wherein, The determination of the size information of all or part of the sub-units in the at least two sub-units based on the data packet boundary, and / or the determination of the amount of data carried by all or part of the sub-units in the at least two sub-units based on the data packet boundary, includes: Based on the data packet boundary, determine the size information of the sub-units with the same attributes among the at least two sub-units, and / or, based on the data packet boundary, determine the information on the amount of data carried by the sub-units with the same attributes among the at least two sub-units.

8. The method of claim 3, wherein, The determination of the size information of all or part of the sub-units in the at least two sub-units based on the data packet boundary, and / or the determination of the amount of data carried by all or part of the sub-units in the at least two sub-units based on the data packet boundary, includes: Based on the data packet boundary, determine the size information of the first Y sub-units in the at least two sub-units, and / or, based on the data packet boundary, determine the data volume information carried by the first Y sub-units in the at least two sub-units, where Y is a positive integer.

9. The method according to any one of claims 2 to 8, characterized in that, The method further includes: Send segmentation information of the data packets carried by the at least two sub-units, and / or send information on the amount of data carried by the at least two sub-units, and / or send information on the size of the at least two sub-units.

10. The method according to any one of claims 1 to 9, characterized in that, All or some of the at least two sub-units are obtained by segmenting based on data packet boundaries.

11. The method according to any one of claims 2 to 10, characterized in that, The data packet boundary is the boundary of the Service Data Unit (SDU) or the boundary of the SDU segment.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: Add padding bits to all or some of the at least two sub-units.

13. The method according to claim 12, characterized in that, The padding bits are used to prevent the data packets carried by all or part of the sub-units from being segmented.

14. The method according to claim 12 or 13, characterized in that, Adding padding bits to all or some of the at least two sub-units includes: The padding bit is added to the first sub-unit according to the amount of data corresponding to the first sub-unit among the at least two sub-units; or, the padding bit is added to the first sub-unit according to the size of the first sub-unit among the at least two sub-units. The amount of data corresponding to the first sub-unit is determined by the first communication device or by the second communication device, and the size of the first sub-unit is determined by the first communication device or by the second communication device.

15. The method according to claim 14, characterized in that, The step of adding the padding bits to the first sub-unit based on the data amount corresponding to the first sub-unit among the at least two sub-units includes: When the first data quantity corresponding to the first sub-unit is less than the second data quantity corresponding to the first sub-unit, the padding bit is added to the first sub-unit; Wherein, the first data volume is determined by the first communication device, and the second data volume is determined by the second communication device; or, the first data volume is the data volume or the sum of data volumes that are allowed to carry or support carrying or multiplexing or multiplexing data packets in the first subunit, or the data volume or the sum of data volumes that are allowed to carry or support carrying or multiplexing or multiplexing or multiplexing complete data packets in the first subunit, and the second data volume is the size of the first subunit or the data volume corresponding to the first subunit.

16. The method according to any one of claims 12 to 15, characterized in that, Adding padding bits to all or some of the at least two sub-units includes: The padding bits are added to all or some of the first Z sub-units of the at least two sub-units, where Z is a positive integer.

17. The method according to any one of claims 12 to 16, characterized in that, The method further includes: Send the padding information for the padding bits.

18. The method according to any one of claims 1 to 17, characterized in that, The method further includes: Different logical channels (LCHs) or different service data are multiplexed to different sub-units of the at least two sub-units, or the different LCHs or the different service data are transmitted through different sub-units of the at least two sub-units.

19. The method according to claim 18, characterized in that, The multiplexing of different LCHs or different service data to different sub-units of the at least two sub-units includes: According to the first mapping relationship, the different LCHs are multiplexed to different sub-units in the at least two sub-units; or... According to the second mapping relationship, the different business data are reused to different sub-units in the at least two sub-units; The first mapping relationship includes a mapping relationship and / or mapping restrictions between at least one LCH and at least one sub-unit, and the second mapping relationship includes a mapping relationship and / or mapping restrictions between at least one service data and the at least one sub-unit.

20. The method according to claim 19, characterized in that, The first mapping relationship includes the mapping relationship between the first parameter of the at least one LCH and the second parameter of the at least one subunit; The first parameter includes at least one of the following: LCH identifier, LCH index, LCH sequence number ID, LCH priority, LCH priority bit rate (PBR), LCH corresponding service, LCH corresponding reliable transmission requirement, LCH corresponding priority transmission requirement, whether LCH contains delay-sensitive data, whether LCH contains delay report data, whether LCH uses additional LCH priority, LCH corresponding importance, whether LCH requires a preset decoding method, and whether LCH data packets do not support or are not allowed to be segmented. The second parameter includes at least one of the following: sub-unit identifier, sub-unit sorting, sub-unit index, sub-unit priority, sub-unit corresponding reliable transmission requirement, sub-unit corresponding priority transmission requirement, sub-unit corresponding importance, sub-unit corresponding data transmission type, sub-unit guaranteed bit error rate, sub-unit corresponding decoding method, sub-unit corresponding reporting method, sub-unit corresponding segmentation method, and sub-unit corresponding padding method.

21. The method according to claim 19 or 20, characterized in that, The second mapping relationship includes the mapping relationship between the third parameter of the at least one business data and the second parameter of the at least one sub-unit; The third parameter includes at least one of the following: service data identifier, service data index, service data ID, service data priority, service data PBR, service corresponding to the service data, reliable transmission requirement corresponding to the service data, priority transmission requirement corresponding to the service data, whether the service data contains delay-sensitive data, whether the service data contains delay report data, whether the service data uses additional service data priority, importance corresponding to the service data, whether the service data requires a preset decoding method, and whether the data packet of the service data does not support or allow segmented transmission. The second parameter includes at least one of the following: sub-unit identifier, sub-unit sorting, sub-unit index, sub-unit priority, reliable transmission requirement corresponding to the sub-unit, priority transmission requirement corresponding to the sub-unit, importance corresponding to the sub-unit, data transmission type corresponding to the sub-unit, bit error rate guaranteed by the sub-unit, decoding method corresponding to the sub-unit, reporting method corresponding to the sub-unit, segmentation method corresponding to the sub-unit, and padding method corresponding to the sub-unit.

22. The method according to any one of claims 19 to 21, characterized in that, The step of multiplexing the different LCHs to different sub-units in the at least two sub-units according to the first mapping relationship includes: Map the LCH that has or is configured with the first mapping relationship to the sub-unit indicated by the first mapping relationship; or, Multiplex the LCH that has or is configured with the first mapping relationship to the sub-unit indicated by the first mapping relationship; or, The LCH that has or is configured with the first mapping relationship is preferentially mapped to the sub-unit indicated by the first mapping relationship; or, The LCH that has or is configured with the first mapping relationship is preferentially reused to the sub-unit indicated by the first mapping relationship.

23. The method according to any one of claims 19 to 22, characterized in that, The first LCH does not support reuse in a subunit with the first attribute; or, The first LCH supports reuse in sub-units that do not have the first attribute; or, The first LCH does not support preferential reuse in sub-units with the first attribute; or, The first LCH can be multiplexed in any sub-unit; The first LCH includes LCHs that do not exist or have not been configured with the first mapping relationship.

24. The method according to any one of claims 19 to 23, characterized in that, The second LCH does not support reuse in subunits with a second attribute; or, The second LCH supports reuse in subunits that do not have the second attribute; or, The second LCH does not support preferential reuse in subunits with the second attribute; Wherein, the second LCH exists or is configured with the first mapping relationship, and the first mapping relationship indicates that the sub-unit set corresponding to the second LCH is 0.

25. The method according to any one of claims 18 to 24, characterized in that, Sub-units with different attributes carry different LCH or service data; or, Sub-units with different attributes may preferentially carry different LCH or service data.

26. The method according to any one of claims 18 to 25, characterized in that, Sub-units with the same attributes carry the same LCH or service data; or, Sub-units with the same attributes are given priority to carry the same LCH or service data.

27. The method according to any one of claims 1 to 26, characterized in that, The at least two sub-units have the same property, or the at least two sub-units have different properties, or some of the sub-units in the at least two sub-units have the same property, and the sub-units other than the partial sub-units have different properties from the partial sub-units.

28. The method according to any one of claims 1 to 27, characterized in that, The attributes of the sub-unit include one or more of the following: Sub-unit identifier; Sub-unit sorting; Sub-unit index; Sub-unit priority; Reliable transmission requirements corresponding to the sub-unit; Priority transmission requirements corresponding to the sub-unit; Importance of the sub-unit; Data transmission type corresponding to the sub-unit; The bit error rate guaranteed by the sub-unit; the decoding method corresponding to the sub-unit; the reporting method corresponding to the sub-unit; the segmentation method corresponding to the sub-unit; and the padding and addition method corresponding to the sub-unit.

29. The method according to any one of claims 1 to 28, characterized in that, One of the at least two sub-units is one of the following: transport block TB, coding block CB, coding block group CBG, sub-data channel, hybrid automatic repeat request (HARQ) process, HARQ sub-process, and codeword CW.

30. The method according to any one of claims 1 to 29, characterized in that, The data unit is one of the following: dynamically authorized DG resources, configured authorized CG resources, physical uplink shared channel (PUSCH), CW, TB, data channel, and HARQ process.

31. The method according to any one of claims 1 to 30, characterized in that, The method is executed by the first Media Access Control (MAC) entity of the first communication device.

32. A data transmission method, characterized in that, The method is performed by a second communication device, and the method includes: A receiving data unit, wherein at least two sub-units are multiplexed in the data unit, or wherein the at least two sub-units are transmitted through the data unit.

33. The method according to claim 32, characterized in that, The data packets corresponding to all or some of the at least two sub-units are segmented based on data packet boundaries, and / or the data packets carried or multiplexed by all or some of the at least two sub-units are determined based on the data packet boundaries, and / or all or some of the at least two sub-units are segmented or divided based on the data packet boundaries, and / or the data packet boundaries or the sub-units to which one or more data packets are multiplexed are determined based on the boundaries of all or some of the at least two sub-units.

34. The method according to claim 32 or 33, characterized in that, The size information of all or some of the at least two sub-units is determined based on the data packet boundary, and / or the information on the amount of data carried by all or some of the at least two sub-units is determined based on the data packet boundary.

35. The method according to claim 33 or 34, characterized in that, The data packet boundary is used to prevent the data packets carried by all or part of the sub-units from being segmented.

36. The method according to claim 33, characterized in that, The data packets corresponding to the sub-units with the same attributes in the at least two sub-units are segmented based on the data packet boundary, and / or the data packets carried or multiplexed by the sub-units with the same attributes in the at least two sub-units are determined based on the data packet boundary, and / or the sub-units with the same attributes in the at least two sub-units are segmented or divided based on the data packet boundary, and / or the data packet boundary or the sub-units to which one or more data packets are multiplexed are determined based on the boundary of the sub-units with the same attributes in the at least two sub-units.

37. The method according to claim 33, characterized in that, The data packets corresponding to the first X sub-units of the at least two sub-units are segmented based on the data packet boundaries, and / or the data packets carried or multiplexed by the first X sub-units of the at least two sub-units are determined based on the data packet boundaries, and / or the first X sub-units of the at least two sub-units are segmented or divided based on the data packet boundaries, and / or the data packet boundaries or the sub-units to which one or more data packets are multiplexed are determined based on the boundaries of the first X sub-units of the at least two sub-units, where X is a positive integer.

38. The method according to claim 34, characterized in that, The size information of the sub-units with the same attributes among the at least two sub-units is determined based on the data packet boundary, and / or the information on the amount of data carried by the sub-units with the same attributes among the at least two sub-units is determined based on the data packet boundary.

39. The method according to claim 34, characterized in that, The size information of the first Y sub-units in the at least two sub-units is determined based on the data packet boundary, and / or the information of the amount of data carried by the first Y sub-units in the at least two sub-units is determined based on the data packet boundary, where Y is a positive integer.

40. The method according to any one of claims 33 to 39, characterized in that, The method further includes: Receive segmentation information of the data packets carried by the at least two sub-units, and / or receive information on the amount of data carried by the at least two sub-units, and / or receive size information of the at least two sub-units.

41. The method according to any one of claims 32 to 40, characterized in that, All or some of the at least two sub-units are obtained by segmenting based on data packet boundaries.

42. The method according to any one of claims 33 to 41, characterized in that, The data packet boundary is the boundary of the SDU or the boundary of the SDU segment.

43. The method according to any one of claims 32 to 42, characterized in that, Padding bits are added to all or some of the at least two sub-units.

44. The method according to claim 43, characterized in that, The padding bits are used to prevent the data packets carried by all or part of the sub-units from being segmented.

45. The method according to claim 43 or 44, characterized in that, The padding bits are added to the first sub-unit according to the amount of data corresponding to the first sub-unit among the at least two sub-units; or, the padding bits are added to the first sub-unit according to the size of the first sub-unit among the at least two sub-units. The amount of data corresponding to the first subunit is determined by the first communication device or the second communication device, and the size of the first subunit is determined by the first communication device or the second communication device.

46. ​​The method according to claim 45, characterized in that, The padding bit is added to the first sub-unit when the first data amount corresponding to the first sub-unit is less than the second data amount corresponding to the first sub-unit. Wherein, the first data volume is determined by the first communication device, and the second data volume is determined by the second communication device; or, the first data volume is the data volume or the sum of data volumes that are allowed to carry or support carrying or multiplexing or multiplexing data packets in the first subunit, or the data volume or the sum of data volumes that are allowed to carry or support carrying or multiplexing or multiplexing or multiplexing complete data packets in the first subunit, and the second data volume is the size of the first subunit or the data volume corresponding to the first subunit.

47. The method according to any one of claims 43 to 46, characterized in that, The padding bits are added to all or some of the first Z sub-units of the at least two sub-units, where Z is a positive integer.

48. The method according to any one of claims 43 to 47, characterized in that, The method further includes: Receive the padding information of the padding bits.

49. The method according to any one of claims 32 to 48, characterized in that, Different subunits in the at least two subunits may reuse different LCHs or different service data, or different subunits in the at least two subunits may be used to transmit the different LCHs or the different service data.

50. The method according to claim 49, characterized in that, The different LCHs are multiplexed to different sub-units among the at least two sub-units based on the first mapping relationship; or... The different business data are reused to different sub-units in the at least two sub-units based on the second mapping relationship; The first mapping relationship includes a mapping relationship and / or mapping restrictions between at least one LCH and at least one sub-unit, and the second mapping relationship includes a mapping relationship and / or mapping restrictions between at least one service data and the at least one sub-unit.

51. The method according to claim 50, characterized in that, The first mapping relationship includes the mapping relationship between the first parameter of the at least one LCH and the second parameter of the at least one subunit; The first parameter includes at least one of the following: LCH identifier, LCH index, LCH ID, LCH priority, LCH PBR, LCH corresponding service, LCH corresponding reliable transmission requirement, LCH corresponding priority transmission requirement, whether LCH contains delay-sensitive data, whether LCH contains delay report data, whether LCH uses additional LCH priority, LCH corresponding importance, whether LCH requires a preset decoding method, and whether LCH data packets do not support or are not allowed to be segmented. The second parameter includes at least one of the following: sub-unit identifier, sub-unit sorting, sub-unit index, sub-unit priority, sub-unit corresponding reliable transmission requirement, sub-unit corresponding priority transmission requirement, sub-unit corresponding importance, sub-unit corresponding data transmission type, sub-unit guaranteed bit error rate, sub-unit corresponding decoding method, sub-unit corresponding reporting method, sub-unit corresponding segmentation method, and sub-unit corresponding padding method.

52. The method according to claim 50 or 51, characterized in that, The second mapping relationship includes the mapping relationship between the third parameter of the at least one business data and the second parameter of the at least one sub-unit; The third parameter includes at least one of the following: service data identifier, service data index, service data ID, service data priority, service data PBR, service corresponding to the service data, reliable transmission requirement corresponding to the service data, priority transmission requirement corresponding to the service data, whether the service data contains delay-sensitive data, whether the service data contains delay report data, whether the service data uses additional service data priority, importance corresponding to the service data, whether the service data requires a preset decoding method, and whether the data packet of the service data does not support or allow segmented transmission. The second parameter includes at least one of the following: sub-unit identifier, sub-unit sorting, sub-unit index, sub-unit priority, reliable transmission requirement corresponding to the sub-unit, priority transmission requirement corresponding to the sub-unit, importance corresponding to the sub-unit, data transmission type corresponding to the sub-unit, bit error rate guaranteed by the sub-unit, decoding method corresponding to the sub-unit, reporting method corresponding to the sub-unit, segmentation method corresponding to the sub-unit, and padding method corresponding to the sub-unit.

53. The method according to any one of claims 50 to 52, characterized in that, The LCH that has or is configured with the first mapping relationship is mapped to the sub-unit indicated by the first mapping relationship; or, The LCH that exists or is configured with the first mapping relationship is multiplexed to the sub-unit indicated by the first mapping relationship; or, LCHs that have or are configured with the first mapping relationship are preferentially mapped to the sub-cells indicated by the first mapping relationship; or, The LCH that has or is configured with the first mapping relationship is preferentially reused to the sub-unit indicated by the first mapping relationship.

54. The method according to any one of claims 50 to 53, characterized in that, The first LCH does not support reuse in a subunit with the first attribute; or, The first LCH supports reuse in sub-units that do not have the first attribute; or, The first LCH does not support preferential reuse in sub-units with the first attribute; or, The first LCH can be multiplexed in any sub-unit; The first LCH includes LCHs that do not exist or have not been configured with the first mapping relationship.

55. The method according to any one of claims 50 to 54, characterized in that, The second LCH does not support reuse in subunits with a second attribute; or, The second LCH supports reuse in subunits that do not have the second attribute; or, The second LCH does not support preferential reuse in subunits with the second attribute; Wherein, the second LCH exists or is configured with the first mapping relationship, and the first mapping relationship indicates that the sub-unit set corresponding to the second LCH is 0.

56. The method according to any one of claims 49 to 55, characterized in that, Sub-units with different attributes carry different LCH or service data; or, Sub-units with different attributes may preferentially carry different LCH or service data.

57. The method according to any one of claims 49 to 56, characterized in that, Sub-units with the same attributes carry the same LCH or service data; or, Sub-units with the same attributes are given priority to carry the same LCH or service data.

58. The method according to any one of claims 32 to 57, characterized in that, The at least two sub-units have the same property, or the at least two sub-units have different properties, or some of the sub-units in the at least two sub-units have the same property, and the sub-units other than the partial sub-units have different properties from the partial sub-units.

59. The method according to any one of claims 32 to 58, characterized in that, The attributes of the sub-unit include one or more of the following: Sub-unit identifier; Sub-unit sorting; Sub-unit index; Sub-unit priority; Reliable transmission requirements corresponding to the sub-unit; Priority transmission requirements corresponding to the sub-unit; Importance of the sub-unit; Data transmission type corresponding to the sub-unit; The bit error rate guaranteed by the sub-unit; the decoding method corresponding to the sub-unit; the reporting method corresponding to the sub-unit; the segmentation method corresponding to the sub-unit; and the padding and addition method corresponding to the sub-unit.

60. The method according to any one of claims 32 to 59, characterized in that, One of the at least two sub-units is one of TB, CB, CBG, sub-data channel, HARQ process, HARQ sub-process, and CW.

61. The method according to any one of claims 32 to 60, characterized in that, The data unit is one of DG resources, CG resources, PUSCH, CW, TB, data channel, or HARQ process.

62. The method according to any one of claims 31 to 61, characterized in that, The method is executed by the second MAC entity of the second communication device.

63. A first device, characterized in that, The first device includes: A transmitting module is used to multiplex at least two sub-units into the same data unit, and / or to transmit the at least two sub-units through the same data unit.

64. A second device, characterized in that, The second device includes: A receiving module is used to receive a data unit, wherein the data unit multiplexes at least two sub-units, or the at least two sub-units are transmitted through the data unit.

65. A first communication device, characterized in that, The first communication device includes: processor; A transceiver connected to the processor; The transceiver is used to multiplex at least two sub-units into the same data unit, and / or to transmit the at least two sub-units through the same data unit.

66. A second communication device, characterized in that, The second communication device includes: processor; A transceiver connected to the processor; The transceiver is used to receive data units, wherein at least two sub-units are multiplexed in the data unit, or the at least two sub-units are transmitted through the data unit.

67. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that is executed by a processor to implement the data transmission method according to any one of claims 1 to 62.

68. A chip, characterized in that, The chip includes programmable logic circuits and / or program instructions, which, when the chip is running on a communication device, are used to multiplex at least two sub-units to the same data unit, and / or to transmit the at least two sub-units through the same data unit.

69. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium; the processor of the communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the communication device to implement the data transmission method according to any one of claims 1 to 62.

70. A computer program, characterized in that, The computer program is executed by the processor of the communication device to implement the data transmission method according to any one of claims 1 to 62.

Images