CN117044334A - Method and device for configuring carrier, terminal equipment and network equipment - Google Patents

Abstract

The embodiment of the application provides a method and a device for configuring carrier waves, 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 configuring an association relationship between an uplink carrier and a downlink carrier; and the terminal equipment determines the association relationship between the uplink carrier and the downlink carrier based on the first configuration information.

Description

A method and device for configuring carriers, terminal equipment, and network equipment Technical field

The embodiments of the present application relate to the field of mobile communication technology, and specifically relate to a method and device for configuring a carrier, terminal equipment, and network equipment.

Background technique

Carrier aggregation can provide larger bandwidth for services, thereby improving service throughput. In carrier aggregation, since traditional services have a large downlink traffic volume, the number of downlink carriers is greater than the number of uplink carriers.

In the process of the evolution of mobile communication technology, various new services will appear, and the uplink business volume will become larger and larger. The uplink throughput can be improved by increasing the number of uplink carriers. Since there are a large number of uplink carriers, there may be situations where an uplink carrier does not have a corresponding downlink carrier, which will result in the downlink scheduling of the uplink carrier being unable to be resolved.

Contents of the invention

Embodiments of the present application provide a method and device for configuring a carrier, terminal equipment, network equipment, chips, computer-readable storage media, computer program products, and computer programs.

The method for configuring a carrier provided by the embodiment of this application includes:

The terminal device receives first configuration information sent by the network device, where the first configuration information is used to configure the association between the uplink carrier and the downlink carrier;

The terminal device determines an association relationship between an uplink carrier and a downlink carrier based on the first configuration information.

The method for configuring a carrier provided by the embodiment of this application includes:

The network device sends first configuration information to the terminal device, where the first configuration information is used to configure the association between the uplink carrier and the downlink carrier.

The device for configuring carriers provided in the embodiment of this application is applied to terminal equipment, and the device includes:

A receiving unit configured to receive first configuration information sent by the network device, where the first configuration information is used to configure the association between the uplink carrier and the downlink carrier;

A determining unit configured to determine an association relationship between an uplink carrier and a downlink carrier based on the first configuration information.

The device for configuring a carrier provided by the embodiment of the present application is applied to network equipment. The device includes:

A sending unit, configured to send first configuration information to the terminal device, where the first configuration information is used to configure the association relationship between the uplink carrier and the downlink carrier.

The terminal device provided by the embodiment of the present application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer program stored in the memory, and execute the above method of configuring a carrier.

The network device provided by the embodiment of the present application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer program stored in the memory, and execute the above method of configuring a carrier.

The chip provided by the embodiment of the present application is used to implement the above method of configuring a carrier.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above method of configuring a carrier.

The computer-readable storage medium provided by the embodiment of the present application is used to store a computer program. The computer program causes the computer to execute the above method of configuring a carrier.

The computer program product provided by the embodiment of the present application includes computer program instructions, which cause the computer to execute the above method of configuring a carrier.

The computer program provided by the embodiment of the present application, when run on a computer, causes the computer to execute the above method of configuring a carrier.

Through the above technical solution, the network equipment flexibly configures the association between the uplink carrier and the downlink carrier for the terminal equipment, so that any uplink carrier can have an associated downlink carrier, ensuring that the uplink carrier can be processed through its associated downlink carrier. Normal scheduling improves the uplink throughput of services.

Description of the drawings

The drawings described here are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation of the present application. In the attached picture:

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

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

Figure 3 is an architecture diagram of the uplink protocol stack in a carrier aggregation scenario according to an embodiment of the present application;

Figure 4 is a schematic flowchart of a method for configuring a carrier provided by an embodiment of the present application;

Figure 5 is a schematic diagram 1 of MAC CE for changing carrier association relationships provided by an embodiment of the present application;

Figure 6 is a schematic diagram 2 of MAC CE for changing carrier association relationships provided by an embodiment of the present application;

Figure 7 is a schematic diagram three of the MAC CE for changing carrier association relationships provided by the embodiment of the present application;

Figure 8 is a schematic structural diagram of a device for configuring a carrier provided by an embodiment of the present application;

Figure 9 is a schematic diagram 2 of the structural composition of a device for configuring a carrier provided by an embodiment of the present application;

Figure 10 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

Figure 11 is a schematic structural diagram of a chip according to an embodiment of the present application;

Figure 12 is a schematic block diagram of a communication system provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

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

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

It should be understood that the embodiment of the present application is only exemplified by using the communication system 100, but the embodiment of the present application is not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Communication System (Universal Mobile Communication System). Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also called New Radio (NR) communication system), or future communication system, etc.

In the communication system 100 shown in FIG. 1 , the network device 120 may be an access network device that communicates with the terminal device 110 . The access network device may provide communication coverage for a specific geographical area and may communicate with terminal devices 110 (eg, UEs) located within the coverage area.

The network device 120 may be an evolutionary 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 (NG RAN) device, It may be a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, access point, vehicle-mounted device, or wearable device. Equipment, hubs, switches, bridges, routers, or network equipment in the future evolved Public Land Mobile Network (Public Land Mobile Network, PLMN), etc.

The terminal device 110 may be any terminal device, including but not limited to terminal devices that are wired or wirelessly connected to the network device 120 or other terminal devices.

For example, the terminal equipment 110 may refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication Device, user agent, or user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, or a Personal Digital Assistant (Personal Digital Assistant). , PDA), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or terminal devices in future evolution networks, etc.

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

The wireless communication system 100 may also include a core network device 130 that communicates with the base station. The core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an access and mobility management function (Access and Mobility Management Function). , AMF), for example, Authentication Server Function (AUSF), for example, User Plane Function (UPF), for example, Session Management Function (Session Management Function, SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device of the LTE network, for example, a session management function + core network data gateway (Session Management Function + Core Packet Gateway, SMF + PGW- C) Equipment. It should be understood that SMF+PGW-C can simultaneously realize the functions that SMF and PGW-C can realize. In the process of network evolution, the above-mentioned core network equipment may also be called by other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited by the embodiments of this application.

Various functional units in the communication system 100 can also establish connections through a next generation network (NG) interface to implement communication.

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

Figure 1 exemplarily shows a base station, a core network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices and other numbers of terminals may be included within the coverage of each base station. Equipment, the embodiments of this application do not limit this.

It should be noted that FIG. 1 only illustrates the system to which the present application is applicable in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems. Additionally, the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is just an association relationship that describes related objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and they exist alone. B these three situations. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship. It should also be understood that the "instruction" mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed. , configuration and configured relationship. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be pre-saved in the device (for example, including terminal devices and network devices) by pre-saving corresponding codes, tables or other available The method is implemented by indicating relevant information, and this application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol. It should also be understood that in the embodiments of this application, the "protocol" may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this. .

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be optionally combined with the technical solutions of the embodiments of the present application, and they all belong to the embodiments of the present application. protected range.

With people's pursuit of speed, delay, high-speed mobility, energy efficiency, and the diversity and complexity of services in future life, the ^3rd Generation Partnership Project (3GPP) international standards organization has begun to develop 5G . The main application scenarios of 5G are: enhanced mobile ultra-broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine-type communications (mMTC) ).

On the one hand, eMBB still aims at users to obtain multimedia content, services and data, and its demand is growing rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoors, urban areas, rural areas, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail based on specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety and security, etc. Typical features of mMTC include: high connection density, small data volume, delay-insensitive services, low cost and long service life of the module.

In the early deployment of NR, complete NR coverage was difficult to obtain, so typical network coverage was wide-area LTE coverage and NR island coverage mode. And a large amount of LTE is deployed below 6GHz, and there is very little sub-6GHz spectrum available for 5G. Therefore, NR must study spectrum applications above 6GHz, but high-frequency band coverage is limited and signals fade quickly. At the same time, in order to protect mobile operators' early investment in LTE, a tight interworking working model between LTE and NR was proposed.

In order to achieve 5G network deployment and commercial applications as soon as possible, 3GPP first completed the first 5G version, namely EN-DC (LTE-NR Dual Connectivity). In EN-DC, the LTE base station (eNB) serves as the master node (MN), and the NR base station (gNB or en-gNB) serves as the secondary node (Secondary Node, SN), connected to the EPC core network. Later in R15, other DC modes will be supported, namely NE-DC, 5GC-EN-DC, NR DC. In NE-DC, the NR base station serves as the MN and the eLTE base station serves as the SN, connecting to the 5GC core network. In 5GC-EN-DC, the eLTE base station serves as the MN and the NR base station serves as the SN, connecting to the 5GC core network. In the NR DC, the NR base station serves as the MN and the NR base station serves as the SN, connecting to the 5GC core network.

In 5G, the maximum channel bandwidth can be 400MHZ (called a wideband carrier). Compared with the maximum bandwidth of 20M in LTE, the bandwidth of a wideband carrier is very large. In order to meet the demand for high speed, 5G supports Carrier Aggregation (CA) technology. CA allows the NR system to support larger bandwidth through joint scheduling and use of resources on multiple component carriers (CCs), thereby enabling higher system peak rates. According to the continuity of the aggregated carriers on the spectrum, it can be divided into continuous carrier aggregation and non-continuous carrier aggregation; according to whether the frequency band (band) of the aggregated carriers is the same, it can be divided into intra-band carrier aggregation and inter-band carrier aggregation.

In CA, there is only one primary carrier (Primary Cell Component, PCC). The PCC provides RRC signaling connection, non-access layer (Non-Access Stratrum, NAS) functions, security, etc. The Physical Uplink Control Channel (PUCCH) exists on the PCC and only on the PCC. In CA, there can be one or more secondary carriers (Secondary Cell Component, SCC), and the SCC only provides additional wireless resources. PCC and SCC are both called Serving Cells. The cell on PCC is the primary cell (PCell), and the cell on SCC is the secondary cell (SCell).

Figures 2 and 3 are protocol stack architecture diagrams in a carrier aggregation scenario. Figure 2 is a protocol stack architecture diagram for downlink, and Figure 3 is a protocol stack architecture diagram for uplink. It can be seen that one CC and one HARQ entity correspond.

In carrier aggregation, since traditional services have a large downlink traffic volume, the number of downlink carriers is greater than the number of uplink carriers. In addition, when configuring a carrier, the associated downlink carrier and uplink carrier are configured at the same time.

In the evolution process of 5G and later, various new services will appear, and the uplink business volume will become larger and larger. The uplink throughput can be improved by increasing the number of uplink carriers. Since there are a large number of uplink carriers, there may be situations where an uplink carrier does not have a corresponding downlink carrier, which will result in the downlink scheduling of the uplink carrier being unable to be resolved. In addition, the traditional way of configuring carriers will fixedly configure one uplink carrier and associate one downlink carrier, which limits the flexibility of data scheduling.

To this end, the following technical solutions of the embodiments of the present application are proposed.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application. The embodiments of this application include at least part of the following content.

Figure 4 is a schematic flowchart of a method for configuring a carrier provided by an embodiment of the present application. As shown in Figure 4, the method for configuring a carrier includes the following steps:

Step 401: The network device sends first configuration information to the terminal device, and the terminal device receives the first configuration information sent by the network device. The first configuration information is used to configure the association between the uplink carrier and the downlink carrier.

Step 402: The terminal device determines the association between the uplink carrier and the downlink carrier based on the first configuration information.

In some optional implementations, the network device may be a base station.

In some optional implementations, the first configuration information is carried in RRC signaling.

In this embodiment of the present application, the first configuration information is used to configure the association between the uplink carrier and the downlink carrier. The content of the first configuration information is described below in conjunction with different solutions.

Option One

In this embodiment of the present application, the first configuration information is used to configure at least one SCell; wherein each SCell in the at least one SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier, or includes only An uplink carrier.

It should be noted that SCell only includes one downlink carrier, which can also be understood as SCell having Only DL carrier.

It should be noted that SCell only includes one uplink carrier, which can also be understood as SCell having Only UL carrier.

It should be noted that SCell includes one uplink carrier and one downlink carrier. It can also be understood that SCell has both DL carriers and UL carriers.

In some optional implementations, in the first configuration information, each SCell in the at least one SCell is configured with an SCell index.

In some optional implementations, in the first configuration information, for an SCell that only includes one uplink carrier, a carrier index is configured for the uplink carrier in the SCell.

In this embodiment of the present application, for an SCell that includes only one downlink carrier or includes one uplink carrier and one downlink carrier, the SCell is identified by a physical cell identity (PCI) and a downlink frequency point.

In the embodiment of this application, the first configuration information is used to configure the association between the uplink carrier and the downlink carrier, and there are two ways:

method one:

In some optional implementations, the at least one SCell includes a first SCell, the first SCell includes a first uplink carrier and a first downlink carrier, and the downlink carrier associated with the first uplink carrier is the first Downlink carrier.

Here, the first SCell refers to a SCell including an uplink carrier and a downlink carrier, and the uplink carrier and downlink carrier belonging to the same SCell are associated.

As an example, SCell includes uplink carrier 1 and downlink carrier 1. Then, uplink carrier 1 and downlink carrier 1 have an associated relationship.

Method two:

In some optional implementations, the at least one SCell includes a second SCell, the second SCell only includes a second uplink carrier, and the downlink carrier associated with the second uplink carrier is a downlink carrier in the third SCell; wherein , the third SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.

Here, the second SCell refers to a SCell that includes only one uplink carrier, and the downlink carrier associated with the uplink carrier in the SCell may be the downlink carrier in another SCell. During specific implementation, in the first configuration information, the second SCell is configured to be associated with the identification information of the third SCell; wherein the identification information of the third SCell is the SCell of the third SCell. Index, or the PCI and downlink frequency point of the third SCell.

As an example, SCell 1 only includes uplink carrier 2, SCell 2 includes uplink carrier 1 and downlink carrier 1, SCell 3 includes downlink carrier 2, SCell 1 is associated with the identification information of SCell 3, then uplink carrier 2 is associated with downlink carrier 2 relation.

In some optional implementations, the network device sends a first signaling to the terminal device, the terminal device receives the first signaling sent by the network device, and the first signaling is used to change the The correlation between uplink carriers and downlink carriers. Here, the first signaling is MAC CE or DCI.

In some optional implementations, when the first signaling is MAC CE, the MAC CE includes:

First information, the first information is used to indicate the target downlink carrier;

Second information, the second information is used to indicate at least one uplink carrier that is associated with the target downlink carrier.

The contents of the first information and the second information will be described below.

first information

In this embodiment of the present application, the first information includes the SCell index of the target SCell, and the target SCell includes the target downlink carrier. Optionally, the target SCell also includes an uplink carrier.

Second information

Option 1) In some optional implementations, the second information includes a first bitmap, each bit in the first bitmap corresponds to an SCell index of an SCell, and the value of the bit is used for Indicates whether the uplink carrier included in the SCell corresponding to this bit is associated with the target downlink carrier.

In some optional implementations, the length of the first bitmap is a variable length, and the length of the first bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the first bitmap is equal to the number of uplink carriers divided by N and then rounded up, where N is the number of bits included in one byte, and N is a positive integer. As an example, N=8.

In some optional implementations, the first bitmap includes M bits, M is a positive integer; the M bits are in order from low to high, and the M SCell indexes are in ascending order from small to large. Sequential correspondence; or, the M bits correspond to the M SCell indexes in order from low to high, in order from large to small.

Option 2) In some optional implementations, the second information includes a second bitmap, each bit in the second bitmap corresponds to the carrier index of an uplink carrier, and the value of the bit is To indicate whether the uplink carrier corresponding to the bit has an associated relationship with the target downlink carrier.

In some optional implementations, the length of the second bitmap is variable, and the length of the second bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the second bitmap is equal to the number of uplink carriers divided by N and then rounded up, where N is the number of bits included in one byte, and N is a positive integer. As an example, N=8.

In some optional implementations, the second bitmap includes M bits, M is a positive integer; the M bits are in order from low to high, and the M carrier indexes are in ascending order from small to large. Sequential correspondence; or, the M bits correspond to the M carrier indexes in order from low to high, in order from large to small.

Option 3) In some optional implementations, the second information includes SCell indexes of one or more SCells, and the uplink carrier included in each SCell of the one or more SCells is associated with the target downlink carrier. relation.

Option 4) In some optional implementations, the second information includes a carrier index of one or more uplink carriers, and each of the one or more uplink carriers has an associated relationship with the target downlink carrier. .

Option II

In this embodiment of the present application, the first configuration information is used to configure at least one of the following: at least one SCell and at least one uplink carrier; wherein each SCell in the at least one SCell only includes one downlink carrier, or includes one uplink carrier and one downlink carrier.

Here, each uplink carrier in the at least one uplink carrier can be understood as an Only UL carrier.

It should be noted that SCell only includes one downlink carrier, which can also be understood as SCell having Only DL carrier.

It should be noted that SCell includes one uplink carrier and one downlink carrier. It can also be understood that SCell has both DL carriers and UL carriers.

It should be noted that Only UL carriers do not belong to SCell.

In some optional implementations, in the first configuration information, each SCell in the at least one SCell is configured with an SCell index.

In some optional implementations, in the first configuration information, each uplink carrier in the at least one uplink carrier is configured with a carrier index.

In this embodiment of the present application, for an SCell that includes only one downlink carrier or includes one uplink carrier and one downlink carrier, the SCell is identified by a physical cell identity (PCI) and a downlink frequency point.

In the embodiment of this application, the first configuration information is used to configure the association between the uplink carrier and the downlink carrier, and can be used in the following two ways:

method one:

In some optional implementations, the at least one SCell includes a first SCell, the first SCell includes a first uplink carrier and a first downlink carrier, and the downlink carrier associated with the first uplink carrier is the first Downlink carrier.

Here, the first SCell refers to a SCell including an uplink carrier and a downlink carrier, and the uplink carrier and downlink carrier belonging to the same SCell are associated.

As an example, SCell includes uplink carrier 1 and downlink carrier 1. Then, uplink carrier 1 and downlink carrier 1 have an associated relationship.

Method two:

In some optional implementations, the at least one uplink carrier includes a second uplink carrier, and the downlink carrier associated with the second uplink carrier is a downlink carrier in a third SCell; wherein the third SCell only includes one downlink carrier. carrier, or includes an uplink carrier and a downlink carrier.

Here, the second uplink carrier refers to an Only UL carrier, and the downlink carrier associated with the second uplink carrier may be a downlink carrier in another SCell. During specific implementation, in the first configuration information, the second uplink carrier is configured to be associated with the identification information of the third SCell; wherein the identification information of the third SCell is the identification information of the third SCell. SCell index, or the PCI and downlink frequency point of the third SCell.

As an example, uplink carrier 2 is an Only UL carrier, SCell 2 includes uplink carrier 1 and downlink carrier 1, SCell 3 includes downlink carrier 2, and uplink carrier 2 is associated with the identification information of SCell 3. Then, uplink carrier 2 and downlink carrier 2 have connection relation.

In some optional implementations, the network device sends a first signaling to the terminal device, the terminal device receives the first signaling sent by the network device, and the first signaling is used to change the The correlation between uplink carriers and downlink carriers. Here, the first signaling is MAC CE or DCI.

In some optional implementations, when the first signaling is MAC CE, the MAC CE includes:

First information, the first information is used to indicate the target downlink carrier;

Second information, the second information is used to indicate at least one uplink carrier that is associated with the target downlink carrier.

The contents of the first information and the second information will be described below.

first information

In this embodiment of the present application, the first information includes the SCell index of the target SCell, and the target SCell includes the target downlink carrier. Optionally, the target SCell also includes an uplink carrier.

Second information

Option 1) In some optional implementations, the second information includes a second bitmap, each bit in the second bitmap corresponds to the carrier index of an uplink carrier, and the value of the bit is To indicate whether the uplink carrier corresponding to the bit has an associated relationship with the target downlink carrier.

In some optional implementations, the length of the second bitmap is variable, and the length of the second bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the second bitmap is equal to the number of uplink carriers divided by N and then rounded up, where N is the number of bits included in one byte, and N is a positive integer. As an example, N=8.

In some optional implementations, the second bitmap includes M bits, M is a positive integer; the M bits are in order from low to high, and the M carrier indexes are in ascending order from small to large. Sequential correspondence; or, the M bits correspond to the M carrier indexes in order from low to high, in order from large to small.

Option 2) In some optional implementations, the second information includes a carrier index of one or more uplink carriers, and each of the one or more uplink carriers has an associated relationship with the target downlink carrier. .

third solution

In this embodiment of the present application, the first configuration information is used to configure a downlink carrier set and an uplink carrier set. The downlink carrier set includes at least one downlink carrier, and the uplink carrier set includes at least one uplink carrier.

In some optional implementations, in the first configuration information, each downlink carrier in the downlink carrier set is configured with a carrier index, and each uplink carrier in the uplink carrier set is configured with a carrier index. .

In some optional implementations, in the first configuration information, the downlink carriers in the downlink carrier set and the uplink carriers in the uplink carrier set are configured to have an associated relationship; wherein, the uplink carrier associated with one downlink carrier The number of carriers is one or more, and the number of downlink carriers associated with one uplink carrier is one.

In some optional implementations, the network device sends second signaling to the terminal device, and the terminal device receives the second signaling sent by the network device, and the second signaling is used to change the The correlation between uplink carriers and downlink carriers. Here, the second signaling is MAC CE or DCI.

In some optional implementations, when the second signaling is MAC CE, the MAC CE includes:

Third information, the third information is used to indicate the target downlink carrier;

Fourth information, the fourth information is used to indicate at least one uplink carrier that is associated with the target downlink carrier.

The contents of the third information and the fourth information will be described below.

Third information

In this embodiment of the present application, the third information includes the carrier index of the target downlink carrier.

Fourth information

Option 1) In some optional implementations, the fourth information includes a third bitmap, each bit in the third bitmap corresponds to the carrier index of an uplink carrier, and the value of the bit is To indicate whether the uplink carrier corresponding to the bit has an associated relationship with the target downlink carrier.

In some optional implementations, the length of the third bitmap is a variable length, and the length of the third bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the third bitmap is equal to the number of uplink carriers divided by N and then rounded upward, where N is the number of bits included in one byte, and N is a positive integer. As an example, N=8.

In some optional implementations, the third bitmap includes M bits, M is a positive integer; the M bits are in order from low bit to high bit, and the M carrier indexes are in ascending order from small to large. Sequential correspondence; or, the M bits correspond to the M carrier indexes in order from low to high, in order from large to small.

Option 2) In some optional implementations, the fourth information includes a carrier index of one or more uplink carriers, and each of the one or more uplink carriers has an associated relationship with the target downlink carrier. .

Through the above technical solution of the embodiment of the present application, the network device can flexibly configure the association relationship between the downlink carrier and the uplink carrier. Furthermore, the network device can dynamically change the association relationship between the downlink carrier and the uplink carrier through signaling, so that one downlink carrier can Associating multiple uplink carriers improves uplink throughput while ensuring downlink spectrum efficiency. At the same time, because the association between downlink carriers and uplink carriers is flexible, the association between downlink carriers and uplink carriers can be freely combined. , avoiding the complexity caused by cross-carrier scheduling.

In some optional implementations, the network device sends second configuration information to the terminal device, and the terminal device receives the second configuration information. The second configuration information is used to configure a carrier group, and the carrier group includes At least one uplink carrier and at least one downlink carrier; the terminal device changes the association between the uplink carrier and the downlink carrier within the carrier group. Optionally, the second configuration information is carried in RRC signaling.

In some optional implementations, the terminal device sends first indication information to the network device, and the network device receives the first indication information sent by the terminal device, and the first indication information is used to indicate the The carrier group recommended by the terminal device and/or the association between the uplink carrier and the downlink carrier within the carrier group; wherein the carrier group includes at least one uplink carrier and at least one downlink carrier. Here, the first indication information may carry RRC signaling. As an example, the RRC signaling may be RRC signaling carrying UE assistance information.

The technical solutions of the embodiments of the present application are illustrated below with reference to specific application examples.

Application example one

The network device configures at least one SCell through RRC signaling. The SCell may include only one downlink carrier, one uplink carrier and one downlink carrier, or only one uplink carrier.

In some optional implementations, each SCell in the at least one SCell is configured with an SCell index.

In some optional implementations, for an SCell that includes only one downlink carrier or includes one uplink carrier and one downlink carrier, the SCell is identified by PCI and a downlink frequency point. The PCI and downlink frequency points of the SCell are used to search for the SCell that only includes uplink carriers to identify the SCell.

In some optional implementations, for an SCell that only includes one uplink carrier, the SCell is configured to associate identification information of a target SCell. The identification information of the target SCell may be the SCell index of the target SCell, or the PCI and the downlink frequency point. Here, the target SCell includes a downlink carrier, and optionally may also include an uplink carrier. The identification information of the target SCell may indicate the downlink carrier associated with the Only UL carrier (that is, only one uplink carrier included in the SCell).

In some optional implementations, the association between the downlink carrier and the uplink carrier configured semi-statically by RRC signaling can be dynamically changed through MAC CE or DCI. It should be noted that in RRC signaling, a SCell is configured with both a downlink carrier and an uplink carrier, and the association between the downlink carrier and the uplink carrier cannot be dynamically changed through MAC CE or DCI.

In the embodiment of this application, there are many formats of MAC CE. As an example, referring to Figure 5, the MAC CE includes the SCell index of the target SCell. The target SCell includes a downlink carrier (hereinafter referred to as the target downlink carrier). The MAC CE also includes a bitmap (bitmap). Each bitmap in the bitmap A bit (Ci) corresponds to the SCell index of a SCell (the SCell refers to a SCell that only includes one uplink carrier). The value of the bit is 1 (or 0) to indicate that the uplink carrier in the corresponding SCell is the same as the target downlink carrier. There is an association relationship. The value of the bit is 0 (or 1) indicating that the uplink carrier in the corresponding SCell does not have an association relationship with the target downlink carrier. The MAC CE can indicate the set of uplink carriers associated with the target downlink carrier. It should be noted that MAC CE can only dynamically change the set of uplink carriers associated with a target downlink carrier.

In some optional implementations, the length of the bitmap in the MAC CE is variable. For example, the length of the bitmap depends on the number of uplink carriers (ie, Only UL carriers). The number of bytes of the bitmap is equal to (the number of uplink carriers). Quantity/8) and then rounded up.

In some optional implementations, the bits in the bitmap in the MAC CE correspond one-to-one in order from low to high, and the SCell indexes corresponding to the uplink carriers in the uplink carrier set in order from small to large, or, The bits in the bitmap in the MAC CE are in order from low to high, and correspond one to one with the SCell index corresponding to the uplink carrier in the uplink carrier set in order from large to small.

In some optional implementations, the MAC CE corresponds to a new logical channel identifier (LCID), and the LCID is used to identify and identify the MAC CE.

It should be noted that the format of MAC CE is not limited to the format shown in Figure 5 above, and there can be many other formats. As an example, the MAC CE includes multiple SCell indexes. The first SCell index is the SCell index corresponding to the target downlink carrier, and the other SCell indexes are SCell indexes corresponding to the uplink carrier associated with the target downlink carrier. As an example, the MAC CE includes a SCell index and at least one carrier index, where the SCell index is the SCell index corresponding to the target downlink carrier, and the carrier index is the carrier index of the uplink carrier associated with the target downlink carrier.

Application example two

The network device configures at least one SCell and at least one uplink carrier through RRC signaling. The SCell may include only one downlink carrier, or include one uplink carrier and one downlink carrier. The uplink carrier refers to the Only UL carrier, and the Only UL carrier does not belong to a SCell.

In some optional implementations, each SCell in the at least one SCell is configured with an SCell index.

In some optional implementations, for an SCell that includes only one downlink carrier or includes one uplink carrier and one downlink carrier, the SCell is identified by PCI and a downlink frequency point. The SCell's PCI and downlink frequency points are used for Only UL carrier search to identify the SCell.

In some optional implementations, each uplink carrier in the at least one uplink carrier is configured with a carrier index.

In some optional implementations, for an uplink carrier (that is, an Only UL carrier), the uplink carrier is configured to associate identification information of a target SCell. The identification information of the target SCell may be the SCell index of the target SCell, or the PCI and downlink frequency. point. Here, the target SCell includes a downlink carrier, and optionally may also include an uplink carrier. The identification information of the target SCell may indicate the downlink carrier associated with the Only UL carrier.

In some optional implementations, the association between the downlink carrier and the uplink carrier configured semi-statically by RRC signaling can be dynamically changed through MAC CE or DCI. It should be noted that in RRC signaling, a SCell is configured with both a downlink carrier and an uplink carrier, and the association between the downlink carrier and the uplink carrier cannot be dynamically changed through MAC CE or DCI.

In the embodiment of this application, there are many formats of MAC CE. As an example, referring to Figure 6, the MAC CE includes the SCell index of the target SCell. The target SCell includes a downlink carrier (hereinafter referred to as the target downlink carrier). The MAC CE also includes a bitmap (bitmap). Each bitmap in the bitmap Bits (UCi) correspond to the carrier index of an uplink carrier (i.e. Only UL carrier). The value of the bit is 1 (or 0) indicating that the corresponding uplink carrier is associated with the target downlink carrier. The value of the bit A value of 0 (or 1) indicates that the corresponding uplink carrier does not have an associated relationship with the target downlink carrier. The MAC CE can indicate the set of uplink carriers associated with the target downlink carrier. It should be noted that MAC CE can only dynamically change the set of uplink carriers associated with a target downlink carrier.

In some optional implementations, the length of the bitmap in the MAC CE is variable. For example, the length of the bitmap depends on the number of uplink carriers (ie, Only UL carriers). The number of bytes of the bitmap is equal to (the number of uplink carriers). Quantity/8) and then rounded up.

In some optional implementations, the bits in the bitmap in the MAC CE correspond one-to-one in order from low to high, and the carrier indexes of the uplink carriers in the uplink carrier set in order from small to large, or, MAC The bits in the bitmap in the CE are in order from low to high and correspond to the carrier indexes of the uplink carriers in the uplink carrier set in order from large to small.

In some optional implementations, the MAC CE corresponds to a new logical channel identifier (LCID), and the LCID is used to identify and identify the MAC CE.

It should be noted that the format of MAC CE is not limited to the format shown in Figure 6 above, and there can be many other formats. As an example, the MAC CE includes a SCell index and at least one carrier index, where the SCell index is the SCell index corresponding to the target downlink carrier, and the carrier index is the carrier index of the uplink carrier associated with the target downlink carrier.

Application example three

The network device configures a downlink carrier set and an uplink carrier set through RRC signaling, and configures the initial association relationship between the uplink carrier and the downlink carrier. A downlink carrier can be associated with one or more uplink carriers, but an uplink carrier can only be associated with one For downlink carriers, each downlink carrier is configured with a carrier index, and each uplink carrier is configured with a carrier index.

In some optional implementations, the association between the downlink carrier and the uplink carrier configured semi-statically by RRC signaling can be dynamically changed through MAC CE or DCI.

In the embodiment of this application, there are many formats of MAC CE. As an example, referring to Figure 7, the MAC CE includes the carrier index of the target downlink carrier. The MAC CE also includes a bitmap (bitmap). Each bit (UCi) in the bitmap corresponds to the carrier index of an uplink carrier. , a bit value of 1 (or 0) indicates that the corresponding uplink carrier has an associated relationship with the target downlink carrier, and a bit value of 0 (or 1) indicates that the corresponding uplink carrier does not have an associated relationship with the target downlink carrier. The MAC CE can indicate the set of uplink carriers associated with the target downlink carrier. It should be noted that MAC CE can only dynamically change the set of uplink carriers associated with a target downlink carrier.

In some optional implementations, the length of the bitmap in the MAC CE is variable. For example, the length of the bitmap depends on the number of uplink carriers. The number of bytes of the bitmap is equal to (number of uplink carriers/8) and then upward. Rounding.

In some optional implementations, the bits in the bitmap in the MAC CE correspond one-to-one in order from low to high, and the carrier indexes of the uplink carriers in the uplink carrier set in order from small to large, or, MAC The bits in the bitmap in the CE are in order from low to high and correspond to the carrier indexes of the uplink carriers in the uplink carrier set in order from large to small.

In some optional implementations, the MAC CE corresponds to a new logical channel identifier (LCID), and the LCID is used to identify and identify the MAC CE.

It should be noted that the format of MAC CE is not limited to the format shown in Figure 7 above, and there can be many other formats. As an example, the MAC CE includes a carrier index of a downlink carrier and a carrier index of at least one uplink carrier, where at least one uplink carrier has an associated relationship with the downlink carrier.

Application example four

The network device configures a carrier group for the terminal device through RRC signaling. The carrier group includes at least one uplink carrier and at least one downlink carrier. Changes in the association between downlink carriers and uplink carriers can only be done within the carrier group.

It should be noted that the solution of application example 4 can be arbitrarily combined with the solutions of application example 1, application example 2, and application example 3 mentioned above. For the case where a carrier group is configured, in the above solution, the SCell index or carrier index corresponding to the bitmap in the MAC CE refers to the index within the carrier group, that is, the carriers are numbered within the carrier group to determine the carrier correspondence. The carrier index or SCell index. In addition, the number of bytes of the bitmap is equal to (the number of uplink carriers in the carrier group/8) and then rounded up.

In some optional implementations, the terminal device may send indication information through the RRC signaling network device. The indication information is used to indicate the carrier group recommended by the terminal device and/or the association relationship between the recommended uplink carrier and downlink carrier.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings. However, the present application is not limited to the specific details of the above-mentioned embodiments. Within the scope of the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application. These simple modifications all belong to the protection scope of this application. For example, each specific technical feature described in the above-mentioned specific embodiments can be combined in any suitable way without conflict. In order to avoid unnecessary repetition, this application will no longer describe various possible combinations. Specify otherwise. For another example, any combination of various embodiments of the present application can be carried out. As long as they do not violate the idea of the present application, they should also be regarded as the contents disclosed in the present application. For another example, on the premise of no conflict, each embodiment described in this application and/or the technical features in each embodiment can be arbitrarily combined with the existing technology, and the technical solution obtained after the combination shall also fall within the scope of this application. protected range.

It should also be understood that in the various method embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be used in this application. The execution of the examples does not constitute any limitations. In addition, in the embodiments of this application, the terms "downlink", "uplink" and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate that the transmission direction of signals or data is from the station. The first direction to the user equipment of the cell, "uplink" is used to indicate that the transmission direction of the signal or data is the second direction from the user equipment of the cell to the site, and "sidelink" is used to indicate that the transmission direction of the signal or data is A third direction sent from User Device 1 to User Device 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiment of this application, the term "and/or" is only an association relationship describing associated objects, indicating that three relationships can exist. Specifically, A and/or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

Figure 8 is a schematic structural diagram of a device for configuring a carrier provided by an embodiment of the present application. It is applied to terminal equipment. As shown in Figure 8, the device for configuring a carrier includes:

The receiving unit 801 is configured to receive the first configuration information sent by the network device, where the first configuration information is used to configure the association between the uplink carrier and the downlink carrier;

The determining unit 802 is configured to determine the association between the uplink carrier and the downlink carrier based on the first configuration information.

In some optional implementations, the first configuration information is used to configure at least one secondary cell SCell;

Each SCell in the at least one SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier, or only includes one uplink carrier.

In some optional implementations, the first configuration information is used to configure at least one of the following: at least one SCell, at least one uplink carrier;

Each SCell in the at least one SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.

In some optional implementations, in the first configuration information, each SCell in the at least one SCell is configured with an SCell index.

In some optional implementations, in the first configuration information, for an SCell that only includes one uplink carrier, a carrier index is configured for the uplink carrier in the SCell.

In some optional implementations, in the first configuration information, each uplink carrier in the at least one uplink carrier is configured with a carrier index.

In some optional implementations, for an SCell that includes only one downlink carrier or includes one uplink carrier and one downlink carrier, the SCell is identified by a physical cell identity PCI and a downlink frequency point.

In some optional implementations, the at least one SCell includes a first SCell, the first SCell includes a first uplink carrier and a first downlink carrier, and the downlink carrier associated with the first uplink carrier is the first Downlink carrier.

In some optional implementations, the at least one SCell includes a second SCell, the second SCell only includes a second uplink carrier, and the downlink carrier associated with the second uplink carrier is a downlink carrier in the third SCell;

Wherein, the third SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.

In some optional implementations, in the first configuration information, the second SCell is configured to be associated with the identification information of the third SCell;

Wherein, the identification information of the third SCell is the SCell index of the third SCell, or the PCI and downlink frequency point of the third SCell.

In some optional implementations, the at least one uplink carrier includes a second uplink carrier, and the downlink carrier associated with the second uplink carrier is a downlink carrier in the third SCell;

Wherein, the third SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.

In some optional implementations, in the first configuration information, the second uplink carrier is configured to be associated with the identification information of the third SCell;

Wherein, the identification information of the third SCell is the SCell index of the third SCell, or the PCI and downlink frequency point of the third SCell.

In some optional implementations, the receiving unit 801 is also configured to receive the first signaling sent by the network device, where the first signaling is used to change the association between the uplink carrier and the downlink carrier. .

In some optional implementations, the first signaling is media access control MAC control element CE or downlink control information DCI.

In some optional implementations, when the first signaling is MAC CE, the MAC CE includes:

First information, the first information is used to indicate the target downlink carrier;

Second information, the second information is used to indicate at least one uplink carrier that is associated with the target downlink carrier.

In some optional implementations, the first information includes an SCell index of a target SCell, and the target SCell includes the target downlink carrier.

In some optional implementations, the second information includes a first bitmap, each bit in the first bitmap corresponds to an SCell index of an SCell, and the value of the bit is used to indicate the bit Whether the uplink carrier included in the SCell corresponding to the bit is associated with the target downlink carrier.

In some optional implementations, the length of the first bitmap is a variable length, and the length of the first bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the first bitmap is equal to the number of uplink carriers divided by N and then rounded up, where N is the number of bits included in one byte, and N is a positive integer.

In some optional implementations, the first bitmap includes M bits, where M is a positive integer;

The M bits correspond to the M SCell indexes in order from low to high, in order from small to large; or,

The M bits correspond to the M SCell indexes in order from low to high, in order from large to small.

In some optional implementations, the second information includes a second bitmap, each bit in the second bitmap corresponds to a carrier index of an uplink carrier, and the value of the bit is used to indicate the Whether the uplink carrier corresponding to the bit is associated with the target downlink carrier.

In some optional implementations, the length of the second bitmap is variable, and the length of the second bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the second bitmap is equal to the number of uplink carriers divided by N and then rounded up, where N is the number of bits included in one byte, and N is a positive integer.

In some optional implementations, the second bitmap includes M bits, where M is a positive integer;

The M bits correspond to the M carrier indexes in order from low to high, in order from small to large; or,

The M bits correspond to the M carrier indexes in order from low to high, in order from large to small.

In some optional implementations, the second information includes SCell indexes of one or more SCells, and the uplink carrier included in each SCell of the one or more SCells has an association relationship with the target downlink carrier.

In some optional implementations, the second information includes carrier indexes of one or more uplink carriers, and each of the one or more uplink carriers has an association relationship with the target downlink carrier.

In some optional implementations, the first configuration information is used to configure a downlink carrier set and an uplink carrier set, the downlink carrier set includes at least one downlink carrier, and the uplink carrier set includes at least one uplink carrier.

In some optional implementations, in the first configuration information, each downlink carrier in the downlink carrier set is configured with a carrier index, and each uplink carrier in the uplink carrier set is configured with a carrier index. .

In some optional implementations, in the first configuration information, the downlink carriers in the downlink carrier set and the uplink carriers in the uplink carrier set are configured to have an associated relationship;

Wherein, the number of uplink carriers associated with one downlink carrier is one or more, and the number of downlink carriers associated with one uplink carrier is one.

In some optional implementations, the receiving unit 801 is also configured to receive second signaling sent by the network device, where the second signaling is used to change the association between the uplink carrier and the downlink carrier. .

In some optional implementations, the second signaling is MAC CE or DCI.

In some optional implementations, when the second signaling is MAC CE, the MAC CE includes:

Third information, the third information is used to indicate the target downlink carrier;

Fourth information, the fourth information is used to indicate at least one uplink carrier that is associated with the target downlink carrier.

In some optional implementations, the third information includes a carrier index of the target downlink carrier.

In some optional implementations, the fourth information includes a third bitmap, each bit in the third bitmap corresponds to a carrier index of an uplink carrier, and the value of the bit is used to indicate the Whether the uplink carrier corresponding to the bit is associated with the target downlink carrier.

In some optional implementations, the length of the third bitmap is a variable length, and the length of the third bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the third bitmap is equal to the number of uplink carriers divided by N and then rounded upward, where N is the number of bits included in one byte, and N is a positive integer.

In some optional implementations, the third bitmap includes M bits, where M is a positive integer;

The M bits correspond to the M carrier indexes in order from low to high, in order from small to large; or,

The M bits correspond to the M carrier indexes in order from low to high, in order from large to small.

In some optional implementations, the fourth information includes carrier indexes of one or more uplink carriers, and each of the one or more uplink carriers has an associated relationship with the target downlink carrier.

In some optional implementations, the receiving unit 801 is also configured to receive second configuration information, where the second configuration information is used to configure a carrier group, where the carrier group includes at least one uplink carrier and at least one downlink carrier;

The device further includes: a changing unit configured to change the association between the uplink carrier and the downlink carrier within the carrier group.

In some optional implementations, the second configuration information is carried in radio resource control RRC signaling.

In some optional implementations, the apparatus further includes: a sending unit, configured to send first indication information to the network device, where the first indication information is used to indicate the carrier group and/or recommended by the terminal device. The correlation between uplink carriers and downlink carriers within the carrier group;

Wherein, the carrier group includes at least one uplink carrier and at least one downlink carrier.

In some optional implementations, the first configuration information is carried in RRC signaling.

Persons skilled in the art should understand that the relevant description of the device for configuring a carrier in the embodiment of the present application can be understood with reference to the relevant description of the method of configuring a carrier in the embodiment of the present application.

Figure 9 is a schematic diagram 2 of the structural composition of a device for configuring a carrier provided by an embodiment of the present application. It is applied to network equipment. As shown in Figure 9, the device for configuring a carrier includes:

The sending unit 901 is configured to send first configuration information to the terminal device, where the first configuration information is used to configure the association relationship between the uplink carrier and the downlink carrier.

In some optional implementations, the first configuration information is used to configure at least one SCell;

Each SCell in the at least one SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier, or only includes one uplink carrier.

In some optional implementations, the first configuration information is used to configure at least one of the following: at least one SCell, at least one uplink carrier;

Each SCell in the at least one SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.

In some optional implementations, in the first configuration information, each SCell in the at least one SCell is configured with an SCell index.

In some optional implementations, in the first configuration information, for an SCell that only includes one uplink carrier, a carrier index is configured for the uplink carrier in the SCell.

In some optional implementations, in the first configuration information, each uplink carrier in the at least one uplink carrier is configured with a carrier index.

In some optional implementations, for an SCell that includes only one downlink carrier or includes one uplink carrier and one downlink carrier, the SCell is identified by PCI and a downlink frequency point.

In some optional implementations, the at least one SCell includes a first SCell, the first SCell includes a first uplink carrier and a first downlink carrier, and the downlink carrier associated with the first uplink carrier is the first Downlink carrier.

In some optional implementations, the at least one SCell includes a second SCell, the second SCell only includes a second uplink carrier, and the downlink carrier associated with the second uplink carrier is a downlink carrier in the third SCell;

Wherein, the third SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.

In some optional implementations, in the first configuration information, the second SCell is configured to be associated with the identification information of the third SCell;

Wherein, the identification information of the third SCell is the SCell index of the third SCell, or the PCI and downlink frequency point of the third SCell.

In some optional implementations, the at least one uplink carrier includes a second uplink carrier, and the downlink carrier associated with the second uplink carrier is a downlink carrier in the third SCell;

Wherein, the third SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.

In some optional implementations, in the first configuration information, the second uplink carrier is configured to be associated with the identification information of the third SCell;

Wherein, the identification information of the third SCell is the SCell index of the third SCell, or the PCI and downlink frequency point of the third SCell.

In some optional implementations, the sending unit 901 is further configured to send first signaling to the terminal device, where the first signaling is used to change the association relationship between the uplink carrier and the downlink carrier.

In some optional implementations, the first signaling is MAC CE or DCI.

In some optional implementations, when the first signaling is MAC CE, the MAC CE includes:

First information, the first information is used to indicate the target downlink carrier;

Second information, the second information is used to indicate at least one uplink carrier that is associated with the target downlink carrier.

In some optional implementations, the first information includes an SCell index of a target SCell, and the target SCell includes the target downlink carrier.

In some optional implementations, the second information includes a first bitmap, each bit in the first bitmap corresponds to an SCell index of an SCell, and the value of the bit is used to indicate the bit Whether the uplink carrier included in the SCell corresponding to the bit is associated with the target downlink carrier.

In some optional implementations, the length of the first bitmap is a variable length, and the length of the first bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the first bitmap is equal to the number of uplink carriers divided by N and then rounded up, where N is the number of bits included in one byte, and N is a positive integer.

In some optional implementations, the first bitmap includes M bits, where M is a positive integer;

The M bits correspond to the M SCell indexes in order from low to high, in order from small to large; or,

The M bits correspond to the M SCell indexes in order from low to high, in order from large to small.

In some optional implementations, the second information includes a second bitmap, each bit in the second bitmap corresponds to a carrier index of an uplink carrier, and the value of the bit is used to indicate the Whether the uplink carrier corresponding to the bit is associated with the target downlink carrier.

In some optional implementations, the length of the second bitmap is variable, and the length of the second bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the second bitmap is equal to the number of uplink carriers divided by N and then rounded up, where N is the number of bits included in one byte, and N is a positive integer.

In some optional implementations, the second bitmap includes M bits, where M is a positive integer;

The M bits correspond to the M carrier indexes in order from low to high, in order from small to large; or,

The M bits correspond to the M carrier indexes in order from low to high, in order from large to small.

In some optional implementations, the second information includes SCell indexes of one or more SCells, and the uplink carrier included in each SCell of the one or more SCells has an association relationship with the target downlink carrier.

In some optional implementations, the second information includes carrier indexes of one or more uplink carriers, and each of the one or more uplink carriers has an association relationship with the target downlink carrier.

In some optional implementations, the first configuration information is used to configure a downlink carrier set and an uplink carrier set, the downlink carrier set includes at least one downlink carrier, and the uplink carrier set includes at least one uplink carrier.

In some optional implementations, in the first configuration information, each downlink carrier in the downlink carrier set is configured with a carrier index, and each uplink carrier in the uplink carrier set is configured with a carrier index. .

In some optional implementations, in the first configuration information, the downlink carriers in the downlink carrier set and the uplink carriers in the uplink carrier set are configured to have an associated relationship;

Among them, the number of uplink carriers associated with one downlink carrier is one or more, and the number of downlink carriers associated with one uplink carrier is one.

In some optional implementations, the sending unit 901 is further configured to send second signaling to the terminal device, where the second signaling is used to change the association between the uplink carrier and the downlink carrier.

In some optional implementations, the second signaling is MAC CE or DCI.

In some optional implementations, when the second signaling is MAC CE, the MAC CE includes:

Third information, the third information is used to indicate the target downlink carrier;

Fourth information, the fourth information is used to indicate at least one uplink carrier that is associated with the target downlink carrier.

In some optional implementations, the third information includes a carrier index of the target downlink carrier.

In some optional implementations, the fourth information includes a third bitmap, each bit in the third bitmap corresponds to a carrier index of an uplink carrier, and the value of the bit is used to indicate the Whether the uplink carrier corresponding to the bit is associated with the target downlink carrier.

In some optional implementations, the length of the third bitmap is a variable length, and the length of the third bitmap is determined based on the number of uplink carriers.

In some optional implementations, the number of bytes of the third bitmap is equal to the number of uplink carriers divided by N and then rounded upward, where N is the number of bits included in one byte, and N is a positive integer.

In some optional implementations, the third bitmap includes M bits, where M is a positive integer;

The M bits correspond to the M carrier indexes in order from low to high, in order from small to large; or,

The M bits correspond to the M carrier indexes in order from low to high, in order from large to small.

In some optional implementations, the fourth information includes carrier indexes of one or more uplink carriers, and each of the one or more uplink carriers has an associated relationship with the target downlink carrier.

In some optional implementations, the sending unit 901 is also configured to send second configuration information to the terminal device, where the second configuration information is used to configure a carrier group, where the carrier group includes at least one uplink carrier and At least one downlink carrier; the configured carrier group supports changing the association relationship between the uplink carrier and the downlink carrier.

In some optional implementations, the second configuration information is carried in RRC signaling.

In some optional implementations, the apparatus further includes: a receiving unit, configured to receive first indication information sent by the terminal equipment, where the first indication information is used to indicate the carrier group and/or recommended by the terminal equipment. Or the correlation between uplink carriers and downlink carriers within a carrier group;

Wherein, the carrier group includes at least one uplink carrier and at least one downlink carrier.

In some optional implementations, the first configuration information is carried in RRC signaling.

Persons skilled in the art should understand that the relevant description of the device for configuring a carrier in the embodiment of the present application can be understood with reference to the relevant description of the method of configuring a carrier in the embodiment of the present application.

Figure 10 is a schematic structural diagram of a communication device 1000 provided by an embodiment of the present application. The communication device can be a terminal device or a network device. The communication device 1000 shown in Figure 10 includes a processor 1010. The processor 1010 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in Figure 10, the communication device 1000 may further include a memory 1020. The processor 1010 can call and run the computer program from the memory 1020 to implement the method in the embodiment of the present application.

The memory 1020 may be a separate device independent of the processor 1010, or may be integrated into the processor 1010.

Optionally, as shown in Figure 10, the communication device 1000 can also include a transceiver 1030. The processor 1010 can control the transceiver 1030 to communicate with other devices. Specifically, it can send information or data to other devices, or receive other devices. Information or data sent by the device.

Among them, the transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 1000 may specifically be a network device according to the embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of brevity, details will not be repeated here. .

Optionally, the communication device 1000 can be a mobile terminal/terminal device according to the embodiment of the present application, and the communication device 1000 can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application. For the sake of simplicity, , which will not be described in detail here.

Figure 11 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1100 shown in Figure 11 includes a processor 1110. The processor 1110 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 11 , the chip 1100 may also include a memory 1120 . The processor 1110 can call and run the computer program from the memory 1120 to implement the method in the embodiment of the present application.

The memory 1120 may be a separate device independent of the processor 1110, or may be integrated into the processor 1110.

Optionally, the chip 1100 may also include an input interface 1130. The processor 1110 can control the input interface 1130 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

Optionally, the chip 1100 may also include an output interface 1140. The processor 1110 can control the output interface 1140 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of brevity, the details will not be described again.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiment of the present application. For the sake of simplicity, here No longer.

It should be understood that the chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.

Figure 12 is a schematic block diagram of a communication system 1200 provided by an embodiment of the present application. As shown in Figure 12, the communication system 1200 includes a terminal device 1210 and a network device 1220.

Among them, the terminal device 1210 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1220 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, no details will be described here. .

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip and has signal processing capabilities. During the implementation process, each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software. The above-mentioned processor can 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 available processors. Programmed logic devices, discrete gate or transistor logic devices, discrete hardware components. Each method, step and logical block diagram disclosed in the embodiment of this application can be implemented or executed. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of illustration, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

It should be understood that the above memory is illustrative but not restrictive. For example, the memory in the embodiment of the present application can also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, memories in embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

Embodiments of the present application also provide a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of simplicity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiment of the present application. , for the sake of brevity, will not be repeated here.

An embodiment of the present application also provides a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of brevity, they are not included here. Again.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For the sake of brevity, no further details will be given here.

An embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of simplicity , which will not be described in detail here.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiments of the present application. When the computer program is run on the computer, it causes the computer to execute the various methods implemented by the mobile terminal/terminal device in the embodiments of the present application. The corresponding process, for the sake of brevity, will not be repeated here.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims (96)

1. A method of configuring a carrier, 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 configuring an association relationship between an uplink carrier and a downlink carrier;

   and the terminal equipment determines the association relationship between the uplink carrier and the downlink carrier based on the first configuration information.
2. The method of claim 1, wherein the first configuration information is used to configure at least one secondary cell, SCell;

   wherein each SCell of the at least one SCell comprises only one downlink carrier, or comprises one uplink carrier and one downlink carrier, or comprises only one uplink carrier.
3. The method of claim 1, wherein the first configuration information is used to configure at least one of: at least one SCell, at least one uplink carrier;

   Wherein each SCell of the at least one SCell comprises only one downlink carrier, or one uplink carrier and one downlink carrier.
4. A method according to claim 2 or 3, wherein in the first configuration information, each SCell of the at least one SCell is configured with one SCell index.
5. The method of claim 2, wherein in the first configuration information, for an SCell including only one uplink carrier, the uplink carrier in the SCell is configured with a carrier index.
6. The method of claim 3, wherein in the first configuration information, each of the at least one uplink carrier is configured with a carrier index.
7. A method according to claim 2 or 3, wherein for an SCell comprising only one downlink carrier, or comprising one uplink carrier and one downlink carrier, the SCell is identified by a physical cell identity, PCI, and a downlink frequency point.
8. A method according to claim 2 or 3, wherein the at least one SCell comprises a first SCell comprising a first uplink carrier and a first downlink carrier, the first uplink carrier associated downlink carrier being the first downlink carrier.
9. The method of claim 2, wherein the at least one SCell comprises a second SCell comprising only a second uplink carrier, the downlink carrier associated with the second uplink carrier being a downlink carrier in a third SCell;

   wherein the third SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.
10. The method of claim 9, wherein in the first configuration information, the second SCell is configured to be associated with identification information of the third SCell;

    the identification information of the third SCell is an SCell index of the third SCell, or a PCI and a downlink frequency point of the third SCell.
11. The method of claim 3, wherein the at least one uplink carrier comprises a second uplink carrier, the downlink carrier associated with the second uplink carrier being a downlink carrier in a third SCell;

    wherein the third SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.
12. The method of claim 11, wherein in the first configuration information, the second uplink carrier is configured to be associated with identification information of the third SCell;

    The identification information of the third SCell is an SCell index of the third SCell, or a PCI and a downlink frequency point of the third SCell.
13. The method of any of claims 2 to 12, wherein the method further comprises:

    the terminal equipment receives a first signaling sent by the network equipment, wherein the first signaling is used for changing the association relation between the uplink carrier and the downlink carrier.
14. The method of claim 13, wherein the first signaling is a medium access control, MAC, control element, CE, or downlink control information, DCI.
15. The method of claim 14, wherein, in the case where the first signaling is a MAC CE, the MAC CE comprises:

    the first information is used for indicating a target downlink carrier;

    and the second information is used for indicating at least one uplink carrier with an association relation with the target downlink carrier.
16. The method of claim 15, wherein the first information comprises an SCell index of a target SCell comprising the target downlink carrier.
17. The method of claim 15 or 16, wherein the second information includes a first bitmap, each bit in the first bitmap corresponds to an SCell index of one SCell, and the value of the bit is used to indicate whether an uplink carrier included in the SCell corresponding to the bit has an association relationship with the target downlink carrier.
18. The method of claim 17, wherein the length of the first bitmap is a variable length, the length of the first bitmap being determined based on a number of uplink carriers.
19. The method of claim 18, wherein the number of bytes of the first bitmap is equal to the number of uplink carriers divided by N, N being the number of bits comprised by one byte, N being a positive integer.
20. The method of any of claims 17 to 19, wherein the first bitmap comprises M bits, M being a positive integer;

    the M bits correspond to the M SCell indexes from the lower order to the higher order; or,

    the M bits correspond to the M SCell indexes in the order from the low order to the high order.
21. The method of claim 15 or 16, wherein the second information includes a second bitmap, each bit in the second bitmap corresponds to a carrier index of an uplink carrier, and the value of the bit is used to indicate whether the uplink carrier corresponding to the bit has an association relationship with the target downlink carrier.
22. The method of claim 21, wherein the length of the second bitmap is a variable length, the length of the second bitmap being determined based on a number of uplink carriers.
23. The method of claim 22, wherein the number of bytes of the second bitmap is equal to the number of uplink carriers divided by N, N being a number of bits included in one byte, and N being a positive integer.
24. The method of any of claims 21 to 23, wherein the second bitmap comprises M bits, M being a positive integer;

    the M bits correspond to the M carrier indexes from the low order to the high order according to the indexes from the low order to the high order; or,

    the M bits correspond to the M carrier indexes in the order from the low order to the high order, and the indexes are from the high order to the low order.
25. The method of claim 15 or 16, wherein the second information includes SCell indexes of one or more scells, each of the one or more scells including an uplink carrier having an association relationship with the target downlink carrier.
26. The method of claim 15 or 16, wherein the second information includes carrier indexes of one or more uplink carriers, each of the one or more uplink carriers having an association relationship with the target downlink carrier.
27. The method of claim 1, wherein the first configuration information is used to configure a downlink carrier set comprising at least one downlink carrier and an uplink carrier set comprising at least one uplink carrier.
28. The method of claim 27, wherein in the first configuration information, each downlink carrier in the set of downlink carriers is configured with a carrier index, and each uplink carrier in the set of uplink carriers is configured with a carrier index.
29. The method of claim 27 or 28, wherein, in the first configuration information, a downlink carrier in the downlink carrier set and an uplink carrier in the uplink carrier set are configured to have an association relationship;

    wherein, the number of the uplink carriers associated with one downlink carrier is one or more, and the number of the downlink carriers associated with one uplink carrier is one.
30. The method of any one of claims 27 to 29, wherein the method further comprises:

    the terminal equipment receives a second signaling sent by the network equipment, wherein the second signaling is used for changing the association relation between the uplink carrier and the downlink carrier.
31. The method of claim 30, wherein the second signaling is a MAC CE or DCI.
32. The method of claim 31, wherein, in the case where the second signaling is a MAC CE, the MAC CE comprises:

    third information, wherein the third information is used for indicating a target downlink carrier;

    Fourth information, where the fourth information is used to indicate at least one uplink carrier having an association relationship with the target downlink carrier.
33. The method of claim 32, wherein the third information comprises a carrier index of a target downlink carrier.
34. The method of claim 32 or 33, wherein the fourth information includes a third bitmap, each bit in the third bitmap corresponds to a carrier index of an uplink carrier, and the value of the bit is used to indicate whether the uplink carrier corresponding to the bit has an association relationship with the target downlink carrier.
35. The method of claim 34, wherein the length of the third bitmap is a variable length, the length of the third bitmap being determined based on a number of uplink carriers.
36. The method of claim 35, wherein the number of bytes of the third bitmap is equal to the number of uplink carriers divided by N, N being the number of bits included in one byte, and N being a positive integer.
37. The method of any of claims 34 to 36, wherein the third bitmap comprises M bits, M being a positive integer;

    the M bits correspond to the M carrier indexes from the low order to the high order according to the indexes from the low order to the high order; or,

    The M bits correspond to the M carrier indexes in the order from the low order to the high order, and the indexes are from the high order to the low order.
38. The method of claim 32 or 33, wherein the fourth information comprises carrier indices of one or more uplink carriers, each of the one or more uplink carriers having an association with the target downlink carrier.
39. The method of any one of claims 1 to 38, wherein the method further comprises:

    the terminal equipment receives second configuration information, wherein the second configuration information is used for configuring a carrier group, and the carrier group comprises at least one uplink carrier and at least one downlink carrier;

    and the terminal equipment changes the association relation between the uplink carrier and the downlink carrier in the carrier group.
40. The method of claim 39, wherein the second configuration information is carried in radio resource control, RRC, signaling.
41. The method of any one of claims 1 to 40, 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 a carrier group suggested by the terminal equipment and/or an association relationship between an uplink carrier and a downlink carrier in the carrier group;

    Wherein, the carrier group includes at least one uplink carrier and at least one downlink carrier.
42. The method of any one of claims 1 to 41, wherein the first configuration information is carried in RRC signaling.
43. A method of configuring a carrier, the method comprising:

    the network equipment sends first configuration information to the terminal equipment, wherein the first configuration information is used for configuring the association relation between the uplink carrier and the downlink carrier.
44. The method of claim 43, wherein the first configuration information is used to configure at least one SCell;

    wherein each SCell of the at least one SCell comprises only one downlink carrier, or comprises one uplink carrier and one downlink carrier, or comprises only one uplink carrier.
45. The method of claim 43, wherein the first configuration information is used to configure at least one of: at least one SCell, at least one uplink carrier;

    wherein each SCell of the at least one SCell comprises only one downlink carrier, or one uplink carrier and one downlink carrier.
46. The method of claim 44 or 45, wherein in the first configuration information, each SCell of the at least one SCell is configured with one SCell index.
47. The method of claim 44, wherein in the first configuration information, for an SCell including only one uplink carrier, the uplink carrier in the SCell is configured with a carrier index.
48. The method of claim 45, wherein in the first configuration information, each of the at least one uplink carrier is configured with a carrier index.
49. The method of claim 44 or 45, wherein for an SCell comprising only one downlink carrier, or comprising one uplink carrier and one downlink carrier, the SCell is identified by a PCI and a downlink frequency point.
50. The method of claim 44 or 45, wherein the at least one SCell comprises a first SCell comprising a first uplink carrier and a first downlink carrier, the first uplink carrier associated downlink carrier being the first downlink carrier.
51. The method of claim 44, wherein the at least one SCell comprises a second SCell comprising only a second uplink carrier, the downlink carrier associated with the second uplink carrier being a downlink carrier in a third SCell;

    wherein the third SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.
52. The method of claim 51, wherein in the first configuration information, the second SCell is configured to be associated with identification information of the third SCell;

    the identification information of the third SCell is an SCell index of the third SCell, or a PCI and a downlink frequency point of the third SCell.
53. The method of claim 45, wherein the at least one uplink carrier comprises a second uplink carrier, the downlink carrier associated with the second uplink carrier being a downlink carrier in a third SCell;

    wherein the third SCell includes only one downlink carrier, or includes one uplink carrier and one downlink carrier.
54. The method of claim 53, wherein in the first configuration information, the second uplink carrier is configured to be associated with identification information of the third SCell;

    the identification information of the third SCell is an SCell index of the third SCell, or a PCI and a downlink frequency point of the third SCell.
55. The method of any one of claims 44 to 54, wherein the method further comprises:

    the network device sends a first signaling to the terminal device, wherein the first signaling is used for changing the association relationship between the uplink carrier and the downlink carrier.
56. The method of claim 55, wherein the first signaling is a MAC CE or DCI.
57. The method of claim 56, wherein, in the case where the first signaling is a MAC CE, the MAC CE comprises:

    the first information is used for indicating a target downlink carrier;

    and the second information is used for indicating at least one uplink carrier with an association relation with the target downlink carrier.
58. The method of claim 57, wherein the first information comprises an SCell index of a target SCell comprising the target downlink carrier.
59. The method of claim 57 or 58, wherein the second information includes a first bitmap, each bit in the first bitmap corresponds to an SCell index of one SCell, and the value of the bit is used to indicate whether an uplink carrier included in the SCell corresponding to the bit has an association relationship with the target downlink carrier.
60. The method of claim 59, wherein the first bitmap has a variable length, and the length of the first bitmap is determined based on the number of uplink carriers.
61. The method of claim 60, wherein the number of bytes of the first bitmap is equal to the number of uplink carriers divided by N, N being the number of bits included in one byte, and N being a positive integer.
62. The method of any one of claims 59 to 61, wherein the first bitmap comprises M bits, M being a positive integer;

    the M bits correspond to the M SCell indexes from the lower order to the higher order; or,

    the M bits correspond to the M SCell indexes in the order from the low order to the high order.
63. The method of claim 57 or 58, wherein the second information includes a second bitmap, each bit in the second bitmap corresponds to a carrier index of an uplink carrier, and the value of the bit is used to indicate whether the uplink carrier corresponding to the bit has an association relationship with the target downlink carrier.
64. The method of claim 63, wherein the length of the second bitmap is a variable length, the length of the second bitmap being determined based on the number of uplink carriers.
65. The method of claim 64, wherein the number of bytes of the second bitmap is equal to the number of uplink carriers divided by N, N being the number of bits included in one byte and N being a positive integer.
66. The method of any one of claims 63 to 65, wherein the second bitmap comprises M bits, M being a positive integer;

    The M bits correspond to the M carrier indexes from the low order to the high order according to the indexes from the low order to the high order; or,

    the M bits correspond to the M carrier indexes in the order from the low order to the high order, and the indexes are from the high order to the low order.
67. The method of claim 57 or 58, wherein the second information comprises SCell indices of one or more scells, each of the one or more scells comprising an uplink carrier having an association with the target downlink carrier.
68. The method of claim 57 or 58, wherein the second information comprises carrier indices of one or more uplink carriers, each of the one or more uplink carriers having an association with the target downlink carrier.
69. A method as defined in claim 43, wherein the first configuration information is used to configure a downlink carrier set including at least one downlink carrier and an uplink carrier set including at least one uplink carrier.
70. The method of claim 69, wherein in the first configuration information, each downlink carrier in the downlink carrier set is configured with a carrier index, and each uplink carrier in the uplink carrier set is configured with a carrier index.
71. The method of claim 69 or 70, wherein, in the first configuration information, a downlink carrier in the downlink carrier set and an uplink carrier in the uplink carrier set are configured to have an association relationship;

    wherein, the number of the uplink carriers associated with one downlink carrier is one or more, and the number of the downlink carriers associated with one uplink carrier is one.
72. The method of any one of claims 69 to 71, wherein the method further comprises:

    the network device sends a second signaling to the terminal device, where the second signaling is used to change the association relationship between the uplink carrier and the downlink carrier.
73. The method of claim 72, wherein the second signaling is a MAC CE or DCI.
74. The method of claim 73, wherein, in the case where the second signaling is a MAC CE, the MAC CE comprises:

    third information, wherein the third information is used for indicating a target downlink carrier;

    fourth information, where the fourth information is used to indicate at least one uplink carrier having an association relationship with the target downlink carrier.
75. The method of claim 74, wherein the third information comprises a carrier index of a target downlink carrier.
76. The method of claim 74 or 75, wherein the fourth information includes a third bitmap, each bit in the third bitmap corresponds to a carrier index of an uplink carrier, and the value of the bit is used to indicate whether the uplink carrier corresponding to the bit has an association relationship with the target downlink carrier.
77. The method of claim 76, wherein the length of the third bitmap is a variable length, the length of the third bitmap being determined based on a number of uplink carriers.
78. The method of claim 77, wherein the number of bytes of the third bitmap is equal to the number of uplink carriers divided by N, N being the number of bits comprised by one byte, N being a positive integer.
79. The method of any one of claims 76 to 78, wherein the third bitmap comprises M bits, M being a positive integer;

    the M bits correspond to the M carrier indexes from the low order to the high order according to the indexes from the low order to the high order; or,

    the M bits correspond to the M carrier indexes in the order from the low order to the high order, and the indexes are from the high order to the low order.
80. The method of claim 74 or 75, wherein the fourth information comprises carrier indices of one or more uplink carriers, each of the one or more uplink carriers having an association with the target downlink carrier.
81. The method of any one of claims 43 to 80, 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 carrier group, and the carrier group comprises at least one uplink carrier and at least one downlink carrier; and supporting and changing the association relation between the uplink carrier and the downlink carrier in the configuration carrier group.
82. The method of claim 81, wherein the second configuration information is carried in RRC signaling.
83. The method of any one of claims 43 to 82, wherein the method further comprises:

    the network equipment receives first indication information sent by the terminal equipment, wherein the first indication information is used for indicating a carrier group suggested by the terminal equipment and/or an association relationship between an uplink carrier and a downlink carrier in the carrier group;

    wherein, the carrier group includes at least one uplink carrier and at least one downlink carrier.
84. The method of any of claims 43-83, wherein the first configuration information is carried in RRC signaling.
85. An apparatus for configuring a carrier wave, 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 configure an association relationship between an uplink carrier and a downlink carrier;

    and the determining unit is used for determining the association relation between the uplink carrier and the downlink carrier based on the first configuration information.
86. An apparatus for configuring a carrier wave for use in a network device, the apparatus comprising:

    the sending unit is used for sending first configuration information to the terminal equipment, wherein the first configuration information is used for configuring the association relationship between the uplink carrier and the downlink carrier.
87. 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 42.
88. 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 43 to 84.
89. 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 42.
90. A chip, comprising: a processor for calling and running a computer program from memory, causing a device on which the chip is mounted to perform the method of any one of claims 43 to 84.
91. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 42.
92. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 43 to 84.
93. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 42.
94. A computer program product comprising computer program instructions which cause a computer to perform the method of any one of claims 43 to 84.
95. A computer program which causes a computer to perform the method of any one of claims 1 to 42.
96. A computer program which causes a computer to perform the method of any one of claims 43 to 84.