Communication method and apparatus

Abstract

A communication method and apparatus. The method comprises: on a first carrier, receiving first scheduling information from a network device, wherein the first scheduling information is used for scheduling first downlink data; and on a second carrier, receiving second scheduling information from the network device, wherein the second scheduling information is used for scheduling second downlink data. The first downlink data corresponds to a first hybrid automatic repeat request (HARQ) process, the second downlink data corresponds to a second HARQ process, the first HARQ process and the second HARQ process belong to a first HARQ process group, and the first HARQ process group is maintained by a first HARQ entity. By means of the method, one HARQ process group maintained by one HARQ entity can correspond to a plurality of carriers, e.g., a first carrier and a second carrier. In this way, there are fewer maintained HARQ process groups than there are downlink carriers supported by a terminal device for parallel reception, thereby reducing resources required by the maintained HARQ process groups.

Description

A communication method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411719049.2, filed on November 26, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] Carrier aggregation (CA) technology refers to providing communication services to terminal devices using multiple component carriers (CCs), which can increase data transmission bandwidth and improve peak data rates. To ensure data transmission reliability, the terminal device needs to maintain a hybrid automatic repeat request (HARQ) process group for each downlink CC.

[0005] Maintaining HARQ process groups requires significant memory resources and is complex to implement. If the network device configures a large number of downlink CCs for the terminal device, the terminal device must maintain multiple HARQ process groups, leading to high resource overhead. Therefore, reducing the resource overhead of terminal devices in maintaining HARQ process groups is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a communication method and apparatus for reducing the resource overhead of HARQ process groups.

[0007] Firstly, this application provides a communication method, wherein the execution subject of the method is a terminal device or a module or chip within the terminal device, and the method is described here using a terminal device as the execution subject as an example. The method includes: receiving first scheduling information from a network device on a first carrier; the first scheduling information being used to schedule first downlink data; receiving second scheduling information from the network device on a second carrier; the second scheduling information being used to schedule second downlink data; wherein the first downlink data corresponds to a first Hybrid Automatic Repeat Request (HARQ) process, the second downlink data corresponds to a second HARQ process, the first HARQ process and the second HARQ process belong to a first HARQ process group, and the first HARQ process group is maintained by a first HARQ entity.

[0008] Using this method, a HARQ process group maintained by one HARQ entity can correspond to multiple carriers (the number of carriers is a positive integer). For example, the first HARQ process group maintained by the first HARQ entity corresponds to the first carrier and the second carrier. In this way, the number of HARQ process groups maintained by the terminal device is less than the number of downlink carriers that the terminal device supports for parallel reception. This can reduce the number of HARQ process groups maintained by the terminal device, reduce the resources required for the HARQ process groups maintained by the terminal device, reduce the resource overhead of the HARQ process groups, and meet the needs of low-capability terminal devices.

[0009] In one possible implementation, the first carrier and the second carrier belong to a first carrier group, the first carrier group is associated with the first HARQ process group, and the carriers in the first carrier group are associated with the HARQ processes in the first HARQ process group.

[0010] This method allows a HARQ process group to be associated with the first carrier group, thus maintaining one HARQ process group for each carrier group. This saves on the number of HARQ processes and memory resources, which helps reduce the cost of terminal devices and meet the needs of low-capacity terminal devices.

[0011] In one possible implementation, the method further includes: receiving first information from the network device, the first information indicating M carrier groups, one carrier group including at least one carrier, the M carrier groups including the first carrier group, and M being an integer greater than 0; determining M HARQ process groups associated with the M carrier groups, the M HARQ process groups including the first HARQ process group.

[0012] In one possible implementation, M is less than or equal to X, where X is the maximum number of downlink carriers supported by the terminal device.

[0013] In one possible implementation, after the second carrier receives second scheduling information from the network device, the method further includes: designating the first HARQ process group associated with the first carrier as the HARQ process group associated with the second carrier.

[0014] This method allows terminal devices to flexibly switch HARQ process groups associated with different carriers, reducing the number of HARQ process groups to maintain while improving the flexibility of associating carriers with HARQ process groups. It also saves memory resources, which helps reduce the cost of terminal devices and meets the needs of low-capacity terminal devices.

[0015] In one possible implementation, the first scheduling information further includes a first new data indication, and the second scheduling information further includes a second new data indication; wherein, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication is not flipped relative to the first new data indication, then the second downlink data is retransmission data of the first downlink data;

[0016] Alternatively, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication has been flipped relative to the first new data indication, then the second downlink data is the initial transmission data.

[0017] In one possible implementation, the method further includes: receiving handover indication information from the network device, the handover indication information indicating a handover from the first carrier to the second carrier.

[0018] In one possible implementation, the switching indication information further indicates that the first HARQ process group associated with the first carrier is used as the HARQ process group associated with the second carrier.

[0019] Secondly, this application provides a communication method, wherein the execution subject of the method is a network device or a module or chip within a network device, and the method is described here using a network device as the execution subject as an example. The method includes: sending first scheduling information to a terminal device on a first carrier; the first scheduling information is used to schedule first downlink data; sending second scheduling information to the terminal device on a second carrier; the second scheduling information is used to schedule second downlink data; wherein the first downlink data corresponds to a first Hybrid Automatic Repeat Request (HARQ) process, the second downlink data corresponds to a second HARQ process, the first HARQ process and the second HARQ process belong to a first HARQ process group, and the first HARQ process group is maintained by a first HARQ entity.

[0020] In one possible implementation, the first carrier and the second carrier belong to a first carrier group, and the carriers in the first carrier group are associated with the first HARQ process group.

[0021] In one possible implementation, the method further includes: sending first information to the terminal device, the first information indicating M carrier groups, one carrier group including at least one carrier, the M carrier groups including the first carrier group, and M being an integer greater than 0.

[0022] In one possible implementation, M is less than or equal to X, where X is the maximum number of downlink carriers supported by the terminal device.

[0023] In one possible implementation, the first scheduling information further includes a first new data indication, and the second scheduling information further includes a second new data indication; wherein, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication is not flipped relative to the first new data indication, then the second downlink data is retransmission data of the first downlink data;

[0024] Alternatively, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication has been flipped relative to the first new data indication, then the second downlink data is the initial transmission data.

[0025] In one possible implementation, the method further includes: sending handover indication information to the terminal device, the handover indication information indicating a handover from the first carrier to the second carrier.

[0026] In one possible implementation, the switching indication information further indicates that the first HARQ process group associated with the first carrier is used as the HARQ process group associated with the second carrier.

[0027] Thirdly, this application also provides a communication device capable of implementing any of the methods provided in any of the first to second aspects described above. This communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the aforementioned functions.

[0028] In one possible implementation, the communication device includes a processor configured to support the communication device in performing corresponding functions of the network device, terminal device, or core network device described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and devices such as terminal devices.

[0029] In one possible implementation, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0030] In one possible implementation, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples, as described in the methods provided in any of the first or second aspects, and will not be repeated here.

[0031] Fourthly, a communication device is provided, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor implements the functional modules of the methods in any possible implementation of any of the first to second aspects through logic circuits or by executing computer programs or instructions. Optionally, the communication device further includes a memory for storing computer programs or instructions.

[0032] Fifthly, a computer-readable storage medium is provided that stores a computer program or instructions which, when executed by a processor, implement the method in any possible implementation of any of the first to second aspects described above.

[0033] In a sixth aspect, a computer program product storing instructions is provided, which, when read and executed by a computer, implements the method in any possible implementation of any of the first to second aspects described above.

[0034] In a seventh aspect, a circuit is provided for performing the methods in any possible implementation of any of the first to second aspects described above. The circuit may include chip circuitry. Optionally, the circuit may also be coupled to a memory.

[0035] Eighthly, a chip is provided, comprising a processor, which, when executing a computer program or instructions, implements the methods in any possible implementation of any of the first to second aspects described above. Optionally, the chip may further include a memory, and the chip may be composed of chips or may include chips and other discrete devices.

[0036] A ninth aspect provides a communication device including a processor that implements the method in any possible implementation of any of the first to second aspects by means of logic circuits or by executing computer programs or instructions.

[0037] In a tenth aspect, a communication apparatus is provided, comprising a unit or module for performing a method in any possible implementation of any of the first to second aspects described above.

[0038] Eleventhly, embodiments of this application also provide a communication system. The communication system includes: a terminal device for implementing the methods of the first aspect and any possible implementation thereof; and a network device for implementing the methods of the second aspect and any possible implementation thereof. Attached Figure Description

[0039] Figure 1 is a schematic diagram of the architecture of a communication system applicable to an embodiment of this application;

[0040] Figure 2 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0041] Figure 3 is a schematic diagram of carrier aggregation provided in an embodiment of this application;

[0042] Figure 4 is a schematic diagram of carrier aggregation provided in an embodiment of this application;

[0043] Figure 5 is a schematic diagram of a communication device structure provided in an embodiment of this application;

[0044] Figure 6 is a schematic diagram of a communication device structure provided in an embodiment of this application;

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

[0046] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. The terms "first," "second," and corresponding terminology in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be interchanged where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or device that comprises a series of units is not necessarily limited to those units, but may include other units not explicitly listed or inherent to these processes, methods, products, or devices. The methods and apparatus provided in the embodiments of this application are based on the same or similar technical concepts. Since the principles by which the methods and apparatus solve problems are similar, the implementations of the apparatus and methods can refer to each other, and repeated details will not be repeated.

[0047] The method provided in this application can be applied to various mobile communication systems, such as the Internet of Things (IoT), narrowband Internet of Things (NB-IoT), fourth-generation (4G) communication systems (e.g., Long Term Evolution (LTE)), fifth-generation (5G) communication systems (e.g., 5G New Radio (NR)), LTE and NR hybrid architectures, or new communication systems emerging in future communication developments. The communication system can also include machine-to-machine (M2M) networks, machine-type communication (MTC) networks, or other networks.

[0048] The following section will first explain some of the terms used in the embodiments of this application so that those skilled in the art can understand them.

[0049] Figure 1 is a schematic diagram of the architecture of a communication system applicable to an embodiment of this application. As shown in Figure 1, the communication system includes an access network 100 and a core network 200. Optionally, the communication system may also include an Internet 300. The access network 100 may include at least one radio access network (RAN) node, such as 110a and 110b in Figure 1, and may also include at least one terminal device, such as 120a-120j in Figure 1. Specifically, 110a is a base station (BS), 110b is a micro-station, 120a, 120e, 120f, and 120j are mobile phones, 120b is a car, 120c is a fuel dispenser, 120d is a home access point (HAP) deployed indoors or outdoors, 120g is a laptop computer, 120h is a printer, and 120i is a drone. The same terminal device or network device can provide different functions in different application scenarios. For example, the mobile phones in Figure 1 are 120a, 120e, 120f and 120j. Mobile phone 120a can access base station 110a, connect to car 120b, communicate directly with mobile phone 120e and access HAP. Car 120b can access HAP and communicate directly with mobile phone 120a. Mobile phone 120f can access micro-station 110b, connect to laptop 120g and printer 120h. Mobile phone 120j can control drone 120i.

[0050] In this embodiment, the network device can be a device in a wireless network, and can also be referred to as a network apparatus, a radio access network device, or an access network device. For example, the network device can be a radio access network (RAN) node that connects a terminal device to a wireless network, and can also be referred to as an access network device. The network device includes, but is not limited to: base station, evolved NodeB (eNodeB), transmission reception point (TRP), next-generation NodeB (gNB) in a 5th generation (5G) mobile communication system, access network device in an open radio access network (O-RAN), base station in a future mobile communication system, or access node in a wireless fidelity (WiFi) system; or it can be a module or unit that performs some functions of a base station, such as a central unit (CU), a distributed unit (DU), a central unit control plane (CU-CP) module, or a central unit user plane (CU-UP) module. Network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, or donor nodes, etc. This application does not limit the specific technology or form of the network equipment.

[0051] In some implementations, network devices can include centralized units (CUs) and distributed units (DUs). This includes RAN devices at CU and DU nodes that separate the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed across the DUs, which are then centrally controlled by the CU. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP handles control plane functions, primarily including radio resource control (RRC) and the corresponding packet data convergence protocol (PDCP) (PDCP-C). PDCP-C is mainly responsible for control plane data encryption / decryption, integrity protection, and data transmission. The CU-UP handles user plane functions, primarily including the service data adaptation protocol (SDAP) and the corresponding PDCP (PDCP-U). SDAP is mainly responsible for processing core network data and mapping flows to bearers. PDCP-U is primarily responsible for data plane encryption / decryption, integrity protection, header compression, sequence number maintenance, and data transmission. CU-CP and CU-UP are connected via the E1 interface. CU-CP represents the gNB connected to the core network via the NG interface and to the DU via the F1 interface control plane (F1-C). CU-UP is connected to the DU via the F1 interface user plane (F1-U). Alternatively, PDCP-C may also be located within CU-UP.

[0052] It is understood that CU (including CU-CP or CU-UP) or DU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN) system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, and CU-UP can also be called O-CU-UP. For ease of description, this application uses CU, CU-CP, CU-UP, and DU as examples. Network devices may also include active antenna units (AAU). CU implements some of the functions of gNB, and DU implements some of the functions of gNB. For example, CU is responsible for handling non-real-time protocols and services, implementing the functions of the RRC layer. DU is responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer. In some deployments, the CU can also be divided into a centralized unit control plane (CU-CP) node and a centralized unit user plane (CU-UP) node. The CU-CP is responsible for control plane functions, while the CU-UP is responsible for user plane functions.

[0053] The terminal device involved in the embodiments of this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The terminal device can be referred to as a terminal device, or it can also be called user equipment (UE), terminal, mobile station (MS), mobile terminal (MT), etc. The terminal device can be a device that includes wireless communication functions (providing voice / data connectivity to the user). For example, a handheld device with wireless connectivity, or an in-vehicle device, in-vehicle module, etc. Currently, examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in vehicle-to-everything (V2X) communication, wireless terminals in vehicle-to-everything (V2X) communication, intelligent vehicles, in-vehicle infotainment systems (or onboard transmitters) (T-boxes), machine-to-machine / machine-type communications (M2M / MTC) terminal devices, and the Internet of Things (IoT). Wireless terminals in industrial control systems can include devices such as IoT (Internet of Things) terminals. For example, terminal devices can be in-vehicle equipment, vehicle-mounted modules, vehicles, on-board units (OBUs), roadside units (RSUs), T-boxes, chips, or systems-on-chips (SoCs), which can be installed in vehicles, OBUs, RSUs, or T-boxes. Wireless terminals in industrial control systems can be cameras, robots, etc. Wireless terminals in smart homes can be televisions, air conditioners, robot vacuums, speakers, set-top boxes, etc.Terminal devices can also be V2X devices, such as smart cars, digital cars, unmanned cars, driverless cars, pilotless cars, autonomous cars, pure electric vehicles (EVs), hybrid electric vehicles (HEVs), range-extended electric vehicles (REEVs), plug-in hybrid electric vehicles (PHEVs), new energy vehicles, and roadside units (RSUs). Terminal devices can also be devices in device-to-device (D2D) communication, such as electricity meters and water meters. Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of future information technology development, and its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and machine-to-machine interconnection.

[0054] Network devices can employ carrier aggregation technology to increase data transmission bandwidth. In carrier aggregation, the number of downlink CCs configured by the network device for the terminal device can be greater than or equal to the number of uplink CCs. For example, the network device can configure 2 CC aggregations in the uplink direction and 4 CC aggregations in the downlink direction. The terminal device can configure a HARQ entity for each downlink CC and maintain a HARQ process group through this HARQ entity. A HARQ process group includes multiple parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The maximum number of parallel HARQ processes in the HARQ process group maintained by each HARQ entity is configured by the network device. When the physical layer is not configured for downlink spatial multiplexing, one HARQ process supports one transmission block (TB); when the physical layer is configured for downlink spatial multiplexing, one HARQ process supports one or two TBs.

[0055] Maintaining HARQ process groups requires significant memory resources and is complex to implement. If the network device configures a large number of downlink CCs for the terminal device, the resource overhead of maintaining multiple HARQ process groups is high. Especially when the downlink data baseband processing capability of the terminal device is limited, maintaining a HARQ process group for each downlink CC may exceed the device's capacity. Therefore, this application provides a method to reduce the resource overhead of maintaining HARQ process groups for the terminal device.

[0056] The methods executed by the network device in this application can also be executed by modules or chips in the network device, or by a control subsystem that includes network device functions. Similarly, the methods executed by the terminal device in this application can also be executed by modules or chips (such as baseband or modem) in the terminal device, or by a device that includes terminal device functions.

[0057] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0058] It is understood that this application does not specifically limit the structure of the execution subject of the method provided in the embodiments of this application. It can be applied to modules or chips in terminal devices or modules or chips in network devices, as long as it can communicate according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application. The following description takes the interaction between terminal devices and network devices as an example.

[0059] Figure 2 shows a flowchart of a communication method provided in an embodiment of this application. The method includes:

[0060] Step 201: The network device sends the first scheduling information to the terminal device on the first carrier.

[0061] Accordingly, the terminal device receives the first scheduling information from the network device on the first carrier.

[0062] The first scheduling information is used to schedule the first downlink data. The first scheduling information may indicate information such as time-frequency resources for the first downlink data, but this application is not limited in this regard. The first scheduling information can also be understood as first control information. For example, the first scheduling information can be first downlink control information (DCI).

[0063] The first downlink data can also be replaced with the description of the first TB, the first physical downlink shared channel (PDSCH), or the first physical sidelink shared channel (PSSCH), etc. The specific content of the first downlink data is not limited in this application.

[0064] In one implementation, the first downlink data corresponds to the first HARQ process, and the first HARQ process belongs to the first HARQ process group, that is, the first HARQ process is a HARQ process in the first HARQ process group.

[0065] Optionally, in this application, a HARQ process group is maintained, sustained, or managed by a HARQ entity in the terminal device, or a HARQ process group is associated with or corresponds to a HARQ entity. For example, a first HARQ process group is maintained by a first HARQ entity, that is, the first HARQ entity in the terminal device maintains, sustains, or manages the first HARQ process group, or the first HARQ process group is associated with or corresponds to the first HARQ entity.

[0066] In one implementation, the first scheduling information may further indicate a first HARQ process identifier. The first HARQ process identifier indicated by the first scheduling information may be the HARQ process identifier of the first HARQ process.

[0067] The first HARQ process group can include multiple HARQ processes. The number of HARQ processes in the first HARQ process group can be configured by the network device or preset. A HARQ process group can also be described as a set of HARQ processes or a group of HARQ processes. The number of HARQ processes in a HARQ process group is a positive integer.

[0068] Optionally, in this application, the first carrier can be one of the carriers in a first carrier aggregation combination, which includes at least two carriers. The network device can perform carrier aggregation on the carriers included in the first carrier aggregation combination, and the terminal device can simultaneously receive data on at least one carrier included in the first carrier aggregation combination. This example only illustrates the terminal device receiving downlink data on the first carrier; the terminal device can also receive downlink data on other carriers in the first carrier aggregation combination, but the specific process will not be elaborated further.

[0069] In one implementation, before step 201, the network device may configure a first carrier and a second carrier to the terminal device; the network device may also configure a first carrier aggregation combination. The specific process is not limited in this application and will not be described in detail here.

[0070] Step 202: The network device sends the second scheduling information to the terminal device on the second carrier.

[0071] Correspondingly, the terminal device receives second scheduling information from the network device on the second carrier.

[0072] The second scheduling information is used to schedule the second downlink data. The second scheduling information can indicate information such as time-frequency resources for the second downlink data, and can also be understood as second control information. For example, the second scheduling information can be second downlink control information. The second downlink data can also be described as a second TB, a second PDSCH, or a second PSSCH, etc. The specific content of the second downlink data is not limited in this application.

[0073] In one implementation, the second downlink data corresponds to a second HARQ process, which belongs to the first HARQ process group; that is, the second HARQ process is a HARQ process within the first HARQ process group. In other words, both the first and second HARQ processes belong to the first HARQ process group.

[0074] In one implementation, the second scheduling information may further indicate a second HARQ process identifier. The second HARQ process identifier indicated by the first scheduling information may be the HARQ process identifier of the second HARQ process.

[0075] Optionally, before step 202, the network device may also send a handover instruction message; correspondingly, the terminal device receives the handover instruction message from the network device, which indicates a handover from the first carrier to the second carrier.

[0076] Optionally, the handover indication information can be carried in the control information, such as in the DCI. Alternatively, the handover indication information can be carried in the first scheduling information.

[0077] In this application, a HARQ process group maintained by one HARQ entity can correspond to multiple carriers (the number of carriers is a positive integer). For example, the first HARQ process group maintained by the first HARQ entity corresponds to the first carrier and the second carrier. In this way, the number of HARQ process groups maintained by the terminal device is less than the number of downlink carriers that the terminal device supports for parallel reception. This reduces the number of HARQ process groups maintained by the terminal device, reduces the resources required for the HARQ process groups maintained by the terminal device, and reduces the resource overhead of the HARQ process groups, which can meet the needs of low-capability terminal devices.

[0078] Optionally, in this application, the second carrier can be one of the carriers in a second carrier aggregation combination, which includes at least two carriers. The network device can perform carrier aggregation on the carriers included in the second carrier aggregation combination, and the terminal device can simultaneously receive data on at least one carrier included in the second carrier aggregation combination. This example only illustrates the terminal device receiving downlink data on the second carrier; the terminal device can also receive downlink data on other carriers in the second carrier aggregation combination, but the specific process will not be elaborated further.

[0079] In one implementation, before step 201, the network device may further configure a second carrier aggregation combination. The specific process is not limited in this application and will not be described in detail here.

[0080] In this application, there may be multiple ways to implement a HARQ process group maintained by a HARQ entity corresponding to multiple carriers. Several examples are given below.

[0081] Example 1: Multiple carriers configured by the network device for the terminal device can be divided into M carrier groups. Each carrier group includes at least one carrier, and M is an integer greater than 0. The terminal device can determine the M HARQ process groups or M HARQ entities associated with the M carrier groups. That is, one carrier group in the M carrier groups is associated with one HARQ process group in the M HARQ process groups, or one carrier group in the M carrier groups is associated with one HARQ entity in the M HARQ entities, where M is an integer greater than 0. For example, the number of carriers included in each of the M carrier groups differs by less than or equal to 1. That is, the carrier groups are grouped as evenly as possible.

[0082] For example, a carrier group is associated with a HARQ process group. A HARQ process group is managed or maintained by a HARQ entity, or in other words, a HARQ process and a HARQ entity are associated.

[0083] For example, a carrier in a carrier group is associated with a HARQ process group. This HARQ process group associated with a carrier is managed or maintained by a HARQ entity, or in other words, a HARQ process associated with a carrier is associated with a HARQ entity.

[0084] For example, one HARQ entity corresponds to one MAC entity, or one MAC entity includes one HARQ entity, or one MAC entity manages one HARQ entity. For instance, one carrier group corresponds to one HARQ process group, one HARQ process group corresponds to one HARQ entity, and one HARQ entity corresponds to one MAC entity.

[0085] For example, a MAC entity corresponds to at least one HARQ entity, or a MAC entity includes at least one HARQ entity, or a MAC entity manages at least one HARQ entity. For instance, a carrier group corresponds to a HARQ process group, and each carrier in the carrier group corresponds to its own HARQ entity (one carrier corresponds to one HARQ entity, and different carriers correspond to different HARQ entities), and the MAC entity corresponds to at least one HARQ entity.

[0086] Among them, the carriers included in the M carrier groups can be downlink carriers. The number of carriers included in the M carrier groups is greater than M.

[0087] In this example, the first carrier and the second carrier belong to the first carrier group, the first carrier group is associated with the first HARQ process group, and the carriers in the first carrier group are associated with the HARQ processes in the first HARQ process group. Specifically, M carrier groups include the first carrier group, and M HARQ process groups include the first HARQ process group.

[0088] The M carrier groups can be preset, or they can be indicated by the network device. For example, the network device sends first information to the terminal device; correspondingly, the terminal device receives the first information from the network device; the first information indicates the M carrier groups.

[0089] The M carrier groups can also be determined by the terminal device. After determining the M carrier groups, the terminal device can indicate the M carrier groups to the network device; the specific process will not be elaborated here.

[0090] In one possible implementation, for a network device, given one of M carrier groups, the network device performs data scheduling and carrier switching within that carrier group. The network device does not switch carriers within that carrier group to carriers outside that carrier group. For example, the network device schedules a terminal device to receive downlink data on a first carrier; if the network device instructs the terminal device to switch from the first carrier to another carrier to receive downlink data, the carrier after the first carrier switch is a carrier within the same first carrier group as the first carrier, for example, the carrier after the first carrier switch is the second carrier.

[0091] In one possible implementation, M is less than or equal to X, where X is the maximum number of downlink carriers supported by the terminal device or the maximum number of HARQ process groups supported by the terminal device. The maximum number of downlink carriers supported by the terminal device or the maximum number of HARQ process groups supported by the terminal device can represent the capabilities of the terminal device, which it can report to the network device. Optionally, the terminal device can also report combinations of supported carriers.

[0092] In this application, the network device can schedule the same downlink data in different carriers within the same carrier group, and the HARQ process identifier corresponding to the downlink data in different carriers can remain unchanged.

[0093] For example, the second downlink data scheduled by the network device in the second carrier is retransmission data of the first downlink data scheduled by the network device in the first carrier. The first HARQ process corresponding to the first downlink data and the second HARQ process corresponding to the second downlink data can be the same HARQ process, and the HARQ process identifier of the first HARQ process is the same as that of the second HARQ process. The second new data indicator (NDI) included in the second scheduling information is not flipped relative to the first new data indicator included in the first scheduling information.

[0094] The second downlink data scheduled by the network device in the second carrier is either initial transmission data or new transmission data. If the first HARQ process corresponding to the first downlink data and the second HARQ process corresponding to the second downlink data are the same HARQ process, the second new data indication is flipped relative to the first new data indication.

[0095] Accordingly, the terminal device can determine whether the received downlink data is an initial transmission or a retransmission using the following methods:

[0096] If the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indicator (NDI) included in the second scheduling information has not been overridden relative to the first new data indicator included in the first scheduling information, then the second downlink data is retransmission data of the first downlink data.

[0097] Alternatively, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication has been flipped relative to the first new data indication, then the second downlink data is either initial transmission data or new transmission data, and in this case, the second downlink data is different from the first downlink data.

[0098] Alternatively, if the first HARQ process and the second HARQ process are different HARQ processes, then the second downlink data is either initial transmission data or newly transmitted data, and in this case, the second downlink data is different from the first downlink data.

[0099] Of the bits corresponding to the scheduling information, one bit can be used to indicate a new data indication. For example, if the first new data indication is 0 and the second new data indication is 1, it means that the second new data indication has been flipped relative to the first new data indication. Alternatively, if the first new data indication is 1 and the second new data indication is 0, it means that the second new data indication has been flipped relative to the first new data indication. Another example is if both the first and second new data indications are 1, it means that the second new data indication has not been flipped relative to the first new data indication. Finally, if both the first and second new data indications are 0, it means that the second new data indication has not been flipped relative to the first new data indication.

[0100] The first scheduling information may also indicate a first HARQ process identifier, and the second scheduling information may also indicate a second HARQ process identifier. If the first HARQ process identifier and the second HARQ process identifier are the same, then the first HARQ process and the second HARQ process are the same HARQ process; if the first HARQ process identifier and the second HARQ process identifier are different, then the first HARQ process and the second HARQ process are different HARQ processes.

[0101] Optionally, the network device may also send a first signaling instruction to the terminal device, indicating that an HAQR entity or HARQ process group is maintained for a carrier group. The terminal device may maintain an HAQR entity or HARQ process group for each of the M carrier groups according to the first signaling instruction. If the network device does not send the first signaling instruction, the terminal device may maintain one HAQR entity or HARQ process group for one carrier.

[0102] Optionally, the network device can also send a second signaling message to the terminal device, indicating that an HAQR entity or HARQ process group is maintained for each carrier. If the terminal device maintains an HAQR entity or HARQ process group for a carrier group, after receiving the second signaling message, the terminal device can maintain an HAQR entity or HARQ process group for each carrier according to the second signaling message. Here, the carrier can refer to a downlink carrier.

[0103] The first and second signaling can be RRC signaling or other higher-level signaling, and this application does not limit them.

[0104] Based on the preceding description, as shown in Figure 3, the network device configures four downlink carriers for the terminal device: carrier 1, carrier 2, carrier 3, and carrier 4. These four carriers are divided into two carrier groups: carrier 1 and carrier 2 belong to the first carrier group; carrier 3 and carrier 4 belong to the second carrier group. These two carrier groups can be preset or specified by the network device.

[0105] The terminal device can configure a first HARQ entity for the first carrier group. The first HARQ entity maintains a first HARQ process group, meaning the first carrier group is associated with the first HARQ process group. Similarly, the terminal device can configure a second HARQ entity for the second carrier group. The second HARQ entity maintains a second HARQ process group, meaning the second carrier group is associated with the second HARQ process group. Therefore, carriers 1 and 2 are associated with the HARQ processes in the first HARQ process group; carriers 3 and 4 are associated with the HARQ processes in the second HARQ process group.

[0106] Carrier 1 and carrier 3 can be combined as a carrier aggregation. In time slot 1, the network device sends the first DCI to the terminal device on carrier 1. The first DCI schedules the terminal device to receive the first TB on carrier 1 in time slot 3. The first TB corresponds to the first HARQ process in the first HARQ process group. The first DCI also includes the first NDI (field).

[0107] Optionally, in time slot 1, the network device can also schedule the terminal device to receive downlink TB on carrier 3 in time slot 3, the specific process of which will not be elaborated here.

[0108] Furthermore, the network device can also instruct the terminal device to switch from carrier 1 to carrier 2 to receive downlink data. In this case, carrier 2 and carrier 3 can be combined as a single carrier aggregation. The following description assumes that the terminal device completes the switch from carrier 1 to carrier 2 before time slot 4.

[0109] In time slot 4, the network device sends a second DCI to the terminal device on carrier 2. The second DCI schedules the terminal device to receive the second TB on carrier 2 in time slot 6. The second DCI also includes a second NDI (field). For the terminal device, after determining that it is switching from carrier 1 to carrier 2, the terminal device can determine that carrier 2 is associated with the first HARQ process group.

[0110] Optionally, in time slot 4, the network equipment can also schedule the terminal equipment to receive downlink TB on carrier 3 in time slot 6; the specific process will not be described in detail.

[0111] Optionally, in implementation method one, the second TB is a retransmission of the first TB, the HARQ process identifier included in the first DCI is the same as the HARQ process identifier included in the second DCI, and the second NDI is not flipped relative to the first NDI.

[0112] Accordingly, if the terminal device determines that the HARQ process identifier included in the first DCI is the same as the HARQ process identifier included in the second DCI (that is, the HARQ process corresponding to the first TB is the same as the HARQ process corresponding to the second TB), and determines that the second NDI has not flipped relative to the first NDI, then it can be determined that the second TB is a retransmission of the first TB.

[0113] Optionally, in the second implementation, the second TB is either the initial transmission or the new transmission, the HARQ process identifier included in the first DCI is the same as the HARQ process identifier included in the second DCI, and the second NDI is flipped relative to the first NDI.

[0114] Accordingly, if the terminal device determines that the HARQ process identifier included in the first DCI is the same as the HARQ process identifier included in the second DCI (that is, the HARQ process corresponding to the first TB is the same as the HARQ process corresponding to the second TB), and determines that the second NDI has been flipped relative to the first NDI, then it can be determined that the second TB is the initial transmission or the new transmission, that is, the first TB and the second TB are different.

[0115] Optionally, in implementation method three, the second TB is either the initial transmission or the new transmission, and the HARQ process identifier included in the first DCI is different from the HARQ process identifier included in the second DCI.

[0116] Accordingly, if the terminal device determines that the HARQ process identifier included in the first DCI is different from the HARQ process identifier included in the second DCI (that is, the HARQ process corresponding to the first TB is different from the HARQ process corresponding to the second TB), then it can be determined that the second TB is the initial transmission or the new transmission, that is, the first TB and the second TB are different.

[0117] Example 2: The terminal device can maintain M HARQ entities, where M is preset, indicated by the network device, or determined by the terminal device. The M HARQ entities maintain M HARQ process groups that correspond one-to-one with M carriers; that is, one carrier among the M carriers is associated with one HARQ process group among the M HARQ process groups. The M carriers can be downlink carriers, configured by the network device, and include a first carrier and a second carrier.

[0118] Where M is less than or equal to X, the meaning of X can be referred to the previous description, and will not be repeated here.

[0119] When a terminal device performs a carrier switch, the HARQ process group associated with the carrier before the switch is associated with the carrier after the switch. For example, the first carrier is associated with the first HARQ process group. Taking the terminal device switching from the first carrier to the second carrier as an example, the terminal device will use the first HARQ process group associated with the first carrier as the HARQ process group associated with the second carrier. In this way, the terminal device does not need to maintain a new HARQ entity for the second carrier.

[0120] Optionally, the network device may also send handover indication information, indicating a handover from the first carrier to the second carrier. Optionally, the handover indication information may also indicate that the first HARQ process group associated with the first carrier is used as the HARQ process group associated with the second carrier.

[0121] During carrier switching, when the initial transmission and retransmission of the same downlink data are transmitted on the carrier before and after the switching respectively, the HARQ process identifier of the HARQ process corresponding to the downlink data remains unchanged and the value of the new data indication is the same, that is, the new data indication does not flip.

[0122] For example, the second downlink data scheduled by the network device in the second carrier is retransmission data of the first downlink data scheduled by the network device in the first carrier. The first HARQ process corresponding to the first downlink data and the second HARQ process corresponding to the second downlink data can be the same HARQ process, and the HARQ process identifier of the first HARQ process is the same as that of the second HARQ process. The second new data indication included in the second scheduling information is not flipped relative to the first new data indication included in the first scheduling information.

[0123] The second downlink data scheduled by the network device in the second carrier is either initial transmission data or new transmission data. If the first HARQ process corresponding to the first downlink data and the second HARQ process corresponding to the second downlink data are the same HARQ process, the second new data indication is flipped relative to the first new data indication.

[0124] Accordingly, the terminal device can use the method in Example 1 to determine whether the received downlink data is an initial transmission or a retransmission; the specific process will not be elaborated further.

[0125] Optionally, the network device may also send a third signaling message to the terminal device, instructing the HARQ process group associated with the carrier before the handover to be associated with the carrier after the handover. If the network device does not send the third signaling message, the terminal device may maintain one HAQR entity or HARQ process group for a carrier.

[0126] Optionally, the network device can also send a fourth signaling message to the terminal device, indicating that a HAQR entity or HARQ process group is maintained for each carrier. If the terminal device associates the HARQ process group associated with the carrier before the handover to the carrier after the handover, after receiving the fourth signaling message, the terminal device can maintain a HAQR entity or HARQ process group for each carrier according to the fourth signaling message. Here, the carrier can refer to a downlink carrier.

[0127] The third and fourth signaling messages can be RRC signaling or other higher-level signaling; this application does not limit them.

[0128] Based on the preceding description, as shown in Figure 4, the network device configures four downlink carriers for the terminal device, namely carrier 1, carrier 2, carrier 3 and carrier 4.

[0129] The terminal device can configure a first HARQ entity for carrier 1. The first HARQ entity maintains a first HARQ process group, meaning carrier 1 is associated with the first HARQ process group. The terminal device can configure a second HARQ entity for carrier group 3. The second HARQ entity maintains a second HARQ process group, meaning carrier 3 is associated with the first HARQ process group. The terminal device does not configure HARQ entities for carriers 2 and 4.

[0130] If the network device instructs the terminal device to switch from carrier 1 to carrier 2, then carrier 2 is associated with the first HARQ process group; if the network device instructs the terminal device to switch from carrier 3 to carrier 4, then carrier 4 is associated with the second HARQ process group; and so on for other cases.

[0131] Carrier 1 and carrier 3 can be combined as a carrier aggregation. In time slot 1, the network device sends a first DCI to the terminal device on carrier 1. The first DCI schedules the terminal device to receive a first TB on carrier 1 in time slot 3. The first TB corresponds to the first HARQ process in the first HARQ process group. The first DCI includes the HARQ process identifier of the first HARQ process and the first NDI.

[0132] Optionally, in time slot 1, the network device can also schedule the terminal device to receive downlink TB on carrier 3 in time slot 3, the specific process of which will not be elaborated here.

[0133] Furthermore, the network device can also instruct the terminal device to switch from carrier 1 to carrier 2 to receive downlink data. In this case, carrier 2 and carrier 3 can be combined as a single carrier aggregation. The following description assumes that the terminal device completes the switch from carrier 1 to carrier 2 before time slot 4.

[0134] In time slot 4, the network device sends a second DCI to the terminal device on carrier 2. The second DCI schedules the terminal device to receive the third TB on carrier 2 in time slot 6. The second DCI includes the HARQ process identifier of the first HARQ process and the second NDI. For the terminal device, after determining that it is switching from carrier 1 to carrier 2, the terminal device can determine that carrier 2 is associated with the first HARQ process group.

[0135] Optionally, in time slot 4, the network device can also schedule the terminal device to receive downlink TB on carrier 3 in time slot 6; the specific process will not be described in detail here.

[0136] Optionally, in implementation method one, the second TB is a retransmission of the first TB, the HARQ process identifier included in the first DCI is the same as the HARQ process identifier included in the second DCI, and the second NDI is not flipped relative to the first NDI.

[0137] Accordingly, if the terminal device determines that the HARQ process identifier included in the first DCI is the same as the HARQ process identifier included in the second DCI (that is, the HARQ process corresponding to the first TB is the same as the HARQ process corresponding to the second TB), and determines that the second NDI has not flipped relative to the first NDI, then it can be determined that the second TB is a retransmission of the first TB.

[0138] Optionally, in the second implementation, the second TB is either the initial transmission or the new transmission, the HARQ process identifier included in the first DCI is the same as the HARQ process identifier included in the second DCI, and the second NDI is flipped relative to the first NDI.

[0139] Accordingly, if the terminal device determines that the HARQ process identifier included in the first DCI is the same as the HARQ process identifier included in the second DCI (that is, the HARQ process corresponding to the first TB is the same as the HARQ process corresponding to the second TB), and determines that the second NDI has been flipped relative to the first NDI, then it can be determined that the second TB is the initial transmission or the new transmission, that is, the first TB and the second TB are different.

[0140] Optionally, in implementation method three, the second TB is either the initial transmission or the new transmission, and the HARQ process identifier included in the first DCI is different from the HARQ process identifier included in the second DCI.

[0141] Accordingly, if the terminal device determines that the HARQ process identifier included in the first DCI is different from the HARQ process identifier included in the second DCI (that is, the HARQ process corresponding to the first TB is different from the HARQ process corresponding to the second TB), then it can be determined that the second TB is the initial transmission or the new transmission, that is, the first TB and the second TB are different.

[0142] It is understood that, in order to achieve the functions in the above embodiments, the terminal device or network device includes hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0143] The following are schematic diagrams of possible communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of terminal devices or network devices in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0144] As shown in Figure 5, the communication device 500 includes a processing unit 510 and a communication unit 520. The communication device 500 is used to implement the functions of the terminal device or network device in the various method embodiments shown above.

[0145] When the communication device 500 is used to implement the functions of a terminal device:

[0146] The processing unit is configured to receive first scheduling information from a network device via a communication unit on a first carrier; the first scheduling information is used to schedule first downlink data.

[0147] The processing unit is configured to receive second scheduling information from the network device via a communication unit on a second carrier; the second scheduling information is used to schedule second downlink data.

[0148] Wherein, the first downlink data corresponds to the first Hybrid Automatic Repeat Request (HARQ) process, the second downlink data corresponds to the second HARQ process, the first HARQ process and the second HARQ process belong to the first HARQ process group, and the first HARQ process group is maintained by the first HARQ entity.

[0149] In one implementation, the first carrier and the second carrier belong to a first carrier group, the first carrier group is associated with the first HARQ process group, and the carriers in the first carrier group are associated with the HARQ processes in the first HARQ process group.

[0150] In one implementation, the communication unit is further configured to:

[0151] Receive first information from the network device, the first information indicating M carrier groups, one carrier group including at least one carrier, the M carrier groups including the first carrier group, M being an integer greater than 0; determine M HARQ process groups associated with the M carrier groups, the M HARQ process groups including the first HARQ process group.

[0152] In one implementation, the processing unit is further configured to:

[0153] The first HARQ process group associated with the first carrier is designated as the HARQ process group associated with the second carrier.

[0154] In one implementation, the first scheduling information further includes a first new data indication, and the second scheduling information further includes a second new data indication; wherein, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication has not been flipped relative to the first new data indication, then the second downlink data is retransmission data of the first downlink data;

[0155] Alternatively, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication has been flipped relative to the first new data indication, then the second downlink data is the initial transmission data.

[0156] In one implementation, the communication unit is further configured to:

[0157] The system receives a handover instruction from the network device, the handover instruction indicating a switch from the first carrier to the second carrier.

[0158] When the communication device 500 is used to implement the functions of a network device:

[0159] The processing unit is configured to send first scheduling information to the terminal device via a communication unit on a first carrier; the first scheduling information is used to schedule first downlink data.

[0160] The processing unit is configured to send second scheduling information to the terminal device via a communication unit on a second carrier; the second scheduling information is used to schedule second downlink data.

[0161] Wherein, the first downlink data corresponds to the first Hybrid Automatic Repeat Request (HARQ) process, the second downlink data corresponds to the second HARQ process, the first HARQ process and the second HARQ process belong to the first HARQ process group, and the first HARQ process group is maintained by the first HARQ entity.

[0162] In one implementation, the first carrier and the second carrier belong to a first carrier group, and the carriers in the first carrier group are associated with the first HARQ process group.

[0163] In one implementation, the communication unit is further configured to:

[0164] Send first information to the terminal device, the first information indicating M carrier groups, each carrier group including at least one carrier, the M carrier groups including the first carrier group, where M is an integer greater than 0.

[0165] In one implementation, the first scheduling information further includes a first new data indication, and the second scheduling information further includes a second new data indication;

[0166] Wherein, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication has not been flipped relative to the first new data indication, then the second downlink data is the retransmission data of the first downlink data;

[0167] Alternatively, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication has been flipped relative to the first new data indication, then the second downlink data is the initial transmission data.

[0168] In one implementation, the communication unit is further configured to:

[0169] The terminal device is sent a handover instruction message, which indicates a handover from the first carrier to the second carrier.

[0170] More detailed descriptions of the processing unit 510 and the communication unit 520 can be obtained directly from the relevant descriptions in the above method embodiments, and will not be repeated here.

[0171] It should be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, while others are implemented in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the device. Moreover, these units can be fully or partially integrated together, or implemented independently. The processing element here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, the operations or units described above can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0172] In one example, a unit in any of the above devices can be one or more integrated circuits configured to implement the methods described above, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor capable of calling programs. Furthermore, these units can be integrated together to implement a system-on-a-chip (SOC).

[0173] The receiving unit described above is an interface circuit of the device, used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is an interface circuit for the chip to receive signals from other chips or devices. The transmitting unit described above is an interface circuit of the device, used to transmit signals to other devices. For example, when the device is implemented as a chip, the transmitting unit is an interface circuit for the chip to transmit signals to other chips or devices.

[0174] As another possible product form, the terminal device or network device of this application embodiment can be implemented by a general bus architecture. For ease of explanation, refer to FIG6, which is a schematic diagram of the structure of a communication device 600 provided in an embodiment of this application. The communication device 600 includes a processor 601 and a transceiver 602. The communication device 600 can be a terminal device, or a chip or chip system therein; or, the communication device 600 can be a network device, or a chip or module therein. FIG6 only shows the main components of the communication device 600. In addition to the processor 601 and transceiver 602, the communication device 600 may further include a memory 603 and input / output devices (not shown in the figure).

[0175] Optionally, the processor 601 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 603 is mainly used to store software programs and data. The transceiver 602 may include radio frequency (RF) circuitry and an antenna. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0176] Optionally, the processor 601, transceiver 602, and memory 603 can be connected via a communication bus.

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

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

[0179] In some embodiments, those skilled in the art will recognize that the above-described communication device 500 can take the form of the communication device 600 shown in FIG6 in terms of hardware implementation.

[0180] As an example, the function / implementation process of the processing unit 510 in FIG5 can be implemented by the processor 601 in the communication device 600 shown in FIG6 calling the computer execution instructions stored in the memory 603. The function / implementation process of the communication unit 520 in FIG5 can be implemented by the transceiver 602 in the communication device 600 shown in FIG6.

[0181] As another possible product form, the terminal device or network device in this application may adopt the composition structure shown in FIG. 7, or include the components shown in FIG. 7. FIG. 7 is a schematic diagram of the composition of a communication device 700 provided in this application.

[0182] As shown in Figure 7, the communication device 700 includes at least one processor 701. Optionally, the communication device also includes a communication interface 702.

[0183] When the relevant program instructions are executed in the at least one processor 701, the communication device 700 can implement the methods and any possible designs provided in any of the foregoing embodiments. Alternatively, the processor 701 can implement the methods and any possible designs provided in any of the foregoing embodiments through logic circuits or executable code instructions.

[0184] The communication interface 702 can be used to receive program instructions and transmit them to the processor, or it can be used for communication interaction between the communication device 700 and other communication devices, such as exchanging control signaling and / or service data. For example, the communication interface 702 can be used to receive signals from other devices besides the communication device 700 and transmit them to the processor 701, or to send signals from the processor 701 to other communication devices besides the communication device 700.

[0185] Optionally, the communication interface 702 can be a code and / or data read / write interface circuit, or the communication interface 702 can be a signal transmission interface circuit between a communication processor and a transceiver, or a chip pin.

[0186] Optionally, the communication device 700 may further include at least one memory 703, which can be used to store the required program instructions and / or data. It should be noted that the memory 703 may exist independently of the processor 701 or may be integrated with the processor 701. The memory 703 may be located within or outside the communication device 700, without limitation.

[0187] Optionally, the communication device 700 may further include a power supply circuit 704, which can be used to power the processor 701. The power supply circuit 704 may be located in the same chip as the processor 701, or in a separate chip outside the chip containing the processor 701.

[0188] Optionally, the communication device 700 may also include a bus, through which the various parts of the communication device 700 can be interconnected.

[0189] In some embodiments, those skilled in the art will recognize that the communication device 500 shown in FIG5 can take the form of the communication device 700 shown in FIG7 in terms of hardware implementation.

[0190] As an example, the function / implementation process of the processing unit 510 in FIG5 can be implemented by the processor 701 in the communication device 700 shown in FIG7 calling computer execution instructions stored in the memory 703. The function / implementation process of the communication unit 520 in FIG5 can be implemented by the communication interface 702 in the communication device 700 shown in FIG7.

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

[0192] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules (such as radio frequency modules or antennas) in the terminal, which is information sent to the terminal by the base station; or, the terminal chip sends information to other modules (such as radio frequency modules or antennas) in the terminal, which is information sent to the base station by the terminal.

[0193] When the aforementioned communication device is a module applied to a base station, the base station module implements the functions of the base station in the above method embodiments. The base station module receives information from other modules (such as radio frequency modules or antennas) in the base station, information sent by the terminal to the base station; or, the base station module sends information to other modules (such as radio frequency modules or antennas) in the base station, information sent by the base station to the terminal. Here, the base station module can be the baseband chip of the base station, or a DU (Digital Unit) or other modules. The DU can be a DU under an Open Radio Access Network (O-RAN) architecture.

[0194] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0195] Based on the same technical concept, embodiments of this application also provide a computer-readable storage medium storing instructions, which may also be referred to as computer programs, computer program code, etc. The instructions, when executed on a computer, cause the computer to perform the functions of the terminal device or network device described in the above method embodiments.

[0196] Based on the same technical concept, this application also provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run by a communication device, the method steps executed by the terminal device or network device in the above method embodiments are executed.

[0197] Based on the same concept, embodiments of this application also provide a chip, which may include a processor and a memory (or the chip may be coupled to the memory). The chip executes program instructions in the memory to perform the methods provided in the above embodiments. Here, "coupling" refers to two components being directly or indirectly connected to each other; for example, coupling can refer to an electrical connection between two components.

[0198] Based on the same concept, embodiments of this application also provide a communication system, including a terminal device and a network device. The terminal device is used to implement the functions of the terminal device in the foregoing embodiments; the network device is used to implement the functions of the network device in the foregoing embodiments.

[0199] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. Of course, the processor and storage medium can also exist as discrete components in the base station or terminal.

[0200] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0201] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0202] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0203] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0204] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0205] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method characterized by comprising: Comprising: receiving, from a network device, first scheduling information on a first carrier; the first scheduling information is used for scheduling first downlink data; receiving, from the network device, second scheduling information on a second carrier; the second scheduling information is used for scheduling second downlink data; wherein the first downlink data corresponds to a first hybrid automatic repeat request (HARQ) process, the second downlink data corresponds to a second HARQ process, the first HARQ process and the second HARQ process belong to a first HARQ process group, and the first HARQ process group is maintained by a first HARQ entity.

2. The method of claim 1, wherein, The first carrier and the second carrier belong to a first carrier group, the first carrier group is associated with the first HARQ process group, and a carrier in the first carrier group is associated with a HARQ process in the first HARQ process group.

3. The method of claim 2, wherein, The method further comprises: receiving first information from the network device, the first information indicating M carrier groups, one of the carrier groups including at least one carrier, and the M carrier groups including the first carrier group, M being an integer greater than 0; determining M HARQ process groups associated with the M carrier groups, the M HARQ process groups including the first HARQ process group.

4. The method of claim 3, wherein, M is less than or equal to X, X being a maximum number of downlink carriers supported by the terminal device.

5. The method of claim 1, wherein, After the second scheduling information on the second carrier is received from the network device, the method further comprises: regarding the first HARQ process group associated with the first carrier as a HARQ process group associated with the second carrier.

6. The method according to any one of claims 1 to 5, characterized in that, The first scheduling information further includes a first new data indication, and the second scheduling information further includes a second new data indication; wherein, if the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication has not been flipped relative to the first new data indication, the second downlink data is retransmission data of the first downlink data; or, if the first HARQ process and the second HARQ process are the same HARQ process and the second new data indication has been flipped relative to the first new data indication, the second downlink data is initial transmission data.

7. The method according to any one of claims 1 to 6, characterized in that, The method further comprises: receiving switching indication information from the network device, the switching indication information indicating switching from the first carrier to the second carrier.

8. The method of claim 7, wherein, The switching indication information further indicates regarding the first HARQ process group associated with the first carrier as a HARQ process group associated with a second carrier.

9. A communication method characterized by comprising: Comprising: sending, to a terminal device, first scheduling information on a first carrier; the first scheduling information is used for scheduling first data; sending, to the terminal device, second scheduling information on a second carrier; the second scheduling information is used for scheduling second data; wherein the first data corresponds to a first hybrid automatic repeat request (HARQ) process, the second data corresponds to a second HARQ process, the first HARQ process and the second HARQ belong to a first HARQ process group, and the first HARQ process group is maintained by the first HARQ entity.

10. The method of claim 9, wherein, The first carrier and the second carrier belong to a first carrier group, and carriers in the first carrier group are associated with the first HARQ process group.

11. The method of claim 10, wherein, The method further comprises: sending first information to the terminal device, the first information indicating M carrier groups, one of the carrier groups including at least one carrier, the M carrier groups including the first carrier group, and M being an integer greater than 0.

12. The method of claim 11, wherein, M is less than or equal to X, X being a maximum number of downlink carriers supported by the terminal device.

13. The method according to any one of claims 9 to 12, characterized in that, The first scheduling information further includes first new data indication, and the second scheduling information further includes second new data indication. If the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication does not flip relative to the first new data indication, the second downlink data is retransmission data of the first downlink data. Or, if the first HARQ process and the second HARQ process are the same HARQ process, and a flip occurs in the second new data indication relative to the first new data indication, the second downlink data is initial transmission data.

14. The method according to any one of claims 1 to 13, characterized in that, The method further comprises: sending switching indication information to the terminal device, the switching indication information indicating switching from the first carrier to the second carrier.

15. The method of claim 14, wherein, The switching indication information further indicates that the first HARQ process group associated with the first carrier is used as a HARQ process group associated with the second carrier.

16. A communications device, characterized by Comprise: a processing unit configured to receive, through a communication unit, first scheduling information from a network device on a first carrier; The first scheduling information is used to schedule first downlink data. The processing unit is configured to receive, through the communication unit, second scheduling information from the network device on a second carrier; the second scheduling information is used to schedule second downlink data. The first downlink data corresponds to a first hybrid automatic repeat request (HARQ) process, and the second downlink data corresponds to a second HARQ process, the first HARQ process and the second HARQ process belong to a first HARQ process group, and the first HARQ process group is maintained by a first HARQ entity.

17. The apparatus of claim 16, wherein, The first carrier and the second carrier belong to a first carrier group, and carriers in the first group are associated with the first HARQ process group.

18. The apparatus of claim 17, wherein, The communication unit is further configured to: receive first information from the network device, the first information indicating M carrier groups, one of the carrier groups including at least one of the carriers, the M carrier groups including the first carrier group, and M being an integer greater than 1. Determine M HARQ process groups associated with the M carrier groups, the M HARQ process groups including the first HARQ process group.

19. The apparatus of claim 16, wherein, The processing unit is further configured to: use the first HARQ process group associated with the first carrier as a HARQ process group associated with the second carrier.

20. The apparatus of any one of claims 16 to 19, wherein, The first scheduling information further includes first new data indication, and the second scheduling information further includes the second new data indication. If the first HARQ process and the second HARQ process are the same HARQ process, and the second new data indication does not flip relative to the first new data indication, the second downlink data is retransmission data of the first downlink data. Or, if the first HARQ process and the second HARQ process are the same HARQ process, and flipping occurs in the second new data indication relative to the first new data indication, the second downlink data is initial transmission data.

21. The apparatus of any one of claims 16 to 20, wherein, The communication unit is further configured to: receive switching indication information from the network device, the switching indication information indicating switching from the first carrier to the second carrier.

22. A communications device, characterized by comprising: a processing unit configured to send first scheduling information to a terminal device via a communication unit on a first carrier; the first scheduling information is used for scheduling first downlink data; the processing unit is configured to send second scheduling information to the terminal device via the communication unit on a second carrier; the second scheduling information is used for scheduling second downlink data; wherein the first downlink data corresponds to a first hybrid automatic repeat request (HARQ) process, the second downlink data corresponds to a second HARQ process, the first HARQ process and the second HARQ process belong to a first HARQ process group, and the first HARQ process group is maintained by a first HARQ entity.

23. The apparatus of claim 22, wherein, The first carrier and the second carrier belong to a first carrier group, and the carriers in the first carrier group are associated with the first HARQ process group.

24. The apparatus of claim 23, wherein, The communication unit is further configured to: send first information to the terminal device, the first information indicating M carrier groups, one of the carrier groups including at least one carrier, the M carrier groups including the first carrier group, and M being an integer greater than 0.

25. The apparatus of any one of claims 22 to 24, wherein, The first scheduling information further includes a first new data indication, and the second scheduling information further includes a second new data indication; If the first HARQ process and the second HARQ process are the same HARQ process, the second new data indication does not flip relative to the first new data indication, and the second downlink data is retransmission data of the first downlink data. Or, the first HARQ process and the second HARQ process are the same HARQ process, flipping occurs in the second new data indication relative to the first new data indication, and the second downlink data is initial transmission data.

26. The apparatus of any one of claims 22 to 25, wherein, The communication unit is further configured to: send switching indication information to the terminal device, the switching indication information indicating switching from the first carrier to the second carrier.

27. A communications device, characterized by comprising at least one processor; and a communication interface connected in communication with the at least one processor; the at least one processor, by executing instructions stored in a memory, causes the method of any one of claims 1-8 to be performed, or causes the method of any one of claims 9-15 to be performed.

28. A computer-readable storage medium, characterized in that, The computer program or instructions are stored in a memory, and when the computer program or instructions are run on a computer, the computer implements the method of any one of claims 1-15.

29. A computer program product, characterised in that, When the computer reads and executes the computer program product, the method as claimed in any one of claims 1 to 15 is caused to be performed.

Images