Data processing method and communication apparatus

Abstract

The present application relates to the field of communications, and provides a data processing method and a communication apparatus, capable of reducing service latency. In the method, a first communication apparatus generates a first TB, and sends the first TB to a second communication apparatus, wherein the first TB corresponds to N MAC subPDUs and L pieces of boundary identification information, N is a positive integer, and L is a positive integer less than or equal to N. Further, the second communication apparatus processes the first TB on the basis of first boundary identification information, wherein the first boundary identification information is one of the L pieces of boundary identification information.

Description

Data processing methods and communication devices

[0001] This application claims priority to Chinese patent application filed on August 27, 2024, with the State Intellectual Property Office of China, application number 202411188113.9, entitled "Data Processing Method and Communication Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to data processing methods and communication devices. 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 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, if even one CB CRC check fails at the receiving end, the entire TB cannot be submitted to the MAC layer for processing and will need to wait for a hybrid automatic repeat request (HARQ) retransmission, which increases service latency and affects communication quality. Summary of the Invention

[0005] This application provides a data processing method and a communication device that can reduce service latency.

[0006] Firstly, a data processing method is provided. This method can be executed by a second communication device, or by a component of the second communication device, such as a processor, chip, or chip system of the second communication device, or by a logic module or software capable of implementing all or part of the functions of the second communication device. The second communication device can be an access network device or a terminal. The method includes: receiving a first TB, the first TB corresponding to N media access control sub-protocol data units (MAC subPDUs) and L boundary identification information, where N is a positive integer and L is a positive integer less than or equal to N. Further, processing the first TB based on the first boundary identification information, where the first boundary identification information is one of the L boundary identification information.

[0007] Based on the method provided in the first aspect, the N MAC subPDUs corresponding to the first TB are divided into L groups or L+1 groups of MAC subPDUs using L boundary identification information. The MAC subPDUs divided by the boundary identification information can be considered independent of each other, and the second communication device can decode each group of MAC subPDUs independently. Decoding a group of MAC subPDUs does not depend on other groups of MAC subPDUs. Even if at least one CB corresponding to a group of MAC subPDUs fails to be received, the subsequently successfully received CBs can still be submitted to the MAC layer for continued decoding, enabling the second communication device to process successfully received CBs in a timely manner, thereby reducing service latency. Furthermore, timely submission of subsequently successfully received CBs to the MAC layer reduces the number of CBs that cannot be submitted to the MAC layer, thus reducing storage requirements, i.e., reducing memory increases, saving costs, and also reducing device power consumption caused by double data rate (DDR) erasure and rewriting.

[0008] In one possible design, the first boundary identification information includes a first boundary identifier and / or first verification information.

[0009] Based on this possible design, the format of the boundary identification information is designed so that the N MAC subPDUs corresponding to the first TB can be divided into L groups or L+1 groups of MAC subPDUs through boundary identifiers and / or verification information. This facilitates the second communication device to decode each group of MAC subPDUs individually. Even if the CB corresponding to other groups of MAC subPDUs fails to be received, the current CB can still be decoded, thereby reducing the number of CBs that cannot be submitted to the MAC layer for processing, thus reducing storage requirements, i.e. reducing the increase in memory, saving costs, and reducing processing latency.

[0010] In one possible design, if the first verification information passes the verification, the first TB is processed based on the first boundary identification information.

[0011] Based on this possible design, the verification information in the first boundary identification information needs to be verified before processing the first TB based on the first boundary identification information. Only if the verification passes will the second communication device process the first TB based on the first boundary identification information, which helps to improve the reliability of the boundary identification information.

[0012] In one possible design, the first boundary identification information also includes first length information, which indicates the length of one or more MAC subPDUs associated with the first boundary identification information.

[0013] Based on this possible design, the first boundary identification information is also used to indicate the byte length associated with the first boundary identification information (i.e., the byte length included in at least one MAC subPDU associated with the first identification information). After the second communication device successfully decodes the first boundary identification information, it can determine the position of the next set of MAC subPDUs (or the next boundary identification information) based on the first length information in the first boundary identification information. This can avoid the second communication device from searching and verifying the next boundary identification information, which is beneficial to saving the power consumption of the second communication device.

[0014] In one possible design, the first boundary identification information is contained in the first MAC subheader, which is the MAC subheader of one of the N MAC subPDUs.

[0015] Based on this possible design, the location of the boundary identification information is designed. Since the format or byte length of the MAC subheader is not fixed, the boundary identification information is located in the MAC subheader. This eliminates the need to determine the starting position of the MAC subheader based on its format or byte length, which helps improve the accuracy of determining the starting bit position of the MAC subheader (or the boundary of the MAC subPDU) based on the boundary identification information.

[0016] In one possible design, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information.

[0017] In one possible design, the first verification information is used to verify fields in the first MAC subheader other than the first boundary identification information; or, the first verification information is used to verify M1 bytes after the first boundary identification information, where M1 is a positive integer; or, the first verification information is used to verify the first length information.

[0018] Based on this possible design, the verification information in the boundary identification information is designed, and multiple design schemes for the verification information are provided, which helps to improve the flexibility of the verification information.

[0019] In one possible design, the first boundary identification information is located before the first MAC subheader or the first MAC subPDU, and / or the first boundary identification information is located after the second MAC subPDU; wherein the first MAC subheader is the MAC subheader of one of the N MAC subPDUs, the first MAC subPDU and the second MAC subPDU are two adjacent MAC subPDUs among the N MAC subPDUs, and the second MAC subPDU is located before the first MAC subPDU.

[0020] Based on this possible design, the position of the first boundary identifier information is designed. Since the format or byte length of the MAC subheader is not fixed, the first boundary identifier information can be located before the first MAC subheader, or before the first MAC subPDU, or after the second MAC subPDU, or both before the first MAC subPDU (or the first MAC subheader) and after the second MAC subPDU. This eliminates the need to determine the starting position of the MAC subheader based on its format or byte length, which helps improve the accuracy of determining the starting bit position of the MAC subheader (or the boundary of the MAC subPDU) based on the boundary identifier information.

[0021] In one possible design, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information, or the first MAC subheader is the MAC subheader of the MAC subPDU following the last MAC subPDU associated with the first boundary identification information.

[0022] In one possible design, the first verification information is used to verify the first MAC subheader; or, the first verification information is used to verify the M1 bytes following the first boundary identification information, where M1 is a positive integer; or, the first verification information is used to verify the first length information; or, the first verification information is used to verify the M2 bytes preceding the first boundary identification information, where M2 is a positive integer.

[0023] Based on this possible design, the verification information in the boundary identification information is designed, and multiple design schemes for the verification information are provided, which helps to improve the flexibility of the verification information.

[0024] In one possible design, the first TB corresponds to C CBs, which include the first CB and the second CB, with the first CB preceding the second CB, and C being an integer greater than 1. In the event of a reception error in the first CB, boundary identification information is retrieved from the second CB; if the first boundary identification information is found in the second CB, the MAC subPDU associated with the first boundary identification information is parsed based on it.

[0025] Based on this possible design, each CB corresponding to the first TB at the receiving end is decoded independently. If a CB (e.g., the first CB) is received incorrectly, subsequent CBs (e.g., the second CB) are submitted to the MAC layer for further decoding. This allows the second communication device to process successfully received CBs promptly, thereby reducing service latency. Furthermore, promptly submitting subsequently received CBs to the MAC layer reduces the number of CBs that cannot be submitted to the MAC layer, thus reducing storage requirements, i.e., reducing memory usage and saving costs.

[0026] In one possible design, if the size of the first TB is greater than or equal to a first threshold, the first TB corresponds to boundary identification information; or, if the size of the first TB is less than the first threshold, the first TB does not correspond to boundary identification information; or, if the number of CBs or CB groups corresponding to the first TB is greater than or equal to a second threshold, the first TB corresponds to boundary identification information; or, if the number of CBs or CB groups corresponding to the first TB is less than the second threshold, the first TB does not correspond to boundary identification information.

[0027] Based on this possible design, the second communication device can determine whether the first TB corresponds to boundary identification information based on the relationship between the size of the first TB and a first threshold, or based on the relationship between the number of CBs or CB groups corresponding to the first TB and a second threshold. Aligning the first and second communication devices based on this possible design to determine whether the first TB corresponds to boundary identification information helps improve the accuracy of the second communication device in decoding the first TB.

[0028] In one possible design, a first indication is received, which corresponds to boundary identification information for the first TB.

[0029] Based on this possible design, the second communication device can determine whether the first TB corresponds to boundary identification information according to the instructions of the first communication device. Aligning the first and second communication devices based on this possible design to determine whether the first TB corresponds to boundary identification information helps improve the accuracy of the second communication device in decoding the first TB.

[0030] Secondly, a data processing method is provided. This method can be executed by a first communication device, or by a component of the first communication device, such as a processor, chip, or chip system of 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. The first communication device can be a terminal or an access network device. The method includes: generating a first TB, which corresponds to N MAC subPDUs and L boundary identification information, where N is a positive integer and L is a positive integer less than or equal to N; further, transmitting the first TB.

[0031] Based on the method provided in the second aspect, the N MAC subPDUs corresponding to the first TB are divided into L groups or L+1 groups of MAC subPDUs using L boundary identification information. Each boundary identification information indicates the boundary of at least one MAC subPDU. The groups of MAC subPDUs divided by the boundary identification information can be considered independent of each other, and each group of MAC subPDUs can be decoded independently. Decoding a group of MAC subPDUs does not depend on other groups of MAC subPDUs. Even if at least one CB corresponding to a group of MAC subPDUs fails to be received, the subsequently successfully received CBs can still be submitted to the MAC layer for continued decoding, enabling the second communication device to process the successfully received CBs in a timely manner, thereby reducing service latency. Furthermore, timely submission of subsequently successfully received CBs to the MAC layer reduces the number of CBs that cannot be submitted to the MAC layer for processing, thereby reducing storage requirements, i.e., reducing memory increases, saving costs, and also reducing device power consumption caused by DDR erasure and writing.

[0032] In one possible design, the first boundary identification information is one of the L boundary identification information, and the first boundary identification information includes a first boundary identifier and / or first verification information.

[0033] In one possible design, the first boundary identification information also includes first length information, which indicates the length of the MAC subPDU associated with the first boundary identification information.

[0034] In one possible design, the first boundary identification information is contained in the first MAC subheader, which is the MAC subheader of one of the N MAC subPDUs.

[0035] In one possible design, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information.

[0036] In one possible design, the first verification information is generated based on fields in the first MAC subheader other than the first boundary identification information; or, the first verification information is generated based on M1 bytes following the first boundary identification information, where M1 is a positive integer; or, the first verification information is generated based on the first length information.

[0037] In one possible design, the first boundary identification information is located before the first MAC subheader or the first MAC subPDU, and / or the first boundary identification information is located after the second MAC subPDU; wherein the first MAC subheader is the MAC subheader of one of the N MAC subPDUs, the first MAC subPDU and the second MAC subPDU are two adjacent MAC subPDUs among the N MAC subPDUs, and the second MAC subPDU is located before the first MAC subPDU.

[0038] In one possible design, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information, or the first MAC subheader is the MAC subheader of the MAC subPDU following the last MAC subPDU associated with the first boundary identification information.

[0039] In one possible design, the first verification information is generated based on the first MAC subheader; or, the first verification information is generated based on M1 bytes after the first boundary identification information, where M1 is a positive integer; or, the first verification information is generated based on the first length information; or, the first verification information is generated based on M2 bytes before the first boundary identification information, where M2 is a positive integer.

[0040] In one possible design, if the size of the first TB is greater than or equal to a first threshold, the first TB corresponds to boundary identification information; or, if the size of the first TB is less than the first threshold, the first TB does not correspond to boundary identification information; or, if the number of CBs or CB groups corresponding to the first TB is greater than or equal to a second threshold, the first TB corresponds to boundary identification information; or, if the number of CBs or CB groups corresponding to the first TB is less than the second threshold, the first TB does not correspond to boundary identification information.

[0041] In one possible design, a first indication message is sent, which indicates that the first TB corresponds to boundary identification information.

[0042] Thirdly, 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.

[0043] 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.

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

[0045] Fourthly, a communication device is provided, comprising: a processor and a memory; the memory being used to store computer instructions that, when executed by the processor, cause the communication device to perform the method described in any of the above aspects and any possible design thereof.

[0046] Fifthly, 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 the methods described in any of the above aspects and any possible designs thereof.

[0047] A sixth aspect provides a communication device comprising: at least one processor; said processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the methods described in any of the foregoing aspects and any possible designs thereof. The memory may be coupled to the processor, or may be independent of the processor.

[0048] 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.

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

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

[0051] The communication device described in the third to seventh aspects may be the second communication device in the first aspect, or a device included in the second communication device, such as a chip or chip system; or the communication device may be the first communication device in the second aspect, or a device included in the first communication device, such as a chip or chip system.

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

[0053] 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.

[0054] A ninth aspect provides a computer-readable storage medium storing a computer program or instructions that, when executed on a communication device, enable the communication device to perform the methods described in any of the foregoing aspects and any possible design thereof.

[0055] 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 the methods described in any of the foregoing aspects and any possible design thereof.

[0056] Eleventhly, a communication system is provided, comprising a first communication device and a second communication device. The first communication device is used to implement the method described in the second aspect and any possible design thereof, and the second communication device is used to implement the method described in the first aspect and any possible design thereof.

[0057] The technical effects of any of the design methods in aspects three through eleven 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

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

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

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

[0061] Figure 4 is a schematic diagram of an LCP provided in this application;

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

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

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

[0065] Figures 8-10 are schematic diagrams of the structure of the MAC subheader provided in this application;

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

[0067] Figure 12 is a schematic diagram of a CB receiver provided in this application;

[0068] Figure 13 is a flowchart illustrating a data processing method provided in this application;

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

[0070] Figures 15-17 are schematic diagrams of a MAC subheader containing boundary identification information provided in this application;

[0071] Figure 18 is a schematic diagram of a boundary marker provided in this application;

[0072] Figures 19-20 are schematic diagrams of the second communication device provided in this application processing the first TB based on the first boundary identification information;

[0073] Figures 21-23 are schematic diagrams of the communication device provided in this application. Detailed Implementation

[0074] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0075] Hereinafter, 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 technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0076] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0077] 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.

[0078] It should be understood that in this application, "at least one (item)" means one or more. "More than one" means two or more. "At least two (items)" means two or three or more. "And / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can 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. Both "...when" and "if" indicate that a corresponding action will be taken under certain objective circumstances. They are not time limits, nor do they require a judgment action to be taken when the action is taken, nor do they imply any other limitations.

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

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

[0081] 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.

[0082] 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.

[0083] 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.

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

[0085] 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.

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

[0087] 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.

[0088] 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.

[0089] 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.

[0090] In this application, unless otherwise specified, the same or similar parts between the various embodiments can 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 mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0091] To facilitate a detailed understanding of the embodiments of this application, the system architecture involved in the embodiments of this application will be described below.

[0092] 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.

[0093] 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.

[0094] Figure 1 illustrates a possible, non-limiting system diagram. As shown in Figure 1, 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 connected to core network 200 wirelessly or via wired connection. 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.

[0095] 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.

[0096] 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.

[0097] 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.

[0098] 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.

[0099] 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).

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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).

[0104] 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).

[0105] 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.

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

[0107] 1. Protocol layer structure:

[0108] 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.

[0109] As shown in Figure 2(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.

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

[0111] 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.

[0112] Figure 3 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 3 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.

[0113] For example, 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.

[0114] Furthermore, for the sending end, the data received by a certain layer 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).

[0115] For the receiving end, the data received by a certain layer from the lower layer is called PDU, and the data that the layer passes to the upper layer is called SDU. For that 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).

[0116] 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, which is then submitted 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, which is then submitted to the MAC entity, and so on. After certain processing at the PHY layer, air interface transmission is performed. For example, data transmitted over the air interface can be called a transport block (TB).

[0117] Correspondingly, after the terminal's PHY 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 does not process it to obtain a MAC SDU, which is then submitted to the RLC entity. The RLC entity processes the data received from the MAC entity (i.e., the RLC PDU) or does not process it to obtain an RLC SDU, which is then submitted to the PDCP entity, and so on. After the data reaches 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).

[0118] 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.

[0119] 2. MAC package:

[0120] 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.

[0121] For example, LCP is used to determine the data transmitted on uplink (UL) new transmission resources, such as one or more MAC CEs and / or one or more MAC SDUs. MAC CE and MAC SDU multiplexing is used to multiplex the MAC CE and / or MAC SDU determined after performing the LCP procedure into a single MAC PDU.

[0122] 3. LCP process:

[0123] Currently, the LCP process is granular at the level 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.

[0124] 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.

[0125] For example, LCP may include B j Maintenance, logical channel selection, and resource allocation are related. As shown in Figure 4, during the LCP process, LCH selection is first performed according to LCP constraints (or logical channel (LCH) constraints), and then resources are allocated based on the priority of the selected logical channel (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.

[0126] 3.1, B j maintain:

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

[0128] 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 bucket size, 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.

[0129] 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 are configured to the terminal by the access network equipment.

[0130] 3.2 Logical Channel Selection:

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

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

[0133] 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...

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

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

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

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

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

[0139] 3.3 Resource Allocation:

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

[0141] 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.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] 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.

[0146] 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):

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

[0148] Configured grant confirmation (MAC CE);

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

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

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

[0152] Padding BSR MAC CE.

[0153] 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 (MAC SDU), and does not constitute any limitation on this application.

[0154] 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 5, 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 5 represent the order of resource allocation.

[0155] 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.

[0156] Referring to Figure 5, 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 filler in Figure 5), or in other words, this part of the data could not be transmitted in this new transmission.

[0157] It should be noted that the example shown in Figure 5 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.

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

[0159] MAC CE and MAC SDU multiplexing is used to multiplex the MAC CE and / or MAC SDU determined after LCP execution 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:

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

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

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

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

[0164] 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 0, meaning padding is optional. Furthermore, in the current MAC PDU, the MAC CEs are placed together.

[0165] For example, Figure 6 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 7 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.

[0166] Each MAC subPDU contains a MAC subheader and a MAC CE, MAC SDU, or padding; that is, one MAC subheader corresponds to one 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 header fields R / F / LCID / (eLCID) / L. For example, the MAC subheader corresponding to fixed-size MAC CEs and paddings consists of the header fields R / LCID / (eLCID). For example, the MAC subheader corresponding to MAC SDUs containing CCCHs consists of the header fields R / LCID. Example:

[0167] LCID: Logical Channel Identifier (LCID) field, used to indicate the logical channel of the MAC SDU corresponding to the MAC subheading, or the type of the MAC CE corresponding to the MAC subheading, or the padding corresponding to the MAC subheading. 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 the LCID field.

[0168] eLCID: Extended Logical Channel Identifier 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, with a size of 8 bits or 16 bits. The eLCID field is optional.

[0169] 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.

[0170] 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.

[0171] R: Reserved bit, set to 0.

[0172] For example, Figure 8 shows the structure of a MAC subheader containing the R / F / LCID / (eLCID) / L fields when the L field size is 8 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. For example, Figure 9 shows the structure of a MAC subheader containing the R / F / LCID / (eLCID) / L fields when the L field size is 16 bits. 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. As shown in Figure 9(c), the MAC subheader includes the eLCID field, which is 16 bits in size. For example, Figure 10 shows the structure of a MAC subheader containing the R / LCID / (eLCID) field. As shown in Figure 10(a), the MAC subheader does not include the eLCID field. As shown in Figure 10(b), the MAC subheader includes the eLCID field, which is 8 bits in size. The MAC subheader is octet (or byte) aligned.

[0173] 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 8(a) as an example, the receiver determines the size of the L field based on the F field of the MAC subheader, determines the type of logical channel or MAC CE corresponding to the MAC subheader based on the LCID field, 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 identified as a MAC SDU or a MAC CE, and then decoded.

[0174] 5. Physical layer data processing flow:

[0175] After assembling the MAC PDU at the sending end's MAC layer, it submits the MAC PDU to the PHY layer. For example, a 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 11(a), the PHY layer first adds a cyclic redundancy check (CRC) code to the TB. If the TB (or TB and TB CRC) is large, it divides the TB (or TB and TB CRC) into multiple CBs and adds a CB CRC to each CB.

[0176] 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.

[0177] For example, 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. K′ is the first size of each CB. B′ = B + C·L.

[0178] For example, based on the above partitioning principles, the first size of the CB includes the size of the data portion (or payload portion) of the CB and the size of the TB CRC, or, includes the size of the data portion of the CB and the size of the CB CRC, or, includes the size of the data portion of the CB, 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).

[0179] 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.

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

[0181] 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.

[0182] Furthermore, based on the above division of CBs, the structure of CBs is not related to that of MAC PDUs. The boundary (or start bit) of each CB is not necessarily the start 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. 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, so the boundary (or start bit) of each CB is not necessarily the start bit of a MAC subPDU. For example, as shown in Figure 11(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.

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

[0184] For the receiving end, after the physical layer receives a 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, after receiving a CB or TB, 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 is successful, the physical layer submits the TB to the MAC layer. However, if even one CB CRC check fails, the entire TB cannot be submitted to the MAC layer for processing and must wait for a hybrid automatic repeat request (HARQ) retransmission (e.g., TB or code block group (CBG) retransmission). This increases service latency and affects communication quality. For example, it may cause data to fail to arrive within the service's latency requirements, thus affecting service communication quality or system capacity.

[0185] To address this issue, one possible solution is as follows: After the PHY layer at the receiving end receives the CB (or TB), it performs a CB CRC check. If the CB CRC check passes, the CB is submitted to the MAC layer for processing (or the CB is processed for subsequent data) without waiting for the TB CRC check result. However, this can only be done by submitting the CB to the MAC layer for processing (or processing the CB for subsequent data) in order.

[0186] Since the division of CBs is independent of the structure of MAC PDUs, if the CRC check of a CB fails, the receiver 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). Therefore, it cannot decode the subsequent CBs, resulting in all subsequent CBs not being submitted to the MAC layer for processing (or, all subsequent CBs not being able to perform subsequent data processing). It needs to wait for HARQ retransmission (e.g., TB or CBG retransmission), which increases service latency and affects communication quality. For example, it may cause data to not arrive within the service's latency requirements, thus affecting service communication quality or system capacity. For example, as shown in Figure 12, because the CRC check of CB2 fails, CB2 is not successfully received. Therefore, all subsequent CBs, i.e., CB3, ..., CB... C-2 CB C-1 None of them can be submitted to the MAC layer for processing (or, cannot be processed further).

[0187] Another possible implementation involves processing data (e.g., at least one of PHY layer processing, MAC layer processing, RLC layer processing, and PDCP layer processing) on ​​on-chip memory. However, the 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 with 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 synchronous dynamic random access memory (SDRAM).

[0188] For CBs that cannot be submitted to the MAC layer for processing (or cannot be processed subsequently), if they are all cached in on-chip memory, more on-chip memory is needed, which increases 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), which increases cost. In addition, the erasing and writing of DDR will also increase device power consumption.

[0189] It can be seen that even without waiting for (or considering) the TB CRC check result, CBs are submitted sequentially if the CB CRC check passes. If a CB CRC check fails, it will still increase service latency, posing a greater challenge, especially for services requiring lower latency in the future. Furthermore, it will increase equipment costs, particularly for future higher-speed services, where cost pressure will be even greater. If CBs cannot be submitted to the MAC layer for processing using DDR storage, it will also increase equipment power consumption.

[0190] Based on this, this application provides a data processing method in which the boundary (or start bit or end bit) of at least one MAC subPDU corresponding to a TB is marked at the transmitting end using boundary identification information. If a CB fails to be received, the boundary of the MAC subPDU can be determined in subsequent CBs by retrieving the boundary identification information, thereby enabling the receiving end to perform decoding at the granularity of CBs or CB groups. This avoids the problem that a single CB error (or a CB failure to be received, or a CB CRC check failure / failure / error) will cause all subsequent CBs of the entire TB or the erroneous CB (or the failed CB, or the CB CRC check failure / failure / error) to be unable to be processed (or to be stuck), thus helping to reduce latency.

[0191] Furthermore, based on the data processing method of this application, subsequently successfully received CBs or CB groups can be promptly submitted to the MAC layer for processing. This reduces the number of CBs that cannot be submitted to the MAC layer, thereby reducing storage requirements, i.e., reducing the need for additional memory (e.g., not requiring a large amount of on-chip memory), which can save costs. Alternatively, it can reduce DDR bandwidth requirements (e.g., not requiring a large amount of DDR bandwidth), which can also save costs. Simultaneously, it can reduce device power consumption caused by DDR erasure and writing. It is also beneficial for addressing the challenges of future services requiring lower latency and / or higher data rates.

[0192] In this embodiment, the data processing method provided by this application is described using the interaction between a terminal and an access network device as an example. It should be noted that the message names, parameter names, or information names between devices in the following embodiments are merely examples, and may be different in other embodiments. The method provided in this application does not specifically limit these names.

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

[0194] It is understood that this application uses the first and second communication devices as examples to illustrate the execution of the interaction, but this application does not limit the execution of 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 by a logic node, logic module, or software that can implement all or part of the functions of the first communication device; similarly, the method executed by the second communication device can also be executed by a module (e.g., a chip, chip system, or processor) applied to the second communication device, or by a logic node, logic module, or software that can implement all or part of the functions of the second communication device.

[0195] In the data processing method provided in this application, the sending end and / or receiving end of TB (or, the first communication device and / or the second communication device) can determine the data format corresponding to the first TB according to at least one of the following embodiments (e.g., determining whether the first TB corresponds to boundary identification information).

[0196] It should be noted that the TB mentioned in this application may include / be replaced by MAC PDU, or data, or code word (CW), or other names, without limitation, and will not be described again in subsequent embodiments. For example, the first TB may include / be replaced by the first MAC PDU, or the first data, or the first CW, or other names, without limitation, and will not be described again in subsequent embodiments.

[0197] It should also be noted that the MAC subPDU mentioned in this application may include / be replaced by MAC SDU, or MAC CE, or padding, or data unit 1, or other names, without limitation. This will be uniformly stated here, and will not be repeated in subsequent embodiments.

[0198] For example, in this application, whether there is a corresponding condition can be included / replaced with: corresponding condition or not corresponding condition. This is explained uniformly here and will not be repeated in subsequent embodiments.

[0199] For example, in this application, the corresponding word can be included / replaced with: include, or contain. This is explained uniformly here and will not be repeated in subsequent embodiments.

[0200] Optionally, in one possible implementation, the first communication device and / or the second communication device determine whether the first TB corresponds to boundary identification information based on the first indication information (or the first field).

[0201] For example, the first indication information includes information on whether the first TB corresponds to boundary identification information.

[0202] For example, the first field includes / carries information on whether the first TB corresponds to boundary identification information.

[0203] Optionally, the first indication information is carried in the first field.

[0204] For example, the second communication device may send first instruction information (or first field) to the first communication device. Accordingly, the first communication device receives the first instruction information (or first field).

[0205] Alternatively, for example, the first communication device may send first instruction information (or a first field) to the second communication device. Accordingly, the second communication device receives the first instruction information (or the first field).

[0206] For example, when the first communication device is a terminal and the second communication device is an access network device, the second communication device can send first indication information (or a first field) to the first communication device. Correspondingly, the first communication device receives the first indication information (or the first field). For example, the first communication device determines whether the first TB corresponds to boundary identification information based on the first indication information (or the first field).

[0207] For example, when the first communication device is an access network device and the second communication device is a terminal, the first communication device can send first indication information (or a first field) to the second communication device. Correspondingly, the second communication device receives the first indication information (or the first field). For instance, the second communication device determines whether the first TB corresponds to boundary identification information based on the first indication information (or the first field).

[0208] For example, the first indication information (or the first field) may occupy at least one bit (such as 1 bit or 2 bits or others).

[0209] For example, taking the first indication information (or the first field) as occupying 1 bit, if the value of the bit is "0" or "false", it indicates that the first TB does not have corresponding boundary identification information; if the value of the bit is "1" or "true", it indicates that the first TB has corresponding boundary identification information; or vice versa.

[0210] For example, if the first indication information (or the first field) occupies 1 bit, if the value of the bit is valid (e.g., 0 or 1), it indicates that the first TB has boundary identification information; if the value of the bit is invalid (e.g., empty or null), it indicates that the first TB does not have boundary identification information.

[0211] For example, if the first indication information (or the first field) exists (or is sent), it indicates that the first TB corresponds to boundary identification information; if the first indication information (or the first field) does not exist (or is not sent), it indicates that the first TB does not correspond to boundary identification information; or vice versa.

[0212] For example, the first indication information includes information on the boundary identification information corresponding to the first TB.

[0213] For example, the first field includes / carries information corresponding to the first TB with boundary identification information.

[0214] For example, when the first TB corresponds to boundary identification information, the second communication device sends first indication information (or first field) to the first communication device, the first indication information (or first field) indicating that the first TB corresponds to boundary identification information. Accordingly, the first communication device receives the first indication information (or first field).

[0215] Alternatively, for example, if the first TB does not correspond to boundary identification information, the second communication device does not send the first indication information (or the first field) to the first communication device. The first indication information (or the first field) indicates that the first TB corresponds to boundary identification information. Accordingly, the first communication device cannot / does not receive the first indication information (or the first field).

[0216] For example, when the first TB corresponds to boundary identification information, the first communication device sends first indication information (or first field) to the second communication device, the first indication information (or first field) indicating that the first TB corresponds to boundary identification information. Accordingly, the second communication device receives the first indication information (or first field).

[0217] Alternatively, for example, if the first TB does not correspond to boundary identification information, the first communication device does not send the first indication information (or the first field) to the second communication device. The first indication information (or the first field) indicates that the first TB corresponds to boundary identification information. Accordingly, the second communication device cannot / does not receive the first indication information (or the first field).

[0218] As one possible implementation, the first indication information (or the first field) is associated with one of the following, or the first indication information (or the first field) is indicated / transmitted at a granularity of one of the following: terminal, downlink control information (DCI), TB, semi-persistent scheduling (SPS), configuration grant (CG), LCH, radio bearer (RB). For example, SPS and / or CG may be transport resources indicated by the access network device via RRC (or, RRC and DCI).

[0219] For example, associating the first indication information with a terminal can indicate that different terminals can correspond to different first indication information (or first field). For example, associating the first indication information with DCI can indicate that different DCI schedules / corresponding TBs can correspond to different first indication information (or first field). For example, associating the first indication information with TB can indicate that different TBs can correspond to different first indication information (or first field). For example, associating the first indication information with SPS / CG can indicate that different SPS / CGs can correspond to different first indication information (or first field). Associating the first indication information with RB can indicate that different RBs can correspond to different first values; for example, different RBs corresponding to different TBs can correspond to different first indication information (or first field).

[0220] For example, when the first TB corresponds to boundary identification information, the first communication device sends first indication information (or first field) to the second communication device. The first indication information (or first field) includes information about the first TB corresponding to boundary identification information.

[0221] For example, if the first TB does not correspond to boundary identification information, the first communication device may send the first indication information (or the first field) to the second communication device or may not send the first indication information (or the first field). If the second communication device receives the first indication information (or the first field) from the first communication device or does not receive the first indication information (or the first field), then the second communication device determines that the first TB does not correspond to boundary identification information.

[0222] Optionally, the first indication information (or the first field) may be carried in at least one of the following: first control information or information of the first control information (e.g., at least one of the format of the first control information, scrambling information, time domain resources, search space, frequency domain resources, control resource set (CORESET), or others, without limitation), or information of the first resource, or others, without limitation.

[0223] For example, at least one of the first indication information, the second information, and the third information can be carried by at least one of the following: the format of the control information (e.g., a different, special, or separate control information format), the scrambling information of the control information (e.g., scrambling information of a different, special, or separate control information format), the information in the control information, the time-domain resources of the control information (e.g., the time-domain resources / search space of a different, special, or separate control information format), and the frequency-domain resources of the control information (e.g., the frequency-domain resources / CORESET of a different, special, or separate control information format). For example, at least one of the first indication information, the second information, and the third information can be indicated by at least one of the following: the format of the different, special, or separate control information, the scrambling information of the control information, the information in the control information, the time-domain resources of the control information, the search space, the frequency-domain resources of the control information, and the CORESET. For example, the control information can include / be replaced by: DCI.

[0224] For example, in this application, "based on the first instruction information (or the first field)," or "based on the first instruction information," may include / be replaced by: "based on control information" or information about control information (e.g., at least one of the following: control information format, scrambling information, time-domain resources, search space, frequency-domain resources, and CORESET). This will be uniformly described here and will not be repeated hereafter. For example, "based on the control information" or "based on the information about control information" may include / be replaced by: "first control information" or "based on the information about first control information." For example, "control information" may include / be replaced by: "first control information."

[0225] For example, the first control information is used to schedule the first resource. For example, the first resource is used to carry / transmit the first TB. For example, the information of the first resource may include / be replaced by at least one of the following: configuration information of the first resource.

[0226] For example, the first resource can be a dynamic resource, or a configuration resource, or an SPS resource, or a CG resource.

[0227] For example, the first resource is a dynamic resource, and the first instruction information (or the first field) is carried in the first control information.

[0228] For example, the first resource is a configuration resource, an SPS resource, or a CG resource, and the first instruction information (or the first field) is carried in the information of the first resource.

[0229] Optionally, the first communication device and / or the second communication device may determine whether the first TB corresponds to boundary identification information based on the second information and / or the third information.

[0230] For example, the second information includes information corresponding to the boundary identification information of the first TB.

[0231] For example, the third information includes information that the first TB does not correspond to boundary identification information.

[0232] Optionally, the second and / or third information may be carried on the first field.

[0233] For example, taking the first field as an example that occupies 1 bit, if the value of the bit is "0" or "false", it indicates the third information; if the value of the bit is "1" or "true", it indicates the second information; or vice versa.

[0234] For example, taking the first field as an example that occupies 1 bit, if the value of the bit is valid (e.g., 0 or 1), it indicates the second information; if the value of the bit is invalid (e.g., empty or null), it indicates the third information.

[0235] For example, if the first field exists (or is sent), it indicates the second message; if the first field does not exist (or is not sent), it indicates the third message; or vice versa.

[0236] For example, the first communication device and / or the second communication device determine, based on the second information, that the first TB corresponds to boundary identification information. Alternatively, the first communication device and / or the second communication device determine, based on the third information, that the first TB does not correspond to boundary identification information.

[0237] For example, the second communication device can send second information or third information to the first communication device. Accordingly, the first communication device receives the second information or third information.

[0238] Alternatively, for example, the first communication device may send second information or third information to the second communication device. Accordingly, the second communication device receives the second information or third information.

[0239] For example, the content related to the second and / or third information can be referenced to the content related to the first instruction information. For instance, the first instruction information can be replaced with the second and / or third information for understanding, which will not be elaborated here.

[0240] Optionally, in another possible implementation, the first communication device and / or the second communication device determine whether the first TB corresponds to boundary identification information based on the first condition and / or the second condition.

[0241] For example, if the first condition is met, the first communication device and / or the second communication device determine that the first TB corresponds to boundary identification information.

[0242] For example, if the second condition is met, the first communication device and / or the second communication device determine that the first TB does not correspond to boundary identification information.

[0243] For example, the first condition may include at least one of the following: the size of the first TB is greater than or equal to a first threshold; or, the number of CBs or CB groups corresponding to the first TB is greater than or equal to a second threshold. For example, the size of the first TB may include / be replaced by: the TBS of the first TB (or, corresponding to), or, the size of the payload of the first TB (or, corresponding to), or, the size of the payload, or, the payload size.

[0244] For example, the second condition may include at least one of the following: the size of the first TB is less than the first threshold; or, the number of CBs or CB groups corresponding to the first TB is less than the second threshold.

[0245] For example, satisfying the second condition can include / replace it with: not satisfying the first condition.

[0246] For example, the specific value of the first threshold or the second threshold can be adjusted according to the actual application scenario. This application does not specifically limit the specific value of the first threshold or the second threshold.

[0247] It is understood that the thresholds mentioned in this application (e.g., the first threshold and / or the second threshold) may be negotiated / agreed upon by the first and second communication devices (e.g., indicated by the first communication device to the second communication device, or indicated by the second communication device to the first communication device, or the first and second communication devices agree on a specific value for the threshold), or they may be configured by the network device (e.g., configured by the network device to the second communication device, or configured by the network device to the first communication device), or they may be specified by the communication protocol, or they may be predefined. This application itself does not impose specific limitations. For example, the network device may include / be replaced by: an access network device.

[0248] As one possible implementation, the first threshold and / or the second threshold are associated with one of the following, or the first threshold and / or the second threshold are indicated at a granularity of one of the following: terminal, DCI, TB, SPS, CG, LCH, RB.

[0249] Optionally, the CB group in this application may or may not be a CBG. 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.

[0250] For example, in the embodiments of this application, a CB group may include / be replaced by a CB set, or other names, without limitation. This is uniformly stated here and will not be repeated in subsequent embodiments. For example, in the embodiments of this application, a CB or a CB group may include / be replaced by a data unit, or data unit 2, or other names, without limitation. This is uniformly stated here and will not be repeated in subsequent embodiments.

[0251] For example, through the above implementation, the second communication device and the first communication device can align the data format corresponding to the first TB. For example, the second communication device and the first communication device can align whether there is boundary identification information in the first TB.

[0252] For example, the data format corresponding to the first TB may include / be replaced with: the data format of the MAC PDU corresponding to the first TB, or the data format of the first TB corresponding to the first resource (or, scheduled), or the data format of the MAC PDU corresponding to the first resource (or, scheduled).

[0253] For example, whether the first TB corresponds to boundary identification information can include / be replaced by: whether the MAC PDU corresponding to the first TB corresponds to boundary identification information, or whether the first TB corresponding to the first resource (or, scheduled) corresponds to boundary identification information, or whether the MAC PDU corresponding to the first TB corresponding to the first resource (or, scheduled) corresponds to boundary identification information.

[0254] For example, the boundary identification information corresponding to the first TB can include / be replaced by: the MAC PDU corresponding to the first TB has boundary identification information, or the first TB corresponding to the first resource (or, scheduled) has boundary identification information, or the MAC PDU corresponding to the first resource (or, scheduled) has boundary identification information.

[0255] For example, the statement that the first TB does not correspond to boundary identification information may include / be replaced by: the MAC PDU corresponding to the first TB does not correspond to boundary identification information, or the first TB corresponding to the first resource (or, scheduled) does not correspond to boundary identification information, or the MAC PDU corresponding to the first TB corresponding to the first resource (or, scheduled) does not correspond to boundary identification information.

[0256] The data processing method and communication device provided in this application will be further described below with reference to the accompanying drawings: Please refer to Figure 13, which is a schematic flowchart of a data processing method provided in an embodiment of this application. As shown in Figure 13, the data processing method includes the following:

[0257] In Figure 13, the method execution entity can be a first communication device and a second communication device, or the method execution entity shown in Figure 13 can be a module in the first communication device and a module in the second communication device. Figure 13 is used as an example to illustrate the method execution entity using the first communication device and the first terminal device.

[0258] For example, in the data processing method provided in this application, the transmitting end of TB can be a first communication device, and the receiving end of TB can be a second communication device. Alternatively, the module (e.g., chip, processor, etc.) deployed at the transmitting end of TB can be the first communication device, and the module (e.g., chip, processor, etc.) deployed at the receiving end of TB can be the second communication device.

[0259] For example, the first communication device can be the terminal shown in Figure 1, and correspondingly, the second communication device can be the access network device shown in Figure 1; or the first communication device can be the access network device shown in Figure 1, and correspondingly, the second communication device can be the terminal shown in Figure 1; or the first communication device and the second communication device can be different terminals shown in Figure 1; or the first communication device and the second communication device can be two different other devices shown in Figure 1. This application does not specifically limit the product form of the first communication device and the second communication device.

[0260] Optionally, in S1300 (not shown in Figure 13), the first communication device acquires the first resource or information about the first resource or first control information.

[0261] Optionally, S1300 can be performed before step S1301.

[0262] For example, the first resource is used to carry / transmit the first TB. For example, the first resource is a new transmission resource.

[0263] For example, the first resource may be determined by the first communication device itself, or it may be configured by the second communication device to the first communication device, or it may be configured by the access network device. For example, it may be dynamically scheduled by the access network device through DCI, or it may be scheduled by the access network device through semi-static configuration or configuration authorization, without restriction.

[0264] For example, the first resource can be an uplink resource. For instance, if the first communication device is a terminal and the second communication device is an access network device, the first resource is an uplink resource, and the first communication device receives the first resource or information about the first resource or first control information from the second communication device. Alternatively, for example, the first resource can be a downlink resource. For instance, if the first communication device is an access network device and the second communication device is a terminal, the first resource is a downlink resource, and the first communication device can send the first resource or information about the first resource or first control information to the second communication device.

[0265] For example, the first control information may include / be replaced by: a first DCI. For example, the first control information includes information about a first resource. For example, the first control information is used to schedule the first resource.

[0266] For example, in this application, control information may include / be replaced with: information, or, other.

[0267] For example, the information of the first resource may include / be replaced with at least one of the following: the configuration information of the first resource.

[0268] For example, the first resource can be a dynamic resource, or a configuration resource, or an SPS resource, or a CG resource.

[0269] For example, the first resource is a dynamic resource, and the first instruction information (or the first field) is carried in the first control information.

[0270] For example, the first resource is a configuration resource, an SPS resource, or a CG resource, and the first instruction information (or the first field) is carried in the information of the first resource.

[0271] Optionally, in S1301, the first communication device generates the first TB.

[0272] Optionally, one possible implementation is that the first TB corresponds to boundary identification information.

[0273] Optionally, this application may further include: a first communication device determining, based on first indication information (or a first field) or a first condition, that the first TB corresponds to boundary identification information. Optionally, this step may be performed before S1301, and / or this step may be performed after S1300.

[0274] For example, the content related to "the first communication device determines that the first TB corresponds to boundary identification information" can be referred to in the previous introduction, and will not be repeated here.

[0275] Alternatively, another possible implementation 2 is that the first TB does not correspond to boundary identification information.

[0276] Optionally, this application may further include: a first communication device determining, based on first indication information (or a first field) or a second condition, that the first TB does not correspond to boundary identification information. Optionally, this step may be performed before S1301, and / or this step may be performed after S1300.

[0277] For example, the content related to "the first communication device determines that the first TB does not correspond to boundary identification information" can be referred to in the previous introduction, and will not be repeated here.

[0278] Optionally, this application may further include: a first communication device determining whether a first TB corresponds to boundary identification information based on a first indication information (or a first field) or a first condition (or, the first condition and / or a second condition). Optionally, this step may be performed before S1301, and / or this step may be performed after S1300.

[0279] For example, the content related to "the first communication device determining whether the first TB corresponds to boundary identification information" can be found in the previous introduction and will not be repeated here.

[0280] Optionally, the first TB corresponds to boundary identification information, which may include / be replaced by: the first TB corresponds to N MAC subPDUs and L boundary identification information.

[0281] For example, the first TB corresponds to N MAC subPDUs and L boundary identification information.

[0282] 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.

[0283] Optional, L is less than or equal to N.

[0284] In one possible case 1, L is N or N-1. For example, if N is 7, L is 7 or 6.

[0285] In one possible case 2, L is any value less than N, except for N-1. For example, if N is 7, L can be one of 5, 4, 3, 2, or 1.

[0286] Optionally, for the first resource, the first communication device generates a first TB. For example, for the first resource, the first communication device performs LCP to determine the first TB transmitted on the first resource. For example, in this application, the corresponding term may include / be replaced with: include, or contain, which is uniformly stated here and will not be repeated in subsequent embodiments.

[0287] 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.

[0288] 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.

[0289] For example, Figure 14 illustrates the association between the L boundary identification information and the N MAC subPDUs corresponding to the first TB / MAC PDU. For example, the case where L equals N is shown in (a) or (b) of Figure 14.

[0290] 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.

[0291] For example, Figure 14 illustrates the association between the L boundary identification information and the N MAC subPDUs corresponding to the first TB. For instance, the case where L equals N-1 is shown in (c) or (d) of Figure 14.

[0292] 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.

[0293] For example, Figure 14 shows the association between the L boundary identification information and the N MAC subPDUs corresponding to the first TB. For example, the case where L is less than or equal to N (or, L is any value less than N except N-1) is shown in (e) to (h) of Figure 14.

[0294] It should also be noted that, optionally, the boundary identification information mentioned in this application is used to indicate / identify / determine the boundary of a MAC subPDU or the boundary of one or more associated MAC subPDUs, or for a second communication device to determine the boundary of a MAC subPDU. Optionally, the boundary identification information mentioned in this application may also be called demarcation information, boundary information, or identification information, etc., and this application does not limit its name.

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

[0296] It is understood that the boundary identification information mentioned in this application 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 what to use as the boundary identification information), or it may be configured by the network device (e.g., the network device configures the second communication device, or the network device configures the first communication device), or it may be specified by the communication protocol, or it may be predefined. This application does not specifically limit it.

[0297] To facilitate understanding of the boundary identification information mentioned in this application, the following explanation will use the first boundary identification information as an example to illustrate the content and location of the boundary identification information mentioned in this application.

[0298] For example, the first boundary identification information is one of L boundary identification information.

[0299] The following is a description of the content included in the boundary marking information mentioned in this application.

[0300] Optionally, the first boundary identification information may include / be replaced with: information of the first boundary identifier and / or first verification information.

[0301] It is understood that the boundary identifier (e.g., the first boundary identifier) ​​mentioned in this application may be negotiated / agreed upon by the first communication device and the second communication device (e.g., indicated by the first communication device to the second communication device, or indicated by the second communication device to the first communication device, or agreed upon by the first communication device and the second communication device as the boundary identifier), or may be configured by the network device (e.g., configured by the network device to the second communication device, or configured by the network device to the first communication device), or may be specified by the communication protocol, or may be predefined. This application does not specifically limit the boundary identifier.

[0302] It should be noted that the verification information mentioned in this application (e.g., the first verification information) can be CRC or other verification information, without limitation. For example, the length / algorithm of the verification information can be negotiated / agreed upon by the first and second communication devices (e.g., the first communication device instructs the second communication device, or the second communication device instructs the first communication device, or the first and second communication devices agree on the length / algorithm of the verification information), or it can be configured by the network device (e.g., the network device configures the second communication device, or the network device configures the first communication device), or it can be specified by the communication protocol, or it can be predefined; this application itself does not impose specific limitations. It should also be noted that this application does not limit the method of generating the verification information. It should be noted that the specific content of the verification information can be found in the relevant description below. Optionally, the generation process of the verification information mentioned in this application and the boundary identification information are associated with the position of the associated MAC subPDU.

[0303] It should be noted that the verification information mentioned in this application (e.g., the first verification information) may be CRC or security-related verification information or other verification information, without limitation.

[0304] For example, security-related verification information may include / be replaced with / be called: verification information for security.

[0305] For example, security-related verification information can be included or replaced with integrity protection-related verification information.

[0306] For example, integrity protection-related verification information may include / be replaced with / referred to as: verification information for integrity protection, or, verification information related to integrity protection verification, or, verification information for integrity protection verification, or, verification information related to integrity verification, or, verification information for integrity verification.

[0307] For example, integrity protection-related verification information may include / be replaced with: Message Authentication Code for Integrity (MAC-I), or Message Authentication Code for Integrity (MAC-I).

[0308] For example, authentication can include / be replaced by: verification, or, identification, or, authorization.

[0309] For example, in this application, "related" may include / be replaced with: of.

[0310] For example, in this application, "verification" may include / be replaced with: verification.

[0311] For example, in this application, length may include / be replaced by at least one of the following: size, bit length, byte length, number of bits, or number of bytes.

[0312] For example, the first boundary identification information may include any of the following possible implementations:

[0313] To achieve ①, the first boundary identification information can include / be replaced with: the information of the first boundary identifier.

[0314] For example, a first boundary identifier is 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 a second communication device to determine the boundary of a MAC subPDU.

[0315] 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.

[0316] For example, a first boundary identifier is used to determine the boundary of a MAC subPDU. For example, a second communication device can determine the boundary of a MAC subPDU based on the first boundary identifier. For example, Figure 15 shows a schematic diagram of a MAC subheader containing boundary identification information. For example, as shown in Figure 15(a), the boundary identification information includes a field for indicating the boundary identifier.

[0317] ② The first boundary identification information can be included or replaced with: the first verification information.

[0318] For example, the first verification information is used to indicate / identify / determine the boundary of a MAC subPDU or the boundary of one or more associated MAC subPDUs, or for a second communication device to determine the boundary of a MAC subPDU. For example, the first verification information is used for security, or for the security of a MAC subPDU, or for the security of one or more associated MAC subPDUs, or for verifying / determining security, or for verifying / determining the security of a MAC subPDU, or for verifying / determining the security of one or more associated MAC subPDUs. For example, a MAC subPDU may include / be replaced by: a MAC subPDU other than at least one of the first boundary identification information (or, boundary identification information) or the first verification information (or, verification information) or the MAC subheader. For example, a MAC subPDU may include / be replaced by: one or more MAC subPDUs associated with the first verification information other than at least one of the first boundary identification information (or, boundary identification information) or the first verification information (or, verification information) or the MAC subheader. For example, a MAC subPDU may include / be replaced by: a MAC SDU or a MAC CE. For example, security can include / be replaced by: integrity protection, or integrity protection verification, or integrity verification. For example, a second communication device can determine the security of the MAC subPDU based on the first verification information.

[0319] For example, the first verification information is used to determine the boundaries of the MAC subPDU. For example, the second communication device can determine the boundaries of the MAC subPDU based on the first verification information. For example, Figure 15 shows a schematic diagram of a MAC subheader containing boundary identification information. As shown in Figure 15(b), the boundary identification information includes a field for indicating verification information.

[0320] For example, the first boundary identification information includes first verification information, which can determine (or simultaneously determine, or together determine) the security of the MAC subPDU and the boundary of the MAC subPDU. Optionally, the length / overhead of the boundary identification information (or verification information) can be reduced.

[0321] Implementation ③, for example, the first boundary identification information may include / be replaced with: the information of the first boundary identifier and the first verification information.

[0322] For example, the first boundary identifier and the first verification information are 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 a second communication device to determine the boundary of a MAC subPDU. For example, the first boundary identifier is 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 a second communication device to determine the boundary of a MAC subPDU. For example, the first verification information is used for security, or, for the security of a MAC subPDU, or, for the security of one or more MAC subPDUs associated with it, or, for verifying / determining security, or, for verifying / determining the security of a MAC subPDU, or, for verifying / determining the security of one or more MAC subPDUs associated with it. For example, a MAC subPDU may include / be replaced with: a MAC subPDU other than at least one of the first boundary identifier information (or, boundary identifier information) or the first verification information (or, verification information) or the MAC subheader. For example, a MAC subPDU may include / be replaced by: one or more MAC subPDUs associated with first verification information other than at least one of the first boundary identification information (or boundary identification information) or first verification information (or verification information) or MAC subheading. For example, a MAC subPDU may include / be replaced by: MAC SDU or MAC CE. For example, security may include / be replaced by: integrity protection, or integrity protection verification, or integrity verification. For example, a second communication device may determine the security of a MAC subPDU based on the first verification information.

[0323] For example, a first boundary identifier and first verification information are used to determine the boundary of a MAC subPDU. For example, a second communication device can determine the boundary of a MAC subPDU based on the first boundary identifier and the first verification information.

[0324] For example, Figure 15 shows a schematic diagram of a MAC subheader containing boundary identification information. As shown in Figure 15(c), the boundary identification information includes a field for indicating a boundary identifier and a field for indicating verification information.

[0325] 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 15(a), the field used to indicate the boundary identifier is 5 bytes long; in the MAC subheader containing boundary identification information shown in Figure 15(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 15(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.

[0326] For example, the first boundary identification information includes information about the first boundary identifier and first verification information, which can balance the retrieval volume of the boundary identifier and the verification volume of the verification information. Optionally, the length / overhead of the boundary identification information (or boundary identifier) ​​can be reduced.

[0327] For example, the first boundary identification information includes first verification information, which can determine (or simultaneously determine, or together determine) the security of the MAC subPDU and the boundary of the MAC subPDU, or a verification information can be used (or simultaneously use, or together use) for the security of the MAC subPDU and the boundary of the MAC subPDU. Optionally, the length / overhead of the boundary identification information (or verification information) can be reduced. For example, the MAC subPDU can include / be replaced by: MAC subPDUs other than at least one of the first boundary identification information (or boundary identification information) or the first verification information (or verification information) or the MAC subheader. For example, the MAC subPDU can include / be replaced by: one or more MAC subPDUs associated with first verification information other than the first boundary identification information (or boundary identification information) or the first verification information (or verification information) or the MAC subheader. For example, the MAC subPDU can include / be replaced by: MAC SDU or MAC CE.

[0328] Optionally, the first boundary identification information may also include first length information.

[0329] For example, the first length information is used to indicate the length of one or more MAC subPDUs associated with the first boundary identification information, or the length associated with the first boundary identification information (or, the information of the first boundary identifier and / or the first check information), or the length of multiple MAC subPDUs before the next boundary identification information, or the length / interval to the next boundary identification information.

[0330] For example, the length of MAC subPDU#1 corresponding to TB is L1, the length of MAC subPDU#2 is L2, and the length of MAC subPDU#3 is L3. If boundary identifier information #1 is associated with MAC subPDU#1, then the length information of boundary identifier information #1 indicates the length of MAC subPDU#1, i.e., L1. If boundary identifier information #1 is associated with MAC subPDU#1 to MAC subPDU#3, then the length information of boundary identifier information #1 indicates the total length of MAC subPDU#1 to MAC subPDU#3, i.e., L1+L2+L3.

[0331] For example, Figure 16 shows a schematic diagram of a MAC subheader including boundary identification information. As shown in Figure 16(a), the boundary identification information includes a field for indicating a boundary identifier and a field for indicating length information; as shown in Figure 16(b), the boundary identification information includes a field for indicating checksum information and a field for indicating length information; as shown in Figure 16(c), the boundary identification information includes a field for indicating a boundary identifier, a field for indicating checksum information, and a field for indicating length information.

[0332] It should be noted that this application does not specifically limit the length of the field used to indicate length information. For example, the length of the field used to indicate length included in the MAC subheader containing length information shown in Figure 16 is 2 bytes.

[0333] For example, the first length information allows the second communication device to determine the location of the boundary marker information without performing boundary marker information retrieval. For example, if all CBs corresponding to the first TB are successfully received, the first length information allows the second communication device to determine the location of the boundary marker information without performing boundary marker information retrieval. For example, the first length information reduces the workload of the second communication device in retrieving boundary marker information.

[0334] The location of the boundary marking information mentioned in this application will be described below.

[0335] In one possible positional relationship 1, the first boundary identification information is contained in the first MAC subheader.

[0336] For example, the first MAC subheader is the MAC subheader of one of the N MAC subPDUs corresponding to the first TB.

[0337] For example, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information. For example, the first MAC subheader is the MAC subheader of one (or one) of the one or more MAC subPDUs associated with the first boundary identification information.

[0338] For example, the first MAC subheader is the MAC subheader of the first MAC subPDU among one or more MAC subPDUs associated with the first boundary identification information. For example, as shown in (a) or (c) of Figure 14, if a boundary identification information is associated with one MAC subPDU, then the boundary identification information is located in the MAC subheader of the MAC subPDU. For example, as shown in (e) or (g) of Figure 14, if a boundary identification information is associated with multiple MAC subPDUs, then the boundary identification information is located in the MAC subheader of the first MAC subPDU among the multiple MAC subPDUs.

[0339] Optionally, in possible positional relationship 1, the first MAC subheader includes first boundary identification information, and in the first MAC subheader, the field used to indicate the first boundary identification information is located before other fields (e.g., the R / F / LCID / (eLCID) / L fields) other than the boundary identification information.

[0340] Optionally, when the boundary identification information includes verification information, this application also provides several methods for generating the verification information, taking into account the possible positional relationship 1. For example, taking the first verification information in the first boundary identification information as an example, in the possible positional relationship 1, the first verification information can be generated by any of the following methods:

[0341] Generation Method 1: The first verification information is generated based on one or more fields (e.g., R / F / LCID / (eLCID) / L fields) in the first MAC subheader, excluding the first boundary identification information. For example, in Figure 15(b) or (c), the verification information is generated based on the R field, F field, LCID field, and L field. It should be understood that, for the second communication device, the first verification information is used to verify one or more fields in the first MAC subheader, excluding the first boundary identification information.

[0342] Generation Method 2: The first verification information is generated based on M1 bytes / bits after / before the first boundary identification information. For example, M1 is a positive integer. For instance, in Figure 15(b) or (c), the verification information is generated based on M1 bytes / bits after / before the first boundary identification information. It should be understood that, for the second communication device, the first verification information is used to verify the M1 bytes / bits after / before the first boundary identification information. It should be noted that the specific value of M1 can be specified by the protocol, predefined, or negotiated between the first and second communication devices; this application does not impose any restrictions. For example, M1 can be 1 or 2.

[0343] Generation Method 3: The first verification information is generated based on the first length information. For example, in Figure 16(b) or (c), the verification information is generated based on the length information. It should be understood that, for the second communication device, the first verification information is used to verify the first length information.

[0344] Generation Method 4: The first verification information is generated based on the first boundary identification information other than the first verification information itself. It should be understood that, for the second communication device, the first verification information is used to verify the first boundary identification information other than the first verification information itself.

[0345] In one possible positional relationship 2, the first boundary identification information is located before the first MAC subheader or the first MAC subPDU, and / or, the first boundary identification information is located after the second MAC subPDU. Optionally, the first boundary identification information is not included in any of the N MAC subPDUs or any of the MAC subheaders.

[0346] For example, the first MAC subheader is the MAC subheader of one of the N MAC subPDUs corresponding to the first TB. For example, the first MAC subheader is the MAC subheader of the first MAC subPDU. For example, the first MAC subPDU and the second MAC subPDU are two adjacent MAC subPDUs among the N MAC subPDUs. For example, the second MAC subPDU precedes the first MAC subPDU. Or, the second MAC subPDU is positioned before the first MAC subPDU in the bitstream. For example, the bitstream corresponding to the second MAC subPDU precedes the bitstream corresponding to the first MAC subPDU. For example, the bits corresponding to the second MAC subPDU are bits a to a+b-1, and the bits corresponding to the first MAC subPDU are bits a+b to a+2×b-1. For example, the second MAC subPDU corresponds to the high-order bits, and the first MAC subPDU corresponds to the low-order bits; or vice versa.

[0347] Optionally, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information. For example, the first MAC subheader is the MAC subheader of one (or one, or the first) MAC subPDU among one or more MAC subPDUs associated with the first boundary identification information. For example, the first MAC subPDU is one (or one, or the first) MAC subPDU associated with the first boundary identification information.

[0348] For example, the first MAC subheader is the MAC subheader of the first MAC subPDU among one or more MAC subPDUs associated with the first boundary identification information. For example, the first MAC subPDU is the first MAC subPDU among one or more MAC subPDUs associated with the first boundary identification information.

[0349] For example, as shown in Figure 14(b) or (d), if a boundary identification information is associated with a MAC subPDU, then the boundary identification information is located before the MAC subheader of the MAC subPDU. For example, as shown in Figure 14(f) or (h), if a boundary identification information is associated with one or more MAC subPDUs, then the boundary identification information is located before the first MAC subPDU among the multiple MAC subPDUs, or the boundary identification information is located before the MAC subheader of the first MAC subPDU among the multiple MAC subPDUs.

[0350] Optionally, the first MAC subheader is the MAC subheader of the MAC subPDU following the last MAC subPDU associated with the first boundary identification information. For example, the first MAC subPDU is the MAC subPDU following the last MAC subPDU associated with the first boundary identification information. For example, if boundary identification information #1 is associated with MAC subPDU #1, then boundary identification information #1 is located after MAC subPDU #1 and before the MAC subheader of the MAC subPDU following MAC subPDU #2 (i.e., MAC subPDU #2). For example, if boundary identification information #1 is associated with MAC subPDU #1 to MAC subPDU #3, then boundary identification information #1 is located after MAC subPDU #3 and before the MAC subheader of the MAC subPDU following MAC subPDU #4 (i.e., MAC subPDU #4).

[0351] For example, the second MAC subPDU is a MAC subPDU preceding the first MAC subPDU associated with the first boundary identification information. For instance, if boundary identification information #2 is associated with MAC subPDU #2, then boundary identification information #2 is located after the MAC subPDU preceding MAC subPDU #2 (i.e., MAC subPDU #1). If boundary identification information #2 is associated with MAC subPDU #4, then boundary identification information #2 is located after the MAC subPDU preceding MAC subPDU #4 (i.e., MAC subPDU #3).

[0352] When the boundary identification information includes verification information, this application also provides several methods for generating the verification information, taking into account the possible positional relationship 2. For example, taking the first verification information in the first boundary identification information as an example, in the possible positional relationship 2, the first verification information can be generated by any of the following methods:

[0353] Generation Method 5: The first verification information is generated based on the first MAC sub-header (or one or more or all fields in the first MAC sub-header). For example, if the first MAC sub-header includes an R field, an F field, an LCID field, and an L field, then the first verification information is generated based on one or more fields of the R field, F field, LCID field, or L field in the first MAC sub-header. It should be understood that, for the second communication device, the first verification information is used to verify the first MAC sub-header (or one or more or all fields in the first MAC sub-header).

[0354] Generation method 6: The first verification information is generated based on M1 bytes / bits after / before the first boundary identification information. For example, M1 is a positive integer. It should be understood that, for the second communication device, the first verification information is used to verify the M1 bytes / bits after / before the first boundary identification information.

[0355] Generation method 7: The first verification information is generated based on the first length information. It should be understood that, for the second communication device, the first verification information is used to verify the first length information.

[0356] Generation method 8: The first verification information is generated based on the first boundary identification information other than the first verification information itself. It should be understood that, for the second communication device, the first verification information is used to verify the first boundary identification information other than the first verification information itself.

[0357] Generation Method 9: The first verification information is generated based on a MAC subPDU or one or more associated MAC subPDUs. It should be understood that, for the second communication device, the first verification information is used to verify a MAC subPDU or one or more associated MAC subPDUs. For example, a MAC subPDU may include / be replaced by: a MAC subPDU other than at least one of the following: first boundary identification information (or, boundary identification information), first verification information (or, verification information), or a MAC subheader. For example, a MAC subPDU may include / be replaced by: one or more MAC subPDUs associated with first verification information other than at least one of the following: first boundary identification information (or, boundary identification information), first verification information (or, verification information), or a MAC subheader. For example, a MAC subPDU may include / be replaced by: a MAC SDU or a MAC CE.

[0358] It should be noted that this application does not limit the generation method and / or verification method of the first verification information. For example, regarding the aforementioned "for the second communication device, the first verification information is used to verify XXX," one possible implementation is: the second communication device generates second verification information based on XXX, and determines whether the verification passes (or, the verification passes or fails) by comparing the second verification information with the first verification information. For example, if the second verification information is the same as the first verification information, the verification passes. And / or, for example, if the second verification information is different from the first verification information, the verification fails.

[0359] Optionally, the first TB can correspond to Q existence information.

[0360] For example, Q is an integer. For example, Q is greater than or equal to 1.

[0361] Optionally, Q is less than or equal to N. For example, Q is N or N-1. For instance, if N is 7, Q is 7 or 6.

[0362] Optionally, Q existence information items are associated with one or more (or M) MAC subPDUs out of N MAC subPDUs. Optionally, one existence information item (or each existence information item, or one of the Q existence information items, or each of the Q existence information items) is associated with one or more (or N3) MAC subPDUs out of N MAC subPDUs. Optionally, N3 is less than or equal to N.

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

[0364] For example, one MAC subPDU (or one / each MAC subPDU other than the first MAC subPDU) corresponds to one presence information, or one presence information is associated with one MAC subPDU. For instance, in case 1 above when L equals N-1, one MAC subPDU (or one / each MAC subPDU other than the first MAC subPDU) corresponds to one presence information, or one presence information is associated with one MAC subPDU.

[0365] The following explanation, using the first existence information as an example, clarifies the content and location of the existence information mentioned in this application.

[0366] For example, the first existence information is one of the Q existence information.

[0367] The following is a description of the existence information mentioned in this application.

[0368] For example, the first existence information is used to indicate whether the first boundary identification information (or, boundary identification information, or, information of the first boundary identifier, first verification information, first length information, or, boundary identification information other than the first existence information) exists.

[0369] For example, "exists" can be replaced with "exists" or "does not exist".

[0370] For example, existence can include / replace with: send, or, transmit, or, be sent, or, be transmitted.

[0371] The location of the existence information mentioned in this application will be described below.

[0372] In one possible positional relationship 1, the first existence information is contained in the first MAC subheader.

[0373] In one possible positional relationship 2, the first presence information is located before the first MAC subheader or the first MAC subPDU, and / or, the first presence information is located after the second MAC subPDU. It is understood that, optionally, the first presence information is not included in any of the N MAC subPDUs or any of the MAC subheaders.

[0374] For example, the content related to the location of the first existence information can be referred to the content related to the location of the first boundary identification information, which will not be repeated here. For example, the first existence information can be replaced with the first boundary identification information for understanding.

[0375] For example, the first MAC subheader includes first presence information. Optionally, the first MAC subheader is the MAC subheader of one of N MAC subPDUs (or, one of the MAC subPDUs other than the first MAC subPDU).

[0376] For example, the first presence information is used to indicate whether there is first boundary identification information (or, boundary identification information, or, information of the first boundary identifier, first check information, first length information, or, boundary identification information other than the first presence information) in the first MAC subheader.

[0377] For example, Figure 17 shows a schematic diagram of a MAC subheader including a D field for indicating presence information. For example, the D field may be included in the MAC subheader. For example, presence information is the first field in the MAC subheader. For example, as shown in Figure 17(a), when there is no boundary identification information in the MAC subheader, the MAC subheader includes a D field for indicating the absence of boundary identification information, and the D field precedes the F / LCID / L fields. As shown in Figure 17(b), when there is boundary identification information in the MAC subheader, and the boundary identification information includes a field for indicating a boundary identifier, the MAC subheader includes a D field for indicating the presence of boundary identification information, and the D field precedes the field for indicating a boundary identifier. As shown in Figure 17(c), when there is boundary identification information in the MAC subheader, and the boundary identification information includes a field for indicating a boundary identifier and a field for indicating check information, the MAC subheader includes a D field for indicating the presence of boundary identification information, and the D field precedes the field for indicating a boundary identifier. As shown in Figure 17(d), if there is boundary identification information before the MAC subheader and the boundary identification information includes a field for indicating verification information, the MAC subheader includes a D field for indicating the presence of boundary identification information, and the D field precedes the field for indicating verification information.

[0378] For example, the first presence information enables the second communication device to determine the location of the boundary identification information (or, determine whether the boundary identification information exists, or, determine the data format (or, bit meaning) corresponding to the first TB) without performing a boundary identification information retrieval. For example, if all CBs corresponding to the first TB are successfully received, the first presence information enables the second communication device to determine the location of the boundary identification information (or, determine whether the boundary identification information exists, or, determine the data format (or, bit meaning) corresponding to the first TB) without performing a boundary identification information retrieval.

[0379] Optionally, the first boundary identification information may also include one or more reserved bits.

[0380] Optionally, the first boundary identification information can be byte-aligned, or the length of the first boundary identification information can be an integer number of bytes. For example, as shown in Figures 15 and 16.

[0381] Optionally, the total length of the first boundary identification information and the first existence information can be byte-aligned, or the total length of the first boundary identification information and the first existence information can be an integer number of bytes. For example, as shown in (b) to (d) of Figure 17.

[0382] Optionally, the D field used to indicate the first presence information precedes the field used to indicate the boundary identifier and / or the field used to indicate the verification information. For example, as shown in Figures 17(b) to (d).

[0383] Optionally, the first presence information may also include one or more reserved bits. Optionally, the first presence information may be byte-aligned, or the length of the first presence information may be an integer number of bytes.

[0384] Optionally, if the first existence information indicates the existence of first boundary identification information (or, boundary identification information, or, at least one of the information of the first boundary identifier, first check information, and first length information, or, boundary identification information other than the first existence information), the total length of the first boundary identification information and the first existence information may be byte-aligned, or the total length of the first boundary identification information and the first existence information may be an integer number of bytes. For example, as shown in Figures 17(b) to (d).

[0385] Optionally, the first existence information may also be included in the boundary identification information (e.g., first boundary identification information). For example, the first boundary identification information includes the first existence information. Optionally, when the first boundary identification information may include the first existence information, if the first existence information indicates that the first boundary identification information (or, the boundary identification information, or, at least one of the information of the first boundary identifier, the first check information, and the first length information, or, the boundary identification information other than the first existence information) does not exist, the first boundary identification information may not be byte-aligned, or the length of the first boundary identification information may not be an integer number of bytes. For example, as shown in Figure 17(a).

[0386] Optionally, the first TB can correspond to L1 paddings.

[0387] For example, L1 is an integer. For example, L1 is greater than or equal to 0.

[0388] Optional, L1 is less than or equal to L. Optional, L1 is less than or equal to N.

[0389] For example, to reduce the workload of retrieval / verification at the receiving end, the size of one or more MAC subPDUs associated with a boundary identifier (or a boundary identifier other than the last boundary identifier) ​​can be an integer multiple of X bytes, or the interval / length between two boundary identifiers (or the length before the first boundary identifier) ​​can be an integer multiple of X bytes. In one possible implementation, the first communication device generates the first TB by adding padding to the first TB.

[0390] For example, the size (or number of bytes) of a padding is greater than or equal to 0 and less than or equal to X-1. For example, the size (or number of bytes) of a padding is greater than or equal to 1 and less than or equal to X-1.

[0391] Optionally, X is the size of the boundary identification information (or, the first boundary identification information), or the number of bytes of the boundary identification information (or, the first boundary identification information), or the number of bytes corresponding to the boundary identification information (or, the first boundary identification information), or the total size of the boundary identification information and the existence information (or, the first boundary identification information and the first existence information), or the total number of bytes of the boundary identification information and the existence information (or, the first boundary identification information and the first existence information), or the total number of bytes corresponding to the boundary identification information and the existence information (or, the first boundary identification information and the first existence information).

[0392] For example, Figure 18 illustrates the association between L boundary identifiers and N MAC subPDUs corresponding to the first TB. As shown in Figure 18(a), when one boundary identifier corresponds to one MAC subPDU, 0 to (X-1) bytes of padding are added after each MAC subPDU (or, any MAC subPDU except the last one), ensuring that the sum of the size of the MAC subPDU and the padding size is an integer multiple of the size of the boundary identifier. As shown in Figure 18(b), when one boundary identifier corresponds to multiple MAC subPDUs, 0 to (X-1) bytes of padding are added after each boundary identifier (or, any boundary identifier except the last one), ensuring that the sum of the size of the multiple MAC subPDUs and the padding size is an integer multiple of the size of the boundary identifier. For example, 0 to (X-1) bytes of padding are added before each boundary identifier (or, any boundary identifier except the first one). For example, the sum of the size of the multiple MAC subPDUs associated with the boundary identification information and the size of the padding is an integer multiple of the size of the boundary identification information.

[0393] For example, if the size of a MAC subPDU (or any MAC subPDU except the last one) is not an integer multiple of X, padding with 1 to (X-1) bytes (e.g., padding with 1 to (X-1) bytes after the MAC subPDU) is added so that the sum of the size of the MAC subPDU and the padding is an integer multiple of X.

[0394] For example, if the size of one or more MAC subPDUs associated with a boundary identifier (or a boundary identifier other than the last boundary identifier) ​​is not an integer multiple of X, or if the interval / length between two boundary identifiers (or the length before the first boundary identifier) ​​is not an integer multiple of X, or if the size of multiple MAC subPDUs (or multiple MAC subPDUs other than the last multiple MAC subPDUs) is not an integer multiple of X, padding of 1 to (X-1) bytes is added (e.g., padding / adding 1 to (X-1) bytes after the one or more MAC subPDUs) so that the sum of the size of the one or more MAC subPDUs and the size of the padding is an integer multiple of X.

[0395] For example, by adding 1 to (X-1) bytes of padding, the workload of the receiving end in retrieving / verifying boundary identification information can be reduced, which helps to reduce computational load and power consumption. For example, the second communication device can change from retrieving / verifying boundary identification information per byte to retrieving / verifying boundary identification information per X bytes.

[0396] For example, the first TB in S1301 may include / be replaced by: the first MAC PDU.

[0397] For example, by implementing both Implementation 1 and Implementation 2 flexibly, the communication device can determine the appropriate implementation based on the specific service scenario / communication, which is beneficial for balancing service latency requirements and air interface resource overhead. For example, for high-speed scenarios (or, large data volume service scenarios), the TB size is large, and it contains a large number of CBs. The problem proposed in this application is more serious (e.g., one CB error jams many CBs). Implementation 2 can be adopted, which can reduce service latency and power consumption. For example, for low-speed scenarios (or, small data volume service scenarios), the TB size is small, and it contains a small number of CBs. The problem proposed in this application is not very serious (e.g., one CB error jams many CBs). If Implementation 1 (i.e., adding boundary identification information) is used, the resource overhead is large. Considering these factors, Implementation 2 can be adopted.

[0398] S1302, the first communication device sends a first TB to the second communication device. Correspondingly, the second communication device receives the first TB from the first communication device.

[0399] As one possible implementation, the first communication device transmits the first TB on the first resource. For example, the second communication device receives the first TB on the first resource.

[0400] As one possible implementation, after the MAC layer of the first communication device generates the first MAC PDU, it can submit the first MAC PDU (or first TB) to the PHY layer of the first communication device. The first MAC PDU becomes the first TB after being submitted to the PHY layer. The PHY layer of the first communication device can perform relevant processing on the first TB and then send it.

[0401] For example, the processing performed by the PHY layer on the first TB may include at least one of the following: adding TB CRC, dividing it into multiple CBs, adding CB CRC, etc. Of course, other processing may also be performed, which are not specifically limited in this application.

[0402] For example, the first TB corresponds to C CBs. For example, C is a positive integer.

[0403] For example, the second communication device receiving the first TB may include / be replaced by: the second communication device receiving some or all of the C CBs, or the second communication device receiving the first CB, or the second communication device receiving the second CB.

[0404] For example, a second communication device receives a first TB. Reception of the first TB may be successful or unsuccessful; that is, the second communication device may not necessarily successfully receive the first TB (or each CB corresponding to the first TB). For example, successful reception of the first TB may include: the CRC checksum of all CBs corresponding to the first TB passes. For example, unsuccessful reception of the first TB may include: the CRC checksum of at least one CB (or all CBs) corresponding to the first TB fails.

[0405] For example, "pass" can be included / replaced with: "correct". For example, "fail" can be included / replaced with: "error".

[0406] For example, success can be replaced with: Correct. For example, failure can be replaced with: Error.

[0407] For example, the second communication device receiving the first TB can include / be replaced by: the second communication device successfully receiving the first TB, or the second communication device failing to successfully receive the first TB.

[0408] For example, if the second communication device successfully receives the first TB, it can include / be replaced with: the second communication device successfully receives all CBs corresponding to the first TB.

[0409] For example, if the second communication device fails to receive the first TB, it may include / be replaced by: the second communication device only successfully receiving a portion of the CBs corresponding to the first TB, or the second communication device fails to successfully receive at least one CB corresponding to the first TB, or the second communication device fails to successfully receive all CBs corresponding to the first TB.

[0410] For example, a second communication device receives a first CB. The reception of the first CB may be successful or it may fail; that is, the second communication device may not necessarily successfully receive the first CB. For example, successful reception of the first CB may include: the CRC check of the first CB passing. For example, failed reception of the first CB may include: the CRC check of the first CB failing.

[0411] For example, the second communication device receiving the first CB may include / be replaced by: the second communication device successfully receiving the first CB, or the second communication device failing to successfully receive the first CB.

[0412] For example, the content related to "the second communication device receiving the second CB" can be referenced to the content related to "the second communication device receiving the first CB". For example, the first CB can be replaced with the second CB for understanding, which will not be elaborated here.

[0413] Optionally, before step S1302, this embodiment of the application may further include: the second communication device can determine the C CBs corresponding to the first TB.

[0414] For example, the implementation of the second communication device determining the C CBs corresponding to the first TB can be referred to the description of the physical layer data processing flow in the brief introduction of the aforementioned related technologies.

[0415] For example, referring to the description of the physical layer data processing flow in the aforementioned brief introduction to related technologies, the PHY layer of the first communication device divides the first TB into C CBs and sends C CBs to the second communication device. The second communication device receives the C CBs from the first communication device.

[0416] Optionally, in this application, a complete MAC subPDU can correspond to one CB, that is, parsing the CB can obtain the MAC subheader and MAC SDU / CE / padding of the MAC subPDU. Alternatively, a complete MAC subPDU can correspond to multiple CBs, that is, parsing the CB can obtain the MAC subheader and / or a portion of the MAC SDU / CE / padding of the MAC subPDU.

[0417] For example, as shown in Figure 19(a), MAC subPDU#1 corresponds to CB1, that is, CB1 corresponds to the complete MAC subPDU#1; MAC subPDU#2 shown in Figure 19(a) corresponds to CB1 and CB2, CB1 corresponds to the MAC subheader and part of the MAC SDU / CE / padding of MAC subPDU#2, and CB2 corresponds to part of the MAC SDU / CE / padding of MAC subPDU#2.

[0418] For example, the first TB corresponds to N2 CB groups. For example, N2 is a positive integer.

[0419] For example, the second communication device receiving the first TB may include / be replaced by: the second communication device receiving some or all of the CB groups in N2 CB groups, or the second communication device receiving the first CB group, or the second communication device receiving the second CB group.

[0420] For example, the second communication device receives the first TB. The reception of the first TB may be successful or unsuccessful; that is, the second communication device may not necessarily successfully receive the first TB (or each CB corresponding to the first TB, or each group of CBs corresponding to the first TB). For example, successful reception of the first TB may include: the CRC checksum of all CBs corresponding to the first TB passes. For example, unsuccessful reception of the first TB may include: the CRC checksum of at least one CB (or all CBs) corresponding to the first TB fails.

[0421] For example, the second communication device receiving the first TB can include / be replaced by: the second communication device successfully receiving the first TB, or the second communication device failing to successfully receive the first TB.

[0422] For example, if the second communication device successfully receives the first TB, it may include / be replaced by: the second communication device successfully receives all CBs corresponding to the first TB, or the second communication device successfully receives all CB groups corresponding to the first TB.

[0423] For example, if the second communication device fails to receive the first TB, it may include / be replaced by: the second communication device only successfully receiving a portion of the CBs corresponding to the first TB, or the second communication device fails to successfully receive at least one CB corresponding to the first TB, or the second communication device fails to successfully receive all the CBs corresponding to the first TB, or the second communication device only successfully receiving a portion of the CB groups corresponding to the first TB, or the second communication device fails to successfully receive at least one CB group corresponding to the first TB, or the second communication device fails to successfully receive all the CB groups corresponding to the first TB.

[0424] For example, a second communication device receives a first CB group. Reception of the first CB group may be successful or unsuccessful; that is, the second communication device may not necessarily successfully receive the first CB group (or each CB in the first CB group). For example, successful reception of the first CB group may include: all CBs in the first CB group passing CRC checks. For example, failed reception of the first CB group may include: at least one CB (or all CBs) in the first CB group failing CRC checks.

[0425] For example, the second communication device receiving the first CB group may include / be replaced by: the second communication device successfully receiving the first CB group, or the second communication device failing to successfully receive the first CB group.

[0426] For example, if the second communication device successfully receives the first CB group, it can include / be replaced with: the second communication device successfully receives all CBs in the first CB group.

[0427] For example, if the second communication device fails to receive the first CB group, it may include / be replaced by: the second communication device successfully receiving only some of the CBs in the first CB group, or the second communication device fails to receive at least one CB in the first CB group, or the second communication device fails to receive all the CBs in the first CB group.

[0428] For example, the content related to "the second communication device receiving the second CB group" can be referenced to the content related to "the second communication device receiving the first CB group". For example, the first CB group can be replaced with the second CB group for understanding, which will not be elaborated here.

[0429] For example, the second communication device receiving some or all of the N2 CB groups may include / be replaced by: the second communication device receiving some or all of the CB groups in the N2 CB groups.

[0430] Optionally, the embodiments of this application may further include: S1304 (not shown in FIG13), the second communication device acquires the first resource or information of the first resource or first control information.

[0431] Optionally, S1304 can be executed before at least one of steps S1301 and S1302. Optionally, S1304 can also be executed at any position between S1301 and S1302, which is not limited in this embodiment.

[0432] For example, the first resource may be determined by the second communication device itself, or it may be configured by the first communication device to the second communication device, or it may be configured by the access network device. For example, it may be dynamically scheduled by the access network device through DCI, or it may be scheduled by the access network device through semi-static configuration or configuration authorization, without restriction.

[0433] For example, the first resource can be an uplink resource. For instance, if the first communication device is a terminal and the second communication device is an access network device, the first resource is an uplink resource, and the second communication device determines the first resource. Alternatively, for example, the first resource can be a downlink resource. For instance, if the first communication device is an access network device and the second communication device is a terminal, the first resource is a downlink resource, and the first communication device can send the first resource, its information, or control information to the second communication device.

[0434] Optionally, in S1303, the second communication device processes the first TB based on the first boundary identification information.

[0435] Optionally, this application may further include: a second communication device determining, based on first indication information (or a first field) or a first condition, that the first TB corresponds to boundary identification information. Optionally, this step may be performed before S1303, and / or, this step may be performed after S1304.

[0436] For example, the content related to "the second communication device determines that the first TB corresponds to boundary identification information" can be referred to in the previous introduction, and will not be repeated here.

[0437] Optionally, this application may further include: a second communication device determining, based on first indication information (or a first field) or a second condition, that the first TB does not correspond to boundary identification information. Optionally, this step may be performed before S1303, and / or, this step may be performed after S1304.

[0438] For example, the content related to "the second communication device determines that the first TB does not have corresponding boundary identification information" can be referred to in the previous introduction, and will not be repeated here.

[0439] Optionally, this application may further include: a second communication device determining whether the first TB corresponds to boundary identification information based on the first indication information (or the first field) or the first condition (or, the first condition and / or the second condition). Optionally, this step may be performed before S1303, and / or this step may be performed after S1304.

[0440] For example, the content related to "the second communication device determining whether the first TB corresponds to boundary identification information" can be found in the previous introduction and will not be repeated here.

[0441] For example, S1303 may include / be replaced by: the second communication device determining that the first TB corresponds to boundary identification information; or, the second communication device determining whether the first TB corresponds to boundary identification information; or, if the first TB corresponds to boundary identification information, the second communication device processes the first TB based on the first boundary identification information; or, if the first TB does not correspond to boundary identification information, the second communication device processes the first TB as if it does not correspond to boundary identification information.

[0442] For example, the second communication device processing the first TB based on the first boundary identification information may include / be replaced by: the second communication device processing the first TB based on at least one boundary identification information; or, the second communication device decoding some or all of the CBs in C CBs (or, some or all of the CB groups in N2 CB groups). For example, at least one boundary identification information may include: the first boundary identification information. Optionally, at least one boundary identification information may include: L boundary identification information.

[0443] For example, the first boundary identification information is one of L boundary identification information.

[0444] Optionally, the PHY layer of the second communication device receives the first TB and performs CRC (e.g., CB CRC and / or CB group CRC) verification. For example, for a specific CB, after successfully verifying the CB CRC of that CB, the CB is submitted to the MAC layer of the second communication device. Alternatively, for a specific CB group, after successfully verifying the CRC of each CB in the CB group and after the CB group CRC verification is successful, the CB group is submitted to the MAC layer of the second communication device.

[0445] For example, the second communication device may decode some or all of the C CBs (or some or all of the N2 CB groups) respectively, which may include / be replaced by at least one of the following: the second communication device ignores the TB CRC, or the second communication device determines that the first communication device does not add / de-enable the TB CRC, or the second communication device determines that the TB CRC does not exist, or the second communication device decodes the first CB (or the first CB group), or the second communication device decodes the second CB (or the second CB group), or the second communication device decodes the first CB (or the first CB group) and the second CB (or the second CB group) respectively.

[0446] For example, in the embodiments of this application, "not added" can include / replace with: not added.

[0447] For example, in the embodiments of this application, the first communication device does not add / de-enable TB CRC, which may include / be replaced by: for the first TB, the first communication device does not add / de-enable TB CRC.

[0448] For example, in an embodiment of this application, the second communication device determines that the TB CRC does not exist, which may include / be replaced by: for the first TB, the second communication device determines that the TB CRC does not exist.

[0449] For example, some or all of the CBs in C CBs (or some or all of the CB groups in N2 CB groups) may include / be replaced by: a first CB (or a first CB group), or a second CB (or a second CB group), or a first CB (or a first CB group) and a second CB (or a second CB group).

[0450] For example, decoding, or performing decoding, or performing decoding separately, may include / be replaced by at least one of the following: self-decoding, independent decoding, data processing, decoding, splitting, demultiplexing, or retrieving boundary identification information. For example, retrieval may include / be replaced by at least one of the following: retrieval, or verification.

[0451] For example, data processing may include at least one of the following: MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and layer 2 (L2).

[0452] For example, "the second communication device decodes some or all of the C CBs (or some or all of the N2 CB groups) respectively" may include / be replaced by at least one of the following: the second communication device (or the PHY layer of the second communication device) submits some or all of the C CBs (or some or all of the N2 CB groups) to the upper layer or L2 for data processing, or the second communication device (or the PHY layer of the second communication device) submits some or all of the C CBs (or some or all of the N2 CB groups) to the upper layer or L2.

[0453] For example, the upper layer may include / be replaced by a MAC layer, or the MAC layer of the second communication device. For example, "the second communication device decodes the first CB (or the first CB group)" may include / be replaced by at least one of the following: the second communication device (or the PHY layer of the second communication device) submits the first CB (or the first CB group) to the upper layer or L2 for data processing, or the second communication device (or the PHY layer of the second communication device) submits the first CB (or the first CB group) to the upper layer or L2.

[0454] For example, if the first CB (or the first CB group) is successfully received, the second communication device can decode the first CB (or the first CB group) regardless of whether the CBs or CB groups preceding the first CB (or the first CB group) were successfully received.

[0455] For example, if the first CB (or the first CB group) is successfully received, but the CBs or CB groups preceding the first CB (or the first CB group) fail to be received, the second communication device can decode the first CB (or the first CB group).

[0456] For example, if the second CB (or second CB group) is successfully received while the first CB (or first CB group) fails to be received, the second communication device can decode the second CB (or second CB group). For example, the second CB or second CB group follows the first CB or first CB group. For example, the bit stream corresponding to the second CB or second CB group follows the bit stream corresponding to the first CB or first CB group. For example, the bits corresponding to the first CB or first CB group are bits a to a+b-1, and the bits corresponding to the second CB or second CB group are bits a+b to a+2×b-1. For example, the first CB or first CB group corresponds to the high-order bits, and the second CB or second CB group corresponds to the low-order bits; or vice versa.

[0457] For example, if some CBs in the first CB group are successfully received, regardless of whether the CBs or CB groups preceding the first CB group were successfully received, the second communication device can decode the CBs that were successfully received in sequence in the first CB group. For example, the first CB group contains CB1, CB2, and CB3, with CB1 preceding CB2 and CB2 preceding CB3. If CB1 and CB3 are successfully received, but CB2 fails to be received, regardless of whether the CBs or CB groups preceding the first CB group were successfully received, the second communication device can decode the CBs that were successfully received in sequence in the first CB group (i.e., CB1).

[0458] For example, this method allows the decoding of a CB or CB group to be independent of the reception or decoding results of CBs in previous CBs or CB groups, and the decoding of subsequent CBs or CBs can still be performed even if the reception of a CB group or CB fails (e.g., CRC check fails) or the decoding fails.

[0459] For example, at least one of the following: "the second communication device decodes some or all of the CBs in C CBs (or, some or all of the CB groups in N2 CB groups)," "the second communication device decodes the first CB (or, the first CB group)," "the second communication device decodes the second CB (or, the second CB group)," "the second communication device decodes the first CB (or, the first CB group) and the second CB (or, the second CB group)," and S1303, may include / be replaced with / understood as: the second communication device decodes at the granularity of CBs or CB groups.

[0460] Optionally, the second communication device processes the first TB based on the first boundary identification information, which can be understood as: the second communication device determines the data format (or bit meaning) corresponding to the first TB according to the first boundary identification information, and / or the second communication device ignores or deletes L boundary identification information.

[0461] For example, if the second communication device successfully receives all C CBs corresponding to the first TB, the second communication device processes the first TB based on the first boundary identification information. This can be understood as: the second communication device determines the data format (or bit meaning) corresponding to the first TB according to the first boundary identification information, and / or the second communication device ignores or deletes L boundary identification information.

[0462] Optionally, if the second communication device fails to receive some of the C CBs, the following explanation uses the failure of the first CB among the C CBs as an example. The second CB is the CB following the first CB among the C CBs. In this case, if the first CB fails to be received but the second CB is received successfully, the second communication device retrieves boundary identification information from the second CB. If the first boundary identification information is found in the second CB, the MAC subPDU associated with the first boundary identification information is parsed based on the first boundary identification information. For example, the second CB is the first CB after the first CB that contains a MAC subheader or boundary identification information. For example, the first boundary identification information after the first CB is called the first boundary identification information.

[0463] For example, the second communication device processing the first TB according to the absence of corresponding boundary identification information may include / be replaced by: the second communication device decoding some or all of the CBs in C CBs (or some or all of the CB groups in N2 CB groups) sequentially / in order; or, the second communication device decoding some or all of the CBs that were successfully received in sequence in C CBs (or some or all of the CB groups that were successfully received in sequence in N2 CB groups); or, the second communication device delivering the CBs in order when the CB CRC check passes; or, the second communication device delivering the first TB or decoding the first TB when the first TB is successfully received.

[0464] The following examples, provided in this application, illustrate how the second communication device processes the first TB based on the first boundary identification information when some of the C CBs fail to be received.

[0465] Optionally, if the first CB fails to be received but the second CB is successfully received, the second communication device begins to retrieve boundary identification information (e.g., retrieve boundary identification information starting from the second CB).

[0466] Optionally, if the first CB fails to be received but the second CB is received successfully, the second communication device will only begin retrieving the boundary identification information (e.g., starting the retrieval from the second CB) if it cannot determine the boundary / position of the MAC subPDU (or the first MAC subPDU), MAC subheader (or the first MAC subheader), or boundary identification information (or the first boundary identification information) in the second CB (or, the second CB and subsequent CBs). For example, the first CB precedes the second CB. For example, the first CB is the CB preceding the second CB.

[0467] For example, in Example 1, Figure 19 illustrates a scenario where a boundary identification information is associated with a MAC subPDU, and the second communication device processes the first TB based on the first boundary identification information. Figure 19(a) shows the correspondence between each MAC subPDU and each CB corresponding to the first TB. In Figure 19(b), CB2 reception fails (i.e., CB2 is the first CB). It is understandable that because the MAC subheader of the MAC subPDU (i.e., MAC subPDU#5) corresponding to the CB after CB2 (i.e., CB3) is in CB2, CB2 reception fails, and the second communication device cannot determine the end position of MAC subPDU#5, that is, it cannot determine the position of the first MAC subheader after CB2 (i.e., the start position of MAC subPDU#6, or the start position of the MAC subheader of MAC subPDU#6). In this case, the second communication device begins retrieving boundary identification information at the first CB after CB2, and considers the first boundary identification information retrieved after CB2 (i.e., boundary identification information #6 shown in Figure 19(b)) as the first boundary identification information. Furthermore, the second communication device determines the first MAC subheader in CB4 based on the first boundary identification information, and decodes the MAC subPDU associated with the first boundary identification information (i.e., MAC subPDU#6 shown in (b) of Figure 19).

[0468] For example, in another example 2, Figure 20 shows a scenario where a boundary identification information is associated with three MAC subPDUs, and the second communication device processes the first TB based on the first boundary identification information. Figure 20(a) shows the correspondence between each MAC subPDU and each CB corresponding to the first TB. In Figure 20(b), CB2 reception fails (i.e., CB2 is the first CB). It is understandable that since the MAC header of the first MAC subPDU (i.e., MAC subPDU#5) corresponding to the CB after CB2 (i.e., CB3) is in CB2, CB2 reception fails, and the second communication device cannot determine the end position of MAC subPDU#5, nor can it determine the start / end position of MAC subPDU#6. In this case, the second communication device begins retrieving boundary identification information from the first CB after CB2, and considers the first boundary identification information retrieved after CB2 (i.e., boundary identification information #3 shown in Figure 20(b)) as the first boundary identification information. Furthermore, the second communication device determines the first MAC subheader in CB4 based on the first boundary identification information, and decodes the MAC subPDU associated with the first boundary identification information (i.e., MAC subPDU#7 shown in (b) of Figure 20).

[0469] Optionally, if the size of each MAC subPDU in one or more MAC subPDUs associated with the boundary identification information is an integer multiple of the size of the boundary identification information (denoted as X bytes), the second communication device can perform searches on each CB after the first CB with a granularity of X bytes. Compared to the second communication device only being able to perform searches on each CB after the first CB with a granularity of 1 byte, this method is more conducive to improving search efficiency and reducing the power consumption of the second communication device used for searching.

[0470] Optionally, if the first CB fails to be received but the second CB is successfully received, and the second communication device can determine the boundary / position of the MAC subPDU (or the first MAC subPDU) or MAC subheader (or the first MAC subheader) or boundary identification information (or the first boundary identification information) in the second CB (or, the second CB and subsequent CBs), then the second communication device does not need to retrieve the boundary identification information.

[0471] In one example, Figure 19 illustrates the scenario where a boundary identification information is associated with a MAC subPDU, and the second communication device processes the first TB based on the first boundary identification information. Figure 19(a) shows the correspondence between each MAC subPDU and each CB corresponding to the first TB. In Figure 19(c), CB3 reception fails (i.e., CB3 is the first CB). It is understood that since the MAC subheader of the first MAC subPDU (i.e., MAC subPDU#5) corresponding to the CB after CB3 (i.e., CB4) is in CB2, and CB2 is successfully received, the second communication device can decode CB2 to determine the end position of MAC subPDU#5, that is, determine the position of the first MAC subheader after CB3 (i.e., the start position of MAC subPDU#6, or the start position of the MAC subheader of MAC subPDU#6). In this case, the second communication device does not need to retrieve the boundary identification information starting from the first CB after CB3. Further, the second communication device decodes MAC subPDU#6 based on the MAC subheader of MAC subPDU#6.

[0472] In another example, Figure 20 illustrates the scenario where a boundary identification information is associated with three MAC subPDUs, and the second communication device processes the first TB based on the first boundary identification information. Figure 20(a) shows the correspondence between each MAC subPDU and each CB corresponding to the first TB. In Figure 20(c), CB3 reception fails (i.e., CB3 is the first CB). It is understandable that the boundary identification information #2 associated with the first MAC subPDU (i.e., MAC subPDU#6) corresponding to the CB after CB3 (i.e., CB4) is in CB2. CB2 is successfully received, and the second communication device obtains the boundary identification information #2, which contains length information indicating the length of MAC subPDUs #4 to #6. It can be understood that the second communication device can determine the end position of MAC subPDU#6 based on the boundary identification information #2, i.e., determine the position of the first MAC subheader in CB4 (i.e., the MAC subheader of MAC subPDU#7). In this case, the second communication device does not need to retrieve the boundary identification information starting from the first CB after CB3. Furthermore, the second communication device decodes MAC subPDU#7 based on the MAC subheader of MAC subPDU#7.

[0473] Optionally, in conjunction with the aforementioned implementation of the first boundary identifier information including the first verification information in S1301 (i.e., implementation ② or implementation ③ in S1301), if the second communication device retrieves the first boundary identifier, the second communication device needs to verify the first verification information. For example, if the first verification information passes verification, the second communication device determines that the first boundary identifier information is true, and processes the first TB based on the first boundary identifier information. If the second communication device fails to verify the verification information included in the retrieved boundary identifier information, the second communication device determines that the retrieved boundary identifier information is false, and the second communication device continues to search until the verification information included in the retrieved boundary identifier information passes verification, at which point the second communication device processes the first TB based on the boundary identifier information. By implementing this possible implementation, the situation of false detection of boundary identifier information can be avoided, which is beneficial to improving the reliability of boundary identifier information; or, the length of the boundary identifier can be reduced, which is beneficial to saving resources.

[0474] Optionally, embodiments of this application may further include: S1305A and / or S1306A, and / or S1305B and / or S1306B (all not shown in FIG13).

[0475] Optionally, this application also needs to satisfy: S1305A and / or S1306A, and / or, S1305B and / or S1306B.

[0476] Optionally, if the first communication device is an access network device and the second communication device is a terminal, or if the first communication device and the second communication device are two different terminals, the embodiments of this application may further include: S1305A and / or S1306A.

[0477] S1305A (not shown in Figure 13), the first communication device determines that the second communication device supports decoding at the granularity of CB or CB group.

[0478] For example, support can be included / replaced with: able to, or, can.

[0479] For example, decoding at the granularity of CB or CB group can include / replace CB or CB group self-decoding.

[0480] For example, the second communication device supports decoding at the granularity of CB or CB group, which may include / be replaced by: the second communication device supporting decoding of some or all of the CBs in C CBs (or, some or all of the CB groups in N2 CB groups), or the second communication device supporting execution of step S1303; the second communication device supporting TB (or MAC PDU) corresponding to boundary identification information.

[0481] For example, the first communication device determining that the second communication device supports decoding at the granularity of CB or CB group can include / be replaced by: the first communication device determining that the first communication device can have corresponding boundary identification information in TB (or MAC PDU).

[0482] For example, if the first communication device determines that the second communication device supports decoding at the granularity of CB or CB groups, this may include / be replaced by: the first communication device acquiring second indication information, or the first communication device acquiring second indication information from the second communication device. For example, the second communication device sends second indication information to the first communication device, and the first communication device receives second indication information from the second communication device.

[0483] For example, the second indication information includes information indicating whether the second communication device supports or does not support decoding at the granularity of CB or CB group, or information indicating whether the first communication device can or cannot have boundary identification information corresponding to TB (or MAC PDU). For example, "support" or "not support" can include / be replaced with "whether it supports it." For example, "can or cannot" can include / be replaced with "whether it can be used."

[0484] For example, the first communication device can determine whether the second communication device supports decoding at the granular level of CB or CB group, using the terminal as the unit.

[0485] For example, the second communication device can send indication information to the first communication device at the terminal level to indicate whether the second communication device supports "decoding at the CB or CB group level".

[0486] Optionally, step S1305A can be performed before step S1301 (or implementation 1). For example, if the first communication device determines that the second communication device supports decoding at the granularity of CB or CB group, the first communication device will execute step S1301 (or implementation 1), or the first communication device will generate the TB corresponding to the boundary identification information.

[0487] S1306A (not shown in Figure 13), the second communication device determines that the second communication device can perform decoding at the granularity of CB or CB group.

[0488] For example, the second communication device determining that it can decode at the granularity of CB or CB group can include / be replaced by: the second communication device determining that the first communication device has corresponding boundary identification information in TB (or MAC PDU).

[0489] For example, the second communication device may decode at the granularity of CB or CB group, and may include / replace: allowing the second communication device to decode at the granularity of CB or CB group, or the second communication device being allowed to decode at the granularity of CB or CB group.

[0490] For example, the first communication device has boundary identification information in TB (or MAC PDU), which may include / be replaced by: the first communication device executes S1301 (or implements 1), or TB has boundary identification information.

[0491] For example, if the second communication device determines that it can decode at the granularity of CB or CB group, this may include / be replaced by: the second communication device acquiring third indication information, or the second communication device acquiring third indication information from the first communication device. For example, the first communication device sends third indication information to the second communication device, and the second communication device receives third indication information from the first communication device.

[0492] For example, the third indication information includes information indicating whether the second communication device can or cannot decode at the granularity of CB or CB group, or information indicating whether the first communication device has or does not have boundary identification information in the TB (or MAC PDU). For example, "has or does not have" can include / be replaced by: whether it has.

[0493] For example, the first communication device may send information to the second communication device at the granularity of terminal, DCI, TB, CW, SPS, or CG to indicate whether the second communication device can or cannot perform decoding at the granularity of CB or CB group, or to notify the first communication device whether there is or does not correspond to boundary identification information in TB (or MAC PDU).

[0494] As one possible implementation, the third indication information is associated with at least one of the following, or the third indication information is granular with one of the following: terminal, DCI, TB, CW, SPS, CG, LCH, RB.

[0495] For example, associating third indication information with a terminal can indicate that different terminals can correspond to different third indication information. For example, associating third indication information with DCI can indicate that different DCI schedules / corresponding TBs can correspond to different third indication information. For example, associating third indication information with TB can indicate that different TBs can correspond to different third indication information. For example, associating third indication information with SPS / CG can indicate that different SPS / CGs can correspond to different third indication information.

[0496] For example, the third indication information can be carried by at least one of the following: DCI format, DCI scrambling information, information in DCI, time domain resources of DCI, and frequency domain resources of DCI.

[0497] Optionally, step S1306A can be performed before step S1303. For example, if the second communication device determines that it can decode at the granularity of CB or CB group, then the second communication device executes step S1303.

[0498] Optionally, if the first communication device is a terminal and the second communication device is an access network device, or if the first communication device and the second communication device are two different terminals, the embodiments of this application may further include: S1305B and / or S1306B.

[0499] S1305B (not shown in Figure 13) The second communication device determines that the first communication device supports boundary identification information corresponding to the TB (or MAC PDU).

[0500] For example, the first communication device supports the existence of boundary identification information in the TB (or MAC PDU), which may include / be replaced by: the first communication device supports the execution of step S1301, or the TB corresponds to boundary identification information.

[0501] For example, if the second communication device determines that the first communication device supports boundary identification information corresponding to the TB (or MAC PDU), it may include / be replaced by: the second communication device determining that the second communication device can perform decoding at the granularity of CB or CB group.

[0502] For example, if the second communication device determines that the first communication device supports boundary identification information in the TB (or MAC PDU), it may include / be replaced by: the second communication device acquiring fourth indication information, or the second communication device acquiring fourth indication information from the first communication device. For example, the first communication device sends fourth indication information to the second communication device, and the second communication device receives fourth indication information from the first communication device.

[0503] For example, the fourth indication information includes information for indicating whether the first communication device supports or does not support boundary identification information corresponding to the TB (or MAC PDU), or for indicating whether the second communication device can or cannot perform decoding at the granularity of CB or CB group.

[0504] For example, the first communication device can send information to the second communication device at the terminal level to indicate whether the first communication device supports or does not support boundary identification information corresponding to the TB (or MAC PDU).

[0505] Optionally, step S1305B can be performed before step S1303. For example, the second communication device will only execute step S1303 if it determines that the first communication device supports the corresponding boundary identification information in the TB (or MAC PDU).

[0506] S1306B, The first communication device determines that the first communication device can have corresponding boundary identification information in TB (or MAC PDU).

[0507] For example, the first communication device may have boundary identification information in the TB (or MAC PDU), which may include / be replaced by: the first communication device determining that the second communication device can (or supports) decoding at the granularity of CB or CB group.

[0508] For example, the first communication device may have boundary identification information in the TB (or MAC PDU), which may include / be replaced by: allowing the first communication device to have boundary identification information in the TB (or MAC PDU), or the first communication device being allowed to have boundary identification information in the TB (or MAC PDU), or allowing the first communication device to perform the above step S1301 (or implement 1), or allowing the first communication device to generate a TB with corresponding boundary identification information.

[0509] For example, if the first communication device determines that it can have boundary identification information in the TB (or MAC PDU), it may include / be replaced by: the first communication device acquiring the fifth indication information, or the first communication device acquiring the fifth indication information from the second communication device. For example, the second communication device sends the fifth indication information to the first communication device, and the first communication device receives the fifth indication information from the second communication device.

[0510] For example, the fifth indication information includes information indicating that the first communication device can have boundary identification information in the TB (or MAC PDU), or information indicating that the second communication device can (or supports) decoding at the granularity of CB or CB group.

[0511] For example, the second communication device can send information to the first communication device at the granularity of terminal, DCI, TB, CW, SPS, or CG to indicate whether the first communication device has corresponding boundary identification information in TB (or MAC PDU), or to indicate whether the second communication device can (or supports) decode at the granularity of CB or CB group.

[0512] As one possible implementation, the fifth instruction information is associated with one of the following, or in other words, the fifth instruction information is granular with one of the following: terminal, DCI, TB, CW, SPS, CG, LCH, RB.

[0513] For example, associating the fifth indication information with a terminal can indicate that different terminals can correspond to different fifth indication information. For example, associating the fifth indication information with DCI can indicate that different DCI schedules / corresponding TBs can correspond to different fifth indication information. For example, associating the fifth indication information with a TB can indicate that different TBs can correspond to different fifth indication information. For example, associating the fifth indication information with SPS / CG can indicate that different SPS / CGs can correspond to different fifth indication information.

[0514] For example, the fifth indication information can be carried by at least one of the following: DCI format, DCI scrambling information, information in DCI, time domain resources of DCI, and frequency domain resources of DCI.

[0515] Optionally, step S1306B can be performed before step S1301 (or implementation 1). For example, the first communication device executes step S1301 (or implementation 1) only if it determines that the first communication device can have corresponding boundary identification information in the TB (or MAC PDU), or the first communication device generates the TB with corresponding boundary identification information.

[0516] Optionally, the second indication information and the fourth indication information can be the same indication information or different indication information, without limitation. For example, the terminal sends the second indication information to the access network device, and the access network device receives the second indication information from the terminal. For example, the second indication information includes at least one of the following: information for indicating whether the terminal supports or does not support decoding at the granularity of CB or CB group; information for indicating whether the access network device can or cannot have boundary identification information corresponding to TB (or MAC PDU); information for indicating whether the terminal supports or does not support information corresponding to boundary identification information in TB (or MAC PDU); or, information for indicating whether the access network device can or cannot perform decoding at the granularity of CB or CB group.

[0517] For example, the second indication information and / or the fourth indication information may (or may also) include at least one of the following: information for indicating whether the access network device (or, the first communication device or the second communication device) can or cannot ignore the TB CRC, information for indicating whether the terminal (or, the first communication device or the second communication device) adds or does not add (or enables or disables) the TB CRC, or information for indicating whether the TB CRC exists or does not exist.

[0518] Optionally, the third indication information and the fifth indication information can be the same indication information or different indication information, without limitation. For example, the access network device sends the third indication information to the terminal, and the terminal receives the third indication information from the access network device. For example, the third indication information includes at least one of the following: information for indicating whether the terminal can or cannot decode at the granularity of CB or CB group; information for indicating whether the access network device has or does not have boundary identification information in the TB (or MAC PDU); information for indicating whether the terminal can or cannot have boundary identification information in the TB (or MAC PDU); or information for indicating whether the access network device can or cannot (or supports or does not support) decode at the granularity of CB or CB group.

[0519] For example, the third and / or fifth indication information may (or may also) include at least one of the following: information indicating whether the terminal (or, the first or second communication device) can or cannot ignore the TB CRC; information indicating whether the access network device (or, the first or second communication device) adds or does not add (or enables or disables) the TB CRC; or information indicating whether the TB CRC exists or does not exist. For example, ignoring the TB CRC may include / be replaced by: 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. For example, adding or not adding may include / be replaced by: whether it is added. For example, enabling or disabling may include / be replaced by: whether it is enabled. For example, existing or not existing may include / be replaced by: whether it exists.

[0520] In summary, based on the method shown in Figure 13, the N MAC subPDUs corresponding to the first TB are divided into L groups or L+1 groups of MAC subPDUs using L boundary identification information. Each boundary identification information indicates the boundary of at least one MAC subPDU. The groups of MAC subPDUs divided by the boundary identification information can be considered independent of each other. The second communication device can decode each group of MAC subPDUs independently, and the decoding of a certain group of MAC subPDUs does not depend on other groups. For example, if at least one CB corresponding to a certain group of MAC subPDUs fails to be received, the subsequently successfully received CBs can still be submitted to the MAC layer for continued decoding, enabling the second communication device to process the successfully received CBs in a timely manner, thereby reducing service latency. Furthermore, timely submission of subsequently successfully received CBs to the MAC layer reduces the number of CBs that cannot be submitted to the MAC layer for processing, thereby reducing storage requirements, i.e., reducing memory increases, saving costs, and also reducing device power consumption caused by DDR erasure and writing.

[0521] For example, using the method described above, the boundaries of MAC subPDUs can be identified through boundary identification information. Decoding a CB / CB group does not rely on the successful reception of previous CB / CB groups. Even if the reception of a previous CB / CB group fails, the successfully received CB / CB groups can be submitted to the MAC layer for processing. This allows the receiving end to process successfully received CB / CB groups in a timely manner, thereby reducing service latency and ensuring data arrives within the service's latency requirements. This improves communication quality and system capacity. Furthermore, timely submission of subsequently received CB / CB groups to the MAC layer reduces the number of CBs that cannot be submitted, thus reducing storage requirements (e.g., less on-chip memory is needed), saving costs, or reducing DDR bandwidth requirements (e.g., less DDR bandwidth is needed), while also reducing device power consumption from DDR erasure and rewriting. This also helps address the challenges of future services requiring lower latency and / or higher speeds.

[0522] It should be noted that at least one of padding, CB CRC, CB group CRC, TB CRC, etc. may not be shown in the accompanying drawings of this application, but this does not mean that it does not exist.

[0523] 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.

[0524] The method provided in this application has been described above. In addition, this application also provides a communication device for implementing the functions described in the above method embodiments.

[0525] 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.

[0526] 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.

[0527] Figure 21 shows a schematic diagram of a communication device 210. The communication device 210 includes a processing module 2101 and a transceiver module 2102. The communication device 210 can be used to implement the functions of the first communication device and the second communication device described above.

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

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

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

[0531] When the communication device 210 is used to implement the function of the second communication device:

[0532] The transceiver module 2102 is used to receive a first TB, which corresponds to N MAC subPDUs and L boundary identification information, where N is a positive integer and L is a positive integer less than or equal to N; the processing module 2101 is used to process the first TB based on the first boundary identification information, where the first boundary identification information is one of the L boundary identification information.

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

[0534] Optionally, the processing module 2101 is further configured to process the first TB based on the first boundary identification information if the first verification information passes the verification.

[0535] Optionally, the first boundary identification information may further include first length information, which indicates the length of one or more MAC subPDUs associated with the first boundary identification information.

[0536] Optionally, the first boundary identification information is included in the first MAC subheader, which is the MAC subheader of one of the N MAC subPDUs.

[0537] Optionally, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information.

[0538] Optionally, the first verification information is used to verify fields in the first MAC subheader other than the first boundary identification information; or, the first verification information is used to verify M1 bytes after the first boundary identification information, where M1 is a positive integer; or, the first verification information is used to verify the first length information.

[0539] Optionally, the first boundary identification information is located before the first MAC subheader or the first MAC subPDU, and / or the first boundary identification information is located after the second MAC subPDU; wherein the first MAC subheader is the MAC subheader of one of the N MAC subPDUs, the first MAC subPDU and the second MAC subPDU are two adjacent MAC subPDUs among the N MAC subPDUs, and the second MAC subPDU is located before the first MAC subPDU.

[0540] Optionally, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information, or the first MAC subheader is the MAC subheader of the MAC subPDU following the last MAC subPDU associated with the first boundary identification information.

[0541] Optionally, the first verification information is used to verify the first MAC subheader; or, the first verification information is used to verify the M1 bytes following the first boundary identification information, where M1 is a positive integer; or, the first verification information is used to verify the first length information; or, the first verification information is used to verify the M2 bytes preceding the first boundary identification information, where M2 is a positive integer.

[0542] Optionally, the first TB corresponds to C CBs, the C CBs include the first CB and the second CB, the first CB is before the second CB, and C is an integer greater than 1; the processing module 2101 is further configured to retrieve boundary identification information in the second CB in the event of a receiving error in the first CB; the processing module 2101 is further configured to parse the MAC subPDU associated with the first boundary identification information based on the first boundary identification information if the first boundary identification information is retrieved in the second CB.

[0543] Optionally, if the size of the first TB is greater than or equal to the first threshold, the first TB corresponds to boundary identification information; or, if the size of the first TB is less than the first threshold, the first TB does not correspond to boundary identification information; or, if the number of CBs or CB groups corresponding to the first TB is greater than or equal to the second threshold, the first TB corresponds to boundary identification information; or, if the number of CBs or CB groups corresponding to the first TB is less than the second threshold, the first TB does not correspond to boundary identification information.

[0544] Optionally, the transceiver module 2102 is also used to receive first indication information, which corresponds to boundary identification information for the first TB.

[0545] When the communication device 210 is used to perform the functions of the first communication device:

[0546] Processing module 2101 is used to generate a first TB, which corresponds to N MAC subPDUs and L boundary identification information, where N is a positive integer and L is a positive integer less than or equal to N; transceiver module 2102 is used to send the first TB.

[0547] Optionally, the first boundary identification information is at least one of the L boundary identification information, and the first boundary identification information includes a first boundary identifier and / or first verification information.

[0548] Optionally, the first boundary identification information may further include first length information, which indicates the length of the MAC subPDU associated with the first boundary identification information.

[0549] Optionally, the first boundary identification information is included in the first MAC subheader, which is the MAC subheader of one of the N MAC subPDUs.

[0550] Optionally, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information.

[0551] Optionally, the first verification information is generated based on fields in the first MAC subheader other than the first boundary identification information; or, the first verification information is generated based on M1 bytes after the first boundary identification information, where M1 is a positive integer; or, the first verification information is generated based on the first length information.

[0552] Optionally, the first boundary identification information is located before the first MAC subheader or the first MAC subPDU, and / or the first boundary identification information is located after the second MAC subPDU; wherein the first MAC subheader is the MAC subheader of one of the N MAC subPDUs, the first MAC subPDU and the second MAC subPDU are two adjacent MAC subPDUs among the N MAC subPDUs, and the second MAC subPDU is located before the first MAC subPDU.

[0553] Optionally, the first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information, or the first MAC subheader is the MAC subheader of the MAC subPDU following the last MAC subPDU associated with the first boundary identification information.

[0554] Optionally, the first verification information is generated based on the first MAC subheader; or, the first verification information is generated based on M1 bytes after the first boundary identification information, where M1 is a positive integer; or, the first verification information is generated based on the first length information; or, the first verification information is generated based on M2 bytes before the first boundary identification information, where M2 is a positive integer.

[0555] Optionally, if the size of the first TB is greater than or equal to the first threshold, the first TB corresponds to boundary identification information; or, if the size of the first TB is less than the first threshold, the first TB does not correspond to boundary identification information; or, if the number of CBs or CB groups corresponding to the first TB is greater than or equal to the second threshold, the first TB corresponds to boundary identification information; or, if the number of CBs or CB groups corresponding to the first TB is less than the second threshold, the first TB does not correspond to boundary identification information.

[0556] Optionally, the transceiver module 2102 is also used to send first indication information, which indicates that the first TB corresponds to boundary identification information.

[0557] 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.

[0558] In this application, the communication device 210 can be presented in an integrated manner by dividing it 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.

[0559] In some embodiments, when the communication device 210 in FIG21 is a chip or chip system, the function / implementation process of the transceiver module 2102 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 2101 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0560] Since the communication device 210 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.

[0561] As a possible product form, the first or second communication device described in the embodiments of this application can be implemented using 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.

[0562] As another possible product form, the first or second communication device described in this application embodiment can be implemented using a general bus architecture. For ease of explanation, refer to FIG22, which is a schematic diagram of the structure of a communication device 2200 provided in an embodiment of this application. The communication device 2200 includes a processor 2201 and a transceiver 2202. The communication device 2200 can be a first communication device, or a chip, chip system, or module thereof therein; or, the communication device 2200 can be a second communication device, or a chip, chip system, or module thereof therein. FIG22 only shows the main components of the communication device 2200. In addition to the processor 2201 and transceiver 2202, the communication device may further include a memory 2203 and input / output devices (not shown in the figure).

[0563] Optionally, the processor 2201 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 2203 is mainly used to store software programs and data. The transceiver 2202 may include radio frequency (RF) circuitry and an antenna. The RF circuitry 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.

[0564] Optionally, the processor 2201, transceiver 2202, and memory 2203 can be connected via a communication bus.

[0565] When the communication device is powered on, the processor 2201 can read the software program in the memory 2203, execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 2201 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes 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 2201. The processor 2201 converts the baseband signal into data and processes the data.

[0566] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0567] In some embodiments, those skilled in the art will recognize that the above-described communication device 210 can take the form of the communication device 2200 shown in FIG22 in terms of hardware implementation.

[0568] As an example, the function / implementation of the processing module 2101 in Figure 21 can be achieved by the processor 2201 in the communication device 2200 shown in Figure 22 calling computer execution instructions stored in the memory 2203. The function / implementation of the transceiver module 2102 in Figure 21 can be achieved by the transceiver 2202 in the communication device 2200 shown in Figure 22.

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

[0570] As shown in Figure 23, the communication device 2300 includes at least one processor 2301 and at least one communication interface (Figure 23 is merely an example illustrating the inclusion of a communication interface 2304 and a processor 2301). Optionally, the communication device 2300 may also include a communication bus 2302 and a memory 2303.

[0571] Processor 2301 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 2301 can also be other devices with processing functions, such as circuits, devices, or software modules, without limitation.

[0572] The communication bus 2302 is used to connect different components in the communication device 2300, enabling communication between them. The communication bus 2302 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 23, but this does not indicate that there is only one bus or one type of bus.

[0573] Communication interface 2304 is used for communicating with other devices or communication networks. Exemplarily, communication interface 2304 can be a module, circuit, transceiver, or any device capable of communication. Optionally, the communication interface 2304 can also be an input / output interface located within processor 2301, used to implement signal input and signal output for the processor.

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

[0575] For example, the memory 2303 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.

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

[0577] Optionally, the processor 2301 and / or memory 2303 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.

[0578] As an optional implementation, the communication device 2300 may also include an output device 2305 and an input device 2306. The output device 2305 communicates with the processor 2301 and can display information in various ways. For example, the output device 2305 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 2306 communicates with the processor 2301 and can receive user input in various ways. For example, the input device 2306 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0579] In some embodiments, those skilled in the art will recognize that the communication device 210 shown in FIG21 can take the form of the communication device 2300 shown in FIG23 in terms of hardware implementation.

[0580] As an example, the function / implementation process of the processing module 2101 in Figure 21 can be implemented by the processor 2301 in the communication device 2300 shown in Figure 23 calling computer execution instructions stored in the memory 2303. The function / implementation process of the transceiver module 2102 in Figure 21 can be implemented by the communication interface 2304 in the communication device 2300 shown in Figure 23.

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

[0582] 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.

[0583] 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.

[0584] 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.

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

[0586] 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.

[0587] 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.

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

[0589] 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.

[0590] 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 couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0591] 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.

[0592] 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.

[0593] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This 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 processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The 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 available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

[0594] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will 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 a plurality. 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.

[0595] 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 its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

A data processing method, characterized in that, The method includes: Receive a first transport block TB, the first TB corresponding to N Media Access Control Sub-Protocol Data Units (MAC subPDUs) and L boundary identification information, where N is a positive integer and L is a positive integer less than or equal to N; The first TB is processed based on the first boundary identification information, where the first boundary identification information is one of the L boundary identification information. The method according to claim 1 is characterized in that, The first boundary identification information includes a first boundary identifier and / or first verification information. The method according to claim 2 is characterized in that, The processing of the first TB based on the first boundary identification information includes: If the first verification information passes the verification, the first TB is processed based on the first boundary identification information. The method according to claim 2 or 3 is characterized in that, The first boundary identification information also includes first length information, which is used to indicate the length of one or more MAC subPDUs associated with the first boundary identification information. The method according to any one of claims 2-4 is characterized in that, The first boundary identification information is contained in the first MAC subheader, which is the MAC subheader of one of the N MAC subPDUs. The method according to claim 5 is characterized in that, The first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information. The method according to claim 5 or 6 is characterized in that, The first verification information is used to verify fields in the first MAC sub-header other than the first boundary identification information; or, The first verification information is used to verify the M1 bytes following the first boundary identification information, where M1 is a positive integer; or, The first verification information is used to verify the first length information. The method according to claims 2-4 is characterized in that, The first boundary identification information is located before the first MAC subheader or the first MAC subPDU, and / or the first boundary identification information is located after the second MAC subPDU; Wherein, the first MAC subheader is the MAC subheader of one of the N MAC subPDUs, the first MAC subPDU and the second MAC subPDU are two adjacent MAC subPDUs among the N MAC subPDUs, and the second MAC subPDU is before the first MAC subPDU. The method according to claim 8 is characterized in that, The first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information, or; The first MAC subheader is the MAC subheader of the MAC subPDU following the last MAC subPDU associated with the first boundary identification information. The method according to claim 8 or 9 is characterized in that, The first verification information is used to verify the first MAC sub-header; or, The first verification information is used to verify the M1 bytes following the first boundary identification information, where M1 is a positive integer; or, The first verification information is used to verify the first length information; or, The first verification information is used to verify the M2 bytes preceding the first boundary identification information, where M2 is a positive integer. The method according to any one of claims 1-10 is characterized in that, The first TB corresponds to C code blocks CB, the C CBs include the first CB and the second CB, the first CB comes before the second CB, and C is an integer greater than 1; The processing of the first TB based on the first boundary identification information includes: In the event of a reception error in the first CB, the boundary identification information is retrieved from the second CB; If the first boundary identification information is found in the second CB, the MAC subPDU associated with the first boundary identification information is parsed based on the first boundary identification information. The method according to any one of claims 1-11 is characterized in that, If the size of the first TB is greater than or equal to the first threshold, the first TB corresponds to boundary identification information; or, If the size of the first TB is less than the first threshold, the first TB does not have corresponding boundary identification information; or, If the number of CBs or CB groups corresponding to the first TB is greater than or equal to the second threshold, the first TB has boundary identification information. or, If the number of CBs or CB groups corresponding to the first TB is less than the second threshold, the first TB does not correspond to boundary identification information. The method according to any one of claims 1-12 is characterized in that, The method further includes: Receive first indication information, the first indication information having boundary identification information corresponding to the first TB. A data processing method, characterized in that, The method includes: A first transport block TB is generated, which corresponds to N Media Access Control Sub-Protocol Data Units (MAC subPDUs) and L boundary identification information, where N is a positive integer and L is a positive integer less than or equal to N. Send the first TB. The method according to claim 14 is characterized in that, The first boundary identification information is one of the L boundary identification information, and the first boundary identification information includes a first boundary identifier and / or a first verification information. The method according to claim 15 is characterized in that, The first boundary identification information also includes first length information, which is used to indicate the length of the MAC subPDU associated with the first boundary identification information. The method according to claim 15 or 16 is characterized in that, The first boundary identification information is contained in the first MAC subheader, which is the MAC subheader of one of the N MAC subPDUs. The method according to claim 17 is characterized in that, The first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information. The method according to claim 17 or 18 is characterized in that, The first verification information is generated based on fields in the first MAC sub-header other than the first boundary identification information; or, The first verification information is generated based on the M1 bytes following the first boundary identification information, where M1 is a positive integer; or, The first verification information is generated based on the first length information. The method according to claim 15 or 16 is characterized in that, The first boundary identification information is located before the first MAC subheader or the first MAC subPDU, and / or the first boundary identification information is located after the second MAC subPDU; Wherein, the first MAC subheader is the MAC subheader of one of the N MAC subPDUs, the first MAC subPDU and the second MAC subPDU are two adjacent MAC subPDUs among the N MAC subPDUs, and the second MAC subPDU is before the first MAC subPDU. The method according to claim 20 is characterized in that, The first MAC subheader is the MAC subheader of the MAC subPDU associated with the first boundary identification information, or; The first MAC subheader is the MAC subheader of the MAC subPDU following the last MAC subPDU associated with the first boundary identification information. The method according to claim 20 or 21 is characterized in that, The first verification information is generated based on the first MAC sub-header; or, The first verification information is generated based on the M1 bytes following the first boundary identification information, where M1 is a positive integer; or, The first verification information is generated based on the first length information; or, The first verification information is generated based on the M2 bytes preceding the first boundary identification information, where M2 is a positive integer. The method according to any one of claims 14-22 is characterized in that, If the size of the first TB is greater than or equal to the first threshold, the first TB corresponds to boundary identification information; or, If the size of the first TB is less than the first threshold, the first TB does not have corresponding boundary identification information; or, If the number of CBs or CB groups corresponding to the first TB is greater than or equal to the second threshold, the first TB has boundary identification information. or, If the number of CBs or CB groups corresponding to the first TB is less than the second threshold, the first TB does not correspond to boundary identification information. The method according to any one of claims 14-23 is characterized in that, The method further includes: Send a first indication message, which indicates that the first TB has boundary identification information. 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-24. 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-24 to be performed. 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-24 is performed.

Images