Information sending method, information receiving method and device

Abstract

The present application relates to an information sending method, an information receiving method and a device, wherein the method includes: a first device sends a medium access control MAC protocol data unit (PDU) of each carrier in one or more carriers; wherein the MAC PDU of each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-type identification information or second-type identification information; wherein the first-type identification information is used to indicate that the MAC sub-PDU is generated when the data packetization of the data to be sent cannot be completed, and the second-type identification information is different from the first-type identification information.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an information sending method, an information receiving method and a device. Background Art

[0002] In related technologies, the MAC (Medium Access Control) layer generates MAC PDUs (Protocol Data Units), which are then sent by the physical layer. However, when the MAC layer's packetization capabilities are insufficient, preventing data interruptions becomes a challenge. Summary of the Invention

[0003] The present application provides an information sending method, an information receiving method, a device, and a storage medium.

[0004] According to one aspect of the present application, a method for sending information is provided, comprising:

[0005] The first device sends a media access control MAC protocol data unit (PDU) for each of one or more carriers; wherein the MAC PDU for each carrier includes one or more MAC sub-PDUs; each of the one or more MAC sub-PDUs carries first-category identification information or second-category identification information; wherein the first-category identification information is used to characterize that the MAC sub-PDU is generated when data packetization of the data to be sent cannot be completed, and the second-category identification information is different from the first-category identification information.

[0006] According to another aspect of the present application, a method for receiving information is provided, comprising:

[0007] The second device receives a MAC PDU of each carrier in one or more carriers; wherein the MAC PDU of each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-type identification information or second-type identification information; wherein the first-type identification information is used to indicate that the MAC sub-PDU is generated when the data packetization of the data to be sent cannot be completed, and the second-type identification information is different from the first-type identification information

[0008] According to another aspect of the present application, there is provided a first device, comprising:

[0009] A first communication unit is used to send a media access control MAC protocol data unit (PDU) for each carrier in one or more carriers; wherein the MAC PDU of each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-category identification information or second-category identification information; wherein the first-category identification information is used to indicate that the MAC sub-PDU is generated when data packetization of the data to be sent cannot be completed, and the second-category identification information is different from the first-category identification information.

[0010] According to another aspect of the present application, a second device is provided, including:

[0011] A second communication unit is used to receive a MAC PDU of each carrier in one or more carriers; wherein the MAC PDU of each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-category identification information or second-category identification information; wherein the first-category identification information is used to indicate that the MAC sub-PDU is generated when the data packetization of the data to be sent cannot be completed, and the second-category identification information is different from the first-category identification information.

[0012] An embodiment of the present application provides a first device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and execute the computer program stored in the memory, so that the first device performs the above method.

[0013] An embodiment of the present application provides a second device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and execute the computer program stored in the memory, so that the electronic device executes the above method.

[0014] The embodiment of the present application provides a chip for implementing the above method.

[0015] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method.

[0016] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a device to perform the above method when the computer program is executed by the device.

[0017] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above method.

[0018] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method.

[0019] By adopting the above-mentioned solution, the embodiment of the present application can use the first type of identification information in one or more MAC sub-PDUs of the MAC PDU to indicate that the MAC sub-PDU was generated when data packetization of the data to be sent could not be completed. This can avoid the problem of data interruption caused by the inability to transmit data to the peer device when the device's packetization capability is insufficient. In addition, since the insufficient data packetization capability is usually a temporary situation, the solution provided by this embodiment can also avoid the problem of resource waste caused by filling the remaining authorized positions of the MAC PDU when packetization cannot be completed normally.

[0020] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings are provided to facilitate a better understanding of the present invention and do not constitute a limitation of the present application.

[0022] Figure 1 It is a schematic diagram of an application scenario according to an embodiment of the present application.

[0023] Figure 2 This is a schematic diagram of the downlink MAC PDU format according to an embodiment of the present application.

[0024] Figure 3 This is a schematic diagram of the uplink MAC PDU format according to an embodiment of the present application.

[0025] Figures 4 to 6 This is a schematic diagram of the composition of a MAC sub-packet header according to an embodiment of the present application.

[0026] Figure 7 2 is a schematic diagram of package grouping processing according to an embodiment of the present application.

[0027] Figure 8 It is a flowchart of the information sending method according to an embodiment of the present application.

[0028] Figure 9 It is a flowchart of the information receiving method according to an embodiment of the present application.

[0029] Figure 10 This is a schematic diagram of the structure of a downlink MAC PDU according to an embodiment of the present application.

[0030] Figure 11 This is a schematic diagram of the structure of an uplink MAC PDU according to an embodiment of the present application.

[0031] Figure 12is a schematic block diagram of a first device according to an embodiment of the present application.

[0032] Figure 13 is a schematic block diagram of a first device according to another embodiment of the present application.

[0033] Figure 14 This is a schematic block diagram of a second device according to an embodiment of the present application.

[0034] Figure 15 This is another schematic block diagram of a second device according to an embodiment of the present application.

[0035] Figure 16 It is a schematic block diagram of a communication device according to an embodiment of the present application.

[0036] Figure 17 It is a schematic block diagram of a chip according to an embodiment of the present application.

[0037] Figure 18 It is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0038] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0039] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0040] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0041] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0042] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0043] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0044] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0045] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0046] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0047] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0048] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0049] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0050] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0051] Figure 1 A communication system 100 is exemplarily shown. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0052] In one embodiment, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0053] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation Node B (gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0054] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be called a communication device. Figure 1 Taking the communication system shown as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiments of the present application and will not be repeated here; the communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited in the embodiments of the present application.

[0055] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0056] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0057] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0058] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0059] The NR MAC (Medium Access Control) PDU (Protocol Data Unit) contains one or more MAC sub-PDUs. The formats of one or more MAC sub-PDUs that may be included in the downlink MAC PDU are as follows: Figure 2 As shown in; the format of one or more MAC sub-PDUs that may be included in the uplink MAC PDU is as follows: Figure 3 As shown in . Combined Figure 2 or Figure 3 For example, any MAC sub-PDU consists of a MAC sub-header; or any MAC sub-PDU consists of a MAC sub-header plus any one of the following: a MAC service data unit (SDU), a MAC CE (Control Element), or MAC padding. If a MAC PDU contains MAC padding, the MAC sub-PDU (i.e., MAC padding PDU) is placed at the end of the MAC PDU.

[0060] If the MAC sub-PDU is any of the fixed-length (i.e. fixed-size) MAC CE, MAC padding, and MAC SDU containing uplink CCCH (Common Control Channel), its sub-header contains the following: Figure 4 In addition to the fixed-length (i.e., fixed-size) MAC CE, MAC padding, and MAC SDU containing the uplink CCCH, the MAC sub-packet header includes the following: Figure 5 or Figure 6 As shown, the MAC header contains four fixed information fields (or header data fields): R / F / LCID / L. For fixed-size MAC CE, padding, and MAC sub-header containing uplink MAC SDU, two information fields (or header data fields): R / LCID. Among them, the information field R is used to carry reserved content or reservation information; the information field F is used to carry the length of the MAC sub-PDU (excluding the sub-header), for example, Figure 5 As shown in FIG, when the bit value of the information field F is 0, it means that the L field is 8 bits. Figure 6As shown, when the bit value of the information field F is 1, it indicates that the L field is 16 bits; the information field L is used to indicate the length of the MAC layer sub-PDU excluding the packet header; the information field LCID is used to carry the logical channel identifier, for example, if the MAC sub-PDU includes padding, the value of the information field LCID should be 11111.

[0061] Taking uplink transmission as an example, a MAC padding PDU can only be placed in the last sub-PDU of a MAC PDU, and the padding length is calculated by subtracting the effective length from the total MAC PDU length. When uplink packets are numerous, this method loses the flexibility of padding within a sub-PDU within the MAC PDU. For example, a mobile phone with the following capabilities: NR-FR1 band, 6.9 Gbps downlink rate, and 2.5 Gbps uplink per carrier. With a 30 kHz subcarrier spacing (0.5 ms / TTI (Transmission Time Interval)), the downlink transmission consists entirely of 1.5 KB IP packets, and the uplink consists entirely of Transmission Control Protocol (TCP) ACK packets. The downlink transmission rate is 6.9 G * 0.8 / 8 / 1500 / 1000 = 460 packets per millisecond. In TDD (Time Division Duplexing) mode, assuming an uplink and downlink timeslot ratio of 8:2, the number of uplink packet replies is 460 * 8 / 2 / 2 = 920 per millisecond.

[0062] In order to achieve the minimum uplink delay, the Logical Channel Prioritization (LCP) packetization process will be as close to the antenna transmission time as possible. For example, there is a slot (time slot) interval between the UE receiving the uplink authorization and the actual transmission of the data. The UE can use this time slot to do the packetization work. During the LCP packetization process, if there is an uplink data packet with a higher priority to be sent, it must be able to jump in line and catch up with the upcoming transmission time (instant packetization). However, if Figure 7 As shown above the dotted line, if LCP packet processing is performed at the time slot granularity, Figure 7 The high priority uplink data packet (i.e. Figure 7 When the high priority data packets a and b above the dotted line are received, the queue can be interrupted for packet formation. If a new high priority data packet (i.e. Figure 7 For the high priority data packet c) above the dotted line, the problem of not being able to send the high priority data packet may occur.

[0063] In order to achieve the best real-time performance of uplink transmission, the LCP packetization process will start close to the transmission time. Assuming that the physical layer encoder is scheduled at a symbol granularity, it is ideal to start packetization at a time point one symbol in advance. Specifically: the MAC layer generates a data packet of the first symbol (i.e., a MAC sub-PDU of one symbol), the physical layer takes it for encoding and transmission, and the MAC generates the data of the next symbol in parallel, and repeats this process. Figure 7 As shown below the dotted line, a high priority uplink data packet (i.e. Figure 7 When the high priority data packets a and b below the dotted line are received, they can be queued for packet assembly. Slot (time slot) n+2 is the sending time. Before the sending time, the MAC layer starts to perform MAC sub-PDU packet assembly processing with symbols as the granularity. If a new high priority data packet (i.e. Figure 7 The high-priority packet c) below the dotted line can then be assembled and sent. This pipelined approach to assembly is highly efficient, eliminating the need for any buffering at Layer 2 (L2), offering optimal performance in terms of chip power consumption and cost.

[0064] This packetization method poses a significant challenge to software processing. If 920 data packets are packaged, the software needs to process each packet in 300ns. Regarding the aforementioned pipeline operation, if the physical layer needs data at a certain moment, but Layer 2 is not ready, the system will experience an anomaly due to data interruption. Furthermore, 3GPP originally defined the MAC padding PDU as being packaged at the end of the MAC PDU, a drawback of which is low utilization. As mentioned above, the pipeline processing method lacks data buffering and is therefore less robust against system clock cycle (CPI) jitter. CPI jitter can be caused by busy system bus accesses or DDR refreshes, slowing down software instruction execution. However, CPI jitter is random and transient, meaning the system may experience a brief period of slowdown, preventing packet assembly from completing, only to resume normal processing shortly thereafter. However, during this brief period of slowdown, the system may use all remaining MAC PDU grants as padding, wasting significant air interface resources.

[0065] According to the embodiments of the present application, there is provided Figure 8 The process of the information sending method shown includes:

[0066] S801. The first device sends a MAC PDU for each of one or more carriers; wherein the MAC PDU for each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-category identification information or second-category identification information; wherein the first-category identification information is used to indicate that the MAC sub-PDU is generated when the data packetization of the data to be sent cannot be completed, and the second-category identification information is different from the first-category identification information.

[0067] According to the embodiments of the present application, there is provided Figure 9 The process of the information receiving method shown includes:

[0068] S901. The second device receives a MAC PDU of each carrier in one or more carriers; wherein the MAC PDU of each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-category identification information or second-category identification information; wherein the first-category identification information is used to indicate that the MAC sub-PDU is generated when the data packetization of the data to be sent cannot be completed, and the second-category identification information is different from the first-category identification information.

[0069] The aforementioned first device sending the MAC PDU of each carrier on each of the one or more carriers specifically refers to: the first device sending the MAC PDU of each carrier in the one or more carriers to the second device, wherein the MAC PDUs of different carriers are composed of different MAC sub-PDUs.

[0070] In the embodiment of the present application, the first device may be a terminal device or a network device; the second device may be a network device or a terminal device. The network device may specifically refer to an access network device, such as an eNB, gNB, base station, etc.

[0071] Optionally, the first device is a terminal device and the second device is a network device; in this scenario, the aforementioned one or more carriers are one or more carriers used to transmit uplink data; and the MAC PDU is specifically an uplink MAC PDU.

[0072] Optionally, the first device is a network device and the second device is a terminal device; in this scenario, the aforementioned one or more carriers are one or more carriers used to transmit downlink data; and the MAC PDU is specifically a downlink MAC PDU.

[0073] Optionally, the first device and the second device are both terminal devices. In this scenario, the first device and the second device are specifically two terminal devices for sidelink communication. The one or more carriers are one or more carriers used for sidelink communication; and the MAC PDU is a sidelink MAC PDU.

[0074] In some possible implementations, the number of the aforementioned one or more carriers is one.

[0075] In this embodiment, the one carrier is referred to as the first carrier. In this embodiment, the first device sends the MAC PDU of each carrier in the one or more carriers, specifically: the first device sends the MAC PDU of the first carrier to the second device.

[0076] Exemplarily, if the aforementioned first device is a terminal device and the second device is a network device; if in a carrier aggregation scenario, the first device can use multiple carriers but may only receive an uplink authorization for the first carrier, then the first device only sends the uplink MAC PDU of the first carrier. Alternatively, the first device is only configured to use a single carrier for uplink data transmission, then the first device only sends the uplink MAC PDU of the first carrier. In another example, the aforementioned first device is a terminal device and the second device is also a terminal device; the first device can only configure a single carrier for sidelink data transmission with the second device, then the first device sends the sidelink MAC PDU of the single carrier, i.e., the first carrier. In another example, the aforementioned first device is a network device and the second device is a terminal device; the first device and the second device can only use the first carrier for downlink data transmission, then the first device sends the downlink MAC PDU of the first carrier.

[0077] In the process of the first device generating the MAC PDU of the first carrier, specifically, the first device may generate each MAC sub-PDU of the first carrier.

[0078] Each MAC sub-PDU includes a MAC sub-header; the MAC sub-header includes a first information field, and the first information field carries first-type identification information or second-type identification information; wherein the first-type identification information is a reserved value corresponding to the first information field.

[0079] Optionally, the first information field is a logical channel identify (LCID) field. The length of the LCID field can be 5 bits, or can be longer or shorter, and this embodiment does not limit it. More specifically, the LCID field is used to carry identification information, and the identification information is used to indicate the type of data payload in the MAC sub-PDU. That is, the type of data payload in the MAC sub-PDU indicated by the aforementioned first type of identification information is different from the type of data payload in the MAC sub-PDU indicated by the second type of identification information.

[0080] The type of data payload in the MAC sub-PDU indicated by the first type of identification information is the padding bit generated when the data packetization of the data to be sent cannot be completed. The aforementioned first type of identification information may refer to the reserved value corresponding to the LCID field. It should be pointed out that the aforementioned padding bit is only an exemplary description. When actually defined or actually used, it can also be referred to as filling bits, padding bits, etc., and all possible names are not enumerated here. In a preferred example, the first type of identification information can be 33. It should be understood that this is only an exemplary description. As long as the first type of identification information is any one of the reserved values ​​of the LCID field specified in the relevant protocol, it is within the protection scope of this embodiment. The first type of identification information can also be expressed as or called a first type index (Index). The meaning represented by the first type index (Index), that is, the LCID value, can be shown in Table 1:

[0081] First-class index (Index) LCID value 33 Filling

[0082] Table 1

[0083] The second type of identification information is different from the aforementioned first type of identification information. The second type of identification information refers to the value of the LCID field specified in the relevant technology. It should also be pointed out that the second type of identification information does not have only one value. For example, when the second type of identification information is the value "00000" of the LCID field specified in the relevant technology, it is used to indicate that the data payload in the MAC sub-PDU is CCCH (Common Control Channel) information; for example, when the second type of identification information is any one of the values ​​11100, 11101, and 11110 of the LCID field specified in the relevant technology, it indicates that the data payload in the MAC sub-PDU is a buffer status report control information unit (BSR), which is specifically used to transmit the terminal's application for MAC layer memory resources to the base station. The values ​​of LCID specified in the relevant technology are not exhaustively enumerated here.

[0084] Optionally, the MAC sub-header further includes at least one of the following: a second information field, where the second information field is used to indicate the length of a third information field; and a third information field, where the third information field is used to indicate the length of the MAC sub-PDU excluding the MAC sub-header.

[0085] Specifically, the second information field may be an F field, and the length of the F field may be 1 bit. The third information field may be an L field, and the length of the L field may be 8 bits or 16 bits. The length of the L field is indicated by the F field. For example, if the bit value in the F field is 0, it indicates that the length of the L field is 8 bits. If the bit value in the F field is 1, it indicates that the length of the L field is 16 bits.

[0086] The L field is used to indicate the length of the MAC sub-PDU excluding the MAC sub-header, that is, the length of the data payload of the MAC sub-PDU. The length of the data payload of each MAC sub-PDU is related to the length of the data to be sent. For example, when the first information field (LCID field) of the MAC sub-header of the MAC sub-PDU carries the first type of identification information, the length of the third information field (i.e., the L field) is equal to the length of the data to be sent. For another example, when the first information field (LCID field) of the MAC sub-header of the MAC sub-PDU carries the second type of identification information, the length of the third information field (i.e., the L field) is also equal to the length of the data to be sent.

[0087] Optionally, the MAC sub-header may further include a fourth information field, which may specifically be an R (reserved) field, the R field including a reserved bit; the length of the reserved bit may be 1 bit. Exemplarily, the value of the reserved bit included in the R field is "0".

[0088] In combination with the above embodiment, in an exemplary description, the composition of the MAC sub-header of the MAC sub-PDU can be as follows: Figure 5 or Figure 6 As shown, it contains four information fields (or header data fields): LCID, L, F, and R.

[0089] The first device generates each MAC sub-PDU for each carrier respectively, including: when the first device cannot complete the data packetization of the data to be sent in the j-th time unit of the i-th carrier, the first device generates the j-th MAC sub-PDU of the i-th carrier; wherein the j-th MAC sub-PDU includes: a MAC sub-packet header and padding bits carrying the first type of identification information in the first information field; the i-th carrier is one of the one or more carriers; i is a positive integer, and j is a positive integer.

[0090] Since this embodiment only describes the scenario of one carrier, namely the first carrier, the aforementioned first device generates each MAC sub-PDU of each carrier respectively, including: when the first device is unable to complete the data packetization of the data to be sent in the j-th time unit of the first carrier, the first device generates the j-th MAC sub-PDU of the first carrier; wherein the j-th MAC sub-PDU includes: a MAC sub-packet header and padding bits carrying the first type of identification information in the first information field.

[0091] Here, the jth MAC sub-PDU is any one of the one or more MAC sub-PDUs included in the MAC PDU of the first carrier. That is, any MAC sub-PDU in the MAC PDU of the first carrier can be generated using the above method, but will not be described in detail.

[0092] The aforementioned time unit can be set according to actual conditions, for example, it can be any one of a time slot, a subframe, a symbol, etc.; more specifically, the time unit contains several time slots, or several subframes, or several symbols, which can also be set according to actual conditions. For example, a time unit can be set in advance to contain 1 symbol, or 1 time slot, or 2 symbols, etc., which are not exhaustive here.

[0093] Specifically, when the first device is unable to complete the data packetization of the data to be sent in the j-th time unit of the first carrier, the first device generates the j-th MAC sub-PDU of the first carrier, which may mean: when the MAC layer of the first device obtains the data to be sent in the j-th time unit of the first carrier, it determines whether the data packetization processing of the data to be sent in the j-th time unit can be completed before the specified time; if it cannot be completed, the first type of identification information is carried in the first information field of the MAC sub-packet header of the j-th MAC sub-PDU, and padding bits are added to the data payload part of the j-th MAC sub-PDU.

[0094] Since the processing of the MAC layer depends on the processing capability of the first device, the processing capability of the first device can be measured by the number of clock cycles (CPI) required to process each instruction. The processing capability of the first device may result in the MAC layer being unable to complete the packetization processing within the current time unit even though it knows that there is data to be sent. In this case, the first device can measure whether it can complete the packetization processing of the MAC sub-PDU of the current time unit based on its own processing capability in each time unit. The specified time may refer to the time from the moment the data to be sent of the j-th time unit of the first carrier is obtained to the time when it is delayed by one time unit. For example, the time unit is 1 symbol, that is, the first device can use symbols as the granularity for scheduling; after the MAC layer of the first device obtains the data to be sent of the first symbol, it determines whether the data packet processing of the data to be sent of the first symbol can be completed before the end of the second symbol; after the MAC layer of the first device obtains the data to be sent of the second symbol, it determines whether the data packet processing of the data to be sent of the second symbol can be completed before the end of the third symbol; this process is repeated until the processing of all MAC sub-PDUs of the MAC PDU is completed.

[0095] The data packet processing of the first device may be performed by software, and the software may be Logical Channel Prioritization (LCP) software.

[0096] The third information field of the MAC sub-header of the j-th MAC sub-PDU is used to indicate the length of the padding bits; the length of the padding bits is related to the length of the data to be sent in the j-th time unit.

[0097] That is to say, if the first information field of the MAC sub-header of the j-th MAC sub-PDU carries the first type of identification information, it means that the j-th MAC sub-PDU is generated when the data packetization of the data to be sent cannot be completed. At this time, the data payload carried by the j-th MAC sub-PDU is padding bits. The length of the padding bits carried by the j-th MAC sub-PDU may be related to the length of the data to be sent; specifically, the length of the padding bits carried by the j-th MAC sub-PDU is equal to the length of the data to be sent in the j-th time unit. The padding bits may be generated in the same way as the padding of the MAC padding PDU; or, they may be generated according to a preset rule, such as all 1s or all 0s, or 1s and 0s may be arranged in a certain preset rule, etc., all of which are within the protection scope of this embodiment.

[0098] The data to be transmitted in the jth time unit may be one of the following: the jth MAC SDU or the jth MAC CE. The jth MAC SDU is the jth Radio Link Control (RLC) PDU received by the MAC layer from the RLC layer. The RLC layer is the protocol layer above the MAC layer. This embodiment does not limit the method for obtaining the data to be transmitted in the jth time unit.

[0099] Although the aforementioned embodiment only illustrates the relevant descriptions of the first information field and the third information field of the j-th MAC sub-PDU, the j-th MAC sub-PDU may also include the second information field and / or the fourth information field, which are not repeated in this embodiment. The relevant descriptions of the second information field and the fourth information field are also not repeated.

[0100] Optionally, the method may further include: when the first device is able to complete data packetization of the data to be sent in the j-th time unit of the first carrier, the first device generates the j-th MAC sub-PDU of the first carrier; wherein the j-th MAC sub-PDU includes: a MAC sub-header carrying the second identification information in the first information field, and the data to be sent in the j-th time unit. The description of the second identification information, other content that the MAC sub-header can carry, and the data to be sent is the same as that in the previous embodiment, and therefore will not be repeated.

[0101] It should be understood that the MAC PDU of the first carrier may also include a MAC padding PDU. The MAC padding PDU can only be arranged as the last sub-PDU of the MAC PDU, and the padding length needs to be calculated by subtracting the valid length from the length of the entire MAC PDU. In addition, whether the MAC PDU exists and its length are implicitly defined based on the MAC subpacket length or TB size (for example, the length of the entire MAC PDU minus the valid data is the padding). The description of the MAC padding PDU is the same as that of the aforementioned embodiment and is not repeated here.

[0102] The above embodiment provides a detailed description of the manner in which the first device generates a MAC sub-PDU. It should also be understood that after the above first device generates a MAC sub-PDU, the physical layer of the first device can obtain the MAC sub-PDU and encode and send it out; the encoding processing of the physical layer can be performed by an encoder, which is not limited in this embodiment.

[0103] Combine Figure 10 、 Figure 11 , an exemplary description of the above implementation is given:

[0104] Assume that the first device is a network device and the second device is a terminal device; the first device sends a MAC PDU of the first carrier to the second device; the MAC PDU is specifically a downlink MAC PDU. The downlink MAC PDU includes one or more MAC sub-PDUs. The one or more MAC sub-PDUs include Figure 10 As shown: MAC sub-PDU1, which includes a MAC sub-header, which includes R and LCID fields, and the data payload of MAC sub-PDU1 is a fixed-length MACCE1; MAC sub-PDU2, which includes a MAC sub-header, which includes R, F, L, and LCID fields, and the data payload of MAC sub-PDU2 is a variable-length MAC CE2; MAC sub-PDU3, although Figure 10 It is not shown in the figure, but in one example, the MAC sub-PDU3 may include a MAC sub-header, which includes R, F, L, and LCID fields. The data payload of the MAC sub-PDU3 may be a MAC SDU; the MAC sub-PDU4 includes a MAC sub-header, which includes R, F, L, and LCID fields. Although Figure 10 Not shown in the figure, the LCID field carries the first type of identification information, and the data payload of the MAC sub-PDU4 is the filling bit; the MAC sub-PDU5 includes a MAC sub-header, and the MAC sub-header includes R, F, L, and LCID fields. The data payload of the MAC sub-PDU5 is a MAC SDU. Figure 10 The MAC padding sub-PDU at the end of the MAC PDU is also included. Figure 10 It is not shown in the figure, but the LCID fields of the aforementioned MAC sub-PDU1, 2, 3 and MAC sub-PDU5 all carry the second type of identification information. The difference is that the values ​​of the second type of identification information carried by MAC sub-PDU1, 2, 3, 5 can be the same or different, and they are not enumerated here.

[0105] Assume that the first device is a terminal device and the second device is a network device; the first device sends a MAC PDU of the first carrier to the second device; the MAC PDU is specifically an uplink MAC PDU. The uplink MAC PDU includes one or more MAC sub-PDUs. The one or more MAC sub-PDUs include Figure 11 As shown: MAC sub-PDU6, which includes a MAC sub-packet header, which includes four fields: R, F, L, and LCID. The data payload of MAC sub-PDU6 is MACSDU; MAC sub-PDU7, which includes a MAC sub-packet header, which includes four fields: R, F, L, and LCID. Although Figure 11Not shown in the figure, the LCID field carries the first type of identification information, and the data payload of the MAC sub-PDU7 is filling bits; the MAC sub-PDU8 includes a MAC sub-header, and the MAC sub-header includes R and LCID fields. The data payload of the MAC sub-PDU8 is a fixed-sized MAC CE3; the MAC sub-PDU9 includes a MAC sub-header, and the MAC sub-header includes four fields: R, F, L, and LCID. The data payload of the MAC sub-PDU9 is a variable-sized MAC CE4. Figure 11 The MAC padding sub-PDU at the end of the MAC PDU is also included. Figure 11 It is not shown in the figure, but the LCID fields of the aforementioned MAC sub-PDUs 6, 8, and 9 all carry the second type of identification information. The difference is that the values ​​of the second type of identification information carried by the MAC sub-PDUs 6, 8, and 9 can be the same or different, and they are not enumerated here.

[0106] In some possible implementations, the number of the aforementioned one or more carriers is multiple (two or more).

[0107] In the one or more carriers described in this embodiment, different MAC sub-PDUs of different carriers are generated alternately. Specifically, the one or more carriers are at least two carriers, that is, different MAC sub-PDUs of different carriers in the at least two carriers are generated alternately. Exemplarily, if the first device is a terminal device and the second device is a network device; if in a carrier aggregation scenario, the first device can use at least two carriers and may receive uplink authorizations of at least two carriers, then the first device sends the uplink MAC PDU of each carrier on the at least two carriers respectively. In another example, the first device is a terminal device and the second device is also a terminal device; the first device sends the sidelink MAC PDU of the at least two carriers. In another example, the first device is a network device and the second device is a terminal device; the first device and the second device can perform downlink data transmission on the at least two carriers, then the first device sends the downlink MAC PDU of the at least two carriers.

[0108] In the process of the first device generating a MAC PDU for each of the at least two carriers, specifically: the first device generates a MAC sub-PDU for the first carrier of the at least two carriers; then the first device determines whether there are any remaining carriers that have not been traversed this time; if so, it generates a MAC sub-PDU for the next carrier of the at least two carriers; then it again determines whether there are any remaining carriers that have not been traversed this time; if not, it starts processing the next MAC sub-PDU of the first carrier, and so on until all MAC sub-PDUs of all carriers are generated. When traversing the remaining carriers, the first device may sort the at least two carriers and determine the next carrier based on the sorting; or it may randomly select one of the remaining carriers as the next carrier, which is not limited in this embodiment. That is, each time the first device traverses the at least two carriers, it generates a MAC sub-PDU for each carrier in turn, and repeats this traversal multiple times until all MAC sub-PDUs of all carriers are generated.

[0109] For example, in a multi-CC (carrier component) scenario of CA (Carrier Aggregation), assuming there are two CCs, namely CC1 and CC2, the first device can use the LCP software to perform the following processing: when CC1 and CC2 both receive uplink authorization, generate one symbol of data of CC1 (TB1), that is, a MAC sub-PDU, and then switch to the authorization of CC2 to generate one symbol of data of CC2 (TB2), that is, a MAC sub-PDU, and repeat the above process until the MAC sub-PDUs of the two CCs are all generated.

[0110] Each MAC sub-PDU includes a MAC sub-header; the MAC sub-header includes a first information field, the first information field carries first-type identification information or second-type identification information; wherein the first-type identification information is a reserved value corresponding to the first information field. Optionally, the MAC sub-header also includes at least one of the following: a second information field, the second information field is used to indicate the length of the third information field; a third information field, the third information field is used to indicate the length of the MAC sub-PDU excluding the MAC sub-header. Optionally, the MAC sub-header may also include a fourth information field, the fourth information field may specifically be an R (reserved) field, the R field includes a reserved bit; the length of the reserved bit may be 1 bit. Exemplarily, the value of the reserved bit included in the R field is "0". The detailed description of the composition of the MAC sub-header of the MAC sub-PDU is the same as that in the aforementioned embodiment and will not be repeated here.

[0111] The first device generates each MAC sub-PDU for each carrier respectively, including: when the first device cannot complete the data packetization of the data to be sent in the j-th time unit of the i-th carrier, the first device generates the j-th MAC sub-PDU of the i-th carrier; wherein the j-th MAC sub-PDU includes: a MAC sub-packet header and padding bits carrying the first type of identification information in the first information field; the i-th carrier is one of the one or more carriers; i is a positive integer, and j is a positive integer.

[0112] Here, the i-th carrier can be any one of the at least two carriers mentioned above. How the MAC sub-PDUs of at least two carriers are alternately generated has been explained above. Next, only the process of generating a MAC sub-PDU for any one of the carriers will be explained. Since the process of generating a MAC sub-PDU for the remaining carriers of the at least two carriers is the same as that of the i-th carrier, they will not be described one by one. The j-th MAC sub-PDU is any one of the one or more MAC sub-PDUs contained in the MAC PDU of the i-th carrier; since any MAC sub-PDU in the MAC PDU of the i-th carrier can be generated in the above manner, they will not be described one by one.

[0113] Specifically, when the first device is unable to complete the data packetization of the data to be sent in the j-th time unit of the i-th carrier, the first device generates the j-th MAC sub-PDU of the i-th carrier, which may mean that: when the MAC layer of the first device obtains the data to be sent in the j-th time unit of the i-th carrier, it determines whether the data packetization processing of the data to be sent in the j-th time unit can be completed before the specified time; if it cannot be completed, the first type of identification information is carried in the first information field of the MAC sub-packet header of the j-th MAC sub-PDU of the i-th carrier, and padding bits are added to the data payload part of the j-th MAC sub-PDU. The data packetization processing of the first device can be performed by software, and the software can be LCP software.

[0114] The description of the MAC sub-header and padding bits of the j-th MAC sub-PDU is the same as that in the above embodiment and will not be repeated.

[0115] Optionally, the method may further include: when the first device is able to complete data packetization of the data to be sent in the jth time unit of the i-th carrier, the first device generates the j-th MAC sub-PDU of the i-th carrier; wherein the j-th MAC sub-PDU includes: a MAC sub-packet header carrying the second identification information in the first information field, and the data to be sent in the j-th time unit. The description of the second identification information, other content that the MAC sub-packet header can carry, and the data to be sent is the same as that in the above embodiment, and therefore will not be repeated.

[0116] It should be understood that the MAC PDU of the i-th carrier may also include a MAC padding PDU. The MAC padding PDU can only be arranged as the last sub-PDU of the MAC PDU, and the padding length needs to be calculated by subtracting the valid length from the length of the entire MAC PDU. In addition, whether the MAC PDU exists and its length are implicitly defined based on the MAC subpacket length or TB size (for example, the remainder of the valid data minus the length of the entire MAC PDU is the padding). The description of the MAC padding PDU is the same as that of the previous embodiment and is not repeated here.

[0117] The above embodiment provides a detailed description of the manner in which the first device generates different MAC sub-PDUs. It should also be understood that after the above first device generates each MAC sub-PDU for each carrier, the physical layer of the first device can obtain the MAC sub-PDU and encode and send it out; the encoding processing of the physical layer can be performed by an encoder, which is not limited in this embodiment.

[0118] In some possible implementations, when the kth MAC sub-PDU of the i-th carrier carries the first type of identification information, the second device discards the kth MAC sub-PDU of the i-th carrier. The i-th carrier is one of the one or more carriers; i is a positive integer, and k is a positive integer.

[0119] Here, the i-th carrier can be any one of the one or more carriers mentioned above. Since the processing of each carrier in the one or more carriers is the same as that of the i-th carrier, they are not described one by one. The k-th MAC sub-PDU is any one of the one or more MAC sub-PDUs contained in the MAC PDU of the i-th carrier; since the processing method of any MAC sub-PDU in the MAC PDU of the i-th carrier is the same as that of the k-th MAC sub-PDU, they are not described one by one.

[0120] Specifically, when the kth MAC sub-PDU of the i-th carrier carries the first type of identification information, the second device discards the kth MAC sub-PDU of the i-th carrier, which may mean that: when the MAC layer of the second device obtains the kth MAC sub-PDU of the i-th carrier, it parses the MAC sub-header of the k-th MAC sub-PDU; determines whether the identification information carried in the first information field of the MAC sub-header of the k-th MAC sub-PDU is the first type of identification information; if it is the first type of identification information, the MAC layer of the second device discards the k-th MAC sub-PDU.

[0121] Furthermore, the MAC layer of the second device discards the kth MAC sub-PDU, which may also include: the MAC layer of the second device parses the second information field and the third information field of the MAC sub-header of the kth MAC sub-PDU, determines the length of the data payload of the kth MAC sub-PDU and the length of the MAC sub-header, determines the total length of the kth MAC sub-PDU based on the length of the data payload of the kth MAC sub-PDU and the length of the MAC sub-header, and discards the kth MAC sub-PDU. The format of the MAC sub-header of the MAC sub-PDU carrying the first type of identification information and the method for determining the length of its padding bits are the same as those in the aforementioned embodiment and are not described in detail.

[0122] Optionally, the method may further include: when the k-th MAC sub-PDU of the i-th carrier carries the second type of identification information, the second device parses the k-th MAC sub-PDU of the i-th carrier. The description of the second type of identification information is the same as that in the aforementioned embodiment and is not repeated here. The parsing of the k-th MAC sub-PDU of the i-th carrier may be carried out in a manner specified in the relevant protocol and is not limited here.

[0123] It can be seen that by adopting the above solution, the first type of identification information can be used in one or more MAC sub-PDUs of the MAC PDU to indicate that the MAC sub-PDU is generated when the data packetization of the data to be sent cannot be completed. Therefore, the problem of data interruption caused by the inability to transmit data to the opposite device when the device's packetization capability is insufficient can be avoided. In addition, since the insufficient data packetization capability is usually a temporary situation, by adopting the solution provided by this embodiment, the problem of resource waste caused by filling the remaining authorized positions of the MAC PDU once the packetization cannot be completed normally can be avoided. Moreover, by adopting the above solution, the device can still provide the physical layer with MAC sub-PDUs for encoding processing when the packetization capability is insufficient, and the packetization processing capability of the device is also improved.

[0124] It should be noted that the above examples can be combined with various possibilities in the above-mentioned embodiments of the present application, which will not be described in detail here.

[0125] According to an embodiment of the present application, a first device is provided, such as Figure 12 As shown, the first device includes:

[0126] The first communication unit 1201 is used to send the media access control MAC protocol data unit PDU of each carrier in one or more carriers; wherein, the MAC PDU of each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-type identification information or second-type identification information; wherein, the first-type identification information is used to indicate that the MAC sub-PDU is generated when the data packetization of the data to be sent cannot be completed, and the second-type identification information is different from the first-type identification information.

[0127] Each MAC sub-PDU includes a MAC sub-header; the MAC sub-header includes a first information field, and the first information field carries first-type identification information or second-type identification information; wherein the first-type identification information is a reserved value corresponding to the first information field.

[0128] The first information field is a logical channel identifier LCID field.

[0129] The MAC sub-header further includes at least one of the following: a second information field, where the second information field is used to indicate the length of a third information field; and a third information field, where the third information field is used to indicate the length of the MAC sub-PDU excluding the MAC sub-header.

[0130] like Figure 13 As shown, the first device also includes: a first processing unit 1202, which is used to generate the jth MAC sub-PDU of the i-th carrier when the data packetization of the data to be sent in the j-th time unit of the i-th carrier cannot be completed; wherein, the j-th MAC sub-PDU includes: a MAC sub-packet header and padding bits carrying the first type of identification information in the first information field; the i-th carrier is one of the one or more carriers; i is a positive integer, and j is a positive integer.

[0131] The third information field of the MAC sub-header of the j-th MAC sub-PDU is used to indicate the length of the padding bits; the length of the padding bits is related to the length of the data to be sent in the j-th time unit.

[0132] Among the one or more carriers, different MAC sub-PDUs of different carriers are generated alternately.

[0133] The first device is a terminal device or a network device.

[0134] According to an embodiment of the present application, a second device is provided, such as Figure 14 Shown, including:

[0135] The second communication unit 1401 is used to receive the MAC PDU of each carrier in one or more carriers; wherein the MAC PDU of each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-category identification information or second-category identification information; wherein, the first-category identification information is used to indicate that the MAC sub-PDU is generated when the data packetization of the data to be sent cannot be completed, and the second-category identification information is different from the first-category identification information.

[0136] Each MAC sub-PDU includes a MAC sub-header; the MAC sub-header includes a first information field, and the first information field carries first-type identification information or second-type identification information; wherein the first-type identification information is a reserved value corresponding to the first information field.

[0137] The first information field is a logical channel identifier LCID field.

[0138] The MAC sub-header further includes at least one of the following: a second information field, where the second information field is used to indicate the length of a third information field; and a third information field, where the third information field is used to indicate the length of the MAC sub-PDU excluding the MAC sub-header.

[0139] like Figure 15 As shown, the second device also includes: a second processing unit 1402, which is used to discard the kth MAC sub-PDU of the i-th carrier when the k-th MAC sub-PDU of the i-th carrier carries the first type of identification information; the i-th carrier is one of the one or more carriers; i is a positive integer, and k is a positive integer.

[0140] The second device is a terminal device or a network device.

[0141] In the technical solution of this application, the acquisition, storage and application of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0142] Figure 16 1 is a schematic structural diagram of a communication device 1600 according to an embodiment of the present application. The communication device 1600 includes a processor 1610, which can call and run a computer program from a memory to enable the communication device 1600 to implement the method in the embodiment of the present application.

[0143] In one possible implementation, the communication device 1600 may further include a memory 1620. The processor 1610 may call and execute a computer program from the memory 1620 to enable the communication device 1600 to implement the method in the embodiment of the present application. The memory 1620 may be a separate device independent of the processor 1610 or may be integrated into the processor 1610.

[0144] In one possible implementation, the communication device 1600 may further include a transceiver 1630. The processor 1610 may control the transceiver 1630 to communicate with other devices. Specifically, the transceiver 1630 may send information or data to other devices or receive information or data sent by other devices. The transceiver 1630 may include a transmitter and a receiver. The transceiver 1630 may further include one or more antennas.

[0145] In one possible implementation, the communication device 1600 may be the first device of the embodiment of the present application, and the communication device 1600 may implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, no further description is given here. In one possible implementation, the communication device 1600 may be the second device of the embodiment of the present application, and the communication device 1600 may implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, no further description is given here.

[0146] Figure 17 17 is a schematic structural diagram of a chip 1700 according to an embodiment of the present application. The chip 1700 includes a processor 1710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0147] In one possible implementation, the chip 1700 may further include a memory 1720. The processor 1710 may call and execute a computer program from the memory 1720 to implement the method performed by the first device or electronic device in the embodiment of the present application. The memory 1720 may be a separate device independent of the processor 1710 or may be integrated into the processor 1710.

[0148] In a possible implementation, the chip 1700 may further include an input interface 1730. The processor 1710 may control the input interface 1730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0149] In a possible implementation, the chip 1700 may further include an output interface 1740. The processor 1710 may control the output interface 1740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0150] In one possible implementation, the chip can be applied to the first device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the first device in each method in the embodiments of the present application. For the sake of brevity, no further description is given here. In one possible implementation, the chip can be applied to the second device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the second device in each method in the embodiments of the present application. For the sake of brevity, no further description is given here.

[0151] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0152] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0153] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0154] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0155] Figure 18 FIG1 is a schematic block diagram of a communication system 1800 according to an embodiment of the present application. The communication system 1800 includes a first device 1810 and a second device 1820.

[0156] The first device 1810 can be used to implement the corresponding functions implemented by the first device in the above method, and the second device 1820 can be used to implement the corresponding functions implemented by the second device in the above method. For the sake of brevity, they are not described here in detail.

[0157] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state drive (SSD)).

[0158] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean 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 the present application.

[0159] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0160] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for sending information, characterized in that: The method comprises: The first device sends a medium access control MAC protocol data unit (PDU) for each of one or more carriers; wherein the MAC PDU for each carrier includes one or more MAC sub-PDUs; each of the one or more MAC sub-PDUs carries first-type identification information or second-type identification information; wherein the first-type identification information is used to indicate that the MAC sub-PDU is generated when data packetization of the data to be sent cannot be completed, and the second-type identification information is different from the first-type identification information; The method also includes: when the first device is unable to complete the data packetization of the data to be sent in the jth time unit of the i-th carrier, the first device generates the j-th MAC sub-PDU of the i-th carrier; wherein the j-th MAC sub-PDU includes: a MAC sub-packet header and padding bits carrying the first type of identification information in a first information field; the i-th carrier is one of the one or more carriers, and the j-th MAC sub-PDU is one of the one or more MAC sub-PDUs included in the MAC PDU of the i-th carrier; i is a positive integer, and j is a positive integer.

2. The method according to claim 1, characterized in that Each MAC sub-PDU includes a MAC sub-header; the MAC sub-header includes the first information field, and the first information field carries the first type of identification information or the second type of identification information; wherein the first type of identification information is a reserved value corresponding to the first information field.

3. The method according to claim 2, characterized in that The first information field is a logical channel identifier LCID field.

4. The method according to claim 3, characterized in that The MAC sub-packet header further includes at least one of the following: a second information field, where the second information field is used to indicate the length of the third information field; The third information field is used to indicate the length of the MAC sub-PDU excluding the MAC sub-header.

5. The method according to claim 4, characterized in that The third information field of the MAC sub-header of the j-th MAC sub-PDU is used to indicate the length of the padding bits; the length of the padding bits is related to the length of the data to be sent in the j-th time unit.

6. The method according to any one of claims 1 to 5, characterized in that Among the one or more carriers, different MAC sub-PDUs of different carriers are generated alternately.

7. The method according to claim 6, wherein: The first device is a terminal device or a network device.

8. A method for receiving information, characterized in that: The method comprises: The second device receives the MAC PDU of each carrier among one or more carriers; wherein the MAC PDU of each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-type identification information or second-type identification information; wherein the first-type identification information is used to indicate that the MAC sub-PDU is generated when data packetization of the data to be sent cannot be completed, and the second-type identification information is different from the first-type identification information, wherein the k-th MAC sub-PDU of the MAC PDU of the i-th carrier among the one or more carriers is generated by the first device when the data packetization of the data to be sent of the k-th time unit of the i-th carrier cannot be completed; wherein the k-th MAC sub-PDU includes: a MAC sub-packet header and padding bits carrying the first-type identification information in a first information field; i is a positive integer, and k is a positive integer.

9. The method according to claim 8, characterized in that Each MAC sub-PDU includes a MAC sub-header; the MAC sub-header includes the first information field, and the first information field carries the first type of identification information or the second type of identification information; wherein the first type of identification information is a reserved value corresponding to the first information field.

10. The method according to claim 9, characterized in that The first information field is a logical channel identifier LCID field.

11. The method according to claim 10, characterized in that The MAC sub-packet header further includes at least one of the following: a second information field, where the second information field is used to indicate the length of the third information field; The third information field is used to indicate the length of the MAC sub-PDU excluding the MAC sub-header.

12. The method according to any one of claims 8 to 11, characterized in that The method further comprises: When the kth MAC sub-PDU of the i-th carrier carries the first type of identification information, the second device discards the kth MAC sub-PDU of the i-th carrier; the i-th carrier is one of the one or more carriers.

13. The method according to claim 12, wherein: The second device is a terminal device or a network device.

14. A first device, characterized in that: The first device includes: a first communication unit, configured to transmit a medium access control MAC protocol data unit (PDU) for each of one or more carriers; wherein the MAC PDU for each carrier includes one or more MAC sub-PDUs; each of the one or more MAC sub-PDUs carries first-type identification information or second-type identification information; wherein the first-type identification information is used to indicate that the MAC sub-PDU is generated when data packetization of data to be transmitted cannot be completed, and the second-type identification information is different from the first-type identification information; A first processing unit is configured to generate a j-th MAC sub-PDU for the i-th carrier when data packetization of the data to be sent in the j-th time unit of the i-th carrier cannot be completed; wherein the j-th MAC sub-PDU includes: a MAC sub-packet header and padding bits carrying the first type of identification information in a first information field; the i-th carrier is one of the one or more carriers, and the j-th MAC sub-PDU is one of the one or more MAC sub-PDUs included in the MAC PDU of the i-th carrier; i is a positive integer, and j is a positive integer.

15. The first device according to claim 14, characterized in that Each MAC sub-PDU includes a MAC sub-header; the MAC sub-header includes the first information field, and the first information field carries the first type of identification information or the second type of identification information; wherein the first type of identification information is a reserved value corresponding to the first information field.

16. The first device according to claim 15, characterized in that The first information field is a logical channel identifier LCID field.

17. The first device according to claim 16, characterized in that The MAC sub-packet header further includes at least one of the following: a second information field, where the second information field is used to indicate the length of the third information field; The third information field is used to indicate the length of the MAC sub-PDU excluding the MAC sub-header.

18. The first device according to claim 17, characterized in that The third information field of the MAC sub-header of the j-th MAC sub-PDU is used to indicate the length of the padding bits; the length of the padding bits is related to the length of the data to be sent in the j-th time unit.

19. The first device according to any one of claims 14 to 18, characterized in that Among the one or more carriers, different MAC sub-PDUs of different carriers are generated alternately.

20. The first device according to claim 19, wherein The first device is a terminal device or a network device.

21. A second device, characterized in that: The second device includes: A second communication unit is used to receive a MAC PDU of each carrier among one or more carriers; wherein the MAC PDU of each carrier includes one or more MAC sub-PDUs; each MAC sub-PDU in the one or more MAC sub-PDUs carries first-type identification information or second-type identification information; wherein the first-type identification information is used to indicate that the MAC sub-PDU is generated when data packetization of the data to be sent cannot be completed, and the second-type identification information is different from the first-type identification information, wherein the k-th MAC sub-PDU of the MAC PDU of the i-th carrier among the one or more carriers is generated by the first device when the data packetization of the data to be sent of the k-th time unit of the i-th carrier cannot be completed; wherein the k-th MAC sub-PDU includes: a MAC sub-packet header and padding bits carrying the first-type identification information in a first information field; i is a positive integer, and k is a positive integer.

22. The second device according to claim 21, characterized in that Each MAC sub-PDU includes a MAC sub-header; the MAC sub-header includes the first information field, and the first information field carries the first type of identification information or the second type of identification information; wherein the first type of identification information is a reserved value corresponding to the first information field.

23. The second device according to claim 22, characterized in that The first information field is a logical channel identifier LCID field.

24. The second device according to claim 23, characterized in that The MAC sub-packet header further includes at least one of the following: a second information field, where the second information field is used to indicate the length of the third information field; The third information field is used to indicate the length of the MAC sub-PDU excluding the MAC sub-header.

25. The second device according to any one of claims 21 to 24, characterized in that: The second device further includes: The second processing unit is configured to discard the kth MAC sub-PDU of the i-th carrier by the second device when the kth MAC sub-PDU of the i-th carrier carries the first type of identification information; the i-th carrier is one of the one or more carriers.

26. The second device according to claim 25, wherein The second device is a terminal device or a network device.

27. A first device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the first device executes the method according to any one of claims 1 to 7.

28. A second device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so as to enable the second device to perform the method according to any one of claims 8 to 13.

29. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 7.

30. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 8 to 13.

31. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 7 or 8 to 13.

32. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 7 or 8 to 13.

Images