CN115699866A

CN115699866A - Carrier aggregation configuration method, device, equipment and storage medium

Info

Publication number: CN115699866A
Application number: CN202080101625.0A
Authority: CN
Inventors: 王淑坤; 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-16
Filing date: 2020-07-16
Publication date: 2023-02-03
Also published as: WO2022011625A1

Abstract

The application provides a carrier aggregation configuration method, a device, equipment and a storage medium, in a specific scheme, carrier aggregation of carriers of different RATs can be realized by sharing an MAC entity, and a cross-site carrier aggregation configuration scheme is also provided.

Description

Carrier aggregation configuration method, device, equipment and storage medium

Technical Field

The present disclosure relates to communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for configuring carrier aggregation.

Background

Currently, with the pursuit of speed, delay, high speed mobility, energy efficiency and the diversity and complexity of services in future life, the international standard organization of the third Generation Partnership project (3 rd Generation Partnership project,3 gpp) has begun to develop a fifth Generation mobile communication technology (5 g), also called New Radio (NR) technology, for this purpose. The main application scenarios of 5G are: enhanced Mobile Ultra wide band (eMBB), low-Latency high-reliability Communication (URLLC), and massive Machine Type Communication (mMTC).

In early NR deployment, complete NR coverage is difficult to obtain, so typical network coverage is wide area Long Term Evolution (LTE) coverage and an island coverage mode of NR. Moreover, a large amount of LTE is deployed below 6GHz, and the spectrum below 6GHz available for 5G is rare. NR must therefore be studied for spectrum applications above 6GHz, with limited high band coverage and fast signal fading. Meanwhile, in order to protect the early LTE investment of a mobile operator, a light interworking working mode between LTE and NR is provided. In order to enable 5G network deployment and commercial applications as soon as possible, the first 5G release that 3GPP is completing, i.e. E-UTRA and NR Dual Connectivity (LTE-NR Dual Connectivity, EN-DC). Here, LTE serves as a Master Node (MN) and NR serves as a Secondary Node (SN). Fig. 1 is a schematic diagram of a network deployment and networking architecture provided in the prior art, as shown in fig. 1, wherein a main Radio Resource Control (RRC) Control function of an MN node and a Control plane leading to a CN, and an SN node may configure auxiliary signaling and mainly provide a data transmission function. Under the structure, in order to meet the transmission requirements under the various application scenes, the transmission rate can be increased through carrier aggregation. Currently, the transmission rate can be increased by performing carrier aggregation between co-sited carriers and carriers of the same Radio Access Technology (RAT).

However, in the prior art, only carrier aggregation between co-sited co-RAT carriers is supported, and cross-sited or cross-RAT carrier aggregation cannot be supported.

Disclosure of Invention

The embodiment of the application provides a carrier aggregation configuration method, a carrier aggregation configuration device, carrier aggregation equipment and a storage medium, provides carrier aggregation of an NR carrier and an LTE carrier, and a cross-site carrier aggregation mechanism, and can further improve the transmission rate.

In a first aspect, an embodiment of the present application may provide a method for configuring carrier aggregation, where the method is applied to a network device, and the method includes:

acquiring configuration information of UE, wherein the configuration information comprises a carrier list capable of carrying out carrier aggregation, and the carrier list comprises carriers of at least two RAT (radio access technology);

and sending the configuration information to the UE.

In a second aspect, an embodiment of the present application may provide a method for configuring carrier aggregation, where the method is applied to a user equipment UE, and the method includes:

receiving configuration information sent by a network device, wherein the configuration information can be a carrier list for carrier aggregation, and the carrier list comprises carriers of at least two RATs.

In a third aspect, an embodiment of the present application may provide a carrier aggregation configuration method, 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:

acquiring configuration information of User Equipment (UE), wherein the configuration information comprises a carrier list capable of carrying out carrier aggregation, and the carrier list comprises a carrier of the first network equipment and a carrier of the second network equipment;

and sending the configuration information to the UE.

In a fourth aspect, an embodiment of the present application may provide a method for configuring carrier aggregation, where the method is applied to a user equipment UE, and the method includes:

receiving configuration information sent by a first network device, where the configuration information includes a carrier list capable of performing carrier aggregation, the carrier list includes a carrier of the first network device and a carrier of a second network device, and the second network device is connected to an Xn interface of the first network device and provides resources for the UE.

In a fifth aspect, an embodiment 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 a first network device, and the method includes:

and receiving TB data and/or first scheduling information sent by the first network equipment through the Xn interface, wherein the first scheduling information is used for sending downlink data by the second network equipment.

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

a processing module, configured to obtain configuration information for a UE, where the configuration information includes a carrier list capable of performing carrier aggregation, and the carrier list 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 a carrier aggregation configuration apparatus, including:

a receiving module, configured to receive configuration information sent by a network device, where the configuration information may be a carrier list for performing 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 a carrier aggregation configuration apparatus, where a second network device is connected to an Xn interface of the carrier aggregation configuration apparatus, and the apparatus includes:

a processing module, configured to acquire configuration information for a UE, where the configuration information includes a carrier list capable of performing carrier aggregation, and the carrier list includes carriers of a configuration device for carrier aggregation and 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 carrier aggregation configuration apparatus, including:

a receiving module, configured to receive configuration information sent by a first network device, where the configuration information includes a carrier list capable of performing carrier aggregation, the carrier list includes a carrier of the first network device and a carrier of a second network device, and the second network device is connected to an Xn interface of the first network device and provides a resource for a configuration apparatus for carrier aggregation.

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, the apparatus includes:

a receiving module, 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 for the transmission apparatus to send downlink data.

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

a processor, a memory, an interface to communicate with a user device;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored by the memory to cause the processor to perform the method of configuring carrier aggregation of the first aspect.

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

a processor, a memory, an interface to communicate with a network device;

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 of carrier aggregation according to the second aspect.

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

a processor, memory, an interface to communicate with other network devices or user devices;

the memory stores computer execution instructions;

the processor executes the computer-executable instructions stored in the memory, so that the processor executes the configuration method of carrier aggregation according to the third aspect.

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

a processor, a memory, an interface to communicate with a network device;

the memory stores computer-executable instructions;

the processor executes the computer-executable instructions stored by the memory, so that the processor executes the configuration method of carrier aggregation according to the fourth aspect.

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

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored by the memory, causing the processor to perform the transmission method of the fifth aspect.

In a sixteenth aspect, embodiments of the present application may provide a computer-readable storage medium, having stored therein computer-executable instructions for implementing a carrier aggregation configuration method as described in the first aspect or the third aspect when the computer-executable instructions are executed by a processor.

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

In an eighteenth aspect, embodiments of the present application may provide a computer-readable storage medium having stored therein computer-executable instructions for implementing the transmission method according to the fifth aspect when the computer-executable instructions are executed by a processor.

In a nineteenth aspect, embodiments of the present application may provide a chip, including: a processing module and a communication interface, the processing module being configured to perform the configuration method for carrier aggregation according to the first aspect or the third aspect.

In a twentieth aspect, embodiments of the present application may provide a chip, including: a processing module and a communication interface, the processing module is configured to execute the configuration method of carrier aggregation according to the second aspect or the fourth aspect.

In a twenty-first aspect, embodiments of the present application may provide a chip, including: a processing module and a communication interface, the processing module being configured to execute the transmission method according to the fifth aspect.

According to the carrier aggregation configuration method, device, equipment and storage medium provided by the embodiment of the application, carrier aggregation of carriers of different RATs can be realized through a common MAC entity in the technical scheme provided by the embodiment of the application, a cross-site carrier aggregation configuration scheme is also provided, and in the configuration process of carrier aggregation of network equipment, according to whether the UE supports cross-RAT carrier aggregation or cross-site carrier aggregation for transmission and configuration of a protocol stack, the aggregation bandwidth is further increased, and the transmission rate is increased.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.

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

fig. 2 is a schematic flowchart of a first embodiment of a carrier aggregation configuration method provided in the present application;

fig. 3 is a flowchart illustrating a second embodiment of a carrier aggregation configuration method provided in the present application;

fig. 4 is a schematic diagram of a protocol stack of a MAC entity common to an LTE carrier and an NR carrier according to the present application;

fig. 5 is a schematic diagram of another protocol stack of a common MAC entity for LTE carriers and NR carriers provided in the present application;

fig. 6 is a schematic diagram of a protocol stack of independent MAC entities corresponding to LTE carriers and NR carriers provided in the present application;

fig. 7 is a schematic diagram of another protocol stack of independent MAC entities corresponding to LTE carriers and NR carriers provided in the present application;

fig. 8 is a flowchart illustrating a third embodiment of a carrier aggregation configuration method provided in the present application;

fig. 9 is a schematic diagram of a protocol stack for cross-site carrier aggregation according to the present application;

fig. 10 is a schematic structural diagram of a first configuration apparatus for carrier aggregation according to an embodiment of the present disclosure;

fig. 11 is a schematic structural diagram of a second configuration apparatus for carrier aggregation according to the present application;

fig. 12 is a schematic structural diagram of a third configuration apparatus for carrier aggregation according to the present application;

fig. 13 is a schematic structural diagram of a fourth configuration apparatus for carrier aggregation according to the present application;

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

fig. 15 is a schematic structural diagram of a first network device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of an embodiment of a user equipment provided in the present application;

fig. 17 is a schematic structural diagram of a second network device according to the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms "first," "second," and the like in the description and in the claims, and in the foregoing drawings, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In the current Technology, only co-sited carrier aggregation with Radio Access Technology (RAT) carriers is supported. Before a New Radio (NR) technology, each RAT corresponds to a respective Core network, but in NR, NR is connected to a 5G Core network (5G Core network,5 GC), and Long Term Evolution (LTE) is also evolved and can be connected to 5GC. All NRs and LTE can be connected to the same core network, i.e. 5GC. In order to further improve the rate of trading by bandwidth, carrier aggregation of an NR carrier and an LTE carrier and a cross-site carrier aggregation mechanism are proposed.

Because the aggregated carriers need to have the same coverage to be aggregated, the aggregated carriers are not necessarily many in one coverage area, so the bandwidth of the aggregated carriers is limited to a certain extent, and in order to improve the possibility of the aggregated carriers, cross-RAT carrier aggregation is supported, and cross-site carrier aggregation is significant, so that the transmission rate can be improved.

The present application mainly relates to two types of execution main bodies, namely network equipment and user equipment. In this scenario, it should be understood that the network device may be a device that communicates with the UE (or referred to as a terminal device, a communication terminal, a terminal). A network device may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Optionally, the Network device may be a Base Transceiver Station (BTS) in a Global System for Mobile Communications (GSM) System or a Code Division Multiple Access (CDMA) System, may also be a Base Station (NodeB, NB) in a WCDMA System, may also be an evolved Node B (eNB or eNodeB) in an LTE System, or a Radio controller in a Cloud Radio Access Network (CRAN), or may be a Network side device in a 5G Network or a Network device in a future evolved Public Land Mobile Network (PLMN), or may also be a device for providing communication coverage in a new NR technology, and the like, which is not particularly limited in this scheme.

"UE" as used herein includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), digital Subscriber Line (DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., for a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A UE arranged to communicate over a radio 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 Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. In particular implementations, a UE can refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user 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 handheld device with Wireless communication capability, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc. In an embodiment of the present application, the UE has an interface for communicating with a network device (e.g., a cellular network).

With the development of the technology, the 5G technology will support more dual connectivity modes, and in order to further increase the transmission rate, the prior art only supports the carrier aggregation method of the same RAT in the same site, and cannot meet the current scenario. For example, before NR, each RAT corresponds to a respective core network, but in NR, NR is connected to 5GC, and LTE is also evolved and can be connected to 5GC. All NRs and LTE can be connected to the same core network, i.e. 5GC. In order to further improve the rate of exchanging bandwidth, carrier aggregation across RAT technologies is proposed, for example, carrier aggregation of NR carrier and LTE carrier and carrier aggregation across sites may be performed, so that more carriers are aggregated in this way, and the transmission rate is improved. The technical solution of the present application will be described below with reference to several specific examples.

Fig. 2 is a flowchart illustrating a first embodiment of a method for configuring carrier aggregation according to the present application, where as shown in fig. 2, the method for configuring carrier aggregation relates to a network device and a UE, and specifically includes the following steps:

s101: the method comprises the steps of obtaining configuration information of UE, wherein the configuration information comprises a carrier list capable of carrying out carrier aggregation, and the carrier list comprises carriers of at least two RATs.

In this step, the network device may configure the carrier aggregation for the UE according to the capability of carrier aggregation supported by the UE and the measurement of each different RAT, and acquire configuration information, where at least carriers that can be aggregated need to be configured in the configuration information, and the carriers are carriers of different RAT technologies. For example, the configured carrier list includes NR carriers and LTE carriers.

S102: and sending 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. And after receiving the configuration information, the UE transmits data according to the carrier list configured by the configuration information.

In a specific implementation of the scheme, the configuration information may further configure a protocol stack, and in order to implement aggregation between carriers across RATs, in the scheme, carriers of different RATs share a Media Access Control (MAC) entity. The MAC entity may be a hybrid MAC entity, i.e., a mixed MAC, having functions of multiple RAT MAC entities.

In a specific implementation of the solution, in order to configure carrier aggregation, the network device first needs to acquire capability information of the UE, perform frequency point measurement configuration, and configure the UE to measure frequency points of different RATs. Fig. 3 is a flowchart illustrating a second embodiment of a carrier aggregation configuration method provided in the present application, and as shown in fig. 3, the specific implementation step of the step S101 includes:

s201: and reporting capability information to the network equipment, wherein the capability information is used for indicating whether the UE supports the carrier aggregation across the RATs.

In this step, after the UE is in the connected state, it needs to report capability information to the network device, that is, it needs to indicate whether the UE supports carrier aggregation across RATs on the network side.

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

S202: and measuring the frequency points of different RATs according to the configuration of the network equipment to obtain a frequency point measurement result.

In this step, after the UE accesses the network, the network device may configure the UE to perform frequency point measurement, and in this scheme, the network device may configure the UE to perform measurement on frequency points of different RATs to obtain corresponding frequency point measurement results.

S203: and reporting the frequency point measurement result corresponding to each RAT to the network equipment.

And after the UE obtains the frequency point measurement result, reporting the obtained frequency point measurement results of different RATs to the network equipment.

S204: and determining whether cross-RAT carrier aggregation is configured or not according to the frequency point measurement result corresponding to each RAT and the capability information.

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

According to the configuration method for carrier aggregation provided by this embodiment, after the UE accesses the network, capability information whether to support cross-RAT carrier aggregation is reported to the network device, and the network device determines, by combining the capability information and the frequency point measurement result, whether to configure the UE for cross-RAT carrier aggregation, in the configuration process, the configuration information configured by the network device at least includes two or more types of carrier aggregation of the RAT, and after the UE acquires the configuration information, in the data transmission process, the bandwidth during transmission can be further increased by performing carrier aggregation on carriers of multiple RATs, and the efficiency of data transmission can be improved.

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

Under the condition that carriers of different RATs commonly use the same MAC entity, the carriers of at least two RATs share the same Service Data Adaptation Protocol (SDAP) entity.

In the case of this scheme, the MAC entity has MAC layer functions of the at least two RATs, that is, the MAC entity can serve the 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, where the MAC entity may be determined according to a RAT of a primary carrier. In the implementation of the scheme, a MAC adaptation layer is configured below the MAC entity to implement the MAC layer function of the RAT that the MAC entity does not have. That is, the configuration information is also used to configure a MAC adaptation layer located below the MAC entity, the MAC adaptation layer being used to provide MAC layer functions of carriers of a 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 MAC entities corresponding to the carriers of each RAT are different, that is, the carriers of different RATs correspond to independent MAC entities.

When the network device configures the carrier aggregation across RATs, protocol stack configuration and other configurations may also be performed, specifically:

(1) And configuring cross-carrier scheduling among carriers of the same RAT in the carrier list.

(2) And transmitting a Physical Downlink Shared Channel (PDSCH) of a carrier of the same RAT in the configured carrier list through a Physical Uplink Control Channel (PUCCH) of the RAT carrier for feedback.

(3) And configuring the same RAT carrier in the carrier list to comprise at least one carrier used for Physical Uplink Control Channel (PUCCH) transmission.

(4) And configuring Discontinuous Reception (DRX) timers for carriers of different RATs in the carrier list, wherein the DRX timers are used for monitoring a Physical Downlink Control Channel (PDCCH) on the carrier of the corresponding RAT.

On the basis of the above embodiments, the following takes LTE carriers and NR carriers as examples to describe the configuration of carriers across RATs. The configuration list sent by the network equipment to the UE comprises an LTE carrier and an NR carrier, and the NR carrier and the LTE carrier share the same station address in the scheme.

Fig. 4 is a schematic diagram of a protocol stack of a MAC entity common to an LTE carrier and an NR carrier according to the present application. As shown in fig. 4, the network device may configure, when performing cross-RAT carrier aggregation for the UE:

(1) One SDAP entity is shared between LTE carriers and NR carriers aggregated across the RATs, and 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 having LTE MAC entity function and NR MAC entity function, and mixed MAC.

(2) The network device (network side) configures an SDAP, a bearer configuration (Packet Data Convergence Protocol, PDCP), a Radio Link Control (RLC)), and an MAC configuration, and a corresponding carrier list. While supporting whether each carrier in the carrier list is LTE or NR.

Wherein, the version of the PDCP entity is NR version, and the version of the RLC entity may be LTE version or NR version. Configuration may be performed by a network device, or fixation to NR version may also be set.

That is, in a specific implementation manner, the configuration information is further used for configuring a function of a PDCP layer of the PDCP entity having the NR carrier, and the configuration information is further used for configuring the RLC entity to support the LTE technology or the NR technology.

(3) The cross-carrier scheduling can only occur between two carriers of the same RAT, that is, the cross-carrier scheduling can only be performed between two carriers of LTE, or the cross-carrier scheduling can only be performed on quality inspection of two carriers of NR.

(4) The feedback of the downlink PDSCH transmission is also fed back on the PUCCH of the respective RAT. And configuring at least one carrier with PUCCH configuration information in the carrier corresponding to each RAT.

(5) The NR carrier list and the LTE carrier list configure their respective DRX to control 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 PDCCH of 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 function of NR MAC.

Fig. 5 is a schematic diagram of another protocol stack of a MAC entity common to an LTE carrier and an NR carrier according to the present application. As shown in fig. 5, the network device may configure, when performing cross-RAT carrier aggregation for the UE:

(1) And configuring a common SDAP entity among the carriers aggregated by crossing the RATs, wherein the carriers aggregated by different RATs correspond to the same MAC entity.

In the scheme, the version of the MAC entity depends on whether a primary carrier (PCell) is an LTE carrier or an NR carrier, and if the PCell is an LTE carrier, the MAC entity is LTE version, otherwise it is NR version. Because the MAC entity only has the function of one RAT in the scheme, a MAC adaptation layer is arranged below the MAC entity. The role of the MAC adaptation layer is to implement different RAT functions for carriers of different RATs or to provide MAC layer functions of the carrier RAT for carriers of a RAT different from the MAC entity.

(2) The network side configures SDAP, bearer configuration (PDCP, RLC) and MAC configuration, and corresponding carrier list. While supporting whether each carrier in the carrier list is LTE or NR.

Wherein, the version of the PDCP entity is NR version, the version of the RLC entity may be LTE version or NR version, and the configuration is performed by the network side or the RLC entity is fixed to NR version.

In the two specific schemes, the network device may configure the UE to perform carrier aggregation when the LTE carrier and the NR carrier share the same MAC entity, and the MAC entity is required to be capable of adapting to different RATs. When the UE performs data transmission, the UE may map data onto any carrier (including an LTE carrier or an NR carrier) that can transmit data, so as to better embody a gain of carrier aggregation.

Fig. 6 is a schematic diagram of a protocol stack of independent MAC entities corresponding to LTE carriers and NR carriers provided in the present application. As shown in fig. 6, the network device may be configured in performing cross-RAT carrier aggregation for the UE (in this scenario, the LTE carrier and the NR carrier serve different PDU sessions, respectively):

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

(2) And configuring the SDAP configuration, the bearer configuration (PDCP, RLC) and the MAC configuration of each PDU session corresponding to one RAT, and a corresponding carrier list.

(3) Similar to the previous 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 is serving.

(5) The feedback of the downlink PDSCH transmission is also fed back on the PUCCH of the respective RAT. And configuring at least one carrier with PUCCH configuration information in the carrier corresponding to each RAT.

In the scheme, the protocol stacks of the two RATs are relatively independent and are relatively easy to realize.

Fig. 7 is a schematic diagram of another protocol stack of independent MAC entities corresponding to LTE carriers and NR carriers provided in the present application. As shown in fig. 7, the network device may configure, when performing cross-RAT carrier aggregation for the UE:

(1) And configuring a common SDAP entity among the carriers aggregated by crossing the RATs, wherein the carriers aggregated by different RATs correspond to independent MAC entities. For example, 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, corresponding carrier list, under each RAT.

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

The difference between the two schemes and the aforementioned embodiment is that the protocol stacks of the RATs are relatively independent and relatively easy to implement. SDAP is inherently NR version, and PDCP is also NR version. Because the same SDAP is used, different RATs are not used according to PDU session (session), and a new application scene of cross-RAT carrier aggregation is provided.

Fig. 8 is a flowchart illustrating a third embodiment of a carrier aggregation configuration method provided in the present application, and as shown in fig. 8, the carrier aggregation configuration method provided in this embodiment is mainly used for cross-site carrier aggregation configuration, and specifically includes the following steps:

s301: the method comprises the steps of obtaining configuration information of UE, wherein the configuration information comprises a carrier list capable of carrying out carrier aggregation, and the carrier list comprises a carrier of first network equipment and a carrier of second network equipment.

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

After entering a connected state, the UE reports capability information to the first network equipment, the capability information at least indicates whether the UE supports carrier aggregation across sites, and the first network equipment performs carrier aggregation configuration based on the capability information and a network architecture.

And if the UE supports carrier aggregation of cross-site, the first network equipment configures the carriers available for the UE to carry out carrier aggregation.

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

S302: and sending the configuration information to the UE.

The first network device sends the configuration information to the UE, and in the process of data transmission by the UE, the UE may map data onto carriers of the first network device and the second network device for transmission according to the configuration of the network side, so as to improve transmission efficiency.

In a specific implementation of the present scheme, the configuration information may further configure that Hybrid Automatic Repeat-reQuest (HARQ) numbers of the first network device and the second network device are the same.

The configuration information is further used to configure that downlink data transmission of the second network device is 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 in this embodiment.

The carrier aggregation configuration method provided in the foregoing embodiment provides a cross-site carrier aggregation scheme, and in the data transmission process, data interaction may be performed with the UE through carriers on two network devices, so as to effectively improve transmission efficiency.

On the basis of the foregoing embodiment, the first network device may perform scheduling configuration on the second network device, and in a specific implementation, the first network device may 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. For a second network device, TB data and/or first scheduling information sent by a first network device are received through an Xn interface, and then downlink data is sent based on the first scheduling information in the data transmission process.

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

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

In 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 following describes a configuration of cross-site carrier aggregation provided by the present application, taking a first network device as a base station gNB1 and a second network device as a base station gNB2 as an example.

Fig. 9 is a schematic diagram of a protocol stack of carrier aggregation across site addresses provided in the present application, and as shown in fig. 9, a gNB2 is connected to an interface of a gNB1, and the gNB1 and the gNB2 share the same MAC entity. An ideal backhaul connection is between gNB1 and gNB2. CC1 and CC2 belong to the same base station gNB1, and CC3 and CC4 belong to 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 (gNB 1) to which the primary carrier (PCell) belongs configures the configuration of the protocol stacks of all bearers, i.e. the SDAP configuration, PDCP, RLC configuration, and MAC configuration.

In this scheme, the HARQ of the two base stations are numbered uniformly. The base station (gNB 1) where the primary carrier (PCell) is located is responsible for transferring TB data on the Xn interface, and/or scheduling information (i.e. first scheduling information) is provided to the base station (gNB 2) providing resources for transmitting data.

And the base station (gNB 1) where the main carrier is located is responsible for transmitting the scheduling information (i.e. the second scheduling information) to the base station (gNB 2) providing resources on the Xn interface for receiving the uplink data, and the resource base station (gNB 2) is responsible for forwarding the received TB data to the base station (gNB 1) where the PCell is located.

The feedback of the downlink data sent by the base station (gNB 2) configured to provide the resource by the base station (gNB 1) where the primary carrier is located may be fed back on the PUCCH of the base station providing the resource, or fed back on the PUCCH of the carrier of the base station where the PCell is located, which is not limited in the present application.

In addition to the above mentioned data and scheduling information, some other information may be exchanged between two base stations to facilitate scheduling, for example: channel measurement information, such as a Channel Sounding Reference Signal (SRS), reporting information of a Power Headroom Report (PHR), carrier management information of a main carrier, measurement Report information of a Channel State Indicator (CSI), sleep state information of the main carrier, and the like.

The configuration method for carrier aggregation provided in this embodiment may aggregate carriers of a co-sited primary carrier and a resource-providing network device, and further improve a transmission rate. Compared with other schemes of double connection, the scheme can use the resources of two sites more flexibly.

In the technical scheme provided by the embodiment of the application, mechanisms of cross-RAT carrier aggregation and cross-site carrier aggregation are introduced, so that the possibility of aggregating more carriers and providing higher speed is provided.

Fig. 10 is a schematic structural diagram of a first configuration device for carrier aggregation according to the present application, and as shown in fig. 10, the configuration device 10 for carrier aggregation includes:

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

a sending module 12, configured to send the configuration information to the UE.

In a specific implementation of the configuration apparatus 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 apparatus 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, where the MAC entity is determined according to a RAT of a primary carrier.

Optionally, the configuration information is further configured to configure a MAC adaptation layer located below the MAC entity, where the MAC adaptation layer is configured to provide a MAC layer function of a carrier of a RAT different from that of 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 carriers of each RAT are different from the MAC entity.

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 carrier list includes at least one carrier used for PUCCH transmission in the same RAT carrier.

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

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

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

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

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

Optionally, the capability information is further used to indicate a type of supported carrier aggregation, where the type of supported carrier aggregation 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 cross-RAT carrier aggregation is configured according to the frequency point measurement result corresponding to each RAT and the capability information.

The carrier aggregation configuration apparatus provided in any of the embodiments is configured to execute a technical scheme on the network device side in the cross-RAT carrier aggregation scheme in the foregoing method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.

Fig. 11 is a schematic structural diagram of a second configuration apparatus for carrier aggregation according to the present application, and as shown in fig. 11, a configuration apparatus 20 for carrier aggregation according to the present embodiment includes:

a receiving module 21, configured to receive configuration information sent by a network device, 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 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 configuration information is further configured to configure a MAC adaptation layer located below the MAC entity, where the MAC adaptation layer is configured to provide a MAC layer function of a carrier of a RAT different from the MAC entity.

Optionally, the transmission of the physical downlink shared channel of the carrier of the same RAT in the carrier list is fed back through a 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 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 PDCCHs on carriers of corresponding RATs.

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

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

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

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

Optionally, the carrier aggregation configuration apparatus 20 further includes:

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

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

The carrier aggregation configuration device provided in any of the embodiments above is configured to execute a technical scheme on the UE side in the cross-RAT carrier aggregation scheme in the foregoing method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.

Fig. 12 is a schematic structural diagram of a third embodiment of a carrier aggregation configuration apparatus provided in the present application, and as shown in fig. 12, an Xn interface of the carrier aggregation configuration apparatus 30 provided in this embodiment is connected to a second network device, where the carrier aggregation configuration apparatus 30 includes:

a processing module 31, configured to acquire configuration information for a UE, where the configuration information includes a carrier list capable of performing carrier aggregation, and the carrier list 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 further used for configuring a protocol stack of the carriers in the carrier list.

Optionally, the configuration apparatus for carrier aggregation is the same as the HARQ number of the second network device.

Optionally, the sending module 32 is further configured to:

and sending TB data and/or first scheduling information to the second network equipment through the Xn interface, wherein the first scheduling information is used for sending downlink data by the second network equipment.

Optionally, the sending module 32 is further configured to:

and sending second scheduling information to the second network equipment through the Xn interface, wherein the second scheduling information is used for the second network equipment to receive uplink data.

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

a first receiving module 33, 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 that downlink data transmission of the second network device is fed back on a PUCCH of the second network device or fed back on a PUCCH of the configuration apparatus 30 for carrier aggregation.

a second receiving module 34, configured to receive capability information reported by the UE, where the capability information is used to indicate whether the UE supports carrier aggregation across sites.

The carrier aggregation configuration apparatus provided in any of the embodiments above is configured to execute a technical scheme on the first network device side in the cross-site carrier aggregation scheme in the foregoing method embodiments, and the implementation principle and the technical effect are similar, and are not described herein again.

Fig. 13 is a schematic structural diagram of a fourth configuration apparatus for carrier aggregation according to the present application, and as shown in fig. 13, the configuration apparatus 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 carrier list capable of performing 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 device is connected to an Xn interface of the first network device, and provides resources for the configuration apparatus 40 for carrier aggregation.

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

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

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

a sending module 42, configured to report capability information to the first network device, where the capability information is used to indicate whether the carrier aggregation configuration device supports carrier aggregation across sites.

The carrier aggregation configuration apparatus provided in any of the embodiments above is configured to execute a technical scheme on the UE side in the cross-site carrier aggregation scheme in the foregoing method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.

Fig. 14 is a schematic structural diagram of an embodiment of a transmission apparatus provided in the present application, and as shown in fig. 14, the transmission apparatus 50 is connected to an Xn interface of a first network device, where the transmission apparatus 50 includes:

a receiving module 51, 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 for the transmission apparatus to send downlink data.

Optionally, the receiving module 51 is further configured to:

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

In a specific embodiment of the apparatus, the transmission apparatus further comprises:

a sending module 52, 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 above embodiments is configured to execute the technical solution on the second network device side in the foregoing method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.

Fig. 15 is a schematic structural diagram of a first embodiment of a network device provided in the present application, and as shown in fig. 15, the network device 100 includes:

a processor 111, a memory 112, an interface 113 to communicate with user equipment;

the memory 112 stores computer-executable instructions;

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

Fig. 16 is a schematic structural diagram of an embodiment of a user equipment provided in the present application, and as shown in fig. 16, the user equipment 200 includes:

a processor 211, a memory 212, an interface 213 to communicate with a network device;

the memory 212 stores computer-executable instructions;

the processor 211 executes the computer execution instructions stored in the memory, so that the processor executes the technical solution of any one of the foregoing method embodiments on the UE side.

Fig. 17 is a schematic structural diagram of a second embodiment of a network device provided in the present application, and 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 devices;

the memory 312 stores computer-executable instructions;

the processor 311 executes the computer execution instruction stored in the memory, so that the processor executes the technical solution of the second network device side in the cross-site carrier aggregation according to the foregoing method embodiment.

In a specific implementation of the network device or the user equipment, the memory, the processor and the interface may be connected through a bus, or may be connected in another manner. Alternatively, the memory may be integrated within the processor.

The embodiment of the present application further provides a computer-readable storage medium, where a computer executable instruction is stored in the computer-readable storage medium, and when the computer executable instruction is executed by a processor, the computer executable instruction is used to implement the scheme of the network device in the configuration method of cross-RAT carrier aggregation in the foregoing method embodiment or implement the scheme of the first network device in the configuration method of cross-site carrier aggregation in the foregoing method embodiment.

An embodiment of the present application further provides a computer-readable storage medium, where a computer executable instruction is stored in the computer-readable storage medium, and when the computer executable instruction is executed by a processor, the computer executable instruction is used to implement a technical solution on a UE side in any one of the foregoing method embodiments.

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

An embodiment of the present application further provides a chip, including: the processing module is used for executing a scheme of a network device side in the cross-RAT carrier aggregation configuration method or executing a technical scheme of a first network device side in the cross-site carrier aggregation configuration method.

An embodiment of the present application further provides a chip, including: and the processing module is used for executing the technical scheme of the second network equipment side in the cross-site carrier aggregation scheme.

Further, any chip further includes a storage module (e.g., a memory), where the storage module is configured to store an instruction, and the processing module is configured to execute the instruction stored by the storage module, and execute the instruction stored in the storage module, so that the processing module executes the technical solution on the network device side in any method embodiment described above.

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

Further, the chip further includes a storage module (e.g., a memory), where the storage module is configured to store instructions, and the processing module is configured to execute the instructions stored by the storage module, and the execution of the instructions stored in the storage module causes the processing module to execute the technical solution on the UE side in any of the foregoing method embodiments.

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

The embodiment of the present application further provides a program, which is configured to implement the UE-side scheme in any one of the foregoing method embodiments when the program is executed by a processor. Alternatively, the processor may be a chip.

The embodiment of the present application further provides a computer program product, which includes program instructions, where the program instructions are used to implement a scheme of any network device side in any of the foregoing method embodiments.

An embodiment of the present application further provides a computer program product, which includes program instructions, where the program instructions are used to implement the UE-side scheme in any of the foregoing method embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules is only one logical division, and other divisions may be realized in practice, for example, a plurality of modules may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, and the indirect coupling or communication connection of the modules may be in an electrical, mechanical or other form.

In any implementation of the above devices, it should be understood that the Processor may be a Central Processing Unit (CPU), other general purpose processors, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor, or in a combination of the hardware and software modules in the processor.

All or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The aforementioned program may be stored in a readable memory. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state disk, magnetic tape, floppy disk, optical disk, and any combination thereof.

Claims

A configuration method of carrier aggregation is applied to a network device, and the method comprises the following steps:

acquiring configuration information of User Equipment (UE), wherein the configuration information comprises a carrier list capable of carrying out carrier aggregation, and the carrier list comprises carriers of at least two Radio Access Technologies (RAT);

and sending the configuration information to the UE.
The method of claim 1, wherein the carriers of the at least two RATs share a same Service Data Adaptation Protocol (SDAP) entity and wherein the carriers of the at least two RATs share a same Medium Access Control (MAC) entity.
The method of claim 2, wherein the MAC entity has MAC layer functionality of the at least two RATs.
The method of claim 2, wherein the MAC entity has MAC layer functionality of any of the at least two RATs, and wherein the MAC entity is determined according to a RAT of a primary carrier.
The method of claim 4, wherein the configuration information is further used to configure a MAC adaptation layer located below the MAC entity, wherein the MAC adaptation layer is used to provide MAC layer functionality for a carrier of a RAT different from the MAC entity.
The method of claim 1, wherein carriers of the at least two RATs share a same SDAP entity, wherein carriers of a same RAT share a same MAC entity, and wherein carriers of each RAT differ with respect to their respective MAC entities.
The method according to any of claims 1 to 6, wherein cross-carrier scheduling is possible between carriers of the same RAT in the carrier list.
The method according to any of claims 1 to 7, wherein the PDSCH transmissions of the carriers of the same RAT in the carrier list are fed back via a PUCCH.
The method according to claim 8, wherein at least one carrier for physical uplink control channel, PUCCH, transmission is included in a same RAT carrier in the carrier list.
The method according to any of claims 1 to 9, wherein carriers of different RATs in the carrier list are respectively configured with a Discontinuous Reception (DRX) timer for monitoring a Physical Downlink Control Channel (PDCCH) on a carrier of a corresponding RAT.
The method according to any of claims 1 to 10, wherein a long term evolution, LTE, carrier and a new wireless, NR, carrier are included in the carrier list.
The method of claim 11, wherein the configuration information is further used for configuring a function of a PDCP layer of a packet data convergence protocol PDCP entity having an NR carrier, and wherein the configuration information is further used for configuring an RLC entity to support an LTE technology or to support an NR technology.
The method according to any one of claims 1 to 12, further comprising:

and receiving capability information reported by the UE, wherein the capability information is used for indicating whether the UE supports cross-RAT carrier aggregation.
The method of claim 13, wherein the capability information is further used for indicating types of supported carrier aggregation, and wherein the types of carrier aggregation comprise: a common MAC entity or an independent MAC entity.
The method according to claim 13 or 14, characterized in that the method further comprises:

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

and determining whether cross-RAT carrier aggregation is configured or not according to the frequency point measurement result corresponding to each RAT and the capability information.
A configuration method for carrier aggregation is applied to a User Equipment (UE), and comprises the following steps:

receiving configuration information sent by a network device, wherein the configuration information can be a carrier list for carrier aggregation, and the carrier list comprises carriers of at least two Radio Access Technologies (RAT).
The method of claim 16, wherein the carriers of the at least two RATs share a same service data adaptation protocol, SDAP, entity and wherein the carriers of the at least two RATs share a same medium access control, MAC, entity.
The method of claim 17, wherein the MAC entity has MAC layer functionality of the at least two RATs.
The method of claim 17, wherein the MAC entity has MAC layer functionality of any one of the at least two RATs, and wherein the MAC entity is determined according to a RAT of a primary carrier.
The method of claim 19, wherein the configuration information is further used to configure a MAC adaptation layer located below the MAC entity, wherein the MAC adaptation layer is used to provide MAC layer functionality for a carrier of a RAT different from the MAC entity.
The method of claim 16, wherein carriers of the at least two RATs share a same SDAP entity, carriers of a same RAT share a same MAC entity, and wherein carriers of each RAT differ in their respective MAC entities.
The method according to any of claims 16 to 21, wherein cross-carrier scheduling is possible between carriers of the same RAT in the carrier list.
The method according to any of claims 16 to 22, wherein the physical downlink shared channel transmission of the carrier of the same RAT in the carrier list is fed back through a physical uplink control channel, PUCCH, of the RAT carrier.
The method of claim 23, wherein at least one carrier for Physical Uplink Control Channel (PUCCH) transmission is included in a same RAT carrier in the carrier list.
The method according to any of claims 16 to 24, wherein carriers of different RATs in the carrier list are respectively configured with Discontinuous Reception (DRX) timers for monitoring a Physical Downlink Control Channel (PDCCH) on the carrier of the corresponding RAT.
The method according to any of claims 16 to 25, wherein a long term evolution, LTE, carrier and a new wireless, NR, carrier are included in the carrier list.
The method of claim 26, wherein the configuration information is further used for configuring a function of a PDCP layer of a packet data convergence protocol PDCP entity having an NR carrier, and wherein the configuration information is further used for configuring an RLC entity to support an LTE technology or to support an NR technology.
The method of any one of claims 16 to 27, further comprising:

and reporting capability information to the network equipment, wherein the capability information is used for indicating whether the UE supports cross-RAT carrier aggregation.
The method of claim 28, wherein the capability information is further used for indicating types of supported carrier aggregation, and wherein the types of carrier aggregation comprise: a common MAC entity or an independent MAC entity.
The method of claim 28 or 29, further comprising:

measuring the frequency points of different RATs according to the configuration of the network equipment to obtain a frequency point measurement result;

and reporting the frequency point measurement result corresponding to each RAT to the network equipment.
A configuration method for carrier aggregation is applied to a first network device, wherein a second network device is connected to an Xn interface of the first network device, and the method comprises the following steps:

acquiring configuration information of User Equipment (UE), wherein the configuration information comprises a carrier list capable of carrying out carrier aggregation, and the carrier list comprises a carrier of the first network equipment and a carrier of the second network equipment;

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

and sending TB data and/or first scheduling information to the second network equipment through the Xn interface, wherein the first scheduling information is used for sending downlink data by the second network equipment.
The method of any one of claims 31 to 34, further comprising:

and sending second scheduling information to the second network equipment through the Xn interface, wherein the second scheduling information is used for the second network equipment to receive uplink data.
The method of claim 35, further comprising:

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

and receiving capability information reported by the UE, wherein the capability information is used for indicating whether the UE supports carrier aggregation across sites.
A configuration method for carrier aggregation is applied to a User Equipment (UE), and comprises the following steps:

receiving configuration information sent by a first network device, where the configuration information includes a carrier list capable of performing carrier aggregation, where the carrier list includes a carrier of the first network device and a carrier of a second network device, and the second network device is connected to an Xn interface of the first network device to provide resources for the UE.
The method of claim 39, wherein the configuration information is further used for protocol stack configuration of carriers in the carrier list.
The method according to claim 39 or 40, wherein the hybrid automatic repeat request, HARQ, numbers of the first network device and the second network device are the same.
The method according to any of claims 39 to 41, wherein the configuration information is further used for configuring the feedback of the downlink data transmission of the second network device on a Physical Uplink Control Channel (PUCCH) of the second network device or on a PUCCH of the first network device.
The method of any one of claims 39 to 42, further comprising:

and reporting capability information to the first network equipment, wherein the capability information is used for indicating whether the UE supports carrier aggregation of cross-site.
A transmission method applied to a second network device, the second network device being connected to an Xn interface of a first network device, the method comprising:

and receiving TB data and/or first scheduling information sent by the first network equipment through the Xn interface, wherein the first scheduling information is used for sending downlink data by the second network equipment.
The method of claim 44, further comprising:

and receiving second scheduling information sent by the first network equipment through the Xn interface, wherein the second scheduling information is used for the second network equipment to receive uplink data.
The method of claim 45, further comprising:

and sending TB data or hybrid automatic repeat request (HARQ) feedback to the first network equipment through the Xn interface.
An apparatus for configuring carrier aggregation, comprising:

a processing module, configured to obtain configuration information for a user equipment UE, where the configuration information includes a carrier list capable of performing carrier aggregation, and the carrier list includes carriers of at least two Radio Access Technologies (RATs);

a sending module, configured to send the configuration information to the UE.
The apparatus of claim 47, wherein the carriers of the at least two RATs share a same Service Data Adaptation Protocol (SDAP) entity, and wherein the carriers of the at least two RATs share a same Medium Access Control (MAC) entity.
The apparatus of claim 48, wherein the MAC entity has MAC layer functionality of the at least two RATs.
The apparatus of claim 48, wherein the MAC entity has MAC layer functionality of any of the at least two RATs, and wherein the MAC entity is determined according to a RAT of a primary carrier.
The apparatus of claim 50, wherein the configuration information is further configured to configure a MAC adaptation layer located below the MAC entity, the MAC adaptation layer configured to provide MAC layer functionality for a carrier of a different RAT than the MAC entity.
The apparatus of claim 47, wherein carriers of at least two RATs share a same SDAP entity, wherein carriers of a same RAT share a same MAC entity, and wherein carriers of each RAT differ by their respective MAC entities.
The apparatus of any one of claims 47-52, wherein cross-carrier scheduling is enabled between carriers of a same RAT in the carrier list.
The apparatus according to any of claims 47-53, wherein the PDSCH transmissions of carriers of the same RAT in the carrier list are fed back via a PUCCH.
The apparatus according to claim 54, wherein at least one carrier for Physical Uplink Control Channel (PUCCH) transmission is included in a same RAT carrier in the carrier list.
The apparatus according to any of claims 47 to 55, wherein carriers of different RATs in the carrier list are respectively configured with a Discontinuous Reception (DRX) timer for monitoring a Physical Downlink Control Channel (PDCCH) on a carrier of a corresponding RAT.
The apparatus according to any of claims 47-56, wherein a Long term evolution, LTE, carrier and a new wireless NR carrier are comprised in the carrier list.
The apparatus of claim 57, wherein the configuration information is further for configuring a function of a Packet Data Convergence Protocol (PDCP) entity having a PDCP layer of NR carriers, and wherein the configuration information is further for configuring a RLC entity to support LTE technology or NR technology.
The apparatus of any one of claims 47 to 58, further comprising:

a receiving module, configured to receive capability information reported by the UE, where the capability information is used to indicate whether the UE supports inter-RAT carrier aggregation.
The apparatus of claim 59, wherein the capability information is further configured to indicate types of supported carrier aggregation, and wherein the types of carrier aggregation comprise: a common MAC entity or an independent MAC entity.
The apparatus of claim 59 or 60,

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 cross-RAT carrier aggregation is configured according to the frequency point measurement result corresponding to each RAT and the capability information.
An apparatus for configuring carrier aggregation, comprising:

a receiving module, configured to receive configuration information sent by a network device, where the configuration information may be a carrier list for performing carrier aggregation, and the carrier list includes carriers of at least two Radio Access Technologies (RATs).
The apparatus of claim 62, wherein the carriers of the at least two RATs share a same Service Data Adaptation Protocol (SDAP) entity, and wherein the carriers of the at least two RATs share a same Medium Access Control (MAC) entity.
The apparatus of claim 63, wherein the MAC entity has MAC layer functionality of the at least two RATs.
The apparatus of claim 63, wherein the MAC entity has MAC layer functionality of any of the at least two RATs, and wherein the MAC entity is determined according to a RAT of a primary carrier.
The apparatus of claim 65, wherein the configuration information is further configured to configure a MAC adaptation layer located below the MAC entity, wherein the MAC adaptation layer is configured to provide MAC layer functionality for a carrier of a different RAT than the MAC entity.
The apparatus of claim 62, wherein the carriers of the at least two RATs share a same SDAP entity, wherein the carriers of a same RAT share a same MAC entity, and wherein the corresponding MAC entities for the carriers of each RAT are different.
The apparatus of any of claims 62-67, wherein cross-carrier scheduling is possible between carriers of a same RAT in the carrier list.
The apparatus according to any of claims 62 to 68, wherein physical Downlink shared channel transmissions of carriers of a same RAT in the carrier list are fed back via a physical uplink control channel, PUCCH, of the RAT carrier.
The apparatus of claim 69, wherein at least one carrier for Physical Uplink Control Channel (PUCCH) transmission is included in a same RAT carrier in the carrier list.
The apparatus according to any of claims 62 to 70, wherein carriers of different RATs in the carrier list are respectively configured with Discontinuous Reception (DRX) timers for monitoring a Physical Downlink Control Channel (PDCCH) on the carrier of the corresponding RAT.
The apparatus of any one of claims 62 to 71, wherein a Long Term Evolution (LTE) carrier and a new wireless (NR) carrier are included in the carrier list.
The apparatus of claim 72, wherein the configuration information is further for configuring a function of a Packet Data Convergence Protocol (PDCP) entity having a PDCP layer of NR carriers, and wherein the configuration information is further for configuring a RLC entity to support LTE technology or NR technology.
The apparatus of any one of claims 62 to 73, further comprising:

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 device supports inter-RAT carrier aggregation.
The apparatus of claim 74, wherein the capability information is further configured to indicate types of supported carrier aggregation, and wherein the types of carrier aggregation comprise: a common MAC entity or an independent MAC entity.
The apparatus of claim 74 or 75, further comprising:

the processing module is used for measuring the frequency points of different RATs according to the configuration of the network equipment to obtain a frequency point measurement result;

the sending module is further configured to report a frequency point measurement result corresponding to each RAT to the network device.
A configuration apparatus for carrier aggregation, wherein a second network device is connected to an Xn interface of the configuration apparatus for carrier aggregation, the apparatus comprising:

a processing module, configured to obtain configuration information for a user equipment UE, where the configuration information includes a carrier list capable of performing carrier aggregation, and the carrier list includes carriers of a configuration device for carrier aggregation and carriers of the second network device;

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

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

and sending second scheduling information to the second network equipment through the Xn interface, wherein the second scheduling information is used for the second network equipment to receive uplink data.
The apparatus of claim 81, further comprising:

a first receiving module, configured to receive TB data or HARQ feedback sent by the second network device through the Xn interface.
The apparatus of any one of claims 77 to 82, wherein the configuration information is further configured to configure the downlink data transmission of the second network device to be fed back on a Physical Uplink Control Channel (PUCCH) of the second network device or on a PUCCH of the configuration apparatus for carrier aggregation.
The apparatus of any one of claims 77 to 83, further comprising:

a second receiving module, 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.
An apparatus for configuring carrier aggregation, comprising:

a receiving module, configured to receive configuration information sent by a first network device, where the configuration information includes a carrier list capable of performing carrier aggregation, the carrier list includes a carrier of the first network device and a carrier of a second network device, and the second network device is connected to an Xn interface of the first network device and provides a resource for a configuration apparatus for carrier aggregation.
The apparatus of claim 85, wherein the configuration information is further for a protocol stack configuration of carriers in the carrier list.
The apparatus of claim 85 or 86, wherein hybrid automatic repeat request (HARQ) numbers of the first network device and the second network device are the same.
The apparatus of any one of claims 85 to 87, wherein the configuration information is further configured to configure the downlink data transmission of the second network device to be fed back on a physical uplink control channel, PUCCH, of the second network device or on a PUCCH of the first network device.
The apparatus of any one of claims 85 to 88, wherein the apparatus 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 device supports carrier aggregation across sites.
A transmission apparatus, wherein the transmission apparatus is connected to an Xn interface of a first network device, the apparatus comprising:

a receiving module, 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 configuration apparatus for carrier aggregation to send downlink data.
The apparatus of claim 90, wherein the receiving module is further configured to:

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

a sending module, configured to send TB data or HARQ feedback to the first network device through the Xn interface.
A network device, comprising:

a processor, a memory, an interface to communicate with a user device;

the memory stores computer-executable instructions;

the processor executing the computer-executable instructions stored by the memory causes the processor to perform the method of configuring carrier aggregation according to any one of claims 1 to 15.
A user device, comprising:

a processor, a memory, an interface to communicate with a network device;

the memory stores computer-executable instructions;

the processor executing the computer-executable instructions stored by the memory causes the processor to perform the method of configuring carrier aggregation according to any one of claims 16 to 30.
A network device, comprising:

a processor, memory, an interface to communicate with other network devices or user devices;

the memory stores computer-executable instructions;

the processor executing the computer-executable instructions stored by the memory causes the processor to perform the method of configuring carrier aggregation according to any one of claims 31 to 38.
A user device, comprising:

a processor, a memory, an interface to communicate with a network device;

the memory stores computer-executable instructions;

the processor executing the computer-executable instructions stored by the memory causes the processor to perform the method of configuring carrier aggregation according to any one of claims 39 to 43.
A network device, comprising:

a processor, memory, an interface to communicate with other network devices or user devices;

the memory stores computer execution instructions;

the processor executing computer-executable instructions stored by the memory causes the processor to perform the transmission method of any of claims 44 to 46.
A computer-readable storage medium having stored thereon computer-executable instructions for implementing the method of configuring carrier aggregation according to any one of claims 1 to 15, or 31 to 38 when executed by a processor.
A computer-readable storage medium having stored thereon computer-executable instructions for implementing the method of configuring carrier aggregation according to any one of claims 16 to 30, or 39 to 43 when executed by a processor.
A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, perform the transmission method of any one of claims 43 to 46.
A chip, comprising: a processing module and a communication interface, the processing module being configured to perform the method of configuring carrier aggregation according to any one of claims 1 to 15, or 31 to 38.
A chip, comprising: a processing module and a communication interface, the processing module being configured to perform the method of configuring carrier aggregation according to any one of claims 16 to 30, or 39 to 43.
A chip, comprising: a processing module for performing the transmission method of any one of claims 43 to 46 and a communication interface.