WO2022011625A1

WO2022011625A1 - Carrier aggregation configuration method and apparatus, device and storage medium

Info

Publication number: WO2022011625A1
Application number: PCT/CN2020/102260
Authority: WO
Inventors: 王淑坤; 石聪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-07-16
Filing date: 2020-07-16
Publication date: 2022-01-20
Also published as: CN115699866A

Abstract

The present application provides a carrier aggregation configuration method and apparatus, a device and a storage medium, and in a specific solution, carrier aggregation of carriers of different RATs can be implemented by using a common MAC entity. The present application further provides an inter-site carrier aggregation configuration solution, and in the process of configuring carrier aggregation by a network device, transmission and configuration of a protocol stack are performed according to whether UE supports inter-RAT carrier aggregation or inter-site carrier aggregation, so as to further increase aggregatable bandwidth, and increase the transmission rate.

Description

Configuration method, apparatus, device and storage medium for carrier aggregation

technical field

The embodiments of the present application relate to communication technologies, and in particular, to a configuration method, apparatus, device, and storage medium for carrier aggregation.

Background technique

At present, with people's pursuit of speed, delay, high-speed mobility, energy efficiency, and the diversity and complexity of business in future life, the 3rd Generation Partnership Project (3GPP) international standards organization has begun to develop The fifth generation mobile communication technology (5th generation mobile networks, 5G), also known as New Radio (New Radio, NR) technology. The main application scenarios of 5G are: Enhanced Mobile Broadband (eMBB), Ultra-reliable and Low Latency Communications (URLLC), Massive Machine Type of Communication (mMTC) ).

In the early deployment of NR, complete NR coverage is difficult to obtain, so typical network coverage is the long-term evolution (Long Term Evolution, LTE) coverage of the wide area and the island coverage mode of NR. And a lot of LTE is deployed in sub-6GHz, and there is very little sub-6GHz spectrum available for 5G. Therefore, NR must study the spectrum application above 6GHz, while the high frequency band has limited coverage and fast signal fading. At the same time, in order to protect the early investment of mobile operators in LTE, a working mode of tight interworking between LTE and NR is proposed. In order to realize 5G network deployment and commercial applications as soon as possible, 3GPP is completing the first 5G version, namely E-UTRA and NR Dual Connectivity (LTE-NR Dual Connectivity, EN-DC). Here, LTE is used as the master node (Master Node, MN), and NR is used as the secondary node (Secondary Node, SN). FIG. 1 is a schematic diagram of a network deployment and networking architecture provided by the prior art. As shown in FIG. 1, the main radio resource control (Radio Resource Control, RRC) control function of the MN node and the control plane leading to the CN , SN node can configure auxiliary signaling, mainly provide data transmission function. Under this architecture, in order to meet the transmission requirements in the aforementioned application scenarios, the transmission rate can be increased through carrier aggregation. At present, the transmission rate can be improved by performing carrier aggregation between the carriers of the same site and the same radio access technology (Radio Access Technology, RAT).

However, in the prior art, only carrier aggregation between carriers of the same RAT with co-sites is supported, and carrier aggregation across sites or across RATs cannot be supported yet.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a configuration method, apparatus, device, and storage medium for carrier aggregation, and propose carrier aggregation of NR carriers and LTE carriers, as well as a cross-site carrier aggregation mechanism, which can further improve the transmission rate.

In the first aspect, the embodiments of the present application may provide a configuration method for carrier aggregation, which is applied to a network device, and the method includes:

Acquire configuration information for the UE, where the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes carriers of at least two RATs;

sending the configuration information to the UE.

In the second aspect, the embodiments of this application may provide a configuration method for carrier aggregation, which is applied to a user equipment UE, and the method includes:

The configuration information sent by the network device is received, where the configuration information may be a carrier list for carrier aggregation, and the carrier list includes carriers of at least two RATs.

In a third aspect, the embodiments of the present application may provide a configuration method for carrier aggregation, which is applied to a first network device, where an Xn interface of the first network device is connected to a second network device, and the method includes:

Acquire configuration information for the user equipment UE, the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes a carrier of the first network device and a carrier of the second network device;

sending the configuration information to the UE.

In a fourth aspect, the embodiments of the present application may provide a configuration method for carrier aggregation, which is applied to a user equipment UE, and the method includes:

Receive configuration information sent by a first network device, where the configuration information includes a list of carriers that can perform carrier aggregation, and the carrier list includes a carrier of the first network device and a carrier of a second network device, and the second network The device is connected to the Xn interface of the first network device, and provides resources for the UE.

In a fifth aspect, the embodiments of the present application may provide a transmission method, which is applied to a second network device, where the second network device is connected to an Xn interface of the first network device, and the method includes:

Receive TB data and/or first scheduling information sent by the first network device through the Xn interface, where the first scheduling information is used for the second network device to send downlink data.

In a sixth aspect, an embodiment of the present application may provide a configuration device for carrier aggregation, including:

a processing module, configured to acquire configuration information for the UE, where the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes carriers of at least two RATs;

A sending module, configured to send the configuration information to the UE.

In a seventh aspect, an embodiment of the present application may provide an apparatus for configuring carrier aggregation, including:

A receiving module, configured to receive configuration information sent by a network device, where the configuration information can perform a carrier list for carrier aggregation, and the carrier list includes carriers of at least two RATs.

In an eighth aspect, an embodiment of the present application may provide an apparatus for configuring carrier aggregation. A second network device is connected to an Xn interface of the apparatus for configuring carrier aggregation, and the apparatus includes:

a processing module, configured to acquire configuration information for the UE, where the configuration information includes a list of carriers that can perform carrier aggregation, and the carrier list includes the carriers of the configuration apparatus for carrier aggregation and the carriers of the second network device;

A sending module, configured to send the configuration information to the UE.

In a ninth aspect, an embodiment of the present application may provide a configuration device for carrier aggregation, including:

a receiving module, configured to receive configuration information sent by a first network device, where the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes a carrier of the first network device and a carrier of the second network device, The second network device is connected to the Xn interface of the first network device, and provides resources for the carrier aggregation configuration apparatus.

In a tenth aspect, an embodiment of the present application may provide a transmission apparatus, where the transmission apparatus is connected to an Xn interface of a first network device, and the apparatus includes:

A receiving module, configured to receive TB data and/or first scheduling information sent by the first network device through the Xn interface, where the first scheduling information is used for the transmission device to send downlink data.

In an eleventh aspect, an embodiment of the present application may provide a network device, including:

processors, memories, interfaces for communicating with user equipment;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor performs the configuration method for carrier aggregation of the first aspect.

In a twelfth aspect, the embodiments of the present application may provide a user equipment, including:

processors, memories, interfaces for communicating with network devices;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the configuration method for carrier aggregation described in the second aspect.

In a thirteenth aspect, an embodiment of the present application may provide a network device, including:

Processors, memories, interfaces for communicating with other network equipment or user equipment;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the configuration method for carrier aggregation described in the third aspect.

In a fourteenth aspect, an embodiment of the present application may provide a user equipment, including:

processors, memories, interfaces for communicating with network devices;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the configuration method for carrier aggregation described in the fourth aspect.

In a fifteenth aspect, the embodiments of the present application may provide a network device, including:

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the transmission method of the fifth aspect.

In a sixteenth aspect, embodiments of the present application may provide a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, are used to implement the first Aspect or the configuration method for carrier aggregation described in the third aspect.

In a seventeenth aspect, embodiments of the present application may provide a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, are used to implement the second The configuration method for carrier aggregation according to any one of the aspect or the fourth aspect.

In an eighteenth aspect, embodiments of the present application may provide a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, are used to implement the claims The transmission method described in the fifth aspect.

In a nineteenth aspect, an embodiment of the present application may provide a chip, including: a processing module and a communication interface, where the processing module is configured to perform the carrier aggregation configuration method described in the first aspect or the third aspect.

In a twentieth aspect, an embodiment of the present application may provide a chip, including: a processing module and a communication interface, where the processing module is configured to perform the carrier aggregation configuration method described in the second aspect or the fourth aspect.

In a twenty-first aspect, an embodiment of the present application may provide a chip, including: a processing module and a communication interface, where the processing module is configured to execute the transmission method described in the fifth aspect.

The configuration method, device, device, and storage medium for carrier aggregation provided by the embodiments of the present application, in the technical solutions provided by the embodiments of the present application, the carrier aggregation of carriers of different RATs can be realized by sharing the MAC entity, and a cross-site address is also provided. The configuration scheme of carrier aggregation, in the configuration process of carrier aggregation by network equipment, according to whether the UE supports cross-RAT carrier aggregation or cross-site carrier aggregation for transmission and configuration of the protocol stack, to further improve the aggregated bandwidth and improve the transmission rate .

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present application, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without any creative effort.

1 is a schematic diagram of a network deployment and networking architecture provided by the prior art;

FIG. 2 is a schematic flowchart of Embodiment 1 of a configuration method for carrier aggregation provided by the present application;

3 is a schematic flowchart of Embodiment 2 of a configuration method for carrier aggregation provided by the present application;

4 is a schematic diagram of a protocol stack of a common MAC entity of an LTE carrier and an NR carrier provided by the present application;

5 is a schematic diagram of another protocol stack of the common MAC entity of the LTE carrier and the NR carrier provided by the present application;

6 is a schematic diagram of a protocol stack of an LTE carrier and an NR carrier corresponding to independent MAC entities provided by the present application;

7 is a schematic diagram of another protocol stack corresponding to the independent MAC entity of the LTE carrier and the NR carrier provided by the present application;

FIG. 8 is a schematic flowchart of Embodiment 3 of a configuration method for carrier aggregation provided by the present application;

9 is a schematic diagram of a protocol stack of carrier aggregation across sites provided by the present application;

FIG. 10 is a schematic structural diagram of Embodiment 1 of an apparatus for configuring carrier aggregation provided by the present application;

FIG. 11 is a schematic structural diagram of Embodiment 2 of an apparatus for configuring carrier aggregation provided by the present application;

FIG. 12 is a schematic structural diagram of Embodiment 3 of an apparatus for configuring carrier aggregation provided by the present application;

FIG. 13 is a schematic structural diagram of Embodiment 4 of an apparatus for configuring carrier aggregation provided by the present application;

FIG. 14 is a schematic structural diagram of an embodiment of a transmission device provided by the present application;

FIG. 15 is a schematic structural diagram of Embodiment 1 of a network device provided by this application;

FIG. 16 is a schematic structural diagram of an embodiment of a user equipment provided by this application;

FIG. 17 is a schematic structural diagram of Embodiment 2 of a network device provided by this application.

detailed description

In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments It is a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The terms "first", "second" and the like in the description, claims and the above-mentioned drawings of the embodiments of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It is to be understood that the data so used may be interchanged under appropriate circumstances such that the embodiments of the application described herein can, for example, be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

In the current technology, only carrier aggregation between co-sited and the same radio access technology (Radio Access Technology, RAT) carrier is supported. Before New Radio (NR) technology, each RAT corresponds to its own core network, but in NR, NR connects to 5G Core Network (5GC), and Long Term Evolution (LTE) also It has evolved and can be connected to 5GC. All NR and LTE can be connected to the same core network, which is 5GC. In order to further improve the rate in exchange for bandwidth, carrier aggregation of NR carriers and LTE carriers, as well as a cross-site carrier aggregation mechanism, are proposed here.

Because the same coverage between the aggregated carriers can only be aggregated, there may not be many carriers that can be aggregated in a coverage area, so the bandwidth of carrier aggregation is limited to a certain extent. In order to improve the possibility of carrier aggregation, Support cross-RAT carrier aggregation, cross-site carrier aggregation is very meaningful, and can improve the transmission rate.

This application mainly involves two types of executive bodies, network equipment and user equipment. In this solution, it should be understood that the network device may be a device that communicates with the UE (or referred to as terminal device, communication terminal, terminal). A network device can provide communication coverage for a specific geographic area, and can communicate with terminal devices located within the coverage area. Optionally, the network device may be a base station (Base Transceiver Station, BTS) in a Global System for Mobile Communications (GSM) system or a Code Division Multiple Access (Code Division Multiple Access, CDMA) system, or It is a base station (NodeB, NB) in the WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in the LTE system, or a wireless radio in the Cloud Radio Access Network (CRAN). The controller, or the network device can be a network-side device in a 5G network or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), or can also provide communication coverage in a new NR technology equipment, etc., there are no specific restrictions on this program.

"UE" as used herein includes, but is not limited to, connections via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connections; and/or another data connection/network; and/or via a wireless interface, e.g. for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and/or a device configured to receive/transmit communication signals; and/or an Internet of Things (IoT) device. A UE arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radio telephones with data processing, facsimile, and data communication capabilities; may include radio telephones, pagers, Internet/Intranet PDAs with networking access, web browsers, memo pads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or others including radiotelephone transceivers electronic device. In a specific implementation, UE may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user equipment. The UE may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication function Handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved PLMNs, etc. In this embodiment of the present application, the UE has an interface for communicating with a network device (eg, a cellular network).

With the development of technology, 5G technology will support more dual-connection modes. In order to further improve the transmission rate, the existing technology only supports the carrier aggregation method of the same RAT and the same site, which cannot meet the current scenario. For example, before NR, each RAT corresponds to its own core network, but in NR, NR is connected to 5GC, and LTE has also evolved to connect to 5GC. All NR and LTE can be connected to the same core network, which is 5GC. In order to further improve the rate in exchange for bandwidth, carrier aggregation across RAT technologies is proposed here. For example, carrier aggregation of NR carriers and LTE carriers, and carrier aggregation across sites can be used to aggregate more carriers in this way. Transmission rate. Hereinafter, the technical solutions of the present application will be described through several specific embodiments.

FIG. 2 is a schematic flowchart of Embodiment 1 of the configuration method for carrier aggregation provided by the present application. As shown in FIG. 2 , the configuration method for carrier aggregation involves network equipment and UE, and specifically includes the following steps:

S101: Acquire configuration information for the UE, where the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes carriers of at least two RATs.

In this step, the network equipment can configure the carrier aggregation of the accessed UE according to the carrier aggregation capability supported by the UE and the measurement of each different RAT, and obtain configuration information. In the configuration information, at least the configuration is required. Carriers that can be aggregated are carriers of different RAT technologies. For example, the configured carrier list includes NR carriers and LTE carriers.

S102: Send the configuration information to the UE.

In this step, after acquiring the configuration information of carrier aggregation for the UE, the network device sends the configuration information to the UE. After receiving the configuration information, the UE performs data transmission according to the carrier list configured by the configuration information.

In the specific implementation of this solution, the configuration information can also configure the protocol stack. In order to achieve aggregation between carriers across RATs, in this solution, carriers of different RATs share a Media Access Control (MAC) entity. The MAC entity may be a mixed MAC entity with functions of multiple RAT MAC entities, namely mixed MAC.

In a specific implementation of the solution, in order to perform carrier aggregation configuration, the network device first needs to obtain the capability information of the UE, and perform frequency measurement configuration, so as to configure the UE to measure the frequency points of different RATs. FIG. 3 is a schematic flowchart of Embodiment 2 of the configuration method for carrier aggregation provided by the present application. As shown in FIG. 3 , the specific implementation steps of the above step S101 include:

S201: Report capability information to a network device, where the capability information is used to indicate whether the UE supports cross-RAT carrier aggregation.

In this step, after the UE is in the connected state, the capability information needs to be reported to the network device, that is, the network side needs to indicate whether the UE supports cross-RAT carrier aggregation.

The capability information may also indicate the type of carrier aggregation specifically supported by the UE. In an implementation manner, the type of carrier aggregation includes a common MAC entity or an independent MAC entity, that is, an aggregated carrier common MAC or an independent MAC.

S202: Measure the frequency points of different RATs according to the configuration of the network device, and obtain the frequency point measurement result.

In this step, after the UE accesses the network, the network device may configure the UE to perform frequency measurement. In this solution, the network device may configure the UE to measure the frequencies of different RATs to obtain corresponding frequency measurement results.

S203: Report the frequency point measurement result corresponding to each RAT to the network device.

After obtaining the frequency point measurement results, the UE reports the obtained frequency point measurement results of different RATs to the network device.

S204: Determine whether to configure cross-RAT carrier aggregation according to the frequency point measurement result corresponding to each RAT and the capability information.

In this step, after obtaining the capability information of the UE and the frequency measurement results of different RATs, the network device will determine whether to configure cross-RAT carrier aggregation for the UE according to the frequency measurement results of different RATs and the capability information of the UE. .

In the configuration method for carrier aggregation provided in this embodiment, after the UE accesses the network, it reports capability information on whether it supports cross-RAT carrier aggregation to the network device, and the network device determines whether to configure the UE to perform cross-RAT carrier aggregation based on the capability information and the frequency measurement result RAT carrier aggregation. During the configuration process, the configuration information configured by the network device includes at least two or more RAT carriers that can be aggregated. After the UE obtains the configuration information, in the process of data transmission, it can be Carrier aggregation of multiple RAT carriers can further increase the bandwidth during transmission and improve the efficiency of data transmission.

On the basis of any of the above embodiments, the network device configuring the UE to perform cross-RAT carrier aggregation may specifically configure carriers of different RATs to share the same MAC entity or different RAT carriers correspond to independent MAC entities.

In the case where the carriers of different RATs share the same MAC entity, the carriers of the at least two RATs share the same service data adaptation protocol (service data adaptation protocol, SDAP) entity.

In the case of this solution, the MAC entity has the MAC layer function of the at least two RATs, that is to say, the MAC entity can serve the above-mentioned at least two RATs.

Or, in another implementation, the MAC entity has a MAC layer function of any one of the at least two RATs, wherein the MAC entity may be determined according to the RAT of the primary carrier. In the implementation of the solution, a MAC adaptation layer is configured under the MAC entity to implement the MAC layer function of the RAT that the MAC entity does not have. That is to say, the configuration information is also used to configure the MAC adaptation layer located under the MAC entity, and the MAC adaptation layer is used to provide the MAC layer function of the carrier of the RAT different from the MAC entity.

In another case, the configuration information may be that the carriers of the at least two RATs share the same SDAP entity, the carriers of the same RAT share the same MAC entity, and the carriers of each RAT correspond to different MAC entities, that is, different RATs A carrier corresponds to an independent MAC entity.

When the network device configures cross-RAT carrier aggregation, it can also perform protocol stack configuration and other configurations. Specifically, you can also configure:

(1) Cross-carrier scheduling can be performed between carriers of the same RAT in the carrier list.

(2), the physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) transmission of the carrier of the same RAT in the configuration carrier list is fed back through the physical uplink control channel (Physical Uplink Control Channel, PUCCH) of the RAT carrier.

(3) Configure the same RAT carrier in the carrier list to include at least one carrier used for physical uplink control channel PUCCH transmission.

(4) The carriers of different RATs in the carrier list are respectively configured with discontinuous reception (Discontinuous Reception, DRX) timers, and the DRX timers are used to monitor the physical downlink control channel (Physical Downlink Control Channel) on the carrier of the corresponding RAT Channel, PDCCH).

On the basis of the above-mentioned embodiment, the following takes the LTE carrier and the NR carrier as examples to introduce the configuration of the cross-RAT carrier. The configuration list sent by the network device to the UE includes the LTE carrier and the NR carrier. In this solution, the NR carrier and the LTE carrier share the same site.

FIG. 4 is a schematic diagram of a protocol stack of a common MAC entity of an LTE carrier and an NR carrier provided by the present application. As shown in Figure 4, the network equipment can be configured when performing cross-RAT carrier aggregation for the UE:

(1) A single SDAP entity is shared between the LTE carrier and the NR carrier aggregated across the RATs, and the carriers aggregated by different RATs correspond to the same MAC entity.

In a specific implementation, the version of the MAC entity is a mixed MAC entity with LTE MAC entity function and NR MAC entity function, and mixed MAC.

(2) The network device (network side) is configured with SDAP, bearer configuration (Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC)) and MAC configuration, and the corresponding carrier list. It also supports whether each carrier in the carrier list is LTE or NR.

The version of the PDCP entity is the NR version, and the version of the RLC entity may be the LTE version or the NR version. It can be configured through a network device, or it can be fixed to NR version.

That is, in a specific implementation manner, the configuration information is also used to configure the PDCP entity to have the function of the PDCP layer of the NR carrier, and the configuration information is also used to configure the RLC entity to support the LTE technology or support the NR technology.

(3) Cross-carrier scheduling can only occur between two carriers of the same RAT, that is to say, cross-carrier scheduling can only be performed between two carriers of LTE, or, it can only be performed between two carriers of NR. Check for cross-carrier scheduling.

(4) The feedback of downlink PDSCH transmission is also fed back on the PUCCH of the respective RAT. Among the carriers corresponding to each RAT, at least one carrier is configured to have PUCCH configuration information.

(5), the NR carrier list and the LTE carrier list are respectively configured with their own DRX to control the monitoring of the PDCCH. For DRX of NR RAT, only the PDCCH of the NR carrier can trigger the timer of NR DRX. For DRX of LTE RAT, only the PDCCH of the LTE carrier can trigger the timer of LTE DRX.

(6) Other MAC layer functions, such as SR, Power Headroom Report (PHR), Buffer Status Report (BSR), scell carrier management, etc., are implemented according to the functions of NR MAC.

FIG. 5 is a schematic diagram of another protocol stack of the common MAC entity of the LTE carrier and the NR carrier provided by the present application. As shown in Figure 5, the network equipment can configure the following when performing cross-RAT carrier aggregation for the UE:

(1), configure a common SDAP entity between carriers aggregated across RATs, and carriers aggregated by different RATs correspond to the same MAC entity.

In this solution, the version of the MAC entity depends on whether the primary carrier (PCell) is an LTE carrier or an NR carrier. If the PCell is an LTE carrier, the MAC entity is the LTE version, otherwise it is the NR version. Since the MAC entity in this solution only has the function of one RAT, a MAC adaptation layer is set under the MAC entity. The role of the MAC adaptation layer is to implement different RAT functions for the carriers of different RATs or to provide the MAC layer functions of the RAT of the carrier for the carriers of the RATs different from the MAC entity.

(2), the network side configures SDAP, bearer configuration (PDCP, RLC) and MAC configuration, and a corresponding carrier list. It also supports whether each carrier in the carrier list is LTE or NR.

The version of the PDCP entity is the NR version, and the version of the RLC entity can be the LTE version or the NR version, which is configured on the network side or fixed to the NR version.

In the above two specific solutions, the network device can configure the UE to perform carrier aggregation when the same MAC entity is used for the LTE carrier and the NR carrier, and the MAC entity needs to be able to adapt to different RATs. When the UE performs data transmission, the data can be mapped to any carrier (including an LTE carrier or an NR carrier) that can transmit data for transmission, which can better reflect the gain of carrier aggregation.

FIG. 6 is a schematic diagram of a protocol stack of an independent MAC entity corresponding to an LTE carrier and an NR carrier provided by the present application. As shown in Figure 6, the network equipment can be configured when performing cross-RAT carrier aggregation for the UE (in this solution, the LTE carrier and the NR carrier serve different PDU sessions respectively):

(1) The network side can configure the protocol stack configuration and aggregated carrier configuration of another RAT only when two or more Packet Data Unit (PDU) sessions are established, that is to say, the network device Configure after two or more PDU sessions are established.

(2), configure the SDAP configuration, bearer configuration (PDCP, RLC) and MAC configuration corresponding to one RAT for each PDU session, and the corresponding carrier list.

(3) Similar to the foregoing scheme, cross-carrier scheduling can only occur between two carriers of the same RAT.

(4), whether the version of the protocol stack is LTE or NR depends on which RAT the protocol stack serves.

(5) The feedback of downlink PDSCH transmission is also fed back on the PUCCH of the respective RAT. Among the carriers corresponding to each RAT, at least one carrier is configured to have PUCCH configuration information.

In this solution, the protocol stacks of the two RATs are relatively independent and relatively easy to implement.

FIG. 7 is a schematic diagram of another protocol stack of the independent MAC entities corresponding to the LTE carrier and the NR carrier provided by the present application. As shown in Figure 7, the network equipment can configure the following when performing cross-RAT carrier aggregation for the UE:

(1), configure a common SDAP entity between carriers aggregated across RATs, and carriers aggregated by different RATs correspond to independent MAC entities. For example, the LTE carriers CC1 and CC2 in FIG. 7 correspond to the same MAC entity, and the other NR carriers CC3 and CC4 correspond to the same MAC entity.

(2), the network device configures the bearer configuration (PDCP, RLC) and MAC configuration under each RAT, and the corresponding carrier list.

(3) Similar to the foregoing embodiments, cross-carrier scheduling can only occur between two carriers of the same RAT.

The two differences between this solution and the foregoing embodiments are that the protocol stack of the RAT is relatively independent and relatively easy to implement. SDAP is originally NR version, and PDCP is also NR version. Because the same SDAP is used, it is not necessary to use different RATs according to the PDU session (session), and a new application scenario of cross-RAT carrier aggregation is provided.

FIG. 8 is a schematic flowchart of Embodiment 3 of the carrier aggregation configuration method provided by the present application. As shown in FIG. 8 , the carrier aggregation configuration method provided by this embodiment is mainly used for cross-site carrier aggregation configuration, and specifically includes: The following steps:

S301: Acquire configuration information for the UE, where the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes a carrier of a first network device and a carrier of a second network device.

In this solution, the first network device interacts with the core network, a second network device is connected to the Xn interface of the first network device, and the second network device can also provide resources for the UE. are carriers of the same RAT.

After the UE enters the connected state, it reports capability information to the first network device, where the capability information at least indicates whether the UE supports cross-site carrier aggregation, and the first network device configures the carrier aggregation based on the capability information and the network architecture.

If the UE supports carrier aggregation across sites, the first network device configures a carrier available to the UE to perform carrier aggregation.

In a specific implementation, the configuration information is also used for protocol stack configuration of the carriers in the carrier list.

S302: Send the configuration information to the UE.

The first network device sends the configuration information to the UE. During data transmission, the UE can map the data on the carriers of the first network device and the second network device for transmission according to the configuration on the network side to improve transmission efficiency.

In a specific implementation of this solution, the configuration information may further configure the hybrid automatic repeat request (Hybrid Automatic Repeat-reQuest, HARQ) numbers of the first network device and the second network device to be the same.

The configuration information is also used to configure downlink data transmission of the second network device to be fed back on the PUCCH of the second network device or fed back on the PUCCH of the first network device, which is not limited to this solution.

The carrier aggregation configuration method provided by the above embodiments provides a cross-site carrier aggregation solution. In the process of data transmission, data can be exchanged with the UE through carriers on two network devices, thereby effectively improving transmission efficiency.

On the basis of the foregoing embodiment, the first network device may perform scheduling configuration on the second network device. In specific implementation, the first network device may send TB data and/or the first network device to the second network device through the Xn interface. Scheduling information, where the first scheduling information is used by the second network device to send downlink data. For the second network device, the TB data and/or the first scheduling information sent by the first network device are received through the Xn interface, and in the subsequent data transmission process, the downlink data is sent based on the first scheduling information.

Optionally, the first network device may also send second scheduling information to the second network device through the Xn interface, where the second scheduling information is used for the second network device to receive uplink data. After receiving the second scheduling information, the second network device receives uplink data sent by the UE based on the second scheduling information.

In the above manner, the first network device can perform scheduling configuration on the uplink data and the downlink data on the second network device.

During the data transmission process, the first network device may receive TB data or HARQ feedback sent by the second network device through the Xn interface.

The configuration of the cross-site carrier aggregation provided by the present application will be described below by taking the first network device as the base station gNB1 and the second network device as the base station gNB2 as an example.

FIG. 9 is a schematic diagram of a protocol stack for cross-site carrier aggregation provided by the present application. As shown in FIG. 9 , gNB2 is connected to the interface of gNB1, and gNB1 and gNB2 share the same MAC entity. There is an ideal backhaul connection between gNB1 and gNB2. CC1 and CC2 belong to the same base station gNB1, and CC3 and CC4 belong to the base station gNB2. It is transparent to the UE that CC1, CC2, CC3 and CC4 belong to different base stations.

In a specific implementation, the base station (gNB1) to which the primary carrier (PCell) belongs is configured with the configuration of all bearer protocol stacks, namely SDAP configuration, PDCP, RLC configuration and MAC configuration.

In this solution, the HARQs of the two base stations are numbered uniformly. The base station (gNB1) where the primary carrier (PCell) is located is responsible for transferring TB data on the Xn interface, and/or scheduling information (ie, first scheduling information) to the base station (gNB2) providing resources for sending data.

In addition, the base station (gNB1) where the primary carrier is located is responsible for transmitting the scheduling information (ie the second scheduling information) on the Xn interface to the base station (gNB2) providing resources for receiving uplink data, and the resource base station (gNB2) is responsible for the received TB. The data is forwarded to the base station (gNB1) where the PCell is located.

The feedback of the downlink data sent by the base station (gNB1) where the primary carrier is configured to provide the resources (gNB2) can be fed back on the PUCCH on the base station providing the resources, or on the carrier of the base station where the PCell is located. Feedback on the PUCCH, this application Not limited.

In addition to the above data and scheduling information, some other information will be exchanged between the two base stations to facilitate scheduling, for example: channel measurement information, such as channel sounding reference signal (Sounding Reference Signal, SRS), power headroom report ( Power Headroom Report, PHR) report information, carrier management information of the main carrier, measurement report information of the Channel Status Indicator (CSI), sleep state information of the main carrier, and so on.

The configuration method for carrier aggregation provided in this embodiment can aggregate the network equipment of the main carrier of the same site and the carrier of the network equipment that provides resources, so as to further improve the transmission rate. Compared with other dual-connection solutions, this solution can use the resources of the two sites more flexibly.

In the technical solutions provided by the embodiments of the present application, the mechanisms of cross-RAT carrier aggregation and cross-site carrier aggregation are introduced, which provides the possibility to aggregate more carriers and provide a higher rate.

FIG. 10 is a schematic structural diagram of Embodiment 1 of a configuration apparatus for carrier aggregation provided by the present application. As shown in FIG. 10 , the configuration apparatus 10 for carrier aggregation includes:

A processing module 11, configured to acquire configuration information for the UE, where the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes carriers of at least two RATs;

The sending module 12 is configured to send the configuration information to the UE.

In the specific implementation of the configuration device 10 for carrier aggregation, the carriers of the at least two RATs share the same SDAP entity, and the carriers of the at least two RATs share the same MAC entity.

In a specific implementation of the configuration device 10 for carrier aggregation, the MAC entity has MAC layer functions of the at least two RATs.

Optionally, the MAC entity has a MAC layer function of any one of the at least two RATs, wherein the MAC entity is determined according to the RAT of the primary carrier.

Optionally, the configuration information is further used to configure a MAC adaptation layer located below the MAC entity, where the MAC adaptation layer is used to provide a MAC layer function of a carrier of a different RAT from the MAC entity.

Optionally, the carriers of the at least two RATs share the same SDAP entity, the carriers of the same RAT share the same MAC entity, and the corresponding MAC entities of the carriers of each RAT are different.

Optionally, cross-carrier scheduling may be performed between carriers of the same RAT in the carrier list.

Optionally, the PDSCH transmission of the carrier of the same RAT in the carrier list is fed back through the PDSCH of the RAT carrier.

Optionally, the same RAT carrier in the carrier list includes at least one carrier used for PUCCH transmission.

Optionally, the carriers of different RATs in the carrier list are respectively configured with DRX timers, and the DRX timers are used to monitor the physical downlink control channel PDCCH on the carriers of the corresponding RATs.

Optionally, the carrier list includes LTE carriers and NR carriers.

Optionally, the configuration information is also used to configure the PDCP entity to have the function of the PDCP layer of the NR carrier, and the configuration information is also used to configure the RLC entity to support the LTE technology or support the NR technology.

On the basis of any of the foregoing embodiments, the configuration apparatus 10 for carrier aggregation further includes:

The receiving module 13 is configured to receive capability information reported by the UE, where the capability information is used to indicate whether the UE supports cross-RAT carrier aggregation.

Optionally, the capability information is further used to indicate a supported carrier aggregation type, where the carrier aggregation type includes: a common MAC entity or an independent MAC entity.

Optionally, the receiving module 13 is further configured to receive a frequency point measurement result corresponding to each RAT reported by the UE;

The processing module 11 is further configured to determine whether to configure cross-RAT carrier aggregation according to the frequency point measurement result corresponding to each RAT and the capability information.

The configuration apparatus for carrier aggregation provided in any of the above embodiments is used to implement the technical solution on the network device side in the cross-RAT carrier aggregation solution in the foregoing method embodiments, and its implementation principles and technical effects are similar, and will not be repeated here.

FIG. 11 is a schematic structural diagram of Embodiment 2 of a configuration apparatus for carrier aggregation provided by the present application. As shown in FIG. 11 , the configuration apparatus 20 for carrier aggregation provided in this embodiment includes:

The receiving module 21 is configured to receive configuration information sent by a network device, where the configuration information can be a carrier list for carrier aggregation, and the carrier list includes carriers of at least two RATs.

In a specific implementation manner, the carriers of the at least two RATs share the same SDAP entity, and the carriers of the at least two RATs share the same MAC entity.

Optionally, the MAC entity has MAC layer functions of the at least two RATs.

Optionally, the physical downlink shared channel transmission of the carriers of the same RAT in the carrier list is fed back through the physical uplink control channel PUCCH of the RAT carrier.

Optionally, the same RAT carrier in the carrier list includes at least one carrier used for physical uplink control channel PUCCH transmission.

Optionally, the carriers of different RATs in the carrier list are respectively configured with DRX timers, and the DRX timers are used to monitor the PDCCH on the carriers of the corresponding RATs.

Optionally, the carrier list includes LTE carriers and NR carriers.

On the basis of any of the foregoing embodiments, the configuration apparatus 20 for carrier aggregation further includes:

The sending module 22 is configured to report capability information to the network device, where the capability information is used to indicate whether the UE supports cross-RAT carrier aggregation.

Optionally, the configuration apparatus 20 for carrier aggregation further includes:

a processing module 23, configured to measure the frequency points of different RATs according to the configuration of the network device, and obtain a frequency point measurement result;

The sending module 22 is further configured to report the frequency point measurement result corresponding to each RAT to the network device.

The configuration device for carrier aggregation provided by any of the above embodiments is used to implement the technical solution on the UE side in the cross-RAT carrier aggregation solution in the foregoing method embodiments, and its implementation principle and technical effect are similar, and are not repeated here.

FIG. 12 is a schematic structural diagram of Embodiment 3 of a configuration apparatus for carrier aggregation provided by the present application. As shown in FIG. 12 , a second network device is connected to the Xn interface of the configuration apparatus 30 for carrier aggregation provided in this embodiment. The configuration device 30 includes:

a processing module 31, configured to acquire configuration information for the UE, where the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes a carrier of the first network device and a carrier of the second network device;

A sending module 32, configured to send the configuration information to the UE.

Optionally, the configuration information is also used for protocol stack configuration of the carriers in the carrier list.

Optionally, the configuration device for carrier aggregation and the HARQ number of the second network device are the same.

Optionally, the sending module 32 is also used for:

Send TB data and/or first scheduling information to the second network device through the Xn interface, where the first scheduling information is used for the second network device to send downlink data.

Optionally, the sending module 32 is also used for:

Send second scheduling information to the second network device through the Xn interface, where the second scheduling information is used for the second network device to receive uplink data.

On the basis of any of the foregoing embodiments, the configuration device 30 for carrier aggregation further includes:

The first receiving module 33 is configured to receive TB data or HARQ feedback sent by the second network device through the Xn interface.

Optionally, the configuration information is further used to configure downlink data transmission of the second network device to be fed back on the PUCCH of the second network device or fed back on the PUCCH of the carrier aggregation configuration apparatus 30 .

The second receiving module 34 is configured to receive capability information reported by the UE, where the capability information is used to indicate whether the UE supports cross-site carrier aggregation.

The configuration device for carrier aggregation provided by any of the above embodiments is used to implement the technical solution on the first network device side in the cross-site carrier aggregation solution in the foregoing method embodiment. The implementation principle and technical effect are similar, and are not repeated here. Repeat.

FIG. 13 is a schematic structural diagram of Embodiment 4 of a configuration device for carrier aggregation provided by the present application. As shown in FIG. 13 , the configuration device 40 for carrier aggregation includes:

A receiving module 41, configured to receive configuration information sent by a first network device, where the configuration information includes a list of carriers that can perform carrier aggregation, and the carrier list includes a carrier of the first network device and a carrier of the second network device , the second network device is connected to the Xn interface of the first network device, and provides resources for the configuration apparatus 40 for carrier aggregation.

Optionally, the HARQ numbers of the first network device and the second network device are the same.

Optionally, the configuration information is further used to configure downlink data transmission of the second network device to be fed back on the physical uplink control channel PUCCH of the second network device or fed back on the PUCCH of the first network device.

On the basis of any of the foregoing embodiments, the configuration device 40 for carrier aggregation further includes:

The sending module 42 is configured to report capability information to the first network device, where the capability information is used to indicate whether the carrier aggregation configuration apparatus supports cross-site carrier aggregation.

The configuration device for carrier aggregation provided in any of the above embodiments is used to implement the technical solution on the UE side in the cross-site carrier aggregation solution in the foregoing method embodiment, and its implementation principle and technical effect are similar, and are not repeated here.

FIG. 14 is a schematic structural diagram of an embodiment of a transmission device provided by this application. As shown in FIG. 14 , the transmission device 50 is connected to the Xn interface of the first network device. The transmission device 50 includes:

The receiving module 51 is configured to receive, through the Xn interface, TB data and/or first scheduling information sent by the first network device, where the first scheduling information is used by the transmission apparatus to send downlink data.

Optionally, the receiving module 51 is also used for:

The second scheduling information sent by the first network device is received through the Xn interface, where the second scheduling information is used for the transmission apparatus 50 to receive uplink data.

In a specific embodiment of the device, the transmission device further includes:

The sending module 52 is configured to send TB data or HARQ feedback to the first network device through the Xn interface.

The transmission apparatus provided in any of the foregoing embodiments is used to execute the technical solutions on the second network device side in the foregoing method embodiments, and the implementation principles and technical effects thereof are similar, and are not repeated here.

FIG. 15 is a schematic structural diagram of a first embodiment of a network device provided by this application. As shown in FIG. 15 , the network device 100 includes:

a processor 111, a memory 112, an interface 113 for communicating with user equipment;

The memory 112 stores computer-executed instructions;

The processor 111 executes the computer-executable instructions stored in the memory 112, so that the processor 111 executes the solution on the network device side in the aforementioned cross-RAT carrier aggregation configuration method, or performs the aforementioned cross-site carrier aggregation. The solution on the first network device side in the configuration method.

FIG. 16 is a schematic structural diagram of an embodiment of a user equipment provided by this application. As shown in FIG. 16 , the user equipment 200 includes:

a processor 211, a memory 212, an interface 213 for communicating with a network device;

The memory 212 stores computer-executed instructions;

The processor 211 executes the computer-executed instructions stored in the memory, so that the processor executes the technical solutions on the UE side in any of the foregoing method embodiments.

FIG. 17 is a schematic structural diagram of the second embodiment of a network device provided by this application. As shown in FIG. 17 , the network device 100 includes:

a processor 311, a memory 312, an interface 313 for communicating with other network devices or user equipment;

The memory 312 stores computer-executable instructions;

The processor 311 executes the computer-executed instructions stored in the memory, so that the processor executes the technical solution on the second network device side in the cross-site carrier aggregation in the foregoing method embodiment.

In a specific implementation of the above-mentioned network device or user equipment, the memory, the processor, and the interface may be connected through a bus, or may be connected in other ways. Optionally, the memory can be integrated inside the processor.

Embodiments of the present application further provide a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, are used to implement the cross-RAT carrier wave of the foregoing method embodiments The network device solution in the aggregation configuration method or the first network device solution in the cross-site carrier aggregation configuration method in the foregoing method embodiments.

Embodiments of the present application further provide a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, are used to implement the UE in any of the foregoing method embodiments side technical solutions.

Embodiments of the present application further provide a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, are used to implement cross-site carrier aggregation in the foregoing solution The technical solution on the second network device side in the above.

An embodiment of the present application further provides a chip, including: a processing module and a communication interface, where the processing module is configured to perform the solution on the network device side in the aforementioned cross-RAT carrier aggregation configuration method or the aforementioned cross-site carrier aggregation configuration method The technical solution on the side of the first network device in the above.

An embodiment of the present application further provides a chip, including: a processing module and a communication interface, where the processing module is configured to perform the technical solution on the second network device side in the foregoing cross-site carrier aggregation solution.

Further, any of the above-mentioned chips also includes a storage module (such as a memory), the storage module is used for storing instructions, the processing module is used for executing the instructions stored in the storage module, and the execution of the instructions stored in the storage module causes the processing module to execute the aforementioned instructions. A technical solution on the network device side in any method embodiment.

An embodiment of the present application further provides a chip, including: a processing module and a communication interface, where the processing module is configured to execute the technical solution on the UE side in any of the foregoing embodiments.

Further, the chip also includes a storage module (eg, memory), the storage module is used for storing instructions, the processing module is used for executing the instructions stored in the storage module, and the execution of the instructions stored in the storage module causes the processing module to execute any of the foregoing. The technical solution on the UE side in the method embodiment.

The embodiments of the present application further provide a program, which, when the program is executed by a processor, is used to implement the solution of any network device in any of the foregoing method embodiments.

The embodiments of the present application further provide a program, which is used to implement the UE-side solution in any of the foregoing method embodiments when the program is executed by the processor. Optionally, the above-mentioned processor may be a chip.

Embodiments of the present application further provide a computer program product, including program instructions, where the program instructions are used to implement any network device-side solution in any of the foregoing method embodiments.

Embodiments of the present application further provide a computer program product, including program instructions, where the program instructions are used to implement the UE-side solution in any of the foregoing method embodiments.

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

In the specific implementation of any of the above devices, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, referred to as: CPU), or other general-purpose processors, digital signal processors (English: Digital Signal Processors) , referred to as: DSP), application specific integrated circuit (English: Application Specific Integrated Circuit, referred to as: ASIC) and so on. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps in combination with the method disclosed in the present application can be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

All or part of the steps for implementing the above method embodiments may be completed by program instructions related to hardware. The aforementioned program can be stored in a readable memory. When the program is executed, the steps including the above method embodiments are executed; and the aforementioned memory (storage medium) includes: read-only memory (English: read-only memory, abbreviated as: ROM), RAM, flash memory, hard disk, Solid state drive, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), optical disc (English: optical disc) and any combination thereof.

Claims

A configuration method for carrier aggregation, characterized in that it is applied to network equipment, the method comprising:

acquiring configuration information for the user equipment UE, the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes carriers of at least two radio access technologies (RATs);

sending the configuration information to the UE.
The method according to claim 1, wherein the carriers of the at least two RATs share the same service data adaptation protocol (SDAP) entity, and the carriers of the at least two RATs share the same medium access control (MAC) entity.
The method according to claim 2, wherein the MAC entity has MAC layer functions of the at least two RATs.
The method according to claim 2, wherein the MAC entity has a MAC layer function of any one of the at least two RATs, wherein the MAC entity is determined according to the RAT of the primary carrier.
The method according to claim 4, wherein the configuration information is further used to configure a MAC adaptation layer located under the MAC entity, and the MAC adaptation layer is used to provide a different RAT from the MAC entity The MAC layer function of the carrier.
The method according to claim 1, wherein the carriers of the at least two RATs share the same SDAP entity, the carriers of the same RAT share the same MAC entity, and the carriers of each RAT correspond to different MAC entities.
The method according to any one of claims 1 to 6, wherein cross-carrier scheduling can be performed between carriers of the same RAT in the carrier list.
The method according to any one of claims 1 to 7, wherein the physical downlink shared channel PDSCH transmission of the carriers of the same RAT in the carrier list is fed back through the physical uplink control channel PUCCH of the RAT carrier.
The method according to claim 8, wherein the same RAT carrier in the carrier list includes at least one carrier used for physical uplink control channel PUCCH transmission.
The method according to any one of claims 1 to 9, wherein the carriers of different RATs in the carrier list are respectively configured with discontinuous reception DRX timers, and the DRX timers are used to monitor the carriers of the corresponding RATs. The physical downlink control channel PDCCH.
The method according to any one of claims 1 to 10, wherein the carrier list includes Long Term Evolution LTE carriers and New Radio NR carriers.
The method according to claim 11, wherein the configuration information is further used to configure the Packet Data Convergence Protocol (PDCP) entity to have the function of the PDCP layer of the NR carrier, and the configuration information is further used to configure the RLC entity to support the LTE technology or Support NR technology.
The method according to any one of claims 1 to 12, wherein the method further comprises:

Receive capability information reported by the UE, where the capability information is used to indicate whether the UE supports cross-RAT carrier aggregation.
The method according to claim 13, wherein the capability information is further used to indicate a supported type of carrier aggregation, and the type of carrier aggregation includes: a common MAC entity or an independent MAC entity.
The method according to claim 13 or 14, wherein the method further comprises:

receiving a frequency point measurement result corresponding to each RAT reported by the UE;

Whether to configure cross-RAT carrier aggregation is determined according to the frequency point measurement result corresponding to each RAT and the capability information.
A configuration method for carrier aggregation, characterized in that it is applied to a user equipment UE, and the method includes:

The configuration information sent by the network device is received, where the configuration information may be a carrier list for carrier aggregation, and the carrier list includes carriers of at least two radio access technologies (RATs).
The method according to claim 16, wherein the carriers of the at least two RATs share the same service data adaptation protocol (SDAP) entity, and the carriers of the at least two RATs share the same medium access control (MAC) entity.
The method of claim 17, wherein the MAC entity has MAC layer functions of the at least two RATs.
The method according to claim 17, wherein the MAC entity has a MAC layer function of any one of the at least two RATs, wherein the MAC entity is determined according to the RAT of the primary carrier.
The method according to claim 19, wherein the configuration information is further used to configure a MAC adaptation layer located under the MAC entity, and the MAC adaptation layer is used to provide a different RAT from the MAC entity The MAC layer function of the carrier.
The method according to claim 16, wherein the carriers of the at least two RATs share the same SDAP entity, the carriers of the same RAT share the same MAC entity, and the corresponding MAC entities of the carriers of each RAT are different.
The method according to any one of claims 16 to 21, wherein cross-carrier scheduling can be performed between carriers of the same RAT in the carrier list.
The method according to any one of claims 16 to 22, wherein the physical downlink shared channel transmission of the carriers of the same RAT in the carrier list is fed back through the physical uplink control channel PUCCH of the RAT carrier.
The method according to claim 23, wherein the same RAT carrier in the carrier list includes at least one carrier used for physical uplink control channel PUCCH transmission.
The method according to any one of claims 16 to 24, wherein the carriers of different RATs in the carrier list are respectively configured with discontinuous reception DRX timers, and the DRX timers are used to monitor the signals on the carriers of the corresponding RATs. Physical downlink control channel PDCCH.
The method according to any one of claims 16 to 25, wherein the carrier list includes Long Term Evolution LTE carriers and New Radio NR carriers.
The method according to claim 26, wherein the configuration information is further used to configure the Packet Data Convergence Protocol (PDCP) entity to have the function of the PDCP layer of the NR carrier, and the configuration information is further used to configure the RLC entity to support LTE technology or Support NR technology.
The method according to any one of claims 16 to 27, wherein the method further comprises:

reporting capability information to the network device, where the capability information is used to indicate whether the UE supports cross-RAT carrier aggregation.
The method according to claim 28, wherein the capability information is further used to indicate a supported type of carrier aggregation, and the type of carrier aggregation includes: a common MAC entity or an independent MAC entity.
The method according to claim 28 or 29, wherein the method further comprises:

Measure the frequency points of different RATs according to the configuration of the network equipment to obtain frequency point measurement results;

The frequency point measurement result corresponding to each RAT is reported to the network device.
A configuration method for carrier aggregation, characterized in that it is applied to a first network device, and an Xn interface of the first network device is connected to a second network device, and the method includes:

Acquire configuration information for the user equipment UE, the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes a carrier of the first network device and a carrier of the second network device;

sending the configuration information to the UE.
The method according to claim 31, wherein the configuration information is further used for protocol stack configuration of the carriers in the carrier list.
The method according to claim 31 or 32, wherein the HARQ numbers of the HARQ of the first network device and the second network device are the same.
The method according to claims 31 to 33, wherein the method further comprises:

Send TB data and/or first scheduling information to the second network device through the Xn interface, where the first scheduling information is used for the second network device to send downlink data.
The method according to any one of claims 31 to 34, wherein the method further comprises:

Send second scheduling information to the second network device through the Xn interface, where the second scheduling information is used for the second network device to receive uplink data.
The method of claim 35, wherein the method further comprises:

Receive TB data or HARQ feedback sent by the second network device through the Xn interface.
The method according to any one of claims 31 to 36, wherein the configuration information is further used to configure downlink data transmission of the second network device on a physical uplink control channel PUCCH of the second network device feedback or feedback on the PUCCH of the first network device.
The method according to any one of claims 31 to 37, wherein the method further comprises:

Receive capability information reported by the UE, where the capability information is used to indicate whether the UE supports cross-site carrier aggregation.
A configuration method for carrier aggregation, characterized in that it is applied to a user equipment UE, and the method includes:

Receive configuration information sent by a first network device, where the configuration information includes a list of carriers that can perform carrier aggregation, and the carrier list includes a carrier of the first network device and a carrier of a second network device, and the second network The device is connected to the Xn interface of the first network device, and provides resources for the UE.
The method according to claim 39, wherein the configuration information is further used for protocol stack configuration of the carriers in the carrier list.
The method according to claim 39 or 40, wherein the HARQ numbers of the HARQ of the first network device and the second network device are the same.
The method according to any one of claims 39 to 41, wherein the configuration information is further used to configure downlink data transmission of the second network device on a physical uplink control channel PUCCH of the second network device feedback or feedback on the PUCCH of the first network device.
The method according to any one of claims 39 to 42, wherein the method further comprises:

reporting capability information to the first network device, where the capability information is used to indicate whether the UE supports cross-site carrier aggregation.
A transmission method, characterized by being applied to a second network device, the second network device being connected to an Xn interface of the first network device, the method comprising:

Receive TB data and/or first scheduling information sent by the first network device through the Xn interface, where the first scheduling information is used for the second network device to send downlink data.
The method of claim 44, wherein the method further comprises:

The second scheduling information sent by the first network device is received through the Xn interface, where the second scheduling information is used for the second network device to receive uplink data.
The method of claim 45, wherein the method further comprises:

Send TB data or HARQ feedback to the first network device through the Xn interface.
A configuration device for carrier aggregation, comprising:

a processing module, configured to acquire configuration information for the user equipment UE, where the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes carriers of at least two radio access technologies (RATs);

A sending module, configured to send the configuration information to the UE.
The apparatus according to claim 47, wherein the carriers of the at least two RATs share the same service data adaptation protocol (SDAP) entity, and the carriers of the at least two RATs share the same medium access control (MAC) entity.
The apparatus of claim 48, wherein the MAC entity has MAC layer functions of the at least two RATs.
The apparatus of claim 48, wherein the MAC entity has a MAC layer function of any one of the at least two RATs, wherein the MAC entity is determined according to the RAT of the primary carrier.
The apparatus according to claim 50, wherein the configuration information is further used to configure a MAC adaptation layer located under the MAC entity, and the MAC adaptation layer is used to provide a different RAT from the MAC entity The MAC layer function of the carrier.
The apparatus according to claim 47, wherein the carriers of the at least two RATs share the same SDAP entity, the carriers of the same RAT share the same MAC entity, and the corresponding MAC entities of the carriers of each RAT are different.
The apparatus according to any one of claims 47 to 52, wherein cross-carrier scheduling can be performed between carriers of the same RAT in the carrier list.
The apparatus according to any one of claims 47 to 53, wherein the physical downlink shared channel PDSCH transmission of the carriers of the same RAT in the carrier list is fed back through the physical uplink control channel PUCCH of the RAT carrier.
The apparatus according to claim 54, wherein the same RAT carrier in the carrier list includes at least one carrier used for physical uplink control channel PUCCH transmission.
The apparatus according to any one of claims 47 to 55, wherein carriers of different RATs in the carrier list are respectively configured with discontinuous reception DRX timers, and the DRX timers are used to monitor the carriers of the corresponding RATs. The physical downlink control channel PDCCH.
The apparatus according to any one of claims 47 to 56, wherein the carrier list includes Long Term Evolution LTE carriers and New Radio NR carriers.
The apparatus according to claim 57, wherein the configuration information is further used to configure the Packet Data Convergence Protocol (PDCP) entity to have the function of the PDCP layer of the NR carrier, and the configuration information is further used to configure the RLC entity to support LTE technology or Support NR technology.
The device according to any one of claims 47 to 58, wherein the device further comprises:

A receiving module, configured to receive capability information reported by the UE, where the capability information is used to indicate whether the UE supports cross-RAT carrier aggregation.
The apparatus according to claim 59, wherein the capability information is further used to indicate a supported type of carrier aggregation, and the type of carrier aggregation includes: a common MAC entity or an independent MAC entity.
The device according to claim 59 or 60, characterized in that,

The receiving module is further configured to receive a frequency point measurement result corresponding to each RAT reported by the UE;

The processing module is further configured to determine whether to configure cross-RAT carrier aggregation according to the frequency point measurement result corresponding to each RAT and the capability information.
A configuration device for carrier aggregation, comprising:

A receiving module, configured to receive configuration information sent by a network device, where the configuration information can perform carrier aggregation, and the carrier list includes carriers of at least two radio access technologies (RATs).
The apparatus according to claim 62, wherein the carriers of the at least two RATs share the same service data adaptation protocol (SDAP) entity, and the carriers of the at least two RATs share the same medium access control (MAC) entity.
The apparatus of claim 63, wherein the MAC entity has MAC layer functions of the at least two RATs.
The apparatus of claim 63, wherein the MAC entity has a MAC layer function of any one of the at least two RATs, wherein the MAC entity is determined according to the RAT of the primary carrier.
The apparatus according to claim 65, wherein the configuration information is further used to configure a MAC adaptation layer located under the MAC entity, and the MAC adaptation layer is used to provide a different RAT from the MAC entity The MAC layer function of the carrier.
The apparatus according to claim 62, wherein the carriers of the at least two RATs share the same SDAP entity, the carriers of the same RAT share the same MAC entity, and the corresponding MAC entities of the carriers of each RAT are different.
The apparatus according to any one of claims 62 to 67, wherein cross-carrier scheduling can be performed between carriers of the same RAT in the carrier list.
The apparatus according to any one of claims 62 to 68, wherein the physical downlink shared channel transmission of the carriers of the same RAT in the carrier list is fed back through the physical uplink control channel PUCCH of the RAT carrier.
The apparatus according to claim 69, wherein the same RAT carrier in the carrier list includes at least one carrier used for physical uplink control channel PUCCH transmission.
The apparatus according to any one of claims 62 to 70, wherein carriers of different RATs in the carrier list are respectively configured with discontinuous reception DRX timers, and the DRX timers are used to monitor the signals on the carriers of the corresponding RATs. Physical downlink control channel PDCCH.
The apparatus according to any one of claims 62 to 71, wherein the carrier list includes a Long Term Evolution LTE carrier and a new wireless NR carrier.
The apparatus according to claim 72, wherein the configuration information is further used to configure the Packet Data Convergence Protocol (PDCP) entity to have the function of the PDCP layer of the NR carrier, and the configuration information is further used to configure the RLC entity to support the LTE technology or Support NR technology.
The device according to any one of claims 62 to 73, wherein the device further comprises:

A sending module, configured to report capability information to the network device, where the capability information is used to indicate whether the carrier aggregation configuration apparatus supports cross-RAT carrier aggregation.
The apparatus according to claim 74, wherein the capability information is further used to indicate a type of carrier aggregation supported, and the type of carrier aggregation includes: a common MAC entity or an independent MAC entity.
The apparatus of claim 74 or 75, wherein the apparatus further comprises:

a processing module, configured to measure the frequency points of different RATs according to the configuration of the network device, and obtain a frequency point measurement result;

The sending module is further configured to report the frequency point measurement result corresponding to each RAT to the network device.
A configuration device for carrier aggregation, characterized in that a second network device is connected to an Xn interface of the configuration device for carrier aggregation, and the device includes:

A processing module, configured to acquire configuration information for the user equipment UE, the configuration information includes a list of carriers that can perform carrier aggregation, and the carrier list includes the carriers of the configuration device for carrier aggregation and the information of the second network device. carrier;

A sending module, configured to send the configuration information to the UE.
The apparatus according to claim 77, wherein the configuration information is further used for protocol stack configuration of the carriers in the carrier list.
The apparatus according to claim 77 or 78, wherein the configuration apparatus for carrier aggregation and the HARQ number of the HARQ of the second network device are the same.
The device according to claims 77 to 79, wherein the sending module is further configured to:

Send TB data and/or first scheduling information to the second network device through the Xn interface, where the first scheduling information is used for the second network device to send downlink data.
The device according to any one of claims 77 to 80, wherein the sending module is further configured to:

Send second scheduling information to the second network device through the Xn interface, where the second scheduling information is used for the second network device to receive uplink data.
The apparatus of claim 81, wherein the apparatus further comprises:

A first receiving module, configured to receive TB data or HARQ feedback sent by the second network device through the Xn interface.
The apparatus according to any one of claims 77 to 82, wherein the configuration information is further used to configure downlink data transmission of the second network device on a physical uplink control channel PUCCH of the second network device Feedback or feedback on the PUCCH of the carrier aggregation configuration device.
The device according to any one of claims 77 to 83, wherein the device further comprises:

The second receiving module is configured to receive capability information reported by the UE, where the capability information is used to indicate whether the UE supports cross-site carrier aggregation.
A configuration device for carrier aggregation, comprising:

a receiving module, configured to receive configuration information sent by a first network device, where the configuration information includes a list of carriers that can perform carrier aggregation, and the list of carriers includes a carrier of the first network device and a carrier of the second network device, The second network device is connected to the Xn interface of the first network device, and provides resources for the configuration apparatus for carrier aggregation.
The apparatus according to claim 85, wherein the configuration information is further used for protocol stack configuration of the carriers in the carrier list.
The apparatus according to claim 85 or 86, wherein the HARQ numbers of the HARQ of the first network device and the second network device are the same.
The apparatus according to any one of claims 85 to 87, wherein the configuration information is further used to configure downlink data transmission of the second network device on a physical uplink control channel PUCCH of the second network device feedback or feedback on the PUCCH of the first network device.
The device according to any one of claims 85 to 88, wherein the device further comprises:

A sending module, configured to report capability information to the first network device, where the capability information is used to indicate whether the carrier aggregation configuration apparatus supports cross-site carrier aggregation.
A transmission device, characterized in that the transmission device is connected to an Xn interface of a first network device, and the device comprises:

A receiving module, configured to receive TB data and/or first scheduling information sent by the first network device through the Xn interface, where the first scheduling information is used for the configuration apparatus for carrier aggregation to send downlink data.
The apparatus according to claim 90, wherein the receiving module is further configured to:

The second scheduling information sent by the first network device is received through the Xn interface, where the second scheduling information is used by the carrier aggregation configuration apparatus to receive uplink data.
The apparatus of claim 91, wherein the apparatus further comprises:

A sending module, configured to send TB data or HARQ feedback to the first network device through the Xn interface.
A network device, characterized in that it includes:

processors, memories, interfaces for communicating with user equipment;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the configuration method for carrier aggregation according to any one of claims 1 to 15.
A user equipment, characterized in that it includes:

processors, memories, interfaces for communicating with network devices;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the configuration method for carrier aggregation according to any one of claims 16 to 30.
A network device, characterized in that it includes:

processors, memories, interfaces for communicating with other network equipment or user equipment;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the configuration method for carrier aggregation according to any one of claims 31 to 38.
A user equipment, characterized in that it includes:

processors, memories, interfaces for communicating with network devices;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the configuration method for carrier aggregation as claimed in any one of claims 39 to 43.
A network device, characterized in that it includes:

processors, memories, interfaces for communicating with other network equipment or user equipment;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, causing the processor to perform the transmission method of any one of claims 44 to 46.
A computer-readable storage medium, characterized in that, computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, are used to implement claims 1 to 15, or 31 to 31 The configuration method for carrier aggregation described in any one of 38.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement claims 16 to 30, or 39 to 39. The configuration method for carrier aggregation described in any one of 43.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, is used to implement the invention as claimed in any one of claims 43 to 46. the transmission method described.
A chip, characterized by comprising: a processing module and a communication interface, the processing module being configured to execute the carrier aggregation configuration method according to any one of claims 1 to 15 or 31 to 38.
A chip, characterized by comprising: a processing module and a communication interface, the processing module is configured to execute the carrier aggregation configuration method according to any one of claims 16 to 30 or 39 to 43 .
A chip, characterized by comprising: a processing module and a communication interface, wherein the processing module is configured to execute the transmission method according to any one of claims 43 to 46 .