Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus. The communication method comprises: acquiring a first MAC subPDU; and if the first MAC subPDU comprises a reserved value or an invalid value or an unsupported value, executing any one of the following operations: discarding the first MAC subPDU; and discarding the first MAC subPDU and an MAC subPDU associated with a first CB or a first CB group and subsequent to the first MAC subPDU, wherein the first CB or the first CB group is a CB or a CB group associated with the first MAC subPDU or the reserved value or the invalid value or the unsupported value. By means of the technical solution, the communication quality can be improved.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411397895.7, filed on September 30, 2024, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method and a communication device. Background Technology

[0003] In a wireless communication system, after the physical layer at the transmitting end obtains the transport block (TB), it can add a cyclic redundancy check (CRC) to the TB. If the TB (or TB and TB CRC) is large, the TB and TB CRC are divided into multiple code blocks (CBs), and a CB CRC is added to each CB. For the receiving end, the physical layer verifies the CB CRC and the TB CRC. If all CB CRCs are successfully verified and the TB CRC is also verified, the physical layer submits the entire TB to the MAC layer.

[0004] Based on the current data processing procedure, at the receiving end, if the received medium access control sub-protocol data unit (MAC subPDU) contains a reserved or unsupported logical channel identifier, the receiving end should discard at least the MAC subPDU and all remaining MAC subPDUs in the MAC PDU.

[0005] However, the communication quality is low based on the above methods. Summary of the Invention

[0006] This application provides a communication method and a communication device to improve communication quality.

[0007] In a first aspect, this application provides a communication method, which can be executed by a first communication device, or by a component (such as a chip, chip system, etc.) configured in the first communication device, or by a logic module or software capable of implementing all or part of the functions of the first communication device. This application does not limit the method in this regard.

[0008] The first communication device mentioned above is the end that receives data, also known as the receiving end. For example, the first communication device can be an access network device or a terminal.

[0009] The communication method includes: acquiring a first MAC subPDU; if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, performing any of the following: discarding the first MAC subPDU; or, discarding the first MAC subPDU and a MAC subPDU located after the first MAC subPDU and associated with a first CB or a first CB group, wherein the first CB or the first CB group is a CB or CB group associated with the first MAC subPDU or a reserved value, an invalid value, or an unsupported value.

[0010] Based on the method provided in the first aspect, when the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the receiving end discards the first MAC subPDU. Alternatively, it discards both the first MAC subPDU and the MAC subPDUs located after the first MAC subPDU and associated with the first CB or the first CB group. That is, when the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the receiving end can retain / not discard some MAC subPDUs contained in other CBs or CB groups that are not associated with the first CB or the first CB group. Therefore, when the receiving end performs decoding at the CB or CB group granularity, that is, when each CB or CB group does not depend on other CBs or CB groups, and even if a CB or CB group fails to receive data, it can still submit the subsequently successfully received CBs or CB groups to the MAC layer for continued decoding processing, the receiving end can process successfully received CBs or CB groups in a timely manner. This helps reduce service latency and also improves the correct data reception rate or data reliability, thereby improving communication quality.

[0011] For example, reserved, invalid, or unsupported values ​​include: reserved, invalid, or unsupported logical channel identifier values.

[0012] For example, a logical channel identifier is a logical channel identifier (LCID) or an extended LCID (eLCID).

[0013] In one possible design, discarding the first MAC subPDU and the MAC subPDU that follows the first MAC subPDU and is associated with the first CB or the first CB group includes: discarding the first MAC subPDU and at least one MAC subPDU that follows the first MAC subPDU and is located in the first CB or the first CB group.

[0014] In this possible design, all MAC subPDUs associated with the first CB or the first CB group are contained in the first CB or the first CB group, or it can be understood that all bits of the MAC subPDUs associated with the first CB or the first CB group are located in the first CB or the first CB group.

[0015] The above-mentioned discarding of at least one MAC subPDU located after the first MAC subPDU and within the first CB or the first CB group can be replaced by: discarding all MAC subPDUs located after the first MAC subPDU in the first CB or the first CB group. Alternatively, it can be replaced by: discarding all remaining MAC subPDUs located after the first MAC subPDU in the first CB or the first CB group.

[0016] For example, the first MAC subPDU is a MAC subPDU in the first MAC PDU. The first MAC PDU corresponds to N CBs or CB groups. When each CB or CB group in the N CBs or CB groups is associated with a complete MAC subPDU, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the first MAC subPDU and all remaining MAC subPDUs in the first CB or the first CB group that are located after the first MAC subPDU are discarded.

[0017] Based on this possible design, the receiver can discard at the granularity of CB or CB group, thereby improving the efficiency of the receiver in determining all remaining MAC subPDUs after the first MAC subPDU.

[0018] In one possible design, discarding the first MAC subPDU and the MAC subPDU that follows the first MAC subPDU and is associated with the first CB or the first CB group includes: discarding the first MAC subPDU, a first set of bits in the first CB or the first CB group that follows the first MAC subPDU, and a second set of bits that follows the first set of bits and precedes a first start position; wherein the first start position is the position of the “start portion of the MAC subPDU” associated with the second CB or the second CB group, and the second CB or the second CB group is located after the first CB or the first CB group.

[0019] Optionally, the second CB or the second CB group contains information about the location of the "start portion of the MAC subPDU".

[0020] Based on this possible design, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, and if the first CB or the first CB group includes an incomplete MAC subPDU, the receiving end can discard the MAC subPDU associated with the first CB or the first CB group based on the position of the "start portion of the MAC subPDU" associated with the second CB or the second CB group.

[0021] In one possible design, discarding the first MAC subPDU and the MAC subPDU that follows the first MAC subPDU and is associated with the first CB or the first CB group includes: discarding the first MAC subPDU, the first set of bits in the first CB or the first CB group that follows the first MAC subPDU, and the third set of bits that follows the first set of bits and precedes the first boundary identification information; wherein the first boundary identification information is the first boundary identification information associated with the third CB or the third CB group, and the third CB or the third CB group is located after the first CB or the first CB group.

[0022] Optionally, the first boundary identification information includes a first boundary identifier and / or first verification information.

[0023] Optionally, the first MAC PDU contains first boundary identification information.

[0024] Based on this possible design, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, and if the first CB or the first CB group includes an incomplete MAC subPDU, the receiving end can discard the MAC subPDU associated with the first CB or the first CB group based on the first boundary identification information associated with the third CB or the third CB group.

[0025] [Detailed Rules 91, 09.05.2026] Optionally, the method further includes: determining that the first MAC PDU supports CB or CB group self-decoding, wherein the first MAC subPDU is a MAC subPDU in the first MAC PDU.

[0026] Based on this possible design, the receiving end only executes the aforementioned scheme of discarding MAC subPDUs if it determines that the first MAC PDU supports CB or CB group self-decoding. In other words, if it is determined that the first MAC PDU does not support CB or CB group self-decoding, then the first MAC subPDU and all remaining MAC subPDUs following it are discarded. This possible design allows the receiving end to discard MAC subPDUs in multiple ways, providing high flexibility.

[0027] Secondly, this application provides a communication method, which can be executed by a first communication device, or by a component (such as a chip, chip system, etc.) configured in the first communication device, or by a logic module or software capable of implementing all or part of the functions of the first communication device. This application does not limit the method in this regard.

[0028] The first communication device mentioned above is the end that receives data, also known as the receiving end. For example, the first communication device can be an access network device or a terminal.

[0029] The communication method includes: receiving a first MAC subPDU; if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, sending a first confirmation message, wherein the first confirmation message is used to indicate that the first MAC PDU was successfully received or that the first MAC PDU no longer needs to be retransmitted, and the first MAC PDU is a MAC PDU containing the first MAC subPDU.

[0030] Based on the method provided in the second aspect, decoding can be performed at the receiver at the granularity of CB or CB group. That is, each CB or CB group does not depend on other CBs or CB groups, and even if a CB or CB group fails to be received, the CB or CB group that is received later can still be submitted to the MAC layer for continued decoding. This allows the receiver to process the received CB or CB group in a timely manner, which helps to reduce service latency and also reduces unnecessary HARQ retransmissions. This helps to reduce communication overhead and reduce the power consumption of the receiver.

[0031] For example, reserved, invalid, or unsupported values ​​include: reserved, invalid, or unsupported logical channel identifier values.

[0032] For example, a logical channel identifier may be an LCID or an eLCID.

[0033] [Detailed Rule 91, 09.05.2026] In one possible design, the method further includes: stopping the processing of the remaining MAC subPDUs or the remaining code blocks CB associated with the first MAC PDU; and / or discarding the remaining MAC subPDUs or the remaining CB associated with the first MAC PDU.

[0034] Based on this possible design, the power consumption of the receiver decoding can be reduced by stopping the processing of the remaining MAC subPDUs or the remaining code blocks CB associated with the first MAC PDU; and / or discarding the remaining MAC subPDUs or the remaining CB associated with the first MAC PDU.

[0035] [Detailed Rules Article 91, 09.05.2026] In a third aspect, a communication device is provided for implementing various methods. The communication device includes modules, units, or means corresponding to the implementation of the methods, wherein the modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0036] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively used to implement the receiving function and the transmitting function in any of the above aspects and any possible implementations thereof.

[0037] In some possible designs, the transceiver module can consist of transceiver circuits, transceivers, transceivers, or communication interfaces.

[0038] [Detailed Rules 91, 09.05.2026] In a fourth aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer instructions, which, when executed by the processor, cause the communication device to perform any of the above aspects and any possible design methods thereof.

[0039] [Detailed Rules 91, 09.05.2026] In a fifth aspect, a communication device is provided, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute computer programs or instructions to cause the communication device to perform any of the above aspects and any possible design methods thereof.

[0040] [Detailed Rules 91, 09.05.2026] In a sixth aspect, a communication device is provided, comprising: at least one processor; the processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform any of the foregoing aspects and any possible design methods thereof. The memory may be coupled to the processor, or may be independent of the processor.

[0041] In a seventh aspect, a communication device (e.g., a chip or chip system) is provided, the communication device including a processor for implementing the functions involved in any of the above aspects and any possible designs thereof.

[0042] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0043] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

[0044] [Detailed Rules 91, 09.05.2026] Wherein, the communication device of the third to seventh aspects can be the first communication device in the first aspect or the second aspect, or the device contained in the first communication device, such as a chip or chip system.

[0045] Eighthly, a communication device is provided, which may be a first communication device, or a module or unit (e.g., a chip, a chip system, or a circuit) in the first communication device that performs the methods / operations / steps / actions described in the first or second aspect, or a module or unit that can be used in conjunction with the first communication device.

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

[0047] [Detailed Rules 91, 09.05.2026] In a ninth aspect, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform any of the above aspects and any possible design methods thereof.

[0048] [Detailed Rules 91, 09.05.2026] In a tenth aspect, a computer program product containing instructions is provided, which, when run on a communication device, enables the communication device to perform any of the above aspects and any possible design methods thereof.

[0049] The technical effects of any of the design methods in aspects three through ten can be found in the technical effects of different design methods in aspects one or two, and will not be repeated here. Attached Figure Description

[0050] Figure 1 is a schematic diagram of a wireless protocol stack provided in this application;

[0051] Figure 2 is a schematic diagram of downlink data transmission between various protocol layers provided in this application;

[0052] Figure 3 is a schematic diagram of an LCP provided in this application;

[0053] Figure 4 is a schematic diagram of a resource allocation process provided in this application;

[0054] Figure 5 is a schematic diagram of a downlink MAC PDU provided in this application;

[0055] Figure 6 is a schematic diagram of an uplink MAC PDU provided in this application;

[0056] Figures 7-9 are schematic diagrams of the structure of the MAC subheader provided in this application;

[0057] Figure 10 is a schematic diagram of a physical layer TB partitioning provided in this application;

[0058] Figure 11 is a schematic diagram of a CB receiver provided in this application;

[0059] Figure 12 is a schematic diagram of the header structure corresponding to a CB group provided in this application;

[0060] Figure 13 is a schematic diagram of the relationship between CB and MAC subPDU provided in this application;

[0061] Figure 14 is a schematic diagram of the association between boundary identification information and MAC subPDU provided in this application;

[0062] Figure 15 is a schematic diagram of the structure of a communication system provided in this application;

[0063] Figure 16 is a flowchart illustrating the communication method provided in this application;

[0064] Figures 17 to 22 show schematic diagrams of the first communication device discarding the MAC subPDU;

[0065] Figure 23 shows a schematic diagram of the MAC subheader containing the first boundary identification information;

[0066] Figure 24 shows a flowchart illustrating another communication method provided in this application;

[0067] Figures 25 to 27 show structural schematic diagrams of the communication device provided in this application. Detailed Implementation

[0068] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0069] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one" means one or more. "At least two" means two or three or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0070] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features, nor do they limit the number or execution order. Therefore, a feature specified with "first" and "second" may explicitly or implicitly include one or more of that feature. Moreover, the terms "first" and "second" are not necessarily intended to be different.

[0071] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0072] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0073] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

[0074] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0075] [Detailed Rules 91, 09.05.2026] In this application, unless otherwise specified, the same or similar parts between the various embodiments may be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships. The implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0076] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0077] 1. Protocol layer structure:

[0078] For example, currently, communication between terminals and network devices follows a certain protocol layer structure. It can be divided into user plane protocol stack and control plane protocol stack.

[0079] As shown in Figure 1(a), the user plane protocol stack may include a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer.

[0080] As shown in Figure 1(b), the control plane protocol stack may include a radio resource control (RRC) layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer. Furthermore, the control plane protocol stack may also include a non-access-stratum (NAS).

[0081] For example, data processing at each protocol layer is implemented by the corresponding functional entity; for instance, the processing at the PDCP layer is implemented by the corresponding PDCP entity. Furthermore, above the AS layer, there may be an application (APP) layer. Other protocol layers may also exist between the AS layer and the APP layer, without restriction.

[0082] Figure 2 illustrates the transmission of downlink data between the terminal and access network equipment across various protocol layers. Downward arrows represent transmission, and upward arrows represent reception. Furthermore, the protocol layers in Figure 2 can also be understood as corresponding protocol layer entities; for example, the RRC layer can be understood as an RRC entity, and the PDCP layer as a PDCP entity.

[0083] In this process, after the RRC entity of the access network device generates downlink data (also known as signaling, such as an RRC message or RRC protocol data unit (PDU)), the data passes through one or more of the PDCP layer, RLC layer, MAC layer, and PHY layer in sequence, and is transmitted to the terminal via the air interface. After receiving the data at the air interface, the terminal parses the data in the reverse order of the access network device.

[0084] Furthermore, for the sending end, the data received by a certain layer (e.g., MAC, RLC, or PDCP) from the upper layer is called a service data unit (SDU), and the data that the layer delivers to the lower layer is called a PDU. For this layer, the data received from the upper layer and the data delivered to the lower layer may be the same (e.g., transparent transmission) or different (e.g., the data received from the upper layer is encapsulated / processed by this layer to obtain the data delivered to the lower layer).

[0085] For the receiving end, the data received by a certain layer (e.g., RLC, PDCP, SDAP, or RRC) from the lower layer is called PDU, and the data that the layer passes to the upper layer is called SDU. For this layer, the data received from the lower layer and the data passed to the upper layer may be the same (e.g., transparent transmission) or different (e.g., the data received from the lower layer is processed by this layer to obtain the data passed to the upper layer).

[0086] For example, after the RRC entity of the access network device submits the RRC PDU to the PDCP entity, the PDCP entity processes the data (i.e., PDCP SDU) received from the RRC entity (i.e., PDCP PDU) or not, obtaining a PDCP PDU, and then submits the PDCP PDU to the RLC entity. The RLC entity processes the data (i.e., RLC SDU) received from the PDCP entity (i.e., RLC PDU) or not, obtaining an RLC PDU, and then submits the RLC PDU to the MAC entity. The MAC entity processes the data (i.e., MAC SDU) received from the RLC entity (i.e., MAC SDU) or not, obtaining a MAC PDU, and then submits the MAC PDU to the PHY layer. After certain processing at the PHY layer, air interface transmission is performed. For example, the data transmitted over the air interface can be called a transport block (TB). For example, an entity can include / be replaced by: a layer.

[0087] Correspondingly, after the terminal's PHY layer receives the TB, it submits the TB to the MAC entity (the TB can also be called a MAC PDU in the MAC entity). The MAC entity processes the TB or not to obtain a MAC SDU, and submits the MAC SDU to the RLC entity. The RLC entity processes the data received from the MAC entity (i.e., the RLC PDU) or not to obtain an RLC SDU, and submits the RLC SDU to the PDCP entity. The PDCP entity processes the data received from the RLC entity (i.e., the PDCP PDU) or not to obtain a PDCP SDU, and submits the PDCP SDU to the RRC entity. After the data arrives at the RRC entity, the RRC entity can perform RRC decoding or ASN.1 decoding to determine the meaning of the received data (such as a bit string).

[0088] For example, the concepts of "upper layer" and "lower layer" in the embodiments of this application are relative. For instance, taking the RLC layer as an example, the RLC layer can be the lower layer of the RRC layer, but the RLC layer can be the upper layer of the MAC layer. Furthermore, the lower layer of the RRC layer may include any one or more of the following: PHY layer, MAC layer, RLC layer, and PDCP layer.

[0089] It is understandable that the transmission of uplink data between access network devices and terminals across various protocol layers can be understood by referring to the relevant description in Figure 2, which will not be repeated here.

[0090] 2. MAC package:

[0091] For example, MAC packet assembly can also be referred to as multiplexing and assembly. For example, a MAC packet assembly can include two parts: logical channel prioritization (LCP), MAC control element (CE), and multiplexing of MAC control elements and MAC SDUs.

[0092] The LCP or MAC packet is used to determine the data transmitted on newlink resources (e.g., uplink (UL) newlink resources), such as one or more MAC CEs and / or one or more MAC SDUs. The multiplexing of MAC CEs and MAC SDUs is used to multiplex the MAC CEs and / or MAC SDUs determined after performing the LCP procedure into a single MAC PDU.

[0093] 3. LCP process:

[0094] Currently, the LCP process is performed at the granularity of new transmission resources / MAC PDU / TB. For example, after a terminal obtains uplink resources allocated to it by the access network device, the terminal can perform LCP; that is, the terminal obtains a UL new transmission resource and performs LCP once. For example, the terminal's MAC entity can perform LCP based on the TB size. For example, the terminal's MAC entity can include / be replaced by: the terminal.

[0095] It should be noted that in the embodiments of this application, executing LCP may also include / be replaced by executing the LCP process. This will be explained uniformly here and will not be repeated in subsequent embodiments.

[0096] For example, LCP may include B j Maintenance, logical channel selection, and resource allocation are related. As shown in Figure 3, during the LCP process, logical channels (LCHs) are first selected according to LCP constraints (or LCH constraints), and then resources are allocated based on the priority of the selected logical channels (including two rounds of resource allocation). For example, a logical channel can be understood as the channel between the MAC layer and the RLC layer.

[0097] 3.1, B j maintain:

[0098] For example, one logical channel corresponds to one B. j .

[0099] When logical channel j is established, the terminal's MAC entity will send the B corresponding to logical channel j. jInitialize to zero. For each logical channel, the MAC entity sets B before each LCP procedure. j Increase PBR×T. If B j If it is larger than the size of the bucket, then put B... j Set to bucket size; if B j If it is smaller than the size of the bucket, then put B... j Set to the calculated value.

[0100] Where PBR stands for prioritized bit rate. T is the bit rate from B. j The elapsed time since the last / previous increment. The bucket size is PBR × BSD, where BSD is the bucket size duration. PBR and BSD can be configured by the access network equipment to the terminal.

[0101] 3.2 Logical Channel Selection:

[0102] For example, when performing a new transmission, the terminal's MAC entity selects a logical channel that meets all of the following conditions:

[0103] The set of allowed subcarrier spacing (SCS) index values ​​in the allowSCS-List (if configured) includes subcarrier spacing indices associated with UL licenses; and,

[0104] The maxPUSCH-Duration (if configured) is greater than or equal to the physical uplink shared channel (PUSCH) transmission duration associated with the UL authorization; and...

[0105] If the UL grant is configured Grant Type 1, configuredGrantType1Allowed (if configured) is set to TRUE; and,

[0106] allowedServingCells (if configured) include cell information associated with UL authorization; and,

[0107] The allowedCG-List (if configured) includes an index of configured authorizations associated with UL authorizations; and,

[0108] The allowedPHY-PriorityIndex (if configured) includes a priority index associated with dynamic UL authorization; and,

[0109] allowedHARQ-mode (if configured) includes the uplink HARQ mode for the hybrid automatic repeat-request (HARQ) process associated with UL authorization.

[0110] 3.3 Resource Allocation:

[0111] When performing a new transmission, the terminal's MAC entity allocates resources to the selected logical channel in the following manner:

[0112] First round of resource allocation: For the selected logical channel B j For logical channels with a value greater than 0, resources are allocated in descending order of logical channel priority.

[0113] For example, the first round of resource allocation needs to consider meeting PBR requirements to ensure fairness in resource allocation. That is, in the first round of resource allocation, the resources allocated to logical channel j are based on B. j Sure.

[0114] For example, if the PBR of a certain logical channel is configured as "infinite", the terminal's MAC entity will allocate resources for all data available for transmission on that logical channel before satisfying the PBR of the lower priority logical channel.

[0115] For example, after the first round of resource allocation, it is necessary to allocate the B corresponding to logical channel j. j Subtract the total size of the MAC SDU provided by the logical channel j.

[0116] Second round of resource allocation: If there are remaining resources after the first round of resource allocation, data is provided to the selected logical channel in a strictly decreasing priority order until one of the logical channels or UL-authorized data is exhausted.

[0117] It should be noted that the above resource allocation only involves data from the LCH and does not involve MAC CE. When allocating resources for MAC CE and / or data from logical channels, MAC CE or data from logical channels should be prioritized in the following order (listed in descending order of priority):

[0118] Cell radio network temporary identifier (C-RNTI) MAC CE or data from the UL common control channel (CCCH);

[0119] Configured grant confirmation (MAC CE);

[0120] Buffer status report (BSR) MAC CE, except for padding the BSR;

[0121] Single power headroom report (PHP) MAC CE or multiple PHP MAC CE;

[0122] Data from any logical channel, except for data from UL-CCCH;

[0123] Padding BSR MAC CE.

[0124] It is understood that the above order is merely an example, used only to illustrate the priority of allocating resources to MAC CE and data from logical channels (e.g., MAC SDU), and does not constitute any limitation on this application.

[0125] For example, with the access network device as the terminal, the new transmission resource configured / scheduled is uplink resource 1. The terminal will perform new transmission on uplink resource 1. The logical channels selected by the terminal according to the LCP restriction are LCH1, LCH2, and LCH3, with priorities of priority 1, priority 2, and priority 3, respectively, and priority 1 is higher than priority 2, and priority 2 is higher than priority 3. As shown in Figure 4, assuming that in the first round of resource allocation, LCH1 and LCH3 B j Greater than 0, B of LCH2 j If the value is less than 0, then in the first round of resource allocation, resources are allocated to LCH1 and LCH3 in descending order of LCH priority. The resources allocated to LCH1 and LCH3 are determined according to the B priority of the respective LCH. j The allocation is as follows. The numbers 1, 2, 3, and 4 in Figure 4 represent the order of resource allocation.

[0126] After the first round of resource allocation, if there are still remaining resources in uplink resource 1, resources will be allocated in descending order of priority for LCH1, LCH2, and LCH3. That is, resources will be allocated to LCH1 first, and if there are still remaining resources, resources will be allocated to LCH2, and so on, until the resources are exhausted.

[0127] Referring to Figure 4, after the two rounds of resource allocation, all data of LCH1 was allocated to resources, or in other words, all data of LCH1 could be transmitted in this new transmission. Some data of LCH2 and LCH3 were not allocated to resources (as shown by the diagonal fill in Figure 4), or in other words, this part of the data could not be transmitted in this new transmission.

[0128] It should be noted that the example shown in Figure 4 only illustrates the case where the data determined after LCP includes LCH data but excludes MAC CE. In practical applications, there may be situations where both LCH data and MAC CE data need to be transmitted.

[0129] 4. Reuse of MAC CE and MAC SDU:

[0130] The multiplexing of MAC CE and MAC SDU is used to multiplex the MAC CE and / or MAC SDU determined after executing LCP / MAC packet assembly into a single MAC PDU. A MAC PDU consists of one or more MAC subPDUs. For example, the composition of a MAC subPDU may fall into the following four categories:

[0131] Includes only one MAC header (including padding) or only one MAC header (excluding padding);

[0132] It consists of a MAC subheader and a MAC SDU;

[0133] It consists of a MAC subheader and a MAC CE;

[0134] It consists of a MAC header and padding.

[0135] The size of the MAC SDU is variable. Some MAC CEs have a fixed size, while others have a variable size. The padding size is variable and can be zero, meaning padding is optional. Furthermore, in the current MAC PDU, the MAC CEs are placed together.

[0136] For example, Figure 5 shows a schematic diagram of a downlink (DL) MAC PDU. The MAC subPDU containing the MAC CE is placed before the MAC subPDU containing the MAC SDU and the MAC subPDU containing padding. Figure 6 shows a schematic diagram of a UL MAC PDU. The MAC subPDU containing the MAC CE is placed after the MAC subPDU containing the MAC SDU and before the MAC subPDU containing padding.

[0137] A MAC subPDU can include a MAC subheader and a MAC CE, MAC SDU, or padding; that is, a MAC subheader can correspond to a MAC CE, MAC SDU, or padding. For example, the MAC subheader, except for those corresponding to fixed-size MAC CEs, padding, and MAC SDUs containing CCCHs, consists of the fields R / F / LCID / (eLCID) / L. For example, the MAC subheader corresponding to fixed-size MAC CEs and paddings consists of the fields R / LCID / (eLCID). For example, the MAC subheader corresponding to MAC SDUs containing CCCHs consists of the fields R / LCID. Examples:

[0138] LCID: Logical Channel Identifier (LCID) field, used to indicate the logical channel of the MAC SDU corresponding to the MAC subheading, the type of the MAC CE corresponding to the MAC subheading, or the padding corresponding to the MAC subheading. Typically, the LCID field is 6 bits long. If the LCID field is set to 34, the MAC subheading also includes an 8-bit eLCID field; if the LCID field is set to 33, the MAC subheading also includes a 16-bit eLCID field, which follows immediately after the LCID field.

[0139] eLCID: Extended Logical Channel Identifier (eLCID) field, used to indicate the logical channel of the MAC SDU corresponding to the MAC subheader, or to indicate the type of the MAC CE corresponding to the MAC subheader. Typically, the eLCID field is 8 bits or 16 bits long. The eLCID field is optional.

[0140] L: Length field, used to indicate the number of bytes in the MAC SDU corresponding to the MAC subheader, or the number of bytes in the variable-size MAC CE corresponding to the MAC subheader. The size of the L field is indicated by the F field.

[0141] F: Format field, used to indicate the size of the length field L. The size of the F field is 1 bit, a value of 0 indicates that the size of the L field is 8 bits, and a value of 1 indicates that the size of the L field is 16 bits.

[0142] R: Reserved bit. Normally, the value of the R field is set to 0.

[0143] For example, Figure 7 shows the structure of a MAC subheader containing the R / F / LCID / (eLCID) / L fields when the size of the L field is 8 bits. As shown in Figure 7(a), the MAC subheader does not include the eLCID field. As shown in Figure 7(b), the MAC subheader includes the eLCID field, which is 8 bits in size. As shown in Figure 7(c), the MAC subheader includes the eLCID field, which is 16 bits in size.

[0144] For example, Figure 8 shows the structure of a MAC subheader containing the R / F / LCID / (eLCID) / L fields when the size of the L field is 16 bits. As shown in Figure 8(a), the MAC subheader does not include the eLCID field. As shown in Figure 8(b), the MAC subheader includes the eLCID field, which is 8 bits in size. As shown in Figure 8(c), the MAC subheader includes the eLCID field, which is 16 bits in size.

[0145] For example, Figure 9 shows the structure of a MAC subheader that includes the R / LCID / (eLCID) field, as shown in Figure 9(a). The MAC subheader does not include the eLCID field, as shown in Figure 9(b). The MAC subheader includes the eLCID field, which is 8 bits in size.

[0146] For example, the MAC subheader is octet (or byte) aligned.

[0147] For example, the receiver decodes at the MAC subPDU level. For a given MAC subPDU, decoding is required based on the MAC subheader. For instance, the MAC subheader is parsed to determine the structure of the MAC subPDU. Taking the structure of the MAC subheader as shown in Figure 7(a) as an example, the receiver determines the type of logical channel or MAC CE corresponding to the MAC subheader (or determines part or all of the MAC subheader format) based on the LCID field, determines the size of the L field based on the F field of the MAC subheader, and determines the number of bytes P of the MAC SDU or MAC CE corresponding to the MAC subheader based on the L field. Thus, the P bytes following the MAC subheader are determined as a MAC SDU or a MAC CE, and then decoded.

[0148] 5. Physical layer data processing:

[0149] After assembling the MAC PDU at the transmitting end's MAC layer, it submits the MAC PDU to the PHY layer. For example, the MAC PDU can also be called a TB, both representing the same data. For instance, for a given piece of data, it might be called a MAC PDU at the MAC layer and a TB at the PHY layer. After obtaining the TB, as shown in Figure 10(a), the transmitting end adds a cyclic redundancy check (CRC) to the TB. If the TB (or TB and TB CRC) is large, the TB (or TB and TB CRC) is divided into multiple code blocks (CBs), and a CB CRC is added to each CB.

[0150] For example, the number C of CB satisfies the following relationship: if B≤K cb If C = 1, then B > K; cb ,but The first size K′ of CB is: K′=B′ / C.

[0151] Where C is the number of CBs corresponding to one TB. B = A + L1. A is the size of the TB or payload size. L1 is the size of the TB CRC. For example, L1 is 16 bits or 24 bits. K cb This is the maximum value of CB. For example, K. cb It is 8448 bits or 3840 bits. For example, for low-density parity check coding (LDPC) basis graph 1, K cb It is 8448 bits. For example, for LDPC base map 2, K cb It is 3840 bits. L is the size of the CB CRC. For example, L is 24 bits. For example, K′ is the first size of one CB. B′ = B + C·L.

[0152] Understandably, based on the above partitioning principles, the first size of the CB includes the size of the CB's data portion (or payload portion) and the size of the TB CRC, or, includes the size of the CB's data portion and the size of the CB CRC, or, includes the size of the CB's data portion, the size of the TB CRC, and the size of the CB CRC. The first size of the CB does not include the size of padding (e.g., NULL).

[0153] In addition to the first size of CB, CB also has a second size K. The second size of CB includes the size of the data portion of CB, the size of TB CRC, and the size of padding, or, includes the size of the data portion of CB, the size of CB CRC, and the size of padding, or includes the size of the data portion of CB, the size of TB CRC, the size of CB CRC, and the size of padding. The second size of CB may include the size of padding.

[0154] For example, the second size K of CB is determined based on the first size K′ or B of CB. For example, the second size of CB is greater than or equal to the first size of CB.

[0155] For example, if CB does not include padding, or if the padding is 0, the second size of CB does not include the size of the padding, and the second size of CB is the same as the first size of CB.

[0156] Furthermore, based on the above division of CBs, it can be seen that the structure of CBs is not related to that of MAC PDUs. The boundary (or start bit or end bit) of each CB is not necessarily the boundary (or start bit or end bit) of a MAC subPDU, or the boundary (or start bit or end bit) of the data portion of each CB is not necessarily the boundary (or start bit or end bit) of a MAC subPDU, or the boundary (or start bit) of each CB is not necessarily the boundary (or start bit) of a MAC subheader, or the boundary (or start bit) of the data portion of each CB is not necessarily the boundary (or start bit) of a MAC subheader. For example, for a TB, the first size and / or the second size of each CB are the same, but the sizes of different MAC subPDUs are not necessarily the same. Therefore, the boundary (or start bit or end bit) of each CB is not necessarily the boundary (or start bit or end bit) of a MAC subPDU, or the boundary (or start bit or end bit) of the data portion of each CB is not necessarily the boundary (or start bit or end bit) of a MAC subPDU, or the boundary (or start bit) of each CB is not necessarily the boundary (or start bit) of a MAC subheader, or the boundary (or start bit) of the data portion of each CB is not necessarily the boundary (or start bit) of a MAC subheader. For example, as shown in Figure 10(b), the start boundary of CB0 is the start bit of MAC subPDU1, and the start boundaries of CB1 and CB2 are not the start bits of any MAC subPDU.

[0157] It should be noted that Figure 10(b) only shows the data portion of the CB as an example for illustration. The CB may also contain CB CRC, and further padding (e.g., NULL) may be present in the CB, which is not shown in Figure 10(b).

[0158] For the receiving end, after the physical layer receives the CB or TB, it verifies the CB CRC and TB CRC. If all CB CRC checks are successful and the TB CRC check is passed, the physical layer submits the TB to the MAC layer. For example, for the receiving end, after the physical layer receives the CB or TB, it first verifies the CB CRC. If all CB CRC checks are successful, it then verifies the TB CRC. If the TB CRC check is successful, the physical layer submits the TB to the MAC layer.

[0159] 6. Handling of unknown, unforeseen, and erroneous protocol data

[0160] For example, if the receiving end receives a MAC PDU, which includes a MAC subPDU containing a reserved LCID (or eLCID) value or an unsupported LCID (or eLCID) value, the receiving end should discard at least the MAC subPDU and all remaining MAC subPDUs in the MAC PDU.

[0161] For example, when a MAC entity receives a cell-radio network temporary identity (C-RNTI), configured scheduling-radio network temporary identity (CS-RNTI), group-radio network temporary identity (G-RNTI), or group-configured scheduling-radio network temporary identity (G-CS-RNTI) for the MAC entity, or a MAC PDU assigned via configuration downlink, and the MAC PDU includes a MAC subPDU containing a reserved LCID or eLCID value, or an LCID or eLCID value not supported by the MAC entity, the MAC entity should at least: discard the received MAC subPDU and all remaining MAC subPDUs in the MAC PDU.

[0162] For the above processing, at least one of the following factors was considered:

[0163] 1. If a MAC subPDU contains a reserved LCID (or eLCID) value or an unsupported LCID (or eLCID) value, it may be due to a missed CRC (e.g., TB CRC) check or a lack of alignment between the sender and receiver, making the TB or MAC PDU untrustworthy (or unreliable).

[0164] 2. If a MAC subPDU contains a reserved LCID (or eLCID) value or an unsupported LCID (or eLCID) value, the receiver cannot determine the boundaries of subsequent MAC subPDUs and cannot continue parsing the remaining parts of subsequent MAC subPDUs or MAC PDUs. For example, if a MAC subPDU contains a reserved LCID (or eLCID) value or an unsupported LCID (or eLCID) value, the receiver cannot determine the logical channel or MAC CE type corresponding to the MAC subheader based on the LCID field (or determine part or all of the MAC subheader format). The receiver cannot determine the MAC subheader format, or it cannot determine whether the MAC subheader contains the F field and / or L field based on the LCID field. Therefore, it cannot parse the subPDU, nor can it determine the length of the MAC subPDU, and thus cannot determine the boundaries of subsequent MAC subPDUs, and cannot continue parsing the remaining parts of subsequent MAC subPDUs or MAC PDUs.

[0165] 3. The MAC PDU adopts an interleaved structure (i.e., the MAC subheader of each MAC subPDU is before the MAC subPDU). When the receiver parses the MAC PDU, it parses each MAC subPDU in sequence. For the preceding MAC subPDU, if there are no errors, the receiver's MAC layer parses the MAC subPDU and then delivers the corresponding MAC SDU to the upper layer (e.g., the RLC layer), which cannot be withdrawn.

[0166] For example, considering the factors above, if a MAC subPDU contains a reserved LCID (or eLCID) value or an unsupported LCID (or eLCID) value, it means that the entire TB or MAC PDU may be untrusted (or unreliable), and the receiver cannot determine the boundary of subsequent MAC subPDUs, and cannot continue to parse the remaining parts of subsequent MAC subPDUs or MAC PDUs; in addition, the MAC subPDUs preceding the MAC subPDU containing the reserved LCID (or eLCID) value or an unsupported LCID (or eLCID) value (or the MAC SDU corresponding to the MAC subPDU) have already been submitted to the upper layer and cannot be withdrawn, so the receiver's processing is to discard the MAC subPDU and all remaining MAC subPDUs in the MAC PDU.

[0167] For example, if the receiver receives a MAC PDU, which includes a MAC subPDU containing an unconfigured LCID (or eLCID) value or an LCID (or eLCID) value associated with a suspended radio bearer (RB), the receiver should at least discard that MAC subPDU.

[0168] For example, when a MAC entity receives a MAC PDU for the MAC entity via a C-RNTI, CS-RNTI, G-RNTI, or a configured downlink assignment, and the MAC PDU includes a MAC subPDU containing an unconfigured LCID or eLCID value, or an LCID or eLCID value associated with a suspended radio bearer (RB), the MAC entity should at least: discard the received MAC subPDU.

[0169] For example, a MAC entity can include / be replaced with: terminal, or, the MAC entity of the terminal, or, the receiver, or, the MAC entity of the receiver.

[0170] Based on the above physical layer data processing, it is known that for the receiving end, after receiving a CB or TB, the physical layer verifies both the CB CRC and TB CRC. If all CB CRC checks are successful and the TB CRC check passes, the physical layer submits the TB to the MAC layer. For example, for the receiving end, the physical layer first verifies the CB CRC. If all CB CRC checks are successful, it then verifies the TB CRC. If the TB CRC check passes, the physical layer then submits the TB to the MAC layer.

[0171] However, the above technology has the following problems: if any CB CRC fails to pass the check, the entire TB cannot be submitted to the MAC layer for processing and needs to wait for the hybrid automatic repeat request (HARQ) retransmission (e.g., TB or code block group (CBG) retransmission), which leads to increased service latency and affects communication quality. For example, it may cause data to fail to arrive within the service latency requirements, thereby affecting the service communication quality or system capacity.

[0172] To address this issue, one solution is as follows: After receiving the CB (or TB), the PHY layer at the receiving end performs a CB CRC check. If the CB CRC check passes, the CB (or the data portion of the CB) is submitted to the MAC layer for processing (or the CB (or the data portion of the CB) is processed subsequently) without waiting for (or considering) the TB CRC check result.

[0173] [Detailed Rule 91, 09.05.2026] However, in this solution, since the division of CBs is independent of the structure of MAC PDUs, if the CRC check of a certain CB fails, the receiving end cannot know the format of the MAC PDU corresponding to the subsequent CB (or, cannot know the position of the start part of the subsequent MAC subPDU in the CB, or, cannot find the boundary of the next or subsequent MAC subPDU), thus it cannot decode the subsequent CBs (or, the data part of the CB), causing all subsequent CBs (or, the data part of the CB) to be unable to be submitted to the MAC layer for processing (or, causing all subsequent CBs (or, the data part of the CB) to be unable to undergo subsequent data processing), and it needs to wait for HARQ retransmission (e.g., TB or CBG retransmission), which leads to increased service latency and affects communication quality. For example, it may cause data to not arrive within the service latency requirements, thus affecting the service communication quality. Therefore, currently, this solution can only deliver CBs (or, the data part of the CB) to the MAC layer for processing in sequence (or, perform subsequent data processing on CBs (or, the data part of the CB) in sequence). For example, as shown in Figure 11, since the CRC check of CB2 failed and CB2 was not successfully received, all subsequent CBs (or the data portions of CBs), i.e., CB3, ..., CB2, will not be received. C-2 CB C-1 (or, CB3, ..., CB) C-2 CB C-1 The data portion cannot be submitted to the MAC layer for processing (or cannot be processed further).

[0174] Furthermore, since data processing (e.g., at least one of PHY layer processing, MAC layer processing, RLC layer processing, and PDCP layer processing) is currently performed on on-chip memory, but on-chip memory is very small, even unable to hold a large TB, after the terminal performs one data processing step (e.g., PHY layer processing, or PHY layer CB CRC checksum processing), if it cannot continue to perform the next processing step (e.g., MAC layer processing), the data needs to be stored in double data rate (DDR). When the next processing step can be performed, the data is read from DDR into on-chip memory, and then subsequent data processing is performed on the on-chip memory. For example, DDR can be called: DDR synchronous dynamic random access memory (SDRAM).

[0175] For CBs (or the data portion of CBs) that cannot be submitted to the MAC layer for processing (or cannot undergo subsequent data processing), if they are all cached in on-chip memory, more on-chip memory is needed, resulting in increased on-chip memory overhead and chip cost. If they are cached in DDR, more DDR write / read operations are needed (e.g., writing data / from on-chip memory to DDR, and then reading data / from DDR to on-chip memory), and more DDR bandwidth is needed (e.g., DDR bandwidth needs to be reserved according to the air interface), resulting in increased cost. In addition, the erasing and writing of DDR will also increase the power consumption of the device.

[0176] In other words, even without waiting for (or considering) the TB CRC check result, and submitting the CB (or the data portion of the CB) sequentially if the CB CRC check passes, will still increase service latency if any CB CRC check fails. This is especially challenging for services requiring lower latency in the future. Furthermore, it will increase equipment costs, particularly for future higher-speed services, creating greater cost pressure. If DDR storage cannot deliver the CB (or the data portion of the CB) to the MAC layer for processing, it will also increase equipment power consumption.

[0177] To this end, the following three implementation schemes are proposed.

[0178] Implementation Scheme 1: The sending end indicates information about the MAC subPDUs in the CB or CB group to the receiving end. For example, the MAC subPDU may include / be replaced by: MAC subheader, or, the boundary of the MAC subPDU, or, the boundary of the MAC subheader. For example, the information about the MAC subPDUs in the CB or CB group may include / be replaced by: information about the MAC subPDUs carried in the CB or CB group. For example, the information about the MAC subPDUs in the CB or CB group may include / be replaced by: information about the position of the "start portion of the MAC subPDU" in the CB or CB group, or, information about the position of the first "start portion of the MAC subPDU" in the CB or CB group.

[0179] For example, the location can include / replace with: the location in CB or CB group.

[0180] For example, the transmitter can carry information in the CB or CB group (e.g., the CB or CB group header) to indicate the information of the MAC subPDU in the CB or CB group. Alternatively, the transmitter can indicate the information of the MAC subPDU in the CB or CB group through downlink control information (DCI). For example, as shown in Figure 12(a), some or all CBs can correspond to CB headers, and the transmitter can carry information in the CB header corresponding to the CB to indicate the information of the MAC subPDU in the CB.

[0181] For example, as shown in Figure 12(b), CB0 includes complete MAC subPDU1 to MAC subPDU. I-2 and MAC subPDU I-1 The first part, CB1, includes the MAC subPDU. I-1 The remainder, and the complete MAC subPDU I To MAC subPDU Y In CB0, the first "start of MAC subPDU" is marked with position a; in CB1, the first "start of MAC subPDU" is marked with position b. Therefore, the header corresponding to CB0 can carry information indicating the position of position a, and the header corresponding to CB1 can carry information indicating the position of position b.

[0182] This implementation scheme enables the receiving end to determine the structure of the MAC subPDU corresponding to the CB or CB group based on the header indication or the information of the MAC subPDU in the CB or CB group. Therefore, it can decode the CB or CB group without relying on the successful reception of previous CBs or CB groups. For example, it can start decoding the CB (or the data portion of the CB) or CB group (or the data portion of the CB group) from the position of the first "start part of MAC subPDU" in the CB or CB group. This allows the receiving end to process successfully received CBs (or the data portions of the CB) or CB groups (or the data portions of the CB group) in a timely manner, avoiding the problem that a single CB or CB group error would prevent subsequent processing of the entire TB or all subsequent CBs (or the data portions of the CB) or CB groups (or the data portions of the CB group) (or all of them would be stuck). This reduces service latency, allowing data to arrive within the service latency requirements as much as possible, thereby improving service communication quality or increasing system capacity. Promptly delivering successfully received CBs (or the data portion of a CB) or CB groups (or the data portion of a CB group) to the MAC layer for processing reduces the number of CBs (or the data portion of a CB) or CB groups (or the data portion of a CB group) that cannot be delivered to the MAC layer. This reduces storage requirements, i.e., reduces the need for additional memory (e.g., less on-chip memory is required), saving costs. Alternatively, it reduces DDR bandwidth requirements (e.g., less DDR bandwidth is required), and also reduces device power consumption caused by DDR erasure and writing. It also helps address the challenges of future services requiring lower latency and / or higher data rates.

[0183] For example, in the embodiments of this application, CB may include / be replaced by a group of CBs. This application does not impose any restrictions on this, and it is uniformly stated here; subsequent embodiments will not repeat this detail. For example, in the embodiments of this application, a group of CBs may include / be replaced by a set of CBs, or other names. This application does not impose any restrictions on this, and it is uniformly stated here; subsequent embodiments will not repeat this detail.

[0184] Implementation Scheme 2: The boundaries (or start bits or end bits) of the data portion of one / each CB or CB group are aligned with the boundaries (or start bits or end bits) of the MAC subPDU (or MAC subheader), or the boundaries (or start bits) of one / each CB or CB group are aligned with the boundaries (or start bits) of the MAC subPDU (or MAC subheader). Alternatively, each CB or CB group can contain a positive integer number of complete MAC subPDUs. For example, LCP / packetization is performed at the sending end at the granularity of CB or CB groups, such that the boundaries (or start bits or end bits) of the data portion of one / each CB or CB group are aligned with the boundaries (or start bits or end bits) of the MAC subPDU (or MAC subheader), or the boundaries (or start bits) of one / each CB or CB group are aligned with the boundaries (or start bits) of the MAC subPDU (or MAC subheader), such that each CB or CB group can contain a positive integer number of complete MAC subPDUs.

[0185] For example, as shown in Figure 13, CB0 includes complete MAC subPDU1 and MAC subPDU2, CB1 includes complete MAC subPDU3 and MAC subPDU4, and CB2 includes complete MAC subPDU5. It should be noted that Figure 13 only shows the data portion of CB as an example; CB may also contain CB CRC and / or padding (e.g., NULL), which are not shown in Figure 13.

[0186] This second implementation scheme allows the receiver to decode at the granularity of CBs or CB groups. It avoids the problem that a single CB error can prevent further processing (or cause all subsequent CBs, or the data portions of CBs, from being processed due to the entire TB or the erroneous CB). Since each CB or CB group can contain a positive integer number of complete MAC subPDUs, the boundary of a CB or CB group (or the data portion of a CB or CB group) is the starting bit of the MAC subPDU. The MAC header and MAC SDU (or MAC CE or padding) of a MAC subPDU are both located within a CB or CB group. Decoding a CB or CB group does not depend on the successful reception of previous CB groups / CBs. This means that even if the CRC check of a previous CB or CB group fails, the CB or CB group (or the data portion of the CB or CB group) with a successful CRC check can still be submitted to the MAC layer for parsing, thereby reducing service latency and ensuring that data arrives within the service's latency requirements, thus improving communication quality or system capacity. Promptly delivering successfully received CBs (or the data portion of a CB) or CB groups (or the data portion of a CB group) to the MAC layer for processing reduces the number of CBs (or the data portion of a CB) or CB groups (or the data portion of a CB group) that cannot be delivered to the MAC layer. This reduces storage requirements, i.e., reduces the need for additional memory (e.g., less on-chip memory is required), saving costs. Alternatively, it reduces DDR bandwidth requirements (e.g., less DDR bandwidth is required), and also reduces device power consumption caused by DDR erasure and writing. It also helps address the challenges of future services requiring lower latency and / or higher data rates.

[0187] Implementation Plan 3: Add boundary identification information to the MAC PDU.

[0188] For example, as shown in Figure 14, the MAC PDU includes MAC subPDU1 to MAC subPDU6, and MAC subPDU1, MAC subPDU3 and MAC subPDU6 include boundary identification information.

[0189] Through this implementation scheme 3, if a CB or CB group fails to receive data, the boundary of the MAC subPDU can be determined by retrieving the boundary identification information in subsequent CBs or CB groups. This allows the CB or CB group with a successful CRC check (or the data portion of the CB or CB group) to be submitted to the MAC layer for further parsing of the MAC subPDU in subsequent CBs or CB groups, thereby reducing service latency and ensuring that data arrives within the service latency requirements, thus improving the communication quality of the service.

[0190] In the above implementation schemes one through three, even if the receiver encounters a CRC check error for a certain CB or CB group, it can still submit subsequent CBs or CB groups with successful CRC checks to the MAC layer for decoding. This reduces service latency and ensures data arrives within the required latency range, thereby improving communication quality or system capacity. Promptly submitting subsequently received CBs (or the data portion of a CB) or CB groups (or the data portion of a CB group) to the MAC layer reduces the number of CBs (or the data portion of a CB) or CB groups (or the data portion of a CB group) that cannot be submitted to the MAC layer, thus reducing storage requirements (i.e., reducing memory increases, e.g., less on-chip memory is needed), saving costs, or reducing DDR bandwidth requirements (e.g., less DDR bandwidth is needed), and reducing power consumption from DDR erasure and rewriting. It also helps address the challenges of future services requiring lower latency and / or higher speeds.

[0191] However, at least one of the above three implementation schemes may still have the following two problems:

[0192] Question 1: As described above regarding the receiver's handling of unknown, unpredictable, and erroneous protocol data, if the received MAC subPDU contains reserved or unsupported LCID or eLCID values, the receiver will discard the received MAC subPDU and all remaining MAC subPDUs in the MAC PDU. However, for at least one of the above three implementation schemes, it is required to ignore / delete TB CRC. Ignoring TB CRC can be understood as: not performing TB CRC verification, or not considering the TB CRC verification result, or performing TB CRC verification but not considering the TB CRC verification result. This makes the trustworthiness of different CBs or CB groups (e.g., CRC miss detections of different CBs or CB groups) unrelated, or in other words, if a CB or CB group has a CRC miss detection, making that CB or CB group untrustworthy, it does not mean that another CB or CB group also has a CRC miss detection. Through at least one of the above three implementation schemes, if a MAC subPDU contains reserved or unsupported LCID or eLCID values, the receiver can determine the boundary of subsequent MAC subPDUs and can continue to parse the remaining parts of subsequent MAC subPDUs or MAC PDUs. In this scenario, if a MAC subPDU contains a reserved or unsupported LCID or eLCID value, discarding that received MAC subPDU and all subsequent MAC subPDUs would be unreasonable (e.g., for some MAC subPDUs, discarding is unnecessary). This could reduce the reliability of data transmission or increase service latency (e.g., discarded data needs to be retransmitted to be received again), affecting communication quality. For example, it might cause data to fail to arrive within the service's latency requirements, thus impacting service communication quality or system capacity.

[0193] Question 2: For at least one of the above three implementation schemes, if the CRC check of a certain CB or CB group fails at the receiving end, then the CB or CB group will be retransmitted via a hybrid automatic repeat request (HARQ). However, there may be CBs or CB groups that have passed the CRC check before the CB or CB group, and the MAC subPDUs included in them may contain reserved LCIDs or unsupported LCIDs. In this case, it is meaningless to continue retransmitting the CB or CB group that has failed the CRC check, because even if the CRC check of the retransmitted CB or CB group passes, it will still be discarded at the MAC layer, resulting in high power consumption of the terminal and wasting air interface resources.

[0194] In view of this, this application provides a technical solution for solving at least one of the problems 1 and 2 in the above three implementation schemes.

[0195] The technical solution provided in this application will now be described in detail with reference to the accompanying drawings.

[0196] First, the communication systems to which this application can be applied will be introduced.

[0197] The technical solutions of this application embodiment can be used in various communication systems, including third-generation partnership project (3GPP) communication systems, such as fourth-generation (4G) systems like Long Term Evolution (LTE), fifth-generation (5G) systems like New Radio (NR), LTE and 5G hybrid networking systems, non-terrestrial networks (NTN), device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, machine-type communication (MTC) systems, Internet of Things (IoT) systems such as wireless local area networks (WLANs), universal mobile communication systems (GMSMs), or other future communication systems. The communication system can also be a non-3GPP communication system; there is no limitation on this.

[0198] [Detailed Rules 91, 09.05.2026] This communication system can also be applied to next-generation systems (e.g., possible sixth-generation (6G) communication systems), and the technical solutions provided in the embodiments of this application are applicable to all of them. The system architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0199] The technical solutions of this application embodiment can also be applied to various communication systems, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems.

[0200] The term "system" can be used interchangeably with "network".

[0201] The communication systems described above are merely illustrative examples, and are not limited to those described herein. The communication systems provided in this application do not impose any limitations on the solutions described herein. This will be explained uniformly here and will not be repeated below.

[0202] Figure 15 illustrates a possible, non-limiting system diagram. As shown in Figure 15, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one access network device (110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal (120a-120j in Figure 1, collectively referred to as 120). RAN 100 may also include other access network devices, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). Terminal 120 is wirelessly connected to access network device 110. Access network device 110 is wirelessly or wired connected to core network 200. The core network device in core network 200 and access network device 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

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

[0204] A terminal can also be called a terminal device, UE, mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as D2D, V2X communication, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, smart homes, transportation safety, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the device form of the terminal.

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

[0206] In one possible scenario, the access network device can be a base station, an evolved NodeB (eNodeB), an access point (AP), a TRP, a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. The access network device can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the access network device can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network device in V2X technology can be a roadside unit (RSU). All or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the access network device functions.

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

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

[0209] As one possible implementation, the CU and DU each implement some protocol layer functions of the access network device. For example, some protocol layer functions are implemented in the CU, while the remaining or all protocol layer functions are implemented in the DU. The CU can control one or more DUs. For instance, the CU can deploy the RRC layer, SDAP layer, and PDCP layer; or, the CU can be understood as a logical node carrying the RRC, SDAP, and PDCP layers of the access network device. Thus, the CU has the processing capabilities of the RRC, PDCP, and SDAP layers. Of course, the CU can also implement or carry other control functions. Similarly, the DU can deploy the RLC layer, MAC layer, and PHY layer; or, the DU can be understood as a logical node carrying the RLC, MAC, and PHY layers. Thus, the DU has the processing capabilities of the RLC, MAC, and PHY layers; of course, the DU can also implement or carry other functions.

[0210] The functional division of CU and DU described above is merely an example and does not constitute a limitation on CU and DU. Furthermore, the functions of CU and DU can be configured as needed. For example, CU or DU can be configured as a node with more protocol layer functions, or as a node with partial protocol layer processing functions.

[0211] In another possible scenario, the access network equipment may include a non-real time RAN intelligent controller (Non-RT RIC or NRT RIC) and / or a near-real time RAN intelligent controller (Near-RT RIC or nRT RIC).

[0212] Non-RT RIC is used to implement non-real-time intelligent management of the RAN, enabling artificial intelligence (AI) / machine learning (ML) for model training and updates, and guiding applications / functions within the Near-RT RIC based on policies. Near-RT RIC is used to implement near real-time intelligent management of the RAN, achieving near real-time control and optimization of O-RAN modules and resources through data collection and related operations on the E2 interface. The E2 interface can be understood as an open interface between two nodes (or endpoints).

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

[0214] The communication method and communication device will be further described below with reference to the accompanying drawings.

[0215] It is understood that this application uses the first communication device as an example for illustration, but this application does not limit the execution subject illustrated in the interaction. For example, the method executed by the first communication device in this application can also be executed by a module (e.g., a chip, chip system, or processor) applied to the first communication device, or it can be implemented by a logic node, logic module, or software that can implement all or part of the functions of the first communication device, without limitation.

[0216] Figure 16 is a schematic flowchart of the communication method 1600 provided in this application. As shown in Figure 16, method 1600 includes:

[0217] S1601, the first communication device acquires the first MAC subPDU.

[0218] For example, a first communication device may include / be replaced by: a MAC entity of the first communication device, or a MAC layer of the first communication device, or a first MAC entity, or a first MAC layer.

[0219] For example, "acquisition" can include / be replaced by: receiving, or receiving what is sent by the second communication device, or acquiring from the PHY layer of the lower layer or the first communication device.

[0220] For example, the lower layer may include: the lower layer of the MAC layer of the first communication device, or the lower layer of the first MAC entity, or the lower layer of the first MAC layer.

[0221] For example, the second communication device is a transmitter (e.g., the transmitter of the first MAC subPDU or the first MAC PDU), and the first communication device is a receiver (e.g., the receiver of the first MAC subPDU or the first MAC PDU). Exemplarily, the second communication device can be a terminal, and correspondingly, the first communication device can be a network device; or, the second communication device can be a network device, and correspondingly, the first communication device can be a terminal; or, the second communication device and the first communication device can be different terminals; or, the first communication device and the second communication device can be two different other devices. This application does not specifically limit the product form of the first communication device and the second communication device.

[0222] For example, network devices may include / be replaced by: access network devices.

[0223] For example, the first MAC subPDU may include / be replaced by at least one of the following: the first MAC PDU, a portion of the first MAC PDU, the first CB or the first CB group, the data portion of the first CB or the data portion of the first CB group, or the fourth bit set.

[0224] For example, the data portion of the first CB group may include the data portions of all CBs corresponding to the first CB group.

[0225] For example, the first communication device acquiring the first MAC subPDU may include / be replaced by at least one of the following: the first communication device acquiring the first MAC PDU; the first communication device acquiring a portion of the first MAC PDU; the first communication device acquiring the first CB or the first CB group; the first communication device acquiring the data portion of the first CB or the data portion of the first CB group; or, the first communication device acquiring the fourth bit set.

[0226] For example, the first MAC PDU includes the first MAC subPDU.

[0227] For example, a first MAC subPDU is included in a portion of the first MAC PDU.

[0228] For example, the first CB or the first CB group includes the first MAC subPDU.

[0229] For example, the data portion of the first CB or the data portion of the first CB group includes the first MAC subPDU.

[0230] For example, the fourth bit set includes the first MAC subPDU.

[0231] For example, the MAC PDU to which the first MAC subPDU belongs is the first MAC PDU. For example, the first MAC subPDU is contained in the first MAC PDU, or the first MAC subPDU is associated with the first MAC PDU. For example, association can include / replace with: correspondence.

[0232] For example, the first MAC subPDU belongs to a CB or CB group that is the first CB or the first CB group. For example, the first MAC subPDU is contained in the first CB or the first CB group, or the first MAC subPDU is associated with the first CB or the first CB group. For example, the first MAC subPDU is contained in the data portion of the first CB or the data portion of the first CB group, or the first MAC subPDU is associated with the data portion of the first CB or the data portion of the first CB group.

[0233] For example, the first MAC PDU may include / be replaced with: first data, or, first TB, or, first code word (CW), or, other names, without restriction. This will be explained uniformly here and will not be repeated later.

[0234] For example, in the embodiments of this application, the MAC subPDU may include / be replaced by: MAC SDU, or MAC CE, or padding, or data unit 1, or other names, without limitation, and will not be repeated hereafter. For example, the first MAC subPDU may include / be replaced by: first MAC SDU, or first MAC CE, or first padding, or first data unit 1, or other names, without limitation, and will not be repeated hereafter.

[0235] For example, in the embodiments of this application, CB or CB group may include / be replaced by: data unit, or data unit 2, or other names. This application does not impose any restrictions on this, and it is uniformly stated here; subsequent embodiments will not repeat this. For example, in the embodiments of this application, the first CB or first CB group may include / be replaced by: first data unit, or first data unit 2, or other names. This application does not impose any restrictions on this, and it is uniformly stated here; subsequent embodiments will not repeat this.

[0236] For example, a CB group may include / be replaced by a CB set, or other names, without limitation. Optionally, the CB group in this application may be the same as or different from a CBG. For example, a CBG may be associated with HARQ feedback and / or HARQ retransmission. For example, a CBG may be the granularity of HARQ feedback and / or HARQ retransmission.

[0237] For example, a bit set can include / be replaced with: a byte set, or a bit set, or a byte set.

[0238] Optionally, the first MAC subPDU (or the first MAC PDU or a portion of the first MAC PDU or the first CB or the first CB group or the data portion of the first CB or the data portion of the first CB group or the fourth bit set) is associated with at least one of C-RNTI or configured scheduling-radio network temporary identifier (CS-RNTI) or group-RNTI (G-RNTI) or group-configured scheduling-RNTI (G-CS-RNTI) or configured downlink assignment.

[0239] For example, the first MAC subPDU (or the first MAC PDU or a portion of the first MAC PDU or the first CB or the first CB group or the data portion of the first CB or the data portion of the first CB group or the fourth bit set) is scheduled by control information (e.g., DCI) scrambled by C-RNTI or CS-RNTI or G-RNTI or G-CS-RNTI.

[0240] For example, at least one of C-RNTI, CS-RNTI, G-RNTI, G-CS-RNTI, or a configured downlink allocation may include / be replaced by: at least one of C-RNTI, CS-RNTI, G-RNTI, G-CS-RNTI, or a configured downlink allocation for the first communication device (or, for the MAC entity of the first communication device).

[0241] For example, the first communication device obtains the C-RNTI or CS-RNTI or G-RNTI or G-CS-RNTI for the first communication device (or, the MAC entity for the first communication device) or the first MAC subPDU (or the first MAC PDU or a portion of the first MAC PDU or the first CB or the first CB group or the data portion of the first CB or the data portion of the first CB group or the fourth bit set) allocated by the configured downlink.

[0242] For example, the configured downlink allocation can include / be replaced by: configured resources, or semi-persistent scheduling (SPS) resources, or conditional grant (CG) resources.

[0243] For example, the downlink allocation configured can include / be replaced with: the transmission configured for downlink allocation.

[0244] S1602, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the first communication device performs any of the following: discards the first MAC subPDU; or, discards the first MAC subPDU and the MAC subPDU located after the first MAC subPDU and associated with the first CB or the first CB group.

[0245] For example, execution can be included or replaced with: at least execution.

[0246] For example, discard can include / be replaced with: at least discard, or, only discard.

[0247] Optionally, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, it may include / replace it with: if the first MAC PDU or a portion of the first MAC PDU or the first CB or the first CB group or the data portion of the first CB or the data portion of the first CB group or the fourth bit set contains a reserved value, an invalid value, or an unsupported value.

[0248] For example, a MAC subPDU may contain reserved, invalid, or unsupported values. A MAC subPDU containing reserved, invalid, or unsupported values ​​is considered an incorrect (or untrustworthy, unreliable, or meaningless) MAC subPDU, and the first communication device cannot decode a MAC subPDU containing reserved, invalid, or unsupported values.

[0249] For example, in this application, decoding may include / be replaced by parsing, or processing.

[0250] For example, reserved or invalid values ​​can include / replace / be called: reserved values.

[0251] For example, "not supported" can be included / replaced with: "not supported by the first communication device".

[0252] For example, the reserved value or invalid value may be negotiated / agreed upon by the first communication device and the second communication device (e.g., the first communication device instructs the second communication device, or the second communication device instructs the first communication device, or the first communication device and the second communication device agree on the specific value of the reserved value or invalid value), or it may be configured by the network device (e.g., the network device is configured for the second communication device, or the network device is configured for the first communication device), or it may be specified by the communication protocol, or it may be predefined, and the application itself does not specify any limitations.

[0253] Optionally, reserved, invalid, or unsupported values ​​may include / become: reserved, invalid, or unsupported logical channel identifier values.

[0254] For example, the logical channel identifier value can include / be replaced with: the value of the logical channel identifier.

[0255] For example, logical channel identifiers may include / are: LCID and / or eLCID.

[0256] For example, LCID or the LCID field or LCID value can be used to indicate the logical channel of the MAC SDU corresponding to the MAC subheader, or to indicate the type of the MAC CE corresponding to the MAC subheader, or to indicate the padding corresponding to the MAC subheader, or to indicate whether the eLCID field exists.

[0257] For example, indicating the presence of an eLCID field can include / be replaced with: indicating the presence of an 8-bit eLCID field, a 16-bit eLCID field, a 1-byte eLCID field, or a 2-byte eLCID field.

[0258] For example, "exists" can be included / replaced with "exists".

[0259] For example, LCID or the LCID field or LCID value can be used to identify the logical channel of the MAC SDU or the type of the MAC CE or padding, or to indicate the presence of the eLCID field.

[0260] For example, the size of the LCID or LCID field can be 6 bits.

[0261] For example, the eLCID or eLCID field or eLCID value can be used to indicate the logical channel of the MAC SDU corresponding to the MAC subheader, or to indicate the type of the MAC CE corresponding to the MAC subheader.

[0262] For example, the eLCID or eLCID field or eLCID value can be used to indicate the logical channel instance of the MAC SDU or the type of the MAC CE.

[0263] For example, the size of the eLCID or eLCID field can be 8 or 16 bits (or 1 or 2 bytes).

[0264] For example, the meanings of LCID and eLCID can be found in the descriptions above or in related technologies, and will not be repeated here.

[0265] For example, the field carrying the logical channel identifier occupies k bits, and k bits can correspond to 2... k There are several values, where k is a positive integer.

[0266] For example, 2 k Some of the values ​​can be defined by the communication protocol as values ​​with specific meanings (or valid values). For example, a valid value can uniquely indicate a logical channel. Another example is that a valid value can uniquely indicate a MAC CE type. Yet another example is that a valid value can indicate padding. And yet another example is that a valid value can identify the existence of the eLCID field. For example, in an embodiment of this application, the first communication device can decode the MAC subPDU corresponding to the valid value.

[0267] For example, 2 k Some of the values ​​can be specified as reserved values ​​by the communication protocol. For example, reserved values ​​may not have any meaning.

[0268] For example, Table 1 provides an example of LCID values ​​for a downlink shared channel (DL-SCH).

[0269] For example, Table 2 provides an example of a 2-byte eLCID value for DL-SCH.

[0270] For example, Table 3 provides an example of a 1-byte eLCID value for DL-SCH.

[0271] For example, in the example of Table 1, a codepoint / index value of 35-46 corresponds to a reserved or invalid logical channel identifier. For example, in the example of Table 3, a codepoint value of 0-215 (or an index value of 64-279) corresponds to a reserved or invalid logical channel identifier.

[0272] For example, reserved can include / replace / be called: reserved.

[0273] In addition, for the first communication device, some logical channel identifiers may not be supported by the first communication device.

[0274] For example, as communication technology develops, communication protocol versions gradually change, and the logical channel identifiers specified in different versions of the communication protocol may change. For instance, a logical channel identifier defined in one communication protocol version (e.g., communication protocol version #1) may include identifier 1, but a logical channel identifier defined in another communication protocol version (e.g., communication protocol version #2) may not define identifier 1. Therefore, if the first communication device supports communication protocol version #2 but not communication protocol version #1, and if the received first MAC subPDU includes identifier 1, it can be assumed that the logical channel identifier included in the received first MAC subPDU is not supported.

[0275] For example, with the development of communication technology, communication protocols may correspond to different research topics, and the logical channel identifiers specified by the communication protocols for different research topics may be different. For instance, the logical channel identifier defined in Research Topic 1 includes identifier 1, but the logical channel identifier defined in Research Topic 2 does not define identifier 1. Therefore, if the first communication device only supports Research Topic 2 and not Research Topic 1, and if the received first MAC subPDU includes identifier 1, it can be considered that the logical channel identifier included in the received first MAC subPDU is not supported.

[0276] Table 1

[0277] Table 2

[0278] Table 3

[0279] Optionally, a reserved, invalid, or unsupported value may be associated with the first MAC subPDU (or the first MAC PDU or a portion of the first MAC PDU or the first CB or the first CB group or the data portion of the first CB or the data portion of the first CB group or the fourth bit set).

[0280] For example, the first MAC subPDU (or the first MAC PDU or a portion of the first MAC PDU or the first CB or the first CB group or the data portion of the first CB or the data portion of the first CB group or the fourth bit set) includes a reserved value or an invalid value or an unsupported value.

[0281] For example, a reserved value, an invalid value, or an unsupported value is located in the first MAC subPDU (or the first MAC PDU or a part of the first MAC PDU or the first CB or the first CB group or the data portion of the first CB or the data portion of the first CB group or the fourth bit set).

[0282] For example, the first CB or the first CB group is a CB or CB group associated with the first MAC subPDU or a reserved value or an invalid value or an unsupported value.

[0283] For example, the first MAC subPDU, or a reserved, invalid, or unsupported value, is associated with the first CB or the first CB group.

[0284] For example, in this application, if the first MAC subPDU or reserved value or invalid value or unsupported value is located in the first CB or the first CB group, then the first MAC subPDU or reserved value or invalid value or unsupported value is associated with the first CB or the first CB group.

[0285] For example, the first MAC subPDU, or a reserved value, invalid value, or unsupported value is located in the first CB or the first CB group.

[0286] For example, the first MAC subPDU or reserved value or invalid value or unsupported value located in the first CB or the first CB group may include / be replaced by: all bits of the first MAC subPDU or reserved value or invalid value or unsupported value located in the first CB or the first CB group, or some bits of the first MAC subPDU or reserved value or invalid value or unsupported value located in the first CB or the first CB group.

[0287] For example, as shown in Figure 17(a) or (b), the first communication device receives CB0 and CB1. CB0 includes a portion of bits from MAC subPDU1 and MAC subPDU2, and CB1 includes another portion of bits from MAC subPDU2, MAC subPDU3, and MAC subPDU4. Then: MAC subPDU1 is associated with CB0, MAC subPDU2 is associated with CB0 and CB1, MAC subPDU3 is associated with CB1, and MAC subPDU4 is associated with CB1. That is, MAC subPDU1 is associated with CB0, MAC subPDU1 is associated with both CB0 and CB1, MAC subPDU3 is associated with CB1, and MAC subPDU4 is associated with CB1.

[0288] Optionally, the CRC check of the first CB or the first CB group passes, or the first CB or the first CB group is a CB or CB group that passes the CRC check.

[0289] For example, CRC check can include / be replaced by at least one of the following: CB CRC check, or CB group CRC check, or all CB CRCs corresponding to the CB group.

[0290] For example, "validation passed" can be replaced with: "validation correct" or "validation successful".

[0291] For example, passing the CRC check of the first CB or the first CB group may include / be replaced by at least one of the following: passing the CRC check associated with the first CB or the first CB group, or successfully receiving the first CB or the first CB group, or passing the CRC check of all CBs corresponding to the first CB group, or submitting the first CB or the first CB group to the upper layer, or submitting the data portion of the first CB or the data portion of the first CB group to the upper layer.

[0292] For example, "submit to" can include / replace with: submit to, or submit to.

[0293] For example, the upper layer may include / be replaced by: the upper layer of the first device, or the upper layer of the PHY layer of the first device, or the MAC layer.

[0294] For example, a CB or CB group that passes CRC check can include / be replaced by at least one of the following: a CB or CB group that passes CRC check associated with the CB or CB group, or a CB or CB group that is successfully received, or a CB group that passes CRC check for all CBs corresponding to the CB group, or a CB or CB group that is submitted to the upper layer, or a CB or CB group whose data portion is submitted to the upper layer.

[0295] Optionally, the first communication device acquires the data portion of the first CB or the data portion of the first CB group, or the first CB or the first CB group is the CB or CB group acquired by the first communication device, or the first CB or the first CB group is the CB or CB group of the data portion of the CB or the data portion of the CB group acquired by the first communication device.

[0296] For example, the first CB or the first CB group is a CB or CB group acquired by the first communication device and associated with the first MAC subPDU or a reserved value or an invalid value or an unsupported value.

[0297] Optionally, the first communication device can only obtain the first MAC subPDU if the CRC check of the first CB or the first CB group associated with the first MAC subPDU passes. For example, if the CRC check of the first CB or the first CB group associated with the first MAC subPDU passes, but the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, then the first CB or the first CB group may have experienced a CRC miss. Therefore, the first CB or the first CB group is considered an incorrect (or untrustworthy, unreliable, or meaningless) CB or CB group.

[0298] For example, referring to Figure 17, as shown in Figure 17(a), the CRC check of CB0 and CB1 passes, and CB0 and CB1 (or, the data portion of CB0 and the data portion of CB1) are submitted to the MAC layer. The first communication device determines that MAC subPDU1 includes a reserved value, an invalid value, or an unsupported value. The first communication device determines that MAC subPDU1 is associated with CB0 (or the reserved value, invalid value, or unsupported value is located in CB0). The first communication device discards MAC subPDU1 and the MAC subPDUs located after MAC subPDU1 and associated with CB0. For example, the MAC subPDUs discarded by the first communication device include MAC subPDU1 and MAC subPDU2.

[0299] For example, referring to Figure 17, as shown in Figure 17(b), the CRC check of CB0 and CB1 passes, and CB0 and CB1 (or, the data portions of CB0 and CB1) are submitted to the MAC layer. The first communication device determines that MAC subPDU2 includes a reserved value, an invalid value, or an unsupported value. The first communication device determines that MAC subPDU2 is associated with CB0 and CB1. If the reserved value, invalid value, or unsupported value is located in CB1, the first communication device discards MAC subPDU2 and the MAC subPDUs located after MAC subPDU2 and associated with CB1. For example, the MAC subPDUs discarded by the first communication device include MAC subPDU2, MAC subPDU3, and MAC subPDU4. If the reserved value, invalid value, or unsupported value is located in CB0, the first communication device discards MAC subPDU2 and the MAC subPDUs located after MAC subPDU2 and associated with CB0. For example, the MAC subPDUs discarded by the first communication device include MAC subPDU2.

[0300] It should be noted that Figure 17 only shows the data portion of CB and CRC as an example for illustration. For example, there may also be padding (e.g., NULL) in CB.

[0301] The following details the implementation of discarding the first MAC subPDU and the MAC subPDU located after the first MAC subPDU and associated with the first CB or the first CB group.

[0302] For example, in a first implementation, discarding the first MAC subPDU and the MAC subPDU that follows the first MAC subPDU and is associated with the first CB or the first CB group may include / be replaced by: discarding the first MAC subPDU and at least one MAC subPDU that follows the first MAC subPDU and is located in the first CB or the first CB group, or discarding the first MAC subPDU and at least one MAC subPDU located in the first CB or the first CB group, or discarding at least one MAC subPDU located in the first CB or the first CB group.

[0303] Optionally, at least one MAC subPDU may include / be replaced with: all MAC subPDUs.

[0304] Optionally, at least one MAC subPDU may include / be replaced by at least one bit. For example, at least one MAC subPDU located in the first CB or the first CB group may include / be replaced by at least one bit located in the first CB or the first CB group.

[0305] Optionally, the first MAC subPDU may include / be replaced with: a reserved value, an invalid value, or an unsupported value. For example, discarding the first MAC subPDU may include / be replaced with: discarding a reserved value, an invalid value, or an unsupported value. For example, the value following the first MAC subPDU may include / be replaced with: the value following a reserved value, an invalid value, or an unsupported value.

[0306] Optionally, at least one bit may include / be replaced with: all bits.

[0307] Optionally, at least one bit may include / be replaced with: at least one bit acquired.

[0308] Optionally, all bits can include / be replaced with: all bits obtained.

[0309] Optionally, the all bit set can include / be replaced with: the all bit set obtained.

[0310] Optionally, at least one MAC subPDU may include / be replaced with: at least one acquired MAC subPDU.

[0311] Optionally, all MAC subPDUs can include / replace with: all MAC subPDUs obtained.

[0312] For example, the acquired information may include / be replaced by: received information, or information acquired from the PHY layer of the lower layer or the first communication device, or information acquired by the first communication device, or information received by the first communication device, or information acquired by the first communication device from the PHY layer of the lower layer or the first communication device.

[0313] For example, "all" can include / be replaced with at least one of the following: any, any, remainder, all remainder, remainder all, any remainder, or, any remainder.

[0314] Optionally, at least one MAC subPDU located after the first MAC subPDU and located in the first CB or the first CB group may include / be replaced by at least one MAC subPDU located in the first CB or the first CB group.

[0315] Optionally, at least one MAC subPDU located after the first MAC subPDU and located in the first CB or the first CB group may include / be replaced by: all MAC subPDUs located after the first MAC subPDU and located in the first CB or the first CB group.

[0316] Optionally, at least one MAC subPDU located in the first CB or the first CB group may include / be replaced by: all MAC subPDUs located in the first CB or the first CB group.

[0317] Optionally, at least one bit located in the first CB or the first CB group may include / be replaced by all bits located in the first CB or the first CB group.

[0318] For example, the part following the first MAC subPDU can include / replace the part following the first MAC subPDU.

[0319] For example, what follows a reserved value, invalid value, or unsupported value can include / replace with: what follows a reserved value, invalid value, or unsupported value.

[0320] For example, that located in the first CB or the first CB group can include / replace with: the first CB or the first CB group.

[0321] For example, a bit can be included or replaced with a byte.

[0322] Optionally, discarding a reserved value, invalid value, or unsupported value can include / replace with: the byte containing the reserved value, invalid value, or unsupported value.

[0323] For example, "where" can be replaced with "belonging to".

[0324] Optionally, the first implementation can be applied to implementation scheme two. For example, all MAC subPDUs associated with the first CB or the first CB group are contained within the first CB or the first CB group. For example, all bits of the MAC subPDU associated with the first CB or the first CB group are located within the first CB or the first CB group.

[0325] Optionally, the first MAC PDU corresponds to N CBs or CB groups, and each CB or CB group is associated with a complete MAC subPDU. For example, the second communication device, through implementation scheme two, ensures that the MAC subPDUs contained in or corresponding to the CBs or CB groups received by the first communication device are all complete MAC subPDUs. In this case, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the first communication device discards the first MAC subPDU, as well as all MAC subPDUs in the first CB or first CB group associated with the first MAC subPDU that are located after the first MAC subPDU. That is, it discards the first MAC subPDU and all MAC subPDUs in the first CB or first CB group that are located after the first MAC subPDU.

[0326] For example, as shown in Figure 18(a), the first communication device receives CB0, CB1, and CB2. The CRC checks of CB0, CB1, and CB2 pass, and CB0, CB1, and CB2 (or, the data portions of CB0, CB1, and CB2) are submitted to the MAC layer. MAC subPDU1 and MAC subPDU2 are associated with CB0, MAC subPDU3 and MAC subPDU4 are associated with CB1, and MAC subPDU5 is associated with CB2. If the first communication device determines that MAC subPDU3 contains a reserved value, an invalid value, or an unsupported value, the first communication device determines that MAC subPDU3 is associated with CB1, and the first communication device discards MAC subPDU3 and any MAC subPDUs in CB1 that follow MAC subPDU3. That is, MAC subPDU3 and MAC subPDU4 are discarded.

[0327] For example, as shown in Figure 18(b), the first communication device receives CB group 1 and CB group 2. CB group 1 includes CB0 and CB1, and CB group 2 includes CB2 and CB3. The CRC check of CB0, CB1, CB2, and CB3 passes. The first communication device submits CB group 1 and CB group 2 (or the data portions of CB group 1 and CB group 2) to the MAC layer. MAC subPDU1, MAC subPDU2, and MAC subPDU3 are associated with CB group 1, and MAC subPDU4, MAC subPDU5, and MAC subPDU6 are associated with CB group 2. If the first communication device determines that MAC subPDU4 contains a reserved value, an invalid value, or an unsupported value, the first communication device determines that MAC subPDU4 is associated with CB group 2, and the first communication device discards MAC subPDU4 and the MAC subPDUs in CB group 2 that are located after MAC subPDU4. That is, the first communication device discards MAC subPDU4, MAC subPDU5, and MAC subPDU6.

[0328] It should be noted that Figure 18 only shows the data portion of CB or CB group as an example for illustration. CB or CB group may also contain at least one of the following: CB CRC, CB group CRC, padding (e.g., NULL), which is not shown in Figure 18.

[0329] Optionally, if the CRC check of CB group 1 and CB group 2 passes, the first communication device submits CB group 1 and CB group 2 (or, the data portion of CB group 1 and the data portion of CB group 2) to the MAC layer.

[0330] For example, if the first MAC subPDU is the last MAC subPDU in the first CB or the first CB group, discarding the first MAC subPDU and the MAC subPDUs that follow the first MAC subPDU and are associated with the first CB or the first CB group can be replaced with / understood as: discarding the first MAC subPDU.

[0331] For example, taking Figure 18(a) as an example, if MAC subPDU2 contains a reserved value, an invalid value, or an unsupported value, the first communication device discards MAC subPDU2. As another example, taking Figure 18(b) as an example, if MAC subPDU3 contains a reserved value, an invalid value, or an unsupported value, the first communication device discards MAC subPDU3.

[0332] Optionally, the application may further include: the first communication device does not discard MAC subPDUs (e.g., at least one or all MAC subPDUs) / bits (e.g., at least one or all bits) after at least one MAC subPDU / at least one bit in the first implementation, or does not discard MAC subPDUs (e.g., at least one or all MAC subPDUs) / bits (e.g., at least one or all bits) located in the fourth CB or the fourth CB group.

[0333] For example, the fourth CB or the fourth CB group is located after the first CB or the first CB group. For example, the fourth CB or the fourth CB group includes CBs or CB groups located after the first CB or the first CB group (e.g., at least one or all CBs or CB groups).

[0334] For example, taking Figure 18(a) as an example, if MAC subPDU2 contains a reserved value, an invalid value, or an unsupported value, the first communication device discards MAC subPDU2, but does not discard MAC subPDU3, MAC subPDU4, and MAC subPDU5 (or, MAC subPDU3, MAC subPDU4, MAC subPDU5, and subsequent MAC subPDUs).

[0335] For example, "not discard" can be replaced with "retain".

[0336] For example, in the second implementation, discarding the first MAC subPDU and the MAC subPDU that follows the first MAC subPDU and is associated with the first CB or the first CB group can include / be replaced by: discarding the first MAC subPDU, the first set of bits in the first CB or the first CB group that follows the first MAC subPDU, and the second set of bits that follows the first set of bits and precedes the first start position.

[0337] Optionally, the first MAC subPDU may include / be replaced with: a reserved value, an invalid value, or an unsupported value. For example, discarding the first MAC subPDU may include / be replaced with: discarding a reserved value, an invalid value, or an unsupported value. For example, the value following the first MAC subPDU may include / be replaced with: the value following a reserved value, an invalid value, or an unsupported value.

[0338] Optionally, the first set of bits may include / be replaced by: at least one bit. Optionally, at least one bit may include / be replaced by: all bits, or, all set of bits. For example, the first set of bits in the first CB or the first CB group following the first MAC subPDU may include / be replaced by: all bits in the first CB or the first CB group following the first MAC subPDU.

[0339] Optionally, the second set of bits may include / be replaced by at least one bit. Optionally, at least one bit may include / be replaced by all bits, or all sets of bits. For example, the second set of bits that follows the first set of bits and precedes the first start position may include / be replaced by all bits that follow the first set of bits and precede the first start position.

[0340] Optionally, the first bit set may include / be replaced with: the first bit set obtained.

[0341] Optionally, the second bit set may include / be replaced with: the acquired second bit set.

[0342] For example, after the first set of bits, it can include / be replaced with: after the first CB or the first CB group.

[0343] For example, after the first set of bits, it can include / replace with: after the first set of bits.

[0344] For example, after the first CB or the first CB group, it can include / replace with: after the first CB or the first CB group.

[0345] For example, "before the first starting position" can include / before the first starting position.

[0346] For example, what is located before the first starting position can include / be replaced with: the MAC subheader or MAC subPDU associated with the first starting position.

[0347] For example, the MAC subheader or MAC subPDU associated with the first starting position may include / be replaced with: the MAC subheader or MAC subPDU following the MAC subPDU associated with the first starting position (or, the first MAC subheader or MAC subPDU thereafter).

[0348] For example, the first starting position is the position of the "starting portion of the MAC subPDU" or the position of the "starting portion of the MAC subPDU" associated with the second CB or the second CB group.

[0349] For example, "start of MAC subPDU" can include / be replaced with: the position of MAC subPDU, or "start of MAC subheader", or the first "start of MAC subPDU", or the first "start of MAC subheader". For example, the position of "start of MAC subPDU" associated with the second CB or the second CB group can include / be replaced with: the position of the first "start of MAC subPDU" associated with the second CB or the second CB group.

[0350] For example, the first starting position is the location of the MAC subPDU or the location of the MAC subPDU associated with the second CB or the second CB group. For example, the MAC subPDU may include / be replaced by: a MAC subheader, or the boundary of the MAC subPDU, or the boundary of the MAC subheader. For example, the location of the MAC subPDU associated with the second CB or the second CB group may include / be replaced by: the location of the "start portion of the MAC subPDU" associated with the second CB or the second CB group.

[0351] For example, the position can include / replace with: the position in CB or CB group, or the position in the second CB or second CB group.

[0352] For example, the position of "start of MAC subPDU" can include / be replaced with: the position of "start of MAC subPDU" in CB or CB group, or the position of "start of MAC subPDU" in second CB or second CB group.

[0353] For example, what is associated with the second CB or the second CB group can include / replace: the second CB or the second CB group.

[0354] For example, the second CB or the second CB group is different from the first CB or the first CB group. For example, the second CB or the second CB group is independent of the first CB or the first CB group.

[0355] For example, the second CB or the second CB group or the first starting position is located after the first CB or the first CB group.

[0356] For example, a boundary may include / be replaced with: at least one of the following: start boundary, end boundary, start bit, end bit, start byte, or end byte. For example, a start boundary may include / be replaced with at least one of the following: start bit, or start byte. For example, an end boundary may include / be replaced with at least one of the following: end bit, or end byte.

[0357] Optionally, the second CB or the second CB group is the first CB or CB group that, after the first CB or the first CB group, contains / indicates the location of the "start portion of the MAC subPDU".

[0358] Optionally, the second CB or second CB group is the CB or CB group whose location of the "start portion of the MAC subPDU" is determined / known by the first communication device after the first CB or first CB group.

[0359] Optionally, the first starting position is the CB or CB group whose position of the "starting portion of the MAC subPDU" is determined / known by the first communication device after the first CB or the first CB group. Optionally, the second CB or the second CB group is the CB or CB group whose position of the "starting portion of the MAC subPDU" is determined / known by the first communication device after the first CB or the first CB group.

[0360] For example, "know" can include / be replaced with: obtain, or, acquire, or, understand. This application does not limit how the first communication device determines / knows the location of the "start portion of the MAC subPDU".

[0361] This application does not limit how the first communication device determines / knows the first starting position.

[0362] Optionally, the first starting position can be a position indicated in the second CB or the second CB group. For example, the first starting position can be a position indicated in the header of the second CB or the second CB group.

[0363] Optionally, the trusted (or, check missed, or, CRC missed) or CRC check associated with the second CB or the second CB group and the trusted or check associated with the first CB or the first CB group are independent of each other.

[0364] For example, as shown in Figure 19(a), CB0 includes the complete MAC subPDU1 to MAC subPDUI-2. ，The first communication device receives CB0 and CB1, and submits CB0 and CB1 (or the data portion of CB0 and CB1) to the MAC layer. CB1 includes the first part of MAC subPDUI-1, the remainder of MAC subPDUI-1, and the complete MAC subPDUI to MAC subPDUY. CB0's header carries information indicating the position 'a' of the "start of MAC subPDU" in CB0, and CB1's header carries information indicating the position 'b' of the "start of MAC subPDU" in CB1. The first communication device receives CB0 and CB1, and submits CB0 and CB1 (or the data portion of CB0 and the data portion of CB1) to the MAC layer. The first communication device determines that MAC subPDU1 contains a reserved value, an invalid value, or an unsupported value. MAC subPDU1 is associated with CB0. CB1 is the first CB after CB0 to contain the "start of MAC subPDU". The first communication device determines that CB0 is the first CB and CB1 is the second CB.

[0365] For example, as shown in Figure 19(b), CB0 includes the complete MAC subPDU1 to MAC subPDUI-2. ， The MAC subPDUI-1 includes the first part of CB1, the middle part of CB1, and the remaining part of CB2, as well as the complete MAC subPDUI to MAC subPDUIY. The header of CB0 carries information indicating the position 'a' of the "start of MAC subPDU" in CB0. The header of CB1 carries information indicating that the "start of MAC subPDU" does not exist in CB1. The header of CB2 carries information indicating the position 'c' of the "start of MAC subPDU" in CB2. The first communication device receives CB0, CB1, and CB2, and submits CB0, CB1, and CB2 (or the data portions of CB0, CB1, and CB2) to the MAC layer. The first communication device determines that MAC subPDU1 contains a reserved value, an invalid value, or an unsupported value. MAC subPDU1 is associated with CB0. CB2 is the first CB after CB0 that contains the "start of MAC subPDU". The first communication device determines that CB0 is the first CB and CB2 is the second CB.

[0366] It should be noted that Figure 19 only shows the data portion of the CB and the CB header as an example for illustration. The CB may also contain CB CRC and / or padding (e.g., NULL), which are not shown in Figure 19.

[0367] Optionally, the second set of bits that follows the first set of bits and precedes the first start position may include / be replaced by: the second set of bits in the second CB or the second CB group that precedes the first start position.

[0368] Optionally, discarding the first MAC subPDU, the first set of bits in the first CB or the first CB group that follows the first MAC subPDU, and the second set of bits that follows the first set of bits and precedes the first start position may include / be replaced by: discarding the first MAC subPDU and at least one bit (or all bits) that follows the first MAC subPDU and precedes the first start position, or discarding the first MAC subPDU and at least one MAC subPDU (or all MAC subPDUs) that follows the first MAC subPDU and precedes the first start position.

[0369] For example, if the first CB or the first CB group includes an incomplete MAC subPDU located after the first MAC subPDU, in this case, the first communication device discards the first MAC subPDU and all MAC subPDUs located after the first MAC subPDU and before the first starting position.

[0370] Alternatively, the second implementation method can be applied to implementation method one.

[0371] For example, in this application, the first communication device can obtain the first starting position in different ways, without limitation.

[0372] For example, the second communication device can instruct the first communication device via DCI; or, the second communication device can include information about the location of the "start portion of the MAC subPDU" in the header of the second CB or the second CB group. For example, the second communication device includes information about the location of the "start portion of the MAC subPDU" in the header of the second CB or the second CB group.

[0373] The following explanation is based on the example in Figure 20. As shown in Figure 20, CB group 1 includes complete MAC subPDU1 to MAC subPDUI-2, and the first part of MAC subPDUI-1. CB group 2 includes the remaining part of MAC subPDUI-1, and complete MAC subPDUI to MAC subPDUY. The position of the first "start of MAC subPDU" in CB group 1 is marked with 'a'. The position of the first "start of MAC subPDU" in CB group 2 is marked with 'b'. The first communication device determines that MAC subPDU1 contains a reserved value, an invalid value, or an unsupported value. The first communication device discards MAC subPDU1 and all bits before position 'b', i.e., discards MAC subPDU1, ..., MAC subPDUI-2 and MAC subPDUI-1.

[0374] It should be noted that Figure 20 only shows the data portion of the CB or CB group and the header of the CB or CB group as an example for illustration. The CB or CB group may also contain CB CRC and / or CB group CRC and / or padding (e.g., NULL), which are not shown in Figure 20.

[0375] The following explanation is based on an example from Figure 21. As shown in Figure 21, CB0 includes the complete MAC subPDU1 and a portion of MAC subPDU2, CB1 includes a portion of MAC subPDU2, and CB2 includes a portion of MAC subPDU2 and MAC subPDU3. MAC subPDU2 is associated with CB0, CB1, and CB2. The position of the first "starting part of the MAC subPDU" in CB2 is marked with b. The first communication device determines that MAC subPDU1 contains a reserved value, an invalid value, or an unsupported value, and discards MAC subPDU1 and all bits before position b, i.e., discards MAC subPDU1 and MAC subPDU2.

[0376] It should be noted that Figure 21 only shows the data portion of the CB and the header of the CB as an example for illustration. The CB may also contain CB CRC and / or padding (e.g., NULL), which are not shown in Figure 21.

[0377] Optionally, this application may further include: the first communication device does not discard the second set of bits or the MAC subPDU (e.g., at least one or all MAC subPDUs) / bits (e.g., at least one or all bits) after the first starting position.

[0378] For example, taking Figure 21 as an example, if MAC subPDU1 contains a reserved value, an invalid value, or an unsupported value, the first communication device discards MAC subPDU1 and MAC subPDU2, but does not discard MAC subPDU3 (or MAC subPDU3 and subsequent MAC subPDUs).

[0379] For example, in the third implementation, discarding the first MAC subPDU and the MAC subPDU that follows the first MAC subPDU and is associated with the first CB or the first CB group can include / be replaced by: discarding the first MAC subPDU, the first set of bits in the first CB or the first CB group that follows the first MAC subPDU, and the third set of bits that follows the first set of bits and precedes the first boundary identification information.

[0380] Optionally, the first MAC subPDU may include / be replaced with: a reserved value, an invalid value, or an unsupported value. For example, discarding the first MAC subPDU may include / be replaced with: discarding a reserved value, an invalid value, or an unsupported value. For example, the value following the first MAC subPDU may include / be replaced with: the value following a reserved value, an invalid value, or an unsupported value.

[0381] Optionally, the third bit set may include / be replaced by: at least one bit. Optionally, at least one bit may include / be replaced by: all bits, or, all bit sets. For example, the third bit set located after the first bit set and before the first boundary identification information may include / be replaced by: all bits located after the first bit set and before the first boundary identification information.

[0382] Optionally, the third bit set may include / be replaced with: the acquired third bit set.

[0383] For example, after the first set of bits, it can include / be replaced with: after the first CB or the first CB group.

[0384] For example, after the first set of bits, it can include / replace with: after the first set of bits.

[0385] For example, after the first CB or the first CB group, it can include / replace with: after the first CB or the first CB group.

[0386] For example, the section before the first boundary identification information can include / be replaced with: before the first boundary identification information.

[0387] For example, the first boundary identification information can be used to indicate / identify / determine the boundary of a MAC subPDU or the boundary of one or more MAC subPDUs associated with it, or, for the first communication device to determine the boundary of a MAC subPDU.

[0388] For example, in the embodiments of this application, the boundary of a MAC subPDU may include / be replaced by: the boundary of a MAC subheader, or the boundary of the MAC subheader of one or more MAC subPDUs (or the first or last MAC subPDU among one or more MAC subPDUs) associated with the first boundary identification information, or the boundary of one or more MAC subPDUs (or the first or last MAC subPDU among one or more MAC subPDUs) associated with the first boundary identification information.

[0389] For example, the first boundary identification information may include / be replaced with: the MAC subheader or MAC subPDU associated with the first boundary identification information.

[0390] For example, what precedes the first boundary identification information can be included / replaced with: what precedes the MAC subheader or MAC subPDU associated with the first boundary identification information.

[0391] For example, the part located before the MAC subheader or MAC subPDU associated with the first boundary identification information can be included / replaced with: the part before the MAC subheader or MAC subPDU associated with the first boundary identification information.

[0392] For example, the MAC subheader or MAC subPDU associated with the first boundary identification information may include / be replaced with: the first MAC subheader or MAC subPDU associated with the first boundary identification information, or the MAC subheader or MAC subPDU following the MAC subheader or MAC subPDU associated with the first boundary identification information (or the first MAC subheader or MAC subPDU thereafter).

[0393] For example, the first boundary identification information can be associated with / replaced with: the location of the first boundary identification information.

[0394] For example, the third bit set located after the first bit set and before the first boundary identification information can be replaced with: the third bit set located after the first bit set and before the MAC subheader or MAC subPDU associated with the first boundary identification information.

[0395] For example, the first boundary identification information can be the boundary identification information following the first MAC subPDU, the first CB, or the first CB group (e.g., the first boundary identification information).

[0396] For example, the first boundary identification information can be the boundary identification information associated with the third CB or the third CB group.

[0397] For example, what is associated with the third CB or the third CB group can include / replace with: the third CB or the third CB group.

[0398] For example, the third CB or the third CB group is different from the first CB or the first CB group. For example, the third CB or the third CB group is independent of the first CB or the first CB group.

[0399] For example, the third CB or the third CB group is located after the first CB or the first CB group.

[0400] Optionally, the third CB or the third CB group is the first CB or CB group that has boundary identification information after the first CB or the first CB group.

[0401] Optionally, the first boundary identification information may include / be replaced with: the bytes containing the first boundary identification information.

[0402] For example, what precedes the first boundary identification information can be included / replaced with: the byte preceding the first boundary identification information.

[0403] For example, the byte preceding the first boundary identification information can be included or replaced with: the byte preceding the first boundary identification information.

[0404] Optionally, the trusted (or, check missed, or, CRC missed) or CRC check associated with the third CB or the third CB group and the trusted or check associated with the first CB or the first CB group are independent of each other.

[0405] For example, as shown in Figure 22(a), the MAC PDU includes MAC subPDU1 to MAC subPDU6, and MAC subPDU1, MAC subPDU3, and MAC subPDU6 include boundary identification information. CB0 includes the complete MAC subPDU1 and a part of MAC subPDU2; CB1 includes another part of MAC subPDU2, the complete MAC subPDU3, the complete MAC subPDU4, and the first part of MAC subPDU5; CB2 includes the second part of MAC subPDU5; and CB3 includes the last part of MAC subPDU5 and the complete MAC subPDU6. The first communication device receives CB0, CB1, CB2, and CB3, and submits CB0, CB1, CB2, and CB3 (or, the data portions of CB0, CB1, CB2, and CB3) to the MAC layer. The first communication device determines that MAC subPDU3 contains a reserved value, an invalid value, or an unsupported value. MAC subPDU3 is associated with CB1. CB3 is the first CB after CB1 that has boundary identification information. The first communication device determines that CB1 is the first CB and CB3 is the third CB.

[0406] For example, as shown in Figure 22(b), the MAC PDU includes MAC subPDU1 to MAC subPDU6. MAC subPDU1, MAC subPDU2, MAC subPDU3, and MAC subPDU5 include boundary identification information. CB0 includes the complete MAC subPDU1 and a portion of MAC subPDU2. CB1 includes another portion of MAC subPDU2, the complete MAC subPDU3, the complete MAC subPDU4, the first portion of MAC subPDU5, CB2 includes the second portion of MAC subPDU5, and CB3 includes the last portion of MAC subPDU5 and the complete MAC subPDU6. The first communication device receives CB0, CB1, CB2, and CB3, and submits CB0, CB1, CB2, and CB3 (or, the data portions of CB0, CB1, CB2, and CB3) to the MAC layer. The first communication device determines that MAC subPDU1 contains a reserved value, an invalid value, or an unsupported value. MAC subPDU1 is associated with CB0. CB1 is the first CB with boundary identification information after CB0. The first communication device determines that CB0 is the first CB and CB1 is the third CB.

[0407] It should be noted that Figure 22 only shows the CB data portion as an example for illustration. CB may also contain CB CRC and / or padding (e.g., NULL), which are not shown in Figure 22.

[0408] Optionally, the third set of bits located after the first set of bits and before the first boundary identification information may include / be replaced by: the third set of bits in the third CB or the third CB group that is before the first boundary identification information.

[0409] Optionally, discarding the first MAC subPDU, the first set of bits in the first CB or the first CB group that follows the first MAC subPDU, and the third set of bits that follows the first set of bits and precedes the first boundary identification information may include / be replaced by: discarding the first MAC subPDU and at least one bit (or all bits) that follows the first MAC subPDU and precedes the first boundary identification information, or discarding the first MAC subPDU and at least one MAC subPDU (or all MAC subPDUs) that follows the first MAC subPDU and precedes the first boundary identification information.

[0410] Alternatively, the second implementation method can be applied to implementation method three.

[0411] For example, boundary identification information can be used to indicate / identify / determine the boundary of a MAC subPDU or the boundary of one or more associated MAC subPDUs, or, for a first communication device to determine the boundary of a MAC subPDU.

[0412] Optionally, the second communication device may mark the boundary of each MAC subPDU corresponding to the MAC PDU.

[0413] For example, the first MAC PDU corresponds to / includes N MAC subPDUs. For example, the first MAC PDU corresponds to / includes L boundary identification information. For example, N is an integer. For example, L is an integer. For example, N is greater than or equal to 1. For example, L is greater than or equal to 1.

[0414] Optionally, L is less than or equal to N. In one possible case 1, L is N or N-1. In one possible case 2, L is any value less than N except N-1.

[0415] Optionally, L boundary identifiers are associated with one or more (or M) MAC subPDUs out of N MAC subPDUs. Optionally, M is less than or equal to N. Optionally, one boundary identifier (or each boundary identifier, or one of the L boundary identifiers, or each of the L boundary identifiers) is associated with one or more (or N1) MAC subPDUs out of N MAC subPDUs. Optionally, N1 is less than or equal to N. For example, the number of MAC subPDUs associated with different boundary identifiers (e.g., N1) can be the same or different, without restriction.

[0416] For example, one (or each) MAC subPDU corresponds to one boundary identifier, or one (or each) boundary identifier is associated with one MAC subPDU, or there is a one-to-one correspondence between MAC subPDUs and boundary identifiers. For instance, in case 1 above when L equals N, one (or each) MAC subPDU corresponds to one boundary identifier, or one (or each) boundary identifier is associated with one MAC subPDU, or there is a one-to-one correspondence between MAC subPDUs and boundary identifiers.

[0417] For example, a MAC subPDU (or, one / each MAC subPDU except the first / last MAC subPDU) corresponds to a boundary identification information, or a boundary identification information is associated with a MAC subPDU. For instance, in case 1 above when L equals N-1, a MAC subPDU (or, one / each MAC subPDU except the first / last MAC subPDU) corresponds to a boundary identification information, or a boundary identification information is associated with a MAC subPDU.

[0418] For example, one or more (or N1) MAC subPDUs correspond to one boundary identification information, or one boundary identification information is associated with one or more (or N1) MAC subPDUs. For instance, in case 2 above, when L is a value less than N other than N-1, one or more (or N1) MAC subPDUs correspond to one boundary identification information, or one boundary identification information is associated with one or more (or N1) MAC subPDUs.

[0419] In one example, the first boundary identification information is the first boundary identification information among one or more boundary identification information associated with the third CB or the third CB group.

[0420] This application does not limit how the first communication device determines / knows the first boundary identification information.

[0421] For example, boundary identification information (or, first boundary identification information) can be implemented in different ways, without restriction.

[0422] For example, boundary identification information (or, first boundary identification information) is included in the MAC PDU (e.g., the first MAC PDU). For example, the boundary identification information (or, first boundary identification information) may be included in the MAC subheader (or MAC subPDU), or it may not be included in the MAC subheader (or MAC subPDU).

[0423] For example, in one implementation, the first boundary identification information may include / be replaced by a first boundary identifier. For example, a first communication device may determine the boundary of a MAC subPDU based on the first boundary identifier. For example, Figure 23 shows a schematic diagram of a MAC subheader containing first boundary identification information. For example, as shown in Figure 23(a), the boundary identification information includes a field for indicating the boundary identifier.

[0424] For example, in another implementation, the first boundary identification information may include / be replaced with first verification information. For example, the first communication device may determine the boundary of the MAC subPDU based on the first verification information. For example, Figure 23 shows a schematic diagram of a MAC subheader containing first boundary identification information. As shown in Figure 23(b), the first boundary identification information includes a field for indicating verification information.

[0425] For example, in another implementation, the first boundary identification information can be replaced by: information of a first boundary identifier and first check information. For example, the first communication device can determine the boundary of the MAC subPDU based on the first boundary identifier and the first check information. For example, Figure 23 shows a schematic diagram of a MAC subheader containing first boundary identification information. As shown in Figure 23(c), the first boundary identification information includes a field for indicating the boundary identifier and a field for indicating the check information.

[0426] It should be noted that this application does not specifically limit the length of the field used to indicate the boundary identifier or the length of the field used to indicate the verification information. For example, in the MAC subheader containing boundary identification information shown in Figure 23(a), the field used to indicate the boundary identifier is 5 bytes long; in the MAC subheader containing boundary identification information shown in Figure 23(b), the field used to indicate the verification information is 3 bytes long; and in the MAC subheader containing boundary identification information shown in Figure 23(c), the field used to indicate the boundary identifier is 4 bytes long and the field used to indicate the verification information is 1 byte long.

[0427] For example, let's illustrate with the example in Figure 14. As shown in Figure 14, the MAC PDU includes MAC subPDU1 to MAC subPDU6. MAC subPDU1, MAC subPDU3, and MAC subPDU6 include boundary identification information. MAC subPDU3 and MAC subPDU4 are associated with CB1, MAC subPDU5 is associated with CB1, CB2, and CB3, and MAC subPDU6 is associated with CB3. In this case, if MAC subPDU3 contains a reserved value, an invalid value, or an unsupported value, the first communication device discards MAC subPDU3, MAC subPDU4, and MAC subPDU5, that is, it discards the bits preceding MAC subPDU3 and MAC subPDU6.

[0428] Optionally, this application may further include: the first communication device does not discard MAC subPDUs (e.g., at least one or all MAC subPDUs) / bits (e.g., at least one or all bits) after the third bit set or the first boundary identification information.

[0429] For example, taking Figure 22(b) as an example, if MAC subPDU1 contains a reserved value, an invalid value, or an unsupported value, the first communication device discards MAC subPDU1 and MAC subPDU2, but does not discard MAC subPDU3, MAC subPDU4, MAC subPDU5, and MAC subPDU6.

[0430] The following details the implementation of discarding the first MAC subPDU.

[0431] For example, in one scenario, the MAC subPDUs contained in the first CB or the first CB group are all complete MAC subPDUs, and the first MAC subPDU is the last MAC subPDU in the first CB or the first CB group. If the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the first communication device may discard only the first MAC subPDU. A detailed description of this part can be found in the first implementation above, and will not be repeated here.

[0432] For example, in another scenario, the first MAC subPDU is associated with multiple CBs or CB groups. The first MAC subPDU includes reserved values, invalid values, or unsupported values. If the reserved values, invalid values, or unsupported values ​​are not located in the last CB or CB group among the multiple CBs or CB groups, the first communication device may simply discard the first MAC subPDU.

[0433] For example, let's refer to Figure 17(b). As shown in Figure 17(b), after the CRC check of CB0 and CB1 is successful and CB0 and CB1 (or the data portions of CB0 and CB1) are submitted to the MAC layer, the first communication device determines that MAC subPDU2 includes a reserved value, an invalid value, or an unsupported value. The first communication device determines that MAC subPDU2 is associated with CB0 and CB1. If the reserved value, invalid value, or unsupported value included in MAC subPDU2 is located in CB0, the first communication device may discard only MAC subPDU2. For example, there are no restrictions on how the location of MAC subPDU3 is obtained. For example, it can be determined by the boundary identification information of MAC subPDU3, or it can be determined by the location of the "start portion of the MAC subPDU" associated with CB1.

[0434] It should be noted that the operations related to discarding (or not discarding) in this application (e.g., operations related to discarding (or not discarding) MAC subPDUs, or operations related to discarding (or not discarding) bits) apply to the data / MAC PDU / MAC subPDU / bit / bit set / CB or CB group / CB data portion or CB group data portion acquired by the first communication device. For example, operations related to discarding (or not discarding) are not involved (or cannot be discussed) for the data / MAC PDU / MAC subPDU / bit / bit set / CB or CB group / CB data portion or CB group data not acquired by the first communication device.

[0435] Optionally, this application may also include / before the first communication device performs step S1602, it must also satisfy the following: the first communication device determines that the first MAC PDU supports CB or CB group self-decoding.

[0436] For example, if the first communication device determines that the first MAC PDU supports CB or CB group self-decoding, it may include / be replaced by: for the first MAC PDU, the first communication device may perform decoding at the granularity of CB or CB group; or, the first MAC PDU may be associated with CB or CB group self-decoding, Embodiment 1, Embodiment 2, Embodiment 3, or at least one of these. It can be seen that, based on the communication method provided above, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the first communication device discards the first MAC subPDU, or discards the first MAC subPDU and MAC subPDUs located after the first MAC subPDU and associated with the first CB or first CB group; or, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the first communication device may not discard some MAC subPDUs contained in other CBs or CB groups that are not associated with the first CB or first CB group. It can avoid unnecessary MAC subPDU dropping, improve data transmission reliability, reduce service latency, and guarantee / improve communication quality. For example, it can ensure that data arrives within the service latency requirements as much as possible, thereby improving service communication quality or increasing system capacity. In addition, it can reduce unnecessary retransmissions and save air interface resources.

[0437] For example, the communication method provided in this application can be applied to at least one of the scenarios described in Embodiments 1 to 3, and can also be applied to other scenarios, which are not limited by this application. For example, this application can also be applied to scenarios where the trusted (or, check miss, or, CRC miss) of different CBs or CB groups are not associated and / or scenarios where the receiver can decode at the granularity of CBs or CB groups. For example, the scenario where the trusted of different CBs or CB groups is not associated can be understood as: the checks (e.g., CRC checks) of different CBs or CB groups are independent, or different CBs or CB groups are not associated with the same check (e.g., CRC check, or, TB CRC check). For example, the scenario where the receiver can decode at the granularity of CBs or CB groups can be understood as: decoding a certain CB or CB group does not depend on the successful reception of previous CB groups / CBs, so that even if the CRC check of the previous CB or CB group fails, the CB or CB group (or the data part of the CB or CB group) with successful CRC check of the later CB or CB group can be submitted to the MAC layer for parsing.

[0438] Regarding problem 2, with reference to Figure 24, we will introduce another communication method provided in this application to solve problem 2.

[0439] The following is a detailed explanation with reference to Figure 24. As shown in Figure 24, this communication method includes:

[0440] S2401, The first communication device acquires the first MAC subPDU.

[0441] For example, the description related to S2401 can be found in S1601 or the relevant content in the embodiment shown in Figure 16, and will not be repeated here.

[0442] S2402. If the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the first communication device sends a first confirmation message.

[0443] For example, the first confirmation message is used to indicate that the first MAC PDU (or, the first CBG) was successfully received or that the first MAC PDU (or, the first CBG) no longer needs to be retransmitted (or, HARQ retransmit).

[0444] For example, the first confirmation information may include / be replaced with: first positive confirmation information, or, first HARQ ACK information, or, first ACK information, or, first HARQ ACK, or, first ACK, or, positive confirmation information, or, HARQ ACK information, or, ACK information, or, HARQ ACK, or, ACK.

[0445] For example, the first CBG is associated with the first MAC subPDU (or, a reserved value, an invalid value, or an unsupported value, or, a portion of the first MAC PDU, or the first CB, or the first CB group, or the data portion of the first CB, or the data portion of the first CB group, or the fourth bit set). For example, the first CBG includes the first MAC subPDU (or, a reserved value, an invalid value, or an unsupported value, or, a portion of the first MAC PDU, or the first CB, or the first CB group, or the data portion of the first CB, or the data portion of the first CB group, or the fourth bit set).

[0446] For a detailed description of the reserved, invalid, or unsupported values, please refer to the description in S1602, which will not be repeated here.

[0447] For example, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the MAC entity of the first communication device will discard the first MAC subPDU and any remaining MAC subPDUs in the first MAC PDU, wherein the remaining MAC subPDUs refer to the MAC subPDUs that are located after the first MAC subPDU.

[0448] Understandably, if the first communication device submits a CB or CB group (or the data portion of the CB or CB group) to the MAC layer as soon as the CRC check of that CB or CB group is successful, and if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, and the first MAC subPDU is located in the first CB or the first CB group, the MAC subPDUs associated with subsequent CBs or CB groups submitted by the PHY layer (e.g., CBs or CB groups after the first CB or CB group) will also be discarded. Therefore, it is meaningless to continue retransmitting those CBs or CB groups that fail the CRC check, because even if the CRC check of the retransmitted CBs or CB groups passes, they will still be discarded at the MAC layer. Therefore, in this embodiment, when the first MAC subPDU submitted by the PHY layer contains a reserved value, an invalid value, or an unsupported value, the first communication device can send a first acknowledgment message (ACK). The ACK is used to indicate that the first MAC PDU (or the first CBG) was successfully received or that the first MAC PDU (or the first CBG) no longer needs to be retransmitted.

[0449] Optionally, this application may also include: the first communication device performing one or more of the following:

[0450] (1) The MAC layer of the first communication device may indicate to the PHY layer that the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value.

[0451] (2) The first communication device (or the PHY layer of the first communication device) stops processing the remaining MAC subPDUs in the first MAC PDU (or, the first CBG) or the remaining CBs associated with the first MAC PDU (or, the first CBG), or the first communication device (or the PHY layer of the first communication device) stops processing the CBs that have not yet been processed among all the CBs corresponding to the first MAC PDU (or, the first CBG).

[0452] (3) The first communication device discards the remaining MAC subPDUs in the first MAC PDU (or, the first CBG) or the remaining CBs associated with the first MAC PDU (or, the first CBG), or the first communication device discards all CBs that have not yet been processed from the first MAC PDU (or, the first CBG).

[0453] It can be seen that this communication method can reduce unnecessary HARQ retransmissions and data processing, which on the one hand helps to reduce communication overhead (e.g., save air interface resources), and on the other hand can reduce the power consumption of the receiver.

[0454] For example, the communication method provided in this application embodiment can be applied to at least one of the scenarios described in embodiment one to embodiment three, and can also be applied to other scenarios. This application embodiment does not impose any restrictions on this.

[0455] It should be noted that the CB or CB group involved in the embodiments of this application may only show one or more of the CB data, the CB data portion, and the CB CRC header, but this does not mean that there are no other items in the CB or CB group.

[0456] In the embodiments of this application, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or devices.

[0457] In this application, "instruction" may include: direct instruction, or indirect instruction, or explicit instruction, or implicit instruction.

[0458] In this application, "including" can include: direct inclusion, indirect inclusion, explicit inclusion, or implicit inclusion.

[0459] It should be understood that existing technologies may change as technical solutions evolve, and the technical solutions provided in this application are not limited to the existing technologies provided.

[0460] It should be noted that different embodiments or some steps (e.g., any one or more steps) in different embodiments of this application can be combined with each other to form new embodiments. It should also be noted that the scope of this application is not limited to including optional steps in a certain embodiment, mandatory steps in a certain embodiment, or both optional and mandatory steps in a certain embodiment.

[0461] It should be noted that, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be referenced in each other.

[0462] It should be noted that the order of the steps in the embodiments of this application is not limited by this application.

[0463] It should be noted that the order in which different conditions are judged in the embodiments of this application is not limited by this application.

[0464] It should be noted that the terms "after" and "time" in this application do not strictly limit the specific point in time.

[0465] It should be noted that the nouns and terms used in this application are merely examples and may be other names, which are not limited in this application.

[0466] In one possible implementation, for the above method embodiments, in a CU-DU architecture or ORAN system, the function of interaction between the access network device and the terminal can be implemented by a DU or an O-DU. The information sent by the access network device to the terminal can be generated by a DU or an O-DU, or it can be generated by a CU or an O-CU and sent to a DU or an O-DU. The processing function of the access network device can be implemented by a CU or an O-CU, or it can be implemented by a DU or an O-DU, or it can be jointly implemented by a CU and a DU (or an O-CU and an O-DU), without limitation.

[0467] [Detailed Rules 91, 09.05.2026] The methods provided by this application have been described above. In addition, this application also provides a communication device for implementing the functions in the above method embodiments.

[0468] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

[0470] Figure 25 shows a schematic diagram of a communication device 2500. The communication device 2500 includes a processing module 2501 and a transceiver module 2502. This communication device 2500 can be used to implement the functions of the first communication device described above.

[0471] In some embodiments, the communication device 2500 may further include a storage module (not shown in FIG25) for storing program instructions and data.

[0472] In some embodiments, the transceiver module 2502, also referred to as a transceiver unit, is used to implement sending and / or receiving functions. The transceiver module 2502 may consist of a transceiver circuit, a transceiver, a transceiver unit, or a communication interface.

[0473] In some embodiments, the transceiver module 2502 may include a receiving module and a sending module, respectively configured to perform the receiving and sending steps performed by the first communication device in the above method embodiments, and / or other processes to support the technology described herein; the processing module 2501 may be configured to perform the processing steps performed by the first communication device in the above method embodiments, and / or other processes to support the technology described herein.

[0474] In one embodiment, when the communication device 2500 is used to implement the functions of the first communication device:

[0475] Processing module 2501 is configured to obtain a first MAC subPDU; processing module 2501 is further configured to, if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, perform any of the following: discard the first MAC subPDU; or, discard the first MAC subPDU and the MAC subPDU located after the first MAC subPDU and associated with the first CB or the first CB group, wherein the first CB or the first CB group is the CB or CB group associated with the first MAC subPDU or the reserved value, the invalid value, or the unsupported value.

[0476] Optionally, reserved, invalid, or unsupported values ​​include: reserved, invalid, or unsupported logical channel identifier values.

[0477] Optionally, the logical channel identifier can be either the logical channel identifier LCID or the extended logical channel identifier eLCID.

[0478] Optionally, the processing module 2501 is specifically used to: discard the first MAC subPDU, and at least one MAC subPDU located after the first MAC subPDU and located in the first CB or the first CB group.

[0479] Optionally, the first MAC subPDU is a MAC subPDU in the first MAC PDU, the first MAC PDU corresponds to N CBs or CB groups, and each CB or CB group in the N CBs or CB groups is associated with a complete MAC subPDU.

[0480] Optionally, the processing module 2501 is specifically used to: discard the first MAC subPDU, the first set of bits in the first CB or the first CB group that is located after the first MAC subPDU, and the second set of bits that is located after the first set of bits and before the first starting position; wherein, the first starting position is the position of the "starting part of the MAC subPDU" associated with the second CB or the second CB group, and the second CB or the second CB group is located after the first CB or the first CB group.

[0481] Optionally, the second CB or the second CB group contains information about the location of the "start portion of the MAC subPDU".

[0482] Optionally, the processing module 2501 is specifically used to: discard the first MAC subPDU, the first set of bits in the first CB or the first CB group that is located after the first MAC subPDU, and the third set of bits that is located after the first set of bits and before the first boundary identification information.

[0483] The first boundary identification information is the first boundary identification information associated with the third CB or the third CB group, and the third CB or the third CB group is located after the first CB or the first CB group.

[0484] Optionally, the first boundary identification information includes a first boundary identifier and / or first verification information.

[0485] Optionally, the first MAC PDU contains first boundary identification information.

[0486] Optionally, the processing module 2501 is further configured to determine that the first MAC PDU supports CB or CB group self-decoding, and the first MAC subPDU is a MAC subPDU in the first MAC PDU.

[0487] In the second embodiment, when the communication device 2500 is used to implement the functions of the first communication device:

[0488] Processing module 2501 is used to receive a first MAC subPDU; processing module 2501 is also used to send a first confirmation message if the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, the first confirmation message being used to indicate that the first MAC PDU was successfully received or that the first MAC PDU no longer needs to be retransmitted, the first MAC PDU being a MAC PDU containing the first MAC subPDU.

[0489] Optionally, reserved, invalid, or unsupported values ​​include: reserved, invalid, or unsupported logical channel identifier values.

[0490] Optionally, the logical channel identifier can be either the logical channel identifier LCID or the extended logical channel identifier eLCID.

[0491] Optionally, the processing module 2501 is further configured to stop processing the remaining MAC subPDUs or the remaining code blocks CB associated with the first MAC PDU; and / or discard the remaining MAC subPDUs or the remaining CB associated with the first MAC PDU.

[0492] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0493] In this application, the communication device 2500 can be presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0494] In some embodiments, when the communication device 2500 in FIG25 is a chip or chip system, the function / implementation process of the transceiver module 2502 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 2501 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0495] Since the communication device 2500 provided in this embodiment can execute the above method, the technical effects it can achieve can be referred to the above method embodiment, and will not be repeated here.

[0496] [Detailed Rules 91, 09.05.2026] As a possible product form, the first communication device of this application embodiment can be implemented using the following: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0497] [Detailed Rules 91, 09.05.2026] As another possible product form, the first communication device in this application embodiment can be implemented by a general bus architecture. For ease of explanation, refer to FIG26, which is a structural schematic diagram of the communication device 2600 provided in this application embodiment. The communication device 2600 includes a processor 2601 and a transceiver 2602. The communication device 2600 can be a first communication device, or a chip, chip system, or module therein. FIG26 only shows the main components of the communication device 2600. In addition to the processor 2601 and the transceiver 2602, the communication device may further include a memory 2603 and an input / output device (not shown in the figure).

[0498] Optionally, the processor 2601 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs, thereby implementing the methods provided in the above-described method embodiments. The memory 2603 is mainly used to store software programs and data. The transceiver 2602 may include a radio frequency (RF) circuit and an antenna. The RF circuit is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0499] Optionally, the processor 2601, transceiver 2602, and memory 2603 can be connected via a communication bus.

[0500] When the communication device is powered on, the processor 2601 can read the software program in the memory 2603, execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 2601 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit then performs RF processing on the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 2601. The processor 2601 converts the baseband signal into data and processes the data.

[0501] [Detailed Rule 91, 09.05.2026] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor that performs baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged in a remote manner, independent of the communication device.

[0502] In some embodiments, those skilled in the art will recognize that the above-described communication device 2500 can be implemented in the form of the communication device 2500 shown in FIG26.

[0503] As an example, the function / implementation of the processing module 2601 in Figure 25 can be achieved by the processor 2601 in the communication device 2600 shown in Figure 26 calling computer execution instructions stored in the memory 2603. The function / implementation of the transceiver module 2502 in Figure 25 can be achieved by the transceiver 2602 in the communication device 2600 shown in Figure 26.

[0504] As another possible product form, the first communication device in this application may adopt the composition structure shown in FIG27, or include the components shown in FIG27. FIG27 is a schematic diagram of the composition of a communication device 2700 provided in this application. The communication device 2700 may be the first communication device, or a module, chip, or system-on-a-chip in the first communication device.

[0505] As shown in Figure 27, the communication device 2700 includes at least one processor 2701 and at least one communication interface (Figure 27 is merely an example illustrating the inclusion of a communication interface 2704 and a processor 2701). Optionally, the communication device 2700 may also include a communication bus 2702 and a memory 2703.

[0506] Processor 2701 can be a general-purpose central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a PLD, or any combination thereof. Processor 2701 can also be other devices with processing functions, such as circuits, devices, or software modules, without limitation.

[0507] Communication bus 2702 is used to connect different components in communication device 2700, enabling communication between them. Communication bus 2702 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 27, but this does not indicate that there is only one bus or one type of bus.

[0508] [Detailed Rules 91, 09.05.2026] Communication interface 2704 is used for communicating with other devices or communication networks. For example, communication interface 2704 can be a module, circuit, transceiver, or any device capable of communication. Optionally, the communication interface 2704 can also be an input / output interface located within processor 2701, used to implement signal input and signal output for the processor.

[0509] The memory 2703 may be a device with storage function, used to store instructions and / or data. The instructions may be computer programs.

[0510] For example, the memory 2703 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and / or instructions; it may also be a random access memory (RAM) or other type of dynamic storage device capable of storing information and / or instructions; it may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.

[0511] It should be noted that the memory 2703 can exist independently of the processor 2701, or it can be integrated with the processor 2701. The memory 2703 can be located inside or outside the communication device 2700, without limitation. The processor 2701 can be used to execute the instructions stored in the memory 2703 to implement the methods provided in the following embodiments of this application.

[0512] Optionally, the processor 2701 and / or memory 2703 may include an artificial intelligence (AI) module, which is used to implement AI-related functions. The AI ​​module can be implemented through software, hardware, or a combination of both. For example, the AI ​​module may include a radio network intelligent controller (RIC) module. For example, the AI ​​module can be a near real-time RIC or a non-real-time RIC.

[0513] As an optional implementation, the communication device 2700 may also include an output device 2705 and an input device 2706. The output device 2705 communicates with the processor 2701 and can display information in various ways. For example, the output device 2705 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 2706 communicates with the processor 2701 and can receive user input in various ways. For example, the input device 2706 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0514] In some embodiments, those skilled in the art will recognize that the communication device 2500 shown in FIG25 can be implemented in the form of the communication device 2700 shown in FIG27.

[0515] As an example, the function / implementation of the processing module 2501 in Figure 25 can be achieved by the processor 2701 in the communication device 2700 shown in Figure 27 calling computer execution instructions stored in the memory 2703. The function / implementation of the transceiver module 2502 in Figure 25 can be achieved by the communication interface 2704 in the communication device 2700 shown in Figure 27.

[0516] It should be noted that the structure shown in Figure 27 does not constitute a specific limitation on the first communication device. For example, in other embodiments of this application, the first communication device may include more or fewer components than shown, or combine some components, or split some components, or have different component arrangements. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0517] In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.

[0518] As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.

[0519] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0520] As another possible implementation, the communication device also includes a communication interface for communicating with modules outside the communication device.

[0521] It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

[0522] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

[0523] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0524] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0525] It is understood that the systems, apparatuses, and methods described in this application can also be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0526] [Detailed Rules 91, 09.05.2026] The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. The components shown as units may or may not be physical units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0527] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0528] [Detailed Rules 91, 09.05.2026] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The aforementioned computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The aforementioned computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the aforementioned computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The aforementioned computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The aforementioned usable media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)). In embodiments of this application, the computer may include the aforementioned device.

[0529] [Detailed Rules 91, 09.05.2026] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the foregoing drawings, disclosure, and appended claims, can understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0530] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, include: Obtain the first Media Access Control subprotocol data unit (MAC subPDU); If the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, perform any of the following: Discard the first MAC subPDU; or, Discard the first MAC subPDU and any MAC subPDU located after the first MAC subPDU and associated with the first code block CB or the first CB group, wherein the first CB or the first CB group is the CB or CB group associated with the first MAC subPDU or a reserved value, an invalid value, or an unsupported value.

2. The method according to claim 1, characterized in that, The reserved, invalid, or unsupported values ​​include: reserved, invalid, or unsupported logical channel identifier values.

3. The method according to claim 2, characterized in that, The logical channel identifier is either a logical channel identifier (LCID) or an extended logical channel identifier (eLCID).

4. The method according to any one of claims 1-3, characterized in that, The discarding of the first MAC subPDU and the MAC subPDUs located after the first MAC subPDU and associated with the first code block CB or the first CB group includes: Discard the first MAC subPDU, as well as at least one MAC subPDU located after the first MAC subPDU and located in the first CB or the first CB group.

5. The method according to any one of claims 1-4, characterized in that, The first MAC subPDU is a MAC subPDU in the first MAC PDU. The first MAC PDU corresponds to N CBs or CB groups, and each of the N CBs or CB groups is associated with a complete MAC subPDU.

6. The method according to any one of claims 1-3, characterized in that, The discarding of the first MAC subPDU and the MAC subPDUs located after the first MAC subPDU and associated with the first code block CB or the first CB group includes: Discard the first MAC subPDU, the first set of bits in the first CB or the first CB group that is located after the first MAC subPDU, and the second set of bits that is located after the first set of bits and before the first start position; Wherein, the first starting position is the position of the "starting portion of MAC subPDU" associated with the second CB or the second CB group, and the second CB or the second CB group is located after the first CB or the first CB group.

7. The method according to claim 6, characterized in that, The second CB or the second CB group contains information about the location of the "start portion of the MAC subPDU".

8. The method according to any one of claims 1-3, characterized in that, The discarding of the first MAC subPDU and the MAC subPDUs located after the first MAC subPDU and associated with the first code block CB or the first CB group includes: Discard the first MAC subPDU, the first set of bits in the first CB or the first CB group that is located after the first MAC subPDU, and the third set of bits that is located after the first set of bits and before the first boundary identification information. Wherein, the first boundary identification information is the boundary identification information associated with the third CB or the third CB group, and the third CB or the third CB group is located after the first CB or the first CB group.

9. The method according to claim 8, characterized in that, The first boundary identification information includes a first boundary identifier and / or first verification information.

10. The method according to any one of claims 1-3, 8, characterized in that, The first MAC PDU contains the first boundary identification information.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: It is determined that the first MAC PDU supports CB or CB group self-decoding, and the first MAC subPDU is a MAC subPDU in the first MAC PDU.

12. A communication method, characterized in that, include: Obtain the first Media Access Control subprotocol data unit (MAC subPDU); If the first MAC subPDU contains a reserved value, an invalid value, or an unsupported value, a first confirmation message is sent. The first confirmation message is used to indicate that the first MAC PDU was successfully received or that the first MAC PDU no longer needs to be retransmitted. The first MAC PDU is a MAC PDU that contains the first MAC subPDU.

13. The method according to claim 12, characterized in that, The reserved, invalid, or unsupported values ​​include: reserved, invalid, or unsupported logical channel identifier values.

14. The method according to claim 13, characterized in that, The logical channel identifier is either a logical channel identifier (LCID) or an extended logical channel identifier (eLCID).

15. The method according to any one of claims 12 to 14, characterized in that, The method further includes: Stop processing of the remaining MAC subPDU in the first MAC PDU or the remaining code block CB associated with the first MAC PDU; and / or, Discard any remaining MAC subPDUs in the first MAC PDU or any remaining CBs associated with the first MAC PDU.

16. A communication device, characterized in that, It includes a module for performing the method as described in any one of claims 1 to 11; or, it includes a module for performing the method as described in any one of claims 12 to 15.

17. A communication device, characterized in that, The communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1-15.

18. A computer-readable storage medium, characterized in that, A computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method described in any one of claims 1-15 to be performed.

19. A computer program product, characterized in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, the method described in any one of claims 1-15 is performed.

Images