CN117204087A

CN117204087A - Cross-carrier retransmission method and device, terminal equipment and network equipment

Info

Publication number: CN117204087A
Application number: CN202180097393.0A
Authority: CN
Inventors: 王淑坤; 林雪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-07-19
Filing date: 2021-07-19
Publication date: 2023-12-08
Also published as: WO2023000141A1

Abstract

The embodiment of the application provides a method and a device for cross-carrier retransmission, terminal equipment and network equipment, wherein the method comprises the following steps: the method comprises the steps that terminal equipment receives first configuration information sent by network equipment, wherein the first configuration information is used for determining cross-carrier retransmission configuration; and the terminal equipment performs cross-carrier retransmission operation based on the cross-carrier retransmission configuration, wherein the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.

Description

Cross-carrier retransmission method and device, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to a method and a device for cross-carrier retransmission, terminal equipment and network equipment.

Background

The carrier aggregation can provide a larger bandwidth for the service, thereby improving the throughput of the service. In carrier aggregation, each carrier corresponds to a hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) entity, each HARQ entity maintaining a respective HARQ process.

At present, HARQ retransmission can only be performed in the same carrier, which can cause HARQ retransmission delay and even cause the problem that HARQ retransmission cannot be realized in some scenes.

Disclosure of Invention

The embodiment of the application provides a method and a device for cross-carrier retransmission, terminal equipment, network equipment, a chip, a computer readable storage medium, a computer program product and a computer program.

The method for cross-carrier retransmission provided by the embodiment of the application comprises the following steps:

the method comprises the steps that terminal equipment receives first configuration information sent by network equipment, wherein the first configuration information is used for determining cross-carrier retransmission configuration;

and the terminal equipment performs cross-carrier retransmission operation based on the cross-carrier retransmission configuration, wherein the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.

the network equipment sends first configuration information to the terminal equipment, wherein the first configuration information is used for determining cross-carrier retransmission configuration; the cross-carrier retransmission is configured to perform cross-carrier retransmission operation by the terminal equipment, and the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.

The device for cross-carrier retransmission provided by the embodiment of the application is applied to terminal equipment and comprises the following components:

a receiving unit, configured to receive first configuration information sent by a network device, where the first configuration information is used to determine a cross-carrier retransmission configuration;

And the retransmission unit is used for carrying out cross-carrier retransmission operation based on the cross-carrier retransmission configuration, wherein the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.

The device for cross-carrier retransmission provided by the embodiment of the application is applied to network equipment, and comprises the following components:

a sending unit, configured to send first configuration information to a terminal device, where the first configuration information is used to determine a cross-carrier retransmission configuration; the cross-carrier retransmission is configured to perform cross-carrier retransmission operation by the terminal equipment, and the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.

The terminal equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method of cross-carrier retransmission.

The network equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method of cross-carrier retransmission.

The chip provided by the embodiment of the application is used for realizing the method for cross-carrier retransmission.

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device installed with the chip executes the method of cross-carrier retransmission.

The computer readable storage medium provided by the embodiment of the application is used for storing a computer program, and the computer program enables a computer to execute the method of cross-carrier retransmission.

The computer program product provided by the embodiment of the application comprises computer program instructions, wherein the computer program instructions enable a computer to execute the method of cross-carrier retransmission.

The computer program provided by the embodiment of the application, when running on a computer, causes the computer to execute the method of cross-carrier retransmission.

According to the technical scheme, in carrier aggregation, the network equipment enables the terminal equipment to perform cross-carrier retransmission operation by configuring cross-carrier retransmission configuration, so that the efficiency of the cross-carrier retransmission is improved, and the time delay of data retransmission is reduced.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application;

fig. 2 is a diagram of a downlink protocol stack frame in a carrier aggregation scenario according to an embodiment of the present application;

fig. 3 is an uplink protocol stack structure diagram under a carrier aggregation scenario according to an embodiment of the present application;

fig. 4 is a flowchart of a method for cross-carrier retransmission according to an embodiment of the present application;

fig. 5 is a schematic diagram of an associated carrier supporting cross-carrier retransmission according to an embodiment of the present application;

fig. 6 is a schematic diagram ii of an associated carrier supporting cross-carrier retransmission according to an embodiment of the present application;

fig. 7 is a schematic diagram of the structural composition of a device for cross-carrier retransmission according to an embodiment of the present application;

fig. 8 is a schematic diagram ii of a structural composition of a device for cross-carrier retransmission according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 10 is a schematic block diagram of a chip of an embodiment of the application;

fig. 11 is a schematic block diagram of a communication system provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

As shown in fig. 1, communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air interface. Multi-service transmission is supported between terminal device 110 and network device 120.

It should be understood that embodiments of the present application are illustrated by way of example only with respect to communication system 100, and embodiments of the present application are not limited thereto. That is, the technical solution of the embodiment of the present application may be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), internet of things (Internet of Things, ioT) systems, narrowband internet of things (Narrow Band Internet of Things, NB-IoT) systems, enhanced Machine-type-Type Communications (eMTC) systems, 5G communication systems (also known as New Radio (NR) communication systems), or future communication systems, etc.

In the communication system 100 shown in fig. 1, the network device 120 may be an access network device in communication with the terminal device 110. The access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., UEs) located within the coverage area.

The network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long term evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, or a base station (gNB) in a NR system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 may be a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

Terminal device 110 may be any terminal device including, but not limited to, a terminal device that employs a wired or wireless connection with network device 120 or other terminal devices.

For example, the terminal device 110 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, an IoT device, a satellite handset, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handset with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

The terminal Device 110 may be used for Device-to-Device (D2D) communication.

The wireless communication system 100 may further comprise a core network device 130 in communication with the base station, which core network device 130 may be a 5G core,5gc device, e.g. an access and mobility management function (Access and Mobility Management Function, AMF), further e.g. an authentication server function (Authentication Server Function, AUSF), further e.g. a user plane function (User Plane Function, UPF), further e.g. a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be a packet core evolution (Evolved Packet Core, EPC) device of the LTE network, for example a session management function+a data gateway (Session Management Function + Core Packet Gateway, smf+pgw-C) device of the core network. It should be appreciated that SMF+PGW-C may perform the functions performed by both SMF and PGW-C. In the network evolution process, the core network device may also call other names, or form new network entities by dividing the functions of the core network, which is not limited in this embodiment of the present application.

Communication may also be achieved by establishing connections between various functional units in the communication system 100 through a next generation Network (NG) interface.

For example, the terminal device establishes an air interface connection with the access network device through an NR interface, and is used for transmitting user plane data and control plane signaling; the terminal equipment can establish control plane signaling connection with AMF through NG interface 1 (N1 for short); an access network device, such as a next generation radio access base station (gNB), can establish a user plane data connection with a UPF through an NG interface 3 (N3 for short); the access network equipment can establish control plane signaling connection with AMF through NG interface 2 (N2 for short); the UPF can establish control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the UPF can interact user plane data with the data network through an NG interface 6 (N6 for short); the AMF may establish a control plane signaling connection with the SMF through NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (N7 for short).

Fig. 1 exemplarily illustrates one base station, one core network device, and two terminal devices, alternatively, the wireless communication system 100 may include a plurality of base station devices and each base station may include other number of terminal devices within a coverage area, which is not limited by the embodiment of the present application.

It should be noted that fig. 1 is only an exemplary system to which the present application is applicable, and of course, the method shown in the embodiment of the present application may be applicable to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship. It should also be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B. It should also be understood that "corresponding" mentioned in the embodiments of the present application may mean that there is a direct correspondence or an indirect correspondence between the two, may mean that there is an association between the two, and may also be a relationship between an instruction and an indicated, configured, or the like. It should also be understood that "predefined" or "predefined rules" mentioned in the embodiments of the present application may be implemented by pre-storing corresponding codes, tables or other manners in which related information may be indicated in devices (including, for example, terminal devices and network devices), and the present application is not limited to the specific implementation thereof. Such as predefined may refer to what is defined in the protocol. It should be further understood that, in the embodiment of the present application, the "protocol" may refer to a standard protocol in the field of communications, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited by the present application.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description describes related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the protection scope of the embodiments of the present application.

With the pursuit of speed, delay, high speed mobility, energy efficiency and diversity and complexity of future life business, the third generation partnership project (3 ^rd Generation Partnership Project,3 GPP) international standards organization began developing 5G. The main application scenario of 5G is: enhanced mobile Ultra-wideband (enhanced Mobile Broadband, emmbb), low latency high reliability communication (URLLC), large-scale Machine-based communication (mctc).

On the one hand, embbs still target users to obtain multimedia content, services and data, and their demand is growing very rapidly. On the other hand, since an eMBB may be deployed in different scenarios, such as indoors, urban, rural, etc., its capabilities and requirements are also quite different, so that detailed analysis must be performed in connection with a specific deployment scenario, not in general. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical characteristics of mctc include: high connection density, small data volume, delay insensitive traffic, low cost and long service life of the module, etc.

At early deployment of NRs, full NR coverage is difficult to acquire, so typical network coverage is wide area LTE coverage and island coverage mode of NRs. And a large amount of LTE is deployed below 6GHz, and the frequency spectrum below 6GHz which can be used for 5G is few. NR must study spectral applications above 6GHz while high-band coverage is limited and signal fading is fast. Meanwhile, in order to protect the mobile operators from early investment in LTE, a working mode of close cooperation (tight interworking) between LTE and NR is proposed.

To enable 5G network deployment and commercial applications as soon as possible, 3GPP first completes the first 5G release, EN-DC (LTE-NR Dual Connectivity). In EN-DC, an LTE base station (eNB) serves as a Master Node (MN), and an NR base station (gNB or EN-gNB) serves as a Secondary Node (SN), which is connected to an EPC core network. In the later stages of R15, other DC modes, namely NE-DC,5GC-EN-DC, NR DC will be supported. In NE-DC, NR base station is used as MN, eLTE base station is used as SN, and is connected with 5GC core network. In 5GC-EN-DC, an eLTE base station is used as MN, an NR base station is used as SN, and a 5GC core network is connected. In NR DC, NR base station is used as MN, NR base station is used as SN, and connected with 5GC core network.

In 5G, the maximum channel bandwidth may be 400MHZ (known as wideband carrier), which is a large bandwidth compared to the LTE maximum 20M bandwidth. To meet the high rate requirements, carrier aggregation (Carrier Aggregation, CA) techniques are supported in 5G. CA enables higher system peak rates by jointly scheduling and using resources on multiple member carriers (Component Carrier, CC) so that the NR system can support a larger bandwidth. Spectrum continuity according to the aggregated carriers can be divided into continuous carrier aggregation and discontinuous carrier aggregation; according to whether the frequency bands (bands) where the aggregated carriers are located are the same, the method is divided into Intra-band (Intra-band) carrier aggregation and inter-band (inter-band) carrier aggregation.

In CA there is and only one primary carrier (Primary Cell Component, PCC) providing RRC signaling connections, non-Access stratum (NAS) functionality, security, etc. The physical uplink control channel (Physical Downlink Control Channel, PUCCH) is present on and only on the PCC. In CA there may be one or more secondary carriers (Secondary Cell Component, SCC), which provide only additional radio resources. The PCC and the SCC are commonly referred to as Serving cells (Serving cells), where the cells on the PCC are primary cells (PCell) and the cells on the SCC are secondary cells (SCell).

Fig. 2 and fig. 3 are protocol stack diagrams in a carrier aggregation scenario, where fig. 2 is a protocol stack diagram for downlink, and fig. 3 is a protocol stack diagram for uplink, and it can be seen that in carrier aggregation, all carriers share one medium access control (Media Access Control, MAC) entity, and each carrier corresponds to one HARQ entity. Each HARQ entity maintains a respective plurality of HARQ processes (HARQ processes).

Currently, for a data (such as a Transport Block (TB)), if the data is initially transmitted on an HARQ entity corresponding to a carrier, a retransmission corresponding to the data should also be transmitted on the HARQ entity corresponding to the carrier, and the HARQ process corresponding to the initial transmission is the same as the HARQ process corresponding to the retransmission, that is, the HARQ retransmission across carriers is not supported.

For a New Radio-Unlicensed (NR-U) scenario, when the NR-U carrier is used as one carrier for carrier aggregation, if the NR-U carrier does not preempt a channel, it may cause a HARQ retransmission on the NR-U carrier to be sent with delay.

For a time division duplex (Time Division Duplex, TDD) scenario, HARQ retransmission delay may also result if the downlink subframes of the TDD carrier corresponding to HARQ retransmissions are separated by a larger number of subframes relative to the downlink subframes corresponding to the initial transmissions.

For this reason, the following technical solutions of the embodiments of the present application are provided. The technical scheme of the embodiment of the application supports cross-carrier retransmission and solves the problem of data transmission delay.

It should be noted that, the "retransmission" described in the embodiment of the present application may be, but is not limited to, the "HARQ retransmission".

In order to facilitate understanding of the technical solution of the embodiments of the present application, the technical solution of the present application is described in detail below through specific embodiments. The above related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application. Embodiments of the present application include at least some of the following.

Fig. 4 is a flowchart of a method for cross-carrier retransmission according to an embodiment of the present application, as shown in fig. 4, where the method for cross-carrier retransmission includes the following steps:

Step 401: the network equipment sends first configuration information to the terminal equipment, and the terminal equipment receives the first configuration information sent by the network equipment, wherein the first configuration information is used for determining cross-carrier retransmission configuration.

Step 402: and the terminal equipment performs cross-carrier retransmission operation based on the cross-carrier retransmission configuration, wherein the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.

In some alternative embodiments, the network device may be a base station.

In some alternative embodiments, the first configuration information is carried in RRC signaling. Here, the first configuration information is used for determining a cross-carrier retransmission configuration, and the cross-carrier retransmission configuration is used for the terminal equipment to perform cross-carrier retransmission operation. In one manner, the first configuration information includes association information of a cross-carrier retransmission configuration, for example, an index of the cross-carrier retransmission configuration, from which the cross-carrier retransmission configuration can be determined. In another manner, the first configuration information includes a cross-carrier retransmission configuration. The network device semi-statically configures cross-carrier retransmission configuration through RRC signaling.

In the embodiment of the application, the terminal equipment supports carrier aggregation, and in the aggregated carrier set, the network equipment can configure the carrier supporting the cross-carrier retransmission operation in the carrier set through cross-carrier retransmission configuration.

In some alternative embodiments, the cross-carrier retransmission configuration includes at least one of:

the first information is used for indicating that uplink transmission and/or downlink transmission of the terminal equipment supports cross-carrier retransmission operation;

the second information is used for indicating the association relation among the plurality of carriers, and the carriers with the association relation support cross-carrier retransmission operation;

and third information, wherein the third information is used for indicating a carrier group, and cross-carrier retransmission operation is supported among a plurality of carriers in the carrier group.

As an example, the cross-carrier retransmission configuration includes first information, where the first information is used to indicate that uplink transmission of the terminal device supports cross-carrier retransmission operation, or the first information is used to indicate that downlink transmission of the terminal device supports cross-carrier retransmission operation, or the first information is used to indicate that uplink transmission and downlink transmission of the terminal device support cross-carrier retransmission operation.

As an example, the cross-carrier retransmission configuration includes second information, where the second information is used to indicate an association relationship between multiple carriers, and the carriers with the association relationship support cross-carrier retransmission operation. Here, alternatively, the plurality of carriers may be a plurality of carriers in which the terminal device performs carrier aggregation. As shown in fig. 5, the plurality of carriers includes CC1, CC2, CC3, CC4, and CC5, and the 5 carriers are all carriers or part of carriers in a carrier set aggregated by the terminal device. CC1 and CC2 have association, CC1 and CC3 have association, and CC4 and CC5 have association, then CC2 can be used for cross-carrier retransmission of CC1, CC3 can be used for cross-carrier retransmission of CC1, and CC5 can be used for cross-carrier retransmission of CC 4.

It should be noted that, the two carriers supporting the cross-carrier retransmission operation may be bidirectional or unidirectional, for example, the cross-carrier retransmission operation is supported between CC1 and CC2, so that, for bidirectional, CC1 may be used for cross-carrier retransmission of CC2 and CC2 may be used for cross-carrier retransmission of CC1, and for unidirectional, CC1 may be used for cross-carrier retransmission of CC2 or CC2 may be used for cross-carrier retransmission of CC 1.

As an example, the cross-carrier retransmission configuration includes third information indicating a carrier group supporting cross-carrier retransmission operations among a plurality of carriers within the carrier group. Here, the third information may indicate one or more carrier groups. Here, alternatively, the carriers within the carrier group may be carriers that the terminal device performs carrier aggregation. As shown in fig. 6, the network device configures a carrier group 1 and a carrier group 2, wherein the carrier group 1 includes CC1, CC2, and CC3, and the carrier group 2 includes CC4 and CC5. For carrier group 1, cross-carrier retransmission operations are supported between CC1, CC2 and CC3, and for carrier group 2, cross-carrier retransmission operations are supported between CC4 and CC5. Optionally, cross-carrier retransmission operations are not supported between carriers within different carrier groups.

In some optional embodiments, in the first configuration information, each carrier of the plurality of carriers is configured with a carrier index. Here, the carrier index is used to indicate a carrier.

In some optional embodiments, the terminal device sends first indication information to the network device, where the network device receives the first indication information sent by the terminal device, where the first indication information is used to indicate a carrier group proposed by the terminal device and/or an association relationship between an uplink carrier and a downlink carrier in the carrier group. Here, optionally, the first indication information is carried in RRC signaling. As an example, the first indication information is carried in UE assistance information (UE Assistance Information).

In the embodiment of the present application, for downlink data retransmission scheduling or uplink data retransmission scheduling, the network device is configured to indicate that the scheduling corresponding to the DCI is cross-carrier retransmission scheduling by carrying indication information in downlink control information (Downlink Control Information, DCI).

Specifically, the network device sends first DCI, and the terminal device receives the first DCI, where the first DCI is used to schedule retransmission of first data, and the retransmission of the first data is cross-carrier retransmission. Here, the first data may be downlink data or uplink data. In some of the embodiments of the present application in the alternative,

The first DCI carries at least one of the following information:

a first carrier index, where the first carrier index is a carrier index of a first carrier where the primary transmission of the first data is located;

a second carrier index, where the second carrier index is a carrier index of a second carrier where the retransmission of the first data is located;

a first HARQ process identifier, where the first HARQ process identifier is an HARQ process identifier of a first carrier corresponding to an initial transmission of the first data;

a second HARQ process identifier, where the second HARQ process identifier is an HARQ process identifier of a second carrier corresponding to retransmission of the first data;

the first indication information is used for indicating that the first DCI is DCI triggering cross-carrier retransmission.

In the above scheme, the "carrier index" may also be referred to as "carrier identification", and the carrier index may be a carrier index configured in the first configuration information in the above scheme, and may be a secondary cell (SCell) index or a serving cell index (serving cell index), as an example.

In the above scheme, the carrier indexes may be numbered in carrier groups, that is, in one carrier group, the carriers have unique carrier indexes. Alternatively, the carrier indexes may be numbered within multiple carriers, between which cross-carrier retransmission is supported, where the carriers have unique carrier indexes.

In the above scheme, the first HARQ process identifier is an HARQ process identifier of the first carrier corresponding to the initial transmission of the first data, and the second HARQ process identifier is an HARQ process identifier of the second carrier corresponding to the retransmission of the first data. Here, each carrier corresponds to one HARQ entity, and one HARQ may maintain one or more HARQ processes. As an example, the initial transmission of the first data is performed on the first carrier, where the HARQ process identifier corresponding to the initial transmission of the first data is a first HARQ process identifier, and the first HARQ process identifier is maintained by the HARQ entity corresponding to the first carrier. The retransmission of the first data is performed on the second carrier, where the HARQ process identifier corresponding to the retransmission of the first data is a second HARQ process identifier, and the second HARQ process identifier is maintained by the HARQ entity corresponding to the second carrier.

In the embodiment of the present application, the carrier on which the first DCI is located (i.e., the carrier on which the terminal device receives the first DCI) may have the following relationships with the first carrier and the second carrier:

relationship one: the carrier wave where the first DCI is located is the same as the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first DCI is initially transmitted, and the carrier wave where the first DCI is located is different from the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted; or,

Relationship II: the carrier wave where the first DCI is located is different from the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first DCI is initially transmitted, and the carrier wave where the first DCI is located is the same as the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted; or,

relationship III: the carrier wave where the first DCI is located is different from the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first data is initially transmitted, and the carrier wave where the first DCI is located is different from the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted.

As an example, the terminal device receives RRC signaling, and acquires a cross-carrier retransmission configuration according to the RRC signaling. And the terminal equipment receives the first DCI on a certain carrier and performs cross-carrier retransmission operation according to the information carried in the first DCI. The information carried in the first DCI includes at least one of:

In some optional embodiments, if the terminal device determines that the first DCI schedules downlink retransmission of the first data according to the format of the first DCI, the terminal device receives cross-carrier retransmission of the first data; or if the terminal equipment determines that the first DCI schedules uplink retransmission of the first data according to the format of the first DCI, the terminal equipment sends cross-carrier retransmission of the first data.

As an example, in the case that the terminal device receives the cross-carrier retransmission of the first data, the terminal device soft combines the first data corresponding to the received second HARQ process identifier with the first data corresponding to the stored first HARQ process identifier, and decodes the first data to obtain the first data.

As an example, in the case that the terminal device sends the cross-carrier retransmission of the first data, the terminal device retransmits the first data corresponding to the first HARQ process identifier through the second carrier, where the first data retransmitted through the second carrier corresponds to the second HARQ process identifier.

In some optional embodiments, the network device sends a first command to the terminal device, and the terminal device receives the first command sent by the network device, where the first command is used to trigger the terminal device to activate or start a cross-carrier retransmission function; and under the condition that the cross-carrier retransmission function is activated or started, the terminal equipment performs cross-carrier retransmission based on the cross-carrier retransmission configuration. Here, optionally, the first command is carried in DCI or MAC CE or RRC signaling.

In some alternative embodiments, the first command carries a first timer, and the first timer is used to trigger the terminal device to deactivate or stop a cross-carrier retransmission function. After receiving the first command, the terminal equipment activates or starts a cross-carrier retransmission function and starts the first timer; and if the first timer is overtime, the terminal equipment deactivates or stops the cross-carrier retransmission function.

In some optional embodiments, the network device sends a second command to the terminal device, and the terminal device deactivates or stops the cross-carrier retransmission function after receiving the second command; the second command is used for triggering the terminal equipment to deactivate or stop a cross-carrier retransmission function. Here, optionally, the second command is carried in DCI or MAC CE or RRC signaling.

As an example, the terminal device receives a first command sent by the network device, where the first command is used to activate or start the cross-carrier retransmission function, and an association relationship between carriers supporting cross-carrier retransmission is given in the first command or in RRC signaling (i.e., first configuration information in RRC signaling). As a way, a timer is configured in the first command or RRC signaling, and the timer is used to control deactivation or stopping of the cross-carrier retransmission function. As another way, the terminal device receives a second command sent by the network device, where the second command is used to deactivate or stop the cross-carrier retransmission function. For example: the RRC signaling configures a timer, the terminal device starts the timer after receiving the timer configured by the network device, and starts or activates the cross-carrier retransmission function, and if the timer is overtime or stopped, the cross-carrier retransmission function is stopped or deactivated.

In some optional embodiments, the first command carries an index of a carrier that activates or turns on a cross-carrier retransmission function, for example, a carrier index including two carriers with an association relationship, where the association relationship refers to support of a cross-carrier retransmission operation between the two carriers.

In some alternative embodiments, the second command carries an index of a carrier that deactivates or stops the cross-carrier retransmission function, for example, the index includes carrier indexes of two carriers with an association relationship, where the association relationship refers to support of cross-carrier retransmission operation between the two carriers.

In some optional embodiments, the network device sends second configuration information to the terminal device, where the terminal device receives the second configuration information sent by the network device, where the second configuration information is used to configure a first transmission resource on a first carrier, and the first transmission resource is used for cross-carrier retransmission of a second carrier. Here, in the second configuration information, the first transmission resource is configured with identification information associated with the second carrier. Further optionally, the identification information of the second carrier includes at least one of: the service cell index corresponding to the second carrier, the SCell index corresponding to the second carrier, and the carrier index of the second carrier.

In the above solution, optionally, the first transmission resource includes at least one of: an Grant (CG) resource and a Semi-persistent scheduling (Semi-Persistent Scheduling, SPS) resource are Configured.

In some alternative embodiments, the network device sends a third command to the terminal device, and the terminal device receives the third command sent by the network device, where the third command is used to activate or deactivate the first transmission resource.

As an example, the network device configures CG resources or SPS resources on the first carrier through RRC signaling, where the CG resources or SPS resources are used for cross-carrier retransmission of the second carrier, where the CG resources or SPS resources are associated with a carrier identifier of the second carrier, such as an SCell index or a serving cell index, and the second carrier is a carrier where the initial transmission of data is located, and accordingly, the first carrier is a carrier where the retransmission of the data is located. The network device may activate or deactivate CG resources or SPS resources for cross-carrier retransmission through DCI or MAC CE, and for CG resources or SPS resources in an active state, the terminal device receives DCI sent by the network device, where information carried by the DCI may refer to the foregoing description about the first DCI, and in addition, the DCI may also carry indication information of CG resources or SPS resources.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings, but the present application is not limited to the specific details of the above embodiments, and various simple modifications can be made to the technical solution of the present application within the scope of the technical concept of the present application, and all the simple modifications belong to the protection scope of the present application. For example, the specific features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various possible combinations are not described further. As another example, any combination of the various embodiments of the present application may be made without departing from the spirit of the present application, which should also be regarded as the disclosure of the present application. For example, on the premise of no conflict, the embodiments described in the present application and/or technical features in the embodiments may be combined with any other embodiments in the prior art, and the technical solutions obtained after combination should also fall into the protection scope of the present application.

It should be further understood that, in the various method embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application. Furthermore, in the embodiment of the present application, the terms "downstream", "upstream" and "sidestream" are used to indicate a transmission direction of signals or data, where "downstream" is used to indicate that the transmission direction of signals or data is a first direction from a station to a user equipment of a cell, and "upstream" is used to indicate that the transmission direction of signals or data is a second direction from the user equipment of the cell to the station, and "sidestream" is used to indicate that the transmission direction of signals or data is a third direction from the user equipment 1 to the user equipment 2. For example, "downstream signal" means that the transmission direction of the signal is the first direction. In addition, in the embodiment of the present application, the term "and/or" is merely an association relationship describing the association object, which means that three relationships may exist. Specifically, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Fig. 7 is a schematic structural diagram of a device for cross-carrier retransmission according to an embodiment of the present application, which is applied to a terminal device, as shown in fig. 7, where the device for cross-carrier retransmission includes:

a receiving unit 701, configured to receive first configuration information sent by a network device, where the first configuration information is used to determine a cross-carrier retransmission configuration;

and the retransmission unit 702 is configured to perform a cross-carrier retransmission operation based on the cross-carrier retransmission configuration, where the cross-carrier retransmission operation includes cross-carrier retransmission reception and/or cross-carrier retransmission transmission.

In some optional embodiments, in the first configuration information, each carrier of the plurality of carriers is configured with a carrier index.

In some alternative embodiments, the apparatus further comprises: and the sending unit is used for sending first indication information to the network equipment, wherein the first indication information is used for indicating the suggested carrier group of the terminal equipment and/or the association relationship between the uplink carrier and the downlink carrier in the carrier group.

In some alternative embodiments, the first indication information is carried in radio resource control RRC signaling.

In some optional embodiments, the receiving unit 701 is further configured to receive a first DCI, where the first DCI is used to schedule a retransmission of first data, and the retransmission of the first data is a cross-carrier retransmission.

In some optional embodiments, the first DCI carries at least one of the following information:

a first hybrid automatic repeat request (HARQ) process identifier, wherein the first HARQ process identifier is an HARQ process identifier of a first carrier corresponding to initial transmission of the first data;

In some optional embodiments, the carrier on which the first DCI is located is the same as the first carrier on which the first data is transmitted and/or the first carrier on which the first DCI is transmitted, and the carrier on which the first DCI is located is different from the second carrier on which the first data is retransmitted and/or the second carrier on which the first data is retransmitted; or,

the carrier wave where the first DCI is located is different from the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first DCI is initially transmitted, and the carrier wave where the first DCI is located is the same as the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted; or,

the carrier wave where the first DCI is located is different from the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first data is initially transmitted, and the carrier wave where the first DCI is located is different from the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted.

In some optional embodiments, if the terminal device determines that the first DCI schedules downlink retransmission of the first data according to the format of the first DCI, the retransmission unit 702 receives cross-carrier retransmission of the first data; or if the terminal device determines that the first DCI schedules uplink retransmission of the first data according to the format of the first DCI, the retransmission unit 702 sends cross-carrier retransmission of the first data.

In some optional embodiments, the receiving unit 701 is further configured to receive a first command sent by the network device, where the first command is used to trigger the terminal device to activate or start a cross-carrier retransmission function;

the retransmission unit 702 is further configured to perform cross-carrier retransmission based on the cross-carrier retransmission configuration when a cross-carrier retransmission function is activated or turned on.

In some alternative embodiments, the first command carries a first timer, the apparatus further comprising:

a control unit, configured to activate or start a cross-carrier retransmission function after the receiving unit 701 receives the first command, and start the first timer; and if the first timer is overtime, deactivating or stopping the cross-carrier retransmission function.

In some alternative embodiments, the apparatus further comprises: a control unit, configured to deactivate or stop the cross-carrier retransmission function after the receiving unit 701 receives the second command; the second command is used for triggering the terminal equipment to deactivate or stop a cross-carrier retransmission function.

In some alternative embodiments, the second command is carried in DCI or in a medium access control MAC control element CE or RRC signaling.

In some alternative embodiments, the first command is carried in DCI or MAC CE or RRC signaling.

In some optional embodiments, the receiving unit 701 is further configured to receive second configuration information sent by the network device, where the second configuration information is used to configure a first transmission resource on a first carrier, and the first transmission resource is used for cross-carrier retransmission of a second carrier.

In some optional embodiments, in the second configuration information, the first transmission resource is configured with identification information associated with the second carrier.

In some alternative embodiments, the identification information of the second carrier includes at least one of: the service cell index corresponding to the second carrier, the SCell index corresponding to the second carrier, and the carrier index of the second carrier.

In some optional embodiments, the receiving unit 701 is further configured to receive a third command sent by the network device, where the third command is used to activate or deactivate the first transmission resource.

In some alternative embodiments, the first transmission resource comprises at least one of: CG resources, SPS resources.

In some alternative embodiments, the first configuration information is carried in RRC signaling.

It should be understood by those skilled in the art that the above description of the apparatus for cross-carrier retransmission according to the embodiments of the present application may be understood with reference to the description of the method for cross-carrier retransmission according to the embodiments of the present application.

Fig. 8 is a schematic diagram ii of the structural composition of a device for cross-carrier retransmission according to an embodiment of the present application, which is applied to a network device, as shown in fig. 8, where the device for cross-carrier retransmission includes:

a sending unit 801, configured to send first configuration information to a terminal device, where the first configuration information is used to determine a cross-carrier retransmission configuration; the cross-carrier retransmission is configured to perform cross-carrier retransmission operation by the terminal equipment, and the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.

In some alternative embodiments, the apparatus further comprises: the receiving unit is used for receiving first indication information sent by the terminal equipment, wherein the first indication information is used for indicating the suggested carrier group of the terminal equipment and/or the association relationship between uplink carriers and downlink carriers in the carrier group.

In some alternative embodiments, the first indication information is carried in RRC signaling.

In some optional embodiments, the sending unit 801 is further configured to send a first DCI, where the first DCI is used to schedule a retransmission of the first data, and the retransmission of the first data is a cross-carrier retransmission.

In some optional embodiments, the sending unit 801 is further configured to send a first command to the terminal device, where the first command is used to trigger the terminal device to activate or turn on a cross-carrier retransmission function.

In some alternative embodiments, the first command carries a first timer, and the first timer is used to trigger the terminal device to deactivate or stop a cross-carrier retransmission function.

In some optional embodiments, the sending unit 801 is further configured to send a second command to the terminal device, where the second command is used to trigger the terminal device to deactivate or stop the cross-carrier retransmission function.

In some alternative embodiments, the second command is carried in DCI or MAC CE or RRC signaling.

In some optional embodiments, the sending unit 801 is further configured to send second configuration information to the terminal device, where the second configuration information is used to configure a first transmission resource on a first carrier, and the first transmission resource is used for cross-carrier retransmission of a second carrier.

In some alternative embodiments, the sending unit 801 is further configured to send a third command to the terminal device, where the third command is used to activate or deactivate the first transmission resource.

Fig. 9 is a schematic block diagram of a communication device 900 according to an embodiment of the present application. The communication device may be a terminal device or a network device. The communication device 900 shown in fig. 9 comprises a processor 910, from which the processor 910 may call and run a computer program to implement the method in an embodiment of the application.

Optionally, as shown in fig. 9, the communication device 900 may also include a memory 920. Wherein the processor 910 may invoke and run a computer program from the memory 920 to implement the method in the embodiments of the present application.

Wherein the memory 920 may be a separate device from the processor 910 or may be integrated in the processor 910.

Optionally, as shown in fig. 9, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

Wherein transceiver 930 may include a transmitter and a receiver. Transceiver 930 may further include antennas, the number of which may be one or more.

Optionally, the communication device 900 may be specifically a network device in the embodiment of the present application, and the communication device 900 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 900 may be specifically a mobile terminal/terminal device according to an embodiment of the present application, and the communication device 900 may implement corresponding processes implemented by the mobile terminal/terminal device in each method according to the embodiment of the present application, which are not described herein for brevity.

Fig. 10 is a schematic structural view of a chip of an embodiment of the present application. The chip 1000 shown in fig. 10 includes a processor 1010, and the processor 1010 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 10, the chip 1000 may further include a memory 1020. Wherein the processor 1010 may call and run a computer program from the memory 1020 to implement the methods in embodiments of the present application.

The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.

Optionally, the chip 1000 may also include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.

Optionally, the chip 1000 may further include an output interface 1040. Wherein the processor 1010 may control the output interface 1040 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 11 is a schematic block diagram of a communication system 1100 provided by an embodiment of the present application. As shown in fig. 11, the communication system 1100 includes a terminal device 1110 and a network device 1120.

The terminal device 1110 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1120 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of cross-carrier retransmission, the method comprising:

the method comprises the steps that terminal equipment receives first configuration information sent by network equipment, wherein the first configuration information is used for determining cross-carrier retransmission configuration;

and the terminal equipment performs cross-carrier retransmission operation based on the cross-carrier retransmission configuration, wherein the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.
The method of claim 1, wherein the cross-carrier retransmission configuration comprises at least one of:

the first information is used for indicating that uplink transmission and/or downlink transmission of the terminal equipment supports cross-carrier retransmission operation;

the second information is used for indicating the association relation among the plurality of carriers, and the carriers with the association relation support cross-carrier retransmission operation;

And third information, wherein the third information is used for indicating a carrier group, and cross-carrier retransmission operation is supported among a plurality of carriers in the carrier group.
The method of claim 2, wherein in the first configuration information, each carrier of the plurality of carriers is configured with a carrier index.
A method according to any one of claims 1 to 3, wherein the method further comprises:

the terminal equipment sends first indication information to the network equipment, wherein the first indication information is used for indicating the carrier group suggested by the terminal equipment and/or the association relationship between uplink carriers and downlink carriers in the carrier group.
The method of claim 4, wherein the first indication information is carried in radio resource control, RRC, signaling.
The method of any one of claims 1 to 5, wherein the method further comprises:

the terminal equipment receives first Downlink Control Information (DCI), wherein the first DCI is used for scheduling retransmission of first data, and the retransmission of the first data is cross-carrier retransmission.
The method of claim 6, wherein the first DCI carries at least one of:

a first carrier index, where the first carrier index is a carrier index of a first carrier where the primary transmission of the first data is located;

A second carrier index, where the second carrier index is a carrier index of a second carrier where the retransmission of the first data is located;

a first hybrid automatic repeat request (HARQ) process identifier, wherein the first HARQ process identifier is an HARQ process identifier of a first carrier corresponding to initial transmission of the first data;

a second HARQ process identifier, where the second HARQ process identifier is an HARQ process identifier of a second carrier corresponding to retransmission of the first data;

the first indication information is used for indicating that the first DCI is DCI triggering cross-carrier retransmission.
The method according to claim 6 or 7, wherein,

the carrier wave where the first DCI is located is the same as the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first DCI is initially transmitted, and the carrier wave where the first DCI is located is different from the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted; or,

the carrier wave where the first DCI is located is different from the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first DCI is initially transmitted, and the carrier wave where the first DCI is located is the same as the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted; or,

the carrier wave where the first DCI is located is different from the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first data is initially transmitted, and the carrier wave where the first DCI is located is different from the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted.
The method according to any one of claims 6 to 8, wherein the method further comprises:

if the terminal equipment determines that the first DCI schedules downlink retransmission of the first data according to the format of the first DCI, the terminal equipment receives cross-carrier retransmission of the first data; or,

and if the terminal equipment determines that the first DCI schedules uplink retransmission of the first data according to the format of the first DCI, the terminal equipment sends cross-carrier retransmission of the first data.
The method according to any one of claims 1 to 9, wherein,

the method further comprises the steps of: the terminal equipment receives a first command sent by the network equipment, wherein the first command is used for triggering the terminal equipment to activate or start a cross-carrier retransmission function;

the terminal equipment performs cross-carrier retransmission based on the cross-carrier retransmission configuration, and the method comprises the following steps: and under the condition that the cross-carrier retransmission function is activated or started, the terminal equipment performs cross-carrier retransmission based on the cross-carrier retransmission configuration.
The method of claim 10, wherein the first command carries a first timer, the method further comprising:

After receiving the first command, the terminal equipment activates or starts a cross-carrier retransmission function and starts the first timer;

and if the first timer is overtime, the terminal equipment deactivates or stops the cross-carrier retransmission function.
The method of claim 10, wherein the method further comprises:

after receiving the second command, the terminal equipment deactivates or stops the cross-carrier retransmission function; the second command is used for triggering the terminal equipment to deactivate or stop a cross-carrier retransmission function.
The method of claim 12, wherein the second command is carried in DCI or in a medium access control, MAC, control element, CE, or RRC, signaling.
The method of any of claims 10 to 13, wherein the first command is carried in DCI or MAC CE or RRC signaling.
The method of any one of claims 1 to 14, wherein the method further comprises:

the terminal equipment receives second configuration information sent by the network equipment, wherein the second configuration information is used for configuring first transmission resources on a first carrier, and the first transmission resources are used for cross-carrier retransmission of a second carrier.
The method of claim 15, wherein in the second configuration information, the first transmission resource is configured with identification information associated with the second carrier.
The method of claim 16, wherein the identification information of the second carrier comprises at least one of: the service cell index corresponding to the second carrier, the SCell index corresponding to the second carrier, and the carrier index of the second carrier.
The method of any one of claims 15 to 17, wherein the method further comprises:

and the terminal equipment receives a third command sent by the network equipment, wherein the third command is used for activating or deactivating the first transmission resource.
The method of any of claims 15 to 18, wherein the first transmission resource comprises at least one of: configuring authorized CG resources and semi-persistent scheduling SPS resources.
The method of any of claims 1 to 19, wherein the first configuration information is carried in RRC signaling.
A method of cross-carrier retransmission, the method comprising:

the network equipment sends first configuration information to the terminal equipment, wherein the first configuration information is used for determining cross-carrier retransmission configuration; the cross-carrier retransmission is configured to perform cross-carrier retransmission operation by the terminal equipment, and the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.
The method of claim 21, wherein the cross-carrier retransmission configuration comprises at least one of:

the first information is used for indicating that uplink transmission and/or downlink transmission of the terminal equipment supports cross-carrier retransmission operation;

the second information is used for indicating the association relation among the plurality of carriers, and the carriers with the association relation support cross-carrier retransmission operation;

and third information, wherein the third information is used for indicating a carrier group, and cross-carrier retransmission operation is supported among a plurality of carriers in the carrier group.
The method of claim 22, wherein in the first configuration information, each carrier of the plurality of carriers is configured with a carrier index.
The method of any one of claims 21 to 23, wherein the method further comprises:

the network device receives first indication information sent by the terminal device, where the first indication information is used to indicate a carrier group suggested by the terminal device and/or an association relationship between an uplink carrier and a downlink carrier in the carrier group.
The method of claim 24, wherein the first indication information is carried in RRC signaling.
The method of any one of claims 21 to 25, wherein the method further comprises:

the network device sends first DCI, wherein the first DCI is used for scheduling retransmission of first data, and the retransmission of the first data is cross-carrier retransmission.
The method of claim 26, wherein the first DCI carries at least one of:

a first carrier index, where the first carrier index is a carrier index of a first carrier where the primary transmission of the first data is located;

a second carrier index, where the second carrier index is a carrier index of a second carrier where the retransmission of the first data is located;

a first HARQ process identifier, where the first HARQ process identifier is an HARQ process identifier of a first carrier corresponding to an initial transmission of the first data;

a second HARQ process identifier, where the second HARQ process identifier is an HARQ process identifier of a second carrier corresponding to retransmission of the first data;

the first indication information is used for indicating that the first DCI is DCI triggering cross-carrier retransmission.
The method of claim 26 or 27, wherein,

the carrier wave where the first DCI is located is the same as the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first DCI is initially transmitted, and the carrier wave where the first DCI is located is different from the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted; or,

The carrier wave where the first DCI is located is different from the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first DCI is initially transmitted, and the carrier wave where the first DCI is located is the same as the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted; or,

the carrier wave where the first DCI is located is different from the first carrier wave where the first data is initially transmitted and/or the first carrier wave where the first data is initially transmitted, and the carrier wave where the first DCI is located is different from the second carrier wave where the first data is retransmitted and/or the second carrier wave where the first data is retransmitted.
The method of any one of claims 26 to 28, wherein the method further comprises:

the network device sends a first command to the terminal device, wherein the first command is used for triggering the terminal device to activate or start a cross-carrier retransmission function.
The method of claim 29, wherein the first command carries a first timer for triggering the terminal device to deactivate or stop a cross-carrier retransmission function.
The method of claim 29, wherein the method further comprises:

the network device sends a second command to the terminal device, where the second command is used to trigger the terminal device to deactivate or stop the cross-carrier retransmission function.
The method of claim 31, wherein the second command is carried in DCI or MAC CE or RRC signaling.
The method of any of claims 29 to 32, wherein the first command is carried in DCI or MAC CE or RRC signaling.
The method of any one of claims 21 to 33, wherein the method further comprises:

the network device sends second configuration information to the terminal device, wherein the second configuration information is used for configuring a first transmission resource on a first carrier, and the first transmission resource is used for cross-carrier retransmission of a second carrier.
The method of claim 34, wherein in the second configuration information, the first transmission resource is configured with identification information associated with the second carrier.
The method of claim 35, wherein the identification information of the second carrier comprises at least one of: the service cell index corresponding to the second carrier, the SCell index corresponding to the second carrier, and the carrier index of the second carrier.
The method of any one of claims 34 to 36, wherein the method further comprises:

the network device sends a third command to the terminal device, where the third command is used to activate or deactivate the first transmission resource.
The method of any of claims 34-37, wherein the first transmission resource comprises at least one of: CG resources, SPS resources.
The method of any of claims 21 to 38, wherein the first configuration information is carried in RRC signaling.
An apparatus for cross-carrier retransmission, applied to a terminal device, the apparatus comprising:

a receiving unit, configured to receive first configuration information sent by a network device, where the first configuration information is used to determine a cross-carrier retransmission configuration;

and the retransmission unit is used for carrying out cross-carrier retransmission operation based on the cross-carrier retransmission configuration, wherein the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.
An apparatus for cross-carrier retransmission, applied to a network device, the apparatus comprising:

a sending unit, configured to send first configuration information to a terminal device, where the first configuration information is used to determine a cross-carrier retransmission configuration; the cross-carrier retransmission is configured to perform cross-carrier retransmission operation by the terminal equipment, and the cross-carrier retransmission operation comprises cross-carrier retransmission receiving and/or cross-carrier retransmission sending.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 1 to 20.
A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 21 to 39.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 20.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 21 to 39.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 20.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 21 to 39.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 20.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 21 to 39.
A computer program which causes a computer to perform the method of any one of claims 1 to 20.
A computer program which causes a computer to perform the method of any one of claims 21 to 39.