Method and device for reporting multi-carrier aggregation capability

Abstract

The embodiment of the invention discloses a method and a device for reporting multi-carrier aggregation capability, which can be applied to communication systems such as a long term evolution (LTE) system, a 5th generation (5G) mobile communication system, a 5G new radio (NR) system, or other future novel mobile communication systems, and can be used for reporting the multi-carrier aggregation capability of the multi-carrier aggregation capability of the multi-carrier aggregation capability of the multi-carrier aggregation capability of the multi-carrier aggregation capability of the multi-carrier aggregation capability of the multi-carrier aggregation capability of the multi-carrier aggregation capability of the multi-carrier aggregation capability of the multi-carrier aggregation capability. The method comprises the following steps: reporting an aggregation bandwidth level or aggregation capability information supported by terminal equipment to network side equipment through a first signaling, and reporting the aggregation bandwidth level supported by the terminal equipment to the network side equipment through a second signaling; wherein the aggregation bandwidth level reported by the second signaling is a rollback aggregation bandwidth level of the aggregation bandwidth level reported by the first signaling. According to the embodiment of the invention, the aggregation bandwidth level supported by the terminal equipment can be reported according to the first signaling and the second signaling. Through the mode, the situation that the network side equipment cannot be compatible with the aggregation bandwidth level contained in the first signaling can be avoided, and therefore resource waste can be avoided.

Description

[0001] This application is a divisional application of application number 202180003037.8, application date October 13, 2021, and invention name “A method and device for reporting multi-carrier aggregation capabilities”. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a method and device for reporting multi-carrier aggregation capability. Background Art

[0003] With the development of mobile communication technology, in order to meet the requirements of higher speeds, high frequency, large bandwidth, large-scale antenna technology and multi-carrier aggregation are increasingly becoming the development trend of wireless communication technology.

[0004] Multi-carrier aggregation technology is also widely used in the fifth-generation communication system, which is mainly divided into continuous carrier aggregation within a frequency band, non-continuous carrier aggregation within a frequency band, and carrier aggregation between frequency bands. For continuous carrier aggregation within a frequency band, RAN4 defines the aggregation bandwidth level of continuous carrier aggregation. In order to meet different application scenarios and different terminal capabilities, RAN4 further defines different fallback groups. Summary of the invention

[0005] The embodiment of the present application provides a method and device for reporting multi-carrier aggregation capability, which can be applied to a long term evolution (LTE) system, a fifth generation (5G) mobile communication system, a 5G new radio (NR) system, or other future new mobile communication systems and other communication systems. By implementing the embodiment of the present application, the aggregation bandwidth level supported by the terminal device can be reported according to the first signaling and the second signaling. In this way, it can be avoided that the network side device is incompatible with the aggregation bandwidth level contained in the first signaling, which is conducive to avoiding resource waste.

[0006] In a first aspect, an embodiment of the present application provides a method for reporting a multi-carrier aggregation capability, which is performed by a terminal device, and the method includes:

[0007] The aggregation bandwidth level or aggregation capability information supported by the terminal device is reported to the network side device through the first signaling, and the aggregation bandwidth level supported by the terminal device is reported to the network side device through the second signaling; wherein the aggregation bandwidth level reported in the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

[0008] Optionally, the aggregate bandwidth level reported in the first signaling and the aggregate bandwidth level reported in the second signaling belong to the same fallback group;

[0009] or

[0010] The aggregate bandwidth level reported in the second signaling and the aggregate bandwidth level reported in the first signaling are in different fallback groups;

[0011] or

[0012] The fallback group to which the aggregate bandwidth level reported in the second signaling belongs is a subgroup of the fallback group to which the aggregate bandwidth level reported in the first signaling belongs.

[0013] Optionally, the aggregation capability information is used to report the aggregation status within the uplink and downlink frequency bands supported by the terminal device, respectively, or to report the aggregation status within the frequency band.

[0014] Optionally, the aggregation state includes at least one of the following:

[0015] Continuous type;

[0016] Non-continuous type;

[0017] Continuous and discontinuous.

[0018] Optionally, the first signaling is NR carrier aggregation bandwidth level CA-BandwidthClassNR-v17xy signaling, where xy is a sequence number.

[0019] Optionally, the first signaling includes at least one of NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL-NR-v17xy signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

[0020] Optionally, the CA-BandwidthClassNR-v17xy signaling, the CA-BandwidthClassDL-NR-v17xy signaling, the CA-BandwidthClassUL-NR-v17xy signaling, the BandParameters-v17xy signaling, the BandList-v17xy signaling, the BandCombination-v17xy signaling, the BandCombinationList-v17xy signaling, the

[0021] SupportedBandCombinationList-v17xy signaling has the same identifier.

[0022] Optionally, the first signaling also includes NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling and NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, or NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL1-NR-v17xy signaling and NR uplink carrier aggregation bandwidth level

[0023] CA-BandwidthClassUL2-NR-v17xy signaling.

[0024] Optionally, the first signaling also includes at least one of band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list supportedBandCombinationList-v17xy signaling.

[0025] Optionally, the NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling, the NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, the NR uplink carrier aggregation bandwidth level

[0026] CA-BandwidthClassUL1-NR-v17xy signaling, NR uplink carrier aggregation bandwidth class CA-BandwidthClassUL2-NR-v17xy signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list supportedBandCombinationList-v17xy have the same identifier.

[0027] Optionally, the aggregation bandwidth level reported in the first signaling is one or more of extended aggregation bandwidth levels R, S, T, U, MA, MD, ME and MF.

[0028] Optionally, when the aggregate bandwidth level reported in the first signaling is one or more of R, S, T and U, the aggregate bandwidth level reported in the second signaling is F.

[0029] Optionally, when the aggregate bandwidth level reported in the first signaling is one or more of MA, MD, ME and MF, the aggregate bandwidth level reported in the second signaling is one of M, F, E, D or A.

[0030] Optionally, the first signaling includes: Intra-bandCA-support-v17xy signaling supporting intra-band carrier aggregation, and the Intra-bandCA-support-v17xy signaling is used to indicate the aggregation status within the uplink and downlink frequency bands supported by the terminal device.

[0031] Optionally, the first signaling includes: a combination of Intra-band CAUL-support-v17xy signaling supporting intra-band uplink carrier aggregation and Intra-band CADL-support-v17xy signaling supporting intra-band downlink carrier aggregation, and the Intra-band CAUL-support-v17xy signaling and Intra-band CADL-support-v17xy signaling are used to indicate the uplink carrier aggregation status and the downlink carrier aggregation status, respectively.

[0032] Optionally, the first signaling also includes at least one of band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

[0033] Optionally, the supported intra-band carrier aggregation Intra-band CA-support signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling have the same identifier.

[0034] Optionally, the supported intra-band uplink carrier aggregation Intra-band CA UL-support signaling and the supported intra-band downlink carrier aggregation Intra-band CA DL-support signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy have the same identifier.

[0035] In a second aspect, an embodiment of the present application provides another method for acquiring multi-carrier aggregation capability, which is performed by a network side device, and the method includes:

[0036] Receive a first signaling and a second signaling sent by a terminal device; wherein the first signaling is used to indicate the aggregation bandwidth level or aggregation capability information supported by the terminal device, and wherein the second signaling is used to indicate the aggregation bandwidth level supported by the terminal device; and wherein the aggregation bandwidth level reported in the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

[0037] Optional, where

[0038] The aggregate bandwidth level reported in the first signaling and the aggregate bandwidth level reported in the second signaling belong to the same fallback group;

[0039] or

[0040] The aggregate bandwidth level reported in the second signaling and the aggregate bandwidth level reported in the first signaling are in different fallback groups;

[0041] or

[0042] The fallback group to which the aggregate bandwidth level reported in the second signaling belongs is a subgroup of the fallback group to which the aggregate bandwidth level reported in the first signaling belongs.

[0043] Optionally, the method includes: parsing the first signaling, and determining an aggregated bandwidth level supported by the terminal device according to the parsing result.

[0044] Optionally, determining the aggregate bandwidth level supported by the terminal device according to the analysis result includes at least one of the following steps:

[0045] In response to being able to parse the first signaling, determining the aggregate bandwidth level or aggregation capability information supported by the terminal device according to the first signaling, and determining the aggregate bandwidth level supported by the terminal device according to the aggregate bandwidth level supported by the terminal device in the first signaling, or determining the aggregate bandwidth level supported by the terminal device according to the aggregation capability information in the first signaling;

[0046] or

[0047] In response to a failure to parse the first signaling, determining an aggregated bandwidth level supported by the terminal device according to the second signaling.

[0048] Optionally, at least one of the following steps is included:

[0049] In response to being able to parse the first signaling, ignoring the second signaling;

[0050] or

[0051] In response to a failure to parse the first signaling, the first signaling is ignored.

[0052] Optionally, the aggregation capability information is used to respectively obtain the aggregation status within the uplink and downlink frequency bands supported by the terminal device, or to obtain the aggregation status within the frequency band.

[0053] Optionally, the aggregation state includes at least one of the following:

[0054] Continuous type;

[0055] Non-continuous type;

[0056] Continuous and discontinuous.

[0057] Optionally, the first signaling is NR carrier aggregation bandwidth level CA-BandwidthClassNR-v17xy signaling, where xy is a sequence number.

[0058] Optionally, the first signaling includes at least one of NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL-NR-v17xy signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

[0059] Optionally, the CA-BandwidthClassNR-v17xy signaling, the CA-BandwidthClassDL-NR-v17xy signaling, the CA-BandwidthClassUL-NR-v17xy signaling, the BandParameters-v17xy signaling, the BandList-v17xy signaling, the BandCombination-v17xy signaling, the BandCombinationList-v17xy signaling, the

[0060] SupportedBandCombinationList-v17xy signaling has the same identifier.

[0061] Optionally, the first signaling also includes NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling and NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, or NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL1-NR-v17xy signaling and NR uplink carrier aggregation bandwidth level

[0062] CA-BandwidthClassUL2-NR-v17xy signaling.

[0063] Optionally, the first signaling also includes at least one of band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list supportedBandCombinationList-v17xy signaling.

[0064] Optionally, the NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling, the NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, the NR uplink carrier aggregation bandwidth level

[0065] CA-BandwidthClassUL1-NR-v17xy signaling, NR uplink carrier aggregation bandwidth class CA-BandwidthClassUL2-NR-v17xy signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list supportedBandCombinationList-v17xy signaling have the same identifier.

[0066] Optionally, the aggregation bandwidth level obtained according to the first signaling is one or more of extended aggregation bandwidth levels R, S, T, U, MA, MD, ME and MF.

[0067] Optionally, when the aggregate bandwidth level obtained according to the first signaling is one or more of R, S, T and U, the aggregate bandwidth level obtained according to the second signaling is F.

[0068] Optionally, when the aggregation bandwidth level obtained according to the first signaling is one or more of MA, MD, ME and MF, the aggregation bandwidth level obtained according to the second signaling is one of M, F, E, D or A.

[0069] Optionally, the first signaling includes: Intra-bandCA-support-v17xy signaling supporting intra-band carrier aggregation, and the Intra-bandCA-support-v17xy signaling is used to indicate the aggregation status within the uplink and downlink frequency bands supported by the terminal device.

[0070] Optionally, the first signaling includes: a combination of Intra-band CAUL-support-v17xy signaling supporting intra-band uplink carrier aggregation and Intra-band CADL-support-v17xy signaling supporting intra-band downlink carrier aggregation, and the Intra-band CAUL-support-v17xy signaling and Intra-band CADL-support-v17xy signaling are used to indicate the uplink carrier aggregation status and the downlink carrier aggregation status, respectively.

[0071] Optionally, the first signaling also includes at least one of band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

[0072] Optionally, the supported intra-band carrier aggregation Intra-band CA-support signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling have the same identifier.

[0073] Optionally, the supported intra-band uplink carrier aggregation Intra-band CA UL-support signaling and the supported intra-band downlink carrier aggregation Intra-band CA DL-support signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling have the same identifier.

[0074] In a third aspect, an embodiment of the present application provides a communication device, which has some or all of the functions of the terminal device in the method described in the first aspect above. For example, the functions of the communication device may have some or all of the functions in the embodiments of the present application, or may have the functions of implementing any one of the embodiments of the present application separately. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0075] In one implementation, the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is used to couple with the transceiver module and the processing module, and store the computer programs and data necessary for the communication device.

[0076] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory. In one implementation, the communication device includes:

[0077] A reporting module is used to report the aggregation bandwidth level or aggregation capability information supported by the terminal device to the network side device through a first signaling, and to report the aggregation bandwidth level supported by the terminal device to the network side device through a second signaling; wherein the aggregation bandwidth level reported in the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

[0078] In a fourth aspect, an embodiment of the present application provides another communication device, which has some or all of the functions of the network device in the method example described in the second aspect above, such as the functions of the communication device may have some or all of the functions in the embodiments of the present application, or may have the functions of implementing any one of the embodiments of the present application separately. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0079] In one implementation, the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is used to couple with the transceiver module and the processing module, and store the computer programs and data necessary for the communication device.

[0080] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory. In one implementation, the communication device includes:

[0081] A receiving module, used to receive a first signaling and a second signaling sent by a terminal device; wherein the first signaling is used to indicate the aggregation bandwidth level or aggregation capability information supported by the terminal device, and wherein the second signaling is used to indicate the aggregation bandwidth level supported by the terminal device; and wherein the aggregation bandwidth level reported in the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

[0082] In a fifth aspect, an embodiment of the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the first aspect is executed.

[0083] In a sixth aspect, an embodiment of the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the second aspect is executed.

[0084] In the seventh aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.

[0085] In an eighth aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.

[0086] In a ninth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.

[0087] In the tenth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.

[0088] In the eleventh aspect, an embodiment of the present application provides a multi-carrier aggregation capability reporting system, the system including the communication device described in the third aspect and the communication device described in the fourth aspect, or the system including the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system including the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system including the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0089] In a twelfth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the above-mentioned terminal device, and when the instructions are executed, the terminal device executes the method described in the first aspect.

[0090] In a thirteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used by the above-mentioned network device, and when the instructions are executed, the network device executes the method described in the above-mentioned second aspect.

[0091] In a fourteenth aspect, the present application also provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0092] In a fifteenth aspect, the present application also provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0093] In a sixteenth aspect, the present application provides a chip system, which includes at least one processor and an interface, for supporting a terminal device to implement the functions involved in the first aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the terminal device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0094] In the seventeenth aspect, the present application provides a chip system, which includes at least one processor and an interface, and is used to support the network device to implement the functions involved in the second aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, and the memory is used to store computer programs and data necessary for the network device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0095] In an eighteenth aspect, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0096] In a nineteenth aspect, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method described in the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0097] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.

[0098] Figure 1 It is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application;

[0099] Figure 2 It is a flowchart of a method for reporting multi-carrier aggregation capability provided in an embodiment of the present application;

[0100] Figure 3 It is a flowchart of a method for acquiring multi-carrier aggregation capability provided in an embodiment of the present application;

[0101] Figure 4 It is a structural diagram of a terminal device provided in an embodiment of the present application;

[0102] Figure 5 It is a structural diagram of a network device provided in an embodiment of the present application;

[0103] Figure 6 is a structural diagram of a communication device provided in an embodiment of the present application;

[0104] Figure 7 is a structural diagram of another communication device provided in an embodiment of the present application;

[0105] Figure 8 It is a schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0106] To facilitate understanding, the terms involved in this application are first introduced.

[0107] 1. Carrier Aggregation (CA)

[0108] Carrier aggregation is a technology that increases transmission bandwidth by aggregating multiple carriers of different frequencies (or the same frequency) into a wider spectrum. It can also aggregate some discontinuous spectrum fragments together to achieve the effect of increasing bandwidth. For example, a carrier bandwidth of 100MHz can only have one carrier. In order to pursue higher transmission rates, the application of carrier aggregation technology can establish a connection with the user equipment UE to provide data transmission. For example, two 100MHz bandwidth carriers are aggregated, and a total bandwidth of 200MHz can be obtained after aggregation. The data transmission speed is directly doubled compared to a single 100MHz carrier, which improves the usage and transmission rate.

[0109] In order to better understand a method for reporting multi-carrier aggregation capability disclosed in an embodiment of the present application, the communication system to which the embodiment of the present application is applicable is first described below.

[0110] See also Figure 1 , Figure 1 The present invention provides a schematic diagram of the architecture of a communication system. The communication system may include but is not limited to a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of the present application. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown includes a network device 101 and a terminal device 102 as an example.

[0111] It should be noted that the technical solutions of the embodiments of the present application can be applied to various communication systems. For example: long term evolution (LTE) system, fifth generation (5G) mobile communication system, 5G new radio (NR) system, or other future new mobile communication systems. It should also be noted that the side link in the embodiments of the present application can also be called a side link or a through link.

[0112] The network device 101 in the embodiment of the present application is an entity for transmitting or receiving signals on the network side. For example, the network device 101 may be an evolved NodeB (eNB), a transmission reception point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device. The network device provided in the embodiment of the present application may be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU may also be referred to as a control unit. The CU-DU structure may be used to split the protocol layer of the network device, such as the base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0113] The terminal device 102 in the embodiment of the present application is an entity for receiving or transmitting signals on the user side, such as a mobile phone. The terminal device can also be called a terminal device (terminal), a user equipment (UE), a mobile station (MS), a mobile terminal device (MT), etc. The terminal device can be a car with communication function, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote surgery (remote mediCAl surgery), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in smart city (smart city), a wireless terminal device in smart home (smart home), etc. The embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.

[0114] With the development of mobile communication technology, in order to meet the requirements of higher speeds, high frequency, large bandwidth, large-scale antenna technology and multi-carrier aggregation are increasingly becoming the development trend of wireless communication technology.

[0115] Multi-carrier aggregation technology is also widely used in the fifth-generation communication system, which is mainly divided into continuous carrier aggregation within a frequency band, non-continuous carrier aggregation within a frequency band, and carrier aggregation between frequency bands. For continuous carrier aggregation within a frequency band, RAN4 defines the aggregation bandwidth level of continuous carrier aggregation. In order to meet different application scenarios and different terminal capabilities, RAN4 further defines different fallback groups (FBG).

[0116] The network side will configure a default number of carriers supporting CA for all terminal devices, such as 8. However, some terminal devices cannot support the aggregation of so many carriers due to the limitation of their own terminal capabilities. In that case, the terminal devices need to select the number of carriers supporting other CAs, and can obtain the number of carriers supporting other CAs according to the fallback group.

[0117]

[0118] Table 1

[0119] Table 1 shows the aggregation bandwidth class and corresponding fallback group defined for millimeter wave FR2 continuous carrier aggregation. The bandwidth aggregation class NR CA bandwidth class is the range of the total bandwidth supported after carrier aggregation. Table 1 defines some bandwidth aggregation class codes (A, B, C, D, E, F, G, H, I, J, K, L, M, O, P, Q). The NR CA bandwidth class corresponds to the total bandwidth range Aggregated channel bandwidth after carrier aggregation according to the NR CA bandwidth class. Number of contiguous CC is the number of carriers used to achieve the Aggregated channel bandwidth. Because the bandwidth of each carrier can be different, the same total bandwidth may correspond to different numbers of carriers. The fallback group (FBG) is the fallback group corresponding to the NR CA bandwidth class. The definition of the FR2 fallback group is based on the maximum channel bandwidth that can be supported, and in each aggregation level, only one carrier bandwidth can be less than the maximum channel bandwidth supported. For example, the bandwidth aggregation level of FBG 1 is defined for the maximum channel bandwidth supported by a single carrier of 400MHz, the bandwidth aggregation level of FBG 2 is defined for the maximum channel bandwidth supported by a single carrier of 200MHz, and the bandwidth aggregation level of FBG 3 is defined for the maximum channel bandwidth supported by a single carrier of 100MHz. The fallback group corresponding to NR CA bandwidth class A can be FBG 1, FBG 2, FBG 3, or FBG 4, which is different from the fallback groups corresponding to other NR CA bandwidth classes.

[0120] The above-mentioned aggregation bandwidth level of continuous carrier aggregation of FR2 only requires that the terminal must be able to fall back to a lower-order aggregation bandwidth level in the same fallback group, and fallback between different fallback groups is not mandatory.

[0121]

[0122] Table 2

[0123] As shown in Table 2, with the continuous enhancement of terminal capabilities, operators have proposed adding larger aggregation bandwidth levels, such as adding aggregation bandwidth levels R, S, T, and U with maximum aggregation capabilities of 1000MHz, 1200MHz, 1400MHz, and 1600MHz respectively in fallback group FBG2.

[0124]

[0125] Table 3

[0126] As shown in Table 3, RAN4 is currently discussing the introduction of four Intra-band contiguous CA bandwidth classes for continuous carrier aggregation across fallback groups in FR2. For example, the aggregation bandwidth class M (8 100MHz carriers) in fallback group 3 and the aggregation bandwidth class A (1 200MHz carrier) in fallback group 2 are combined to form the aggregation bandwidth class MA (9 continuous carrier aggregation bandwidth is 1000MHz). There are other possible aggregation bandwidth classes MD, ME, MF, etc. The fallback groups corresponding to the aggregation bandwidth classes MA, MD, ME, and MF of continuous carrier aggregation are all FBG2-3.

[0127] Currently, the aggregation bandwidth level of the continuous carrier aggregation within the frequency band is reported by enumeration in the following information element (IE).

[0128]

[0129] q,...}

[0130] NR carrier aggregation bandwidth class signaling IE CA-BandwidthClassNR reserves extension bits, which can directly extend new aggregation bandwidth combinations R, S, T, U, MA, MD, ME, MF in the current IECA-BandwidthClassNR. The above IEs are used to report that UE supports new aggregation bandwidth levels.

[0131] As terminal capabilities continue to increase, operators have proposed adding larger aggregation bandwidth levels, such as adding aggregation bandwidth levels with maximum aggregation capabilities of 1000MHz, 1200MHz, 1400MHz and 1600MHz in fallback group FBG2. They have also proposed the need for aggregation bandwidth levels for continuous carrier aggregation across fallback groups.

[0132] If a new aggregate bandwidth combination is directly extended in the existing IE CA-BandwidthClassNR, it will cause network backward compatibility issues. For example, when the terminal reports its supported aggregate bandwidth R, S, T, U through the IE CA-BandwidthClassNR in the signaling supportedBandCombinationList, but some networks cannot recognize the newly extended aggregate bandwidth level in the IE CA-BandwidthClassNR, the network cannot configure the corresponding aggregate bandwidth for the terminal.

[0133] Specifically, if new aggregate bandwidth levels R, S, T, U, MA, MD, ME, MF are directly extended in the existing carrier aggregation bandwidth level signaling IE CA-BandwidthClassNR, it may cause network backward compatibility issues. For example, when the terminal reports its supported aggregate bandwidth levels R, S, T, U through the carrier aggregation bandwidth level signaling IECA-BandwidthClassNR in the supported band combination list SupportedBandCombinationList, if the network side device cannot recognize the newly extended aggregate bandwidth levels R, S, T, U in IECA-BandwidthClassNR, the network side device cannot configure the corresponding aggregate bandwidth for the terminal device.

[0134] It can be understood that the communication system described in the embodiment of the present application is for more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided in the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0135] The method and device for reporting multi-carrier aggregation capability provided in the present application are described in detail below with reference to the accompanying drawings.

[0136] See also Figure 2 , Figure 2 1 is a flow chart of a method for acquiring multi-carrier aggregation capability provided in an embodiment of the present application. The method is executed by a network side device. Figure 2 As shown, the method may include but is not limited to the following steps:

[0137] Step S201: Report the aggregation bandwidth level or aggregation capability information supported by the terminal device to the network side device through the first signaling, and report the aggregation bandwidth level supported by the terminal device to the network side device through the second signaling; wherein the aggregation bandwidth level reported in the second signaling is the fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

[0138] In a possible embodiment, the terminal device supports one or more of the aggregated bandwidth levels R, S, T, and U, and the terminal device sends a first signaling and a second signaling to the network side device. The first signaling is supportedBandCombinationList-v17xy, where the suffix -v17xy is optional and can be changed according to different Releases (for example, it may be called v18xy in Release18); and xy is a sequence number; the same below, no further description is given. The CA-BandwidthClassDL-NR-v17xy in the supportedBandCombinationList-v17xy is used to report that the terminal device supports one or more aggregated bandwidth levels of R, S, T, and U in the downlink; or the CA-BandwidthClassUL-NR-v17xy in the supportedBandCombinationList-v17xy is used to report that the terminal device supports any one or more aggregated bandwidth levels of R, S, T, and U in the uplink; wherein the suffix -v17xy is optional, which may change according to different Releases; and wherein xy is a sequence number; the same below, no further details are given. The second signaling is supportedBandCombinationList. The aggregated bandwidth level F supported by the terminal device in the downlink is reported through the CA-BandwidthClassDL-NR in the supportedBandCombinationList; or the aggregated bandwidth level F supported by the terminal device in the uplink is reported through the CA-BandwidthClassUL-NR in the supportedBandCombinationList.

[0139] In a possible embodiment, the terminal device supports aggregated bandwidth levels MA, MD, ME, MF, and the terminal device sends a first signaling and a second signaling to a network side device. The first signaling is supportedBandCombinationList-v17xy, where xy is a sequence number. The CA-BandwidthClassDL-NR-v17xy in the supportedBandCombinationList-v17xy is used to report that the terminal device supports any one or more aggregated bandwidth levels of MA, MD, ME, MF in the downlink; or the CA-BandwidthClassUL-NR-v17xy in the supportedBandCombinationList-v17xy is used to report that the terminal device supports any one or more aggregated bandwidth levels of MA, MD, ME, MF in the uplink. The second signaling is supportedBandCombinationList. The CA-BandwidthClassDL-NR in the supportedBandCombinationList reports the aggregation bandwidth level M or A supported by the terminal device in the downlink; or the CA-BandwidthClassUL-NR in the supportedBandCombinationList reports the aggregation bandwidth level M or A supported by the terminal device in the uplink.

[0140] In a possible embodiment, the terminal device supports aggregate bandwidth levels MA, MD, ME, and MF, and the terminal device sends a first signaling and a second signaling to a network side device. The first signaling is supportedBandCombinationList-v17xy, where xy is a sequence number. The downlink supports any one or more aggregate bandwidth levels of MA, MD, ME, and MF through CA-BandwidthClassDL1-NR-v17xy and CA-BandwidthClassDL2-NR-v17xy in the supportedBandCombinationList-v17xy signaling (for example, CA-BandwidthClassDL1-NR-v17xy reports M and CA-BandwidthClassDL2-NR-v17xy reports A, which means that the terminal supports aggregate bandwidth level MA) or through CA-BandwidthClassUL1-NR-v17xy and

[0141] When CA-BandwidthClassUL2-NR-v17xy reports that its uplink supports any one or more aggregation bandwidth levels of MA, MD, ME, MF, it reports its downlink support aggregation bandwidth level M or A through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling, or CA-BandwidthClassUL-NR reports its uplink support aggregation bandwidth level M or A, where the second signaling is supportedBandCombinationList.

[0142] Of course, in an embodiment of the present application, the first signaling and the second signaling may be different signalings, or, in another possible implementation, the first signaling and the second signaling may be different fields of the same signaling. In an embodiment of the present application, the network side device may not be able to recognize the newly added aggregate bandwidth level due to a backward version. In order to avoid the network side device being unable to recognize the newly extended aggregate bandwidth level, resulting in the network side device being unable to configure the corresponding aggregate bandwidth for the terminal device. The aggregate bandwidth level reported by the second signaling is the fallback aggregate bandwidth level of the aggregate bandwidth level reported by the first signaling. As shown in Table 2, in a possible embodiment, the aggregate bandwidth level reported by the first signaling is at least one of the following: R or S or T or U, then the aggregate bandwidth level reported by the second signaling is FBG2.

[0143] By implementing the embodiment of the present application, the aggregated bandwidth level supported by the terminal device can be reported according to the first signaling and the second signaling. In this way, it can be avoided that the network side device is incompatible with the aggregated bandwidth level included in the first signaling, thereby helping to avoid resource waste.

[0144] Optionally, the aggregate bandwidth level reported in the first signaling and the aggregate bandwidth level reported in the second signaling belong to the same fallback group; or

[0145] The aggregate bandwidth level reported in the second signaling and the aggregate bandwidth level reported in the first signaling are in different fallback groups;

[0146] or

[0147] The fallback group to which the aggregate bandwidth level reported in the second signaling belongs is a subgroup of the fallback group to which the aggregate bandwidth level reported in the first signaling belongs.

[0148] The terminal device reports the supportedBandCombinationList signaling through the second signaling, and reports the supportedBandCombinationList-v17xy signaling through the first signaling. When the terminal reports that its downlink supports one or more aggregated bandwidth levels of R, S, T, and U through CA-BandwidthClassDL-NR-v17xy in the supportedBandCombinationList-v17xy signaling, or reports that its uplink supports one or more aggregated bandwidth levels of R, S, T, and U through CA-BandwidthClassUL-NR-v17xy, it can only report its downlink support for aggregated bandwidth level F through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling, or report its uplink support for aggregated bandwidth level F through CA-BandwidthClassUL-NR. The R, S, T, U, and F all belong to fallback group 2.

[0149] In a possible embodiment, the aggregate bandwidth level reported in the first signaling is MA, and the aggregate bandwidth level reported in the second signaling is M or A. Aggregate bandwidth level MA belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level A belongs to fallback group 2 and fallback group 3. The fallback group to which aggregate bandwidth level M or aggregate bandwidth level A belongs is different from the fallback group to which aggregate bandwidth level MA belongs.

[0150] In a possible embodiment, the aggregate bandwidth level reported in the first signaling is MD, and the aggregate bandwidth level reported in the second signaling is M or D. Aggregate bandwidth levels MD belong to fallback groups 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level D belongs to fallback group 2. The fallback group to which aggregate bandwidth level M or aggregate bandwidth level D belongs is different from the fallback group to which aggregate bandwidth level MD belongs.

[0151] In a possible embodiment, the aggregate bandwidth level reported in the first signaling is ME, and the aggregate bandwidth level reported in the second signaling is M or E. Aggregate bandwidth level ME belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level E belongs to fallback group 2. The fallback group to which aggregate bandwidth level M or aggregate bandwidth level E belongs is different from the fallback group to which aggregate bandwidth level ME belongs.

[0152] In a possible embodiment, the aggregate bandwidth level reported in the first signaling is MF, and the aggregate bandwidth level reported in the second signaling is M or F. Aggregate bandwidth levels MF belong to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level F belongs to fallback group 2. The fallback group to which aggregate bandwidth level M or aggregate bandwidth level F belongs is different from the fallback group to which aggregate bandwidth level MF belongs.

[0153] In a possible embodiment, the terminal device needs to report the supportedBandCombinationList signaling through the second signaling, and report the supportedBandCombinationList-v17xy signaling through the first signaling. When the terminal device reports its downlink support for aggregate bandwidth level MA or reports its uplink support for aggregate bandwidth level MA through the first signaling, it can only report its downlink support for aggregate bandwidth level M or A through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling or report its uplink support for aggregate bandwidth level M or A through CA-BandwidthClassUL-NR. Aggregate bandwidth level MA belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level A belongs to fallback group 2 and fallback group 3. The fallback group 3 and fallback group 2 are both subgroups of fallback group 2-3, that is, the fallback group to which the aggregate bandwidth level M or aggregate bandwidth level A belongs is a subgroup of the fallback group to which the aggregate bandwidth level MA belongs.

[0154] In a possible embodiment, when the terminal device reports its downlink support for aggregate bandwidth level MD or reports its uplink support for aggregate bandwidth level MD through the first signaling, it can only report its downlink support for aggregate bandwidth level M or D through the CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling or report its uplink support for aggregate bandwidth level M or D through the CA-BandwidthClassUL-NR. Aggregate bandwidth level MD belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level D belongs to fallback group 2. Fallback group 3 and fallback group 2 are both subgroups of fallback group 2-3, that is, the fallback group to which aggregate bandwidth level M or aggregate bandwidth level D belongs is a subgroup of the fallback group to which aggregate bandwidth level MD belongs.

[0155] In a possible embodiment, when the terminal device reports its downlink support for aggregate bandwidth level ME or reports its uplink support for aggregate bandwidth level ME through the first signaling, it can only report its downlink support for aggregate bandwidth level M or E through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling or report its uplink support for aggregate bandwidth level M or E through CA-BandwidthClassUL-NR. Aggregate bandwidth level ME belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level E belongs to fallback group 2. Fallback group 3 and fallback group 2 are both subgroups of fallback group 2-3, that is, the fallback group to which aggregate bandwidth level M or aggregate bandwidth level E belongs is a subgroup of the fallback group to which aggregate bandwidth level ME belongs.

[0156] In a possible embodiment, when the terminal device reports its downlink support for aggregate bandwidth level MF or reports its uplink support for aggregate bandwidth level MF through the first signaling, it can only report its downlink support for aggregate bandwidth level M or F through the CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling or report its uplink support for aggregate bandwidth level M or F through the CA-BandwidthClassUL-NR. Aggregate bandwidth level MF belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level F belongs to fallback group 2. Fallback group 3 and fallback group 2 are both subgroups of fallback group 2-3, that is, the fallback group to which aggregate bandwidth level M or aggregate bandwidth level F belongs is a subgroup of the fallback group to which aggregate bandwidth level MF belongs.

[0157] Optionally, the aggregation capability information is used to report the aggregation status within the uplink and downlink frequency bands supported by the terminal device, respectively, or to report the aggregation status within the frequency band.

[0158] In an embodiment of the present application, the aggregation capability information is used to report the aggregation status within the uplink and downlink frequency bands supported by the terminal device, and the aggregation status includes: continuous, non-continuous, continuous and non-continuous. Multi-carrier aggregation technology is divided into intra-band carrier aggregation and inter-band carrier aggregation. Both continuous carrier aggregation and non-continuous carrier aggregation can be performed within the frequency band. In order to support different types of carrier aggregation, the terminal device needs to report the aggregation status within the supported uplink and downlink frequency bands, or report the aggregation status within the supported frequency band.

[0159] The uplink and downlink aggregation states may be uniformly configured by a signaling supporting intra-band carrier aggregation Intra-bandCA-support-v17xy, that is, the uplink and downlink carrier aggregation states must be consistent.

[0160] In a possible embodiment, the aggregation capability information is used to report that the aggregation states in the uplink and downlink frequency bands supported by the terminal device are both continuous, and the network side device indicates that the aggregation states in the uplink and downlink frequency bands of the terminal device are both continuous.

[0161] In a possible embodiment, the aggregation capability information is used to report that the aggregation states in the uplink and downlink frequency bands supported by the terminal device are both discontinuous, and the network side device indicates that the aggregation states in the uplink and downlink frequency bands of the terminal device are both discontinuous.

[0162] In a possible embodiment, the aggregation capability information is used to report whether the aggregation states in the uplink and downlink frequency bands supported by the terminal device are both continuous or discontinuous. The network side device then determines the aggregation states in the uplink and downlink frequency bands configured for the terminal device based on a configured judgment mechanism. If the network side device determines that the aggregation states need to be configured as discontinuous, the network side device indicates that the aggregation states in the uplink and downlink frequency bands of the terminal device are both discontinuous.

[0163] In a possible embodiment, the uplink and downlink aggregation states can be configured separately according to a combination of intra-band uplink carrier aggregation Intra-bandCAUL-support-v17xy signaling and intra-band downlink carrier aggregation Intra-bandCADL-support-v17xy signaling, that is, the uplink and downlink carrier aggregation states can be consistent or inconsistent.

[0164] In a possible embodiment, the aggregation capability information is used to report that the aggregation state in the uplink frequency band supported by the terminal device is continuous, and the aggregation state in the downlink frequency band is continuous, then the network side device indicates that the aggregation state in both the uplink and downlink frequency bands of the terminal device is continuous.

[0165] In a possible embodiment, the aggregation capability information is used to report that the aggregation state in the uplink frequency band supported by the terminal device is continuous, and the aggregation state in the downlink frequency band is discontinuous, then the network side device indicates that the aggregation state in the uplink frequency band of the terminal device is continuous, and the aggregation state in the downlink frequency band is discontinuous.

[0166] In a possible embodiment, the aggregation capability information is used to report that the aggregation state in the uplink frequency band supported by the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous, then the network side device indicates that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous.

[0167] In a possible embodiment, the aggregation capability information is used to report that the aggregation state in the uplink frequency band supported by the terminal device is discontinuous, and the aggregation state in the downlink frequency band is discontinuous, then the network side device indicates that the aggregation state in both the uplink and downlink frequency bands of the terminal device is discontinuous.

[0168] In a possible embodiment, the aggregation capability information is used to report that the aggregation state in the uplink frequency band supported by the terminal device is continuous and discontinuous, and the aggregation state in the downlink frequency band is discontinuous, then the network side device configures the aggregation state in the uplink frequency band for the terminal device according to the configured judgment mechanism, if the network side device determines that the aggregation state in the uplink frequency band needs to be configured as discontinuous, then the network side device indicates that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is discontinuous. If the network side device determines that the aggregation state in the uplink frequency band needs to be configured as continuous, then the network side device indicates that the aggregation states in both the uplink and downlink frequency bands of the terminal device are continuous.

[0169] In a possible embodiment, the aggregation capability information is used to report that the aggregation state in the uplink frequency band supported by the terminal device is continuous and discontinuous, and the aggregation state in the downlink frequency band is continuous. Then, the network side device configures the aggregation state in the uplink frequency band for the terminal device according to the configured judgment mechanism, indicating that the aggregation state in both the uplink and downlink frequency bands of the terminal device is continuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous.

[0170] In a possible embodiment, the aggregation capability information is used to report that the aggregation state in the uplink frequency band supported by the terminal device is continuous, and the aggregation state in the downlink frequency band is continuous and discontinuous. Then, the network side device configures the aggregation state in the downlink frequency band for the terminal device according to the configured judgment mechanism, indicating that the aggregation state in both the uplink and downlink frequency bands of the terminal device is continuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is continuous, and the aggregation state in the downlink frequency band is discontinuous.

[0171] In a possible embodiment, the aggregation capability information is used to report that the aggregation state in the uplink frequency band supported by the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous and discontinuous. Then, the network side device configures the aggregation state in the downlink frequency band for the terminal device according to the configured judgment mechanism, indicating that the aggregation state in both the uplink and downlink frequency bands of the terminal device is discontinuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous.

[0172] In a possible embodiment, the aggregation capability information is used to report that the aggregation state in the uplink frequency band supported by the terminal device is continuous and discontinuous, and the aggregation state in the downlink frequency band is continuous and discontinuous. Then, the network side device configures the aggregation state in the uplink and downlink frequency bands for the terminal device according to the configured judgment mechanism, indicating that the aggregation state in the uplink and downlink frequency bands of the terminal device are both continuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is continuous, and the aggregation state in the downlink frequency band is discontinuous, or indicating that the aggregation state in the uplink and downlink frequency bands of the terminal device are both discontinuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous.

[0173] Optionally, the aggregation state includes at least one of the following:

[0174] Continuous type;

[0175] Non-continuous type;

[0176] Continuous and discontinuous.

[0177] In the embodiment of the present application, the multi-carrier aggregation technology is divided into intra-band carrier aggregation and inter-band carrier aggregation. Both continuous carrier aggregation and non-continuous carrier aggregation can be performed within the frequency band. In order to support different types of carrier aggregation, the terminal device needs to report the aggregation status within the supported uplink and downlink frequency bands, or report the aggregation status within the supported frequency bands. Continuous carrier aggregation means that the aggregated carriers are close together, and non-continuous carrier aggregation means that there is a partition in the middle of the aggregated carriers, and they are not continuous carriers.

[0178] Optionally, the first signaling is NR carrier aggregation bandwidth level CA-BandwidthClassNR-v17xy signaling, where xy is a sequence number.

[0179] In the embodiment of the present application, the suffix -v17xy is optional, and may be changed according to different Releases (for example, it may be called v18xy in Release 18); and xy is a serial number.

[0180] Optionally, the first signaling includes at least one of NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL-NR-v17xy signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

[0181] In an embodiment of the present application, the aggregated bandwidth level supported by the terminal device is one or more of R, S, T, and U, which is reported by the first signaling. Among them, CA-BandwidthClassNR-v17xy is an upper-level signaling, and the upper-level signaling is included layer by layer by the following other signaling. The other signaling includes: CA-BandwidthClassDL-NR-v17xy signaling, used to report the aggregated bandwidth level supported by the terminal device in the downlink; CA-BandwidthClassUL-NR-v17xy signaling, used to report the aggregated bandwidth level supported by the terminal device in the uplink; BandParameters-v17xy signaling, used to carry the CA-BandwidthClassDL-NR-v17xy signaling and

[0182] CA-BandwidthClassUL-NR-v17xy signaling; BandList-v17xy signaling, used to report the frequency band list in carrier aggregation;

[0183] BandCombination-v17xy signaling is used to report the list of frequency band combinations in carrier aggregation; BandCombinationList-v17xy signaling is used to report the list of frequency band combinations in carrier aggregation; SupportedBandCombinationList-v17xy signaling is used to report the frequency band combinations supported by the terminal device.

[0184] In a possible implementation, the CA-BandwidthClassNR-v17xy signaling, the

[0185] The CA-BandwidthClassDL-NR-v17xy signaling, the CA-BandwidthClassUL-NR-v17xy signaling, the BandParameters-v17xy signaling, the BandList-v17xy signaling, the BandCombination-v17xy signaling, the BandCombinationList-v17xy signaling, and the SupportedBandCombinationList-v17xy signaling have corresponding identifiers. For example, these IEs have the same sequence number (that is, xy is consistent).

[0186] In some possible implementations, the uplink and downlink parameters may be indicated by the same IE. In other possible implementations, the uplink and downlink parameters may be indicated by the same IE, and the uplink and downlink use the same parameters. In some other possible implementations, the uplink and downlink parameters are indicated by different IEs respectively; for example: the first signaling includes NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling and NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, or, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL1-NR-v17xy signaling and NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL2-NR-v17xy signaling.

[0187] CA-BandwidthClassNR-v17xy is an upper signaling, which is included layer by layer by the following other signaling. The other signaling includes: NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling and NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, or NR uplink carrier aggregation bandwidth level

[0188] CA-BandwidthClassUL1-NR-v17xy signaling and NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL2-NR-v17xy signaling.

[0189] In the embodiment of the present application, the aggregated bandwidth level supported by the terminal device is one or more of MA, MD, ME, and MF, which is reported by the first signaling. The terminal device reports its downlink support for any one or more of MA, MD, ME, and MF through CA-BandwidthClassDL1-NR-v17xy signaling and CA-BandwidthClassDL2-NR-v17xy signaling in supportedBandCombinationList-v17xy; or, the terminal device reports its downlink support for any one or more of MA, MD, ME, and MF through CA-BandwidthClassUL1-NR-v17xy signaling and

[0190] CA-BandwidthClassUL2-NR-v17xy signaling reports that its uplink supports any one or multiple aggregate bandwidth levels of MA, MD, ME, and MF.

[0191] Optionally, the first signaling includes at least one of band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list supportedBandCombinationList-v17xy signaling.

[0192] CA-BandwidthClassNR-v17xy is an upper signaling, which is included layer by layer by the following other signaling. The other signaling includes: BandParameters-v17xy signaling, used to report frequency band parameters; BandList-v17xy signaling, used to report frequency band lists; BandCombination-v17xy signaling, used to report frequency band combinations; BandCombinationList-v17xy signaling, used to report frequency band combination lists; supportedBandCombinationList-v17xy signaling, used to report supported frequency band combination lists.

[0193] Optionally, the NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling, the NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, the NR uplink carrier aggregation bandwidth level

[0194] CA-BandwidthClassUL1-NR-v17xy signaling, NR uplink carrier aggregation bandwidth class CA-BandwidthClassUL2-NR-v17xy signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, supported band combination list supportedBandCombinationList-v17xy signaling have corresponding identifiers. For example, these IEs have the same sequence number (that is, xy is consistent).

[0195] Optionally, the aggregation bandwidth level reported in the first signaling is one or more of extended aggregation bandwidth levels R, S, T, U, MA, MD, ME and MF.

[0196] In this embodiment of the present application, the aggregation bandwidth level reported by the first signaling is one or more of the extended new aggregation bandwidth levels R, S, T, U, MA, MD, ME and MF.

[0197] Optionally, when the aggregate bandwidth level reported in the first signaling is one or more of R, S, T and U, the aggregate bandwidth level reported in the second signaling is F.

[0198] In an embodiment of the present application, the terminal device reports the supportedBandCombinationList signaling through the second signaling, and reports the supportedBandCombinationList-v17xy signaling through the first signaling. When the terminal reports that its downlink supports any one of the aggregation bandwidth levels of R, S, T, and U through CA-BandwidthClassDL-NR-v17xy in the supportedBandCombinationList-v17xy signaling, or reports that its uplink supports any one of the aggregation bandwidth levels of R, S, T, and U through CA-BandwidthClassUL-NR-v17xy, it can only report its downlink support for aggregation bandwidth level F through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling, or report its uplink support for aggregation bandwidth level F through CA-BandwidthClassUL-NR. Aggregation bandwidth levels R, S, T, U, and F all belong to fallback group 2.

[0199] Optionally, when the aggregate bandwidth level reported in the first signaling is one or more of MA, MD, ME and MF, the aggregate bandwidth level reported in the second signaling is one of M, F, E, D or A.

[0200] In the embodiment of the present application, the terminal device needs to report the supportedBandCombinationList signaling through the second signaling, and report the supportedBandCombinationList-v17xy signaling through the first signaling.

[0201] CA-BandwidthClassDL1-NR-v17xy and supportedBandCombinationList-v17xy in signaling

[0202] When CA-BandwidthClassDL2-NR-v17xy reports that it supports any one of the aggregate bandwidth levels MA, MD, ME, and MF in the downlink (for example, CA-BandwidthClassDL1-NR-v17xy reports M and CA-BandwidthClassDL2-NR-v17xy reports A, which means that the terminal device supports the aggregate bandwidth level MA), or when CA-BandwidthClassUL1-NR-v17xy and CA-BandwidthClassUL2-NR-v17xy report that it supports any one of the aggregate bandwidth levels MA, MD, ME, and MF in the uplink, it can only report its downlink supported aggregate bandwidth level M or F through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling, or report its uplink supported aggregate bandwidth level M or F through CA-BandwidthClassUL-NR. Aggregate bandwidth levels MA, MD, ME, and MF all belong to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level F belongs to fallback group 2. The fallback group 3 and the fallback group 2 are both subgroups of the fallback group 2-3, that is, the fallback group to which the aggregate bandwidth level M or the aggregate bandwidth level F belongs is a subgroup of the fallback group to which the aggregate bandwidth levels MA, MD, ME, and MF belong.

[0203] Optionally, the first signaling includes: Intra-bandCA-support-v17xy signaling supporting intra-band carrier aggregation, and the Intra-bandCA-support-v17xy signaling is used to indicate the aggregation status within the uplink and downlink frequency bands supported by the terminal device.

[0204] In the embodiment of the present application, the terminal device reports the supported carrier aggregation status of the uplink and downlink at the same time through the first signaling, that is, the uplink and downlink carrier aggregation status must be consistent, as shown in Table 4

[0205]

[0206] Table 4

[0207] In a possible embodiment, the state indicated by IE Intra-bandCA-support-v17xy is contiguous, and the uplink and downlink carrier aggregation states reported by the terminal device are both continuous. The network side device can configure the uplink and downlink of the terminal device as continuous carrier aggregation states.

[0208] In a possible embodiment, the state indicated by IE Intra-bandCA-support-v17xy is non-contiguous, and the uplink and downlink supported carrier aggregation states reported by the terminal device are both non-contiguous. The network side device can configure the uplink and downlink of the terminal device as non-contiguous carrier aggregation states.

[0209] In a possible embodiment, the state indicated by IE Intra-bandCA-support-v17xy is both, then the carrier aggregation state supported by the uplink and downlink reported by the terminal device can be either continuous or discontinuous. The network side device determines the aggregation state within the uplink and downlink frequency bands configured for the terminal device according to the configured judgment mechanism. If the network side device determines that it needs to be configured as continuous, the network side device indicates that the aggregation state within the uplink and downlink frequency bands of the terminal device is continuous; if the network side device determines that it needs to be configured as discontinuous, the network side device indicates that the aggregation state within the uplink and downlink frequency bands of the terminal device is discontinuous.

[0210] Optionally, the first signaling includes: a combination of Intra-band CAUL-support-v17xy signaling supporting intra-band uplink carrier aggregation and Intra-band CADL-support-v17xy signaling supporting intra-band downlink carrier aggregation, and the Intra-band CAUL-support-v17xy signaling and Intra-band CADL-support-v17xy signaling are used to indicate the uplink carrier aggregation status and the downlink carrier aggregation status, respectively.

[0211] CA-BandwidthClassNR-v17xy is an upper signaling, which is included layer by layer by the following other signaling. The other signaling includes: a combination of Intra-bandCAUL-support-v17xy signaling supporting intra-band uplink carrier aggregation and Intra-bandCADL-support-v17xy signaling supporting intra-band downlink carrier aggregation, and the Intra-bandCAUL-support-v17xy signaling and Intra-bandCADL-support-v17xy signaling are used to indicate the uplink carrier aggregation state and the downlink carrier aggregation state, respectively.

[0212] In the embodiment of the present application, the terminal device reports the supported carrier aggregation status of the uplink and downlink respectively through the first signaling, that is, the uplink and downlink carrier aggregation status may not be consistent, as shown in Table 5

[0213]

[0214] Table 5

[0215] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is contiguous, and the state indicated by IE Intra-bandCADL-support-v17xy is contiguous, then the uplink supported carrier aggregation state reported by the terminal device is continuous, and the downlink supported carrier aggregation state reported by the terminal device is continuous, and the network side device can configure the uplink and downlink of the terminal device as continuous carrier aggregation states.

[0216] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is contiguous, and the state indicated by IE Intra-bandCADL-support-v17xy is non-contiguous, then the carrier aggregation state supported by the uplink reported by the terminal device is continuous, and the carrier aggregation state supported by the downlink reported by the terminal device is non-contiguous, and the network side device can configure the uplink of the terminal device as a continuous carrier aggregation state and the downlink as a non-contiguous carrier aggregation state.

[0217] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is non-contiguous, and the state indicated by IE Intra-bandCADL-support-v17xy signaling is contiguous, then the uplink supported carrier aggregation state reported by the terminal device is non-continuous, and the downlink supported carrier aggregation state reported by the terminal device is continuous, and the network side device can configure the uplink of the terminal device as a non-continuous carrier aggregation state and the downlink as a continuous carrier aggregation state.

[0218] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is non-contiguous, and the state indicated by IE Intra-bandCADL-support-v17xy signaling is non-contiguous, then the uplink supported carrier aggregation state reported by the terminal device is non-contiguous, and the downlink supported carrier aggregation state reported by the terminal device is non-contiguous, and the network side device can configure the uplink and downlink of the terminal device as non-contiguous carrier aggregation states.

[0219] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is both, and the state indicated by IE Intra-bandCADL-support-v17xy signaling is contiguous, then the uplink supported carrier aggregation state reported by the terminal device is continuous and discontinuous, and the downlink supported carrier aggregation state reported by the terminal device is continuous, and the network side device can configure the uplink and downlink of the terminal device as a continuous carrier aggregation state, or configure the uplink of the terminal device as a discontinuous carrier aggregation state and the downlink as a continuous carrier aggregation state.

[0220] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is both, and the state indicated by IE Intra-bandCADL-support-v17xy signaling is non-contiguous, then the uplink supported carrier aggregation state reported by the terminal device is continuous and non-contiguous, and the downlink supported carrier aggregation state reported by the terminal device is non-contiguous, and the network side device may configure the uplink and downlink of the terminal device as non-continuous carrier aggregation states, or configure the uplink of the terminal device as a continuous carrier aggregation state and the downlink as a non-contiguous carrier aggregation state.

[0221] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is contiguous, and the state indicated by IE Intra-bandCADL-support-v17xy signaling is both, then the uplink supported carrier aggregation state reported by the terminal device is continuous, and the downlink supported carrier aggregation state reported by the terminal device is continuous and non-continuous, and the network side device can configure the uplink and downlink of the terminal device as a continuous carrier aggregation state, or configure the uplink of the terminal device as a continuous carrier aggregation state and the downlink as a non-continuous carrier aggregation state.

[0222] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is non-contiguous, and the state indicated by IE Intra-bandCADL-support-v17xy signaling is both, then the uplink supported carrier aggregation state reported by the terminal device is non-continuous, and the downlink supported carrier aggregation state reported by the terminal device is continuous and non-continuous, and the network side device may configure the uplink and downlink of the terminal device as non-continuous carrier aggregation states, or configure the uplink of the terminal device as a non-continuous carrier aggregation state and the downlink as a continuous carrier aggregation state.

[0223] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is both, and the state indicated by IE Intra-bandCADL-support-v17xy signaling is both, then the uplink supported carrier aggregation state reported by the terminal device is continuous and discontinuous, and the downlink supported carrier aggregation state reported by the terminal device is continuous and discontinuous, and the network side device may configure the uplink and downlink of the terminal device as discontinuous carrier aggregation states, or configure the uplink and downlink of the terminal device as continuous carrier aggregation states, or configure the uplink of the terminal device as a continuous carrier aggregation state and the downlink as a discontinuous carrier aggregation state, or configure the uplink of the terminal device as a discontinuous carrier aggregation state and the downlink as a continuous carrier aggregation state.

[0224] Optionally, the first signaling also includes at least one of band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

[0225] In the embodiment of the present application, CA-BandwidthClassNR-v17xy is an upper signaling, which is included layer by layer by the following other signaling. The other signaling includes: BandParameters-v17xy signaling, used to report frequency band parameters; BandList-v17xy signaling, used to report the frequency band list in carrier aggregation; BandCombination-v17xy signaling, used to report the frequency band combination list in carrier aggregation; BandCombinationList-v17xy signaling, used to report the list of frequency band combinations in carrier aggregation;

[0226] SupportedBandCombinationList-v17xy signaling is used to report the frequency band combinations supported by the terminal device.

[0227] Optionally, the supported intra-band carrier aggregation Intra-band CA-support signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling have the same identifier. For example, these IEs have the same sequence number (that is, xy is consistent).

[0228] Optionally, the supported intra-band uplink carrier aggregation Intra-band CAUL-support signaling and supported intra-band downlink carrier aggregation Intra-band CADL-support signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling have the same identifier. For example, these IEs have the same sequence number (that is, xy is consistent).

[0229] See also Figure 3 , Figure 3 1 is a flow chart of a method for acquiring multi-carrier aggregation capability provided in an embodiment of the present application. The method is executed by a network side device. Figure 3 As shown, the method may include but is not limited to the following steps:

[0230] Step S301: Receive a first signaling and a second signaling sent by a terminal device; wherein the first signaling is used to indicate an aggregation bandwidth level or aggregation capability information supported by the terminal device, and wherein the second signaling is used to indicate an aggregation bandwidth level supported by the terminal device; and wherein the aggregation bandwidth level reported by the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported by the first signaling.

[0231] In a possible embodiment, the terminal device supports one or more of the aggregated bandwidth levels R, S, T, and U, and the terminal device sends a first signaling and a second signaling to the network side device. The first signaling is supportedBandCombinationList-v17xy, where the suffix -v17xy is optional and can be changed according to different Releases (for example, it may be called v18xy in Release18); and xy is a sequence number; the same below, no further description is given. The CA-BandwidthClassDL-NR-v17xy in the supportedBandCombinationList-v17xy is used to report that the terminal device supports one or more aggregated bandwidth levels of R, S, T, and U in the downlink; or the CA-BandwidthClassUL-NR-v17xy in the supportedBandCombinationList-v17xy is used to report that the terminal device supports any one or more aggregated bandwidth levels of R, S, T, and U in the uplink; wherein the suffix -v17xy is optional, which may change according to different Releases; and wherein xy is a sequence number; the same below, no further details are given. The second signaling is supportedBandCombinationList. The aggregated bandwidth level F supported by the terminal device in the downlink is reported through the CA-BandwidthClassDL-NR in the supportedBandCombinationList; or the aggregated bandwidth level F supported by the terminal device in the uplink is reported through the CA-BandwidthClassUL-NR in the supportedBandCombinationList.

[0232] In a possible embodiment, the terminal device supports aggregated bandwidth levels MA, MD, ME, MF, and the terminal device sends a first signaling and a second signaling to a network side device. The first signaling is supportedBandCombinationList-v17xy, where xy is a sequence number. The CA-BandwidthClassDL-NR-v17xy in the supportedBandCombinationList-v17xy is used to report that the terminal device supports any one or more aggregated bandwidth levels of MA, MD, ME, MF in the downlink; or the CA-BandwidthClassUL-NR-v17xy in the supportedBandCombinationList-v17xy is used to report that the terminal device supports any one or more aggregated bandwidth levels of MA, MD, ME, MF in the uplink. The second signaling is supportedBandCombinationList. The CA-BandwidthClassDL-NR in the supportedBandCombinationList reports the aggregation bandwidth level M or A supported by the terminal device in the downlink; or the CA-BandwidthClassUL-NR in the supportedBandCombinationList reports the aggregation bandwidth level M or A supported by the terminal device in the uplink.

[0233] In a possible embodiment, the terminal device supports aggregate bandwidth levels MA, MD, ME, and MF, and the terminal device sends a first signaling and a second signaling to a network side device. The first signaling is supportedBandCombinationList-v17xy, where xy is a sequence number. The downlink supports any one or more aggregate bandwidth levels of MA, MD, ME, and MF through CA-BandwidthClassDL1-NR-v17xy and CA-BandwidthClassDL2-NR-v17xy in the supportedBandCombinationList-v17xy signaling (for example, CA-BandwidthClassDL1-NR-v17xy reports M and CA-BandwidthClassDL2-NR-v17xy reports A, which means that the terminal supports aggregate bandwidth level MA) or through CA-BandwidthClassUL1-NR-v17xy and

[0234] When CA-BandwidthClassUL2-NR-v17xy reports that its uplink supports any one or more aggregation bandwidth levels of MA, MD, ME, MF, it reports its downlink support aggregation bandwidth level M or A through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling, or CA-BandwidthClassUL-NR reports its uplink support aggregation bandwidth level M or A, where the second signaling is supportedBandCombinationList.

[0235] Of course, in an embodiment of the present application, the first signaling and the second signaling may be different signalings, or, in another possible implementation, the first signaling and the second signaling may be different fields of the same signaling. In an embodiment of the present application, the network side device may not be able to recognize the newly added aggregate bandwidth level due to a backward version. In order to avoid the network side device being unable to recognize the newly extended aggregate bandwidth level, resulting in the network side device being unable to configure the corresponding aggregate bandwidth for the terminal device. The aggregate bandwidth level reported by the second signaling is the fallback aggregate bandwidth level of the aggregate bandwidth level reported by the first signaling. As shown in Table 2, in a possible embodiment, the aggregate bandwidth level reported by the first signaling is at least one of the following: R or S or T or U, then the aggregate bandwidth level reported by the second signaling is FBG2.

[0236] By implementing the embodiment of the present application, the aggregated bandwidth level supported by the terminal device can be reported according to the first signaling and the second signaling. In this way, it can be avoided that the network side device is incompatible with the aggregated bandwidth level included in the first signaling, thereby helping to avoid resource waste.

[0237] Optionally, the aggregate bandwidth level reported in the first signaling and the aggregate bandwidth level reported in the second signaling belong to the same fallback group;

[0238] or

[0239] The aggregate bandwidth level reported in the second signaling and the aggregate bandwidth level reported in the first signaling are in different fallback groups;

[0240] or

[0241] The fallback group to which the aggregate bandwidth level reported in the second signaling belongs is a subgroup of the fallback group to which the aggregate bandwidth level reported in the first signaling belongs.

[0242] The terminal device reports the supportedBandCombinationList signaling through the second signaling, and reports the supportedBandCombinationList-v17xy signaling through the first signaling. When the terminal reports that its downlink supports one or more aggregated bandwidth levels of R, S, T, and U through CA-BandwidthClassDL-NR-v17xy in the supportedBandCombinationList-v17xy signaling, or reports that its uplink supports one or more aggregated bandwidth levels of R, S, T, and U through CA-BandwidthClassUL-NR-v17xy, it can only report its downlink support for aggregated bandwidth level F through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling, or report its uplink support for aggregated bandwidth level F through CA-BandwidthClassUL-NR. The R, S, T, U, and F all belong to fallback group 2.

[0243] In a possible embodiment, the aggregate bandwidth level reported in the first signaling is MA, and the aggregate bandwidth level reported in the second signaling is M or A. Aggregate bandwidth level MA belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level A belongs to fallback group 2 and fallback group 3. The fallback group to which aggregate bandwidth level M or aggregate bandwidth level A belongs is different from the fallback group to which aggregate bandwidth level MA belongs.

[0244] In a possible embodiment, the aggregate bandwidth level reported in the first signaling is MD, and the aggregate bandwidth level reported in the second signaling is M or D. Aggregate bandwidth levels MD belong to fallback groups 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level D belongs to fallback group 2. The fallback group to which aggregate bandwidth level M or aggregate bandwidth level D belongs is different from the fallback group to which aggregate bandwidth level MD belongs.

[0245] In a possible embodiment, the aggregate bandwidth level reported in the first signaling is ME, and the aggregate bandwidth level reported in the second signaling is M or E. Aggregate bandwidth level ME belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level E belongs to fallback group 2. The fallback group to which aggregate bandwidth level M or aggregate bandwidth level E belongs is different from the fallback group to which aggregate bandwidth level ME belongs.

[0246] In a possible embodiment, the aggregate bandwidth level reported in the first signaling is MF, and the aggregate bandwidth level reported in the second signaling is M or F. Aggregate bandwidth levels MF belong to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level F belongs to fallback group 2. The fallback group to which aggregate bandwidth level M or aggregate bandwidth level F belongs is different from the fallback group to which aggregate bandwidth level MF belongs.

[0247] In a possible embodiment, the terminal device needs to report the supportedBandCombinationList signaling through the second signaling, and report the supportedBandCombinationList-v17xy signaling through the first signaling. When the terminal device reports its downlink support for aggregate bandwidth level MA or reports its uplink support for aggregate bandwidth level MA through the first signaling, it can only report its downlink support for aggregate bandwidth level M or A through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling or report its uplink support for aggregate bandwidth level M or A through CA-BandwidthClassUL-NR. Aggregate bandwidth level MA belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level A belongs to fallback group 2 and fallback group 3. The fallback group 3 and fallback group 2 are both subgroups of fallback group 2-3, that is, the fallback group to which the aggregate bandwidth level M or aggregate bandwidth level A belongs is a subgroup of the fallback group to which the aggregate bandwidth level MA belongs.

[0248] In a possible embodiment, when the terminal device reports its downlink support for aggregate bandwidth level MD or reports its uplink support for aggregate bandwidth level MD through the first signaling, it can only report its downlink support for aggregate bandwidth level M or D through the CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling or report its uplink support for aggregate bandwidth level M or D through the CA-BandwidthClassUL-NR. Aggregate bandwidth level MD belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level D belongs to fallback group 2. Fallback group 3 and fallback group 2 are both subgroups of fallback group 2-3, that is, the fallback group to which aggregate bandwidth level M or aggregate bandwidth level D belongs is a subgroup of the fallback group to which aggregate bandwidth level MD belongs.

[0249] In a possible embodiment, when the terminal device reports its downlink support for aggregate bandwidth level ME or reports its uplink support for aggregate bandwidth level ME through the first signaling, it can only report its downlink support for aggregate bandwidth level M or E through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling or report its uplink support for aggregate bandwidth level M or E through CA-BandwidthClassUL-NR. Aggregate bandwidth level ME belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level E belongs to fallback group 2. Fallback group 3 and fallback group 2 are both subgroups of fallback group 2-3, that is, the fallback group to which aggregate bandwidth level M or aggregate bandwidth level E belongs is a subgroup of the fallback group to which aggregate bandwidth level ME belongs.

[0250] In a possible embodiment, when the terminal device reports its downlink support for aggregate bandwidth level MF or reports its uplink support for aggregate bandwidth level MF through the first signaling, it can only report its downlink support for aggregate bandwidth level M or F through the CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling or report its uplink support for aggregate bandwidth level M or F through the CA-BandwidthClassUL-NR. Aggregate bandwidth level MF belongs to fallback group 2-3, aggregate bandwidth level M belongs to fallback group 3, and aggregate bandwidth level F belongs to fallback group 2. Fallback group 3 and fallback group 2 are both subgroups of fallback group 2-3, that is, the fallback group to which aggregate bandwidth level M or aggregate bandwidth level F belongs is a subgroup of the fallback group to which aggregate bandwidth level MF belongs.

[0251] Optionally, the method includes: parsing the first signaling, and determining an aggregated bandwidth level supported by the terminal device according to the parsing result.

[0252] The configuration information of different network side devices is different. If the configuration information version of the network side device is updated in time and the first signaling can be parsed, the aggregation bandwidth level supported by the terminal device can be obtained by parsing the first signaling.

[0253] Optionally, determining the aggregate bandwidth level supported by the terminal device according to the analysis result includes at least one of the following steps:

[0254] In response to being able to parse the first signaling, determining the aggregate bandwidth level or aggregation capability information supported by the terminal device according to the first signaling, and determining the aggregate bandwidth level supported by the terminal device according to the aggregate bandwidth level supported by the terminal device in the first signaling, or determining the aggregate bandwidth level supported by the terminal device according to the aggregation capability information in the first signaling;

[0255] or

[0256] In response to a failure to parse the first signaling, determining an aggregated bandwidth level supported by the terminal device according to the second signaling.

[0257] In an embodiment of the present application, the configuration information of different network side devices is different. If the version information of the network side device is updated in time and the first signaling can be parsed, the aggregation bandwidth level or aggregation capability information supported by the terminal device can be determined according to the first signaling, and the aggregation bandwidth level supported by the terminal device can be determined according to the aggregation bandwidth level supported by the terminal device in the first signaling, or the aggregation bandwidth level supported by the terminal device can be determined according to the aggregation capability information in the first signaling.

[0258] In a possible embodiment, the network side device version update is relatively lagging, and cannot parse the first signaling, and thus cannot interpret the newly extended aggregate bandwidth level, and it is necessary to determine the aggregate bandwidth level supported by the terminal device based on the second signaling.

[0259] Optionally, at least one of the following steps is included:

[0260] In response to being able to parse the first signaling, ignoring the second signaling;

[0261] or

[0262] In response to a failure to parse the first signaling, the first signaling is ignored.

[0263] In an embodiment of the present application, the configuration information of different network side devices is different. If the version information of the network side device is updated in time and the first signaling can be parsed, the aggregation bandwidth level or aggregation capability information supported by the terminal device can be determined according to the first signaling, and the aggregation bandwidth level supported by the terminal device can be determined according to the aggregation bandwidth level supported by the terminal device in the first signaling, or the aggregation bandwidth level supported by the terminal device can be determined according to the aggregation capability information in the first signaling.

[0264] In a possible embodiment, the network side device version update is relatively lagging, and cannot parse the first signaling, and thus cannot interpret the newly extended aggregate bandwidth level, and it is necessary to determine the aggregate bandwidth level supported by the terminal device based on the second signaling.

[0265] Optionally, the aggregation capability information is used to respectively obtain the aggregation status within the uplink and downlink frequency bands supported by the terminal device, or to obtain the aggregation status within the frequency band.

[0266] In an embodiment of the present application, the aggregation capability information is used to report the aggregation status within the uplink and downlink frequency bands supported by the terminal device, and the aggregation status includes: continuous, non-continuous, continuous and non-continuous. Multi-carrier aggregation technology is divided into intra-band carrier aggregation and inter-band carrier aggregation. Both continuous carrier aggregation and non-continuous carrier aggregation can be performed within the frequency band. In order to support different types of carrier aggregation, the terminal device needs to report the aggregation status within the supported uplink and downlink frequency bands, or report the aggregation status within the supported frequency bands. If the network side can parse the first signaling, the aggregation status within the uplink and downlink frequency bands supported by the terminal device, or the aggregation status within the frequency band supported by the terminal device can be obtained according to the first signaling.

[0267] The uplink and downlink aggregation states may be uniformly configured by a signaling supporting intra-band carrier aggregation Intra-bandCA-support-v17xy, that is, the uplink and downlink carrier aggregation states must be consistent.

[0268] In a possible embodiment, the network side device obtains, based on the aggregation capability information, that the aggregation states in the uplink and downlink frequency bands supported by the terminal device are both continuous, and then the network side device indicates that the aggregation states in the uplink and downlink frequency bands of the terminal device are both continuous.

[0269] In a possible embodiment, the network side device obtains, based on the aggregation capability information, that the aggregation states in the uplink and downlink frequency bands supported by the terminal device are both discontinuous, and the network side device indicates that the aggregation states in the uplink and downlink frequency bands of the terminal device are both discontinuous.

[0270] In a possible embodiment, the network side device obtains, based on the aggregation capability information, whether the aggregation states in the uplink and downlink frequency bands supported by the terminal device are both continuous or discontinuous. The network side device then determines, based on the configured judgment mechanism, the aggregation states in the uplink and downlink frequency bands configured for the terminal device. If the network side device determines that the aggregation states need to be configured as discontinuous, the network side device indicates that the aggregation states in the uplink and downlink frequency bands of the terminal device are both discontinuous.

[0271] In a possible embodiment, the uplink and downlink aggregation states can be configured separately according to a combination of intra-band uplink carrier aggregation Intra-bandCAUL-support-v17xy signaling and intra-band downlink carrier aggregation Intra-bandCADL-support-v17xy signaling, that is, the uplink and downlink carrier aggregation states can be consistent or inconsistent.

[0272] In a possible embodiment, the network side device obtains, based on the aggregation capability information, that the aggregation state in the uplink frequency band supported by the terminal device is continuous, and the aggregation state in the downlink frequency band is continuous, then the network side device indicates that the aggregation state in both the uplink and downlink frequency bands of the terminal device is continuous.

[0273] In a possible embodiment, the network side device obtains, based on the aggregation capability information, that the aggregation state in the uplink frequency band supported by the terminal device is continuous, and the aggregation state in the downlink frequency band is discontinuous. Then, the network side device indicates that the aggregation state in the uplink frequency band of the terminal device is continuous, and the aggregation state in the downlink frequency band is discontinuous.

[0274] In a possible embodiment, the network side device obtains, based on the aggregation capability information, that the aggregation state in the uplink frequency band supported by the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous. Then, the network side device indicates that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous.

[0275] In a possible embodiment, the network side device obtains, based on the aggregation capability information, that the aggregation state in the uplink frequency band supported by the terminal device is discontinuous, and the aggregation state in the downlink frequency band is discontinuous, then the network side device indicates that the aggregation state in both the uplink and downlink frequency bands of the terminal device is discontinuous.

[0276] In a possible embodiment, the network side device obtains the aggregation state in the uplink frequency band supported by the terminal device according to the aggregation capability information as continuous and discontinuous, and the aggregation state in the downlink frequency band is discontinuous, then the network side device configures the aggregation state in the uplink frequency band for the terminal device according to the configured judgment mechanism, if the network side device determines that the aggregation state in the uplink frequency band needs to be configured as discontinuous, then the network side device indicates that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is discontinuous. If the network side device determines that the aggregation state in the uplink frequency band needs to be configured as continuous, then the network side device indicates that the aggregation states in both the uplink and downlink frequency bands of the terminal device are continuous.

[0277] In a possible embodiment, the network side device obtains, based on the aggregation capability information, that the aggregation state in the uplink frequency band supported by the terminal device is continuous and discontinuous, and the aggregation state in the downlink frequency band is continuous. Then, the network side device configures the aggregation state in the uplink frequency band for the terminal device according to the configured judgment mechanism, indicating that the aggregation state in both the uplink and downlink frequency bands of the terminal device is continuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous.

[0278] In a possible embodiment, the network side device obtains, based on the aggregation capability information, that the aggregation state in the uplink frequency band supported by the terminal device is continuous, and the aggregation state in the downlink frequency band is continuous and discontinuous. Then, the network side device configures the aggregation state in the downlink frequency band for the terminal device according to the configured judgment mechanism, indicating that the aggregation state in both the uplink and downlink frequency bands of the terminal device is continuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is continuous, and the aggregation state in the downlink frequency band is discontinuous.

[0279] In a possible embodiment, the network side device obtains, based on the aggregation capability information, that the aggregation state in the uplink frequency band supported by the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous and discontinuous. Then, the network side device configures the aggregation state in the downlink frequency band for the terminal device according to the configured judgment mechanism, indicating that the aggregation state in both the uplink and downlink frequency bands of the terminal device is discontinuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous.

[0280] In a possible embodiment, the network side device obtains the aggregation state in the uplink frequency band supported by the terminal device according to the aggregation capability information, which is continuous and discontinuous, and the aggregation state in the downlink frequency band is continuous and discontinuous. Then, the network side device configures the aggregation state in the uplink and downlink frequency bands for the terminal device according to the configured judgment mechanism, indicating that the aggregation state in the uplink and downlink frequency bands of the terminal device are both continuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is continuous, and the aggregation state in the downlink frequency band is discontinuous, or indicating that the aggregation state in the uplink and downlink frequency bands of the terminal device are both discontinuous, or indicating that the aggregation state in the uplink frequency band of the terminal device is discontinuous, and the aggregation state in the downlink frequency band is continuous.

[0281] Optionally, the aggregation state includes at least one of the following:

[0282] Continuous type;

[0283] Non-continuous type;

[0284] Continuous and discontinuous.

[0285] In the embodiment of the present application, the multi-carrier aggregation technology is divided into intra-band carrier aggregation and inter-band carrier aggregation. Both continuous carrier aggregation and non-continuous carrier aggregation can be performed within the frequency band. In order to support different types of carrier aggregation, the terminal device needs to report the aggregation status within the supported uplink and downlink frequency bands, or report the aggregation status within the supported frequency bands. Continuous carrier aggregation means that the aggregated carriers are close together, and non-continuous carrier aggregation means that there is a partition in the middle of the aggregated carriers, and they are not continuous carriers.

[0286] Optionally, the first signaling is NR carrier aggregation bandwidth level CA-BandwidthClassNR-v17xy signaling, where xy is a sequence number.

[0287] In the embodiment of the present application, the suffix -v17xy is optional, and may be changed according to different Releases (for example, it may be called v18xy in Release 18); and xy is a serial number.

[0288] Optionally, the first signaling includes at least one of NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL-NR-v17xy signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

[0289] In an embodiment of the present application, the aggregation bandwidth level supported by the terminal device is one or more of R, S, T, and U, which is obtained by the network side device according to the first signaling. Among them, CA-BandwidthClassNR-v17xy is an upper-level signaling, and the upper-level signaling is included layer by layer by the following other signaling. The other signaling includes: CA-BandwidthClassDL-NR-v17xy signaling, used to report the aggregation bandwidth level supported by the terminal device in the downlink; CA-BandwidthClassUL-NR-v17xy signaling, used to report the aggregation bandwidth level supported by the terminal device in the uplink; BandParameters-v17xy signaling, used to carry the CA-BandwidthClassDL-NR-v17xy signaling and CA-BandwidthClassUL-NR-v17xy signaling; BandList-v17xy signaling, used to report the frequency band list in carrier aggregation;

[0290] BandCombination-v17xy signaling is used to report the list of frequency band combinations in carrier aggregation; BandCombinationList-v17xy signaling is used to report the list of frequency band combinations in carrier aggregation; SupportedBandCombinationList-v17xy signaling is used to report the frequency band combinations supported by the terminal device.

[0291] In a possible implementation, the CA-BandwidthClassNR-v17xy signaling, the

[0292] The CA-BandwidthClassDL-NR-v17xy signaling, the CA-BandwidthClassUL-NR-v17xy signaling, the BandParameters-v17xy signaling, the BandList-v17xy signaling, the BandCombination-v17xy signaling, the BandCombinationList-v17xy signaling, and the SupportedBandCombinationList-v17xy signaling have corresponding identifiers. For example, these IEs have the same sequence number (that is, xy is consistent).

[0293] In an embodiment of the present application, CA-BandwidthClassNR-v17xy is an upper signaling, which is included layer by layer by the following other signaling. The other signaling includes: NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling and NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, or, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL1-NR-v17xy signaling and NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL2-NR-v17xy signaling.

[0294] In some possible implementations, uplink and downlink parameters may be indicated by the same IE. In other possible implementations, uplink and downlink parameters may be indicated by the same IE, and the uplink parameters and downlink parameters are the same. In some other possible implementations, the uplink and downlink parameters are indicated by different IEs respectively; for example: the first signaling includes NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling and NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, or, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL1-NR-v17xy signaling and NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL2-NR-v17xy signaling.

[0295] In the embodiment of the present application, the aggregated bandwidth level supported by the terminal device is one or more of MA, MD, ME, and MF, which is obtained by the network side device according to the first signaling. The network side device obtains the terminal downlink support for any one or more of MA, MD, ME, and MF through CA-BandwidthClassDL1-NR-v17xy signaling and CA-BandwidthClassDL2-NR-v17xy signaling in supportedBandCombinationList-v17xy; or, the network side device obtains the terminal downlink support for any one or more of MA, MD, ME, and MF through CA-BandwidthClassDL1-NR-v17xy signaling and CA-BandwidthClassDL2-NR-v17xy signaling in supportedBandCombinationList-v17xy;

[0296] CA-BandwidthClassUL1-NR-v17xy signaling and CA-BandwidthClassUL2-NR-v17xy signaling obtain the terminal uplink support for any one or multiple aggregation bandwidth levels of MA, MD, ME, MF.

[0297] Optionally, the first signaling also includes at least one of band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list supportedBandCombinationList-v17xy signaling.

[0298] In the embodiment of the present application, CA-BandwidthClassNR-v17xy is an upper signaling, which is included layer by layer by the following other signaling. The other signaling includes: BandParameters-v17xy signaling, used to report frequency band parameters; BandList-v17xy signaling, used to report frequency band lists; BandCombination-v17xy signaling, used to report frequency band combinations; BandCombinationList-v17xy signaling, used to report frequency band combination lists; supportedBandCombinationList-v17xy signaling, used to report supported frequency band combination lists.

[0299] Optionally, the NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling, the NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, the NR uplink carrier aggregation bandwidth level

[0300] CA-BandwidthClassUL1-NR-v17xy signaling, NR uplink carrier aggregation bandwidth class CA-BandwidthClassUL2-NR-v17xy signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, supported band combination list supportedBandCombinationList-v17xy have the same identifier. For example, these IEs have the same sequence number (that is, xy) and are consistent.

[0301] Optionally, the aggregation bandwidth level obtained according to the first signaling is one or more of extended aggregation bandwidth levels R, S, T, U, MA, MD, ME and MF.

[0302] In this embodiment of the present application, the aggregation bandwidth level obtained by the first signaling is one or more of the extended new aggregation bandwidth levels R, S, T, U, MA, MD, ME and MF.

[0303] Optionally, when the aggregate bandwidth level obtained according to the first signaling is one or more of R, S, T and U, the aggregate bandwidth level obtained according to the second signaling is F.

[0304] In an embodiment of the present application, the terminal device reports the supportedBandCombinationList signaling through the second signaling, and reports the supportedBandCombinationList-v17xy signaling through the first signaling. When the network side device can parse the first signaling, the terminal supports any one of the aggregation bandwidth levels R, S, T, and U in the downlink through CA-BandwidthClassDL-NR-v17xy in the supportedBandCombinationList-v17xy signaling, or the terminal supports any one of the aggregation bandwidth levels R, S, T, and U in the uplink through CA-BandwidthClassUL-NR-v17xy. When the network side device cannot parse the first signaling, it can only obtain the downlink support aggregation bandwidth level F of the terminal device through CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling, or obtain the uplink support aggregation bandwidth level F of the terminal device through CA-BandwidthClassUL-NR. Aggregation bandwidth levels R, S, T, U and F all belong to fallback group 2.

[0305] Optionally, when the aggregation bandwidth level obtained according to the first signaling is one or more of MA, MD, ME and MF, the aggregation bandwidth level obtained according to the second signaling is one of M, F, E, D or A.

[0306] In an embodiment of the present application, the network side device needs to obtain the supportedBandCombinationList signaling through the second signaling, and obtain the supportedBandCombinationList-v17xy signaling through the first signaling. When the network side device can parse the first signaling, the network side device obtains the terminal device's downlink support for any one of MA, MD, ME, and MF aggregation bandwidth levels through CA-BandwidthClassDL1-NR-v17xy and CA-BandwidthClassDL2-NR-v17xy in the supportedBandCombinationList-v17xy signaling (for example, CA-BandwidthClassDL1-NR-v17xy reports M and CA-BandwidthClassDL2-NR-v17xy reports A, which means that the terminal device supports the aggregation bandwidth level MA) or CA-BandwidthClassUL1-NR-v17xy and CA-BandwidthClassUL2-NR-v17xy report its uplink support for any one of MA, MD, ME, and MF. When the network-side device cannot parse the first signaling, it can only obtain the terminal's downlink support for aggregated bandwidth level M or F through the CA-BandwidthClassDL-NR in the supportedBandCombinationList signaling, or obtain the terminal's uplink support for aggregated bandwidth level M or F through CA-BandwidthClassUL-NR. The aggregated bandwidth levels MA, MD, ME, and MF all belong to fallback group 2-3, the aggregated bandwidth level M belongs to fallback group 3, and the aggregated bandwidth level F belongs to fallback group 2. The fallback group 3 and fallback group 2 are both subgroups of fallback group 2-3, that is, the fallback group to which the aggregated bandwidth level M or aggregated bandwidth level F belongs is a subgroup of the fallback group to which the aggregated bandwidth levels MA, MD, ME, and MF belong.

[0307] Optionally, the first signaling includes: Intra-bandCA-support-v17xy signaling supporting intra-band carrier aggregation, and the Intra-bandCA-support-v17xy signaling is used to indicate the aggregation status within the uplink and downlink frequency bands supported by the terminal device.

[0308] In the embodiment of the present application, the terminal device reports the supported carrier aggregation status of the uplink and downlink at the same time through the first signaling, that is, the uplink and downlink carrier aggregation status must be consistent, as shown in Table 4. In a possible embodiment, the state indicated by IEIntra-bandCA-support-v17xy is continuous, then the uplink and downlink supported carrier aggregation states obtained by the network side device are both continuous. The network side device can configure the uplink and downlink of the terminal device as continuous carrier aggregation states.

[0309] In a possible embodiment, the state indicated by IE Intra-bandCA-support-v17xy is non-contiguous, and the carrier aggregation states supported by the uplink and downlink acquired by the network side device are both non-contiguous. The network side device can configure the uplink and downlink of the terminal device to non-contiguous carrier aggregation states.

[0310] In a possible embodiment, the state indicated by IE Intra-bandCA-support-v17xy is both, then the carrier aggregation state supported by the uplink and downlink obtained by the network side device can be either continuous or discontinuous. The network side device determines the aggregation state within the uplink and downlink frequency bands configured for the terminal device according to the configured judgment mechanism. If the network side device determines that it needs to be configured as continuous, the network side device indicates that the aggregation state within the uplink and downlink frequency bands of the terminal device is continuous; if the network side device determines that it needs to be configured as discontinuous, the network side device indicates that the aggregation state within the uplink and downlink frequency bands of the terminal device is discontinuous.

[0311] Optionally, the first signaling includes: a combination of Intra-band CAUL-support-v17xy signaling supporting intra-band uplink carrier aggregation and Intra-band CADL-support-v17xy signaling supporting intra-band downlink carrier aggregation, and the Intra-band CAUL-support-v17xy signaling and Intra-band CADL-support-v17xy signaling are used to indicate the uplink carrier aggregation status and the downlink carrier aggregation status, respectively.

[0312] In the embodiment of the present application, CA-BandwidthClassNR-v17xy is an upper signaling, which is included layer by layer by the following other signaling. Other signaling includes: a combination of Intra-bandCAUL-support-v17xy signaling supporting intra-band uplink carrier aggregation and Intra-bandCADL-support-v17xy signaling supporting intra-band downlink carrier aggregation, and the Intra-bandCAUL-support-v17xy signaling and Intra-bandCADL-support-v17xy signaling are used to indicate the uplink carrier aggregation state and the downlink carrier aggregation state, respectively.

[0313] In an embodiment of the present application, the network side device obtains the supported carrier aggregation status of the uplink and downlink respectively through the first signaling, that is, the uplink and downlink carrier aggregation status may not be consistent, as shown in Table 5. In a possible embodiment, the state indicated by IEIntra-bandCAUL-support-v17xy is contiguous, and the state indicated by the Intra-bandCADL-support-v17xy signaling is contiguous. Then, the uplink supported carrier aggregation state obtained by the network side device is continuous, and the downlink supported carrier aggregation state obtained by the network side device is continuous. The network side device can configure the uplink and downlink of the terminal device as continuous carrier aggregation states.

[0314] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is contiguous, and the state indicated by the Intra-bandCADL-support-v17xy signaling is non-contiguous, then the uplink supported carrier aggregation state obtained by the network side device is continuous, and the downlink supported carrier aggregation state obtained by the network side device is non-contiguous, and the network side device can configure the uplink of the terminal device as a continuous carrier aggregation state and the downlink configuration as a non-contiguous carrier aggregation state.

[0315] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is non-contiguous, and the state indicated by the Intra-bandCADL-support-v17xy signaling is contiguous. The uplink supported carrier aggregation state obtained by the network side device is non-continuous, and the downlink supported carrier aggregation state obtained by the network side device is continuous. The network side device can configure the uplink of the terminal device as a non-continuous carrier aggregation state and the downlink configuration as a continuous carrier aggregation state.

[0316] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is non-contiguous, and the state indicated by the Intra-bandCADL-support-v17xy signaling is non-contiguous, then the uplink supported carrier aggregation state obtained by the network side device is non-contiguous, and the downlink supported carrier aggregation state obtained by the network side device is non-contiguous, and the network side device can configure the uplink and downlink of the terminal device as non-contiguous carrier aggregation states.

[0317] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is both, and the state indicated by the Intra-bandCADL-support-v17xy signaling is contiguous, then the uplink supported carrier aggregation state obtained by the network side device is continuous and discontinuous, and the downlink supported carrier aggregation state obtained by the network side device is continuous, and the network side device can configure the uplink and downlink of the terminal device as a continuous carrier aggregation state, or configure the uplink of the terminal device as a discontinuous carrier aggregation state, and the downlink configuration as a continuous carrier aggregation state.

[0318] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is both, and the state indicated by the Intra-bandCADL-support-v17xy signaling is non-contiguous, then the uplink supported carrier aggregation state obtained by the network side device is continuous and non-contiguous, and the downlink supported carrier aggregation state obtained by the network side device is non-contiguous. The network side device can configure the uplink and downlink of the terminal device as non-continuous carrier aggregation states, or configure the uplink of the terminal device as a continuous carrier aggregation state and the downlink as a non-contiguous carrier aggregation state.

[0319] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is contiguous, and the state indicated by the Intra-bandCADL-support-v17xy signaling is both, then the uplink supported carrier aggregation state obtained by the network side device is continuous, and the downlink supported carrier aggregation state obtained by the network side device is continuous and discontinuous, and the network side device may configure the uplink and downlink of the terminal device as a continuous carrier aggregation state, or configure the uplink of the terminal device as a continuous carrier aggregation state and the downlink as a discontinuous carrier aggregation state.

[0320] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is non-contiguous, and the state indicated by the Intra-bandCADL-support-v17xy signaling is both. Then the uplink supported carrier aggregation state obtained by the network side device is non-continuous, and the downlink supported carrier aggregation state obtained by the network side device is continuous and non-continuous. The network side device can configure the uplink and downlink of the terminal device as non-continuous carrier aggregation state, or configure the uplink of the terminal device as non-continuous carrier aggregation state and the downlink as continuous carrier aggregation state.

[0321] In a possible embodiment, the state indicated by IE Intra-bandCAUL-support-v17xy is both, and the state indicated by the Intra-bandCADL-support-v17xy signaling is both, then the uplink supported carrier aggregation state obtained by the network side device is continuous and discontinuous, and the downlink supported carrier aggregation state obtained by the network side device is continuous and discontinuous, and the network side device may configure the uplink and downlink of the terminal device as a discontinuous carrier aggregation state, or configure the uplink and downlink of the terminal device as a continuous carrier aggregation state, or configure the uplink of the terminal device as a continuous carrier aggregation state and the downlink as a discontinuous carrier aggregation state, or configure the uplink of the terminal device as a discontinuous carrier aggregation state and the downlink as a continuous carrier aggregation state.

[0322] Optionally, the first signaling also includes at least one of band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

[0323] In the embodiment of the present application, CA-BandwidthClassNR-v17xy is an upper signaling, which is included layer by layer by the following other signaling. Other signaling includes: BandParameters-v17xy signaling, used to report frequency band parameters; BandList-v17xy signaling, used to report the frequency band list in carrier aggregation; BandCombination-v17xy signaling, used to report the frequency band combination list in carrier aggregation; BandCombinationList-v17xy signaling, used to report the frequency band combination list in carrier aggregation;

[0324] SupportedBandCombinationList-v17xy signaling is used to report the frequency band combinations supported by the terminal device.

[0325] Optionally, the supported intra-band carrier aggregation Intra-band CA-support signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy have the same identifier. For example, these IEs have the same sequence number (that is, xy is consistent).

[0326] Optionally, the supported intra-band uplink carrier aggregation Intra-band CAUL-support signaling and the supported intra-band downlink carrier aggregation Intra-band CADL-support signaling, band parameter BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy have the same identifier. For example, these IEs have the same sequence number (that is, xy is consistent).

[0327] In the embodiments provided by the present application, the methods provided by the embodiments of the present application are introduced from the perspectives of network equipment and terminal equipment, respectively. In order to implement the functions in the methods provided by the embodiments of the present application, the network equipment and the terminal equipment may include hardware structures and software modules, and the functions are implemented in the form of hardware structures, software modules, or hardware structures plus software modules. A certain function in the functions may be executed in the form of hardware structures, software modules, or hardware structures plus software modules.

[0328] See also Figure 6 , is a structural diagram of a communication device 60 provided in an embodiment of the present application. Figure 6 The communication device 60 shown may include a transceiver module 601 and a processing module 602. The transceiver module 601 may include a sending module and / or a receiving module, the sending module is used to implement a sending function, the receiving module is used to implement a receiving function, and the transceiver module 601 may implement a sending function and / or a receiving function.

[0329] The communication device 60 may be a terminal device (such as the terminal device in the aforementioned method embodiment), or a device in a terminal device, or a device that can be used in conjunction with a terminal device. Alternatively, the communication device 60 may be a network device, or a device in a network device, or a device that can be used in conjunction with a network device.

[0330] The communication device 60 is a terminal device, such as Figure 4 As shown, the terminal device 40 includes:

[0331] The reporting module 410 is used to report the aggregation bandwidth level or aggregation capability information supported by the terminal device to the network side device through the first signaling, and to report the aggregation bandwidth level supported by the terminal device to the network side device through the second signaling; wherein the aggregation bandwidth level reported in the second signaling is the fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

[0332] The communication device 60 is a network device, such as Figure 5 As shown, the network device 50 includes:

[0333] The receiving module 510 is used to receive a first signaling and a second signaling sent by a terminal device; wherein the first signaling is used to indicate the aggregation bandwidth level or aggregation capability information supported by the terminal device, and wherein the second signaling is used to indicate the aggregation bandwidth level supported by the terminal device; and wherein the aggregation bandwidth level reported by the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported by the first signaling.

[0334] See also Figure 7 , Figure 7 : is a schematic diagram of the structure of another communication device 70 provided in an embodiment of the present application. The communication device 70 can be a network device, or a terminal device (such as the terminal device in the aforementioned method embodiment), or a chip, a chip system, or a processor that supports the network device to implement the aforementioned method, or a chip, a chip system, or a processor that supports the terminal device to implement the aforementioned method. The device can be used to implement the method described in the aforementioned method embodiment, and the details can be referred to the description in the aforementioned method embodiment.

[0335] The communication device 70 may include one or more processors 701. The processor 701 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and communication data, and the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.

[0336] Optionally, the communication device 70 may further include one or more memories 702, on which a computer program 703 may be stored, and the processor 701 executes the computer program 703 so that the communication device 70 performs the method described in the above method embodiment. Optionally, data may also be stored in the memory 702. The communication device 70 and the memory 702 may be provided separately or integrated together.

[0337] Optionally, the communication device 70 may further include a transceiver 704 and an antenna 705. The transceiver 704 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function. The transceiver 704 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

[0338] Optionally, the communication device 70 may further include one or more interface circuits 706. The interface circuit 706 is used to receive code instructions and transmit them to the processor 701. The processor 701 runs the code instructions to enable the communication device 70 to perform the method described in the above method embodiment.

[0339] The communication device 70 is a terminal device (such as the terminal device in the aforementioned method embodiment): the transceiver 704 is used to execute the steps of reporting the aggregation bandwidth level or aggregation capability information supported by the terminal device to the network side device through the first signaling, and reporting the aggregation bandwidth level supported by the terminal device to the network side device through the second signaling.

[0340] The communication device 70 is a network device: the transceiver 704 is used to perform Figure 2 Step S201 in .

[0341] In one implementation, the processor 701 may include a transceiver for implementing the receiving and sending functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0342] In one implementation, the processor 701 may store a computer program 703, which runs on the processor 701 and enables the communication device 70 to perform the method described in the above method embodiment. The computer program 703 may be fixed in the processor 701, in which case the processor 701 may be implemented by hardware.

[0343] In one implementation, the communication device 70 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiment. The processor and transceiver described in the present application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channelmetal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0344] The communication device described in the above embodiments may be a network device or a terminal device (such as the terminal device in the above method embodiment), but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited thereto. Figure 7 The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0345] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0346] (2) having a set of one or more ICs, and optionally, the IC set may also include a storage component for storing data and computer programs;

[0347] (3) ASIC, such as modem;

[0348] (4) Modules that can be embedded in other devices;

[0349] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0350] (6)Others

[0351] For the case where the communication device may be a chip or a chip system, see Figure 8 Schematic diagram of the chip structure shown. Figure 8 The chip shown includes a processor 801 and an interface 802. The number of the processor 801 may be one or more, and the number of the interface 802 may be multiple.

[0352] Optionally, the chip further includes a memory 803, and the memory 803 is used to store necessary computer programs and data.

[0353] Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present application.

[0354] The embodiment of the present application also provides a system for reporting multi-carrier aggregation capability, the system comprising the aforementioned Figure 5 In the embodiment, the communication device as the terminal device (such as the terminal device in the aforementioned method embodiment) and the communication device as the network device, or the system includes the aforementioned Figure 7 The communication device in the embodiment serves as a terminal device (such as the terminal device in the aforementioned method embodiment) and the communication device serves as a network device.

[0355] The present application also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0356] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0357] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0358] A person skilled in the art may understand that the various numerical numbers such as first and second involved in the present application are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application, and also indicate the order of precedence.

[0359] At least one in the present application can also be described as one or more, and a plurality can be two, three, four or more, which is not limited in the present application. In the embodiments of the present application, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no order of precedence or size between the technical features described by the "first", "second", "third", "A", "B", "C" and "D".

[0360] The corresponding relationships shown in each table in the present application can be configured or predefined. The values ​​of the information in each table are only examples and can be configured as other values, which are not limited by the present application. When configuring the corresponding relationship between the information and each parameter, it is not necessarily required to configure all the corresponding relationships illustrated in each table. For example, in the table in the present application, the corresponding relationships shown in some rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values ​​or representations of the parameters can also be other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.

[0361] The predefined in the present application may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

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

[0363] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0364] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for reporting multi-carrier aggregation capability, characterized in that: Executed by a terminal device, the method includes: The aggregation bandwidth level or aggregation capability information supported by the terminal device is reported to the network side device through the first signaling, and the aggregation bandwidth level supported by the terminal device is reported to the network side device through the second signaling; wherein the aggregation bandwidth level reported by the second signaling is the fallback aggregation bandwidth level of the aggregation bandwidth level reported by the first signaling; the first signaling is the NR carrier aggregation bandwidth level CA-BandwidthClassNR-v17xy signaling, wherein xy is the sequence number.

2. The method according to claim 1, characterized in that in, The aggregate bandwidth level reported in the first signaling and the aggregate bandwidth level reported in the second signaling belong to the same fallback group; or The aggregate bandwidth level reported in the second signaling and the aggregate bandwidth level reported in the first signaling are in different fallback groups; or The fallback group to which the aggregate bandwidth level reported in the second signaling belongs is a subgroup of the fallback group to which the aggregate bandwidth level reported in the first signaling belongs.

3. The method according to claim 1, characterized in that in, The aggregation capability information is used to report the aggregation status within the uplink and downlink frequency bands supported by the terminal device, or to report the aggregation status within the frequency band.

4. The method according to claim 3, characterized in that The aggregation state includes at least one of the following: Continuous type; Non-continuous type; Continuous and discontinuous.

5. The method according to claim 1, characterized in that The first signaling includes at least one of NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL-NR-v17xy signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

6. The method according to claim 5, characterized in that The CA-BandwidthClassNR-v17xy signaling, the CA-BandwidthClassDL-NR-v17xy signaling, the CA-BandwidthClassUL-NR-v17xy signaling, the BandParameters-v17xy signaling, the BandList-v17xy signaling, the BandCombination-v17xy signaling, the BandCombinationList-v17xy signaling, and the SupportedBandCombinationList-v17xy signaling have the same identifier.

7. The method according to claim 1, characterized in that The first signaling also includes NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling and NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, or NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL1-NR-v17xy signaling and NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL2-NR-v17xy signaling.

8. The method according to claim 7, characterized in that The first signaling also includes at least one of a band parameter BandParameters-v17xy signaling, a band list BandList-v17xy signaling, a band combination BandCombination-v17xy signaling, a band combination list BandCombinationList-v17xy signaling, and a supported band combination list supportedBandCombinationList-v17xy signaling.

9. The method according to claim 8, characterized in that The NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling, NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL1-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL2-NR-v17xy signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list supportedBandCombinationList-v17xy have the same identifier.

10. The method according to claim 1, characterized in that When the aggregate bandwidth level reported in the first signaling is one or more of R, S, T and U, the aggregate bandwidth level reported in the second signaling is F.

11. The method according to claim 1, characterized in that When the aggregate bandwidth level reported in the first signaling is one or more of MA, MD, ME and MF, the aggregate bandwidth level reported in the second signaling is one of M, F, E, D or A.

12. The method according to claim 3, characterized in that The first signaling includes: Intra-band CA-support-v17xy signaling supporting intra-band carrier aggregation, and the Intra-band CA-support-v17xy signaling is used to indicate the aggregation status within the uplink and downlink frequency bands supported by the terminal device.

13. The method according to claim 3 or 12, characterized in that: The first signaling includes: a combination of Intra-band CAUL-support-v17xy signaling supporting intra-band uplink carrier aggregation and Intra-band CADL-support-v17xy signaling supporting intra-band downlink carrier aggregation, and the Intra-band CAUL-support-v17xy signaling and Intra-band CADL-support-v17xy signaling are used to indicate the uplink carrier aggregation status and the downlink carrier aggregation status, respectively.

14. The method according to claim 12 or 13, characterized in that The first signaling also includes at least one of a band parameter BandParameters-v17xy signaling, a band list BandList-v17xy signaling, a band combination BandCombination-v17xy signaling, a band combination list BandCombinationList-v17xy signaling, and a supported band combination list SupportedBandCombinationList-v17xy signaling.

15. The method according to claim 14, characterized in that The support for intra-band carrier aggregation Intra-band CA-support signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, support band combination list SupportedBandCombinationList-v17xy has the same identification.

16. The method according to claim 14, characterized in that The intra-band uplink carrier aggregation Intra-band CA UL-support signaling and the intra-band downlink carrier aggregation Intra-band CA DL-support signaling, the band parameters BandParameters-v17xy signaling, the band list BandList-v17xy signaling, the band combination BandCombination-v17xy signaling, the band combination list BandCombinationList-v17xy signaling, and the supported band combination list SupportedBandCombinationList-v17xy have the same identifier.

17. A method for reporting multi-carrier aggregation capability, characterized in that: Executed by a terminal device, the method includes: The aggregation bandwidth level or aggregation capability information supported by the terminal device is reported to the network side device through the first signaling, and the aggregation bandwidth level supported by the terminal device is reported to the network side device through the second signaling; wherein the aggregation bandwidth level reported in the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

18. A method for acquiring multi-carrier aggregation capability, characterized in that: The method is performed by a network side device and includes: Receive a first signaling and a second signaling sent by a terminal device; wherein the first signaling is used to indicate the aggregation bandwidth level or aggregation capability information supported by the terminal device, and wherein the second signaling is used to indicate the aggregation bandwidth level supported by the terminal device; wherein the aggregation bandwidth level reported by the second signaling is the fallback aggregation bandwidth level of the aggregation bandwidth level reported by the first signaling; and the first signaling is the NR carrier aggregation bandwidth level CA-BandwidthClassNR-v17xy signaling, wherein xy is a sequence number.

19. The method according to claim 18, characterized in that in, The aggregate bandwidth level reported in the first signaling and the aggregate bandwidth level reported in the second signaling belong to the same fallback group; or The aggregate bandwidth level reported in the second signaling and the aggregate bandwidth level reported in the first signaling are in different fallback groups; or The fallback group to which the aggregate bandwidth level reported in the second signaling belongs is a subgroup of the fallback group to which the aggregate bandwidth level reported in the first signaling belongs.

20. The method of claim 18, wherein: The method includes: parsing the first signaling, and determining the aggregation bandwidth level supported by the terminal device according to the parsing result.

21. The method of claim 20, wherein: Determining the aggregated bandwidth level supported by the terminal device according to the analysis result includes at least one of the following steps: In response to being able to parse the first signaling, determining the aggregate bandwidth level or aggregation capability information supported by the terminal device according to the first signaling, and determining the aggregate bandwidth level supported by the terminal device according to the aggregate bandwidth level supported by the terminal device in the first signaling, or determining the aggregate bandwidth level supported by the terminal device according to the aggregation capability information in the first signaling; or In response to a failure to parse the first signaling, determining an aggregated bandwidth level supported by the terminal device according to the second signaling.

22. The method of claim 20, wherein: Include at least one of the following steps: In response to being able to parse the first signaling, ignoring the second signaling; or In response to a failure to parse the first signaling, the first signaling is ignored.

23. The method of claim 19, wherein: in, The aggregation capability information is used to obtain the aggregation status within the uplink and downlink frequency bands supported by the terminal device, or to obtain the aggregation status within the frequency band.

24. The method of claim 23, wherein: The aggregation state includes at least one of the following: Continuous type; Non-continuous type; Continuous and discontinuous.

25. The method of claim 18, wherein: The first signaling includes at least one of NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL-NR-v17xy signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list SupportedBandCombinationList-v17xy signaling.

26. The method of claim 25, wherein: The CA-BandwidthClassNR-v17xy signaling, the CA-BandwidthClassDL-NR-v17xy signaling, the CA-BandwidthClassUL-NR-v17xy signaling, the BandParameters-v17xy signaling, the BandList-v17xy signaling, the BandCombination-v17xy signaling, the BandCombinationList-v17xy signaling, and the SupportedBandCombinationList-v17xy have the same identifier.

27. The method of claim 18, wherein: The first signaling also includes NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling and NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, or NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL1-NR-v17xy signaling and NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL2-NR-v17xy signaling.

28. The method of claim 27, wherein: The first signaling also includes at least one of a band parameter BandParameters-v17xy signaling, a band list BandList-v17xy signaling, a band combination BandCombination-v17xy signaling, a band combination list BandCombinationList-v17xy signaling, and a supported band combination list supportedBandCombinationList-v17xy signaling.

29. The method of claim 28, wherein: The NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL1-NR-v17xy signaling, NR downlink carrier aggregation bandwidth level CA-BandwidthClassDL2-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL1-NR-v17xy signaling, NR uplink carrier aggregation bandwidth level CA-BandwidthClassUL2-NR-v17xy signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, and supported band combination list supportedBandCombinationList-v17xy have the same identifier.

30. The method of claim 18, wherein: When the aggregate bandwidth level obtained according to the first signaling is one or more of R, S, T and U, the aggregate bandwidth level obtained according to the second signaling is F.

31. The method of claim 18, wherein: When the aggregation bandwidth level obtained according to the first signaling is one or more of MA, MD, ME and MF, the aggregation bandwidth level obtained according to the second signaling is one of M, F, E, D or A.

32. The method of claim 23, wherein: The first signaling includes: Intra-band CA-support-v17xy signaling supporting intra-band carrier aggregation, and the Intra-band CA-support-v17xy signaling is used to indicate the aggregation status within the uplink and downlink frequency bands supported by the terminal device.

33. The method according to claim 23 or 32, characterized in that The first signaling includes: a combination of Intra-band CAUL-support-v17xy signaling supporting intra-band uplink carrier aggregation and Intra-band CADL-support-v17xy signaling supporting intra-band downlink carrier aggregation, and the Intra-band CAUL-support-v17xy signaling and Intra-band CADL-support-v17xy signaling are used to indicate the uplink carrier aggregation status and the downlink carrier aggregation status, respectively.

34. The method according to claim 32 or 33, characterized in that The first signaling also includes at least one of a band parameter BandParameters-v17xy signaling, a band list BandList-v17xy signaling, a band combination BandCombination-v17xy signaling, a band combination list BandCombinationList-v17xy signaling, and a supported band combination list SupportedBandCombinationList-v17xy signaling.

35. The method of claim 34, wherein: The support for intra-band carrier aggregation Intra-band CA-support signaling, band parameters BandParameters-v17xy signaling, band list BandList-v17xy signaling, band combination BandCombination-v17xy signaling, band combination list BandCombinationList-v17xy signaling, support band combination list SupportedBandCombinationList-v17xy signaling has the same identifier.

36. The method of claim 34, wherein: The intra-band uplink carrier aggregation Intra-band CA UL-support signaling and the intra-band downlink carrier aggregation Intra-band CA DL-support signaling, the band parameters BandParameters-v17xy signaling, the band list BandList-v17xy signaling, the band combination BandCombination-v17xy signaling, the band combination list BandCombinationList-v17xy signaling, and the supported band combination list SupportedBandCombinationList-v17xy signaling have the same identifier.

37. A method for acquiring multi-carrier aggregation capability, characterized in that: The method is performed by a network side device and includes: Receive a first signaling and a second signaling sent by a terminal device; wherein the first signaling is used to indicate the aggregation bandwidth level or aggregation capability information supported by the terminal device, and wherein the second signaling is used to indicate the aggregation bandwidth level supported by the terminal device; and wherein the aggregation bandwidth level reported in the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

38. A device for reporting multi-carrier aggregation capability, characterized in that: Applied to a terminal device, the device comprises: A reporting module is used to report the aggregation bandwidth level or aggregation capability information supported by the terminal device to the network side device through a first signaling, and to report the aggregation bandwidth level supported by the terminal device to the network side device through a second signaling; wherein the aggregation bandwidth level reported in the second signaling is the fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling; and the first signaling is the NR carrier aggregation bandwidth level CA-BandwidthClassNR-v17xy signaling, where xy is the sequence number.

39. A device for reporting multi-carrier aggregation capability, characterized in that: Applied to a terminal device, the device comprises: A reporting module is used to report the aggregation bandwidth level or aggregation capability information supported by the terminal device to the network side device through a first signaling, and to report the aggregation bandwidth level supported by the terminal device to the network side device through a second signaling; wherein the aggregation bandwidth level reported in the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

40. A device for acquiring multi-carrier aggregation capability, characterized in that: Applied to a network side device, the device comprises: A receiving module, used to receive a first signaling and a second signaling sent by a terminal device; wherein the first signaling is used to indicate the aggregation bandwidth level or aggregation capability information supported by the terminal device, and wherein the second signaling is used to indicate the aggregation bandwidth level supported by the terminal device; wherein the aggregation bandwidth level reported by the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported by the first signaling; and the first signaling is an NR carrier aggregation bandwidth level CA-BandwidthClassNR-v17xy signaling, wherein xy is a sequence number.

41. A device for acquiring multi-carrier aggregation capability, characterized in that: Applied to a network side device, the device comprises: A receiving module, used to receive a first signaling and a second signaling sent by a terminal device; wherein the first signaling is used to indicate the aggregation bandwidth level or aggregation capability information supported by the terminal device, and wherein the second signaling is used to indicate the aggregation bandwidth level supported by the terminal device; and wherein the aggregation bandwidth level reported in the second signaling is a fallback aggregation bandwidth level of the aggregation bandwidth level reported in the first signaling.

42. A communication device, characterized in that: The device comprises a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 1 to 17.

43. A communication device, characterized in that: The device comprises a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 18 to 37.

44. A computer-readable storage medium, used for storing instructions, which, when executed, enable the method according to any one of claims 1 to 17 to be implemented.

45. A computer-readable storage medium storing instructions, which, when executed, enable the method according to any one of claims 18 to 37 to be implemented.

Images