Carrier switching method and apparatus, message sending method and apparatus, and terminal and network-side device

Abstract

The present application belongs to the technical field of communications. Disclosed are a carrier switching method and apparatus, a message sending method and apparatus, and a terminal and a network-side device. The carrier switching method in the embodiments of the present application comprises: a terminal switching between two scenarios, wherein the switching between the two scenarios comprises: downlink reception switching from a first carrier to a second carrier, or downlink reception switching from the second carrier to the first carrier.

Description

Carrier switching method, message sending method, apparatus, terminal and network-side equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411973311.6, filed in China on December 30, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a carrier switching method, a message sending method, an apparatus, a terminal, and network-side equipment. Background Technology

[0004] In some related technologies, carrier switching schemes are used for uplink transmission, meaning only the uplink carrier is switched; this is called uplink switching. This limits the switching scenarios to those where the uplink carrier changes, restricting the switching scenarios and resulting in relatively poor communication performance of the terminal. Summary of the Invention

[0005] This application provides a carrier switching method, a message sending method, an apparatus, a terminal, and a network-side device, which can solve the problem of poor communication performance of the terminal.

[0006] Firstly, a carrier switching method is provided, including:

[0007] The terminal switches between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0008] Secondly, a message sending method is provided, including:

[0009] The network-side device sends a first message to the terminal, which instructs the terminal to switch between two scenarios. The switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0010] Thirdly, a carrier switching device is provided, comprising:

[0011] The processing module is used to switch between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0012] Fourthly, a message sending device is provided, comprising:

[0013] The sending module is used to send a first message to the terminal, the first message being used to instruct the terminal to switch between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0014] Fifthly, a carrier switching apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect.

[0015] In a sixth aspect, a message sending apparatus is provided, the apparatus being configured to perform the steps of the method described in the second aspect.

[0016] In a seventh aspect, a terminal is provided, the terminal 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.

[0017] Eighthly, a terminal is provided, including a processor and a communication interface, wherein the processor is used to switch between two scenarios, wherein switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0018] In a ninth aspect, a network-side device is provided, the terminal 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.

[0019] In a tenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send a first message to a terminal, the first message being used to instruct the terminal to switch between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0020] Eleventhly, 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 as described in the first aspect, or the program or instructions, when executed by a processor, implement the steps of the method as described in the second aspect.

[0021] 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.

[0022] 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 perform the steps of the method as described in the first aspect, or the computer program / program product is executed by at least one processor to perform the steps of the method as described in the second aspect.

[0023] In a fourteenth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the carrier switching method provided in the embodiments of this application, and the network-side device is configured to perform the steps of the message sending method provided in the embodiments of this application.

[0024] In this embodiment, the terminal switches between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier. Because the switching between the two scenarios includes switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier, the terminal is able to perform downlink carrier switching, enabling it to switch between more scenarios and thus improving its communication performance. Attached Figure Description

[0025] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0026] Figure 2 is a flowchart of a carrier switching method provided in an embodiment of this application;

[0027] Figure 3 is a flowchart of a message sending method provided in an embodiment of this application;

[0028] Figure 4 is a schematic diagram of a carrier switching time domain mode provided in an embodiment of this application;

[0029] Figure 5 is a schematic diagram of a carrier switching time domain mode provided in an embodiment of this application;

[0030] Figure 6 is a schematic diagram of a carrier switching time domain mode provided in an embodiment of this application;

[0031] Figure 7 is a schematic diagram of a carrier switching device provided in an embodiment of this application;

[0032] Figure 8 is a schematic diagram of a message sending device provided in an embodiment of this application;

[0033] Figure 9 is a schematic diagram of a communication device provided in an embodiment of this application;

[0034] Figure 10 is a schematic diagram of a terminal provided in an embodiment of this application;

[0035] Figure 11 is a schematic diagram of a network-side device provided in an embodiment of this application. Detailed Implementation

[0036] 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.

[0037] 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.

[0038] 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 the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0039] It is worth noting that the technologies described in this application are 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. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems 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) radio systems. th Generation 6G communication system.

[0040] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and 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), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, 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 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as 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), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0041] 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 (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0042] 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).

[0043] The carrier switching method, apparatus, and terminal provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0044] Please refer to Figure 2, which is a flowchart of a carrier switching method provided in an embodiment of this application. As shown in Figure 2, it includes the following steps:

[0045] Step 201: The terminal switches between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from the first carrier to the second carrier, or switching downlink reception from the second carrier to the first carrier.

[0046] The aforementioned downlink reception switching from the first carrier to the second carrier can be either a complete switch of downlink reception from the first carrier to the second carrier, or a partial switch of downlink reception from the first carrier to the second carrier. For example, if the terminal has two downlink receptions on the first carrier, one of the downlink receptions can be switched from the first carrier to the second carrier.

[0047] Similarly, the downlink reception switching from the second carrier to the first carrier can be a complete switch of downlink reception from the second carrier to the first carrier, or a partial switch of downlink reception from the second carrier to the first carrier.

[0048] In some implementations, step 201 further includes performing downlink reception.

[0049] In the case where downlink reception is switched from the first carrier to the second carrier, the downlink reception described above is performed on the second carrier, or a portion of downlink reception is performed on the second carrier and another portion of downlink reception is performed on the first carrier.

[0050] When downlink reception switches from the second carrier to the first carrier, the downlink reception described above can be performed on the first carrier, or a portion of downlink reception can be performed on the first carrier and another portion on the second carrier.

[0051] It should be noted that the aforementioned terminal switching between two scenarios and performing downlink reception can also be referred to as:

[0052] The terminal switches between two carriers for downlink reception, wherein the switching between the two carriers includes: switching downlink reception from the first carrier to the second carrier, or switching downlink reception from the second carrier to the first carrier; or,

[0053] The terminal switches between a first carrier and a second carrier and performs downlink reception. The switching between the first carrier and the second carrier includes: switching downlink reception from the first carrier to the second carrier, or switching downlink reception from the second carrier to the first carrier.

[0054] In some implementations, the switching to the first carrier may be a fallback to the first carrier, and the switching to the second carrier may be a fallback to the second carrier.

[0055] In some implementations, the first carrier may be a normal downlink (NDL) carrier or a supplementary downlink (SDL) carrier.

[0056] In some implementations, the second carrier may be an SDL carrier or an NDL carrier.

[0057] In the embodiments of this application, since the switching between two scenarios includes: switching downlink reception from the first carrier to the second carrier, or switching downlink reception from the second carrier to the first carrier, the terminal is able to perform downlink carrier switching, so that the terminal can switch between more scenarios, thereby improving the communication performance of the terminal.

[0058] It should be noted that, in the embodiments of this application, the first carrier and the second carrier are not limited. For example, in some embodiments, one of the first carrier and the second carrier satisfies at least one of the following:

[0059] Primary cell (PCell) or primary secondary cell (PSCell);

[0060] The duplex mode is Frequency Division Duplex (FDD);

[0061] The first carrier and the other carrier of the second carrier satisfy at least one of the following:

[0062] Secondary Cell (SCell);

[0063] For SDL carrier.

[0064] For example, the first carrier is PCell or PSCell, or the first carrier operates in FDD mode with paired uplink and downlink spectrum, and the second carrier is SCell or SDL carrier; or the second carrier is PCell or PSCell, and the first carrier is SCell or SDL carrier; in this embodiment, the first carrier is mainly PCell or PSCell, and the second carrier is SCell or SDL carrier for illustration.

[0065] In some implementations, for the SCell described above (e.g., the second carrier is the SCell), the SCell has at least one of the following characteristics:

[0066] It can be activated; go ahead and activate it.

[0067] The sleep bandwidth portion (BWP) can be configured;

[0068] Terminals cannot camp on or access a cell on an SCell (e.g., the second carrier mentioned above);

[0069] Control resource set (CORESET) #0 will not be configured on the SCell (e.g., the second carrier mentioned above);

[0070] The Type 0 / 0A / 1 / 2 Common Search Space (CSS) will not be configured on the SCell (e.g., the second carrier mentioned above). For example, the terminal will not monitor the Type 0 / 0A / 1 / 2 CSS on the second carrier.

[0071] The SSB on a SCell (e.g., the second carrier mentioned above) can only be at least one of the non-Cell Defining SSBs (NCD-SSB).

[0072] In some implementations, for the aforementioned SDL carrier (e.g., the second carrier is SDL), the SDL carrier has at least one of the following characteristics:

[0073] SDL carriers (e.g., second carriers) cannot be deactivated;

[0074] SDL carriers (e.g., second carriers) cannot be configured or have a dormant BWP;

[0075] The terminal can camp on or access the cell on an SDL carrier (e.g., the second carrier);

[0076] CORESET#0 can be configured on the SDL carrier (e.g., the second carrier), and at least one CSS of Type 0 / 0A / 1 / 2CSS can be configured on the SDL carrier (e.g., the second carrier). For example, when Type 1CSS is configured on the SDL carrier (e.g., the second carrier), if the terminal initiates random access on the first carrier, that is, the Physical Random Access Channel (PRACH) is transmitted on the first carrier, the terminal can monitor the scheduling of Message 2 (Msg2) of the PRACH on the Type 1CSS configured on the SDL carrier (e.g., the second carrier). As another example, when Type 2CSS is configured on the SDL carrier (e.g., the second carrier), if the terminal hears a paging message for itself on the SDL carrier (e.g., the second carrier), the terminal can switch back to the first carrier to initiate random access, that is, the PRACH is transmitted on the first carrier.

[0077] The frequency domain offset indicated by the NCD-SSB on the SDL carrier (e.g., the second carrier) corresponds to the Cell Defining SSB (CD-SSB) of carrier 1, which is the Global Synchronization Channel Number (GSCN) deviation between the NCD-SSB of the SDL carrier (e.g., the second carrier) and the CD-SSB of the first carrier: that is, the SSB of the SDL carrier (e.g., the second carrier) indicates that the terminal tunes to the first carrier for initial access or cell selection;

[0078] The SSB on the SDL carrier (e.g., the second carrier) can be a CD-SSB. For example, when the network-side device configures a CD-SSB on the SDL carrier (e.g., the second carrier), except for the frequency domain resource location, other configurations such as time domain resources, SSB index, power, period, etc. are the same as those on the first carrier; the system or common information transmitted on the SDL carrier (e.g., the second carrier) is the same as the system or common information transmitted on the first carrier.

[0079] The SDL carrier (e.g., the second carrier) has no SSB, or carrier 2 is an SSB-less Scell, characterized by at least one of the following:

[0080] There is no SSB on the SDL carrier (e.g., the second carrier);

[0081] The SDL carrier (e.g., the second carrier) does not have a synchronization signal / physical broadcast channel block measurement timing configuration (SS / PBCH block measurement timing configuration, SMTC).

[0082] As an optional implementation, in one of the two scenarios, the terminal performs uplink transmission between the first carrier and the second carrier, or performs uplink transmission on both the first carrier and the second carrier, but does not perform uplink transmission in the other scenario. That is, the terminal performs uplink transmission in one of the two scenarios and does not perform uplink transmission in the other scenario; or

[0083] The terminal sends uplink data in both scenarios.

[0084] The aforementioned uplink transmission can also be called uplink transmission, and the downlink reception can also be called downlink transmission.

[0085] The aforementioned uplink transmission between the first carrier and the second carrier may be performed by the terminal before the handover, and the terminal may pause or stop uplink transmission after the handover; or the terminal may have paused or stopped uplink transmission before the handover, and the terminal may resume uplink transmission or start a new uplink transmission after the handover.

[0086] The fact that the aforementioned terminal transmits uplink data in both scenarios could mean that the uplink transmission remained unchanged before and after the switch, or that the uplink transmission was switched.

[0087] In the above embodiments, uplink transmission can be changed accordingly when downlink switching is performed, so as to further improve the communication performance of the terminal.

[0088] As an optional implementation, the switching between the two scenarios includes one of the following:

[0089] Switch from the first scene to the second scene, or switch from the second scene to the first scene;

[0090] Switch from the first scene to the third scene, or switch from the third scene to the first scene;

[0091] Switch from the first scene to the fourth scene, or switch from the fourth scene to the first scene;

[0092] Switch from the third scene to the fourth scene, or switch from the fourth scene to the third scene;

[0093] In the first scenario, the terminal performs uplink transmission and downlink reception on the first carrier, and does not perform uplink transmission and downlink reception on the second carrier.

[0094] In the second scenario, the terminal does not perform uplink transmission and downlink reception on the first carrier, the terminal performs downlink reception on the second carrier, and the terminal does not perform uplink transmission on the second carrier;

[0095] In the third scenario, the terminal performs downlink reception on the first carrier and does not perform uplink transmission on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier.

[0096] In the fourth scenario, the terminal performs uplink transmission on the first carrier and does not perform downlink reception on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier.

[0097] The above-mentioned uplink transmission and downlink reception on the carrier can also be referred to as uplink transmission on the carrier, and the absence of uplink transmission and downlink reception on the carrier can also be referred to as no uplink transmission and downlink reception on the second carrier.

[0098] For example, the above scenarios can be defined as follows:

[0099] In the first scenario, the terminal has uplink transmission and downlink reception on the first carrier, but the terminal does not have uplink transmission and downlink reception on the second carrier.

[0100] In the second scenario, the terminal does not transmit uplink or receive downlink on the first carrier, the terminal receives downlink on the second carrier, and the terminal does not transmit uplink on the second carrier;

[0101] In the third scenario, the terminal receives downlink on the first carrier but does not transmit uplink on the first carrier; the terminal receives downlink on the second carrier but does not transmit uplink on the second carrier.

[0102] In the fourth scenario, the terminal transmits uplink on the first carrier but does not receive downlink on the first carrier; the terminal receives downlink on the second carrier but does not transmit uplink on the second carrier.

[0103] Taking the first carrier as carrier 1 (e.g., NDL) as an example, the above four scenarios will be illustrated:

[0104] The first scenario (Case 1) above: Carrier 1 has uplink transmission (e.g., uplink transmission with 1 antenna) and downlink reception (e.g., downlink reception with 2 or 4 antennas), that is, carrier 1 has 1 uplink transmission (Transmission, Tx) / 2 or 4 downlink receptions (Reception, Rx) and carrier 2 has neither uplink transmission nor downlink reception (e.g., 0Tx / 0Rx), where Tx represents uplink transmission and Rx represents downlink reception;

[0105] The second scenario (Case 2) above: there is no uplink transmission or downlink reception on carrier 1 (e.g., 0Tx / 0Rx), and only downlink reception on carrier 2 (e.g., downlink reception with 2 or 4 antennas). There is no uplink transmission on carrier 2, i.e., carrier 2 is 0Tx / 2 or 4Rx.

[0106] The third scenario (Case 3) above: There is no uplink transmission on carrier 1, no uplink transmission on carrier 2, but there is downlink transmission on both carrier 1 and carrier 2;

[0107] The fourth scenario (Case 4) above: there is uplink transmission on carrier 1, no uplink transmission on carrier 2, no downlink transmission on carrier 1, and downlink transmission on carrier 2.

[0108] Switching from the first scene to the second scene; switching from the second scene to the first scene can be done as follows:

[0109] (NDL 1Tx / 2Rx+SDL 0Tx / 0Rx<->NDL 0Tx / 0Rx+SDL 0Tx / 2Rx);

[0110] Switching from the first scene to the third scene; switching from the third scene to the first scene can be done as follows:

[0111] (NDL 1Tx / 2Rx+SDL 0Tx / 0Rx<->NDL 0Tx / 1Rx+SDL 0Tx / 1Rx);

[0112] Among them, switching from the first scenario to the third scenario; switching from the third scenario to the first scenario can be applied when the uplink and downlink frequency bands of the Normal Uplink (NUL) are relatively close, requiring that the uplink of NUL and the downlink of SDL are not transmitted simultaneously.

[0113] Switching from the first scene to the fourth scene; switching from the fourth scene to the first scene can be done as follows:

[0114] (NDL 1Tx / 2Rx+SDL 0Tx / 0Rx<->NDL 1Tx / 0Rx+SDL 0Tx / 2Rx);

[0115] Switching from scenario one to scenario four; switching from scenario four to scenario one is applicable when the uplink / downlink of NUL and the downlink of SDL are far apart. When NUL downlink and SDL share the UE's Rx, it is required that NUL downlink and SDL downlink are not transmitted simultaneously, but NUL uplink and SDL downlink can be transmitted simultaneously.

[0116] Switching from the third scene to the fourth scene; switching from the fourth scene to the third scene can be done as follows:

[0117] (NDL 0Tx / 1Rx+SDL 0Tx / 1Rx<->NDL 1Tx / 0Rx+SDL 0Tx / 2Rx);

[0118] Switching from the third scenario to the fourth scenario; switching from the fourth scenario to the third scenario can be applied when the uplink / downlink of NUL and the downlink of SDL are far apart. When NUL downlink and SDL do not share or share the terminal part Rx, NUL uplink / downlink and SDL downlink can be transmitted simultaneously.

[0119] It should be noted that the one transmit and two receive operations in the 1Tx / 2Rx carriers mentioned above are exemplary, and the embodiments of this application do not limit the number of transmit and receive operations on each carrier.

[0120] By switching between the first, second, third, and fourth scenarios, the terminal can switch between more scenarios, enabling better communication performance and meeting the communication needs of terminals in different regions and environments.

[0121] In some implementations, step 201 may also include the following:

[0122] Downlink reception is switched from the first carrier to the second carrier, wherein before the switch, the terminal performs uplink transmission and downlink reception on the first carrier, and after the switch, the terminal does not perform uplink transmission and downlink reception on the first carrier; after the switch, the terminal performs downlink reception on the second carrier, and after the switch, the terminal does not perform uplink transmission on the second carrier.

[0123] Downlink reception is switched from the second carrier to the first carrier, wherein before the switch, the terminal does not perform uplink transmission and downlink reception on the first carrier, and after the switch, the terminal performs uplink transmission and downlink reception on the first carrier; after the switch, the terminal does not perform uplink transmission and downlink reception on the second carrier.

[0124] Downlink reception is switched from the first carrier to the second carrier. Before the switch, the terminal performs uplink transmission and N downlink receptions on the first carrier, and after the switch, the terminal does not perform uplink transmission on the first carrier, and performs M downlink receptions on the first carrier, where N is an integer greater than 1 and M is a positive integer less than N. After the switch, the terminal performs MN downlink receptions on the second carrier, and does not perform uplink transmission on the second carrier.

[0125] Downlink reception is switched from the second carrier to the first carrier, wherein, before the switch, the terminal does not perform uplink transmission on the first carrier, and before the switch, the terminal performs M downlink receptions on the first carrier; after the switch, the terminal performs uplink transmission and N downlink receptions on the first carrier, where N is an integer greater than 1 and M is a positive integer less than N; after the switch, the terminal does not perform uplink transmission or downlink reception on the second carrier.

[0126] Downlink reception is switched from the first carrier to the second carrier, wherein before the switch, the terminal performs uplink transmission and downlink reception on the first carrier, and after the switch, the terminal performs uplink transmission on the first carrier but does not perform downlink reception on the first carrier; after the switch, the terminal performs downlink reception on the second carrier but does not perform uplink transmission on the second carrier.

[0127] Downlink reception is switched from the second carrier to the first carrier, wherein before the switch, the terminal performs uplink transmission on the first carrier, and before the switch, the terminal does not perform downlink reception on the first carrier, and after the switch, the terminal performs both uplink transmission and downlink reception on the first carrier; after the switch, the terminal does not perform both uplink transmission and downlink reception on the second carrier.

[0128] Downlink reception is switched from the first carrier to the second carrier, wherein, before the switch, the terminal performs downlink reception on the first carrier and does not perform uplink transmission on the first carrier, and after the switch, the terminal performs uplink transmission on the first carrier and does not perform downlink reception on the first carrier; before the switch, the terminal performs K downlink receptions on the second carrier and does not perform uplink transmission on the second carrier, and after the switch, the terminal performs J downlink receptions on the second carrier and does not perform uplink transmission on the second carrier, where J is an integer greater than 1 and K is a positive integer less than J;

[0129] Downlink reception is switched from the second carrier to the first carrier, wherein, before the switch, the terminal performs uplink transmission on the first carrier, and before the switch, the terminal does not perform downlink reception on the first carrier, and after the switch, the terminal performs downlink reception on the first carrier, and after the switch, the terminal does not perform uplink reception on the first carrier; before the switch, the terminal performs J downlink receptions on the second carrier, and before the switch, the terminal does not perform uplink transmission on the second carrier, and after the switch, the terminal performs K downlink receptions on the second carrier, and after the switch, the terminal does not perform uplink transmission on the second carrier, where J is an integer greater than 1 and K is a positive integer less than J.

[0130] As an optional implementation, the terminal switching between the two scenarios includes one of the following:

[0131] The terminal switches between the two scenarios based on the first downlink control information (DCI).

[0132] The aforementioned terminal switching between two scenarios based on the first DCI can be either based on the terminal's indication of the first DCI or triggered by the first DCI.

[0133] Since the switching between the two scenarios is based on the first DCI, dynamic triggering of the switching can be achieved, making the terminal switching more flexible.

[0134] In some implementations, the switching between the two scenarios by the aforementioned terminal based on downlink control information (DCI) includes:

[0135] If the downlink reception carrier scheduled by the first DCI is different from the downlink reception carrier of the previous or last time, the terminal switches between the two scenarios.

[0136] The aforementioned "previous downlink reception" refers to the downlink reception prior to the handover, and the aforementioned "last downlink reception" refers to the last downlink reception prior to the handover.

[0137] In this implementation, switching between two scenarios can be achieved when the downlink reception carrier is different from the previous or last downlink reception carrier, thereby enabling downlink reception based on DCI scheduling to improve the communication performance of the terminal.

[0138] In some embodiments, the method further includes:

[0139] The terminal determines, based on at least one of the second DCI and the first time, whether the downlink reception carrier scheduled by the first DCI is the same as the carrier of the previous or last downlink reception. The first time includes the difference between the start time and the handover preparation time corresponding to the downlink reception scheduled by the first DCI. The second DCI is the DCI received before the first DCI.

[0140] If the terminal is based on T0-T_offset DL1-DL2 or T0-T_offset DL2-DL1 The second DCI (which can be one or more DCIs) received at the specified time and / or previously determines the difference between the second carrier on which the transmission or reception scheduled by the second DCI is located and the first carrier on which the previous / most recent transmission or reception was located (e.g., if the first carrier is carrier 1, then the second carrier is carrier 2; or if the first carrier is carrier 2, then the second carrier is carrier 1). If this is determined, a carrier switch is triggered, switching from the first carrier to the second carrier. Here, T0 is the start time of the first symbol or time slot of the transmission or reception channel or signal on the second carrier according to the scheduling of the first DCI, and T_offset... DL1-DL2 T_offset is the preparation time for switching from carrier 1 to carrier 2. DL2-DL1 This is the preparation time for switching from carrier 2 to carrier 1.

[0141] The above implementation method can accurately determine whether the downlink reception carrier of the first DCI scheduling is the same as the downlink reception carrier of the previous or last time, so as to perform switching under different circumstances and improve the switching performance.

[0142] It should be noted that the embodiments of this application do not limit the determination of whether two downlink received carriers are the same in the above manner. For example, the DCI indicates the carriers of each downlink received carrier, so it is possible to determine whether two downlink received carriers are the same simply and directly.

[0143] In some implementations, the first DCI explicitly or explicitly indicates whether each scheduled downlink reception is transmitted on the first carrier 1 or the second carrier, or the first DCI may implicitly indicate whether the scheduled downlink reception is transmitted on the first carrier 1 or the second carrier.

[0144] In some implementations, if the first DCI triggers carrier switching, the start time for transmission or transmission on the carrier after switching (denoted as K0_post-switch) indicated in the first DCI minus the end time for transmission or transmission on the carrier before switching (denoted as L_pre-switch) can be greater than or not less than the terminal carrier switching time or a preset time. The terminal carrier switching time or preset time can be at least one of the following based on the terminal's reported capabilities and / or the network-side device configuration. This allows the terminal sufficient time for carrier switching, thereby improving switching performance.

[0145] In some implementations, the first DCI indicates the carrier on which downlink reception is located via a carrier indicator field (CIF); or,

[0146] The first DCI indicates the carrier on which the downlink reception is located using 1 bit; or,

[0147] The first DCI indicates the carrier on which downlink reception resides through the most significant bit (MSB) in the frequency domain resource assignment (FDRA) field; or,

[0148] The first DCI indicates the carrier on which the downlink reception is located via a Hybrid Automatic Repeat Request (HARQ) process number.

[0149] Specifically, when using the carrier indication field to indicate the carrier on which downlink reception is located, the second carrier can be configured as a downlink-only SCell (i.e., DL-only SCell), and its CIF value corresponding to carrier 2 can be assigned; alternatively, the CIF value corresponding to the first carrier or the CIF value corresponding to the default carrier 1 can be assigned as 0. This can better indicate the carrier on which downlink reception is located.

[0150] Since the carrier indication field is used for indication, there is no need to modify the DCI format, thus reducing the complexity of downlink handover.

[0151] In the case where the first DCI indicates the carrier on which the downlink reception is located using 1 bit, this 1 bit can be a new 1-bit indication field introduced into the DCI format. This 1 bit is used to indicate whether it is the first carrier (such as NDL) or the second carrier (such as SDL). The corresponding carrier can be indicated simply and directly through this 1 bit.

[0152] The MSB or HARQ process number indication described above can be understood as a reinterpretation of fields in the DCI format. For example, in the X-bit FDRA field, 1 bit is reserved for the MSB to indicate whether it is the first or second carrier, and the remaining (X-1) bits are used to indicate the FDRA. Another example: the Y-bit DL HARQ process number is divided between the first and second carriers, ensuring that the HARQ process numbers used on the first and second carriers do not overlap. Thus, the carrier 1 or carrier 2 can be determined by the HARQ process number indication in the first DCI. For instance, a 4-bit HARQ process number field contains 16 HARQ processes, numbered 0-15, where 0-7 can be configured / assigned to the first carrier, and 8-15 can be configured / assigned to the second carrier.

[0153] The overhead of DCI can be saved by using the MSB or HARQ process number indication mentioned above.

[0154] In some implementations, the terminal switching between two scenes based on a first DCI includes at least one of the following:

[0155] When the uplink transmission of the terminal is only performed on the first carrier, the terminal switches between two scenarios based on the first DCI. The switching between the two scenarios includes switching the downlink reception from the second carrier to the first carrier.

[0156] When the terminal receives a first DCI of a first format on the first carrier, the terminal switches between two scenarios, and the switching between the two scenarios includes switching downlink reception from the first carrier to the second carrier.

[0157] When the terminal receives a first DCI of a second format on the second carrier, the terminal switches between two scenarios, and the switching between the two scenarios includes switching downlink reception from the second carrier to the first carrier.

[0158] The statement that the uplink transmission of the aforementioned terminal is only on the first carrier can be understood as meaning that the uplink transmission of the terminal can only be performed on the first carrier.

[0159] Since the handover between the two scenarios only occurs on the first carrier, including the downlink reception switching from the second carrier to the first carrier, the performance of the terminal's uplink transmission can be guaranteed. For example, based on the indicated and / or configured timing of the Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback for the Physical Downlink Shared Channel (PDSCH), if the previous / most recent reception of the HARQ-ACK transmission was on the second carrier, a carrier handover is triggered, switching from the second carrier to the first carrier. Another example: if the terminal receives a first DCI scheduling (e.g., UL grant) uplink transmission on the second carrier, and the Physical Downlink Control Channel (PDCCH) command triggers at least one of the Physical Random Access Channel (PRACH) transmissions, a carrier handover is triggered, switching from the second carrier to the first carrier.

[0160] The first and second formats mentioned above can be new DCI formats that support carrier switching, corresponding to the first and second carriers respectively, or the first and second formats can be the same format. In this way, when the terminal receives the new DCI format on the first carrier, it is triggered to switch to the second carrier, or when the terminal receives the new DCI format on the second carrier, it is triggered to switch to the first carrier. This eliminates the need for additional signaling to trigger the switching, thus saving transmission overhead.

[0161] As an optional implementation, the terminal switching between the two scenarios includes one of the following:

[0162] The terminal switches between two scenarios based on high-level configuration.

[0163] The aforementioned higher-level configuration can be the higher-level configuration sent by the terminal to the network-side device.

[0164] For example, based on the transmission and reception configuration of the higher layer, if the first carrier configured for transmission or reception differs from the second carrier configured for the previous / most recent transmission or reception, a carrier handover is triggered: switching from the first carrier to the second carrier. For example, if the first carrier is carrier 1, then the second carrier is carrier 2; or if the first carrier is carrier 2, then the second carrier is carrier 1, and the handover proceeds from the first carrier to the second carrier.

[0165] Because the terminal switches between the two scenarios based on the high-level configuration, this allows the terminal to support more flexible switching.

[0166] As an optional implementation, the terminal switching between the two scenarios includes one of the following:

[0167] The terminal switches between two scenarios based on a first semi-static signaling, which is used to indicate the carrier switching time-domain mode (or simply time-domain mode).

[0168] The aforementioned first semi-static signaling can be higher-layer signaling, Radio Resource Control (RRC) signaling, system information, etc. For example, the time-division multiplexing mode (ndl-sdl-TDMPattern) parameters of NDL and SDL indicate the carrier switching time-domain mode of the terminal in downlink reception.

[0169] The aforementioned carrier switching time-domain mode can be time division multiplexing (TDM) mode, that is, carrier switching is performed based on the TDM mode configured by the first semi-static signaling.

[0170] The aforementioned carrier switching time-domain mode can indicate the carrier on which each downlink receiver is located or the active carrier, etc.

[0171] The aforementioned handover between two scenarios based on the first semi-static signaling refers to the handover between two scenarios based on the carrier handover time-domain mode indicated by the first semi-static signaling. This can support multiple handovers to save transmission overhead.

[0172] In some implementations, the first semi-static signaling described above is used to indicate at least one of the following:

[0173] At least one time unit of active carrier;

[0174] The usage period of the carrier switching time-domain mode;

[0175] The length of the carrier switching time-domain mode;

[0176] The start time or time offset of the carrier switching time-domain mode.

[0177] Among them, at least one of the above time units is the time unit corresponding to the above carrier switching time domain mode.

[0178] The aforementioned time unit can be a symbol, time slot, or subframe. For example, the granularity of the carrier switching time-domain mode can be at least one of X OFDM symbols, Y time slots, and Z subframes, where X, Y, and Z are all positive integers greater than or equal to 1. The length of the OFDM symbol, time slot, or subframe is determined by the maximum or minimum value in the parameter set (numerology) or subcarrier spacing (SCS) of carrier 1 and carrier 2; or by a reference number / SCS configured by the network. In some implementations, the number / SCS of the first and second carriers are the same; the granularity of the carrier switching time-domain mode is Y = 1 time slot.

[0179] The effective carrier of at least one time unit mentioned above can be a carrier that is effective at at least one time-domain granularity within the length of the carrier switching time-domain mode, i.e., on which transmission and / or reception is performed.

[0180] In some implementations, a time unit (also called time granularity) of the above-mentioned carrier switching time domain mode can be configured to enable either the first carrier or the second carrier. A time unit without any carrier configured indicates that the first carrier is not enabled, and the time reserved for these time units is used for carrier switching.

[0181] In some implementations, only the time in which the second carrier is active is configured, i.e., which time units the second carrier is active in. If no carrier is configured, the first carrier is active by default.

[0182] The aforementioned active carrier can better indicate downlink carrier switching.

[0183] In some implementations, in the time unit where the effective carrier is the first carrier in the carrier switching time domain mode, the terminal performs at least one of uplink transmission and downlink reception, and in the time unit where the effective carrier is the second carrier in the carrier switching time domain mode, the terminal performs downlink reception.

[0184] Wherein, for resources whose effective carrier is the first carrier, the terminal performs downlink reception on the first carrier including at least one of monitoring and control channels, receiving data channels, and performing downlink measurements, and the terminal performs uplink transmission on the first carrier including at least one of uplink data channel transmission, control channel transmission, PRACH transmission, and reference signal transmission.

[0185] For resources where the effective carrier is the second carrier, the terminal performs downlink reception on the second carrier, including at least one of monitoring the control channel, receiving the data channel, and performing downlink measurements.

[0186] The usage period of the aforementioned carrier switching time-domain mode can also be called the application period of the carrier switching time-domain mode.

[0187] For example, the application period of the above carrier switching time domain mode is {5ms, 10ms, 20ms, 40ms, 80ms, 160ms}.

[0188] In some implementations, if the time-domain mode application / usage period is not configured, the default period can be the period of the Cell Defining SSB (CD-SSB) on the PCell.

[0189] In some implementations, the start time of the aforementioned carrier switching time-domain mode usage period is required to be aligned with the start symbol / first symbol of a certain radio frame or subframe. For example, if the maximum value of the carrier switching time-domain mode application / usage period is Pmax = 160ms, and the currently used time-domain mode usage period is P = 20ms, then the first OFDM symbol of each Pmax / P (=160 / 20=8) period of the carrier switching time-domain mode usage period is the first symbol in the radio frame n_f mod(Pmax / 10) = 0; or the first OFDM symbol of each Pmax / P period of the carrier switching time-domain mode application / usage period is the first symbol of an even-numbered frame or an odd-numbered frame.

[0190] By indicating the usage period of the aforementioned carrier switching time-domain mode, the terminal can perform downlink carrier switching within the period.

[0191] The length of the aforementioned carrier switching time-domain mode can be the duration of the carrier switching time-domain mode. When indicating the length, it can also indicate at least one carrier that is active at the time-domain granularity within that length.

[0192] The length of the carrier switching time domain mode can be flexibly configured by indicating the length of the carrier switching time domain mode, making downlink carrier switching more flexible.

[0193] In some implementations, if no usage period for the carrier switching time-domain mode is configured, the period of the carrier switching time-domain mode is equal to the length of the time-domain mode.

[0194] The start time of the aforementioned carrier switching time-domain mode can be either absolute or relative.

[0195] In some implementations, if the length of the carrier switching time-domain mode is less than the usage period of the carrier switching time-domain mode, then the start time of the carrier switching time-domain mode is the start time or time offset of the time-domain mode within one application period of the carrier switching time-domain mode.

[0196] In some embodiments, the carrier switching of the terminal within the carrier switching time domain mode satisfies at least one of the following:

[0197] The number of switches does not exceed the number of carrier switches supported by the terminal;

[0198] The number of switches does not exceed the maximum value of the number of carrier switches specified by the protocol;

[0199] The switching time does not exceed the switching time specified by the protocol.

[0200] Among them, the above "not exceeding" can be not exceeding within the length of the carrier switching time domain mode. For example: within the length of the carrier switching time domain mode, the number of carrier switches does not exceed the ability of the terminal to support the number of carrier switches or does not exceed the maximum value of the number of carrier switches specified by the protocol, and the switching time does not exceed the first time specified by the protocol. In this way, the interruption time / carrier-free actual transmission time caused by carrier switching cannot exceed the first interruption duration or cannot exceed X% × the first duration, where 1% < X% < 100%, for example, X% = 20%, and the first duration can be the duration specified by the protocol or configured by the network side device.

[0201] Adopting at least one of the above can help reduce switching overhead and improve network resource utilization.

[0202] In some embodiments, when switching between the two scenarios includes switching from receiving downlink from the first carrier to the second carrier:

[0203] When the network side device has not yet indicated the carrier switching time domain mode to the terminal, the terminal does not expect to activate the second carrier.

[0204] The above second carrier can be a Scell or an SDL carrier.

[0205] Since it does not expect to activate the second carrier, this can avoid signaling waste for the second carrier. For example: the terminal does not expect the network side device to activate the Scell without configuring the semi-static TDM mode for carrier switching.

[0206] In some embodiments, the terminal switching between the two scenarios based on the first semi-static signaling includes one of the following:

[0207] When the first semi-static signaling indicates multiple carrier switching time domain modes, the terminal determines the effective carrier switching time domain mode among the multiple carrier switching time domain modes based on the Medium Access Control Control Element (MAC CE) or physical layer information, and switches between the two scenarios based on the effective carrier switching time domain mode;

[0208] When the first semi-static signaling indicates multiple carrier switching time-domain modes, the terminal switches between two scenarios based on the time-cascaded multiple carrier switching time-domain modes.

[0209] Among them, the carrier switching time-domain mode that is effective among multiple carrier switching time-domain modes determined based on MAC CE or physical layer information can be activated, deactivated or released by using MAC CE or physical layer information to make one or more of the time-domain modes effective.

[0210] Since the switching between the two scenarios is based on the effective carrier switching time-domain mode, this makes the switching more reliable.

[0211] In some implementations, when at least two carrier switching time-domain modes are active, there is no carrier conflict between the active at least two carrier switching time-domain modes. For example, if multiple carrier switching time-domain modes can be activated by MAC CE or physical layer information, it is required that the configuration of these multiple time-domain modes does not result in carrier conflict, that is, different time-domain modes indicate different carriers to be active within the same time / time slot. This avoids conflicts and improves handover performance.

[0212] The aforementioned cascaded carrier switching time-domain modes can also be called carrier switching cascaded time-domain modes or cascaded time-domain modes. The application / usage period of a cascaded time-domain mode is the sum of the periods of multiple carrier switching time-domain modes. Unless otherwise specified, the characteristics of a cascaded time-domain mode are the same as those of a carrier switching time-domain mode. For example, the start time of the application period of a cascaded time-domain mode must be aligned with the start symbol / first symbol of a radio frame or subframe.

[0213] Taking two cascaded patterns as an example, for instance, an RRC can be configured with up to two carrier switching time-domain patterns, denoted as ndl-sdl-TDMPattern1 and ndl-sdl-TDMPattern2. The application period of ndl-sdl-TDMPattern1 is denoted as P1, and the application period of ndl-sdl-TDMPattern2 is denoted as P2. After the two carrier switching time-domain patterns are cascaded, the cascaded carrier switching time-domain patterns will repeat periodically according to the period of P1+P2.

[0214] The time-domain modes of multiple carrier switching cascaded in time can support more downlink carrier switching, thereby improving switching performance.

[0215] In some implementations, when switching between two scenarios based on a first semi-static signaling, multi-cell DCI (mc-DCI) can simultaneously schedule DL and SDL.

[0216] As an optional implementation, the terminal switching between the two scenarios includes one of the following:

[0217] The terminal switches between two scenarios based on a second semi-static signaling, which is used to indicate downlink reception on the first carrier or the second carrier.

[0218] The second semi-static signaling can be an explicit or implicit indication of downlink reception on the first carrier or the second carrier.

[0219] In some implementations, the content of the second semi-static signaling includes at least one of the following:

[0220] Whether to perform downlink reception on the first or second carrier;

[0221] Configure, activate, or trigger downlink reception on the second carrier 2;

[0222] Configure, deactivate, or deactivate downlink reception on the second carrier;

[0223] The duration of downlink reception on the indicated carrier.

[0224] In some implementations, the default first carrier is activated before the terminal receives any second semi-static signaling, or in other words, the terminal performs downlink reception on the first carrier.

[0225] The second semi-static signaling terminal determines which carrier to receive downlink data on in order to perform downlink carrier switching.

[0226] As an optional implementation, the terminal switching between the two scenarios includes one of the following:

[0227] The terminal switches between two scenarios based on at least one condition.

[0228] Among them, at least one of the above conditions can be agreed upon in the protocol or configured by the network-side equipment, and can be set according to actual business needs.

[0229] Among them, at least one of the above conditions can also be referred to as at least one event, wherein switching between two scenarios is based on condition or event triggering to save transmission overhead.

[0230] In some implementations, when the handover between the two scenarios includes a downlink reception switch from the second carrier to the first carrier, the at least one condition includes:

[0231] The uplink transmission that needs to be performed on the first carrier is triggered;

[0232] The second carrier is deconfigured, deactivated, or put to sleep, and the active bandwidth part (BWP) on the second carrier becomes dormant.

[0233] A radio link failure occurred.

[0234] The channel quality on the second carrier is below a preset threshold;

[0235] The timer corresponding to the second carrier timed out.

[0236] For example, if certain uplink transmissions are triggered, the terminal needs to transmit at least one of PRACH, Scheduling Request (SR), or Configured Grant Physical Uplink Shared Channel (PUSCH). If the terminal needs to perform the above uplink transmissions on the first carrier, then the second carrier switches to the first carrier. However, if downlink reception is on the first carrier, no switching occurs.

[0237] The aforementioned PRACH transmissions can be contention-based (CB) PRACH transmissions, but do not include contention-free (CF) PRACH transmissions.

[0238] The aforementioned SR or Configured grant PUSCH transmission can be a high-priority transmission, meaning it is configured with a high priority or carries beam failure information.

[0239] For example, if the terminal's previous / most recent received transmission before transmitting the aforementioned uplink transmission was on the second carrier, then the terminal needs to switch from the second carrier to the first carrier to perform the aforementioned uplink transmission.

[0240] The aforementioned preset thresholds and timer durations can be agreed upon by the protocol or configured by the network-side device.

[0241] The aforementioned channel quality can be Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), or Signal to Interference plus Noise Ratio (SINR).

[0242] For example, if the RSRP, RSRQ, or SINR on the second carrier is lower than the network-configured threshold, a carrier handover is triggered, and the terminal switches from the second carrier to the first carrier.

[0243] In some implementations, the terminal can perform carrier switching autonomously or spontaneously based on channel conditions, and then notify the network-side equipment of the switching via PRACH, SR, and configuration authorization PUSCH.

[0244] The aforementioned timer could be a new timer introduced for the second carrier. This timer's timeout triggers a carrier switch, causing the terminal to switch from the second carrier to the first carrier. For example: when the terminal switches to the second carrier, the timer is started. If the terminal receives downlink transmissions (such as PDSCH and / or DCI) on the second carrier, and these downlink transmissions do not carry an indication of carrier switching (i.e., switching from the second carrier to the first carrier), the timer is restarted. If the downlink transmissions received by the terminal on the second carrier carry an indication of carrier switching, the timer is stopped.

[0245] In some implementations, the timer is stopped when switching from the second carrier to the first carrier.

[0246] In some implementations, the timer is stopped when a radio link failure (RLF) or beam failure recovery (BFR) occurs on the first carrier.

[0247] By triggering a handover using at least one of the above conditions, additional signaling can be avoided, thus saving transmission overhead.

[0248] In some implementations, when the handover between the two scenarios includes a downlink reception switch from the first carrier to the second carrier, the at least one condition includes:

[0249] The first carrier is deconfigured, deactivated, or put to sleep, and the active bandwidth portion (BWP) on the first carrier becomes dormant.

[0250] Link failure occurred;

[0251] The channel quality on the first carrier is lower than a preset threshold;

[0252] The timer corresponding to the first carrier timed out.

[0253] For at least one of the above conditions, please refer to the corresponding description of the above implementation method, which will not be repeated here.

[0254] In this implementation, downlink reception can be triggered to switch from the first carrier to the second carrier based on at least one of the above conditions, thus eliminating the need for additional signaling and saving transmission overhead.

[0255] In some implementations, the switching of the terminal between two scenarios includes:

[0256] Under at least one of the conditions, if the terminal receives the first semi-static signaling or the second semi-static signaling, the terminal ignores the first semi-static signaling or the second semi-static signaling and switches between the two scenarios based on the at least one condition.

[0257] In this implementation, handover can be triggered preferentially based on at least one condition to make the handover more consistent with the current situation of the terminal. For example, the carrier handover time domain mode of the first semi-static signaling configuration can be ignored and / or the second semi-static signaling configuration can be activated to perform downlink reception on the second carrier.

[0258] In some implementations, if a terminal or its / MAC entity receives a message instructing it to switch to a second carrier, such as an instruction from DCI or higher-layer configuration, while a random access procedure is in progress or an SR has been triggered but not yet transmitted, the terminal or its MAC entity should ignore the message; that is, the terminal or its MAC entity should not perform a switch from the first carrier to the second carrier.

[0259] In some implementations, after the terminal ignores the first semi-static signaling or the second semi-static signaling, the method further includes:

[0260] Under the second condition, the terminal switches between the two scenarios again based on the first semi-static signaling or the second semi-static signaling. The switching between the two scenarios includes: switching downlink reception from the second carrier to the first carrier, or switching downlink reception from the first carrier to the second carrier.

[0261] The second condition includes at least one of the following:

[0262] The terminal receives a signaling instruction indicating that the first semi-static signaling or the second semi-static signaling is effective;

[0263] The random access process has ended;

[0264] The second carrier is activated again;

[0265] The second carrier becomes a non-dormant carrier.

[0266] The aforementioned signaling may be RRC reconfiguration signaling, which enables the carrier handover time-domain mode configured by the first semi-static signaling to take effect again during carrier handover; or when the contention is successfully resolved after the RACH process ends, or when the second carrier is reactivated or becomes a dormant cell, the carrier handover time-domain mode configured by the first semi-static signaling will take effect again during carrier handover.

[0267] In the above embodiments, the first semi-static signaling or the second semi-static signaling can be restored, so that the terminal can perform a better handover.

[0268] As an optional implementation, during the switching time between the two scenarios, the terminal satisfies one of the following conditions:

[0269] Uplink transmission is not required or expected, and downlink reception is not required or expected.

[0270] Uplink transmission is neither required nor expected.

[0271] Downlink reception is neither required nor expected.

[0272] The above "not required or not expected" may mean that the network-side device is not required or expected to configure the terminal to perform uplink transmission or downlink reception during the above handover time, or that the terminal is not required or expected to perform uplink transmission or downlink reception during the above handover time.

[0273] In this implementation, since uplink transmission or downlink reception is not required or expected during the handover time, the terminal can perform a better handover.

[0274] For example, during carrier switching time, the terminal determines the first action based on at least one of the following:

[0275] The protocol specifies the terminal's reporting capabilities, the frequency spacing between the uplink spectrum of the first carrier and the downlink spectrum of the second carrier, the frequency spacing between the downlink spectrum of the first carrier and the downlink spectrum of the second carrier, and the frequency band combination type between the frequency bands of the first carrier and the second carrier.

[0276] The aforementioned first act includes at least one of the following:

[0277] It is neither required nor expected that the terminal will perform uplink transmission or downlink reception during the handover period;

[0278] The terminal is not required or expected to perform uplink transmission during the handover period (or the terminal is not restricted from performing downlink reception during the handover period; or the terminal is required to perform downlink reception during the handover period; or the terminal can perform downlink reception during the handover period); for example: the terminal can perform downlink reception only on the first carrier during the handover period; or only on the second carrier; or perform downlink reception on both the first and second carriers.

[0279] The terminal is not required or expected to perform downlink reception during the handover period (or, in other words, the terminal is not restricted from performing uplink transmission during the handover period; or, in other words, the terminal is required to perform uplink transmission during the handover period; or, in other words, the terminal can perform uplink transmission during the handover period); for example: the terminal is not required or expected to perform downlink reception on the second carrier during the handover period, but the terminal can perform downlink reception on the first carrier during the handover period; another example: the terminal is not required or expected to perform downlink reception on the first carrier during the handover period, but the terminal can perform downlink reception on the second carrier during the handover period.

[0280] In some implementations, when the first carrier and the second carrier are a first carrier band combination: the terminal does not require or expect to perform uplink transmission during the handover time, and does not require or expect to perform downlink reception; or, the terminal does not require or expect to perform uplink transmission during the handover time; or,

[0281] When the first carrier and the second carrier are a combination of the second carriers: the terminal does not require or expect to receive downlink data during the switching time.

[0282] The first and second carrier combinations mentioned above can be defined by a protocol or configured by network-side equipment. For example, a band combination X is defined, which is a band combination for NDL, NUL, and SDL bands that are very close. When the UE switches over the downlink in this combination, the terminal's behavior can be either not requiring or expecting the terminal to perform uplink transmission and not requiring or expecting the terminal to perform downlink reception during the switching time; or not requiring or expecting the UE to perform uplink transmission during the switching time, or not restricting the terminal to perform downlink reception during the switching time; or requiring the UE to perform downlink reception during the switching time; or allowing the UE to perform downlink reception during the switching time.

[0283] For example, a band combination Y is defined. Band combination Y is a band combination that is far apart from the NUL and SDL bands. When the downlink is switched, the terminal's behavior can be that it does not require or expect the terminal to perform downlink reception during the switching time, or it does not restrict the terminal to perform uplink transmission during the switching time; or it requires the terminal to perform uplink transmission during the switching time; or it allows the terminal to perform uplink transmission during the switching time.

[0284] In the above embodiments, carrier combination enables the terminal to perform carrier switching better.

[0285] As an optional implementation, the processing capabilities of the terminal on the first carrier and the second carrier satisfy at least one of the following:

[0286] The terminal has the same PDSCH processing capability on the first carrier and the second carrier;

[0287] The PUSCH processing capabilities of the terminals on the first carrier and the second carrier are different.

[0288] The aforementioned PDSCH and PUSCH processing capabilities may include capability 1 and capability 2, which are two different processing capabilities agreed upon in the protocol.

[0289] For example, the above terminal does not support the following: the terminal's PDSCH and PUSCH processing capability is capability 1 on the first carrier, while the terminal's PDSCH processing capability is capability 2 on the second carrier.

[0290] For example, the above terminal does not support the following: the terminal's PDSCH and PUSCH processing capability on the first carrier is capability 2, while the terminal's PDSCH processing capability on the second carrier is capability 1.

[0291] For example, the above-mentioned terminal does not support the following: the terminal's PDSCH processing capabilities differ on the first carrier and the second carrier.

[0292] In some implementations, the PDSCH processing capability of the terminal on the first carrier and the second carrier is the same, which may be the PDSCH processing capability capability 1 of the terminal on the first carrier and the second carrier.

[0293] The difference in PUSCH processing capability of the terminal on the first carrier and the second carrier refers to the fact that the PUSCH processing capability of the terminal on the first carrier may be different from the PDSCH processing capability of the terminal on the second carrier.

[0294] Since the terminal has the same PDSCH processing capability on the first carrier and the second carrier, this allows the terminal to perform downlink carrier switching better.

[0295] Because the terminal's PUSCH processing capabilities differ on the first carrier and the second carrier, this may cause the terminal to perform different uplink transmissions on different carriers.

[0296] As an optional implementation, the first carrier and the second carrier satisfy at least one of the following:

[0297] The parameter sets (numerology) of the first carrier and the second carrier are the same;

[0298] The baseband bandwidth of the first carrier and the second carrier is the same, or the difference between the baseband bandwidth of the first carrier and the second carrier is less than or equal to the bandwidth threshold.

[0299] The difference in power spectral density (PSD) between the first carrier and the second carrier does not exceed the power threshold.

[0300] The first carrier and the second carrier share an indication for activating or deactivating discontinuous transmission (DTX) in the cell;

[0301] At least one of the first carrier and the second carrier supports self-scheduling, and among the at least one carrier that supports self-scheduling, one carrier self-scheduling can only schedule downlink reception;

[0302] At least one of the first carrier and the second carrier supports cross-carrier scheduling, and the cross-carrier scheduling of one of the at least one carrier that supports cross-carrier scheduling can only schedule downlink reception;

[0303] At least one of the first carrier and the second carrier can be configured with at least one of CORESET, PDCCH and search space;

[0304] One of the first carrier and the second carrier supports cross-carrier scheduled uplink DCI, while the other carrier does not support cross-carrier scheduled uplink DCI.

[0305] The identical numberology of the first and second carriers can be entirely or partially identical. In some implementations, the identical numberology of the active downlink BWP (active DL BWP) of the first and second carriers can be the same.

[0306] Since the numberology of the first and second carriers is the same, it makes the handover process simpler for the terminal, thereby reducing the complexity of the handover and improving communication efficiency.

[0307] The aforementioned bandwidth threshold can be agreed upon by the protocol or configured by the network-side equipment. For example, the system, channel, or terminal baseband bandwidth of the first carrier and the second carrier are the same, or the difference between the two does not exceed BW, such as BW = 5MHz.

[0308] Since the baseband bandwidth of the first carrier and the second carrier is the same, or the difference between the baseband bandwidth of the first carrier and the second carrier is less than or equal to the bandwidth threshold, the complexity of carrier switching can be reduced.

[0309] The difference between the PSD of the first carrier and the second carrier can be no more than P dB, such as P=6 or other values, which can be agreed upon by the protocol or configured by the network-side equipment.

[0310] Since the difference in PSD between the first carrier and the second carrier does not exceed the power threshold, the complexity of carrier switching can be reduced.

[0311] The above-mentioned indication for activating or deactivating cell DTX can be a Network Energy Saving (NES) cell DTX indication field indicating the activation or deactivation of cell DTX, applicable to the first carrier and the second carrier, or in other words, the first carrier and the second carrier share the indication for activating or deactivating cell DTX using Network Energy Saving.

[0312] Since the first and second carriers share the indication used to activate or deactivate cell DTX, transmission overhead can be saved.

[0313] The scheduling features of the first carrier and the second carrier mentioned above may include at least one of the following:

[0314] First carrier self-scheduling;

[0315] The second carrier is self-scheduled. During the second carrier self-scheduled process, only downlink transmission can be scheduled, and uplink transmission cannot be scheduled.

[0316] When the first carrier schedules the second carrier across carriers, only downlink transmission can be scheduled, not uplink transmission.

[0317] The second carrier cannot schedule the first carrier across carriers.

[0318] The second carrier schedules the first carrier across carriers.

[0319] Wherein, the PDCCH or DCI format corresponding to the first carrier and the second carrier mentioned above includes at least one of the following:

[0320] The second carrier can be configured with at least one of CORESET, PDCCH, and the search space;

[0321] The second carrier does not support DCI format 0-0 / 1-0;

[0322] The second carrier supports DCI format 0-0 and 1-0. When the terminal receives an uplink transmission scheduled by DCI format 0-0 on the second carrier, the uplink transmission is transmitted on the first carrier, or it can be described as supporting receiving uplink scheduling of the first carrier on the second carrier.

[0323] The first carrier supports uplink DCI formats that can be scheduled across carriers. For uplink scheduling DCI formats that include CIF (such as DCI format 0_1 / 0_2), the corresponding n_CI cannot be the n_CI corresponding to the second carrier.

[0324] The second carrier does not support uplink DCI format, such as uplink DCI format 0-1 / 1-1 / 0-2 / 2-2, or the CIF of the DCI format of the second carrier is 0 or the default value.

[0325] It should be noted that the various implementation methods provided in this application can be combined with each other or implemented individually, and there is no limitation thereto.

[0326] In this embodiment, the terminal switches between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier. Because the switching between the two scenarios includes switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier, the terminal is able to perform downlink carrier switching, enabling it to switch between more scenarios and thus improving its communication performance.

[0327] Please refer to Figure 3, which is a flowchart of a message sending method provided in an embodiment of this application. As shown in Figure 3, it includes the following steps:

[0328] Step 301: The network-side device sends a first message to the terminal. The first message is used to instruct the terminal to switch between two scenarios. The switching between the two scenarios includes: switching downlink reception from the first carrier to the second carrier, or switching downlink reception from the second carrier to the first carrier.

[0329] Optionally, the method further includes:

[0330] The network-side device performs downlink transmission carrier switching, which includes switching downlink transmission from a first carrier to a second carrier, or switching downlink transmission from a second carrier to a first carrier.

[0331] In this embodiment, it refers to the case where the first carrier and the second carrier correspond to the same network-side device.

[0332] Optionally, the first message includes at least one of the following:

[0333] First downlink control information (DCI), first semi-static signaling, second semi-static signaling;

[0334] The first DCI is used to indicate the carrier on which downlink reception is located;

[0335] The first semi-static signaling is used to indicate the carrier switching time-domain mode;

[0336] The second semi-static signaling is used to indicate downlink reception on the first carrier or the second carrier.

[0337] Optionally, the first DCI indicates the carrier on which downlink reception is located via a carrier indication field; or,

[0338] The first DCI indicates the carrier on which the downlink reception is located using 1 bit; or,

[0339] The first DCI indicates the carrier on which downlink reception is located by using the most significant bit (MSB) in the Frequency Domain Resource Allocation (FDRA) field; or...

[0340] The first DCI indicates the carrier on which the downlink reception is located via a Hybrid Automatic Repeat Request (HARQ) process number.

[0341] Optionally, the first semi-static signaling is used to indicate at least one of the following:

[0342] At least one time unit of active carrier;

[0343] The usage period of the time-domain mode;

[0344] The length of the time-domain pattern;

[0345] The start time or time offset of the time-domain mode.

[0346] Optionally, in the carrier switching time domain mode, the terminal performs at least one of uplink transmission and downlink reception in the time unit when the effective carrier is the first carrier, and the terminal performs downlink reception in the time unit when the effective carrier is the second carrier.

[0347] It should be noted that this embodiment is an implementation of the network-side device corresponding to the embodiment shown in Figure 2. For the specific implementation, please refer to the relevant description of the embodiment shown in Figure 2. In order to avoid repeated description, this embodiment will not be repeated.

[0348] The methods provided in the embodiments of this application are illustrated below through multiple examples:

[0349] Example 1:

[0350] This embodiment mainly describes carrier switching based on the TDM mode (i.e., the aforementioned carrier switching time domain mode) configured by the first semi-static signaling.

[0351] Higher-layer signaling (such as RRC signaling or RRC parameters ndl-sdl-TDMPattern) provides the terminal with a single carrier-switching time-domain pattern for downlink reception. For example, if the first and second carriers have the same SCS (Sequence Size) of 15 kHz, the time-domain pattern usage period equals the time-domain pattern length (10 slots), the time-domain pattern granularity is one slot, and the maximum number of carrier-switching cycles supported by the protocol or terminal capability is two, then:

[0352] RRC signaling uses 1 bit of information per slot to configure whether the first or second carrier is active on that slot. For example, using the RRC parameter / field: the sequence ndl-sdl-TDMPattern-r19 (size (1..maxNrofSlots)), integers (0..1) provide the terminal with semi-static carrier switching between the first carrier (e.g., PCell) and the second carrier (e.g., SDL carrier). A bit value of 0 in this field indicates that the first carrier is active, and a bit value of 1 indicates that the second carrier is active. ndl-sdl-TDMPattern-r19 = (0, 0, 1, 1, 1, 1, 1, 1, 1, 0), it means that the terminal is active on the first carrier in slots 1, 2, and 10, and on the second carrier in slots 3, 4, 5, 6, 7, 8, and 9. When the terminal performs carrier switching, in this example, it needs to switch from the first carrier to the second carrier between the second and third time slots, and from the second carrier to the first carrier between the ninth and tenth time slots. During the carrier switching time, the terminal is not required to perform uplink transmission or downlink reception.

[0353] Alternatively, the RRC signaling can configure the start time and duration of the first carrier's activation within the time-domain mode length, as well as the start time and duration of the second carrier's activation; the time corresponding to any unconfigured time granularity is reserved for carrier switching time.

[0354] For example, as shown in Figure 4, the length of the time-domain mode is 10 slots. By default, the effective carrier on the first / first symbol / slot of this time-domain mode is the first carrier. The time slots / symbols that are continuously effective for the first carrier are configured to be 4 slots and 7 OFDM symbols. The start time for the second carrier is configured to be the 6th slot, and 4 slots and 7 OFDM symbols are continuously effective.

[0355] For example, as shown in Figure 5, the length of the time-domain mode is 10 slots. By default, the effective carrier on the first / first symbol / slot of this time-domain mode is the first carrier, and the time slots / symbols configured for the first carrier to be continuously effective are 4 slots and 7 OFDM symbols. By default, the effective carrier on the second-to-last symbol / slot of this time-domain mode is the second carrier, and in terms of time, from the second-to-last symbol / slot, the time slots or symbols configured for the second carrier to be continuously effective are 4 slots and 12 OFDM symbols.

[0356] Alternatively, RRC signaling may configure only the start time and consecutive duration of the first or second carrier activation within the time-domain mode length; unconfigured time slots default to the second or first carrier activation. For example, the RRC time-domain mode configuration might be that the first carrier activation time is the first slot out of 10 slots in the time-domain mode length, with two consecutive time slots (numbered time slot 1 and time slot 2). The other time slots in these 10 slots (time slot 3 and time slot 10) are not configured and default to the second carrier activation time slots. When the terminal performs carrier switching, in this example, from time slot 2 to time slot 3, it needs to switch from the first carrier to the second carrier; from time slot 10 to the first time slot of the next / following time-domain mode cycle, it needs to switch from the second carrier to the first carrier. During the carrier switching time, the terminal is not required to perform uplink transmission or downlink reception.

[0357] Alternatively, higher-layer signaling (such as RRC signaling or RRC parameters ndl-sdl-TDMPattern) provides the terminal with N (N>1) carrier switching time-domain modes in downlink transmission. For example, if the first and second carriers have the same SCS (Scanning Cross Section) of 15kHz, the time-domain mode application / usage period equals the time-domain mode length (10 slots), the time-domain mode granularity is 1 slot, and the maximum number of carrier switching times supported by the protocol or UE capability is 2, then:

[0358] Higher-layer signaling (such as RRC signaling parameters like ndl-sdl-TDMPattern) provides the terminal with the time-domain mode for switching between N (N>1) carriers in downlink transmission. For example, if N=2,

[0359] For example: the first time-domain pattern of carrier switching is denoted as ndl-sdl-TDMPattern1, and its period P1 = 5 slots; the effective pattern1 of the carrier in these 5 slots is (0,0,1,1,1), where bit '0' represents the first carrier and bit '1' represents the second carrier;

[0360] For example, the second time-domain pattern of carrier switching is denoted as ndl-sdl-TDMPattern2, and its period P2 = 5 slots; the effective pattern2 of the carrier in these 5 slots is (0,0,0,1,1), where bit '0' represents the first carrier and bit '1' represents the second carrier;

[0361] The period of the cascaded carrier switching cascaded time-domain mode is P1+P2=10 slots. The effective pattern of the carrier within these 10 slots is pattern1+pattern2=(0,0,1,1,1,0,0,0,1,1), where bit'0' represents the first carrier and bit'1' represents the second carrier.

[0362] Alternatively, higher-layer signaling (such as RRC signaling parameters like ndl-sdl-TDMPattern) provides the terminal with the time-domain mode for switching N (N>1) carriers in downlink transmission. For example, if N=2,

[0363] For example, the first time-domain pattern of carrier switching is denoted as ndl-sdl-TDMPattern1, with a period P1 = 5 slots; one slot contains 14 OFDM symbols. These 5 slots are numbered from slot #1 to slot #5. Within these 5 slots, the carrier-effective pattern 1 is as follows: slot #1 is the first carrier; the first 12 OFDM symbols in slot #2 are the first carrier; slots #3, #4, and #5 are the second carrier. The last two OFDM symbols in slot #2 are reserved for the UE to switch from the first carrier to the second carrier.

[0364] For example, the second time-domain pattern for carrier switching is denoted as ndl-sdl-TDMPattern2, with a period P2 of 5 slots; one slot contains 14 OFDM symbols. These 5 slots are numbered from slot #1 to slot #5. Within these 5 slots, the carrier-active pattern 2 is slot #1, slot #2 is the first carrier, the first 12 OFDM symbols in slot #3 are the first carrier, and slots #4 and #5 are the second carrier. The last two OFDM symbols in slot #3 are reserved for the UE to switch from the first carrier to the second carrier.

[0365] The period of the cascaded carrier switching time-domain mode is P1+P2=10 slots. The effective carrier pattern within these 10 slots is pattern1+pattern2, as shown in Figure 6.

[0366] Example 2:

[0367] In this embodiment, the downlink reception on which carrier to perform downlink reception is determined based on the second semi-static signaling. Unlike the carrier switching configured in TDM mode using the first semi-static signaling described above, the carrier switching in this embodiment is primarily triggered by RRC signaling.

[0368] One approach is that if the terminal receives a second semi-static signaling instruction indicating configuration, activation, or triggering of downlink reception on the second carrier while on a carrier other than the second carrier, such as the first carrier, then after the effective time of the second semi-static signaling, the terminal switches from the first carrier to the second carrier for downlink reception. The terminal switches from the second carrier to the first carrier only if one of the following conditions is met:

[0369] Condition 1: If the second semi-static signaling also indicates the time for receiving on the second carrier; or the protocol specifies the time for receiving on the second carrier; or the protocol introduces a timer, then after that time expires or the timer times out, the terminal switches from the second carrier to the first carrier.

[0370] Condition 2: When the terminal receives a second semi-static signaling instruction to configure, deactivate, or release downlink reception on the second carrier, the terminal switches from the second carrier to the first carrier after the effective time of the second semi-static signaling.

[0371] Another approach is that if the terminal receives a second semi-static signaling instruction on a carrier other than the second or first carrier, such as the third carrier, indicating which carrier to configure, activate, or trigger for downlink reception, then after the effective time of the second semi-static signaling, the terminal will perform downlink reception on the indicated carrier. For example, if the terminal is performing downlink reception on the second carrier, it may receive a second semi-static signaling instruction on the third carrier instructing it to switch from the second carrier to the first carrier.

[0372] Example 3:

[0373] In this embodiment, the terminal performs semi-static uplink transmissions such as PUCCH, PUSCH, and SRS on the first carrier only when the first carrier is active, and semi-static downlink receptions such as PDCCH monitoring occasion (MO) and Channel State Information Reference Signal (CSI-RS) on the first carrier only when the first carrier is active; or these semi-static configurations are activated only when the first carrier is active, or the resources of these semi-static configurations are available or valid.

[0374] Alternatively, when the first carrier is not active, or when the second carrier is active, the terminal does not perform semi-static uplink transmissions such as PUCCH, PUSCH, and SRS on the first carrier, nor does it perform semi-static downlink receptions such as PDCCH MO and CSI-RS on the first carrier; or these semi-static configurations are suspended, or the resources of these semi-static configurations are invalid (available, valid).

[0375] Alternatively, the terminal performs semi-static downlink reception such as PDCCH MO and CSI-RS on the second carrier only when the second carrier is active; or these semi-static configurations are activated only when the second carrier is active, or the resources of these semi-static configurations are available or valid.

[0376] Alternatively, when the second carrier is not active, or when the first carrier is active, the terminal does not perform semi-static downlink reception such as PDCCH MO and CSI-RS on the second carrier; or these semi-static configurations are suspended, or the resources of these semi-static configurations are invalid (available, valid).

[0377] In some implementations, for handover between two scenarios based on a first semi-static signaling configuration, the terminal does not expect RRC-dedicated configurations to cause overlap between the semi-static transmission and reception resources on the first carrier and the inactivity period of the first carrier; the terminal also does not expect dedicated RRC signaling configurations to cause overlap between the semi-static reception resources on the second carrier and the inactivity period of the second carrier. If cell-specific configurations on the first or second carrier, such as CORESET#0, Type0 / 0A / 1 / 2CSS MO, CD-SSB, or NCD-SSB resources, overlap with the inactivity period of the corresponding carrier, the terminal receives these cell-specific downlink transmissions.

[0378] In some implementations, for switching between two scenarios based on a first semi-static signaling or a second semi-static signaling, the terminal does not expect to receive dynamic scheduling that causes overlap between uplink transmission and downlink reception resources on the first carrier and the inactive time of the first carrier; the terminal does not expect to receive dynamic scheduling that causes overlap between uplink transmission and downlink reception resources on the second carrier and the inactive time of the second carrier. In other words, the terminal expects to receive dynamic scheduling for uplink transmission and downlink reception on the first carrier during its active time; the terminal expects to receive dynamic scheduling for uplink transmission and downlink reception on the second carrier during its active time.

[0379] Example 4:

[0380] In this embodiment, during the carrier switching time, the terminal may not perform uplink transmission or downlink reception on the first carrier, and may not perform downlink reception on the second carrier.

[0381] Alternatively, when switching from the first carrier to the second carrier, the terminal behaves as follows:

[0382] If the terminal reports that it is unable to perform uplink transmission during the handover period from the first carrier to the second carrier; or the frequency domain spacing between the uplink of the first carrier and the downlink of the second carrier is less than the minimum value of the FDD uplink / downlink protection interval or the first value specified in the protocol; or according to the protocol, the terminal does not perform uplink transmission on the first carrier; or it does not require / expect the terminal to perform uplink transmission on the first carrier.

[0383] If the terminal reports that it can perform uplink transmission during the handover time from the first carrier to the second carrier; or the frequency domain spacing between the uplink of the first carrier and the downlink of the second carrier is not less than the minimum value of the FDD uplink / downlink protection interval or the second value specified in the protocol; or according to the protocol, the terminal can perform uplink transmission on the first carrier; or it requests / expects the terminal to perform uplink transmission on the first carrier.

[0384] If the terminal reports that it is unable to receive downlink data on the first carrier during the handover period from the first carrier to the second carrier; or the frequency domain spacing between the downlink data on the first carrier and the downlink data on the second carrier is greater than the third value specified in the protocol; or according to the protocol, the terminal does not receive downlink data on the first carrier; or it does not require / expect the terminal to receive downlink data on the first carrier.

[0385] If the terminal reports that it can perform downlink reception on the first carrier during the handover time from the first carrier to the second carrier; or the frequency domain interval between the downlink of the first carrier and the downlink of the second carrier is less than the fourth value specified in the protocol; or according to the protocol, the terminal can perform downlink reception on the first carrier; or requests / expects the terminal to perform downlink reception on the first carrier;

[0386] If the terminal reports that it is unable to receive downlink data on the second carrier during the handover period from the first carrier to the second carrier; or the frequency domain spacing between the downlink of the first carrier and the downlink of the second carrier is greater than the fifth value specified in the protocol; or according to the protocol, the terminal does not receive downlink data on the second carrier; or it does not require / expect the terminal to receive downlink data on the second carrier.

[0387] If the terminal reports that it can perform downlink reception on the second carrier during the handover time from the first carrier to the second carrier; or the frequency domain interval between the downlink of the first carrier and the downlink of the second carrier is less than the sixth value specified in the protocol; or according to the protocol, the terminal can perform downlink reception on the second carrier; or requests / expects the terminal to perform downlink reception on the second carrier.

[0388] Alternatively, when switching from the second carrier to the first carrier, the terminal behaves as follows:

[0389] If the terminal reports that it is unable to perform uplink transmission during the handover period from the second carrier to the first carrier; or the frequency domain spacing between the uplink of the first carrier and the downlink of the second carrier is less than the minimum value of the FDD uplink / downlink protection interval or the seventh value specified in the protocol; or according to the protocol, the terminal does not perform uplink transmission on the first carrier; or it does not require / expect the terminal to perform uplink transmission on the first carrier.

[0390] If the terminal reports that it can perform uplink transmission during the handover time from the second carrier to the first carrier; or the frequency domain spacing between the uplink of the first carrier and the downlink of the second carrier is not less than the minimum value of the FDD uplink / downlink protection interval or the eighth value specified in the protocol; or according to the protocol, the terminal can perform uplink transmission on the first carrier; or it requests / expects the terminal to perform uplink transmission on the first carrier.

[0391] If the terminal reports that it is unable to receive downlink data on the first carrier during the handover period from the second carrier to the first carrier; or the frequency domain spacing between the downlink of the first carrier and the downlink of the second carrier is greater than the ninth value specified in the protocol; or according to the protocol, the terminal does not receive downlink data on the first carrier; or it does not require / expect the terminal to receive downlink data on the first carrier.

[0392] If the terminal reports that it can perform downlink reception on the first carrier during the handover time from the second carrier to the first carrier; or the frequency domain interval between the downlink of the first carrier and the downlink of the second carrier is less than the tenth value specified in the protocol; or according to the protocol, the terminal can perform downlink reception on the first carrier; or requests / expects the terminal to perform downlink reception on the first carrier;

[0393] If the terminal reports that it is unable to receive downlink data on the second carrier during the handover period from the second carrier to the first carrier; or the frequency domain spacing between the downlink of the first carrier and the downlink of the second carrier is greater than the eleventh value specified in the protocol; or according to the protocol, the terminal does not receive downlink data on the second carrier; or it does not require / expect the terminal to receive downlink data on the second carrier.

[0394] If the terminal reports that it can perform downlink reception on the second carrier during the handover time from the second carrier to the first carrier; or the frequency domain spacing between the downlink of the first carrier and the downlink of the second carrier is less than the twelfth value specified in the protocol; or according to the protocol, the terminal can perform downlink reception on the second carrier; or requests / expects the terminal to perform downlink reception on the second carrier.

[0395] The method provided in this application embodiment enables the introduction of carrier switching signaling into the protocol to support downlink carrier switching with minimal protocol impact, and ensures the robustness of system operation through fallback to PCell events and behaviors.

[0396] The carrier switching method provided in this application can be executed by a carrier switching device. This application uses the example of a carrier switching device executing a connection method to illustrate the carrier switching device provided in this application.

[0397] This application provides a carrier switching device or a message sending device. As an example, the carrier switching device or message sending device can be a communication device or a component in a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0398] A carrier switching device or message transmitting device includes 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 can include general-purpose processors, special-purpose processors, etc., such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0399] Specifically, referring to Figure 7, when the carrier switching device is a terminal or a component within a terminal, the carrier switching device 700 includes:

[0400] The processing module 701 is used to switch between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0401] Optionally, in one of the two scenarios, the terminal performs uplink transmission between the first carrier and the second carrier, or performs uplink transmission on both the first carrier and the second carrier, but does not perform uplink transmission in the other scenario; or

[0402] The terminal performs uplink transmissions in both scenarios.

[0403] Optionally, the switching between the two scenes includes at least one of the following:

[0404] Switch from the first scene to the second scene, or switch from the second scene to the first scene;

[0405] Switch from the first scene to the third scene, or switch from the third scene to the first scene;

[0406] Switch from the first scene to the fourth scene, or switch from the fourth scene to the first scene;

[0407] Switch from the third scene to the fourth scene, or switch from the fourth scene to the third scene;

[0408] In the first scenario, the terminal performs uplink transmission and downlink reception on the first carrier, and does not perform uplink transmission and downlink reception on the second carrier.

[0409] In the second scenario, the terminal does not perform uplink transmission and downlink reception on the first carrier, the terminal performs downlink reception on the second carrier, and the terminal does not perform uplink transmission on the second carrier;

[0410] In the third scenario, the terminal performs downlink reception on the first carrier and does not perform uplink transmission on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier.

[0411] In the fourth scenario, the terminal performs uplink transmission on the first carrier and does not perform downlink reception on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier.

[0412] Optionally, the processing module 701 is used for one of the following:

[0413] The DCI switches between the two scenarios based on the first downlink control information;

[0414] Switching between two scenarios based on high-level configuration;

[0415] The first semi-static signaling is used to switch between the two scenarios based on the first semi-static signaling, which is used to indicate the carrier switching time domain mode.

[0416] The switching between the two scenarios is based on the second semi-static signaling, which is used to indicate downlink reception on the first carrier or the second carrier.

[0417] Switch between two scenarios based on at least one condition.

[0418] Optionally, the processing module 701 is used to switch between two scenarios when the downlink reception carrier scheduled by the first DCI is different from the downlink reception carrier of the previous or last time.

[0419] Optionally, the processing module 701 is further configured to determine, based on at least one of the second DCI and the first time, whether the carrier on which the downlink reception scheduled by the first DCI is located is the same as the carrier on which the previous or last downlink reception was located, wherein the first time includes the difference between the start time and the handover preparation time corresponding to the downlink reception scheduled by the first DCI, and the second DCI is the DCI received before the first DCI.

[0420] Optionally, the first DCI indicates the carrier on which downlink reception is located via a carrier indication field; or,

[0421] The first DCI indicates the carrier on which the downlink reception is located using 1 bit; or,

[0422] The first DCI indicates the carrier on which downlink reception is located by using the most significant bit (MSB) in the Frequency Domain Resource Allocation (FDRA) field; or...

[0423] The first DCI indicates the carrier on which the downlink reception is located via a Hybrid Automatic Repeat Request (HARQ) process number.

[0424] Optionally, the processing module 701 is used for at least one of the following:

[0425] When the uplink transmission of the terminal is only performed on the first carrier, the terminal switches between two scenarios based on the first DCI. The switching between the two scenarios includes switching the downlink reception from the second carrier to the first carrier.

[0426] When the terminal receives a first DCI of a first format on the first carrier, it switches between two scenarios, and the switching between the two scenarios includes switching downlink reception from the first carrier to the second carrier.

[0427] When the terminal receives a first DCI of a second format on the second carrier, it switches between two scenarios, and the switching between the two scenarios includes switching downlink reception from the second carrier to the first carrier.

[0428] Optionally, the first semi-static signaling is used to indicate at least one of the following:

[0429] At least one time unit of active carrier;

[0430] The usage period of the carrier switching time-domain mode;

[0431] The length of the carrier switching time-domain mode;

[0432] The start time or time offset of the carrier switching time-domain mode.

[0433] Optionally, in the carrier switching time domain mode, the terminal performs at least one of uplink transmission and downlink reception in the time unit when the effective carrier is the first carrier, and the terminal performs downlink reception in the time unit when the effective carrier is the second carrier.

[0434] Optionally, the carrier switching in the carrier switching time-domain mode of the processing module 701 satisfies at least one of the following:

[0435] The number of handovers does not exceed the number of carrier handovers supported by the terminal;

[0436] The number of handovers shall not exceed the maximum number of carrier handovers specified in the protocol;

[0437] The switching time shall not exceed the switching time specified in the protocol.

[0438] Optionally, the handover between the two scenarios includes switching from the first carrier to the second carrier in the downlink reception:

[0439] The terminal does not wish to activate the second carrier if the network-side device has not yet instructed the terminal on the carrier switching time domain mode.

[0440] Optionally, the processing module 701 is used for one of the following:

[0441] When the first semi-static signaling indicates multiple carrier switching time-domain modes, the terminal determines the effective carrier switching time-domain mode among the multiple carrier switching time-domain modes based on the Media Access Control Unit (MAC CE) or physical layer information, and switches between two scenarios based on the effective carrier switching time-domain mode.

[0442] When the first semi-static signaling indicates multiple carrier switching time-domain modes, the terminal switches between two scenarios based on the time-cascaded multiple carrier switching time-domain modes.

[0443] Optionally, in the case of at least two carrier switching time-domain modes in effect, there is no carrier conflict between the at least two carrier switching time-domain modes in effect.

[0444] Optionally, when the handover between the two scenarios includes a switch from downlink reception to the first carrier, the at least one condition includes:

[0445] The uplink transmission that needs to be performed on the first carrier is triggered;

[0446] The second carrier is deconfigured, deactivated, or put to sleep, and the active bandwidth portion (BWP) on the second carrier becomes dormant.

[0447] Link failure occurred;

[0448] The channel quality on the second carrier is below a preset threshold;

[0449] The timer corresponding to the second carrier timed out;

[0450] And / or,

[0451] In the case where the handover between the two scenarios includes a downlink reception switch from the first carrier to the second carrier, the at least one condition includes:

[0452] The first carrier is deconfigured, deactivated, or put to sleep, and the active bandwidth portion (BWP) on the first carrier becomes dormant.

[0453] Link failure occurred;

[0454] The channel quality on the first carrier is lower than a preset threshold;

[0455] The timer corresponding to the first carrier timed out.

[0456] Optionally, the processing module 701 is configured to, under the at least one condition, if the terminal receives the first semi-static signaling or the second semi-static signaling, ignore the first semi-static signaling or the second semi-static signaling, and switch between the two scenarios based on the at least one condition.

[0457] Optionally, the processing module 701 is further configured to switch between two scenarios based on the first semi-static signaling or the second semi-static signaling under the second condition, wherein the switching between the two scenarios includes: switching downlink reception from the second carrier to the first carrier, or switching downlink reception from the first carrier to the second carrier.

[0458] The second condition includes at least one of the following:

[0459] The terminal receives a signaling instruction indicating that the first semi-static signaling or the second semi-static signaling is effective;

[0460] The random access process has ended;

[0461] The second carrier is activated again;

[0462] The second carrier becomes a non-dormant carrier.

[0463] Optionally, during the switching time between the two scenarios, the terminal satisfies one of the following conditions:

[0464] Uplink transmission is not required or expected, and downlink reception is not required or expected.

[0465] Uplink transmission is neither required nor expected.

[0466] Downlink reception is neither required nor expected.

[0467] Optionally, when the first carrier and the second carrier are a combination of the first carriers: the terminal does not request or expect to perform uplink transmission during the handover time, and does not request or expect to perform downlink reception; or, the terminal does not request or expect to perform uplink transmission during the handover time; or...

[0468] When the first carrier and the second carrier are a combination of the second carriers: the terminal does not require or expect to receive downlink data during the switching time.

[0469] Optionally, one of the first carrier and the second carrier satisfies at least one of the following:

[0470] Primary cell PCell or primary / secondary cell PSCell;

[0471] The duplex mode is Frequency Division Multiplexing (FDD).

[0472] The first carrier and the other carrier of the second carrier satisfy at least one of the following:

[0473] As a secondary cell SCell;

[0474] To supplement the downlink SDL carrier.

[0475] Optionally, the processing capabilities of the terminal on the first carrier and the second carrier satisfy at least one of the following:

[0476] The terminals on the first carrier and the second carrier have the same Physical Downlink Shared Channel (PDSCH) processing capability.

[0477] The physical uplink shared channel (PUSCH) processing capabilities of the terminals on the first carrier and the second carrier are different.

[0478] Optionally, the first carrier and the second carrier satisfy at least one of the following:

[0479] The parameter sets (numerology) of the first carrier and the second carrier are the same;

[0480] The baseband bandwidth of the first carrier and the second carrier is the same, or the difference between the baseband bandwidth of the first carrier and the second carrier is less than or equal to the bandwidth threshold.

[0481] The difference in power spectral density (PSD) between the first carrier and the second carrier does not exceed the power threshold.

[0482] The first carrier and the second carrier share an indication for activating or deactivating cell discontinuous transmission (DTX);

[0483] At least one of the first carrier and the second carrier supports self-scheduling, and among the at least one carrier that supports self-scheduling, one carrier self-scheduling can only schedule downlink reception;

[0484] At least one of the first carrier and the second carrier supports cross-carrier scheduling, and the cross-carrier scheduling of one of the at least one carrier that supports cross-carrier scheduling can only schedule downlink reception;

[0485] At least one of the first carrier and the second carrier can be configured with at least one of the control resource set CORESET, physical downlink control channel PDCCH, and search space;

[0486] One of the first carrier and the second carrier supports cross-carrier scheduled uplink DCI, while the other carrier does not support cross-carrier scheduled uplink DCI.

[0487] The aforementioned carrier switching device can improve the communication performance of the terminal.

[0488] The carrier switching device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG2 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0489] Specifically, referring to Figure 8, when the message sending device is a network-side device or a component within a network-side device, the message sending device 800 includes:

[0490] The sending module 801 is used to send a first message to the terminal. The first message is used to instruct the terminal to switch between two scenarios. The switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0491] Optionally, the device further includes:

[0492] The processing module is used to perform downlink transmission carrier switching, which includes: switching downlink transmission from a first carrier to a second carrier, or switching downlink transmission from a second carrier to a first carrier.

[0493] In this embodiment, it refers to the case where the first carrier and the second carrier correspond to the same network-side device.

[0494] Optionally, the first message includes at least one of the following:

[0495] First downlink control information (DCI), first semi-static signaling, second semi-static signaling;

[0496] The first DCI is used to indicate the carrier on which downlink reception is located;

[0497] The first semi-static signaling is used to indicate the carrier switching time-domain mode;

[0498] The second semi-static signaling is used to indicate downlink reception on the first carrier or the second carrier.

[0499] Optionally, the first DCI indicates the carrier on which downlink reception is located via a carrier indication field; or,

[0500] The first DCI indicates the carrier on which the downlink reception is located using 1 bit; or,

[0501] The first DCI indicates the carrier on which downlink reception is located by using the most significant bit (MSB) in the Frequency Domain Resource Allocation (FDRA) field; or...

[0502] The first DCI indicates the carrier on which the downlink reception is located via a Hybrid Automatic Repeat Request (HARQ) process number.

[0503] Optionally, the first semi-static signaling is used to indicate at least one of the following:

[0504] At least one time unit of active carrier;

[0505] The usage period of the time-domain mode;

[0506] The length of the time-domain pattern;

[0507] The start time or time offset of the time-domain mode.

[0508] Optionally, in the carrier switching time domain mode, the terminal performs at least one of uplink transmission and downlink reception in the time unit when the effective carrier is the first carrier, and the terminal performs downlink reception in the time unit when the effective carrier is the second carrier.

[0509] Sending the above messages can improve the communication performance of the terminal.

[0510] The carrier switching device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG3 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0511] As shown in Figure 9, this application embodiment also provides a communication device 900, including a processor 901 and a memory 902. The memory 902 stores programs or instructions that can run on the processor 901. For example, when the communication device 900 is a terminal, the program or instructions executed by the processor 901 implement the various steps of the above-described connection method embodiment and achieve the same technical effect. When the communication device 900 is a network-side device, the program or instructions executed by the processor 901 implement the various steps of the above-described connection method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0512] This application 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 the steps in the method embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the carrier switching device shown in FIG7. Specifically, FIG10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application, which is a first terminal.

[0513] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0514] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1010 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 10 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.

[0515] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processor 10041 and a microphone 10042. The graphics processor 10041 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 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 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.

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

[0517] The memory 1009 can be used to store software programs or instructions, as well as various data. The memory 1009 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 1009 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 1009 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0518] The processor 1010 may include one or more processing units; optionally, the processor 1010 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 the processor 1010.

[0519] The processor 1010 is used to switch between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0520] Optionally, in one of the two scenarios, the terminal performs uplink transmission between the first carrier and the second carrier, or performs uplink transmission on both the first carrier and the second carrier, but does not perform uplink transmission in the other scenario; or

[0521] The terminal performs uplink transmissions in both scenarios.

[0522] Optionally, the switching between the two scenes includes at least one of the following:

[0523] Switch from the first scene to the second scene, or switch from the second scene to the first scene;

[0524] Switch from the first scene to the third scene, or switch from the third scene to the first scene;

[0525] Switch from the first scene to the fourth scene, or switch from the fourth scene to the first scene;

[0526] Switch from the third scene to the fourth scene, or switch from the fourth scene to the third scene;

[0527] In the first scenario, the terminal performs uplink transmission and downlink reception on the first carrier, and does not perform uplink transmission and downlink reception on the second carrier.

[0528] In the second scenario, the terminal does not perform uplink transmission and downlink reception on the first carrier, the terminal performs downlink reception on the second carrier, and the terminal does not perform uplink transmission on the second carrier;

[0529] In the third scenario, the terminal performs downlink reception on the first carrier and does not perform uplink transmission on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier.

[0530] In the fourth scenario, the terminal performs uplink transmission on the first carrier and does not perform downlink reception on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier.

[0531] Optionally, the switching between the two scenes includes one of the following:

[0532] The DCI switches between the two scenarios based on the first downlink control information;

[0533] Switching between two scenarios based on high-level configuration;

[0534] The first semi-static signaling is used to switch between the two scenarios based on the first semi-static signaling, which is used to indicate the carrier switching time domain mode.

[0535] The switching between the two scenarios is based on the second semi-static signaling, which is used to indicate downlink reception on the first carrier or the second carrier.

[0536] Switch between two scenarios based on at least one condition.

[0537] Optionally, the switching between the two scenarios based on downlink control information (DCI) includes:

[0538] If the downlink reception carrier scheduled by the first DCI is different from the downlink reception carrier of the previous or last time, the terminal switches between the two scenarios.

[0539] Optionally, the processor 1010 is further configured to determine, based on at least one of the second DCI and the first time, whether the carrier on which the downlink reception scheduled by the first DCI is located is the same as the carrier on which the previous or last downlink reception was located, wherein the first time includes: the difference between the start time and the handover preparation time corresponding to the downlink reception scheduled by the first DCI, and the second DCI is the DCI received before the first DCI.

[0540] Optionally, the first DCI indicates the carrier on which downlink reception is located via a carrier indication field; or,

[0541] The first DCI indicates the carrier on which the downlink reception is located using 1 bit; or,

[0542] The first DCI indicates the carrier on which downlink reception is located by using the most significant bit (MSB) in the Frequency Domain Resource Allocation (FDRA) field; or...

[0543] The first DCI indicates the carrier on which the downlink reception is located via a Hybrid Automatic Repeat Request (HARQ) process number.

[0544] Optionally, the switching between the two scenes based on the first DCI includes at least one of the following:

[0545] When the uplink transmission of the terminal is only performed on the first carrier, the terminal switches between two scenarios based on the first DCI. The switching between the two scenarios includes switching the downlink reception from the second carrier to the first carrier.

[0546] When the terminal receives a first DCI of a first format on the first carrier, it switches between two scenarios, and the switching between the two scenarios includes switching downlink reception from the first carrier to the second carrier.

[0547] When the terminal receives a first DCI of a second format on the second carrier, it switches between two scenarios, and the switching between the two scenarios includes switching downlink reception from the second carrier to the first carrier.

[0548] Optionally, the first semi-static signaling is used to indicate at least one of the following:

[0549] At least one time unit of active carrier;

[0550] The usage period of the carrier switching time-domain mode;

[0551] The length of the carrier switching time-domain mode;

[0552] The start time or time offset of the carrier switching time-domain mode.

[0553] Optionally, in the carrier switching time domain mode, the terminal performs at least one of uplink transmission and downlink reception in the time unit when the effective carrier is the first carrier, and the terminal performs downlink reception in the time unit when the effective carrier is the second carrier.

[0554] Optionally, the carrier switching of the terminal in the carrier switching time-domain mode satisfies at least one of the following:

[0555] The number of handovers does not exceed the number of carrier handovers supported by the terminal;

[0556] The number of handovers shall not exceed the maximum number of carrier handovers specified in the protocol;

[0557] The switching time shall not exceed the switching time specified in the protocol.

[0558] Optionally, the handover between the two scenarios includes switching from the first carrier to the second carrier in the downlink reception:

[0559] The terminal does not wish to activate the second carrier if the network-side device has not yet instructed the terminal on the carrier switching time domain mode.

[0560] Optionally, the handover between the two scenarios based on the first semi-static signaling includes one of the following:

[0561] When the first semi-static signaling indicates multiple carrier switching time-domain modes, the effective carrier switching time-domain mode among the multiple carrier switching time-domain modes is determined based on the Media Access Control Unit (MAC CE) or physical layer information, and the switching is performed between the two scenarios based on the effective carrier switching time-domain mode.

[0562] When the first semi-static signaling indicates multiple carrier switching time-domain modes, the multiple carrier switching time-domain modes, which are time-cascaded, switch between two scenarios.

[0563] Optionally, in the case of at least two carrier switching time-domain modes in effect, there is no carrier conflict between the at least two carrier switching time-domain modes in effect.

[0564] Optionally, when the handover between the two scenarios includes a switch from downlink reception to the first carrier, the at least one condition includes:

[0565] The uplink transmission that needs to be performed on the first carrier is triggered;

[0566] The second carrier is deconfigured, deactivated, or put to sleep, and the active bandwidth portion (BWP) on the second carrier becomes dormant.

[0567] Link failure occurred;

[0568] The channel quality on the second carrier is below a preset threshold;

[0569] The timer corresponding to the second carrier timed out;

[0570] And / or,

[0571] In the case where the handover between the two scenarios includes a downlink reception switch from the first carrier to the second carrier, the at least one condition includes:

[0572] The first carrier is deconfigured, deactivated, or put to sleep, and the active bandwidth portion (BWP) on the first carrier becomes dormant.

[0573] Link failure occurred;

[0574] The channel quality on the first carrier is lower than a preset threshold;

[0575] The timer corresponding to the first carrier timed out.

[0576] Optionally, the switching between the two scenes includes:

[0577] Under at least one of the conditions, if the terminal receives the first semi-static signaling or the second semi-static signaling, it ignores the first semi-static signaling or the second semi-static signaling and switches between the two scenarios based on the at least one condition.

[0578] Optionally, the processor 1010 is further configured to, under a second condition, re-switch between two scenarios based on the first semi-static signaling or the second semi-static signaling, wherein re-switching between the two scenarios includes: switching downlink reception from the second carrier to the first carrier, or switching downlink reception from the first carrier to the second carrier;

[0579] The second condition includes at least one of the following:

[0580] The terminal receives a signaling instruction indicating that the first semi-static signaling or the second semi-static signaling is effective;

[0581] The random access process has ended;

[0582] The second carrier is activated again;

[0583] The second carrier becomes a non-dormant carrier.

[0584] Optionally, during the switching time between the two scenarios, the terminal satisfies one of the following conditions:

[0585] Uplink transmission is not required or expected, and downlink reception is not required or expected.

[0586] Uplink transmission is neither required nor expected.

[0587] Downlink reception is neither required nor expected.

[0588] Optionally, when the first carrier and the second carrier are a combination of the first carriers: the terminal does not request or expect to perform uplink transmission during the handover time, and does not request or expect to perform downlink reception; or, the terminal does not request or expect to perform uplink transmission during the handover time; or...

[0589] When the first carrier and the second carrier are a combination of the second carriers: the terminal does not require or expect to receive downlink data during the switching time.

[0590] Optionally, one of the first carrier and the second carrier satisfies at least one of the following:

[0591] Primary cell PCell or primary / secondary cell PSCell;

[0592] The duplex mode is Frequency Division Multiplexing (FDD).

[0593] The first carrier and the other carrier of the second carrier satisfy at least one of the following:

[0594] As a secondary cell SCell;

[0595] To supplement the downlink SDL carrier.

[0596] Optionally, the processing capabilities of the terminal on the first carrier and the second carrier satisfy at least one of the following:

[0597] The terminals on the first carrier and the second carrier have the same Physical Downlink Shared Channel (PDSCH) processing capability.

[0598] The physical uplink shared channel (PUSCH) processing capabilities of the terminals on the first carrier and the second carrier are different.

[0599] Optionally, the first carrier and the second carrier satisfy at least one of the following:

[0600] The parameter sets (numerology) of the first carrier and the second carrier are the same;

[0601] The baseband bandwidth of the first carrier and the second carrier is the same, or the difference between the baseband bandwidth of the first carrier and the second carrier is less than or equal to the bandwidth threshold.

[0602] The difference in power spectral density (PSD) between the first carrier and the second carrier does not exceed the power threshold.

[0603] The first carrier and the second carrier share an indication for activating or deactivating cell discontinuous transmission (DTX);

[0604] At least one of the first carrier and the second carrier supports self-scheduling, and among the at least one carrier that supports self-scheduling, one carrier self-scheduling can only schedule downlink reception;

[0605] At least one of the first carrier and the second carrier supports cross-carrier scheduling, and the cross-carrier scheduling of one of the at least one carrier that supports cross-carrier scheduling can only schedule downlink reception;

[0606] At least one of the first carrier and the second carrier can be configured with at least one of the control resource set CORESET, physical downlink control channel PDCCH, and search space;

[0607] One of the first carrier and the second carrier supports cross-carrier scheduled uplink DCI, while the other carrier does not support cross-carrier scheduled uplink DCI.

[0608] The above methods can reduce the power consumption of the terminal.

[0609] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0610] This application also provides a device including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG3. This device embodiment corresponds to the above-described resource configuration method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this device embodiment and can achieve the same technical effect.

[0611] Specifically, this application embodiment also provides a network-side device, which may be the message sending device shown in FIG8. As shown in FIG11, the device 1100 includes: an antenna 1101, a radio frequency device 1102, a baseband device 1103, a processor 1104, and a memory 1105. The antenna 1101 is connected to the radio frequency device 1102. In the uplink direction, the radio frequency device 1102 receives information through the antenna 1101 and sends the received information to the baseband device 1103 for processing. In the downlink direction, the baseband device 1103 processes the information to be sent and sends it to the radio frequency device 1102, which processes the received information and then sends it out through the antenna 1101.

[0612] The methods executed by the device in the above embodiments can be implemented in the baseband device 1103, which includes a baseband processor.

[0613] The baseband device 1103 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG11. One of the chips is, for example, a baseband processor, which is connected to the memory 1105 via a bus interface to call the program in the memory 1105 and execute the network device operation shown in the above method embodiment.

[0614] The device may also include a network interface 1106, such as a Common Public Radio Interface (CPRI).

[0615] Specifically, the device 1100 in this application embodiment further includes: instructions or programs stored in memory 1105 and executable on processor 1104. Processor 1104 calls the instructions or programs in memory 1105 to execute the methods executed by each module shown in FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0616] Radio frequency device 1102 is used to send a first message to a terminal, the first message being used to instruct the terminal to switch between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier.

[0617] Optionally, the processor 1104 is further configured to perform downlink transmission carrier switching, the downlink transmission carrier switching including: switching downlink transmission from a first carrier to a second carrier, or switching downlink transmission from a second carrier to a first carrier.

[0618] In this embodiment, it refers to the case where the first carrier and the second carrier correspond to the same network-side device.

[0619] Optionally, the first message includes at least one of the following:

[0620] First downlink control information (DCI), first semi-static signaling, second semi-static signaling;

[0621] The first DCI is used to indicate the carrier on which downlink reception is located;

[0622] The first semi-static signaling is used to indicate the carrier switching time-domain mode;

[0623] The second semi-static signaling is used to indicate downlink reception on the first carrier or the second carrier.

[0624] Optionally, the first DCI indicates the carrier on which downlink reception is located via a carrier indication field; or,

[0625] The first DCI indicates the carrier on which the downlink reception is located using 1 bit; or,

[0626] The first DCI indicates the carrier on which downlink reception is located by using the most significant bit (MSB) in the Frequency Domain Resource Allocation (FDRA) field; or...

[0627] The first DCI indicates the carrier on which the downlink reception is located via a Hybrid Automatic Repeat Request (HARQ) process number.

[0628] Optionally, the first semi-static signaling is used to indicate at least one of the following:

[0629] At least one time unit of active carrier;

[0630] The usage period of the time-domain mode;

[0631] The length of the time-domain pattern;

[0632] The start time or time offset of the time-domain mode.

[0633] Optionally, in the carrier switching time domain mode, the terminal performs at least one of uplink transmission and downlink reception in the time unit when the effective carrier is the first carrier, and the terminal performs downlink reception in the time unit when the effective carrier is the second carrier.

[0634] The aforementioned equipment can improve the communication performance of the terminal.

[0635] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the resource configuration method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0636] This application also provides a readable storage medium storing a program or instructions. When executed by a processor, the program or instructions implement the various processes of the above-described carrier switching method or message sending method embodiments, achieving the same technical effects. To avoid repetition, these will not be described again here. The processor is the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes a computer-readable storage medium, such as a 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.

[0637] This application also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described carrier switching method or message sending method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here. It should be understood that the chip mentioned in this application embodiment can also be called a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0638] 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 various processes of the above-described carrier switching method or message sending method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0639] This application also provides a wireless communication system, including: a terminal and a network-side device. The terminal can be used to perform the steps of the carrier switching method provided in this application, and the network-side device can be used to perform the steps of the message sending method provided in this application.

[0640] 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.

[0641] 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 the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0642] 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

A carrier switching method, comprising: The terminal switches between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier. The method of claim 1, wherein, In one of the two scenarios, the terminal performs uplink transmission between the first carrier and the second carrier, or performs uplink transmission on both the first carrier and the second carrier, but does not perform uplink transmission in the other scenario; or The terminal performs uplink transmissions in both scenarios. The method according to claim 1 or 2, wherein The switching between the two scenes includes the following: Switch from the first scene to the second scene, or switch from the second scene to the first scene; Switch from the first scene to the third scene, or switch from the third scene to the first scene; Switch from the first scene to the fourth scene, or switch from the fourth scene to the first scene; Switch from the third scene to the fourth scene, or switch from the fourth scene to the third scene; In the first scenario, the terminal performs uplink transmission and downlink reception on the first carrier, and does not perform uplink transmission and downlink reception on the second carrier. In the second scenario, the terminal does not perform uplink transmission and downlink reception on the first carrier, the terminal performs downlink reception on the second carrier, and the terminal does not perform uplink transmission on the second carrier; In the third scenario, the terminal performs downlink reception on the first carrier and does not perform uplink transmission on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier. In the fourth scenario, the terminal performs uplink transmission on the first carrier and does not perform downlink reception on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier. The method of any one of claims 1 to 3, wherein, The switching of the terminal between the two scenarios includes the following: The terminal switches between the two scenarios based on the first downlink control information (DCI). The terminal switches between two scenarios based on high-level configuration; The terminal switches between two scenarios based on a first semi-static signaling, which is used to indicate the carrier switching time domain mode. The terminal switches between two scenarios based on a second semi-static signaling, which is used to indicate downlink reception on the first carrier or the second carrier. The terminal switches between two scenarios based on at least one condition. The method of claim 4, wherein, The terminal switching between two scenes based on the first DCI includes: If the downlink reception carrier scheduled by the first DCI is different from the downlink reception carrier of the previous or last time, the terminal switches between the two scenarios. The method according to claim 5, further comprising: The terminal determines, based on at least one of the second DCI and the first time, whether the downlink reception carrier scheduled by the first DCI is the same as the carrier of the previous or last downlink reception. The first time includes the difference between the start time and the handover preparation time corresponding to the downlink reception scheduled by the first DCI. The second DCI is the DCI received before the first DCI. The method of any one of claims 4 to 6, wherein, The first DCI indicates the carrier on which downlink reception is located via the carrier indication field; or, The first DCI indicates the carrier on which the downlink reception is located using 1 bit; or, The first DCI indicates the carrier on which downlink reception is located by using the most significant bit (MSB) in the Frequency Domain Resource Allocation (FDRA) field; or... The first DCI indicates the carrier on which the downlink reception is located via a Hybrid Automatic Repeat Request (HARQ) process number. The method of any one of claims 4 to 6, wherein, The terminal switching between two scenes based on the first DCI includes at least one of the following: When the uplink transmission of the terminal is only performed on the first carrier, the terminal switches between two scenarios based on the first DCI. The switching between the two scenarios includes switching the downlink reception from the second carrier to the first carrier. When the terminal receives a first DCI of a first format on the first carrier, the terminal switches between two scenarios, and the switching between the two scenarios includes switching downlink reception from the first carrier to the second carrier. When the terminal receives a first DCI of a second format on the second carrier, the terminal switches between two scenarios, and the switching between the two scenarios includes switching downlink reception from the second carrier to the first carrier. The method of claim 4, wherein, The first semi-static signaling is used to indicate at least one of the following: At least one effective carrier in time unit; the usage period of the carrier switching time domain mode; the length of the carrier switching time domain mode; the start time or time domain offset of the carrier switching time domain mode. The method of claim 9, wherein, In the carrier switching time domain mode, the terminal performs at least one of uplink transmission and downlink reception in the time unit when the effective carrier is the first carrier, and performs downlink reception in the time unit when the effective carrier is the second carrier. The method according to claim 4, 9 or 10, wherein, The carrier switching of the terminal in the carrier switching time-domain mode satisfies at least one of the following: The number of handovers does not exceed the number of carrier handovers supported by the terminal; The number of handovers shall not exceed the maximum number of carrier handovers specified in the protocol; The switching time shall not exceed the switching time specified in the protocol. The method of claim 4, 9, 10, or 11, wherein, The handover between the two scenarios includes the case where downlink reception is switched from the first carrier to the second carrier: The terminal does not wish to activate the second carrier if the network-side device has not yet instructed the terminal on the carrier switching time domain mode. The method of claim 4, 9, 10, 11, or 12, wherein, The terminal switching between two scenarios based on the first semi-static signaling includes the following: When the first semi-static signaling indicates multiple carrier switching time-domain modes, the terminal determines the effective carrier switching time-domain mode among the multiple carrier switching time-domain modes based on the Media Access Control Unit (MAC CE) or physical layer information, and switches between two scenarios based on the effective carrier switching time-domain mode. When the first semi-static signaling indicates multiple carrier switching time-domain modes, the terminal switches between two scenarios based on the time-cascaded multiple carrier switching time-domain modes. The method of claim 4, 9, 10, 11, or 12, wherein, When at least two carrier switching time-domain modes are active, there is no carrier conflict between the two active carrier switching time-domain modes. The method of claim 4, wherein, In the case where the handover between the two scenarios includes a downlink reception switch from the second carrier to the first carrier, the at least one condition includes: The uplink transmission that needs to be performed on the first carrier is triggered; The second carrier is deconfigured, deactivated, or put to sleep, and the active bandwidth portion (BWP) on the second carrier becomes dormant. Link failure occurred; The channel quality on the second carrier is below a preset threshold; The timer corresponding to the second carrier timed out; And / or, In the case where the handover between the two scenarios includes a downlink reception switch from the first carrier to the second carrier, the at least one condition includes: The first carrier is deconfigured, deactivated, or put to sleep, and the active bandwidth portion (BWP) on the first carrier becomes dormant. Link failure occurred; The channel quality on the first carrier is lower than a preset threshold; The timer corresponding to the first carrier timed out. The method of any one of claims 4-15, wherein The switching of the terminal between the two scenarios includes: Under at least one of the conditions, if the terminal receives the first semi-static signaling or the second semi-static signaling, the terminal ignores the first semi-static signaling or the second semi-static signaling and switches between the two scenarios based on the at least one condition. The method of claim 16, wherein, After the terminal ignores the first semi-static signaling or the second semi-static signaling, the method further includes: Under the second condition, the terminal switches between the two scenarios again based on the first semi-static signaling or the second semi-static signaling. The switching between the two scenarios includes: switching downlink reception from the second carrier to the first carrier, or switching downlink reception from the first carrier to the second carrier. The second condition includes at least one of the following: The terminal receives a signaling instruction indicating that the first semi-static signaling or the second semi-static signaling is effective; The random access process has ended; The second carrier is activated again; The second carrier becomes a non-dormant carrier. The method of any one of claims 1 to 17, wherein, During the switching time between the two scenarios, the terminal satisfies one of the following conditions: Uplink transmission is neither required nor expected, and downlink reception is neither required nor expected. Uplink transmission is neither required nor expected. Downlink reception is neither required nor expected. The method of claim 18, wherein, When the first carrier and the second carrier are a combination of the first carriers: the terminal does not request or expect to perform uplink transmission during the handover period, and does not request or expect to perform downlink reception; or, the terminal does not request or expect to perform uplink transmission during the handover period; or... When the first carrier and the second carrier are a combination of the second carriers: the terminal does not require or expect to receive downlink data during the switching time. The method of any one of claims 1 to 19, wherein, One of the first carrier and the second carrier satisfies at least one of the following: it is a primary cell PCell or a primary-secondary cell PSCell; the duplex mode is frequency division multiplexing (FDD). The first carrier and the other carrier of the second carrier satisfy at least one of the following: it is a secondary cell SCell; it is a supplementary downlink SDL carrier. The method of any one of claims 1 to 20, wherein, The processing capabilities of the terminal on the first carrier and the second carrier satisfy at least one of the following: The terminals on the first carrier and the second carrier have the same Physical Downlink Shared Channel (PDSCH) processing capability; The physical uplink shared channel (PUSCH) processing capabilities of the terminals on the first carrier and the second carrier are different. The method of any one of claims 1 to 21, wherein, The first carrier and the second carrier satisfy at least one of the following: The parameter sets (numerology) of the first carrier and the second carrier are the same; The baseband bandwidth of the first carrier and the second carrier is the same, or the difference between the baseband bandwidth of the first carrier and the second carrier is less than or equal to the bandwidth threshold. The difference in power spectral density (PSD) between the first carrier and the second carrier does not exceed the power threshold. The first carrier and the second carrier share an indication for activating or deactivating cell discontinuous transmission (DTX); At least one of the first carrier and the second carrier supports self-scheduling, and among the at least one carrier that supports self-scheduling, one carrier self-scheduling can only schedule downlink reception; At least one of the first carrier and the second carrier supports cross-carrier scheduling, and the cross-carrier scheduling of one of the at least one carrier that supports cross-carrier scheduling can only schedule downlink reception; At least one of the first carrier and the second carrier can be configured with at least one of the control resource set CORESET, physical downlink control channel PDCCH, and search space; One of the first carrier and the second carrier supports cross-carrier scheduled uplink DCI, while the other carrier does not support cross-carrier scheduled uplink DCI. A message sending method, comprising: The network-side device sends a first message to the terminal, which instructs the terminal to switch between two scenarios. The switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier. The method according to claim 23, further comprising: The network-side device performs downlink transmission carrier switching, which includes switching downlink transmission from a first carrier to a second carrier, or switching downlink transmission from a second carrier to a first carrier. The method according to claim 23 or 24, wherein The first message includes at least one of the following: First downlink control information (DCI), first semi-static signaling, second semi-static signaling; The first DCI is used to indicate the carrier on which downlink reception is located; The first semi-static signaling is used to indicate the carrier switching time-domain mode; The second semi-static signaling is used to indicate downlink reception on the first carrier or the second carrier. A carrier switching device, comprising: The processing module is used to switch between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier. The apparatus of claim 26, wherein The terminal corresponding to the device performs uplink transmission on either the first carrier or the second carrier in the two scenarios, or performs uplink transmission on both the first carrier and the second carrier, but does not perform uplink transmission in the other scenario; or The terminal performs uplink transmissions in both scenarios. The apparatus of claim 26 or 27, wherein The switching between the two scenes includes at least one of the following: Switch from the first scene to the second scene, or switch from the second scene to the first scene; Switch from the first scene to the third scene, or switch from the third scene to the first scene; Switch from the first scene to the fourth scene, or switch from the fourth scene to the first scene; Switch from the third scene to the fourth scene, or switch from the fourth scene to the third scene; In the first scenario, the terminal performs uplink transmission and downlink reception on the first carrier, but does not perform uplink transmission and downlink reception on the second carrier. In the second scenario, the terminal does not perform uplink transmission and downlink reception on the first carrier, the terminal performs downlink reception on the second carrier, and the terminal does not perform uplink transmission on the second carrier; In the third scenario, the terminal performs downlink reception on the first carrier and does not perform uplink transmission on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier. In the fourth scenario, the terminal performs uplink transmission on the first carrier and does not perform downlink reception on the first carrier; the terminal performs downlink reception on the second carrier and does not perform uplink transmission on the second carrier. The apparatus of any one of claims 26 to 28, wherein The processing module is used for one of the following: The DCI switches between the two scenarios based on the first downlink control information; Switching between two scenarios based on high-level configuration; The first semi-static signaling is used to switch between the two scenarios based on the first semi-static signaling, which is used to indicate the time domain mode; The switching between the two scenarios is based on the second semi-static signaling, which is used to indicate downlink reception on the second carrier; Switch between two scenarios based on at least one condition. A message sending device, comprising: The sending module is used to send a first message to the terminal, the first message being used to instruct the terminal to switch between two scenarios, wherein the switching between the two scenarios includes: switching downlink reception from a first carrier to a second carrier, or switching downlink reception from a second carrier to a first carrier. The method further comprises: The processing module is used to perform downlink transmission carrier switching, which includes: switching downlink transmission from a first carrier to a second carrier, or switching downlink transmission from a second carrier to a first carrier. A terminal includes 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 carrier switching method as described in any one of claims 1 to 22. A network-side device includes 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 message sending method as described in any one of claims 23 to 25. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the carrier switching method as described in any one of claims 1 to 22, or the steps of the message sending method as described in any one of claims 23 to 25. A computer program product stored in a storage medium, the computer program product being executed by at least one processor to implement the steps of the carrier switching method as claimed in any one of claims 1 to 22, or the computer program product being executed by at least one processor to implement the steps of the carrier switching method as claimed in any one of claims 23 to 25.

Images