Communication processing method, device and equipment

Abstract

The invention discloses a communication processing method, device and equipment, and belongs to the technical field of communication, and the communication processing method comprises the steps that a terminal carries out communication through a first link architecture; wherein the first link architecture means that a part of or all carriers of the carrier aggregation use a shared receiving link.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a communication processing method, apparatus, and device. Background Technology

[0002] Existing carrier aggregation receiver links require each carrier to occupy a separate receive (RX) link, which is a waste of link resources and cannot guarantee that fragmented frequency bands in a certain frequency band can be maximized. Summary of the Invention

[0003] This application provides a communication processing method, apparatus, and device to address the problem of how to improve link resource utilization.

[0004] Firstly, a communication processing method is provided, including:

[0005] The terminals communicate through the first link architecture;

[0006] The first link architecture refers to a carrier aggregation where some or all carriers use a shared receiving link.

[0007] Secondly, a communication processing method is provided, including:

[0008] The network-side device sends the second information to the terminal, and at least one of the third carrier aggregation configurations;

[0009] The second information is used to indicate the use of the first link architecture, and the third carrier aggregation configuration is associated with the reception metrics of the first link architecture, wherein the first link architecture refers to the use of a shared reception link for some or all carriers of the carrier aggregation.

[0010] Thirdly, a communication processing apparatus is provided, comprising: a first transceiver unit and a first processing unit;

[0011] The first transceiver unit is used for communication via the first link architecture;

[0012] The first link architecture refers to a carrier aggregation where some or all carriers use a shared receiving link.

[0013] Fourthly, a communication processing apparatus is provided, comprising: a second transceiver unit and a second processing unit;

[0014] The second transceiver unit is used to send second information to the terminal and at least one of the third carrier aggregation configurations;

[0015] The second information is used to indicate the use of the first link architecture, and the third carrier aggregation configuration is associated with the reception metrics of the first link architecture, wherein the first link architecture refers to the use of a shared reception link for some or all carriers of the carrier aggregation.

[0016] Fifthly, a communication processing apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0017] In a sixth aspect, a terminal is provided, the device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0018] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is used to communicate via a first link architecture; wherein the first link architecture refers to a shared receiving link used for some or all of the carriers in carrier aggregation.

[0019] Eighthly, a network-side device is provided, the device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0020] A ninth aspect provides a network-side device, including a processor and a communication interface, wherein the communication interface is used to send at least one of second information and a third carrier aggregation configuration to a terminal; wherein the second information is used to indicate the use of a first link architecture, and the third carrier aggregation configuration is associated with a reception metric of the first link architecture, the first link architecture referring to the use of a shared reception link for some or all carriers of the carrier aggregation.

[0021] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0022] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0023] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0024] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0025] In the embodiments of this application, the terminal can share part or all of the receiving links used for carrier aggregation, thereby saving some receiving link resources, improving the utilization rate of the receiving links, and further aggregating more carriers to improve the utilization rate of fragmented spectrum and enhance the carrier aggregation capability. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of carrier aggregation types;

[0027] Figure 2 This is one of the schematic diagrams of a fragmented spectrum;

[0028] Figure 3 This is the second schematic diagram of a fragmented spectrum;

[0029] Figure 4 This is a schematic diagram comparing the existing receiving link with the shared intra-band NC CA;

[0030] Figure 5 This is a schematic diagram of a system provided in an embodiment of this application;

[0031] Figure 6 This is a flowchart of a communication processing method provided in an embodiment of this application;

[0032] Figure 7 This is a flowchart of another communication processing method provided in the embodiments of this application;

[0033] Figure 8 This is a flowchart of the switching of the receiving link in Embodiment 1 of this application;

[0034] Figure 9 This is a flowchart of the switching of the receiving link in Embodiment 2 of this application;

[0035] Figure 10 This is a flowchart of a switching of the receiving link according to Embodiment 3 of this application;

[0036] Figure 11 This is another flowchart of switching the receiving link in Embodiment 3 of this application;

[0037] Figure 12 This is a flowchart of another switching of the receiving link in Embodiment 3 of this application;

[0038] Figure 13 This is a flowchart of a switching of the receiving link according to Embodiment 5 of this application;

[0039] Figure 14 This is a flowchart of another switching of the receiving link in Embodiment 5 of this application;

[0040] Figure 15 This is a flowchart of another switching of the receiving link in Embodiment 5 of this application;

[0041] Figure 16 This is a flowchart of another switching of the receiving link in Embodiment 5 of this application;

[0042] Figure 17 This is a structural diagram of a communication processing device provided in an embodiment of this application;

[0043] Figure 18 This is a structural diagram of another communication processing device provided in the embodiments of this application;

[0044] Figure 19 This is a structural diagram of a communication device provided in an embodiment of this application;

[0045] Figure 20 This is a structural diagram of a terminal provided in an embodiment of this application;

[0046] Figure 21 This is a structural diagram of a network-side device provided in an embodiment of this application. Detailed Implementation

[0047] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0048] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0049] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0050] It is worth noting that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems.

[0051] The terms "system" and "network" used in the embodiments of this application are often used interchangeably, and the described technologies can be used with respect to the systems and radio technologies mentioned above, as well as other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation 6G communication system.

[0052] To facilitate understanding of the embodiments of this application, the following technical points are introduced first:

[0053] I. About Carrier Aggregation (CA).

[0054] To support wider transmission bandwidth, two or more component carriers are aggregated together, thereby achieving higher peak rates and throughput.

[0055] To make more efficient use of fragmented spectrum, carrier aggregation supports aggregation between different carrier units:

[0056] A) Intra-band contiguous carrier units (CAs) within the same frequency band;

[0057] B) Intra-band non-contiguous carrier units (CAs) within the same frequency band;

[0058] C) Carrier units in different frequency bands (inter-band CA).

[0059] A schematic diagram of the above carrier aggregation types is shown below. Figure 1 As shown.

[0060] II. Multiple Input Multiple Output (MIMO).

[0061] MIMO systems employ multiple antennas (or array antennas) and multiple channels at both the transmitting and receiving ends. MIMO technology can improve channel capacity and reliability, while reducing the bit error rate. The former utilizes the spatial multiplexing gain provided by the MIMO channel (called spatial multiplexing), while the latter utilizes the spatial diversity gain provided by the MIMO channel (called transmit diversity). For spatial multiplexing, the number of antenna layers is defined as the rank of the MIMO channel matrix, which is the number of independent virtual channels. For example, for a 4-transmit, 2-receive antenna system, the number of antenna layers may be 1 or 2 depending on the channel environment, but will not exceed the minimum number of antennas at the receiving and transmitting ends (here, 2).

[0062] III. Regarding the Frequency Separation Class.

[0063] FreqSeparationClass is a signaling term related to intra-band non-contiguous carrier aggregation (CA), used to indicate the frequency spacing width between the lowest and highest frequency carriers within a frequency band. It includes several levels, with different levels representing different frequency spacing widths.

[0064] IV. Regarding fragmented carriers and "interference or blocking signals".

[0065] A certain frequency band has been allocated to several operators, and the spectrum allocated to the same operator may not always be continuous, but rather fragmented. If an operator wants to aggregate several fragmented frequency bands simultaneously, currently each part needs to use its own receiving link.

[0066] Example 1: Fragmentation of the FR1 low-frequency band in Australia. Identical padding indicates spectrum access by the same operator, with each band block width being 5MHz. The n26 and n5 bands in Australia are currently allocated to two operators: Telstra and TPG Telecom.

[0067] like Figure 2As shown, in Telstra's regional network, in the in-band non-contiguous carrier aggregation combination CA_n26(2A), CC1 and CC2 are the carriers participating in the aggregation, and the TPG Telecom carrier in the middle can be defined as a "blocker". Here, "Metro" refers to a network within a metropolitan area, typically used to connect different locations within a city, providing high-speed data transmission and communication services. "Regional" refers to a network connecting an entire region, typically used to span cities, rural areas, and other geographical locations, providing wider communication coverage and connectivity.

[0068] Example 2: Fragmentation of the mid-band of FR1 in Canada. Filling with the same color depth indicates spectrum access from the same operator, with each band block width being 5MHz. For example... Figure 3 As shown, AWS (Advanced Wireless Services), PCS (Personal Communications Service), and BRS (Broadband Radio Service) refer to the spectrum used to provide broadband wireless communication services.

[0069] V. Comparison of receiving links.

[0070] by Figure 4 For example, in the existing in-band non-continuous carrier aggregation receiving links, each link receives only one CC. Assuming there are now 6 receiving links, the number of CCs that can be aggregated is limited, that is, a maximum of 6 CCs can participate in aggregation.

[0071] In carrier aggregation (CA) scenarios, the New Radio (NR) data reception rate is limited by the number of supported carriers. This number is further constrained by the number and capabilities of the terminal's receive links (Rx chains) and the capabilities of the baseband processor within the terminal. Furthermore, fragmented spectrum allocation within the same frequency band requires each carrier to use an independent receive link when aggregating discontinuous carriers. This requirement prevents operators from fully utilizing fragmented spectrum in CA aggregation, thus limiting the capabilities of CA and the upper limit on the number of carriers that can be aggregated.

[0072] Figure 5 This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 51 and a network-side device 52.

[0073] Among them, terminal 51 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipborne equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), game console, personal computer (PC), ATM or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 51 is not limited in the embodiments of this application.

[0074] Network-side equipment 52 may include access network equipment or core network equipment. Access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, radio access network unit, or satellite. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc. In this context, a base station may be referred to as a Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The base station is not limited to any specific technical terminology. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for introduction, and the specific type of base station is not limited.

[0075] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support Function. Support Functions (BSF), Application Functions (AF), Location Management Functions (LMF), Gateway Mobile Location Centres (GMLC), and Network Data Analytics Functions (NWDAF), etc. It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0076] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0077] Based on the above Figure 4 For example, if some CCs can be shared, such as a maximum of two adjacent CCs sharing one RX chain, then the number of links can be reduced to 3 to 6, which can aggregate more CCs and further improve the transmission rate.

[0078] In view of this, embodiments of this application provide a communication processing method, apparatus, and device to solve the problem of wasted link resources in related technologies.

[0079] See Figure 6 This application provides a communication processing method, the specific steps of which include:

[0080] Step 61: The terminal communicates through the first link architecture; wherein, the first link architecture refers to the use of a shared receiving link for some or all of the carriers in carrier aggregation.

[0081] Understandably, the first link architecture can also be called a shared RX chain architecture or state.

[0082] Optionally, the aforementioned terminals support the ability to share a receiving link.

[0083] Optionally, the aforementioned carriers can also be replaced with subcarriers. For example, the use of a shared receive link for some or all carriers in carrier aggregation can also be described as the use of a shared receive link for some or all subcarriers participating in carrier aggregation.

[0084] In one embodiment of this application, before the terminal communicates via the first link architecture, the method further includes:

[0085] The terminal communicates via a second link architecture; wherein, the second link architecture refers to each carrier in carrier aggregation using an independent receiving link.

[0086] Understandably, the second-link architecture can also be referred to as a separate RX chain architecture or state.

[0087] For example, the terminal uses the second link architecture for communication by default, and then the terminal can switch to use the first link architecture for communication.

[0088] In one embodiment of this application, the communication performance under the first link architecture is represented by a first reception indicator, and the communication performance under the second link architecture is represented by a second reception indicator. The first reception indicator may be the same as or different from the second reception indicator.

[0089] Optionally, the first or second reception indicator may include, but is not limited to, at least one of signal strength, signal-to-noise ratio, bit error rate, etc.

[0090] In one embodiment of this application, the terminal communicates via a first link architecture, including:

[0091] If the first condition is met, the terminal communicates through the first link architecture, whereby the first condition is used by the terminal to determine whether to switch to the first link architecture.

[0092] For example, the terminal defaults to using the second link architecture for communication. If the first condition is met, the terminal can switch to using the first link architecture for communication.

[0093] In one embodiment of this application, after the terminal communicates via the first link architecture, the method further includes:

[0094] If the second condition is met, the terminal communicates through the second link architecture, and the second condition is used by the terminal to determine whether to switch to the second link architecture.

[0095] For example, the terminal defaults to using the second link architecture for communication. If the first condition is met, the terminal can switch back to using the first link architecture for communication. If the second condition is met, the terminal communicates via the second link architecture.

[0096] In one embodiment of this application, when a second condition is met, the terminal communicates through the second link architecture, including:

[0097] If the second condition is met, the terminal sends the first information to the network-side device;

[0098] The terminal receives a first carrier aggregation configuration sent by the network-side device. The terminal communicates through a second link architecture, and the first carrier aggregation configuration corresponds to the reception index of the second link architecture.

[0099] In one embodiment of this application, after the terminal communicates via a first link architecture, the method further includes:

[0100] The terminal sends at least one of the following:

[0101] 1) Share the frequency band of the receiving link;

[0102] 2) Share the carrier of the receiving link;

[0103] 3) Unconfigured carriers, which can share an existing receive link or an idle receive link.

[0104] In one embodiment of this application, after the terminal communicates via a first link architecture, the method further includes:

[0105] The terminal receives a second carrier aggregation configuration, which indicates a new carrier that can be aggregated, or indicates a new carrier that supports aggregation, or indicates a new carrier index that supports aggregation, or indicates an updated set of carriers that supports aggregation.

[0106] It is understood that the second carrier aggregation configuration can be a new carrier aggregation configuration, and optionally, the second carrier aggregation configuration can include carriers that were not previously supported for using a shared receive link.

[0107] Optionally, the new carrier can share an existing receiving link; or, the new carrier can share an idle receiving link; or, a portion of the new carriers can share an existing receiving link, while another portion of the new carriers can share an idle receiving link.

[0108] In one embodiment of this application, satisfying the first condition includes at least one of the following:

[0109] 1) The terminal receives second information, the second information instructing the terminal to use the first link architecture;

[0110] 2) The terminal did not receive the third information, which is used to indicate that the terminal is not allowed to use the first link architecture;

[0111] 3) The terminal receives a third carrier aggregation configuration, which is associated with the reception metrics of the first link architecture;

[0112] 4) The configured carrier frequency band is a specific frequency band;

[0113] For example, if the configured carrier is on a specific frequency band, then that carrier can use a shared receive link.

[0114] 5) The frequency spacing between configured adjacent carriers does not exceed the first value;

[0115] For example, if the frequency spacing between configured adjacent carriers is less than 100MHz, then the adjacent carriers can use a shared receive link.

[0116] 6) The power relationship between the first signal and the first carrier or the second carrier satisfies the third condition, where the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier.

[0117] It should be noted that the power relationship between the first signal and the first carrier or the second carrier satisfies the third condition, including at least one of the following: the power relationship between the first signal and the first carrier satisfies the third condition and the power relationship between the first signal and the second carrier satisfies the third condition; the power relationship between the first signal and the first carrier satisfies the third condition; the power relationship between the first signal and the second carrier satisfies the third condition.

[0118] Optionally, the first signal may include, but is not limited to, an interference signal or a blocking signal.

[0119] 7) The time difference between the received signals of the configured carriers satisfies the fourth condition.

[0120] Optionally, the time difference between the received signals of the configured carriers satisfies the fourth condition, including at least one of the following: the time difference between the received signals of the configured carriers is not greater than a preset value, and the time difference between the received signals of the configured carriers is within a preset range. In this embodiment, the above-mentioned preset value and preset range are not specifically limited.

[0121] For example, if the time difference between the received signals of the configured carriers is less than a preset value (e.g., 3µs), then the carrier can use a shared receive link.

[0122] In this embodiment, when the terminal-side hardware resources, the bandwidth of the frequency bands involved in aggregation, and the relative power between carriers meet the first condition, if the receiving links of multiple fragmented carriers of the same operator in intra-band non-contiguous carrier aggregation (NC CA) can be switched from each carrier independently using a separate Rx link to multiple carriers sharing a single Rx link, the number of Rx links used by the terminal can be reduced to free up corresponding resources. Furthermore, existing frequency band combinations can be expanded to support aggregation of more carriers, or the freed link resources can be used for MIMO.

[0123] In one embodiment of this application, the power relationship between the first signal and the first carrier or the second carrier satisfies a third condition, including at least one of the following:

[0124] 1) The power of the first signal is not higher than the power of the first carrier or the second carrier than the second value;

[0125] Optionally, the power of the first signal being no higher than the second value compared to the power of the first carrier or the second carrier includes at least one of the following: a) the power of the first signal being no higher than the second value compared to the power of the first carrier, and the power of the first signal being no higher than the second value compared to the power of the second carrier; b) the power of the first signal being no higher than the second value compared to the first carrier; c) the power of the first signal being no higher than the second value compared to the power of the second carrier.

[0126] 2) The power spectral density of the first signal is not higher than the power spectral density of the first carrier or the second carrier than the third value.

[0127] Optionally, the power spectral density of the first signal being no higher than a third value compared to the power spectral density of the first carrier or the second carrier includes at least one of the following: a) the power spectral density of the first signal being no higher than a third value compared to the power spectral density of the first carrier, and the power spectral density of the first signal being no higher than a third value compared to the power spectral density of the second carrier; b) the power spectral density of the first signal being no higher than a third value compared to the power spectral density of the first carrier; c) the power spectral density of the first signal being no higher than a third value compared to the power spectral density of the second carrier.

[0128] The aforementioned second or third value may be agreed upon by the protocol or indicated by the network side.

[0129] In one embodiment of this application, satisfying the second condition includes at least one of the following:

[0130] 1) The terminal receives third information, which is used to indicate that the terminal is not allowed to use the first link architecture;

[0131] 2) The terminal receives fourth information, which instructs the terminal to use the second link architecture;

[0132] 3) The terminal receives a fourth carrier aggregation configuration, which is associated with the reception metrics of the second link architecture;

[0133] 4) The configured carrier frequency band is not a specific frequency band;

[0134] 5) The frequency spacing between configured adjacent carriers exceeds the first value;

[0135] 6) The power relationship between the first signal and the first carrier or the second carrier does not satisfy the third condition, the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier;

[0136] 7) The time difference between the received signals of the configured carriers does not meet the fourth condition.

[0137] In one embodiment of this application, the method further includes:

[0138] The terminal sends first capability information, which indicates that the terminal has the capability to support a shared receive link.

[0139] In one embodiment of this application, the method further includes:

[0140] The terminal sends information on all frequency band combinations supported by the terminal for carrier aggregation;

[0141] The frequency band combination information for all carrier aggregation includes at least one of the following: frequency band combination information for carrier aggregation that the terminal supports by default, and frequency band combination information for carrier aggregation that the terminal supports when using the first link architecture.

[0142] Optionally, the frequency band combination information may include at least one of the following: the frequency band supported by the terminal, and the number of carriers that the frequency band can support. For example, if the carrier aggregation configuration is: CA_n7A-n25A-n66A-n77(3A), the frequency band combination information reported by the terminal may include: one n7, one n25, one n66, and three n77. This frequency band combination information characterizes the carrier aggregation configuration supported by the terminal. In one embodiment of this application, after the terminal sends all the frequency band combination information supported by the terminal for carrier aggregation, the method further includes:

[0143] The terminal receives information from the first signal;

[0144] Wherein, the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier.

[0145] In one embodiment of this application, the method further includes;

[0146] The terminal sends a fifth message, which includes at least one of the following:

[0147] 1) Sixth information, the sixth information being used to indicate a configured carrier that can use a shared receive link;

[0148] 2) One or more new carriers, each of which uses an independent receive link, or the one or more new carriers share a receive link with the configured carriers, or the multiple new carriers share a receive link;

[0149] 3) Seventh information, which is used to indicate the use of the second link architecture;

[0150] 4) Information on the number of layers supported by the terminal;

[0151] 5) The carrier aggregation combination of the shared links recommended or preferred by the terminal;

[0152] 6) Measurement results between the first signal and the second carrier or the second carrier.

[0153] Optionally, the measurement result between the first signal and the second carrier or the second carrier includes at least one of the following: the measurement result between the first signal and the second carrier and the measurement result between the first signal and the second carrier, the measurement result between the first signal and the second carrier, and the measurement result between the first signal and the second carrier.

[0154] Optionally, the measurement results may include, but are not limited to, at least one of the following: power value, power spectral density, etc.

[0155] In one embodiment of this application, the transmission method of the first information or the fifth information includes at least one of the following: transmission via measurement report, transmission via auxiliary information, transmission via MAC CE, and transmission in response to a request information sent by the network-side device.

[0156] In one embodiment of this application, some or all of the carriers in the carrier aggregation use a shared receiving link, including: all carriers in the carrier aggregation share a single receiving link;

[0157] or,

[0158] A portion of the carriers in the carrier aggregation shares a single receive link, while each carrier in another portion of the carrier aggregation uses an independent receive link.

[0159] or,

[0160] A portion of the carriers in the carrier aggregation share a single receive link, while another portion of the carriers in the carrier aggregation share a different receive link.

[0161] In one embodiment of this application, the first reception indicator includes at least one set of relaxed reception indicators, and the second reception indicator includes at least one set of reception indicators.

[0162] The aforementioned relaxed set of reception metrics refers to a set of reception metrics that includes relaxed or reduced requirements for reception performance. These reception metrics include, but are not limited to, at least one of ΔRIBNC (a relaxed reference sensitivity value allowed due to support for in-band discontinuous CA operation), ACS (adjacent channel selectivity), and in-band blocking.

[0163] In one embodiment of this application, the relaxed set of reception indicators includes at least one subset of reception indicators, which is determined based on at least one of the following: the number of aggregated carriers, the number of shared reception links, the type of reception links, and the power relationship between interference signals and adjacent carriers.

[0164] Optionally, the communication processing method provided in this application embodiment is applicable to at least one of the following scenarios:

[0165] 1) Frequency Division Duplexing (FDD) - Time Division Duplexing (TDD) Dual Connectivity (E-UTRAN New Radio–Dual Connectivity, ENDC);

[0166] 2) FDD-FDD ENDC;

[0167] 3) FDD-TDD uplink carrier aggregation;

[0168] 4) FDD-FDD uplink carrier aggregation;

[0169] 5) FDD-TDD Supplementary Uplink (SUL);

[0170] 6) FDD-FDD SUL.

[0171] In this embodiment, the receiving links used for carrier aggregation (e.g., in-band non-contiguous carrier aggregation) can be partially or fully shared, thereby saving some receiving link resources and improving the utilization rate of the receiving links. Furthermore, more carriers can be aggregated to improve the utilization rate of fragmented spectrum and enhance the carrier aggregation capability. Alternatively, corresponding link resources can be released for MIMO to increase the channel capacity.

[0172] See Figure 7 This application provides a communication processing method, the specific steps of which include:

[0173] Step 71: The network-side device sends at least one of the following to the terminal: second information and third carrier aggregation configuration;

[0174] The second information is used to indicate the use of the first link architecture, and the third carrier aggregation configuration is associated with the reception metrics of the first link architecture, wherein the first link architecture refers to the use of a shared reception link for some or all carriers of the carrier aggregation.

[0175] In one embodiment of this application, before or after the network-side device sends at least one of the second information and the third carrier aggregation configuration to the terminal, the method further includes:

[0176] The network-side device sends at least one of the following to the terminal: third information, fourth information, first carrier configuration, and fourth carrier aggregation configuration;

[0177] The third information indicates that the terminal is not allowed to use the first link architecture, and the fourth information indicates that the terminal uses the second link architecture. The first carrier configuration or the fourth carrier aggregation configuration is associated with the reception index of the second link architecture, which refers to each carrier of the carrier aggregation using an independent reception link.

[0178] In one embodiment of this application, the communication performance under the first link architecture is represented by a first reception indicator, and the communication performance under the second link architecture is represented by a second reception indicator. The first reception indicator may be the same as or different from the second reception indicator.

[0179] In one embodiment of this application, after the network-side device sends the second information to the terminal, the method further includes:

[0180] The network-side device sends a second carrier configuration to the terminal, the second carrier configuration being used to indicate new carriers that can be aggregated.

[0181] In one embodiment of this application, the new carrier can share an existing receiving link; or, the new carrier can share an idle receiving link; or, a portion of the new carriers can share an existing receiving link, and another portion of the new carriers can share an idle receiving link.

[0182] In one embodiment of this application, after the network-side device sends a third carrier aggregation configuration to the terminal, the method further includes:

[0183] The network-side device receives the first information sent by the terminal;

[0184] The network-side device sends a first carrier aggregation configuration to the terminal, and the first carrier aggregation configuration corresponds to the reception index of the second link architecture.

[0185] In one embodiment of this application, before or after the network-side device sends the second information, the third carrier aggregation configuration, the third information, the fourth information, the first carrier configuration, or the fourth carrier aggregation configuration to the terminal, the method further includes:

[0186] The network-side device obtains the fifth piece of information.

[0187] The network-side device determines whether the terminal uses a first link architecture or a second link architecture based on the fifth information.

[0188] The fifth piece of information includes at least one of the following:

[0189] 1) Sixth information, the sixth information being used to indicate a configured carrier that can use a shared receive link;

[0190] 2) One or more new carriers, each of which uses an independent receive link, or the one or more new carriers share a receive link with the configured carriers, or the multiple new carriers share a receive link;

[0191] 3) Seventh information, which is used to indicate the use of the second link architecture;

[0192] 4) Information on the number of layers supported by the terminal;

[0193] 5) The carrier aggregation combination of the shared links recommended or preferred by the terminal;

[0194] 6) Measurement result between the first signal and the second carrier or the second carrier, wherein the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier.

[0195] In one implementation, the measurement result between the first signal and the second carrier or the second carrier is reported by the terminal.

[0196] In another implementation, the measurement result between the first signal and the second carrier or the second carrier is determined by the network-side device.

[0197] Optionally, the communication processing method provided in this application embodiment is applicable to at least one of the following scenarios:

[0198] 1) FDD-TDD ENDC;

[0199] 2) FDD-FDD ENDC;

[0200] 3) FDD-TDD uplink carrier aggregation;

[0201] 4) FDD-FDD uplink carrier aggregation;

[0202] 5) FDD-TDD SUL;

[0203] 6) FDD-FDD SUL.

[0204] In this embodiment, the terminal side can share part or all of the receiving links used for carrier aggregation based on the network side's instructions, thereby saving some receiving link resources and improving the utilization rate of the receiving links. Furthermore, it can aggregate more carriers to improve the utilization rate of fragmented spectrum and enhance the carrier aggregation capability. Alternatively, it can release the corresponding link resources for MIMO to increase the channel capacity.

[0205] The optional implementation methods of this application are described below with reference to Embodiments 1 to 16.

[0206] Example 1

[0207] In this embodiment, the relative power between the carriers participating in the aggregation and the interfering signal (blocker) satisfies the first condition by default. The UE supports the capability of a shared RX chain and reports all supported frequency band combinations for carrier aggregation. The reported frequency band combination information can be associated with reception indicators. Some of the frequency band combination information is only supported in a shared RX chain, corresponding to a set of relaxed reception indicators (first reception indicators). The network-side device judges the reception indicators and combines them with other information, such as environmental interference, to indicate the aggregation carrier configuration. When the aggregation carrier configuration is indicated, the UE needs to switch to a shared RX chain for support.

[0208] See Figure 8 The specific steps include:

[0209] Step 1: The UE supports the sharedRXchain capability and reports information on all frequency band combinations it supports for carrier aggregation.

[0210] Some of the frequency band combination information is only supported in the shared Rx chain and is associated with a set of relaxed reception metrics.

[0211] Step 2: The network-side equipment assigns a third carrier aggregation configuration or a fourth carrier aggregation configuration to the UE;

[0212] For example, network-side equipment can make a comprehensive judgment by combining reception indicators and other information to allocate a third carrier aggregation configuration or a fourth carrier aggregation configuration to the UE.

[0213] Step 3a: Based on the allocated fourth CA configuration, the UE obtains that it can use an independent receive link architecture, and the corresponding receive indicators are a more stringent set of receive indicators, namely the second receive indicators.

[0214] Step 3b: Based on the assigned third CA configuration, the UE learns that it must use a shared receive link architecture, and the corresponding receive metrics are a more lenient set of receive metrics, namely the first receive metrics.

[0215] Example 2

[0216] In this embodiment, the relative power between the carriers participating in the aggregation and the blocker does not always satisfy the first condition, requiring detection and judgment. When the first condition is met, the UE's receive link can switch to the shared RX chain; this operation can be performed by the UE itself. When the first condition is no longer met, the UE's receive link switches back to the separate RX chain.

[0217] See Figure 9 The specific steps include:

[0218] Step 1: The UE supports the sharedRXchain capability and reports all CA configuration combinations it supports.

[0219] Step 2: The network selects the configuration for the UE from the supported CA configurations. The network instructs the UE on the first signal (blocker) between each carrier in each frequency band corresponding to this CA configuration.

[0220] Step 3: The UE detects the blocker's power and determines the power relationship between the blocker's power and the power of the carriers participating in the aggregation.

[0221] The aforementioned carriers are those adjacent to the blocker, including the first carrier and the second carrier.

[0222] Step 4a: The power relationship satisfies the third condition;

[0223] Optionally, the power relationship magnitude satisfies the third condition including at least one of the following: 1) the power of the first signal is not higher than the power of the first carrier or the second carrier by a second value; 2) the power spectral density of the first signal is not higher than the power spectral density of the first carrier or the second carrier by a third value.

[0224] Step 5a: The UE automatically switches to the shared RX chain and relaxes the reception index to a certain level; then proceed to step 6;

[0225] It is understandable that when a UE switches to a shared RX chain on its own and the reception metrics are relaxed to a certain level, it means that the UE uses the first link architecture and the UE uses the first reception metrics.

[0226] Step 4b: The power relationship does not satisfy the third condition;

[0227] Step 5b: The UE maintains the separate RX chain state unchanged;

[0228] That is, the UE uses a second link architecture;

[0229] Step 6: If the power relationship no longer satisfies the third condition.

[0230] Step 7: The UE returns to a standalone CC state, either fully or partially, and the reception metrics change accordingly.

[0231] That is, the UE uses a second link architecture and a second reception metric.

[0232] Example 3

[0233] In this embodiment, the relative power between the carrier and the blocker does not always satisfy the third condition, which requires the UE to detect and determine.

[0234] Compared to Example 2, after the UE switches to the shared RX chain, it can aggregate more carriers and support more CA configurations accordingly.

[0235] At this point, the UE reports all CA configurations and divides them into two main categories: the second link architecture that the UE can support by default and the first link architecture that the UE can only support after switching to the shared RX chain.

[0236] The UE's receive link can only be switched to the shared RX chain when the first condition is met; this operation can be performed by the UE itself. When the first condition is no longer met, the UE reports the corresponding information (i.e., the first information) to the network-side device, the network instructs the UE to a new CA configuration (i.e., the first carrier aggregation configuration) and switches the receive link back to the independent state.

[0237] In one implementation, the network indicates to the UE the first signal (blocker) information between each carrier in each frequency band corresponding to the CA configuration, and the UE can only determine the link sharing possibility for the already allocated carriers.

[0238] See Figure 10 The specific steps include:

[0239] Step 1: The UE supports the shared RX chain capability and reports all supported CA configuration combinations. One type is supported by default, and the other type requires switching to shared RX chain for support.

[0240] Step 2: The network selects the configuration for the UE from the default supported CA configurations (i.e., the fourth carrier aggregation configuration). The network instructs the UE on the blocker information between carriers in each frequency band corresponding to this CA configuration.

[0241] Step 3: The UE detects the power of the first signal (blocker) and determines the power relationship with the carriers participating in the aggregation; then it executes either step 4a or step 5b.

[0242] Step 4a: If the power relationship satisfies the third condition, then proceed to step 5a;

[0243] Step 5a: The UE automatically switches to the shared RX chain and relaxes the reception index to a certain level; then proceed to step 6;

[0244] It is understandable that when a UE switches to a shared RX chain on its own and the reception metrics are relaxed to a certain level, it means that the UE uses the first link architecture and the UE uses the first reception metrics.

[0245] Step 4b: The power relationship does not meet the third condition, then proceed to step 5b;

[0246] Step 5b: The UE maintains the separate RX chain state unchanged, that is, the UE continues to use the second link architecture, and the CA configuration remains unchanged;

[0247] Step 6: The UE reports to the network side which frequency band's receive link has switched to the shared RX chain;

[0248] Step 7: The network issues a new CA configuration (i.e., second carrier aggregation configuration), instructing the UE to aggregate more CCs;

[0249] Step 8: If the power relationship no longer satisfies the third condition;

[0250] Step 9: The UE reports relevant information to the network side (i.e., the first information);

[0251] Step 10: The network issues a new CA configuration, instructing the UE to use the new CA configuration, and the receive link reverts to a single CC independent usage state, either entirely or partially. Receive metrics will change accordingly.

[0252] In other words, the UE uses the second link architecture and the second reception metric based on the new CA configuration (such as the first carrier aggregation configuration) issued by the network.

[0253] In another implementation, the network indicates to the UE the blocker category one information between carriers in each frequency band corresponding to the CA configuration. The network also indicates to the UE the blocker category two information between unconfigured carriers and configured carriers in that frequency band. Compared to... Figure 6 The embodiment shown is in Figure 7 In the implementation shown, the UE can also detect whether an unconfigured carrier can share the RX link of a configured carrier.

[0254] See Figure 11 The specific steps include:

[0255] Step 1: The UE supports the shared RX chain capability and reports all supported CA configuration combinations. One type is supported by default, and the other requires switching to shared RX chain. Step 2: The network selects the configuration for the UE from the default supported CA configurations. The network instructs the UE on the blocker category one information between carriers in each frequency band corresponding to this CA configuration. The network instructs the UE on the blocker category two information between unconfigured carriers and configured carriers in this frequency band.

[0256] Step 3: The UE detects the power of blocker category 1 and determines the power relationship (I) with the carriers participating in the aggregation. The UE detects the power of blocker category 2 and determines the power relationship (II) with the unconfigured carriers and the configured carriers. Execute step 4a, step 4b, or step 4c.

[0257] Step 4a: Only when the power magnitude relationship satisfies the third condition;

[0258] Step 5a: The UE automatically switches to the shared RX chain and relaxes the reception metric to a certain level.

[0259] It is understandable that when a UE switches to a shared RX chain on its own and the reception metrics are relaxed to a certain level, it means that the UE uses the first link architecture and the UE uses the first reception metrics.

[0260] Step 6a: The UE reports to the network side which frequency band's receive link has switched to the shared RX chain.

[0261] Step 7a: The network issues a new CA configuration (i.e., second carrier aggregation configuration) to instruct the UE to aggregate more CCs, and then proceeds to step 8.

[0262] Step 4b: Both power magnitude relationship one and power magnitude relationship two satisfy the third condition;

[0263] Step 5b: The UE automatically switches to the shared RX chain, and the reception index is relaxed to a certain level;

[0264] Step 6b: The UE reports to the network which frequency band's receive link has switched to the shared RX chain, and also reports to the network which unconfigured CCs can also share the existing RX chain.

[0265] Step 7b: The network issues a new CA configuration (i.e., second carrier aggregation configuration), instructing the UE to aggregate more CCs, and then proceeds to step 8.

[0266] Step 4c: Neither power magnitude relationship one nor power magnitude relationship two satisfies the third condition;

[0267] Step 5c: The UE maintains the separate RX chain state and the CA configuration remains unchanged.

[0268] It is understandable that the UE maintaining the separate RX chain state means that the UE continues to use the second link architecture.

[0269] Step 8: If a certain power relationship no longer satisfies the third condition;

[0270] Step 9: The UE reports relevant information to the network side (i.e., the first information);

[0271] Step 10: The network issues a new CA configuration, instructing the UE to use the new CA configuration, and the receive link reverts to a single CC independent usage state, either entirely or partially. Receive metrics will change accordingly.

[0272] In other words, the UE uses the second link architecture and the second reception metric based on the new CA configuration (such as the first carrier aggregation configuration) issued by the network.

[0273] In another implementation, the network indicates to the UE information on blocker category one between carriers in each frequency band corresponding to the CA configuration. The network indicates to the UE information on blocker category two between carriers not configured in that frequency band and configured CCs. The network indicates to the UE information on blocker category three between carriers not configured in that frequency band. Compared to... Figure 11 The implementation method shown, Figure 8 In the illustrated embodiment, the UE can also detect whether link sharing is possible between unconfigured carriers.

[0274] See Figure 12 The specific steps include:

[0275] Step 1: The UE supports the shared RX chain capability and reports all supported CA configuration combinations. One type is supported by default, and the other type requires switching to shared RX chain for support.

[0276] Step 2: The network selects the configuration for the UE from the default supported CA configurations.

[0277] The network instructs the UE to provide blocker category one information between carriers within each frequency band corresponding to the CA configuration. The network instructs the UE to provide blocker category two information between unconfigured CCs and configured carriers in this frequency band. The network instructs the UE to provide blocker category three information between unconfigured carriers in this frequency band.

[0278] Step 3: The UE detects the power of blocker category 1 and determines the power relationship with the configured carriers (Step 1). The UE detects the power of blocker category 2 and determines the power relationship with both unconfigured and configured carriers (Step 2). The UE detects the power of blocker category 3 and determines the power relationship with the unconfigured carriers (Step 3). Then, proceed to step 4a, 4b, 4c, 4d, 4e, or 4f.

[0279] Step 4a: Only when the power magnitude relationship satisfies the third condition;

[0280] Step 5a: The UE automatically switches to the shared RX chain, and the reception metric is relaxed to a certain level.

[0281] That is, the UE uses the first link architecture and the UE uses the first reception metric.

[0282] Step 6a: The UE reports to the network side which frequency band's receive link has switched to the shared RX chain;

[0283] Step 7a: The network issues a new CA configuration (i.e., second carrier aggregation configuration), instructing the UE to aggregate more CCs, and then proceeds to step 8;

[0284] Step 4b: Only when the power magnitude relationship satisfies the third condition.

[0285] Step 5b: The UE reports to the network which unconfigured CCs can also share the existing RX chain.

[0286] Step 6b: The network issues a new CA configuration (i.e., second carrier aggregation configuration), instructing the UE to aggregate more CCs, and then proceeds to step 8.

[0287] Step 4c: Both power magnitude relationship one and power magnitude relationship two satisfy the third condition.

[0288] Step 5c: The UE automatically switches to the shared RX chain, and the reception metric is relaxed to a certain level;

[0289] That is, the UE uses the first link architecture and the UE uses the first reception metric.

[0290] Step 6c: The UE reports to the network which frequency band's receive link has switched to the shared RX chain, and also reports to the network which unconfigured CCs can also share the existing RX chain.

[0291] Step 7c: The network issues a new CA configuration (i.e., second carrier aggregation configuration), instructing the UE to aggregate more CCs, and then proceeds to step 8;

[0292] Step 4d: Both power magnitude relationship one and power magnitude relationship three satisfy the third condition.

[0293] Step 5d: The UE automatically switches to the shared RX chain, and the reception metric is relaxed to a certain level;

[0294] That is, the UE uses the first link architecture and the UE uses the first reception metric.

[0295] Step 6d: The UE reports to the network which frequency band's receive link has switched to a shared RX chain, and at the same time reports to the network which unconfigured CCs can share the freed-up RX chain.

[0296] Step 7d: The network issues a new CA configuration (i.e., second carrier aggregation configuration), instructing the UE to aggregate more CCs, and then proceeds to step 8.

[0297] Step 4e: Power magnitude relationship one, power magnitude relationship two, and power magnitude relationship three all satisfy the first condition;

[0298] Step 5e: The UE automatically switches to the shared RX chain, and the reception metric is relaxed to a certain level;

[0299] That is, the UE uses the first link architecture and the UE uses the first reception metric.

[0300] Step 6e: The UE reports to the network which frequency band's receive link has switched to a shared RX chain, and also reports to the network which unconfigured CCs can share the existing RX chain, and which unconfigured CCs can share the available RX chain.

[0301] Step 7e: The network issues a new CA configuration (i.e., second carrier aggregation configuration), instructing the UE to aggregate more CCs, and then proceeds to step 8.

[0302] Step 4f: Power relationship 1, power relationship 2, and power relationship 3 all fail to meet the third condition;

[0303] Step 5f: The UE maintains the separate RX chain state and the CA configuration remains unchanged.

[0304] In other words, the UE continues to use the second link architecture.

[0305] Step 8: If a certain power relationship no longer satisfies the third condition;

[0306] Step 9: The UE reports relevant information to the network side (i.e., the first information);

[0307] Step 10: The network issues a new CA configuration, instructing the UE to use the new CA configuration, and the receive link reverts to a single CC independent usage state, either entirely or partially. Receive metrics will change accordingly.

[0308] In other words, the UE uses the second link architecture and the second reception metric based on the new CA configuration (such as the first carrier aggregation configuration) issued by the network.

[0309] Example 4:

[0310] In Embodiments 2 and 3, the UE's self-switching to the shared RX chain link state may only be performed under the condition that the UE does not receive a message from the network side prohibiting it from switching to the shared link. That is, if the terminal does not receive the third information, the terminal can use the first link architecture. The third information is used to indicate that the terminal is not allowed to use the first link architecture.

[0311] Example 5

[0312] Compared to Embodiment 2, Embodiment 5 also allows the UE to report fifth information to the network. The network determines that the first condition of the shared RX chain is met before instructing the UE to perform a link handover operation. When the first condition is no longer met, the network instructs the UE's receiving link to switch back to the separate RX chain state.

[0313] See Figure 13 The specific steps include:

[0314] Step 1: The UE supports the sharedRXchain capability and reports all CA configuration combinations it supports.

[0315] Step 2: The network selects the configuration for the UE from the supported CA configurations.

[0316] The network instructs the UE to provide information about the blocker (i.e., the first signal) between each carrier in each frequency band corresponding to the CA configuration.

[0317] Step 3: The UE detects the blocker's power, reports the corresponding fifth information to the network, and then executes step 4a or step 4b.

[0318] For example, the UE periodically reports the corresponding fifth information to the network, or the UE reports the corresponding fifth information to the network when the power of the blocker detected by the UE meets a preset condition (such as the third condition). It is understood that this embodiment does not specifically limit the conditions and methods for the UE to report the fifth information.

[0319] Step 4a: When the network determines that it can switch to the shared RX chain, it sends relevant signaling (i.e., the second information) to the UE;

[0320] Step 5a: The UE switches to the shared RX chain and the reception metric is relaxed to a certain level, then proceed to step 6;

[0321] In other words, the UE uses the first link architecture and the first reception metric.

[0322] Step 4b: If the network determines that it cannot switch to the shared RX chain link at this time, it will not issue relevant signaling.

[0323] Step 5b: The UE maintains the separate RX chain state unchanged;

[0324] In other words, the UE uses a second link architecture.

[0325] Step 6: The network determines that the shared RX chain can no longer be used between certain carriers;

[0326] Step 7: The network instructs the UE to revert to a single carrier state, using only one link, for all or part of its receive link. The receive metrics will change accordingly.

[0327] In other words, the UE uses a second link architecture and a second reception metric.

[0328] Example 6:

[0329] Compared to Example 5, after the UE switches to the shared RX chain, it can aggregate more carriers and support more CA configurations accordingly.

[0330] At this point, the UE reports all CA configurations, which are divided into two categories: those that the UE can support by default, and those that the UE can only support after switching to the shared RX chain.

[0331] When a preset condition (such as the third condition) is met, the UE reports the fifth piece of information to the network. If the network determines that the first condition of the shared RX chain is met, it instructs the UE to perform a link handover operation. When the first condition is no longer met, the network instructs the UE to configure a new CA and switches the receiving link back to independent state.

[0332] The corresponding process is as follows, and there are several possibilities:

[0333] 1. In one implementation, the network instructs the UE to provide information on the blockers between carriers in each frequency band corresponding to the CA configuration, and the network determines whether the allocated carriers can be shared based on the information reported by the UE.

[0334] See Figure 14 The specific steps include:

[0335] Step 1: The UE supports the shared RX chain capability and reports all supported CA configuration combinations. One type is supported by default, and the other type requires switching to shared RX chain for support.

[0336] Step 2: The network selects the configuration for the UE from the default supported CA configurations. The network instructs the UE on the blocker (i.e., the first signal) information between each carrier in each frequency band corresponding to this CA configuration.

[0337] Step 3: The UE detects the blocker's power and reports the corresponding information to the network when certain conditions are met, and then executes step 4a or step 4b.

[0338] Step 4a: When the network determines that it can switch to the shared RX chain, it sends relevant signaling (second information) to the UE; at the same time, it sends a new CA configuration (i.e., second carrier aggregation configuration) to the UE to instruct it to aggregate more CCs.

[0339] Step 5a: The UE switches to a shared RX chain, and the reception metric is relaxed to a certain level. Simultaneously, the UE uses the new CA configuration, and then proceeds to step 6.

[0340] Step 4b: If the network determines that it cannot switch to the shared RX chain link at this time, it will not issue relevant signaling.

[0341] Step 5b: The UE maintains the separate RX chain state and the CA configuration remains unchanged;

[0342] Step 6: The network determines that the shared RX chain can no longer be used between certain carriers;

[0343] Step 7: The network issues a new CA configuration, instructing the UE to revert to a single CC using an independent link state for all or part of its receive links. The receive metrics will change accordingly.

[0344] In other words, the UE uses the second link architecture and the second reception metric based on the new CA configuration (such as the fifth carrier aggregation configuration) issued by the network.

[0345] 2. In another implementation, the network instructs the UE to provide information on blocker category one between carriers in each frequency band corresponding to the CA configuration. The network also instructs the UE to provide information on blocker category two between unconfigured carriers and configured carriers in that frequency band. (This is consistent with the above.) Figure 14 Compared to the illustrated embodiment, the network can also determine whether an unconfigured carrier can share the RX link of a configured carrier based on the information reported by the UE.

[0346] See Figure 15 The specific steps include:

[0347] Step 1: The UE supports the shared RX chain capability and reports all supported CA configuration combinations. One type is supported by default, and the other type requires switching to shared RX chain for support.

[0348] Step 2: The network selects the configuration for the UE from the default supported CA configurations. The network instructs the UE on the blocker category 1 information between each CC in each frequency band corresponding to this CA configuration. The network instructs the UE on the blocker category 2 information between the unconfigured CCs and the configured CCs in this frequency band.

[0349] Step 3: The UE detects the power of blocker category 1 and blocker category 2. When certain conditions are met (e.g., the third condition), it reports the corresponding information (i.e., the fifth information) to the network, and then executes step 4a, step 4b, step 4c, or step 4d.

[0350] Step 4a: The network determines that only certain configured carriers can share the RX chain.

[0351] Step 5a: The network sends relevant signaling (e.g., second information) to the UE to instruct it to switch to the shared RX chain; at the same time, it sends a new CA configuration to the UE to instruct it to aggregate more carriers.

[0352] Step 6a: The UE switches to a shared RX chain, and the reception metric is relaxed to a certain level. Simultaneously, the UE uses the new CA configuration, and then proceeds to step 7.

[0353] Step 4b: The network determines that only certain unconfigured carriers can share the existing RX chain;

[0354] Step 5b: The network sends a new CA configuration to the UE to instruct it to aggregate more carriers; at the same time, it sends relevant signaling to instruct it to switch to the shared RX chain.

[0355] Step 6b: The UE switches to the shared RX chain, and the reception metric is relaxed to a certain level. Simultaneously, the UE uses the new CA configuration, and then proceeds to step 7.

[0356] Step 4c: The network determines that some configured carriers can share the RX chain, and some unconfigured carriers can also share the existing RX chain.

[0357] Step 5c: The network sends relevant signaling (e.g., second information) to the UE to instruct it to switch to the shared RX chain; at the same time, it sends a new CA configuration to the UE to instruct it to aggregate more carriers and share existing RX links.

[0358] Step 6c: The UE switches to the shared RX chain, and the reception metric is relaxed to a certain level. Simultaneously, the UE uses the new CA configuration, and then proceeds to step 7.

[0359] Step 4d: The network determines that there is no carrier and can share the RX chain;

[0360] Step 5d: If the network determines that it cannot switch to a shared RX chain link, then no relevant signaling will be issued.

[0361] Step 6d: The UE maintains the separate RX chain state and the CA configuration remains unchanged.

[0362] In other words, the UE uses a second link architecture.

[0363] Step 7: The network determines that the shared RX chain can no longer be used between certain carriers;

[0364] Step 8: The network issues a new CA configuration, instructing the UE to revert to a single carrier state, using only one link, for all or part of its receive links. The receive metrics will change accordingly.

[0365] In other words, the UE uses the second link architecture and the second reception metric based on the new CA configuration (such as the fifth carrier aggregation configuration) issued by the network.

[0366] 3. In another implementation, the network instructs the UE to provide blocker category one information between carriers in each frequency band corresponding to the CA configuration. The network instructs the UE to provide blocker category two information between unconfigured carriers and configured carriers in that frequency band. The network instructs the UE to provide blocker category three information between unconfigured CCs in that frequency band. Figure 11 Compared to the embodiment shown, the network can also determine whether unconfigured carriers can share an idle RX link based on the information reported by the UE.

[0367] See Figure 16 The specific steps include:

[0368] Step 1: The UE supports the shared RX chain capability and reports all supported CA configuration combinations. One type is supported by default, and the other type requires switching to a shared RX chain.

[0369] Step 2: The network selects the configuration for the UE from the default supported CA configurations.

[0370] The network instructs the UE to provide information on blocker category one for each CC within each frequency band corresponding to the CA configuration.

[0371] The network provides the UE with information on blocker category 2 between unconfigured and configured CCs in this frequency band.

[0372] The network instructs the UE to provide information about blocker category 3 between CCs that are not configured in this frequency band.

[0373] Step 3: The UE detects the power of blocker categories one, two, and three. When certain conditions are met (e.g., the third condition), it reports the corresponding information to the network and then executes step 4a, step 4b, step 4c, step 4d, step 4e, or step 4f.

[0374] Step 4a: The network determines that only certain configured CCs can share the RX chain;

[0375] Step 5a: The network sends relevant signaling (e.g., second information) to the UE to instruct it to switch to the shared RX chain;

[0376] At the same time, a new CA configuration is issued to the UE to instruct it to aggregate more carriers.

[0377] Step 6a: The UE switches to a shared RX chain, and the reception metric is relaxed to a certain level. Simultaneously, the UE uses the new CA configuration, and then proceeds to step 7.

[0378] In other words, the UE uses the first link architecture and the first reception metric.

[0379] Step 4b: The network determines that only certain unconfigured carriers can share the existing RX chain;

[0380] Step 5b: The network sends a new CA configuration (second carrier aggregation configuration) to the UE to instruct it to aggregate more carriers; at the same time, it sends relevant signaling (e.g., second information) to instruct it to switch to the shared RX chain.

[0381] Step 6b: The UE switches to the shared RX chain, and the reception metric is relaxed to a certain level. Simultaneously, the UE uses the new CA configuration, and then proceeds to step 7.

[0382] In other words, the UE uses the first link architecture and the first reception metric.

[0383] Step 4c: The network determines that some configured carriers can share the RX chain, and some unconfigured carriers can also share the existing RX chain;

[0384] Step 5c: The UE switches to a shared RX chain, and the reception metric is relaxed to a certain level. Simultaneously, the UE uses a new CA configuration.

[0385] Step 6c: The UE switches to the shared RX chain, and the reception metric is relaxed to a certain level. Simultaneously, the UE uses the new CA configuration, and then proceeds to step 7.

[0386] Step 4d: The network determines that certain configured carriers can share the RX chain, and that certain unconfigured carriers can also share the idle RX chain;

[0387] Step 5d: The network sends relevant signaling to the UE to instruct it to switch to the shared RX chain;

[0388] At the same time, a new CA configuration is issued to instruct it to aggregate more carriers, and the new carriers can share the idle RX links.

[0389] Step 6d: The UE switches to the shared RX chain, and the reception metric is relaxed to a certain level.

[0390] At the same time, the UE uses the new CA configuration and then performs step 7.

[0391] Step 4e: The network determines that some configured carriers can share the RX chain, some unconfigured carriers can also share the existing RX chain, and some unconfigured carriers can also share the idle RX chain;

[0392] Step 5e: The network sends relevant signaling to the UE to instruct it to switch to the shared RX chain; at the same time, it sends a new CA configuration to instruct it to aggregate more carriers, some of which can share existing RX links; and others can share idle RX links.

[0393] Step 6e: The UE switches to the shared RX chain, and the reception metric is relaxed to a certain level. Simultaneously, the UE uses the new CA configuration, and then proceeds to step 7.

[0394] Step 4f: The network determines that there is no carrier available to share the RX chain.

[0395] Step 5f: If the network determines that it cannot switch to a shared RX chain link, it will not issue relevant signaling.

[0396] Step 6f: The UE maintains the separate RX chain state and the CA configuration remains unchanged.

[0397] Step 7: The network determines that certain CCs can no longer use the shared RX chain;

[0398] Step 8: The network issues a new CA configuration, instructing the UE to revert to a single CC using an independent link state for all or part of its receive links. The receive metrics will change accordingly.

[0399] Example 7:

[0400] Based on Embodiments 3, 5, and 6, the information that the UE reports to the network side and the network makes judgments can include the following:

[0401] 1. The UE reports the measured power values ​​of blocker categories one to three to the network side. The network then determines the power relationship between blocker category one and the configured carriers, the power relationship between blocker category two and the unconfigured and configured carriers, and the power relationship between blocker category three and the unconfigured carriers.

[0402] 2. After the UE determines the power relationship between each blocker and the configured and unconfigured carriers, it reports some auxiliary judgment information (i.e., the fifth information) to the network side. The network side then determines whether to switch to a shared receive link. The auxiliary judgment information includes at least one of the following:

[0403] 1) Which of the configured carriers can be switched to a shared link?

[0404] 2) Which carriers can be newly added to the configuration, and how they can use links, such as: a newly added carrier can have a dedicated link, can share a link with an existing carrier, or several newly added carriers can share a link, etc.

[0405] 3) At this time, the link status cannot be switched, and one carrier will exclusively share one RX chain.

[0406] 4) The number of layers supported by the UE, and its changes can indicate the release of the UE's RX link.

[0407] 5) CA combinations of shared links recommended or preferred by the UE.

[0408] 6) Measurement results for blocker categories one through three.

[0409] Example 8:

[0410] Based on Embodiments 2, 3, 5, and 6, the measurement information for the blocker (first signal) configured by the network side for the UE includes at least one of the following:

[0411] 1. Configure the blocker's measurement information along with the Scell's measurement information.

[0412] 2. Configure the blocker's measurement information separately.

[0413] Example 9:

[0414] In the above embodiments, the UE can report information to the network side in several ways:

[0415] 1. The UE can report blocker (first signal) power information, first information, or fifth information in the following ways:

[0416] 1) Report through measurement reports, including one of the following methods:

[0417] a. Triggered reporting:

[0418] i. Reporting triggered by the blocker's reporting triggering condition (such as the third condition) being met (e.g., when the UE detects and determines that the power of one or more blockers meets the switching link condition);

[0419] ii. Reports triggered by certain reporting conditions of Scell ​​being met.

[0420] b. Periodic reporting:

[0421] i. The terminal periodically reports the power of each blocker obtained from the periodic detection;

[0422] ii. The terminal reports according to the Scell's reporting cycle;

[0423] 2) Reporting methods measured by idle or inactive state: Reporting triggered by network-side request information, such as through RRRCResmueComplete and UEInformationResponse.

[0424] 2. The UE can report the blocker's power information, first information, or fifth information, or it can report through auxiliary information, or it can report through MAC CE, etc.

[0425] Example 10:

[0426] In Example 9, the link is switched when the power of the blocker (first signal) meets the link switching conditions. The link switching refers to switching from an independent link (second link architecture) to a shared link (first link architecture), or switching from a shared link (first link architecture) back to an independent link (second link architecture).

[0427] Example 11:

[0428] The measurement information of the blocker (first signal) indicated by the network to the UE or the measurement results between the blocker and adjacent carriers reported by the UE to the network side are related to at least one of the following: measurement frequency band, measurement center frequency, measurement bandwidth, measurement duration, measurement period, measured power level, and measured PSD level.

[0429] Example 12:

[0430] In the above embodiments, the configured carrier switching to a shared RX chain includes at least one of the following:

[0431] 1. Multiple carriers configured in a certain frequency band share the same Rx chain.

[0432] 2. Some of the configured carriers share one Rx chain, while the others still use their own Rx chain.

[0433] 3. A portion of the configured multiple carriers share one Rx chain, while another portion shares another Rx chain.

[0434] Example 12:

[0435] In the above embodiments, there are several ways to relax the terminal reception requirements:

[0436] 1. The Rx requirements that need to be relaxed form a set of reception metrics. The two sets of metrics (metric set A (setA) and metric set B (setB)) correspond to two sets of Rx requirements respectively. SetA is the reception metrics corresponding to the case where shared RX chain is not supported, and setB is the relaxed reception metrics corresponding to the case where shared RX chain is supported.

[0437] 2. Based on at least one of the following: the number of aggregated carriers, the number of aggregated RX chains, the type of aggregated RX chains, and the power relationship between the first signal (blocker) and adjacent carriers, the relaxed first reception index corresponding to the shared RX chain can be further subdivided into several index sets, such as setB, setC, etc.

[0438] Example 13:

[0439] In the above embodiments, the reception indicators that need to be relaxed may include one or more of the following:

[0440] ΔRIBNC (allowed reference sensitivity relaxation due to support for in-band discontinuous CA operation), ACS (adjacent channel selectivity), in-band blocking.

[0441] Embodiment Fourteen of the present invention:

[0442] In Embodiments 3 and 6 above, when switching to a shared RX chain or when a UE can switch to a shared RX chain, it can also report to the network the number of layers it can support after switching link states. The network can also allocate the released link resources to the UE to support MIMO.

[0443] Example 15:

[0444] In Embodiments 1, 2, 3, 5, and 6 above, the UE indicates its ability to support shared RX chains by reporting frequency separation class information to the network, representing the frequency spacing between the lowest and highest frequency carriers of its supported non-contiguous carriers. The reporting method may include one of the following:

[0445] 1. The FreqSeparation class reported by a UE that supports the shared RX chain capability is different from that reported by a UE that does not support the shared RX chain capability (the reported bandwidth may be wider when the capability is supported). The network can determine whether the UE supports the shared RX chain capability by judging this information.

[0446] 2. For UEs that support the shared RX chain capability, a new FreqSeparation class-R19 capability is reported. This capability information represents the frequency spacing between the lowest frequency carrier and the highest frequency carrier of the non-contiguous carriers supported when supporting the shared RX chain.

[0447] Example 16:

[0448] In the above embodiments five and six, the measurement results of the first signal (blocker) can be obtained by the network itself, in addition to being reported by the UE to the network.

[0449] This application provides a communication processing apparatus. As an example, the communication processing apparatus may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the types of terminals listed above, and the network-side device may include, but is not limited to, the types of network-side devices listed above. This application does not impose specific limitations.

[0450] The communication processing device may include a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor may include a general-purpose processor, a special-purpose processor, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), an Artificial Intelligence (AI) processor, a Graphics Processing Unit (GPU), an Application Specific Integrated Circuit (ASIC), a Network Processor (NP), a Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules may be implemented by a communication interface, which may include one or more of the following: a transceiver, pins, circuits, a bus, and a radio frequency unit.

[0451] See Figure 17 The embodiments of this application provide a communication processing device applied to a terminal. The device 1700 includes: a first transceiver unit 1701 and a first processing unit 1702.

[0452] The first processing unit 1702 is used to communicate through a first link architecture; wherein the first link architecture refers to a shared receiving link used for some or all of the carriers in carrier aggregation.

[0453] In one embodiment of this application, the first processing unit 1702 is further configured to communicate via a second link architecture before communicating via the first link architecture;

[0454] The second link architecture refers to each carrier in carrier aggregation using an independent receiving link.

[0455] In one embodiment of this application, the communication performance under the first link architecture is represented by a first reception indicator, and the communication performance under the second link architecture is represented by a second reception indicator. The first reception indicator may be the same as or different from the second reception indicator.

[0456] In one embodiment of this application, the first processing unit 1702 is further configured to communicate through the first link architecture when a first condition is met, wherein the first condition is used by the terminal to determine whether to switch to the first link architecture.

[0457] In one embodiment of this application, the first processing unit 1702 is further configured to communicate through the second link architecture when a second condition is met, wherein the second condition is used by the terminal to determine whether to switch to the second link architecture.

[0458] In one embodiment of this application, the first transceiver unit 1701 is used to send first information to the network-side device when a second condition is met, the first information being used to determine the carrier aggregation configuration related to the second link architecture;

[0459] The first transceiver unit 1701 is used to receive the first carrier aggregation configuration sent by the network-side device and communicate through the second link architecture. The first carrier aggregation configuration corresponds to the reception index of the second link architecture.

[0460] In one embodiment of this application, the first transceiver unit 1701 is used to transmit at least one of the following:

[0461] Shared frequency band of the receiving link;

[0462] Shared receive link carrier;

[0463] An unconfigured carrier can share an existing receive link or an idle receive link.

[0464] In one embodiment of this application, a first transceiver unit 1701 is used to receive a second carrier aggregation configuration, which indicates new carriers that can be aggregated.

[0465] In one embodiment of this application, the new carrier can share an existing receiving link; or, the new carrier can share an idle receiving link; or, a portion of the new carriers can share an existing receiving link, and another portion of the new carriers can share an idle receiving link.

[0466] In one embodiment of this application, satisfying the first condition includes at least one of the following:

[0467] The terminal receives second information, which instructs the terminal to use the first link architecture.

[0468] The terminal did not receive the third information, which was used to indicate that the terminal was not allowed to use the first link architecture.

[0469] The terminal receives a third carrier aggregation configuration, which is associated with the reception metrics of the first link architecture;

[0470] The configured carrier frequency band is a specific frequency band;

[0471] The frequency spacing between configured adjacent carriers does not exceed the first value;

[0472] The power relationship between the first signal and the first carrier or the second carrier satisfies the third condition, wherein the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier;

[0473] The time difference between the received signals of the configured carriers satisfies the fourth condition.

[0474] In one embodiment of this application, the power relationship between the first signal and the first carrier or the second carrier satisfies a third condition, including at least one of the following:

[0475] The power of the first signal is not higher than the power of the first carrier or the second carrier than the second value;

[0476] The power spectral density of the first signal is not higher than the power spectral density of the first carrier or the second carrier than the third value.

[0477] In one embodiment of this application, satisfying the second condition includes at least one of the following:

[0478] The terminal receives third information, which indicates that the terminal is not allowed to use the first link architecture.

[0479] The terminal receives fourth information, which instructs the terminal to use the second link architecture.

[0480] The terminal receives a fourth carrier aggregation configuration, which is associated with the reception metrics of the second link architecture.

[0481] The configured carrier frequency band is not a specific frequency band;

[0482] The frequency spacing between configured adjacent carriers exceeds a first value;

[0483] The power relationship between the first signal and the first carrier or the second carrier does not satisfy the third condition. The first signal is a signal between the first carrier and the second carrier. The first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier.

[0484] The time difference between the received signals of the configured carriers does not satisfy the fourth condition.

[0485] In one embodiment of this application, a first transceiver unit 1701 is used to transmit first capability information, which indicates that the terminal has the capability to support a shared receiving link.

[0486] In one embodiment of this application, the first transceiver unit 1701 is used to transmit all frequency band combination information for carrier aggregation supported by the terminal;

[0487] The frequency band combination information for all carrier aggregation includes at least one of the following: frequency band combination information for carrier aggregation that the terminal supports by default, and frequency band combination information for carrier aggregation that the terminal supports when using the first link architecture.

[0488] In one embodiment of this application, the first transceiver unit 1701 is further configured to receive information from the first signal from the terminal;

[0489] Wherein, the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier.

[0490] In one embodiment of this application, the first transceiver unit 1701 is used to send fifth information, which is used by the network-side device to determine whether the terminal uses a first link architecture or a second link architecture.

[0491] In one embodiment of this application, the first information or the fifth information includes at least one of the following:

[0492] The sixth information is used to indicate a configured carrier that can use a shared receive link;

[0493] One or more new carriers, each of which uses an independent receive link, or the one or more new carriers share a receive link with the configured carriers, or the multiple new carriers share a receive link;

[0494] The seventh piece of information is used to indicate the use of a second link architecture;

[0495] The terminal supports information on the number of layers;

[0496] The carrier aggregation combination of the shared links recommended or preferred by the terminal;

[0497] The measurement result between the first signal and the second carrier or the second carrier.

[0498] In one embodiment of this application, the method of sending the first or fifth information includes at least one of the following:

[0499] Sending via measurement reports, sending via auxiliary information, sending via MAC CE, and sending in response to request information sent by the network-side device.

[0500] In one embodiment of this application, some or all of the carriers in the carrier aggregation use a shared receiving link, including: all carriers in the carrier aggregation share a single receiving link;

[0501] or,

[0502] A portion of the carriers in the carrier aggregation shares a single receive link, while each carrier in another portion of the carrier aggregation uses an independent receive link.

[0503] or,

[0504] A portion of the carriers in the carrier aggregation share a single receive link, while another portion of the carriers in the carrier aggregation share a different receive link.

[0505] In one embodiment of this application, the first reception indicator includes at least one set of relaxed reception indicators, and the second reception indicator includes at least one set of reception indicators.

[0506] In one embodiment of this application, the relaxed set of reception indicators includes at least one subset of reception indicators, which is determined based on at least one of the following: the number of aggregated carriers, the number of shared reception links, the type of reception links, and the power relationship between interference signals and adjacent carriers.

[0507] In one embodiment of this application, the information of the first signal, or the measurement result between the first signal and the second carrier or the second carrier, is related to at least one of the following: measurement frequency band, measurement center frequency, measurement bandwidth, measurement duration, measurement period, measured power level, and measured power spectral density (PSD) level.

[0508] Optionally, the terminal is suitable for at least one of the following scenarios:

[0509] 1) FDD-TDD ENDC;

[0510] 2) FDD-FDD ENDC;

[0511] 3) FDD-TDD uplink carrier aggregation;

[0512] 4) FDD-FDD uplink carrier aggregation;

[0513] 5) FDD-TDD SUL;

[0514] 6) FDD-FDD SUL.

[0515] The apparatus provided in this application embodiment can achieve... Figure 6 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0516] See Figure 18 The embodiments of this application provide a communication processing apparatus applied to a network-side device. The apparatus 1800 includes: a second transceiver unit 1801 and a second processing unit 1802.

[0517] The second transceiver unit 1801 is used to send second information to the terminal, and at least one of the third carrier aggregation configurations;

[0518] The second information is used to indicate the use of the first link architecture, and the third carrier aggregation configuration is associated with the reception metrics of the first link architecture, wherein the first link architecture refers to the use of a shared reception link for some or all carriers of the carrier aggregation.

[0519] In one embodiment of this application, the second transceiver unit 1801 is further configured to send at least one of the following to the terminal: third information, fourth information, first carrier configuration, and fourth carrier aggregation configuration;

[0520] The third information indicates that the terminal is not allowed to use the first link architecture, and the fourth information indicates that the terminal uses the second link architecture. The first carrier configuration or the fourth carrier aggregation configuration is associated with the reception index of the second link architecture, which refers to each carrier of the carrier aggregation using an independent reception link.

[0521] In one embodiment of this application, the communication performance under the first link architecture is represented by a first reception indicator, and the communication performance under the second link architecture is represented by a second reception indicator. The first reception indicator may be the same as or different from the second reception indicator.

[0522] In one embodiment of this application, the second transceiver unit 1801 is further configured to send a second carrier configuration to the terminal, the second carrier configuration being used to indicate new carriers that can be aggregated.

[0523] In one embodiment of this application, the new carrier can share an existing receiving link; or, the new carrier can share an idle receiving link; or, a portion of the new carriers can share an existing receiving link, and another portion of the new carriers can share an idle receiving link.

[0524] In one embodiment of this application, the second transceiver unit 1801 is further configured to receive first information sent by the terminal, the first information being used to determine a carrier aggregation configuration related to the second link architecture; and to send a first carrier aggregation configuration to the terminal, the first carrier aggregation configuration corresponding to the reception index of the second link architecture.

[0525] In one embodiment of this application, the second transceiver unit 1801 is further configured to acquire fifth information; and determine, based on the fifth information, whether the terminal uses a first link architecture or a second link architecture.

[0526] In one embodiment of this application, the first information or the fifth information includes at least one of the following:

[0527] The sixth information is used to indicate a configured carrier that can use a shared receive link;

[0528] One or more new carriers, each of which uses an independent receive link, or the one or more new carriers share a receive link with the configured carriers, or the multiple new carriers share a receive link;

[0529] The seventh piece of information is used to indicate the use of a second link architecture;

[0530] The terminal supports information on the number of layers;

[0531] The carrier aggregation combination of the shared links recommended or preferred by the terminal;

[0532] The measurement result between the first signal and the second carrier or the second carrier, wherein the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier.

[0533] Optionally, the network-side device is suitable for at least one of the following scenarios:

[0534] 1) FDD-TDD ENDC;

[0535] 2) FDD-FDD ENDC;

[0536] 3) FDD-TDD uplink carrier aggregation;

[0537] 4) FDD-FDD uplink carrier aggregation;

[0538] 5) FDD-TDD SUL;

[0539] 6) FDD-FDD SUL.

[0540] The apparatus provided in this application embodiment can achieve... Figure 7 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0541] like Figure 19 As shown, this application embodiment also provides a communication device 1900, including a processor 1901 and a memory 1902. The memory 1902 stores a program or instructions that can run on the processor 1901. For example, when the communication device 1900 is a terminal, the program or instructions executed by the processor 1901 implement the above-mentioned... Figure 6 The various steps of the illustrated method embodiment can achieve the same technical effect. When the communication device 1900 is a network-side device, the program or instructions executed by the processor 1901 implement the above-described steps. Figure 7 The steps of the method embodiment shown are the same and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0542] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 6 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 17 The communication processing device shown. Specifically, Figure 20 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0543] The terminal 2000 includes, but is not limited to, at least some of the following components: radio frequency unit 2001, network module 2002, audio output unit 2003, input unit 2004, sensor 2005, display unit 2006, user input unit 2007, interface unit 2008, memory 2009, and processor 2010.

[0544] Those skilled in the art will understand that the terminal 2000 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 2010 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 20 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0545] It should be understood that, in this embodiment, the input unit 2004 may include a graphics processor 20041 and a microphone 20042. The graphics processor 20041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 2006 may include a display panel 20061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 2007 includes at least one of a touch panel 20071 and other input devices 20072. The touch panel 20071 is also called a touch screen. The touch panel 20071 may include a touch detection device and a touch controller. Other input devices 20072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0546] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 2001 can transmit it to the processor 2010 for processing; in addition, the radio frequency unit 2001 can send uplink data to the network-side device. Typically, the radio frequency unit 2001 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0547] The memory 2009 can be used to store software programs or instructions, as well as various data. The memory 2009 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 2009 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1809 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0548] Processor 2010 may include one or more processing units; optionally, processor 2010 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 2010.

[0549] The processor 2010 is used for communication via a first link architecture; wherein the first link architecture refers to a shared receiving link used for some or all of the carriers in carrier aggregation.

[0550] In one embodiment of this application, the processor 2010 is also configured to communicate via a second link architecture before communicating via a first link architecture;

[0551] The second link architecture refers to each carrier in carrier aggregation using an independent receiving link.

[0552] In one embodiment of this application, the communication performance under the first link architecture is represented by a first reception indicator, and the communication performance under the second link architecture is represented by a second reception indicator. The first reception indicator may be the same as or different from the second reception indicator.

[0553] In one embodiment of this application, the processor 2010 is further configured to communicate through the first link architecture when a first condition is met, wherein the first condition is used by the terminal to determine whether to switch to the first link architecture.

[0554] In one embodiment of this application, the processor 2010 is further configured to communicate via the second link architecture when a second condition is met, the second condition being used by the terminal to determine whether to switch to the second link architecture.

[0555] It is understood that the implementation process of each implementation method mentioned in this embodiment can be referred to Figure 6 The relevant descriptions of the method embodiments shown herein, which achieve the same or corresponding technical effects, will not be repeated here to avoid duplication.

[0556] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 7 The steps of the method embodiment shown are illustrated. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0557] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 21 The location information acquisition device shown. Figure 21 As shown, the network-side device 2100 includes: an antenna 2101, a radio frequency (RF) device 2102, a baseband device 2103, a processor 2104, and a memory 2105. The antenna 2101 is connected to the RF device 2102. In the uplink direction, the RF device 2102 receives information through the antenna 2101 and sends the received information to the baseband device 2103 for processing. In the downlink direction, the baseband device 2103 processes the information to be transmitted and sends it to the RF device 2102. The RF device 2102 processes the received information and then transmits it through the antenna 2101.

[0558] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 2103, which includes a baseband processor.

[0559] The baseband device 2103 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 21 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 2105 via a bus interface to call the program in the memory 2105 and execute the network device operation shown in the above method embodiment.

[0560] The network-side device may also include a network interface 2106, such as a Common Public Radio Interface (CPRI).

[0561] Specifically, the network-side device 2100 in this application embodiment further includes: instructions or programs stored in memory 2105 and executable on processor 2104, wherein processor 2104 calls the instructions or programs in memory 2105 to execute. Figure 18 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0562] Optionally, the radio frequency device 2102 is used to send second information to the terminal, and at least one of the third carrier aggregation configuration;

[0563] The second information is used to indicate the use of the first link architecture, and the third carrier aggregation configuration is associated with the reception metrics of the first link architecture, wherein the first link architecture refers to the use of a shared reception link for some or all carriers of the carrier aggregation.

[0564] In one embodiment of this application, the radio frequency device 2102 is further configured to send at least one of the following to the terminal: third information, fourth information, first carrier configuration, and fourth carrier aggregation configuration;

[0565] The third information indicates that the terminal is not allowed to use the first link architecture, and the fourth information indicates that the terminal uses the second link architecture. The first carrier configuration or the fourth carrier aggregation configuration is associated with the reception index of the second link architecture, which refers to each carrier of the carrier aggregation using an independent reception link.

[0566] In one embodiment of this application, the communication performance under the first link architecture is represented by a first reception indicator, and the communication performance under the second link architecture is represented by a second reception indicator. The first reception indicator may be the same as or different from the second reception indicator.

[0567] In one embodiment of this application, the radio frequency device 2102 is further configured to send a second carrier configuration to the terminal, the second carrier configuration being configured to indicate new carriers that can be aggregated.

[0568] In one embodiment of this application, the new carrier can share an existing receiving link; or, the new carrier can share an idle receiving link; or, a portion of the new carriers can share an existing receiving link, and another portion of the new carriers can share an idle receiving link.

[0569] It is understood that the implementation process of each implementation method mentioned in this embodiment can be referred to Figure 7 The relevant descriptions of the method embodiments shown herein, which achieve the same or corresponding technical effects, will not be repeated here to avoid duplication.

[0570] This application embodiment also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the above-described functionality. Figure 6 or Figure 7 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0571] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0572] This application embodiment also provides a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the above. Figure 6 or Figure 7 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0573] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0574] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the above. Figure 6 or Figure 7 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0575] This application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the functions provided in this application embodiment. Figure 6 The steps of the method shown can be performed by the network-side device as provided in the embodiments of this application. Figure 7 The steps of the method shown.

[0576] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0577] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0578] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A communication processing method, characterized in that, include: The terminals communicate through the first link architecture; The first link architecture refers to a carrier aggregation where some or all carriers use a shared receiving link.

2. The method according to claim 1, characterized in that, Before the terminal communicates via the first link architecture, the method further includes: The terminal communicates via a second link architecture; The second link architecture refers to each carrier in carrier aggregation using an independent receiving link.

3. The method according to claim 2, characterized in that, The communication performance under the first link architecture is represented by a first reception metric, and the communication performance under the second link architecture is represented by a second reception metric. The first reception metric and the second reception metric may be the same or different.

4. The method according to claim 1 or 2, characterized in that, The terminal communicates via a first link architecture, including: If the first condition is met, the terminal communicates through the first link architecture, whereby the first condition is used by the terminal to determine whether to switch to the first link architecture.

5. The method according to claim 1, characterized in that, After the terminal communicates via the first link architecture, the method further includes: If the second condition is met, the terminal communicates through the second link architecture, and the second condition is used by the terminal to determine whether to switch to the second link architecture.

6. The method according to claim 5, characterized in that, When the second condition is met, the terminal communicates through the second link architecture, including: If the second condition is met, the terminal sends first information to the network-side device, the first information being used to determine the carrier aggregation configuration related to the second link architecture; The terminal receives a first carrier aggregation configuration sent by the network-side device. The terminal communicates through a second link architecture, and the first carrier aggregation configuration corresponds to the reception index of the second link architecture.

7. The method according to claim 1 or 2, characterized in that, The method further includes: The terminal sends at least one of the following: Shared frequency band of the receiving link; Shared receive link carrier; An unconfigured carrier can share an existing receive link or an idle receive link.

8. The method according to claim 1 or 2, characterized in that, The method further includes: The terminal receives a second carrier aggregation configuration, which indicates new carriers that can be aggregated.

9. The method according to claim 8, characterized in that, The new carrier can share an existing receiving link; or, the new carrier can share an idle receiving link; or, a portion of the new carriers can share an existing receiving link, and another portion of the new carriers can share an idle receiving link.

10. The method according to claim 4, characterized in that, The first condition being met includes at least one of the following: The terminal receives second information, which instructs the terminal to use the first link architecture. The terminal did not receive the third information, which was used to indicate that the terminal was not allowed to use the first link architecture. The terminal receives a third carrier aggregation configuration, which is associated with the reception metrics of the first link architecture; The configured carrier frequency band is a specific frequency band; The frequency spacing between configured adjacent carriers does not exceed the first value; The power relationship between the first signal and the first carrier or the second carrier satisfies the third condition, wherein the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier; The time difference between the received signals of the configured carriers satisfies the fourth condition.

11. The method according to claim 10, characterized in that, The power relationship between the first signal and the first carrier or the second carrier satisfies a third condition, including at least one of the following: The power of the first signal is not higher than the power of the first carrier or the second carrier than the second value; The power spectral density of the first signal is not higher than the power spectral density of the first carrier or the second carrier than the third value.

12. The method according to claim 5 or 6, characterized in that, The second condition being met includes at least one of the following: The terminal receives third information, which indicates that the terminal is not allowed to use the first link architecture. The terminal receives fourth information, which instructs the terminal to use the second link architecture. The terminal receives a fourth carrier aggregation configuration, which is associated with the reception metrics of the second link architecture. The configured carrier frequency band is not a specific frequency band; The frequency spacing between configured adjacent carriers exceeds a first value; The power relationship between the first signal and the first carrier or the second carrier does not satisfy the third condition. The first signal is a signal between the first carrier and the second carrier. The first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier. The time difference between the received signals of the configured carriers does not satisfy the fourth condition.

13. The method according to claim 1 or 2, characterized in that, The method further includes: The terminal sends first capability information, which indicates that the terminal has the capability to support a shared receive link.

14. The method according to claim 1, 2, or 5, characterized in that, The method further includes: The terminal sends information on all frequency band combinations supported by the terminal for carrier aggregation; The frequency band combination information for all carrier aggregation includes at least one of the following: frequency band combination information for carrier aggregation that the terminal supports by default, and frequency band combination information for carrier aggregation that the terminal supports when using the first link architecture.

15. The method according to claim 14, characterized in that, The method further includes: The terminal receives information from the first signal; Wherein, the first signal is a signal between a first carrier and a second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier.

16. The method according to claim 15, characterized in that, The method further includes; The terminal sends a fifth piece of information, which is used by the network-side device to determine whether the terminal uses a first link architecture or a second link architecture.

17. The method according to claim 6 or 16, characterized in that, The first information or the fifth information includes at least one of the following: The sixth information is used to indicate a configured carrier that can use a shared receive link; One or more new carriers, each of which uses an independent receive link, or the one or more new carriers share a receive link with the configured carriers, or the multiple new carriers share a receive link; The seventh piece of information is used to indicate the use of a second link architecture; The terminal supports the number of layers; The carrier aggregation combination of the shared links recommended or preferred by the terminal; The measurement result between a first signal and a second carrier or a second carrier, wherein the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier.

18. The method according to claim 6 or 16, characterized in that, The first or fifth information may be sent in at least one of the following ways: via measurement report, via auxiliary information, via MAC CE, or in response to a request message sent by the network-side device.

19. The method according to claim 1, characterized in that, The carrier aggregation uses a shared receiving link for some or all of its carriers, including: all carriers in the carrier aggregation share a single receiving link; or, A portion of the carriers in the carrier aggregation shares a single receive link, while each carrier in another portion of the carrier aggregation uses an independent receive link. or, A portion of the carriers in the carrier aggregation share a single receive link, while another portion of the carriers in the carrier aggregation share a different receive link.

20. The method according to claim 3, characterized in that, The first reception indicator includes at least one set of relaxed reception indicators, and the second reception indicator includes at least one set of reception indicators.

21. The method according to claim 20, characterized in that, The relaxed set of reception indicators includes at least one subset of reception indicators, which is determined based on at least one of the following: the number of aggregated carriers, the number of shared reception links, the type of reception links, and the power relationship between the interference signal and adjacent carriers.

22. The method according to claim 16, characterized in that, The information of the first signal, or the measurement result between the first signal and the second carrier, is related to at least one of the following: measurement frequency band, measurement center frequency, measurement bandwidth, measurement duration, measurement period, measured power level, and measured power spectral density (PSD) level.

23. The method according to any one of claims 1 to 22, characterized in that, The method is applicable to at least one of the following scenarios: Frequency Division Duplex (FDD) - Time Division Duplex (TDD) Dual-Connection ENDC; FDD-FDD ENDC; FDD-TDD uplink carrier aggregation; FDD-FDD uplink carrier aggregation; FDD-TDD assisted uplink SUL; FDD-FDD SUL.

24. A communication processing method, characterized in that, include: The network-side device sends the second information to the terminal, and at least one of the third carrier aggregation configurations; The second information is used to indicate the use of the first link architecture, and the third carrier aggregation configuration is associated with the reception metrics of the first link architecture, wherein the first link architecture refers to the use of a shared reception link for some or all carriers of the carrier aggregation.

25. The method according to claim 24, characterized in that, The method further includes: The network-side device sends at least one of the following to the terminal: third information, fourth information, first carrier configuration, and fourth carrier aggregation configuration; The third information indicates that the terminal is not allowed to use the first link architecture, and the fourth information indicates that the terminal uses the second link architecture. The first carrier configuration or the fourth carrier aggregation configuration is associated with the reception index of the second link architecture, which means that each carrier of the carrier aggregation uses an independent reception link.

26. The method according to claim 25, characterized in that, The communication performance under the first link architecture is represented by a first reception metric, and the communication performance under the second link architecture is represented by a second reception metric. The first reception metric and the second reception metric may be the same or different.

27. The method according to claim 24, characterized in that, The method further includes: The network-side device sends a second carrier configuration to the terminal, the second carrier configuration being used to indicate new carriers that can be aggregated.

28. The method according to claim 27, characterized in that, The new carrier can share an existing receiving link; or, the new carrier can share an idle receiving link; or, a portion of the new carriers can share an existing receiving link, and another portion of the new carriers can share an idle receiving link.

29. The method according to claim 24 or 25, characterized in that, The method further includes: The network-side device receives first information sent by the terminal, the first information being used to determine carrier aggregation configuration related to the second link architecture; The network-side device sends a first carrier aggregation configuration to the terminal, and the first carrier aggregation configuration corresponds to the reception index of the second link architecture.

30. The method according to claim 24 or 25, characterized in that, The method further includes: The network-side device obtains the fifth piece of information; The network-side device determines whether the terminal uses a first link architecture or a second link architecture based on the fifth information.

31. The method according to claim 29 or 30, characterized in that, The first or fifth information includes at least one of the following: The sixth information is used to indicate a configured carrier that can use a shared receive link; One or more new carriers, each of which uses an independent receive link, or the one or more new carriers share a receive link with the configured carriers, or the multiple new carriers share a receive link; The seventh piece of information is used to indicate the use of a second link architecture; The terminal supports the number of layers; The carrier aggregation combination of the shared links recommended or preferred by the terminal; The measurement result between a first signal and a second carrier or a second carrier, wherein the first signal is a signal between the first carrier and the second carrier, the first carrier and the second carrier are configured carriers, or the first carrier and the second carrier are unconfigured carriers, or the first carrier is a configured carrier and the second carrier is an unconfigured carrier.

32. The method according to claim 31, characterized in that, The measurement result between the first signal and the second carrier or between the second carriers is reported by the terminal or determined by the network-side device.

33. The method according to any one of claims 24 to 32, characterized in that, The method is applicable to at least one of the following scenarios: FDD-TDD ENDC; FDD-FDD ENDC; FDD-TDD uplink carrier aggregation; FDD-FDD uplink carrier aggregation; FDD-TDD SUL; FDD-FDD SUL.

34. A communication processing device, characterized in that, include: First transceiver unit and first processing unit; The first processing unit is used to communicate through a first link architecture; wherein, the first link architecture refers to a shared receiving link used for some or all of the carriers in carrier aggregation.

35. The apparatus according to claim 34, characterized in that, The first processing unit is also configured to communicate via the second link architecture before communicating via the first link architecture; The second link architecture refers to each carrier in carrier aggregation using an independent receiving link.

36. A communication processing apparatus, comprising: Second transceiver unit and second processing unit; The second transceiver unit is used to send second information to the terminal, and at least one of the third carrier aggregation configurations; The second information is used to indicate the use of the first link architecture, and the third carrier aggregation configuration is associated with the reception metrics of the first link architecture, wherein the first link architecture refers to the use of a shared reception link for some or all carriers of the carrier aggregation.

37. The apparatus according to claim 36, characterized in that, The second transceiver unit is also configured to send at least one of the following to the terminal: third information, fourth information, first carrier configuration, and fourth carrier aggregation configuration; The third information indicates that the terminal is not allowed to use the first link architecture, and the fourth information indicates that the terminal uses the second link architecture. The first carrier configuration or the fourth carrier aggregation configuration is associated with the reception index of the second link architecture, which means that each carrier of the carrier aggregation uses an independent reception link.

38. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1 to 23.

39. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions, when executed by the processor, implement the steps of the method as described in any one of claims 24 to 32.

40. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 32.

41. A computer program product, characterized in that, The computer program product is stored in a storage medium, and the computer program product is executed by at least one processor to implement the steps of the method as described in any one of claims 1 to 32.

Images