Information transmission method, apparatus, and storage medium

Abstract

Embodiments of the present disclosure relate to the technical field of communications, and provide an information transmission method, an apparatus, and a storage medium. The method is applied to a first node. The method comprises: receiving first control information, wherein the first control information is used for indicating an association relationship between a hybrid automatic repeat request (HARQ) entity and a physical shared channel set; and associating the HARQ entity with the physical shared channel set on the basis of the first control information.

Description

Information transmission method, device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on January 3, 2024, with application number 202410027333.7 and invention name “Information Transmission Method, Device and Storage Medium”. The entire contents of the Chinese patent application are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to the field of communication technologies, and in particular to an information transmission method, device, and storage medium. Background Art

[0004] In a communication system, different carriers are located in different hybrid automatic repeat request (HARQ) entities, and different HARQ entities cannot share data memory and perform cross-carrier data transmission. This makes the communication system unable to fully utilize carrier resources for data transmission, resulting in poor data transmission performance.

[0005] Summary of the Invention

[0006] The embodiments of the present disclosure provide an information transmission method, apparatus, and storage medium for improving resource utilization of carrier resources during data transmission.

[0007] In a first aspect, an information transmission method is provided, applied to a first node, the method comprising: receiving first control information, the first control information being used to indicate an association relationship between a hybrid automatic repeat request HARQ entity and a physical shared channel set; and associating the HARQ entity with the physical shared channel set based on the first control information.

[0008] In a second aspect, an information transmission method is provided, which is applied to a second node, and the method includes: associating a HARQ entity with a physical shared channel set; and sending first control information, where the first control information is used to indicate the association relationship between the HARQ entity and the physical shared channel set.

[0009] According to a third aspect, a communication device is provided, which is applied to a first node. The device includes: a receiving unit for receiving first control information, where the first control information is used to indicate an association relationship between a hybrid automatic repeat request HARQ entity and a physical shared channel set; and a processing unit for associating the HARQ entity with the physical shared channel set based on the first control information.

[0010] In a fourth aspect, a communication device is provided, which is applied to a second node, and the device includes: a processing unit, which is used to associate a HARQ entity with a physical shared channel set; and a sending unit, which is used to send first control information, and the first control information is used to indicate the association relationship between the HARQ entity and the physical shared channel set.

[0011] In a fifth aspect, a communication device is provided, comprising: a processor and a memory; the memory and the processor are coupled; the memory is used to store instructions executable by the processor, and the memory stores instructions executable by the processor; when the processor is configured to execute the instructions, the communication device implements the method provided in any one of the first or second aspects above.

[0012] In a sixth aspect, a computer-readable storage medium is provided, which stores computer instructions. When the computer instructions are executed on a computer, the computer executes the method provided in either the first aspect or the second aspect.

[0013] In a seventh aspect, a computer program product comprising computer instructions is provided, which, when executed on a computer, enables the computer to execute the method provided in either the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present invention and do not constitute a limitation to the technical solution of the present invention.

[0015] FIG1 is a schematic diagram of data mapping of a 5G system provided by related art;

[0016] FIG2 is another data mapping diagram of a 5G system provided by the related art;

[0017] FIG3 is another data mapping diagram of a 5G system provided by the related art;

[0018] FIG4 is a schematic structural diagram of a communication system provided by an embodiment of the present disclosure;

[0019] FIG5 is a flow chart of an information transmission method provided by an embodiment of the present disclosure;

[0020] FIG6 is a flow chart of another information transmission method provided by an embodiment of the present disclosure;

[0021] FIG7 is a schematic diagram of an association relationship between a HARQ entity, a physical shared channel set, and a transmission resource set provided by an embodiment of the present disclosure;

[0022] FIG8 is a schematic diagram of an association relationship among another HARQ entity, a physical shared channel set, and a transmission resource set provided by an embodiment of the present disclosure;

[0023] FIG9 is a schematic diagram of an association relationship between another HARQ entity, a physical shared channel set, and a transmission resource set provided by an embodiment of the present disclosure;

[0024] FIG10 is a schematic diagram of an association relationship between another HARQ entity, a physical shared channel set, and a transmission resource set provided by an embodiment of the present disclosure;

[0025] FIG11 is a schematic diagram of an association relationship between another HARQ entity, a physical shared channel set, and a transmission resource set provided by an embodiment of the present disclosure;

[0026] FIG12 is a schematic diagram of cross-carrier retransmission provided by an embodiment of the present disclosure;

[0027] FIG13 is a schematic diagram of another cross-carrier retransmission provided by an embodiment of the present disclosure;

[0028] FIG14 is a schematic diagram of another cross-carrier retransmission provided by an embodiment of the present disclosure;

[0029] FIG15 is a schematic diagram of association between a carrier and a physical shared channel provided by an embodiment of the present disclosure;

[0030] FIG16 is a schematic diagram of a transmission resource association of multiple DRBs multiplexing a HARQ entity according to an embodiment of the present disclosure;

[0031] FIG17 is a schematic diagram of transmission resource association in which multiple DRBs correspond to one HARQ entity, provided by an embodiment of the present disclosure;

[0032] FIG18 is a schematic diagram of transmission resource association in which one DRB corresponds to one HARQ entity, provided by an embodiment of the present disclosure;

[0033] FIG19 is a flow chart of another information transmission method provided by an embodiment of the present disclosure;

[0034] FIG20 is a flow chart of another information transmission method provided by an embodiment of the present disclosure;

[0035] FIG21 is a schematic diagram of the composition of a communication device provided in an embodiment of the present disclosure;

[0036] FIG22 is a schematic diagram of the composition of another communication device provided in an embodiment of the present disclosure;

[0037] FIG23 is a schematic structural diagram of a communication device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0038] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of the present disclosure.

[0039] Unless the context requires otherwise, throughout the specification and claims, the term "comprise" and its other forms, such as the third person singular form "comprises" and the present participle form "comprising", are to be interpreted as open and inclusive, that is, "including, but not limited to". In the description of the specification, the terms "one embodiment", "some embodiments", "exemplary embodiments", "example", "specific example" or "some examples" are intended to indicate that the particular features, structures, materials or characteristics associated with the embodiment or example are included in at least one embodiment or example of the present disclosure. The schematic representation of the above terms does not necessarily refer to the same embodiment or example. In addition, the particular features, structures, materials or characteristics may be included in any one or more embodiments or examples in any appropriate manner.

[0040] 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 the technical features being referred to. Thus, a feature identified as "first" or "second" may explicitly or implicitly include one or more of such features. Throughout this disclosure, unless otherwise specified, "plurality" means two or more.

[0041] In the embodiments of the present disclosure, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present disclosure should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0042] Additionally, the use of “based on” is meant to be open and inclusive, as a process, step, calculation, or other action “based on” one or more stated conditions or values ​​may, in practice, be based on additional conditions or values ​​beyond those stated.

[0043] With the advancement of wireless communication technology, wireless communication services are becoming increasingly diverse. In addition to the three classic scenarios of fifth-generation mobile networks (5G)—enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (uRLLC), and massive machine type communications (mMTC)—the future will also see the emergence of immersive cloud-based extended reality (XR), multi-dimensional holography, autonomous driving, and industrial internet services. The demand for an ultimate service experience will place even higher demands on networks. In particular, scenarios like XR and holographic communications must simultaneously meet the requirements of high throughput, low latency, and high reliability.

[0044] In the current 5G system, the medium access control (MAC) layer is responsible for scheduling and resource allocation, and uses the HARQ mechanism for data packet transmission and reliability assurance. The MAC entity includes a HARQ entity. Each HARQ entity corresponds to a serving cell, and a component carrier (CC) is bound to only one HARQ entity. Each HARQ entity manages multiple parallel HARQ processes, and data from different HARQ entities and different HARQ processes cannot be merged. The transport block (TB) is the basic unit of HARQ transmission at the physical layer. When there is no spatial multiplexing, one HARQ process corresponds to one TB. When there is spatial multiplexing, one HARQ process corresponds to one or more TBs. At the physical layer, the physical downlink shared channel (PDSCH) is used to transmit downlink TBs, and the physical uplink shared channel (PUSCH) is used to transmit uplink TB data. For 5G single-carrier transmission, as shown in Figure 1, each carrier corresponds to a HARQ entity, and uses one PDSCH for downlink data transmission and one PUSCH for uplink data transmission. For carrier aggregation (CA) transmission, multiple component carriers belong to different cells, each CC corresponds to a HARQ entity, and one HARQ entity corresponds to one PDSCH1 and one PUSCH1. CA has multiple cells and multiple HARQ entities. As shown in Figure 2, under CA, different CCs correspond to different HARQ entities, and each HARQ entity only manages its own HARQ buffer and the scheduling of one CC.

[0045] In order to improve uplink performance, 5G also adopts the supplementary uplink (SUL) method. For SUL transmission, there is a service cell and multiple HARQ entities. Each service cell has a downlink carrier (corresponding to one HARQ entity) and multiple uplink carriers (each uplink carrier corresponds to one HARQ entity, and multiple uplink carriers correspond to multiple HARQ entities), and corresponds to one PDSCH and multiple PUSCHs respectively. As shown in Figure 3, SUL ensures uplink coverage of user equipment (UE) by providing a supplementary uplink (generally in the low frequency band). The UE can dynamically select the transmission link between the normal UL link and the SUL link, but at the same time, the UE can only select one of them to send, and cannot send uplink data on two uplinks at the same time. The downlink (DL), UL and SUL belong to the same cell. Similarly, 5G also supports supplementary downlink (SDL) to improve downlink performance. SDL has one serving cell and multiple downlink carriers (corresponding to multiple HARQ entities) and one uplink carrier (corresponding to one HARQ entity), corresponding to multiple PDSCHs and one PUSCH respectively.

[0046] Due to multipath effects, path loss, channel fading, and interference in wireless environments, TB data may be lost or corrupted during transmission. To ensure data transmission efficiency while improving data reliability, the MAC layer uses the HARQ mechanism with fast retransmission. In this HARQ mechanism, the HARQ process is responsible for sending TB data through the physical layer. Each TB is assigned an available HARQ process, and each HARQ process has an independent HARQ buffer at the receiving end. With HARQ with soft combining, received erroneous packets are stored in a HARQ buffer and combined with subsequently received retransmitted packets to produce a more reliable data packet. If decoding of the combined packet fails, a retransmission and recombining request is requested. HARQ with soft combining is divided into two retransmission methods: append-on combining and incremental redundancy (IR), depending on whether the retransmitted bit information is identical to the original transmission (also called the initial transmission). The retransmitted bits in the append-and-combine method are identical to the original transmission, whereas the retransmitted bits in the IR method can differ from the original transmission. Multiple coded bit sets are generated in the IR, and each transmitted coded bit set becomes a redundant version (RV). Multiple retransmissions and soft combining of the received data increase the probability of successful TB decoding.

[0047] In 5G, each HARQ entity maintains its own HARQ cache. Different HARQ entities do not share HARQ caches, and the HARQ caches of different HARQ entities cannot directly access each other. Regardless of whether CA, SUL, or SDL are used, as long as different HARQ entities are used, cross-carrier HARQ information soft merging cannot be performed, which makes cross-carrier retransmission very difficult. For example, the UE has two carriers, high-frequency and low-frequency, to use, but data transmitted on the high-frequency carrier can only be retransmitted on the high-frequency carrier after failure. Even if the low-frequency carrier is idle, the data cannot be quickly transferred to the low-frequency carrier for retransmission. Due to the low success rate of high-frequency retransmission and the relatively large transmission delay, the data transmission performance is not high.

[0048] In summary, the related technologies cannot fully utilize carrier resources for efficient data transmission, resulting in poor data transmission performance. How to improve the resource utilization of carrier resources during data transmission is an urgent problem to be solved.

[0049] Based on this, the embodiments of the present disclosure provide an information transmission method, device and storage medium. The first node associates the HARQ entity with the physical shared channel set based on the first control information, so as to achieve flexible selection of the physical shared channel for data transmission under one HARQ entity, solve the problem of not supporting cross-carrier data transmission, improve the resource utilization of carrier resources during the data transmission process, and thus improve the data transmission performance.

[0050] The following describes the solutions of the embodiments of the present disclosure in conjunction with the accompanying drawings.

[0051] The technical solutions provided by the embodiments of the present disclosure can be applied to various mobile communication networks, for example, NR mobile communication networks using 5G, future mobile communication networks (such as 6G wireless communication systems) or multiple communication convergence systems, etc., and the embodiments of the present disclosure are not limited to this.

[0052] Figure 4 is a schematic diagram of the structure of a communication system provided by an embodiment of the present disclosure. As shown in Figure 4, the communication system includes, but is not limited to, a first node 110 and a second node 120. Specifically, the first node 110 and the second node 120 can transmit and receive wireless signals, and perform related interactions.

[0053] In a wireless communication scenario, a first node 110 and a second node 120 communicate via a wireless channel. For example, the first node 110 is a terminal and the second node 120 is a base station, and the terminal and the base station communicate via a wireless channel. In another example, the first node 110 is a terminal and the second node 120 is a wireless router, and the wireless router and the terminal communicate via a wireless channel. In another example, the first node 110 is a first base station and the second node 120 is a second base station, and the first base station and the second base station communicate via a wireless channel. In another example, the first node 110 is a first terminal and the second node 120 is a second terminal, and the first terminal and the second terminal communicate via a wireless channel. In another example, the first node 110 is a repeater and the second node 120 is a base station, and the base station and the repeater communicate via a wireless channel. In another example, the first node 110 is a terminal and the second node 120 is a repeater, and the repeater and the terminal communicate via a wireless channel. For another example, the first node 110 is a first relay, the second node 120 is a second relay, and the first relay and the second relay communicate via a wireless channel. For another example, the first node 110 is a base station, the second node 120 is a satellite, and the satellite and the base station communicate via a wireless channel. For another example, the first node 110 is a satellite, the second node 120 is a base station, and the base station and the satellite communicate via a wireless channel. For another example, the first node 110 is a terminal, the second node 120 is a satellite, and the satellite and the terminal communicate via a wireless channel. For another example, the first node 110 is a satellite, the second node 120 is a terminal, and the terminal and the satellite communicate via a wireless channel. For another example, the first node 110 is a ground device, the second node 120 is an aircraft, and the aircraft and the ground device communicate via a wireless channel. For another example, the first node 110 is a first aircraft, the second node 120 is a second aircraft, and the first aircraft and the second aircraft communicate via a wireless channel.

[0054] The "first" node, "second" node, "first" way, "second" way, "first" method, "second" method, "first" matrix, "second" matrix, "first" part, "second" part in this disclosure, unless otherwise specified, are only used to distinguish between the descriptions and do not represent the order of before and after or sequence.

[0055] In the embodiment of the present disclosure, the first node and the second node may also have other names. For example, the first node may also be called a first communication node, and the second node may also be called a second communication node, etc. The embodiment of the present disclosure does not limit this.

[0056] In some embodiments, the base station may be any of an evolution nodeB (eNB), a next generation nodeB (gNB), a transmission receive point (TRP), a transmission point (TP), and some other access node. Depending on the size of the service coverage area provided, base stations can be further divided into macro base stations for providing macro cells, micro base stations for providing pico cells, and femto base stations for providing femto cells. With the continuous evolution of wireless communication technology, future base stations may also adopt other names.

[0057] The terminal may be a device with wireless transceiver capabilities, such as a mobile phone, tablet computer, wearable device, vehicle-mounted device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc. The embodiments of the present disclosure do not limit the specific type of terminal.

[0058] It should be understood that FIG4 is an exemplary structural diagram, and the number of devices included in the communication system shown in FIG4 is not limited. For example, the number of first nodes and second nodes is not limited. Furthermore, in addition to the devices shown in FIG4 , the communication system shown in FIG4 may also include other devices, which is not limited.

[0059] Next, as shown in FIG5 , an embodiment of the present disclosure provides an information transmission method, which is applied to a first node, which may be the first node 110 shown in FIG4 . The method includes the following steps:

[0060] S101: Receive first control information.

[0061] In some embodiments, to improve carrier resource utilization during data transmission, after configuring the first control information, the second node may send the first control information to the first node. Accordingly, the first node receives the first control information sent by the second node. The first control information is used to indicate the association between a HARQ entity and a physical shared channel set. The second node may be the second node 120 shown in FIG. 4 . For ease of description, the following description uses the first node as a terminal and the second node as a base station to illustrate an information transmission method provided in an embodiment of the present disclosure.

[0062] In some embodiments, the first control information is used to indicate an association between a HARQ entity and a physical shared channel set, and specifically may be used to indicate an association between a HARQ entity of the first node and a physical shared channel set. The physical shared channel set may also be referred to by other names, such as a physical data channel list.

[0063] In some embodiments, the physical shared channel set includes at least one of the following: multiple PDSCHs, multiple PUSCHs.

[0064] In some embodiments, all physical shared channels in a physical shared channel set associated with a HARQ entity can share a HARQ buffer of the HARQ entity.

[0065] In some embodiments, a new transmission and a retransmission of the same data packet under a HARQ entity are respectively carried and transmitted on different physical shared channels in the physical shared channel set associated with the HARQ entity. The new transmission may also be called by other names, such as retransmission.

[0066] In some embodiments, the first control information includes at least one of the following: a HARQ entity identifier, a PDSCH identifier, a PUSCH identifier, a carrier identifier, an indication corresponding to the PDSCH identifier and the carrier identifier, an indication corresponding to the PUSCH identifier and the carrier identifier, a rule corresponding to the PDSCH identifier and the carrier identifier, and a rule corresponding to the PUSCH identifier and the carrier identifier.

[0067] In some embodiments, the first control information includes at least one of the following: a Radio Resource Control (RRC) message and downlink control information (DCI). The RRC message may be at least one of the following: an RRC connection establishment message, an RRC reconfiguration message, and an RRC forwarding message.

[0068] In some embodiments, the HARQ entity is any one of the following: a HARQ entity corresponding to a data radio bearer (DRB), a HARQ entity corresponding to multiple DRBs, and a HARQ entity corresponding to multiple DRBs after multiplexing at the MAC layer.

[0069] S102: Associating a HARQ entity with a physical shared channel set based on the first control information.

[0070] In some embodiments, after receiving the first control information, the first node can associate a HARQ entity of the first node with multiple physical shared channels in the physical shared channel set based on the first control information, that is, establish an association relationship between a HARQ entity of the first node and multiple physical shared channels in the physical shared channel set.

[0071] As an example, taking the first control information as an RRC message, the first node associates a HARQ entity of the first node with a physical shared channel set based on the RRC message. Taking the first control information as an RRC reconfiguration message in the RRC message as an example, the RRC reconfiguration message indicates the specific association relationship between a HARQ entity of the first node and the physical shared channel set. The first node can associate the HARQ entity with the physical shared channel set based on the specific association relationship between the HARQ entity and the physical shared channel set. For example, the RRC reconfiguration message includes indication information of two pairs of physical shared channels (PDSCH1, PUSCH1) (PDSCH2, PUSCH2) associated with HARQ entity 1. For another example, the RRC reconfiguration message includes indication information of HARQ entity 1 associating a pair of conventional transmission links (PDSCH1, PUSCH1) and a supplementary transmission link (PUSCH2).

[0072] As another example, taking the first control information as an RRC message, the RRC message (e.g., an RRC connection establishment message) may enable the first node to associate or disassociate a HARQ entity with a physical shared channel set. The first node may associate a HARQ entity of the first node with the physical shared channel set by receiving the RRC message. The first node may disassociate a HARQ entity of the first node with the physical shared channel set by receiving the RRC message.

[0073] As another example, taking the first control information as DCI, the DCI enables the first node to dynamically associate and disassociate a HARQ entity with a physical shared channel set in real time. The first node can associate a HARQ entity of the first node with the physical shared channel set by receiving the DCI. The first node can also disassociate a HARQ entity of the first node from the physical shared channel set by receiving the DCI.

[0074] Based on the embodiment shown in Figure 5, the first node associates the HARQ entity with the physical shared channel set based on the first control information, thereby achieving flexible selection of the physical shared channel for data transmission under one HARQ entity, solving the problem of not supporting cross-carrier data transmission, and improving the resource utilization of carrier resources during data transmission, thereby improving data transmission performance.

[0075] In some embodiments, as shown in FIG6 , the method may further include the following steps:

[0076] S201: Receive second control information.

[0077] The second control information is used to indicate a correspondence between physical shared channels in the physical shared channel set and transmission resources in the transmission resource set.

[0078] In some embodiments, a transmission resource set includes multiple transmission resources, each of which includes at least one of the following: a carrier, a bandwidth part (BWP), a cell, a beam, or a transmit / receive point (TRP). The transmission resource set may also be referred to by other names, such as a service resource list.

[0079] In some embodiments, the transmission resource set includes at least one of the following: a carrier set, a BWP set, a cell set, a beam set, and a TRP set, wherein the number of carriers included in the carrier set is greater than 1, the BWP set includes multiple BWPs located at different carriers, and the beam set includes multiple spatial beams belonging to different carriers.

[0080] In some embodiments, the second control information includes indication information of a physical shared channel to a transmission resource. The second control information includes at least one of the following: a HARQ entity identifier, a PDSCH identifier, a PUSCH identifier, a transmission resource identifier, an indication of correspondence between the PDSCH identifier and the transmission resource identifier, an indication of correspondence between the PUSCH identifier and the transmission resource identifier, a rule for correspondence between the PDSCH identifier and the transmission resource identifier, and a rule for correspondence between the PUSCH identifier and the transmission resource identifier.

[0081] In some embodiments, the second control information includes at least one of the following: an RRC message, a DCI, wherein the RRC message may be at least one of the following: an RRC connection establishment message, an RRC reconfiguration message, and an RRC forwarding message.

[0082] As another example, taking the second control information as an RRC message, the RRC message can enable the first node to dynamically associate and disassociate the physical shared channel set with the transmission resource set in real time. The first node can associate the first node's physical shared channel set with the transmission resource set by receiving the RRC message. The first node can disassociate the first node's physical shared channel set with the transmission resource set by receiving the RRC message.

[0083] As another example, taking the second control information as DCI, the DCI enables the first node to dynamically associate and disassociate a physical shared channel set with a transmission resource set in real time. The first node can associate the first node's physical shared channel set with the transmission resource set by receiving the DCI. The first node can disassociate the first node's physical shared channel set with the transmission resource set by receiving the DCI.

[0084] S202: Determine a transmission resource set corresponding to a physical shared channel set based on the second control information.

[0085] In some embodiments, when the first node associates the HARQ entity with the physical shared channel set based on the first control information, after receiving the second control information, the first node can determine the transmission resource set corresponding to the physical shared channel set based on the second control information, that is, determine the association relationship between the physical shared channel set and the transmission resource set.

[0086] In some embodiments, when the first node determines the transmission resource set corresponding to the physical shared channel set based on the second control information, after receiving the first control information, the first node can determine the association between the HARQ entity and the physical shared channel set based on the first control information.

[0087] In some embodiments, the first node associates the HARQ entity with the transmission resource when the first node associates the HARQ entity with the physical shared channel set based on the first control information and determines the transmission resource set corresponding to the physical shared channel set based on the second control information.

[0088] In some embodiments, the first control information and the second control information are two independent control signaling messages, and the first node receives the first control information and the second control information separately. For example, the first control information and the second control information are two RRC messages. For another example, the first control information and the second control information are two DCI messages. For another example, the first control information is an RRC message, and the second control information is a DCI message. For another example, the first control information is a DCI message, and the second control information is an RRC message.

[0089] In some embodiments, the first control information and the second control information correspond to a control signaling message, and the first node receives a control signaling message including the first control information and the second control information. For example, the first control information and the second control information belong to a RRC message. For another example, the first control information and the second control information belong to a DCI message.

[0090] It should be understood that after the first node determines the transmission resource set corresponding to the physical shared channel set, the physical shared channels in the physical shared channel set can use the transmission resources included in the transmission resource set. For example, the transmission resource set includes carrier resources. After determining the transmission resource set corresponding to the physical shared channel set, the first node can know which carrier resources each physical shared channel is carried on, thereby achieving flexible selection of physical shared channels and transmission resources for data transmission under a HARQ entity, improving the resource utilization of carrier resources during data transmission, and thus improving data transmission performance.

[0091] Take the example that the physical shared channel set includes m PDSCHs and n PUSCHs, and the transmission resource set includes k carriers, that is, in the embodiment of the present disclosure, m PDSCHs and n PUSCHs under one HARQ entity correspond to k carriers. Among them, m and n can both be integers greater than or equal to 0, and m and n are not 0 at the same time, and k is a positive integer. It should be understood that when the first node associates the HARQ entity with the physical shared channel set, and associates the HARQ entity with the transmission resource set, the first node can know which carrier of the k carriers is used by each physical shared channel in the m PDSCHs and n PUSCHs under one HARQ entity. As shown in Figure 7, a schematic diagram of the association relationship between a HARQ entity, a physical shared channel set and a transmission resource set is provided in an embodiment of the present disclosure. Referring to Figure 7, the physical shared channel set includes PDSCH1-PDSCH m and PUSCH1-PUSCH n , the carrier is a component carrier (CC), and the transmission resource set includes CC1-CC k For example, the association relationship between the HARQ entity, the physical shared channel set and the transmission resource set can be HARQ entity 1 associated with PDSCH1-PDSCH m and PUSCH1-PUSCH n , PDSCH1-PDSCH m and PUSCH1-PUSCH n Associate CC1-CC k .

[0092] The following examples illustrate the association relationship between a HARQ entity, a physical shared channel set, and a transmission resource set. For example, taking the physical shared channel set as including m PDSCHs and n PUSCHs, and the transmission resource being a carrier, the HARQ entity is associated with the physical shared channel set, that is, one HARQ entity is associated with m PDSCHs and n PUSCHs. The m PDSCHs can be transmitted using less than or equal to m different carriers. The n PUSCHs can be transmitted using less than or equal to n different carriers. In some embodiments, the m PDSCHs can be transmitted using the same carrier or different carriers. The n PUSCHs can be transmitted using the same carrier or different carriers. In some embodiments, each PDSCH and each PUSCH can be transmitted using the same carrier or different carriers. In other embodiments, each PDSCH and each PUSCH can be transmitted using the same carrier or different carriers. In other words, by associating a HARQ entity with the physical shared channel and the transmission resource set, a HARQ entity can form a corresponding combination with any physical shared channel in the physical shared channel set and any transmission resource in the transmission resource set.

[0093] When m is equal to 0 and n is greater than 0, downlink (DL only) data transmission is performed, that is, the HARQ entity is only associated with one or more PDSCH channels and is not associated with a PUSCH channel.

[0094] When m is greater than 0 and n is equal to 0, UL-only data transmission is formed, that is, the HARQ entity is only associated with one or more PUSCH channels and is not associated with the PDSCH channel.

[0095] When m is equal to 1 and n is greater than 1, it indicates that the HARQ entity is simultaneously associated with one PDSCH channel and multiple PUSCH channels. For example, FIG8 is a schematic diagram of the association relationship between another HARQ entity, a physical shared channel set, and a transmission resource set provided in an embodiment of the present disclosure. Referring to FIG8 , when one physical shared channel corresponds to one carrier, the situation is similar to 5G SUL transmission, but the difference is that only one HARQ entity is used here.

[0096] When m is greater than 1 and n is equal to 1, it means that the HARQ entity is associated with multiple PDSCH channels and one PUSCH channel at the same time. When one physical shared channel corresponds to one carrier, this situation is similar to 5G SDL transmission, but the difference is that only one HARQ entity is used here.

[0097] When m is greater than 1 and n is greater than 1, it indicates that the HARQ entity is simultaneously associated with multiple PDSCH channels and multiple PUSCH channels. For example, FIG9 is a schematic diagram of the association relationship between another HARQ entity, a physical shared channel set, and a transmission resource set provided in an embodiment of the present disclosure. Referring to FIG9 , when the HARQ entity is simultaneously associated with multiple PDSCH channels and multiple PUSCH channels, the situation is similar to 5G CA transmission, but the difference is that only one HARQ entity is used here.

[0098] It should be understood that when one HARQ entity is associated with one physical shared channel set, the flexibility of data transmission can be improved.

[0099] As an example, when a HARQ entity is associated with a physical shared channel set and the corresponding transmission resource set is determined, the same TB of data can be retransmitted across carriers. If the TB of data fails to be transmitted on one carrier, the retransmission success rate may be low if the data is retransmitted on the same carrier. In this way, the retransmission of the failed TB of data can be transferred to another carrier of the same HARQ entity. At the receiving end, a HARQ buffer can be used and soft combining of information can be performed to improve the decoding success rate.

[0100] As another example, when a HARQ entity is associated with a physical shared channel set and the transmission resource set corresponding to the physical shared channel set is determined, since the physical shared channel set uses the same HARQ entity, flexible offloading of a data stream at the physical layer can be supported. For example, different TBs of data in the same data stream can be transmitted on different physical shared channels or on different carriers.

[0101] In some embodiments, the second control information includes at least one of the following: an RRC message, a DCI. Taking the second control information as an RRC message (e.g., an RRC reconfiguration message) as an example, the first node determines the transmission resource set corresponding to the physical shared channel set based on the second control information. It can be that the first node obtains the transmission resource corresponding to each physical shared channel in the physical shared channel set based on the RRC message. For example, PDSCH1 and PDSCH1 both correspond to carrier 1 (CC1), and PDSCH2 and PDSCH2 both correspond to carrier 2 (CC2). Taking the second control information as DCI as an example, the first node determines the transmission resource set corresponding to the physical shared channel set based on the second control information. It can be that the first node performs the correspondence between the physical shared channels in the physical shared channel set and the transmission resources in the transmission resource set based on DCI. It should be understood that DCI enables the first node to dynamically establish and release the correspondence between the physical shared channel set and the transmission resource set in real time.

[0102] In some embodiments, after the first node associates the HARQ entity with the physical shared channel set based on the first control information, or after the first node determines the transmission resource set corresponding to the physical shared channel set based on the second control information, the first node can associate the HARQ entity with the transmission resource set, that is, establish an association relationship between the HARQ entity and the transmission resource set.

[0103] As a possible example, the first node associates the HARQ entity with a physical shared channel set and associates the HARQ entity with a transmission resource set, which may be a MAC entity of the first node associating the HARQ entity with a physical shared channel set and associating the HARQ entity with a transmission resource set.

[0104] For example, taking the transmission resource as a carrier as an example, assuming that a HARQ entity is associated with two pairs of uplink and downlink physical shared channels (PDSCH1, PUSCH1) and (PDSCH2, PUSCH2), and (PDSCH1, PUSCH1) corresponds to carrier 1, and (PDSCH2, PUSCH2) corresponds to carrier 2. Continuing to refer to the above Figure 9, it can be seen that HARQ entity 1 can also correspond to carrier 1 (CC1) and carrier 2 (CC2), that is, HARQ entity 1 is also associated with CC1 and CC2.

[0105] For another example, taking the transmission resource as a cell, the transmission resource set includes multiple logical cells, then one HARQ entity can correspond to multiple logical cells, wherein the multiple logical cells can be multiple logical cells corresponding to different carriers. For example, as shown in FIG10 , another schematic diagram of the association relationship between a HARQ entity, a physical shared channel set, and a transmission resource set provided in an embodiment of the present disclosure is shown. Referring to FIG10 , HARQ entity 1 can be associated with (PDSCH1, PUSCH1) and (PDSCH2, PUSCH2), (PDSCH1, PUSCH1) is associated with cell 1 (Cell1), and (PDSCH2, PUSCH2) is associated with cell 2 (Cell2), then HARQ entity 1 can be associated with Cell1 and Cell2.

[0106] For another example, taking a transmission resource as a BWP, if the transmission resource set includes multiple BWPs, then one HARQ entity can correspond to multiple BWPs, wherein the multiple BWPs can be located on different carriers. For example, as shown in FIG11 , another schematic diagram of the association relationship between a HARQ entity, a physical shared channel set, and a transmission resource set provided in an embodiment of the present disclosure is provided. Referring to FIG11 , HARQ entity 1 can be associated with (PDSCH1, PUSCH1) and (PDSCH2, PUSCH2), (PDSCH1, PUSCH1) is associated with BWP1, and (PDSCH2, PUSCH2) is associated with BWP2. Thus, HARQ entity 1 can be associated with both BWP1 and BWP2. BWP1 and BWP2 can be located on different carriers. In some embodiments, BWP1 and BWP2 are the two activated BWPs corresponding to HARQ entity 1. It should be understood that since there are two activated BWPs under one HARQ entity, it can support multiple data transmission modes such as simultaneous transmission of the same data packet on different BWPs, simultaneous transmission of different data packets under the same data stream on different BWPs, new transmission of the same data packet on one BWP and retransmission on another BWP.

[0107] In some embodiments, when the first node associates the HARQ entity with a physical shared channel set and associates the HARQ entity with a transmission resource set, all transmission resources in the transmission resource set associated with the HARQ entity can be used to transmit data in the HARQ buffer of the HARQ entity.

[0108] In some embodiments, when the first node associates the HARQ entity with a physical shared channel set and associates the HARQ entity with a transmission resource set, the new transmission and retransmission of the same data packet under the HARQ entity are respectively carried on different transmission resources in the transmission resource set associated with the HARQ entity.

[0109] It should be understood that high-frequency carriers can use large bandwidth for high-throughput transmission, but they also have the disadvantages of short propagation distance, susceptibility to interference, and easy obstruction, which results in a low retransmission success rate on high-frequency carriers. Low-frequency carriers have a wide coverage area, strong penetration, and strong anti-interference capabilities, resulting in a high data transmission success rate, but low-frequency carriers have a small bandwidth and cannot support high-speed data transmission. If the new transmission of data packets is placed on the high-frequency carrier and the retransmission of data packets is placed on the low-frequency carrier, both high-speed data transmission and retransmission success rate can be achieved. As can be seen, this approach is beneficial for scenarios with high throughput and high reliability.

[0110] As an example, taking the data packet as TB data as an example, as shown in Figure 12, a cross-carrier retransmission schematic diagram provided by an embodiment of the present disclosure is shown. Referring to Figure 12, under the same HARQ entity, PDSCH1 uses a high-frequency carrier and PDSCH2 uses a low-frequency carrier. When TB data transmission fails in PDSCH1 on the high-frequency carrier, the retransmission of the failed TB data can be placed on PDSCH2 to use the low-frequency carrier for transmission. Since PDSCH1 and PDSCH2 use the same HARQ entity, the data transmitted on the two channels at the receiving end can be soft-merged to improve the decoding success rate. Moreover, since PDSCH1 and PDSCH2 use the same HARQ entity, the HARQ buffers corresponding to PDSCH1 and PDSCH2 are also the same, and the retransmission of the failed TB data can be the same RV version or different RV versions of the TB data. In other words, since PDSCH1 and PDSCH2 use the same HARQ entity, multiple physical downlink shared channels can share the downlink HARQ buffer for bit soft merging.

[0111] In some embodiments, an RRC message may be used to configure the association between an HARQ entity and a physical shared channel set, as well as the correspondence between each physical shared channel in the physical shared channel set and a carrier. For example, an RRC message may be used to configure the association between HARQ entity 1 and PDSCH 1 and PDSCH 2, as well as the correspondence between PDSCH 1 and a high-frequency carrier and PDSCH 2 and a low-frequency carrier.

[0112] As another example, for each physical shared channel in the set of physical shared channels associated with the HARQ entity, the physical shared channel can use a high-frequency carrier and a low-frequency carrier for data transmission in different time slots. For example, taking the physical shared channel as PDSCH1 and the data packet as TB data as an example, as shown in FIG13, another cross-carrier retransmission schematic diagram provided by an embodiment of the present disclosure is shown in FIG13. For PDSCH1 associated with HARQ entity 1, PDSCH1 can use a high-frequency carrier and a low-frequency carrier for data transmission in different time slots. When PDSCH1 fails to transmit a TB using a high-frequency carrier in a HARQ process, the failed TB can be placed on the HARQ process corresponding to the retransmission of PDSCH1 and retransmitted using a low-frequency carrier. Alternatively, as shown in FIG14, another cross-carrier retransmission schematic diagram provided by an embodiment of the present disclosure is shown in FIG14. For PDSCH1 associated with HARQ entity 1, when a TB transmission fails when PDSCH1 uses CC1, multiple RV versions of the failed TB can be placed on multiple CCs for retransmission. For example, the same RV version is transmitted on CC2 and CC3, or different RV versions are transmitted on CC2 and CC3.

[0113] In some embodiments, in order to improve the transmission performance of uplink transmission, the first node may perform cross-carrier retransmission of uplink transmission. Among them, the cross-carrier retransmission of uplink transmission by the first node may also use the correspondence between the physical shared channel and the transmission resource shown in Figures 12 to 14 above to perform cross-carrier retransmission. It should be understood that placing the new transmission of the data packet on a high-frequency carrier can utilize the sufficient bandwidth resources of the high-frequency carrier for high-speed transmission of the data packet; and placing the retransmission of the data packet on a low-frequency carrier can utilize the advantages of the low-frequency carrier's small path loss and strong anti-interference ability to improve the reliability of data transmission.

[0114] In some embodiments, when the first node associates the HARQ entity with a physical shared channel set, and associates the HARQ entity with a transmission resource set, an information transmission method provided by an embodiment of the present disclosure not only supports the transmission of multiple physical shared channels under one HARQ entity on different transmission resources, but also supports the transmission of multiple physical shared channels under one HARQ entity on the same transmission resource. For example, taking the example that the physical shared channel set includes 2 PDSCHs (PDSCH1 and PDSCH2) and the transmission resource set includes 1 carrier (CC1), as shown in Figure 15, a schematic diagram of the association between a carrier and a physical shared channel provided by an embodiment of the present disclosure, referring to Figure 15, indicates that 2 PDSCHs under one HARQ entity 1 are both transmitted on 1 carrier. In other words, the first node can perform data transmission on two downlinks at the same time. For high-throughput services such as XR, the data transmission rate can be improved by using the large bandwidth resources on a carrier to transmit multiple physical shared channels at the same time. For another example, taking the physical shared channel set including 2 PUSCHs and the transmission resource set including 1 carrier as an example, it means that the 2 PUSCHs under one HARQ entity are transmitted on 1 carrier, that is, the first node can simultaneously perform data transmission on two uplinks.

[0115] In some embodiments, when the first node associates the HARQ entity with a physical shared channel set and associates the HARQ entity with a transmission resource set, the uplink data and downlink data under the HARQ entity are respectively transmitted using different transmission resources in the transmission resource set associated with the HARQ entity; or, the uplink data and downlink data under the HARQ entity are respectively transmitted using the same transmission resource in the transmission resource set associated with the HARQ entity. Taking the example of the uplink data and downlink data under the HARQ entity being respectively transmitted using different transmission resources in the transmission resource set associated with the HARQ entity, as an example, the identifier of the transmission resource used by the uplink data is different from the identifier of the transmission resource used by the downlink data; and / or the number of transmission resources used by the uplink data is different from the number of transmission resources used by the downlink data. For example, taking the transmission resource as a carrier as an example, for uplink data, one HARQ entity can use 4 carriers for transmission, and for downlink data, one HARQ entity can use 1 carrier for transmission.

[0116] In some embodiments, different HARQ processes under a HARQ entity use different physical shared channels or different transmission resources. For example, among the multiple HARQ processes of HARQ entity 1, some HARQ processes use PDSCH1, and some HARQ processes use PDSCH2. For example, among the multiple HARQ processes of HARQ entity 1, some HARQ processes use carrier 1 and carrier 2, and some HARQ processes use carrier 2 and carrier 3. For example, among the multiple HARQ processes of HARQ entity 1, some HARQ processes use BWP1 and BWP2, and some HARQ processes use BWP2 and BWP3. For example, among the multiple HARQ processes of HARQ entity 1, some HARQ processes use beam 1, and some HARQ processes use beam 2. For example, among the multiple HARQ processes of HARQ entity 1, some HARQ processes are data transmissions belonging to cell 1, and some HARQ processes are data transmissions belonging to cell 2. That is to say, for the same HARQ entity, the same data packet can be initially transmitted and retransmitted on different transmission resources, and support soft merging of the decoded information of the initial transmission and retransmission in the same HARQ buffer.

[0117] In some embodiments, DRBs correspond to HARQ entities using different transmission resources. In 5G, the MAC layer multiplexes data from multiple DRBs together and provides it to a HARQ entity. This method cannot distinguish data from different DRBs at the physical layer, making it difficult for services to be differentiated at the physical layer. In the embodiment of the present disclosure, it is proposed to correspond one DRB to one HARQ entity, and to achieve cross-carrier transmission of data of one DRB by associating the HARQ entity with a physical shared channel set and by associating the physical shared channel set with a transmission resource set. For example, for low-speed data services, multiple DRBs are used to correspond to one HARQ entity; for high-speed data services, one DRB is used to correspond to one HARQ entity. Regardless of the correspondence method between DRBs and HARQ entities, the association between the HARQ entity and the physical shared channel set and the correspondence between the physical shared channel set and the transmission resource set can be used to perform data transmission across transmission resources (such as cross-carrier retransmission). Taking the transmission resource as a carrier as an example, Figure 16 shows a schematic diagram of the transmission resource association of multiple DRBs multiplexing a HARQ entity, and Figure 17 shows a schematic diagram of the transmission resource association under which multiple DRBs correspond to one HARQ entity. FIG18 is a schematic diagram showing the association of transmission resources under which one DRB corresponds to one HARQ entity.

[0118] Based on the embodiment shown in FIG6 , after the first node determines the transmission resource set corresponding to the physical shared channel set, all physical shared channels in the physical shared channel set can use the transmission resources included in the transmission resource set. The first node can determine which transmission resources each physical shared channel is carried on, thereby achieving flexible selection of physical shared channels and transmission resources for data transmission within a HARQ entity, improving carrier resource utilization during data transmission and thereby enhancing data transmission performance.

[0119] In some embodiments, as shown in FIG19 , an embodiment of the present disclosure further provides an information transmission method, which is applied to a second node. The second node may be the second node 120 shown in FIG4 . The method may include the following steps:

[0120] S301: Associate a HARQ entity with a physical shared channel set.

[0121] In some embodiments, to improve carrier resource utilization during data transmission, the second node may associate a HARQ entity with a physical shared channel set. The second node associating the HARQ entity with the physical shared channel set may involve the second node associating a HARQ entity of the first node with the physical shared channel set, i.e., the second node establishing an association between a HARQ entity of the first node and the physical shared channel set. For the description of the HARQ entity and the physical shared channel set, reference may be made to the corresponding description in the embodiment shown in FIG. 5 above, and is not further elaborated here.

[0122] S302: Send first control information.

[0123] The first control information is used to indicate an association relationship between a HARQ entity and a physical shared channel set.

[0124] In some embodiments, the first control information includes at least one of the following: an RRC message, a DCI, wherein the RRC message may be at least one of the following: an RRC establishment message, an RRC reconfiguration message, and an RRC forwarding message.

[0125] For the description of the first control information, reference may be made to the corresponding description in the embodiment shown in FIG5 , which will not be repeated here.

[0126] It should be understood that after the second node associates a HARQ entity with a physical shared channel set, it sends first control information to the first node, so that the first node associates the HARQ entity with the physical shared channel set based on the first control information, thereby achieving flexible selection of the physical shared channel for data transmission under a HARQ entity, solving the problem of not supporting cross-carrier data transmission, improving the resource utilization of carrier resources during data transmission, and thus improving data transmission performance.

[0127] In some embodiments, as shown in FIG20 , the method may further include the following steps:

[0128] S401: Determine a transmission resource set corresponding to a physical shared channel set.

[0129] In some embodiments, when the second node associates a HARQ entity with a physical shared channel set, the second node may determine a transmission resource set corresponding to the physical shared channel set. For a description of the transmission resource set, reference may be made to the corresponding description in the embodiment shown in FIG. 6 above, and detailed description is omitted here.

[0130] S402: Send second control information.

[0131] The second control information is used to indicate a correspondence between physical shared channels in the physical shared channel set and transmission resources in the transmission resource set.

[0132] In some embodiments, the second control information includes at least one of the following: an RRC message, a DCI, wherein the RRC message may be at least one of the following: an RRC establishment message, an RRC reconfiguration message, and an RRC forwarding message.

[0133] For the description of the second control information, reference may be made to the corresponding description in the embodiment shown in FIG6 , which will not be repeated here.

[0134] It should be understood that after determining the transmission resource set corresponding to the physical shared channel set, the second node sends the second control information to the first node, so that the first node can determine the transmission resource set corresponding to the physical shared channel set based on the second control information, and then the first node can know which transmission resources each physical shared channel is carried on, thereby achieving flexible selection of physical shared channels and flexible selection of transmission resources for data transmission under a HARQ entity, improving the resource utilization of carrier resources during data transmission, and thus improving data transmission performance.

[0135] In some embodiments, after the second node associates a HARQ entity with a physical shared channel set, or after the second node determines a transmission resource set corresponding to the physical shared channel set, the second node may further associate the HARQ entity with the transmission resource set, that is, associate a HARQ entity of the first node with the transmission resource set. In this way, the first node and the second node have consistent knowledge of the transmission resource set associated with the HARQ entity of the first node, thereby helping to improve data transmission performance.

[0136] In some embodiments, the first control information and the second control information are two independent control signaling messages, and the second node sends the first control information and the second control information separately. For example, the first control information and the second control information are two RRC messages. For another example, the first control information and the second control information are two DCI messages. For another example, the first control information is an RRC message, and the second control information is a DCI message. For another example, the first control information is a DCI message, and the second control information is an RRC message.

[0137] In some embodiments, the first control information and the second control information correspond to a control signaling message, and the second node sends a control signaling message including the first control information and the second control information. For example, the first control information and the second control information belong to a RRC message. For example, the first control information and the second control information belong to a DCI message.

[0138] As an example, the second node associates a HARQ entity with a physical shared channel set and associates the HARQ entity with a transmission resource set, which can be the MAC entity of the second node associating a HARQ entity with a physical shared channel set and associating the HARQ entity with a transmission resource set.

[0139] The above mainly introduces the solution provided by the present disclosure from the perspective of the interaction between each node. It is understandable that each node, such as the first node or the second node, includes a hardware structure and / or software module corresponding to the execution of each function in order to realize the above functions. Those skilled in the art should easily realize that, in combination with the algorithm steps of each example described in the embodiments disclosed herein, the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present disclosure.

[0140] FIG21 is a schematic diagram showing the composition of a communication device provided by an embodiment of the present disclosure. As shown in FIG21 , the communication device 50 includes a receiving unit 501 and a processing unit 502 .

[0141] The communication device 50 may be the first node or a chip in the first node. When the communication device 50 is used to implement the function of the first node in the above embodiment, each unit is specifically used to implement the following functions.

[0142] The receiving unit 501 is configured to receive first control information, where the first control information is used to indicate an association relationship between a hybrid automatic repeat request HARQ entity and a physical shared channel set.

[0143] The processing unit 502 associates the HARQ entity with the physical shared channel set based on the first control information.

[0144] In some embodiments, the receiving unit 501 is configured to receive second control information, where the second control information is used to indicate a correspondence between physical shared channels in the physical shared channel set and transmission resources in the transmission resource set.

[0145] The processing unit 502 is configured to determine a transmission resource set corresponding to a physical shared channel set based on the second control information.

[0146] In some embodiments, the processing unit 502 is further configured to associate the HARQ entity with the transmission resource set.

[0147] In some embodiments, the physical shared channel set includes at least one of the following: a plurality of physical downlink shared channels (PDSCHs) and a plurality of physical uplink shared channels (PUSCHs).

[0148] In some embodiments, the transmission resource set includes multiple transmission resources, and the transmission resources include at least one of the following: a carrier, a partial bandwidth BWP, a cell, a beam, and a transmission / reception point TRP.

[0149] In some embodiments, the transmission resource set includes at least one of the following: a carrier set, a BWP set, a cell set, a beam set, and a TRP set, wherein the number of carriers included in the carrier set is greater than 1, the BWP set includes multiple BWPs located at different carriers, and the beam set includes multiple spatial beams belonging to different carriers.

[0150] In some embodiments, all physical shared channels in a physical shared channel set associated with a HARQ entity can share a HARQ buffer of the HARQ entity.

[0151] In some embodiments, all transmission resources in the transmission resource set associated with the HARQ entity can be used to transmit data in the HARQ buffer of the HARQ entity.

[0152] In some embodiments, new transmission and retransmission of the same data packet under the HARQ entity are respectively carried and transmitted on different physical shared channels in the physical shared channel set associated with the HARQ entity.

[0153] In some embodiments, the new transmission and retransmission of the same data packet under the HARQ entity are respectively transmitted using different transmission resources in the transmission resource set associated with the HARQ entity, or the uplink data and downlink data under the HARQ entity are respectively transmitted using the same transmission resources in the transmission resource set associated with the HARQ entity.

[0154] In some embodiments, uplink data and downlink data under the HARQ entity are respectively transmitted using different transmission resources in the transmission resource set associated with the HARQ entity.

[0155] In some embodiments, the identifiers of the transmission resources used by uplink data are different from the identifiers of the transmission resources used by downlink data; and / or the number of transmission resources used by uplink data is different from the number of transmission resources used by downlink data.

[0156] In some embodiments, the first control information includes at least one of the following: a HARQ entity identifier, a PDSCH identifier, a PUSCH identifier, a carrier identifier, an indication corresponding to the PDSCH identifier and the carrier identifier, an indication corresponding to the PUSCH identifier and the carrier identifier, a rule corresponding to the PDSCH identifier and the carrier identifier, and a rule corresponding to the PUSCH identifier and the carrier identifier.

[0157] In some embodiments, the second control information includes at least one of the following: a HARQ entity identifier, a PDSCH identifier, a PUSCH identifier, a transmission resource identifier, an indication corresponding to the PDSCH identifier and the transmission resource identifier, an indication corresponding to the PUSCH identifier and the transmission resource identifier, a rule corresponding to the PDSCH identifier and the transmission resource identifier, and a rule corresponding to the PUSCH identifier and the transmission resource identifier.

[0158] In some embodiments, the first control information includes at least one of the following: a radio resource bearer RRC message, and downlink control information DCI.

[0159] In some embodiments, the second control information includes at least one of the following: an RRC message, a DCI.

[0160] In some embodiments, the HARQ entity is any one of the following: a HARQ entity corresponding to a data radio bearer DRB, a HARQ entity corresponding to multiple DRBs, and a HARQ entity corresponding to multiple DRBs after multiplexing at the media access control MAC layer.

[0161] FIG22 is a schematic diagram showing the composition of another communication device provided by an embodiment of the present disclosure. As shown in FIG22 , the communication device 60 includes a processing unit 601 and a sending unit 602 .

[0162] The communication device 60 may be the second node or a chip in the second node. When the communication device 60 is used to implement the function of the second node in the above embodiment, each unit is specifically used to implement the following functions.

[0163] The processing unit 601 is configured to associate a HARQ entity with a physical shared channel set.

[0164] The sending unit 602 is configured to send first control information, where the first control information is used to indicate an association relationship between a HARQ entity and a physical shared channel set.

[0165] In some embodiments, the processing unit 601 is further configured to determine a transmission resource set corresponding to the physical shared channel set.

[0166] The sending unit 602 is further configured to send second control information, where the second control information is used to indicate a correspondence between physical shared channels in the physical shared channel set and transmission resources in the transmission resource set.

[0167] In some embodiments, the processing unit 601 is further configured to associate the HARQ entity with the transmission resource set.

[0168] In some embodiments, the physical shared channel set includes at least one of the following: a plurality of physical downlink shared channels (PDSCHs) and a plurality of physical uplink shared channels (PUSCHs).

[0169] In some embodiments, the transmission resource set includes multiple transmission resources, and the transmission resources include at least one of the following: a carrier, a partial bandwidth BWP, a cell, a beam, and a transmission / reception point TRP.

[0170] In some embodiments, the transmission resource set includes at least one of the following: a carrier set, a BWP set, a cell set, a beam set, and a TRP set, wherein the number of carriers included in the carrier set is greater than 1, the BWP set includes multiple BWPs located at different carriers, and the beam set includes multiple spatial beams belonging to different carriers.

[0171] In some embodiments, all physical shared channels in a physical shared channel set associated with a HARQ entity can share a HARQ buffer of the HARQ entity.

[0172] In some embodiments, all transmission resources in the transmission resource set associated with the HARQ entity can be used to transmit data in the HARQ buffer of the HARQ entity.

[0173] In some embodiments, new transmission and retransmission of the same data packet under the HARQ entity are respectively carried and transmitted on different physical shared channels in the physical shared channel set associated with the HARQ entity.

[0174] In some embodiments, new transmission and retransmission of the same data packet under the HARQ entity are respectively transmitted using different transmission resources in the transmission resource set associated with the HARQ entity.

[0175] In some embodiments, the uplink data and downlink data under the HARQ entity are respectively transmitted using different transmission resources in the transmission resource set associated with the HARQ entity, or the uplink data and downlink data under the HARQ entity are respectively transmitted using the same transmission resources in the transmission resource set associated with the HARQ entity.

[0176] In some embodiments, the identifiers of the transmission resources used by uplink data are different from the identifiers of the transmission resources used by downlink data; and / or the number of transmission resources used by uplink data is different from the number of transmission resources used by downlink data.

[0177] In some embodiments, the first control information includes at least one of the following: a HARQ entity identifier, a PDSCH identifier, a PUSCH identifier, a carrier identifier, an indication corresponding to the PDSCH identifier and the carrier identifier, an indication corresponding to the PUSCH identifier and the carrier identifier, a rule corresponding to the PDSCH identifier and the carrier identifier, and a rule corresponding to the PUSCH identifier and the carrier identifier.

[0178] In some embodiments, the second control information includes at least one of the following: a HARQ entity identifier, a PDSCH identifier, a PUSCH identifier, a transmission resource identifier, an indication corresponding to the PDSCH identifier and the transmission resource identifier, an indication corresponding to the PUSCH identifier and the transmission resource identifier, a rule corresponding to the PDSCH identifier and the transmission resource identifier, and a rule corresponding to the PUSCH identifier and the transmission resource identifier.

[0179] In some embodiments, the first control information includes at least one of the following: a radio resource bearer RRC message, and downlink control information DCI.

[0180] In some embodiments, the second control information includes at least one of the following: an RRC message, a DCI.

[0181] In some embodiments, the HARQ entity is any one of the following: a HARQ entity corresponding to a data radio bearer DRB, a HARQ entity corresponding to multiple DRBs, and a HARQ entity corresponding to multiple DRBs after multiplexing at the media access control MAC layer.

[0182] It should be noted that the units in Figures 21 and 22 may also be referred to as modules. For example, the sending unit may be referred to as a sending module. In addition, in the embodiments shown in Figures 21 and 22, the names of the units may not be those shown in the figures. For example, the sending unit may be referred to as a communication unit, and the receiving unit may be referred to as a communication unit.

[0183] If the various units in Figures 21 and 22 are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the various embodiments of the present disclosure. The storage medium for storing computer software products includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0184] When the communication device 50 or 60 implements the functions of the integrated modules in hardware, the present disclosure provides a schematic structural diagram of the communication device. As shown in Figure 23, the communication device 70 includes: a processor 702, a communication interface 703, and a bus 704. Optionally, the communication device 70 may also include a memory 701.

[0185] Processor 702 may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the present disclosure. Processor 702 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the present disclosure. Processor 702 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, or a combination of a DSP and a microprocessor.

[0186] The communication interface 703 is used to connect to other devices via a communication network, such as Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0187] The memory 701 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0188] As a possible implementation, the memory 701 can exist independently of the processor 702. The memory 701 can be connected to the processor 702 via a bus 704 to store instructions or program codes. When the processor 702 calls and executes the instructions or program codes stored in the memory 701, the information transmission method provided in the embodiment of the present disclosure can be implemented.

[0189] In another possible implementation, the memory 701 and the processor 702 may also be integrated together.

[0190] Bus 704 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 704 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, FIG23 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0191] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and conciseness of the description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the base station or terminal is divided into different functional modules to complete all or part of the functions described above.

[0192] The embodiments of the present disclosure also provide a computer-readable storage medium. All or part of the processes in the above-mentioned method embodiments can be completed by computer instructions to the relevant hardware. The program can be stored in the above-mentioned computer-readable storage medium. When the program is executed, it can include the processes of the above-mentioned method embodiments. The computer-readable storage medium can be the memory of any of the above-mentioned embodiments. The above-mentioned computer-readable storage medium can also be an external storage device of the above-mentioned first node or second node, such as a plug-in hard disk, a smart memory card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the above-mentioned first node or second node. Furthermore, the above-mentioned computer-readable storage medium can also include both the internal storage unit of the above-mentioned first node or second node and an external storage device. The above-mentioned computer-readable storage medium is used to store the above-mentioned computer program and other programs and data required by the above-mentioned first node or second node. The above-mentioned computer-readable storage medium can also be used to temporarily store data that has been output or is to be output.

[0193] The embodiments of the present disclosure further provide a computer program product, which includes a computer program. When the computer program product is run on a computer, the computer is enabled to execute any one of the information transmission methods provided in the above embodiments.

[0194] Although the present disclosure is described herein in conjunction with various embodiments, in the process of implementing the disclosure for which protection is sought, those skilled in the art may understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple components. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0195] Although the present disclosure has been described with reference to specific features and embodiments thereof, it will be apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present disclosure. Accordingly, this specification and the drawings are merely illustrative of the present disclosure as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present disclosure. Obviously, those skilled in the art may make various modifications and variations to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, the present disclosure is intended to encompass such modifications and variations if they fall within the scope of the claims of the present disclosure and their equivalents.

[0196] The above are only specific embodiments of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or replacements within the technical scope disclosed in the present disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. An information transmission method, wherein, Applied to a first node, the method includes: Receiving first control information, where the first control information is used to indicate an association relationship between a Hybrid Automatic Repeat reQuest (HARQ) entity and a set of Physical Shared Channels; Associating the HARQ entity with the set of Physical Shared Channels based on the first control information.

2. The method according to claim 1, wherein The method further includes: Receiving second control information, where the second control information is used to indicate a correspondence relationship between Physical Shared Channels in the set of Physical Shared Channels and transmission resources in a set of transmission resources; Determining the set of transmission resources corresponding to the set of Physical Shared Channels based on the second control information.

3. The method according to claim 1 or 2, wherein, The method further includes: Associating the HARQ entity with the set of transmission resources.

4. The method according to claim 1, wherein, The set of Physical Shared Channels includes at least one of the following: multiple Physical Downlink Shared Channels (PDSCHs), multiple Physical Uplink Shared Channels (PUSCHs).

5. The method according to claim 2, wherein, The set of transmission resources includes multiple transmission resources, and the transmission resources include at least one of the following: carrier, Bandwidth Part (BWP), cell, beam, Transmit / Receive Point (TRP).

6. The method according to claim 5, wherein, The set of transmission resources includes at least one of the following: a set of carriers, a set of BWPs, a set of cells, a set of beams, a set of TRPs, where the number of carriers included in the set of carriers is greater than 1, the set of BWPs includes multiple BWPs located on different carriers, and the set of beams includes multiple spatial beams belonging to different carriers.

7. The method according to claim 1, wherein All Physical Shared Channels in the set of Physical Shared Channels associated with the HARQ entity can share the HARQ buffer of the HARQ entity.

8. The method according to claim 3, wherein All transmission resources in the set of transmission resources associated with the HARQ entity can be used to transmit data in the HARQ buffer of the HARQ entity.

9. The method according to claim 1, wherein The new transmission and retransmission of the same data packet under the HARQ entity are respectively carried and transmitted on different Physical Shared Channels in the set of Physical Shared Channels associated with the HARQ entity.

10. The method according to claim 3, wherein The new transmission and retransmission of the same data packet under the HARQ entity respectively use different transmission resources in the set of transmission resources associated with the HARQ entity for transmission.

11. The method according to claim 3, wherein, The uplink data and downlink data under the HARQ entity respectively use different transmission resources in the set of transmission resources associated with the HARQ entity; or, The uplink data and downlink data under the HARQ entity respectively use the same transmission resources in the set of transmission resources associated with the HARQ entity.

12. The method according to claim 11, wherein The identifier of the transmission resources used for the uplink data is different from the identifier of the transmission resources used for the downlink data; and / or, the number of transmission resources used for the uplink data is different from the number of transmission resources used for the downlink data.

13. The method according to claim 1, wherein The first control information includes at least one of the following: HARQ entity identifier, PDSCH identifier, PUSCH identifier, carrier identifier, indication corresponding to the PDSCH identifier and the carrier identifier, indication corresponding to the PUSCH identifier and the carrier identifier, rule corresponding to the PDSCH identifier and the carrier identifier, rule corresponding to the PUSCH identifier and the carrier identifier.

14. The method according to claim 2, wherein The second control information includes at least one of the following: HARQ entity identifier, PDSCH identifier, PUSCH identifier, transmission resource identifier, indication corresponding to the PDSCH identifier and the transmission resource identifier, indication corresponding to the PUSCH identifier and the transmission resource identifier, rule corresponding to the PDSCH identifier and the transmission resource identifier, rule corresponding to the PUSCH identifier and the transmission resource identifier.

15. The method according to claim 1, wherein, The first control information includes at least one of the following: radio resource control (RRC) message, downlink control information (DCI).

16. The method according to claim 2, wherein, The second control information includes at least one of the following: RRC message, DCI.

17. The method according to claim 1, wherein The HARQ entity is any one of the following: a HARQ entity corresponding to one data radio bearer (DRB), a HARQ entity corresponding to multiple DRBs, a HARQ entity corresponding to multiple DRBs multiplexed at the media access control (MAC) layer.

18. An information transmission method, wherein, Applied to a second node, the method includes: Associating a HARQ entity with a set of physical shared channels; Sending first control information for indicating the association relationship between the HARQ entity and the set of physical shared channels.

19. The method according to claim 18, wherein, The method further includes: Determining a set of transmission resources corresponding to the set of physical shared channels; Sending second control information for indicating the corresponding relationship between the physical shared channels in the set of physical shared channels and the transmission resources in the set of transmission resources.

20. The method according to claim 18 or 19, wherein The method further includes: Associating the HARQ entity with the set of transmission resources.

21. The method according to claim 18, wherein The set of physical shared channels includes at least one of the following: multiple physical downlink shared channels (PDSCHs), multiple physical uplink shared channels (PUSCHs).

22. The method according to claim 19, wherein The set of transmission resources includes multiple transmission resources, and the transmission resources include at least one of the following: carrier, partial bandwidth (BWP), cell, beam, transmit / receive point (TRP).

23. The method according to claim 22, wherein, The set of transmission resources includes at least one of the following: a set of carriers, a set of BWPs, a set of cells, a set of beams, a set of TRPs, where the number of carriers included in the set of carriers is greater than 1, the set of BWPs includes multiple BWPs located on different carriers, and the set of beams includes multiple spatial beams belonging to different carriers.

24. The method according to claim 18, wherein, All physical shared channels in the set of physical shared channels associated with the HARQ entity can share and use the HARQ buffer of the HARQ entity.

25. The method according to claim 20, wherein All transmission resources in the set of transmission resources associated with the HARQ entity can be used to transmit data in the HARQ buffer of the HARQ entity.

26. The method according to claim 18, wherein The new transmission and retransmission of the same data packet under the HARQ entity are respectively carried and transmitted on different physical shared channels in the set of physical shared channels associated with the HARQ entity.

27. The method according to claim 20, wherein The new transmission and retransmission of the same data packet under the HARQ entity respectively use different transmission resources in the set of transmission resources associated with the HARQ entity for transmission.

28. According to the method of claim 20, wherein, The uplink data and downlink data under the HARQ entity are respectively transmitted using different transmission resources in the set of transmission resources associated with the HARQ entity; or, The uplink data and downlink data under the HARQ entity are respectively transmitted using the same transmission resources in the set of transmission resources associated with the HARQ entity.

29. The method according to claim 28, wherein The identifier of the transmission resource used by the uplink data is different from the identifier of the transmission resource used by the downlink data; and / or, the number of transmission resources used by the uplink data is different from the number of transmission resources used by the downlink data.

30. The method according to claim 18, wherein, The first control information includes at least one of the following: HARQ entity identifier, PDSCH identifier, PUSCH identifier, carrier identifier, indication corresponding to the PDSCH identifier and the carrier identifier, indication corresponding to the PUSCH identifier and the carrier identifier, rule corresponding to the PDSCH identifier and the carrier identifier, rule corresponding to the PUSCH identifier and the carrier identifier.

31. The method according to claim 19, wherein The second control information includes at least one of the following: HARQ entity identifier, PDSCH identifier, PUSCH identifier, transmission resource identifier, indication corresponding to the PDSCH identifier and the transmission resource identifier, indication corresponding to the PUSCH identifier and the transmission resource identifier, rule corresponding to the PDSCH identifier and the transmission resource identifier, rule corresponding to the PUSCH identifier and the transmission resource identifier.

32. The method according to claim 18, wherein The first control information includes at least one of the following: radio resource control (RRC) message, downlink control information (DCI).

33. The method according to claim 19, wherein, The second control information includes at least one of the following: RRC message, DCI.

34. The method according to claim 18, wherein The HARQ entity is any one of the following: a HARQ entity corresponding to one data radio bearer (DRB), a HARQ entity corresponding to multiple DRBs, a HARQ entity corresponding to multiple DRBs multiplexed at the media access control (MAC) layer.

35. A communication device, wherein, Comprising: A memory and a processor; The memory and the processor are coupled; The memory is used to store instructions executable by the processor; When the processor executes the instructions, it executes the method according to any one of claims 1-17, or the method according to any one of claims 18-34.

36. A computer-readable storage medium, wherein, Computer instructions are stored on the computer-readable storage medium, and when the computer instructions run on a computer, the computer is caused to execute the method according to any one of claims 1-17, or the method according to any one of claims 18-34.

Images