Wireless communication method and apparatus, and device

Abstract

The present application relates to the field of communications, and discloses a wireless communication method and apparatus, and a device. The wireless communication method in embodiments of the present application comprises: a terminal acquires first information, wherein the first information comprises at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers; the terminal determines a target uplink carrier on the basis of the first information, and the terminal sends first uplink information on the basis of the target uplink carrier; and / or the terminal determines a target downlink carrier on the basis of the first information, and the terminal receives first downlink information on the basis of the target downlink carrier.

Description

Wireless communication methods, apparatus and equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411561167.5, filed on November 4, 2024, entitled "Wireless Communication Method, Apparatus and Device", 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 wireless communication method, apparatus, and device. Background Technology

[0004] In related technologies, for Small Data Transmission (SDT) based on Random Access Channel (RACH) or Layer 1 / L2-triggered mobility (LTM) based on RACH, after the terminal selects a downlink carrier for random access, the random access process is completed on the selected downlink carrier and its associated downlink carriers. This method is relatively inflexible, does not support adjusting the carrier during the random access process due to changes in load, interference, etc., and is not suitable for multi-carrier or carrier group scenarios. For SDT based on Configured Grant (CG) or RACH-less handover, when the uplink carrier associated with the downlink carrier has a CG configuration and certain conditions are met, the terminal will initiate uplink information transmission based on the CG. This fixed association relationship is not flexible enough, does not support adjusting the transmission carrier due to changes in data volume or channel conditions, and is not suitable for multi-carrier or carrier group scenarios.

[0005] For multi-carrier or carrier group scenarios, determining the uplink and / or downlink carriers during SDT, RACH-less handover, LTM handover, and other processes is a problem that needs to be solved. Summary of the Invention

[0006] This application provides a wireless communication method, apparatus, and device that can solve the problem of determining uplink and / or downlink carriers during SDT, RACH-less handover, LTM handover, and other processes in multi-carrier or carrier group scenarios.

[0007] Firstly, a wireless communication method is provided, comprising:

[0008] The terminal acquires first information; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0009] The terminal determines a target uplink carrier based on the first information, and the terminal transmits first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by a terminal in an idle or deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or,

[0010] The terminal determines a target downlink carrier based on the first information, and the terminal receives first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information of data receiving data in an idle state or a deactivated state, or, the first uplink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access.

[0011] Secondly, another wireless communication method is provided, including:

[0012] The network-side device sends first information to the terminal; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0013] The network-side device receives first uplink information; wherein the first uplink information is transmitted based on a target uplink carrier, and the target uplink carrier is determined based on the first information; wherein the first uplink information is uplink information for data transmission by a terminal in an idle or deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or,

[0014] The network-side device sends first downlink information to the terminal; wherein the first downlink information is sent based on a target downlink carrier, and the target downlink carrier is determined based on the first information; wherein the first downlink information is downlink information for data received by the terminal in an idle state or a deactivated state, or the first uplink information is downlink information during LTM handover, or the first downlink information is downlink information during handover without random access.

[0015] Thirdly, a wireless communication device is provided, comprising: a processing module, a transmitting module, and a receiving module;

[0016] The processing module or the receiving module is used to acquire first information; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0017] The processing module is configured to determine a target uplink carrier based on the first information, and the transmitting module is configured to transmit first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by a terminal in an idle or deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or,

[0018] The processing module is used to determine a target downlink carrier based on the first information, and the receiving module is used to receive first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information of data received by a terminal in an idle state or a deactivated state, or, the first uplink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access.

[0019] Fourthly, another wireless communication device is provided, including: a transmitting module and a receiving module;

[0020] The sending module is used to send first information to the terminal; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0021] The receiving module is used to receive first uplink information; wherein the first uplink information is transmitted based on a target uplink carrier, and the target uplink carrier is determined based on the first information; wherein the first uplink information is uplink information of a terminal transmitting data in an idle state or a deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or,

[0022] The sending module is further configured to send first downlink information to the terminal; wherein the first downlink information is sent based on a target downlink carrier, and the target downlink carrier is determined based on the first information; wherein the first downlink information is downlink information of data received by the terminal in an idle state or a deactivated state, or the first uplink information is downlink information during LTM handover, or the first downlink information is downlink information during handover without random access.

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

[0024] In a sixth 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.

[0025] Seventhly, a terminal is provided, including a processor and a communication interface;

[0026] The processor or the communication interface is used to acquire first information; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0027] The processor is configured to determine a target uplink carrier based on the first information, and the communication interface is configured to transmit first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by a terminal in an idle or deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or,

[0028] The processor is configured to determine a target downlink carrier based on the first information, and the communication interface is configured to receive first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information of data received by a terminal in an idle state or a deactivated state, or, the first uplink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access.

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

[0030] Ninthly, a network-side device is provided, including a processor and a communication interface;

[0031] The communication interface is used to send first information to the terminal; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0032] The communication interface is further configured to receive first uplink information; wherein the first uplink information is transmitted based on a target uplink carrier, and the target uplink carrier is determined based on the first information; wherein the first uplink information is uplink information for data transmission by a terminal in an idle or deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or,

[0033] The communication interface is further configured to send first downlink information to the terminal; wherein the first downlink information is sent based on a target downlink carrier, and the target downlink carrier is determined based on the first information; wherein the first downlink information is downlink information for data received by the terminal in an idle state or a deactivated state, or the first uplink information is downlink information during LTM handover, or the first downlink information is downlink information during handover without random access.

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

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

[0036] 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 programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

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

[0038] In this embodiment, the terminal determines a target uplink carrier based on first information, and the terminal transmits first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by the terminal in an idle state or a deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or, the terminal determines a target downlink carrier based on the first information, and the terminal receives first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information for data reception by the terminal in an idle state or a deactivated state, or, the first uplink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access. Specifically, for processes such as SDT, RACH-less handover, and LTM handover, the target uplink carrier can be flexibly adjusted within the uplink carrier group or at least two uplink carriers, and / or the target downlink carrier can be flexibly adjusted within the downlink carrier group or at least two downlink carriers. While ensuring uplink and downlink transmission coverage, this helps to achieve better load balancing, reduce inter-carrier interference, and improve the performance of processes such as SDT, RACH-less handover, and LTM handover. Attached Figure Description

[0039] Figure 1 is a schematic diagram of a communication system architecture provided in an embodiment of this application.

[0040] Figure 2 is a schematic diagram of an LTM switching method provided in this application.

[0041] Figure 3 is a schematic flowchart of a wireless communication method provided according to an embodiment of this application.

[0042] Figure 4 is a schematic diagram of the association between the beam of a downlink carrier and the CG of an uplink carrier according to an embodiment of this application.

[0043] Figure 5 is an illustration of a method for determining the validity of CG resources according to an embodiment of this application.

[0044] Figure 6 is a schematic block diagram of a wireless communication device according to an embodiment of this application.

[0045] Figure 7 is a schematic block diagram of another wireless communication device provided according to an embodiment of this application.

[0046] Figure 8 is a schematic block diagram of a communication device provided according to an embodiment of this application.

[0047] Figure 9 is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application.

[0048] Figure 10 is a schematic block diagram of a network-side device provided according to an embodiment of this application. Detailed Implementation

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

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

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

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

[0053] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. Specifically, the wireless communication system includes a terminal 11 and a network-side device 12.

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

[0055] Among them, network-side equipment 12 may include access network equipment.

[0056] Alternatively, 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. The term "base station" 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), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0057] To better understand the technical solution of this application, the random access process related to this application is explained below.

[0058] In NR systems, specifically 5G NR, during the initial access phase, the User Equipment (UE) needs to obtain the access carrier frequency by searching for a synchronization block (SS / PBCH Block, SSB) to achieve downlink synchronization. Due to the wide spectrum range of NR, to reduce search complexity, the UE performs SSB searches at certain frequency intervals specified in the protocol; this frequency interval is called the Synchronization Raster. The UE detects the Synchronization Signal Reference Signal Received Power (SS-RSRP) at the corresponding frequency point according to the Synchronization Raster and selects any SSB whose SS-RSRP is higher than a threshold (rsrp-ThresholdSSB). By demodulating the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Physical Broadcast Channel (PBCH) signals in the selected SSB, the UE completes cell selection and synchronizes with the base station, after which random access is performed.

[0059] Random access procedures can be divided into contention-based random access procedures and contention-free random access procedures. In terms of process, random access procedures can be divided into four-step random access procedures (also known as Type-1 random access procedures) and two-step random access procedures (also known as Type-2 random access procedures).

[0060] Competition-based four-step random access channel (RACH)

[0061] The UE first sends message 1 (Msg1) to the network device, such as a random access preamble. After detecting the preamble, the network device sends message 2 (Msg2) to the UE, such as a Random Access Response (RAR) message. This message contains the identifier of the preamble detected by the network device (also known as the preamble number), such as the RACH preamble ID (RAPID), the uplink physical uplink shared channel (PUSCH) resource allocated to the UE for sending message 3 (Msg3) (indicated by uplink grant information), the Temporary Cell Radio Network Temporary Identity (TC-RNTI), and the timing advance. Advance (TA) commands, etc.; after receiving Msg2, if the UE confirms that at least one of the preamble numbers carried in Msg2 matches the preamble number it sent, it sends Msg3 containing contention resolution information according to the uplink resources indicated in the RAR; if the network-side device does not receive Msg3PUSCH, it can schedule the retransmission of Msg3PUSCH in the TC-RNTI scrambled Physical Downlink Control Channel (PDCCH). After receiving Msg3, the network-side device will send message 4 (Msg4) containing contention resolution information; upon receiving Msg4, the UE confirms that the resolution information is consistent with the one it sent in Msg3, thus completing the four-step random access.

[0062] In a contention-based random access procedure, different UEs randomly select a preamble for transmission. This means different UEs might select the same preamble to send at the same random access time, a situation known as UE preamble conflict. In this case, different UEs will receive the same RAR (Registered Access Record), and each UE will transmit the Msg3 PUSCH according to the scheduling information in the RAR's UL grant. The network-side device can only resolve one UE's PUSCH (containing contention resolution information) on a single Msg3 PUSCH scheduling resource. The network-side device will then include the contention resolution information received in Msg3 in Msg4. If the contention resolution information received by the UE in Msg4 matches the contention resolution information sent in the Msg3 PUSCH, the UE considers the contention resolution successful. If they do not match, the contention resolution is considered unsuccessful. If the contention resolution is unsuccessful, the UE will reselect a RACH transmission resource and transmit via the Physical Random Access Channel (PRACH) for the next random access attempt.

[0063] Two-step random access procedure (RACH)

[0064] The first step is for the UE to send message A (MsgA) to the network-side device. After receiving MsgA, the network-side device sends message B (MsgB) to the UE. If the UE does not receive MsgB within a certain time, it will increment a counter counting the number of times MsgA has been sent and resend MsgA. If the counter count reaches a certain threshold, the UE will switch from a two-step random access procedure to a four-step random access procedure.

[0065] MsgA comprises a MsgA preamble and a MsgA PUSCH. The preamble is transmitted on the random access opportunity (RO) used for 2-step RACH, and the PUSCH is transmitted on the MsgA PUSCH resources associated with the transmitted MsgA preamble and RO. The MsgA PUSCH resources are a set of PUSCH resources configured relative to each PRACH slot, including time-frequency resources and demodulation reference signal (DMRS) resources.

[0066] In addition, there are random access procedures associated with multiple SSBs. In cell edge areas or areas with limited coverage, the uplink signal coverage performance of the terminal is inferior to the downlink signal coverage; that is, the coverage performance of Msg1 and Msg3 is inferior to that of Msg2 and Msg4. Furthermore, the difference in uplink and downlink coverage performance is even more pronounced in the high-frequency band FR2. To improve uplink signal coverage performance, a method of repeated uplink signal transmission is considered, and a repeated transmission mechanism for Msg3 is introduced to improve Msg3 coverage performance, but this is still limited to a single Msg3 signal.

[0067] To better understand the technical solution of this application, the following describes the Small Data Transmission (SDT) related to this application.

[0068] The characteristic of efficient small data transmission is that for non-connected UEs, it avoids excessive signaling overhead caused by Radio Resource Control (RRC) state transitions and RRC connection establishment processes, and completes the purpose of small data transmission through a very simple signaling process.

[0069] NR proposes a small data transmission scheme for inactive terminals, allowing the terminal to maintain its RRC inactive state (RRC_INACTIVE) while transmitting data or signaling (i.e., not transitioning to the RRC connected state). SDT is enabled on the radio bearer basis and is only initiated by the UE when the uplink data volume is less than the configured uplink data volume, the downlink reference signal received power (RSRP) is higher than the configured threshold, and there are available SDT resources.

[0070] Small data transfer supports two methods: via RACH or via Type 1 CG resources. For RACH-based small data transfer, the system message provides the relevant configuration for the small data transfer, which can be configured with two-step random access resources or four-step random access resources. Non-contention-based small data transfer is not supported. For configured grant (CG)-based small data transfer, the CG resource is configured for SDT when released via RRC, and the CG resource is associated with one or more SSBs.

[0071] To better understand the technical solution of this application, the LTM related to this application is explained below.

[0072] LTM refers to the process where the base station receives Layer 1 (L1) measurement reports from the terminal. Based on the received L1 measurement results, the base station can send a Cell Switch Command signaling to the terminal via the Media Access Control Control Element (MAC CE) to change the terminal's serving cell, as shown in Figure 2. The base station pre-sends multiple LTM candidate configurations to the terminal via RRC signaling. When LTM is triggered, the sent Cell Switch Command indicates the LTM candidate configuration corresponding to the target cell to be accessed. The terminal then applies the corresponding LTM target configuration to complete the serving cell change. The network-side equipment sending a MAC CE to trigger cell switching based on L1 measurement results can respond to rapid channel changes and trigger the handover promptly.

[0073] During LTM, advance uplink and downlink synchronization for candidate cells is supported, as shown in steps 4a and 4b of Figure 2, thus enabling RACH-less LTM cell switching. Currently, two schemes are supported for obtaining the TA values ​​of LTM candidate cells in advance: timing advance (TA) acquisition and UE-based TA measurement, to support RACH-less LTM cell switching. Performing advance uplink and downlink synchronization for candidate cells to achieve RACH-less LTM cell switching can effectively reduce data interruptions during handover.

[0074] LTM supports subsequent LTM (Subsequent LTM). Therefore, the terminal does not release the LTM candidate configuration after each LTM Cell Switch, allowing the terminal to continue performing subsequent Cell Switches after mobility execution without RRC reconfiguration or reset. Supporting Subsequent LTM can effectively reduce signaling overhead.

[0075] To better understand the technical solution of this application, the following explains the RACH-less switching related to this application.

[0076] To save on signaling overhead during handover, RACH-less handover is supported.

[0077] The main steps of RACH-less handover are as follows:

[0078] When the terminal receives the RACH-less handover command, the RRC reconfiguration message that triggers the RACH-less handover includes a timing adjustment indication and a configured grant or beam indication for accessing the target cell (for listening to the PDCCH related SSB and Transmission Configuration Indicator (TCI) information for initial uplink transmission).

[0079] The UE performs downlink synchronization and uplink synchronization. Uplink synchronization can be achieved by applying the timing adjustment to synchronize to the target cell. If a pre-allocated grant is configured, an RRC Reconfiguration Complete message is sent using the configured uplink configuration grant. If no pre-allocated configured grant is available, the terminal receives the uplink grant through monitoring the PDCCH according to the beam indication.

[0080] To better understand the technical solution of this application, the problems solved by this application are explained below.

[0081] Random access procedures can be divided into single-carrier-based random access and multi-carrier-based random access. Multi-carrier-based random access can be further divided into scenarios with defined anchor carriers and scenarios without defined anchor carriers. Anchor carriers can also be referred to as anchor cells.

[0082] In scenarios where an anchor carrier is defined, during multi-carrier-based random access, the terminal can initiate random access only from the anchor cell or only from a non-anchor cell. In scenarios where the terminal can only access from the anchor cell, a large number of users accessing the network can lead to high load on the anchor cell, impacting access performance. In scenarios where the terminal initiates random access from a non-anchor cell, the terminal receives system messages and related configurations from other non-anchor cells at the anchor cell, selects a non-anchor cell according to certain rules, and completes message transmission and reception during the random access process within the selected non-anchor cell. Supplementary uplinks (SULs) can also be supported for both anchor cells and non-anchor cells; uplink messages during the random access process can be sent via a normal uplink or a supplementary uplink. Overall, once the terminal selects a cell or carrier, the random access process is completed on the selected uplink and downlink carriers, which is relatively inflexible, as it does not support adjusting the carriers during the random access process due to changes in load, interference, etc.

[0083] In multi-carrier scenarios without a configured anchor carrier, this is equivalent to having multiple independent single-carrier-based random access methods. The terminal selects a carrier based on certain rules, and the random access process is the same as that of single-carrier-based random access. However, this approach has several drawbacks. First, compared to providing system messages for multiple carriers based on an anchor carrier, this method involves the network-side device sending synchronization signals and system messages on each downlink carrier supporting random access, increasing carrier activity time and leading to higher network power consumption. Second, once the terminal selects a downlink carrier for random access, the random access process is completed on both the selected uplink and downlink carriers. Again, this method is relatively inflexible and does not support adjusting the carriers used in the random access process due to changes in load, interference, etc.

[0084] For RACH-based SDT and LTM, similarly, after the terminal selects the downlink carrier for random access, the random access process is completed on the selected uplink and downlink carriers. This method is relatively inflexible and does not support adjusting the carrier during the random access process due to changes in load, interference, etc.

[0085] For CG-based SDT and RACH-less handover, when the uplink carrier associated with the downlink carrier has a CG configuration and certain conditions are met, the terminal will initiate uplink information transmission based on the CG. However, this fixed association is not flexible enough and does not support adjusting the transmission carrier due to changes in data volume or channel conditions.

[0086] In multi-carrier or carrier group scenarios, how to simultaneously balance flexibility, coverage performance, and transmission performance during SDT, RACH-less handover, LTM handover, and other processes is an urgent problem to be solved.

[0087] This application provides a carrier determination scheme that allows for flexible adjustment of the target uplink carrier within an uplink carrier group or at least two uplink carriers during processes such as SDT, RACH-less handover, and LTM handover. It also allows for flexible adjustment of the target downlink carrier within a downlink carrier group or at least two downlink carriers. This ensures uplink and downlink transmission coverage while facilitating better load balancing, reducing inter-carrier interference, and improving the performance of processes such as SDT, RACH-less handover, and LTM handover.

[0088] The wireless communication method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0089] Figure 3 is a schematic flowchart of a wireless communication method 200 according to an embodiment of this application. As shown in Figure 3, the wireless communication method 200 may include at least some of the following:

[0090] S210, the network-side device sends first information to the terminal; wherein, the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0091] S220, the terminal obtains first information; wherein, the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0092] S230, the terminal determines a target uplink carrier based on the first information, and the terminal transmits first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by a terminal in an idle state or a deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or, the terminal determines a target downlink carrier based on the first information, and the terminal receives first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information for data reception by a terminal in an idle state or a deactivated state, or, the first downlink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access;

[0093] S240, the network-side device receives the first uplink information; and / or, the network-side device sends the first downlink information to the terminal.

[0094] It should be understood that Figure 3 illustrates the steps or operations of the wireless communication method 200, but these steps or operations are merely examples, and other operations or variations of the operations shown in Figure 3 may also be performed in this application.

[0095] The data transmission in the idle state (RRC idle state) or deactivated state (RRC deactivated state) described in the embodiments of this application can be small data transmission (SDT) or other data transmission, and the embodiments of this application are not limited to this.

[0096] For example, the uplink information for data transmission by a terminal in an idle or deactivated state can be an SDT or a message carrying an SDT, such as the first uplink information being an SDT or a message carrying an SDT.

[0097] For example, the downlink information for data received by a terminal in an idle or deactivated state can be an SDT or a message carrying an SDT, such as the first downlink information being an SDT or a message carrying an SDT.

[0098] It should be noted that the small data transmission in the embodiments of this application can also be replaced with data transmission.

[0099] It should be noted that an inactive UE can also be called a third-state UE.

[0100] In the embodiments of this application, for processes such as SDT, RACH-less handover, and LTM handover, the target uplink carrier can be flexibly adjusted within the uplink carrier group or at least two uplink carriers, and / or the target downlink carrier can be flexibly adjusted within the downlink carrier group or at least two downlink carriers. While ensuring uplink and downlink transmission coverage, this helps to achieve better load balancing, reduce inter-carrier interference, and improve the performance of processes such as SDT, RACH-less handover, and LTM handover.

[0101] In the embodiments of this application, during Small Data Transmission (SDT), the downlink or uplink carrier for transmission is flexibly selected from at least two available uplink carriers or at least two available downlink carriers. The available uplink and downlink carriers can be flexibly paired without requiring a constrained correspondence. This allows for adjustments to the carriers used for transmitting and / or receiving SDT due to changes in load, interference, data volume, channel conditions, etc.

[0102] In this embodiment, during RACH-less handover, the downlink or uplink carrier to be transmitted is flexibly selected from at least two available uplink carriers or at least two available downlink carriers. The available uplink and downlink carriers can be flexibly paired without requiring a constrained correspondence. This allows for adjustment of the transmitted and / or received carriers during RACH-less handover due to changes in load, interference, data volume, channel conditions, etc.

[0103] In this embodiment, during LTM handover, a downlink or uplink carrier is flexibly selected from at least two available uplink carriers or at least two available downlink carriers for transmission. The available uplink and downlink carriers can be flexibly paired without requiring a constrained correspondence. This allows for adjustments to the transmitted and / or received carriers during LTM handover due to changes in load, interference, data volume, channel conditions, etc.

[0104] In the embodiments of this application, "first uplink information" may also be referred to as or replaced by "first uplink message", and "first downlink information" may also be referred to as or replaced by "first downlink message". This application does not limit this.

[0105] Optionally, in S220, the terminal acquires the first information, including:

[0106] The terminal receives the first information from the network-side device; or,

[0107] The terminal obtains the first information based on the information agreed upon in the protocol; or,

[0108] The terminal obtains the first information based on pre-configured parameters.

[0109] The multiple carriers described in this application embodiment can correspond to different cells. For example, each carrier corresponds to one cell, and multiple carriers correspond to multiple cells; or multiple carriers can correspond to the same cell. In this scenario, the carrier can also be called a frequency domain unit, frequency resource, or other names. For example, a cell contains multiple frequency domain units (such as discontinuous frequency domain units), and the frequency domain units can correspond to the carriers described in this application embodiment.

[0110] The cell described in this application embodiment can be equivalent to a carrier, for example, a cell contains one carrier; or, it can be equivalent to a carrier group, for example, a cell contains a group of carriers, each carrier may have the same or different Physical Cell Identifier (PCI); or, it can be equivalent to multiple frequency domain units, for example, a cell contains multiple frequency domain units that are not contiguous in the frequency domain.

[0111] The SSB described in this application embodiment can also be referred to as any module that includes at least one of a synchronization signal, a broadcast signal, a broadcast channel (PBCH), other system message downlink broadcast channels, and their control channels. The SSB can also be other reference signals, such as Channel State Information Reference Signal (CSI-RS), Tracking Reference Signal (TRS), Positioning Reference Signal (PRS), Phase Tracking Reference Signal (PT-RS), Demodulation Reference Signal (DMRS), etc.

[0112] The SDT described in the embodiments of this application may include random access-based SDT (RA-based SDT) and CG-based SDT (CG-based SDT).

[0113] For example, embodiments of this application can perform SDT based on contention-based random access (CBRA) or contention-free random access (CFRA). Optionally, SDT can be performed based on four-step random access (4-step RACH), such as SDT based on contention-based four-step random access (CBRA with 4-step RACH) or SDT based on contention-free four-step random access (CFRA with 4-step RACH). Optionally, SDT can be performed based on two-step random access (2-step RACH), such as SDT based on contention-based two-step random access (CBRA with 2-step RACH) or SDT based on contention-free two-step random access (CFRA with 2-step RACH).

[0114] In some embodiments, a downlink carrier group is associated with one or more uplink carrier groups; and / or, an uplink carrier group is associated with one or more downlink carrier groups.

[0115] In this embodiment, a downlink carrier group is associated with one or more uplink carrier groups, so that the associated one or more uplink carrier groups can be determined based on a downlink carrier group.

[0116] In this embodiment, an uplink carrier group is associated with one or more downlink carrier groups, so that the associated one or more downlink carrier groups can be determined based on an uplink carrier group.

[0117] In some embodiments, the first information includes the association between uplink carrier groups and downlink carrier groups. Thus, the terminal can obtain the association between uplink carrier groups and downlink carrier groups from the network-side device, or the terminal can obtain the association between uplink carrier groups and downlink carrier groups from protocol-defined information.

[0118] In some embodiments, the association between the uplink carrier group and the downlink carrier group can also be agreed upon by the protocol.

[0119] In some embodiments, the association between uplink carrier groups and downlink carrier groups is determined based on at least one of the following: frequency band, frequency band combination, spectrum range, and bandwidth part (BWP).

[0120] In this embodiment, the terminal can determine the association between the uplink carrier group and the downlink carrier group based on at least one of the following: frequency band, frequency band combination, spectrum range, and BWP.

[0121] For example, when defining different bands, the protocol indirectly determines the association between the corresponding uplink carrier group and downlink carrier group.

[0122] In this embodiment, during SDT, RACH-less handover, LTM handover, etc., the network configures multiple available uplink / downlink carriers for sending / receiving different messages during random access. Considering hardware implementation, signal multiplexing, network load, transmission characteristics, etc., the determination of the uplink / downlink carrier can be divided into two steps:

[0123] Carrier group determination and indication;

[0124] Carrier determination and indication within a carrier group.

[0125] When all carriers belong to the same carrier group, the determination and indication of the carrier group can be an optional step.

[0126] In some embodiments, the terminal determines the target uplink carrier based on the first information, including:

[0127] The terminal determines a target uplink carrier group from the at least one uplink carrier group, and the terminal determines the target uplink carrier from the target uplink carrier group; or,

[0128] The terminal determines the target uplink carrier from the at least two uplink carriers.

[0129] In this embodiment, the terminal determines a target uplink carrier group from at least one uplink carrier group, and the terminal determines a target uplink carrier from the target uplink carrier group, so that the terminal can transmit first uplink information based on the target uplink carrier. Alternatively, the terminal determines a target uplink carrier from at least two uplink carriers, so that the terminal can transmit first uplink information based on the target uplink carrier.

[0130] In some embodiments, the terminal determines the target downlink carrier based on the first information, including:

[0131] The terminal determines a target downlink carrier group from the at least one downlink carrier group, and the terminal determines the target downlink carrier from the target downlink carrier group; or,

[0132] The terminal determines the target downlink carrier from the at least two downlink carriers.

[0133] In this embodiment, the terminal determines a target downlink carrier group from at least one downlink carrier group, and the terminal determines a target downlink carrier from the target downlink carrier group, so that the terminal can transmit first downlink information based on the target downlink carrier. Alternatively, the terminal determines a target downlink carrier from at least two downlink carriers, so that the terminal can transmit first downlink information based on the target downlink carrier.

[0134] In the embodiments of this application, considering factors such as carrier purpose, signal multiplexing, and signal differences between carriers, when configuring uplink and / or downlink carriers for processes such as SDT, RACH-less handover, and LTM handover, network-side devices can configure one or more uplink carrier groups and / or downlink carrier groups. Different carrier groups can have different purposes or characteristics, or carry different information.

[0135] Optionally, the network-side device provides carrier configuration via system messages or RRC signaling, wherein the carrier configuration includes one or more uplink carrier groups and / or one or more downlink carrier groups, wherein the uplink carrier group includes one or more uplink carriers and the downlink carrier group includes one or more downlink carriers; further, the network-side device indicates the association between the uplink carrier group and the downlink carrier group.

[0136] In one possible implementation, the network-side device is configured with one or more uplink carrier groups and / or downlink carrier groups for the Small Data Transmission (SDT) process. Uplink Small Data Transmission (SDT) is transmitted only on uplink carriers within the uplink carrier group used for the Small Data Transmission (SDT) process, and downlink Small Data Transmission (SDT) is received only on downlink carriers within the downlink carrier group used for the Small Data Transmission (SDT) process.

[0137] In one possible implementation, the network-side device configures one or more uplink carrier groups and / or downlink carrier groups for the RACH-less handover process. Uplink information during the RACH-less handover process is only transmitted on uplink carriers within the uplink carrier group used for the RACH-less handover process, and downlink information during the RACH-less handover process is only received on downlink carriers within the downlink carrier group used for the RACH-less handover process.

[0138] In one possible implementation, the network-side device is configured with one or more uplink carrier groups and / or downlink carrier groups for the LTM handover process. Uplink information during the LTM handover process is only transmitted on the uplink carriers within the uplink carrier group used for the LTM handover process, and downlink information during the RACH-less handover process is only received on the downlink carriers within the downlink carrier group used for the LTM handover process.

[0139] In one possible implementation, the network-side device is configured with an uplink carrier group for non-PRACH, which contains one or more carriers. These carriers are used to transmit uplink signals other than PRACH during random access or before RRC establishment or RRC recovery, such as Msg3, Msg5 (uplink messages after Msg4), RRC setup request messages, RRC resume request messages, RRC reestablishment request messages, RRC setup complete messages, RRC resume complete messages, and RRC reestablishment complete messages.

[0140] In one possible implementation, for one or more messages (such as Msg1~Msg5, MsgA, MsgB, etc.) during the random access process, the network-side device is configured with uplink carrier groups for transmission, each carrier group containing one or more uplink carriers; and downlink carrier groups for reception, each carrier group containing one or more downlink carriers; optionally, the carrier groups / carriers configured for different messages can be the same or different.

[0141] In one possible implementation, the network side configures one or more synchronization reference downlink carrier groups, which contain one or more carriers, and downlink synchronization between the carriers can be multiplexed. For example, the carriers within the carrier group share a set of radio frequency devices on the base station side. Optionally, within the downlink carrier group, SSB can be transmitted on every carrier, or only on one or a few carriers, to reduce SSB overhead.

[0142] In one possible implementation, the network-side device configures downlink carrier groups with associated SSBs. Each carrier group contains two or more carriers, and the SSBs within the carrier group are associated. For example, the number of SSBs and the SSB beam pointing can be the same across different carriers. Alternatively, the number of SSBs across different carriers can be different, but the SSB beams on different carriers can be associated. For instance, one SSB on a carrier with fewer SSBs can be associated with multiple SSBs on a carrier with more SSBs.

[0143] In one possible implementation, the downlink carrier group configured by the network-side device has the same SSB beam on different carriers. Optionally, in this case, the network-side device may transmit the SSB only on a certain carrier in the carrier group.

[0144] In some embodiments, for SDT, the first information includes, but is not limited to, at least one of the following:

[0145] The preamble's transmit carrier or carrier group;

[0146] Msg 3 (carrying SDT) is the transmit carrier or carrier group;

[0147] Msg A corresponds to the PUSCH (carrying SDT) transmission carrier or carrier group;

[0148] The association between the preamble's transmit carrier or transmit resource and the transmit carrier of Msg 3 (carrying SDT) or the transmit carrier of the PUSCH (carrying SDT) corresponding to Msg A.

[0149] Optionally, for different Msg 3 (carrying SDT) transmit carriers or Msg A corresponding to PUSCH (carrying SDT) transmit carriers, an independent data volume range or data volume threshold can be configured.

[0150] For example, the network-side device configures CG resources for the terminal on multiple carrier groups or multiple carriers, and configures carrier group or carrier selection conditions for the terminal for CG. In one possible implementation, the network-side device configures CG resources for the terminal on multiple carriers, with different data volume thresholds configured for different carriers, and the terminal selects the corresponding carrier based on the size of the transmitted data.

[0151] For example, for an uplink carrier of CG resources, its corresponding downlink carrier may or may not have an SSB transmission. Correspondingly, the association between CG resources and SSBs configured by the network-side device can be based on the same carrier or different carriers. In one possible implementation, the network-side device configures CG resources for the terminal on multiple carriers. If the downlink carrier corresponding to the uplink carrier selected by the terminal does not contain an SSB, the terminal measures the SSBs on other downlink carriers associated with that downlink carrier and determines the CG resources based on the uplink / downlink carrier associations configured by the network-side device. For instance, the network-side device determines the CG resources transmitted on the first uplink carrier based on the SSBs on the first downlink carrier and the association between the SSBs on the first downlink carrier and the CGs on the first uplink carrier configured by the network-side device.

[0152] Figure 4 illustrates a multi-carrier CG-SDT method. The network-side equipment configures CG resources for the terminal on the first uplink carrier and the second uplink carrier for small data transmission (SDT). Both the first uplink carrier and the second uplink carrier are associated with the first downlink carrier. That is, the network-side equipment configures the mapping between the SSB of the first downlink carrier and the CG resources of the first uplink carrier or the second uplink carrier. Based on the SSB measurement of the first downlink carrier (e.g., selecting the SSB with the best channel quality), the terminal selects the optimal CG resource on the first uplink carrier or the second uplink carrier to transmit uplink small data.

[0153] For example, there is a mapping between the SSB of the downlink carrier and the CG resources of the uplink carrier, and a mapping between the SSB of the downlink carrier group and the CG resources of the uplink carrier group.

[0154] For example, the downlink carrier and the uplink carrier are located in the same frequency band or different frequency bands, or the downlink carrier and the uplink carrier belong to the same cell or different cells; or, the downlink carrier group and the uplink carrier group are located in the same frequency band or different frequency bands, or the downlink carrier group and the uplink carrier group belong to the same cell or different cells.

[0155] For example, different downlink carriers or different uplink carriers may be located in the same frequency band or different frequency bands, or different downlink carriers or different uplink carriers may belong to the same cell or different cells; or different downlink carrier groups or different uplink carrier groups may be located in the same frequency band or different frequency bands, or different downlink carrier groups or different uplink carrier groups may belong to the same cell or different cells.

[0156] For example, the terminal sends a preamble on carrier 1 and an RRC reconfiguration complete message on carrier 2. Carrier 1 and carrier 2 are located in the same frequency band or different frequency bands, or carrier 1 and carrier 2 belong to the same cell or different cells.

[0157] For example, the terminal sends a preamble in carrier group 1 and an RRC reconfiguration complete message in carrier group 2. Carrier group 1 and carrier group 2 are located in the same frequency band or different frequency bands, or carrier group 1 and carrier group 2 belong to the same cell or different cells.

[0158] For example, two or more uplink carriers or uplink carrier groups are configured with CG resources, and different uplink carriers or uplink carrier groups are configured with different SDT data volume ranges or SDT data volume thresholds.

[0159] For example, the retransmission carrier or carrier group of the SDT on the CG resource may be the same as or different from the initial carrier or carrier group.

[0160] For example, the retransmission carrier or carrier group of the SDT on the CG resource is configured by the network-side device, or the retransmission carrier or carrier group of the SDT on the CG resource is determined and indicated by the terminal.

[0161] For example, the carrier or carrier group of the subsequent transmission of the SDT on the CG resource may be the same as or different from the carrier or carrier group of the SDT on the CG resource.

[0162] In some embodiments, for the LTM handover process, the terminal may be triggered to perform uplink synchronization, PRACH transmission, or PUSCH transmission in advance on the target uplink carrier group and / or the target uplink carrier based on the first information. For the LTM handover process, network feedback messages may be received on the target downlink carrier group and / or the target downlink carrier based on the first information.

[0163] In some embodiments, for an LTM handover procedure, the LTM handover command may include at least one downlink carrier group and / or at least two downlink carriers for message reception during the random access procedure, and / or, the LTM handover command may include at least one uplink carrier group and / or at least two uplink carriers for message transmission during the random access procedure. In other words, the LTM handover command may include first information.

[0164] In some embodiments, for the RACH-less handover process, the network-side device configures at least one uplink carrier group and / or at least two uplink carriers for uplink PUSCH transmission, repeated transmission, or retransmission during the RACH-less handover. Optionally, the uplink PUSCH may include, but is not limited to, at least one of the following: DG PUSCH, CG PUSCH transmission.

[0165] In some embodiments, for the RACH-less handover process, two or more uplink carriers or carrier groups are configured with authorization settings, and different carriers or carrier groups are configured with different data volume ranges or data volume thresholds.

[0166] For example, the retransmission carrier or carrier group configured for authorized transmission may be the same as or different from the initial transmission carrier or carrier group.

[0167] In some embodiments, the first information includes a carrier indication or a beam indication, which may be used to indicate one or more carriers or a group of carriers; or, the first information includes one or more groups: carrier indication and beam indication.

[0168] In some embodiments, the target uplink carrier group is determined based on at least one of the following:

[0169] The first uplink information includes the available uplink carrier group, the terminal's identification information, the identification information of the terminal group to which the terminal belongs, the paging message sent by the network-side device, the uplink carrier group associated with the downlink carrier group selected by the terminal, the average signal quality of all downlink carriers in the downlink carrier group selected by the terminal, the highest signal quality of all downlink carriers in the downlink carrier group selected by the terminal, the amount of uplink data to be transmitted by the terminal, the amount of uplink buffered data by the terminal, the uplink quality of service (QoS) of the terminal, and the uplink transmission latency of the terminal.

[0170] In this embodiment, the terminal can flexibly determine the target uplink carrier group.

[0171] Optionally, the uplink carrier group available for the first uplink information can be one or more uplink carrier groups.

[0172] Optionally, the terminal's identification information includes the terminal's identifier or a portion of the terminal's identifier. For example, the terminal's identifier (UE ID) can be any one of the following: Cell-Radio Network Temporary Identifier (C-RNTI), Temporary Mobile Subscriber Identity (TMSI), or International Mobile Subscriber Identity (IMSI).

[0173] Optionally, the association between the terminal's identification information and the uplink carrier group can be agreed upon by a protocol, or the association can be configured by the network-side equipment. For example, the network-side equipment can configure two uplink carrier groups, with terminals mod UE ID = 0 associated with the first uplink carrier group and terminals mod UE ID = 1 associated with the second uplink carrier group, where mod represents the modulo operation.

[0174] Optionally, the association between the identification information of the terminal group to which the terminal belongs and the uplink carrier group can be agreed upon by the protocol, or the association between the identification information of the terminal group to which the terminal belongs and the uplink carrier group can be configured by the network-side equipment.

[0175] Optionally, the network-side device may also directly indicate the target uplink carrier group and / or the target uplink carrier via paging messages, and / or, the network-side device may also directly indicate the target downlink carrier group and / or the target downlink carrier via paging messages. Alternatively, the network-side device may also directly indicate the uplink carrier and / or the downlink carrier used for random access via paging messages, or the network-side device may also directly indicate the carrier used for random access via paging messages (without distinguishing between uplink and downlink carriers).

[0176] The signal quality described in the embodiments of this application can also be replaced or equivalent to the function or operation used to determine the signal quality.

[0177] The signal quality described in the embodiments of this application may include, but is not limited to, at least one of the following:

[0178] Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), and Signal to Interference plus Noise Ratio (SINR).

[0179] In some implementations, when the network-side equipment is configured with at least one uplink carrier group, the terminal can select the target uplink carrier group in one of the following ways:

[0180] The network-side equipment configures the association between uplink carrier groups and downlink carrier groups, and the terminal can determine the uplink carrier group based on the selected downlink carrier group.

[0181] When a downlink carrier group configured by the network-side device is associated with two or more uplink carrier groups, the uplink carrier group is determined based on the average RSRP of the downlink carrier group or the highest RSRP within the downlink carrier group. For example, if the RSRP is lower than the threshold configured by the network-side device, the first uplink carrier group is selected; if the RSRP is higher than the threshold configured by the network-side device, the second uplink carrier group is selected.

[0182] When the downlink carrier group configured by the network-side equipment is associated with two or more uplink carrier groups, the uplink carrier group is determined based on factors such as the amount of uplink data to be transmitted by the terminal, the amount of uplink buffered data by the terminal, uplink QoS, or uplink latency. For example, if the amount of uplink data to be transmitted by the terminal is lower than the threshold configured by the network, the first uplink carrier group is selected; if the amount of uplink data to be transmitted by the terminal is higher than the first threshold, the second uplink carrier group is selected.

[0183] In some embodiments, the target downlink carrier group is determined based on at least one of the following:

[0184] The first downlink information includes the available downlink carrier group, the terminal identification information, the terminal group identification information to which the terminal belongs, the paging message sent by the network-side device, the downlink carrier group containing the downlink carrier with the highest measured signal quality in the at least one downlink carrier group, and the downlink carrier group with the highest average signal quality among all downlink carriers in the at least one downlink carrier group.

[0185] In this embodiment, the terminal can flexibly determine the target downlink carrier group.

[0186] Optionally, the downlink carrier group available for the first downlink information can be one or more downlink carrier groups.

[0187] For example, the target downlink carrier group can be the carrier group containing the carrier corresponding to the highest RSRP, or the target downlink carrier group can be the carrier group containing the carrier corresponding to the highest RSRQ, or the target downlink carrier group can be the carrier group containing the carrier corresponding to the highest SINR, or the target downlink carrier group can be the carrier group containing the carrier corresponding to the function or operation used to determine the highest RSRP, or the target downlink carrier group can be the carrier group containing the carrier corresponding to the function or operation used to determine the highest RSRQ, or the target downlink carrier group can be the carrier group containing the carrier corresponding to the function or operation used to determine the highest SINR.

[0188] For example, the target downlink carrier group can be the carrier group with the highest average RSRP of all downlink carriers, or the target downlink carrier group can be the carrier group with the highest average RSRQ of all downlink carriers, or the target downlink carrier group can be the carrier group with the highest average SINR of all downlink carriers, or the target downlink carrier group can be the carrier group containing the carrier corresponding to the function or operation used to determine the average RSRP, or the target downlink carrier group can be the carrier group containing the carrier corresponding to the function or operation used to determine the average RSRQ, or the target downlink carrier group can be the carrier group containing the carrier corresponding to the function or operation used to determine the average SINR.

[0189] In some implementations, when the network-side equipment is configured with at least one downlink carrier group, the terminal can select the target downlink carrier group in one of the following ways:

[0190] Based on the highest RSRP (or highest RSRQ, highest SINR) within a downlink carrier group, each downlink carrier group measures its SSBs, and the downlink carrier group containing the downlink carrier with the highest RSRP is selected. For example, RSRP (using RSRP as an example, it could also be RSRQ or SINR) measurement is based on one or more SSBs within a downlink carrier, and the highest RSRP corresponds to the RSRP of the SSB with the highest measurement result within the downlink carrier. Alternatively, RSRP measurement is based on one or more SSBs within a downlink carrier, and the highest RSRP corresponds to the RSRP of the average measurement result of the multiple SSBs within the downlink carrier.

[0191] Based on the average RSRP within the downlink carrier group, the SSB of each downlink carrier group is measured separately, and the downlink carrier group with the highest average RSRP is selected.

[0192] The network-side equipment is configured with a threshold. The SSB of each downlink carrier group is measured separately. For downlink carrier groups that are higher than the threshold, the downlink carrier group with the highest RSRP is selected, or the downlink carrier group with the highest average RSRP is selected.

[0193] Network-side equipment is configured with a threshold, and the SSB of each downlink carrier group is measured separately. Downlink carrier groups with values ​​above the threshold are randomly selected.

[0194] For example, in some scenarios, during the determination / measurement of the downlink carrier group, the terminal only measures one or some of the downlink carriers within the downlink carrier group. For instance, if the downlink carriers within the downlink carrier group belong to the same band (intra-band scenario), the terminal only measures one downlink carrier within the downlink carrier group and determines the RSRP based on the SSB measurement on that carrier.

[0195] It should be noted that determining the downlink carrier RSRP based on the RSRP corresponding to the highest SSB, or based on the average measurement results of multiple SSBs, is also applicable to the other methods described below, which will not be elaborated further.

[0196] In some embodiments, the downlink carriers within each downlink carrier group of the at least one downlink carrier group satisfy at least one of the following conditions:

[0197] Some or all downlink carriers correspond to the same SSB index;

[0198] There is a correlation between the SSB indices corresponding to some or all downlink carriers;

[0199] The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB.

[0200] An SSB index corresponding to a downlink carrier is associated with one or more ROs corresponding to uplink carriers.

[0201] An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices;

[0202] An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers;

[0203] A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers.

[0204] In this embodiment, in a downlink carrier group, some or all downlink carriers correspond to the same SSB index, so that the SSB indices of some or all downlink carriers in the downlink carrier group can be reused, thereby improving the performance of some or all downlink carriers in the downlink carrier group. For example, the SSB index corresponding to the downlink carrier that has not transmitted an SSB can reuse the SSB index corresponding to the downlink carrier that has transmitted an SSB.

[0205] In this embodiment, in a downlink carrier group, there is an association between some or all of the SSB indices corresponding to the downlink carriers, so that the SSB index corresponding to another downlink carrier can be determined based on the SSB index corresponding to one downlink carrier and the association between the SSB indices corresponding to the downlink carriers.

[0206] In this embodiment, in a downlink carrier group, the SSB index corresponding to a downlink carrier is associated with one or more ROs corresponding to uplink carriers, or the RO corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers, thereby improving coverage performance and random access performance.

[0207] In this embodiment, in a downlink carrier group, the SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers, or the random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers, thereby improving random access performance.

[0208] In some embodiments, the downlink carrier group in the at least one downlink carrier group satisfies at least one of the following conditions:

[0209] Some or all downlink carrier groups correspond to the same SSB index;

[0210] There is a correlation between the SSB indices corresponding to some or all downlink carrier groups;

[0211] An SSB index corresponding to a downlink carrier group is associated with one or more ROs corresponding to uplink carrier groups.

[0212] An RO corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups.

[0213] An SSB index corresponding to a downlink carrier group is associated with one or more random access preambles corresponding to uplink carrier groups.

[0214] A random access preamble corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups.

[0215] In this embodiment, in at least one downlink carrier group, some or all downlink carrier groups correspond to the same SSB index, so that the SSB indexes of some or all downlink carrier groups can be reused, thereby improving the performance of some or all downlink carrier groups. For example, the SSB index corresponding to the downlink carrier group that has not transmitted an SSB can reuse the SSB index corresponding to the downlink carrier group that has transmitted an SSB.

[0216] In this embodiment, in at least one downlink carrier group, there is an association between some or all of the SSB indices corresponding to the downlink carrier groups, so that the SSB index corresponding to another downlink carrier group can be determined based on the SSB index corresponding to one downlink carrier group and the association between the SSB indices corresponding to the downlink carrier groups.

[0217] In this embodiment, in at least one downlink carrier group, the SSB index corresponding to a downlink carrier group is associated with one or more ROs corresponding to uplink carrier groups, or the RO corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups, thereby improving coverage performance and random access performance.

[0218] In this embodiment, in at least one downlink carrier group, the SSB index corresponding to a downlink carrier group is associated with one or more random access preambles corresponding to uplink carrier groups, or the random access preamble corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups, thereby improving random access performance.

[0219] In some embodiments, the downlink carriers of the at least two downlink carriers satisfy at least one of the following conditions:

[0220] Some or all downlink carriers correspond to the same SSB index;

[0221] There is a correlation between the SSB indices corresponding to some or all downlink carriers;

[0222] The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB.

[0223] An SSB index corresponding to a downlink carrier is associated with one or more ROs corresponding to uplink carriers.

[0224] An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices;

[0225] An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers;

[0226] A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers.

[0227] In this embodiment, some or all of the downlink carriers in at least two downlink carriers correspond to the same SSB index, so that the SSB indexes of some or all of the downlink carriers in at least two downlink carriers can be reused, which improves the performance of some or all of the downlink carriers in the downlink carrier group. For example, the SSB index corresponding to the downlink carrier that has not transmitted an SSB can reuse the SSB index corresponding to the downlink carrier that has transmitted an SSB.

[0228] In this embodiment, among at least two downlink carriers, there is an association between some or all of the SSB indices corresponding to the downlink carriers, so that the SSB index corresponding to another downlink carrier can be determined based on the SSB index corresponding to one downlink carrier and the association between the SSB indices corresponding to the downlink carriers.

[0229] In this embodiment, among at least two downlink carriers, the SSB index corresponding to one downlink carrier is associated with one or more ROs corresponding to uplink carriers, or the RO corresponding to one uplink carrier is associated with one or more SSB indices corresponding to downlink carriers, thereby improving coverage performance and random access performance.

[0230] In this embodiment, among at least two downlink carriers, the SSB index corresponding to one downlink carrier is associated with one or more random access preambles corresponding to uplink carriers, or the random access preamble corresponding to one uplink carrier is associated with one or more SSB indices corresponding to downlink carriers, thereby improving random access performance.

[0231] In some embodiments, when an SSB index corresponding to a downlink carrier is associated with an RO corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier is associated with a random access preamble corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers for uplink repetitive transmission.

[0232] In this embodiment, when the SSB index corresponding to a downlink carrier is associated with the RO corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers used for uplink repetitive transmission; and / or, when the SSB index corresponding to a downlink carrier is associated with the random access preamble corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers used for uplink repetitive transmission, thereby improving the uplink repetitive transmission performance.

[0233] In some embodiments, when the SSB index corresponding to a downlink carrier group is associated with the RO corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups for uplink repetitive transmission; and / or, when the SSB index corresponding to a downlink carrier group is associated with the random access preamble corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups for uplink repetitive transmission.

[0234] In this embodiment, when the SSB index corresponding to a downlink carrier group is associated with the RO corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission; and / or, when the SSB index corresponding to a downlink carrier group is associated with the random access preamble corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission, thereby improving uplink repetitive transmission performance.

[0235] It should be noted that the SSB index described in the embodiments of this application may also be referred to as or replaced by SSB beam identifier, beam identifier, etc., and the embodiments of this application are not limited thereto.

[0236] In some embodiments, the wireless communication method 200 further includes:

[0237] The terminal receives the second information;

[0238] The second information includes at least one of the following:

[0239] The conditions that the downlink carriers in each downlink carrier group of the at least one downlink carrier group satisfy;

[0240] The conditions that the downlink carrier groups in the at least one downlink carrier group satisfy;

[0241] The conditions that the downlink carriers of the at least two downlink carriers satisfy.

[0242] Accordingly, the network-side device sends the second information to the terminal.

[0243] In this embodiment, the terminal can obtain at least one of the following based on the second signal received from the network-side device: the conditions satisfied by the downlink carriers in each downlink carrier group in at least one downlink carrier group, the conditions satisfied by the downlink carrier group in at least one downlink carrier group, and the conditions satisfied by the downlink carriers in at least two downlink carriers.

[0244] Optionally, the second information can be carried by system messages or RRC signaling.

[0245] In some embodiments, repeated transmissions of the first uplink information correspond to the same uplink carrier or the same uplink carrier group, or repeated transmissions of the first uplink information correspond to different uplink carriers or different uplink carrier groups.

[0246] In this embodiment, repeated transmission of the first uplink information corresponds to the same uplink carrier or the same uplink carrier group, or repeated transmission of the first uplink information corresponds to different uplink carriers or different uplink carrier groups, thereby allowing for flexible design of the uplink carrier or uplink carrier group corresponding to repeated transmission of the first uplink information.

[0247] In some embodiments, repeated transmission of the first downlink information corresponds to the same downlink carrier or the same downlink carrier group, or repeated transmission of the first downlink information corresponds to different downlink carriers or different downlink carrier groups.

[0248] In this embodiment, repeated transmission of the first downlink information corresponds to the same downlink carrier or the same downlink carrier group, or repeated transmission of the first downlink information corresponds to different downlink carriers or different downlink carrier groups, thereby allowing for flexible design of the downlink carriers or downlink carrier groups corresponding to repeated transmission of the first downlink information.

[0249] In some embodiments, the uplink transmission following the first uplink information or the subsequent uplink transmission corresponds to the same uplink carrier or the same uplink carrier group as the transmission of the first uplink information; or, the uplink transmission following the first uplink information or the subsequent uplink transmission corresponds to a different uplink carrier or a different uplink carrier group as the transmission of the first uplink information.

[0250] In this embodiment, the uplink transmission after the first uplink information or the subsequent uplink transmission corresponds to the same uplink carrier or the same uplink carrier group as the transmission of the first uplink information, or the uplink transmission after the first uplink information or the subsequent uplink transmission corresponds to different uplink carriers or different uplink carrier groups as the transmission of the first uplink information. This allows for flexible design of the uplink carrier or uplink carrier group corresponding to the uplink transmission after the first uplink information or the subsequent uplink transmission and the transmission of the first uplink information.

[0251] For example, in a small data transfer (SDT) process, the first uplink information is an uplink SDT, and the uplink transmission after the first uplink information or subsequent uplink transmissions can be uplink SDTs. The uplink transmission after the first uplink information or subsequent uplink transmissions can also be uplink transmissions after entering the connected state.

[0252] In some embodiments, the downlink transmission following the first downlink information or the subsequent downlink transmission corresponds to the same downlink carrier or the same downlink carrier group as the transmission of the first downlink information; or, the downlink transmission following the first downlink information or the subsequent downlink transmission corresponds to a different downlink carrier or a different downlink carrier group as the transmission of the first downlink information.

[0253] In this embodiment, the downlink transmission after the first downlink information or the subsequent downlink transmission corresponds to the same downlink carrier or the same downlink carrier group as the transmission of the first downlink information, or the downlink transmission after the first downlink information or the subsequent downlink transmission corresponds to different downlink carriers or different downlink carrier groups as the transmission of the first downlink information, so that the downlink carrier or downlink carrier group corresponding to the downlink transmission after the first downlink information or the subsequent downlink transmission and the transmission of the first downlink information can be flexibly designed.

[0254] For example, in a small data transfer (SDT) process, the first downlink information is a downlink SDT, and the downlink transmission after the first downlink information or subsequent downlink transmission can be a downlink SDT. The downlink transmission after the first downlink information or subsequent downlink transmission can also be a downlink transmission after entering the connected state.

[0255] In some embodiments, the first uplink information is uplink information (SDT) for transmitting data in an idle state or a deactivated state, and the uplink information for transmitting data in an idle state or a deactivated state is Msg3 in four-step random access, and the Msg3 in four-step random access includes the first uplink data.

[0256] The target uplink carrier is determined based on at least one of the following:

[0257] The identifier of the terminal;

[0258] Paging messages sent by network-side devices;

[0259] Default uplink carrier;

[0260] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0261] The data volume of the first uplink data;

[0262] The uplink carrier corresponding to the resources of the random access preamble in the four-step random access;

[0263] The uplink carrier identified by the random access preamble in the four-step random access process;

[0264] The uplink carrier available for Msg3 in the four-step random access;

[0265] The uplink carrier indicated in the RAR during four-step random access;

[0266] The uplink carrier corresponding to the PRACH transmission in the four-step random access process.

[0267] In this embodiment, the uplink carrier used for the SDT of Msg3 in the four-step random access can be flexibly determined.

[0268] Optionally, the default uplink carrier can be agreed upon by a protocol, or the default uplink carrier can be configured by the network-side device. For example, the default uplink carrier is the anchor carrier.

[0269] In some embodiments, the first uplink information is uplink information (SDT) for transmitting data in an idle state or a deactivated state, and the uplink information for transmitting data in an idle state or a deactivated state is MsgA in two-step random access, and the MsgA in two-step random access includes second uplink data.

[0270] The target uplink carrier is determined based on at least one of the following:

[0271] The identifier of the terminal;

[0272] Paging messages sent by network-side devices;

[0273] Default uplink carrier;

[0274] The uplink carrier associated with the downlink carrier corresponding to the SSB transmission used for synchronization;

[0275] The uplink carrier available for MsgA in the two-step random access;

[0276] DCI in PDCCH used to trigger non-contention-based two-step random access;

[0277] The amount of data in the second uplink;

[0278] Downlink signal quality of the reference carrier;

[0279] The uplink carrier available for MsgA in the two-step random access associated with the downlink carrier with the highest downlink signal quality.

[0280] In this embodiment, the uplink carrier used for transmitting MsgA in two-step random access can be flexibly determined.

[0281] In some embodiments, the first uplink information is uplink information for transmitting data in an idle state or a deactivated state, and the uplink information for transmitting data in an idle state or a deactivated state is uplink transmission on CG resources.

[0282] The target uplink carrier is determined based on at least one of the following:

[0283] The identifier of the terminal;

[0284] Paging messages sent by network-side devices;

[0285] Default uplink carrier;

[0286] The uplink carrier associated with the downlink carrier corresponding to the SSB transmission used for synchronization;

[0287] The amount of data to be transmitted;

[0288] The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

[0289] In this embodiment, the uplink carrier for uplink transmission on CG resources can be flexibly determined.

[0290] In some embodiments, the first downlink information is downlink information for transmitting data in an idle state or a deactivated state, and the downlink information for transmitting data in an idle state or a deactivated state is Msg4 in four-step random access, and the Msg4 in four-step random access includes the first downlink data.

[0291] The target downlink carrier is determined based on at least one of the following:

[0292] The identifier of the terminal;

[0293] Paging messages sent by network-side devices;

[0294] The downlink carrier available for Msg4 in the four-step random access;

[0295] The downlink carrier corresponding to the RAR transmission in the four-step random access;

[0296] The downlink carrier indicated in the RAR during four-step random access;

[0297] In the four-step random access, the downlink carrier associated with the uplink carrier corresponding to the Msg3 transmission;

[0298] The downlink carrier corresponding to the SSB used for synchronization;

[0299] The data volume of the first downlink data;

[0300] Reference carrier;

[0301] Default downlink carrier;

[0302] The downlink carrier with the highest signal quality (highest RSRP, highest RSRQ, or highest SINR);

[0303] The downlink carrier with the highest average signal quality (highest average RSRP, highest average RSRQ, or highest average SINR).

[0304] In this embodiment, the downlink carrier of the downlink SDT transmitted in Msg4 during the four-step random access can be flexibly determined.

[0305] In some embodiments, the first downlink information is downlink information for transmitting data in an idle state or a deactivated state, and the downlink information for transmitting data in an idle state or a deactivated state is MsgB in two-step random access, and the MsgB in two-step random access includes second downlink data.

[0306] The target downlink carrier is determined based on at least one of the following:

[0307] The identifier of the terminal;

[0308] Paging messages sent by network-side devices;

[0309] The downlink carrier corresponding to the SSB transmission used for synchronization;

[0310] The amount of data in the second downlink data;

[0311] The downlink carrier available for MsgB in the two-step random access;

[0312] The downlink carrier associated with the uplink carrier in the MsgA transmission during two-step random access;

[0313] The downlink carrier indicated in MsgA during two-step random access;

[0314] Reference carrier;

[0315] Default downlink carrier;

[0316] The downlink carrier with the highest signal quality (highest RSRP, highest RSRQ, or highest SINR);

[0317] The downlink carrier with the highest average signal quality (highest average RSRP, highest average RSRQ, or highest average SINR).

[0318] In this embodiment, the downlink carrier of the downlink SDT transmitted in MsgB during two-step random access can be flexibly determined.

[0319] In some embodiments, the first uplink information is uplink information in LTM handover, and the uplink information in LTM handover includes, but is not limited to, at least one of the following: information for uplink synchronization, uplink transmission on CG resources, PRACH in four-step random access, Msg3 in four-step random access, uplink messages after Msg4 in four-step random access (such as Msg5), and MsgA in two-step random access.

[0320] The target uplink carrier is determined based on at least one of the following:

[0321] The identifier of the terminal;

[0322] Paging messages sent by network-side devices;

[0323] Default uplink carrier;

[0324] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0325] The LTM switching command indicates;

[0326] The uplink carrier available for the uplink information during the LTM handover;

[0327] The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

[0328] In this embodiment, the uplink carrier of the uplink information during LTM handover can be flexibly determined.

[0329] It should be noted that PRACH in four-step random access can also be called or replaced by Msg1 or the random access preamble in four-step random access.

[0330] In some implementations, the uplink information in the LTM handover is the PRACH in the four-step random access;

[0331] The target uplink carrier is determined based on at least one of the following:

[0332] The identifier of the terminal;

[0333] Paging messages sent by network-side devices;

[0334] The LTM switching command indicates;

[0335] Uplink carriers available for uplink information during LTM handover;

[0336] The uplink carrier available for PRACH in the four-step random access;

[0337] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0338] Downlink signal quality of the reference carrier;

[0339] DCI in the PDCCH used to trigger non-contentionable four-step random access;

[0340] The uplink carrier available for PRACH in the four-step random access associated with the downlink carrier that has the highest downlink signal quality (e.g., highest RSRP, highest RSRQ, or highest SINR).

[0341] In some implementations, the uplink information in the LTM handover is Msg3 in the four-step random access;

[0342] The target uplink carrier is determined based on at least one of the following:

[0343] The identifier of the terminal;

[0344] Paging messages sent by network-side devices;

[0345] Default uplink carrier;

[0346] The LTM switching command indicates;

[0347] Uplink carriers available for uplink information during LTM handover;

[0348] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0349] The uplink carrier available for Msg3 in the four-step random access;

[0350] The uplink carrier indicated in the RAR during four-step random access;

[0351] The uplink carrier corresponding to the PRACH transmission in the four-step random access process.

[0352] In some implementations, the uplink information in the LTM handover is the uplink message after Msg4 (such as Msg5);

[0353] The target uplink carrier is determined based on at least one of the following:

[0354] The identifier of the terminal;

[0355] Paging messages sent by network-side devices;

[0356] Default uplink carrier;

[0357] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0358] The LTM switching command indicates;

[0359] Uplink carriers available for uplink information during LTM handover;

[0360] The uplink carrier available for uplink messages after Msg4 in four-step random access;

[0361] The DCI used in Msg4 of the four-step random access process to schedule uplink messages after Msg4 in the four-step random access process.

[0362] The uplink carrier corresponding to Msg3 transmission in the four-step random access;

[0363] The uplink carrier indicated in the RAR during four-step random access;

[0364] The uplink carrier corresponding to the PRACH transmission in the four-step random access process.

[0365] Specifically, after receiving Msg4, the terminal needs to send Msg5 to complete the corresponding RRC connection establishment or recovery process. Msg5 can be used to carry the RRC setup complete message, RRC resume complete message, and RRC reestablishment complete message.

[0366] For example, the carrier corresponding to the transmission of Msg5 includes: Msg5 scheduling carrier, Msg5 transmission carrier, and optionally, Msg5 retransmission carrier.

[0367] In some implementations, the uplink information in the LTM handover is MsgA in the two-step random access;

[0368] The target uplink carrier is determined based on at least one of the following:

[0369] The identifier of the terminal;

[0370] Paging messages sent by network-side devices;

[0371] The uplink carrier associated with the downlink carrier corresponding to the SSB transmission used for synchronization;

[0372] The LTM switching command indicates;

[0373] Uplink carriers available for uplink information during LTM handover;

[0374] The uplink carrier available for MsgA in the two-step random access;

[0375] DCI in PDCCH used to trigger non-contention-based two-step random access;

[0376] Downlink signal quality of the reference carrier;

[0377] The uplink carrier available for MsgA in the two-step random access associated with the downlink carrier with the highest downlink signal quality.

[0378] In some embodiments, the first downlink information is downlink information in LTM handover, and the downlink information in LTM handover includes, but is not limited to, at least one of the following: LTM handover command, RAR in four-step random access, Msg4 in four-step random access, and MsgB in two-step random access.

[0379] The target downlink carrier is determined based on at least one of the following:

[0380] The identifier of the terminal;

[0381] Paging messages sent by network-side devices;

[0382] Default downlink carrier;

[0383] The downlink carrier corresponding to the SSB used for synchronization;

[0384] The LTM switching command indicates;

[0385] LTM handover command transmission corresponds to the downlink carrier;

[0386] The uplink carrier available for the downlink information during the LTM handover;

[0387] The downlink carrier with the highest downlink signal quality;

[0388] The downlink carrier with the highest average signal quality.

[0389] In this embodiment, the downlink carrier for downlink information during LTM handover can be flexibly determined.

[0390] It should be noted that RAR in the four-step random access can also be called or replaced by Msg2 in the four-step random access, and this application does not limit it in this way.

[0391] In some implementations, the downlink information in the LTM handover is the RAR in the four-step random access;

[0392] The target downlink carrier is determined based on at least one of the following:

[0393] The identifier of the terminal;

[0394] Paging messages sent by network-side devices;

[0395] The downlink carriers available for RAR in the four-step random access;

[0396] The downlink carrier associated with the uplink carrier corresponding to the PRACH transmission in four-step random access;

[0397] The LTM switching command indicates;

[0398] LTM handover command transmission corresponds to the downlink carrier;

[0399] The uplink carrier available for the downlink information during the LTM handover;

[0400] The downlink carrier corresponding to the SSB used for synchronization;

[0401] Reference carrier;

[0402] Default downlink carrier;

[0403] The downlink carrier with the highest signal quality;

[0404] The downlink carrier with the highest average signal quality.

[0405] In some implementations, the downlink information in the LTM handover is Msg4 in the four-step random access method;

[0406] The target downlink carrier is determined based on at least one of the following:

[0407] The identifier of the terminal;

[0408] Paging messages sent by network-side devices;

[0409] The LTM switching command indicates;

[0410] LTM handover command transmission corresponds to the downlink carrier;

[0411] The uplink carrier available for downlink information during LTM handover;

[0412] The downlink carrier available for Msg4 in the four-step random access;

[0413] The downlink carrier corresponding to the RAR transmission in the four-step random access;

[0414] In the four-step random access, the downlink carrier associated with the uplink carrier corresponding to the Msg3 transmission;

[0415] The downlink carrier corresponding to the SSB used for synchronization;

[0416] Reference carrier;

[0417] Default downlink carrier;

[0418] The downlink carrier with the highest signal quality;

[0419] The downlink carrier with the highest average signal quality.

[0420] In some implementations, the downlink information in the LTM handover is the MsgB from the two-step random access;

[0421] The target downlink carrier is determined based on at least one of the following:

[0422] The identifier of the terminal;

[0423] Paging messages sent by network-side devices;

[0424] The LTM switching command indicates;

[0425] LTM handover command transmission corresponds to the downlink carrier;

[0426] The uplink carrier available for downlink information during LTM handover;

[0427] The downlink carrier corresponding to the SSB transmission used for synchronization;

[0428] The downlink carrier available for MsgB in the two-step random access;

[0429] The uplink carrier corresponding to the MsgA transmission in two-step random access;

[0430] The downlink carrier indicated in MsgA during two-step random access;

[0431] Reference carrier;

[0432] Default downlink carrier;

[0433] The downlink carrier with the highest signal quality;

[0434] The downlink carrier with the highest average signal quality.

[0435] In some embodiments, the first uplink information is uplink information in a RACH-less handover, and the uplink information in the RACH-less handover includes at least one of the following:

[0436] Configure Grant Physical Uplink Shared Channel (CG PUSCH), where the uplink information during the handover without random access is Dynamic Grant Physical Uplink Shared Channel (DG PUSCH).

[0437] In some embodiments, the first uplink information is uplink information in a RACH-less handover, and the uplink information in the RACH-less handover is CG PUSCH;

[0438] The target uplink carrier is determined based on at least one of the following:

[0439] The identifier of the terminal;

[0440] Paging messages sent by network-side devices;

[0441] Default uplink carrier;

[0442] The uplink carrier available for the CG PUSCH;

[0443] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0444] The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

[0445] In this embodiment, the uplink carrier of the uplink information (CG PUSCH) in RACH-less handover can be flexibly determined.

[0446] In some embodiments, the SSB index associated with the uplink carrier corresponding to the initial transmission of CG PUSCH is the same as the SSB index associated with the uplink carrier corresponding to the retransmission of CG PUSCH, or the SSB index associated with the uplink carrier corresponding to the initial transmission of CG PUSCH is associated with the SSB index associated with the uplink carrier corresponding to the retransmission of CG PUSCH.

[0447] In this embodiment, the SSB index associated with the uplink carrier corresponding to the initial transmission of CG PUSCH is the same as the SSB index associated with the uplink carrier corresponding to the retransmission of CG PUSCH, or the SSB index associated with the uplink carrier corresponding to the initial transmission of CG PUSCH is associated with the SSB index associated with the uplink carrier corresponding to the retransmission of CG PUSCH, thereby improving the retransmission performance of CG PUSCH.

[0448] In some embodiments, if the SSB index associated with the uplink carrier corresponding to the initial transmission of the CG PUSCH is the same as the SSB index associated with the uplink carrier corresponding to the retransmission of the CG PUSCH, the retransmission resources on the uplink carrier corresponding to the retransmission of the CG PUSCH are valid; and / or, if the SSB index associated with the uplink carrier corresponding to the initial transmission of the CG PUSCH is associated with the SSB index associated with the uplink carrier corresponding to the retransmission of the CG PUSCH, the retransmission resources on the uplink carrier corresponding to the retransmission of the CG PUSCH are valid.

[0449] In this embodiment, if the SSB index associated with the uplink carrier corresponding to the initial transmission of CG PUSCH is the same as the SSB index associated with the uplink carrier corresponding to the retransmission of CG PUSCH, the retransmission resources on the uplink carrier corresponding to the retransmission of CG PUSCH are valid. Therefore, CG PUSCH retransmission can be performed based on the valid CG PUSCH retransmission resources, which can improve the retransmission performance of CG PUSCH.

[0450] In this embodiment, if the SSB index associated with the uplink carrier corresponding to the initial transmission of CG PUSCH is associated with the SSB index associated with the uplink carrier corresponding to the retransmission of CG PUSCH, the retransmission resources on the uplink carrier corresponding to the retransmission of CG PUSCH are valid. Therefore, CG PUSCH retransmission can be performed based on the valid CG PUSCH retransmission resources, which can improve the retransmission performance of CG PUSCH.

[0451] In some embodiments, the uplink carrier corresponding to the initial transmission of the CG PUSCH is the same as the uplink carrier corresponding to the retransmission of the CG PUSCH, or the uplink carrier corresponding to the initial transmission of the CG PUSCH is different from the uplink carrier corresponding to the retransmission of the CG PUSCH.

[0452] In this embodiment, the uplink carrier corresponding to the initial transmission of CG PUSCH is the same as the uplink carrier corresponding to the retransmission of CG PUSCH, or the uplink carrier corresponding to the initial transmission of CG PUSCH is different from the uplink carrier corresponding to the retransmission of CG PUSCH. This allows for flexible design of the uplink carrier corresponding to the initial transmission of CG PUSCH and the uplink carrier corresponding to the retransmission of CG PUSCH, thereby improving the transmission performance of CG PUSCH.

[0453] In some embodiments, the first uplink information is uplink information in a RACH-less handover, and the uplink information in the RACH-less handover is DG PUSCH;

[0454] The target uplink carrier is determined based on at least one of the following:

[0455] The identifier of the terminal;

[0456] Paging messages sent by network-side devices;

[0457] Default uplink carrier;

[0458] The uplink carrier available for the DG PUSCH;

[0459] The uplink carrier indicated by the RRC reconfiguration message;

[0460] The uplink carrier indicated by the PDCCH used to schedule the DG PUSCH;

[0461] The uplink carrier associated with the downlink carrier corresponding to the DG PUSCH is used to schedule the DG PUSCH.

[0462] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0463] The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

[0464] In this embodiment, the uplink carrier of the uplink information (DG PUSCH) in RACH-less handover can be flexibly determined.

[0465] In some embodiments, the wireless communication method 200 further includes:

[0466] The terminal sends third information;

[0467] The third information is used to indicate whether the terminal supports data transmission based on multiple carriers or multiple carrier groups in idle or deactivated states, or whether the third information is used to indicate whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during LTM handover, or whether the third information is used to indicate whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during handover without random access.

[0468] Correspondingly, the network-side devices receive third-party information from the terminal.

[0469] In this embodiment, the terminal reports third information to the network-side device, thereby enabling the network-side device to determine whether the terminal supports data transmission based on multiple carriers or multiple carrier groups in idle or deactivated states, or whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during LTM handover, or whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during handover without random access.

[0470] Optionally, the third information can be carried by at least one of the following:

[0471] RRC signaling, Uplink Control Information (UCI), MAC CE.

[0472] Therefore, in this embodiment, the terminal determines a target uplink carrier based on the first information, and the terminal sends first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by the terminal in an idle state or a deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or, the terminal determines a target downlink carrier based on the first information, and the terminal receives first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information for data reception by the terminal in an idle state or a deactivated state, or, the first uplink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access. Specifically, for processes such as SDT, RACH-less handover, and LTM handover, the target uplink carrier can be flexibly adjusted within the uplink carrier group or at least two uplink carriers, and / or the target downlink carrier can be flexibly adjusted within the downlink carrier group or at least two downlink carriers. While ensuring uplink and downlink transmission coverage, this helps to achieve better load balancing, reduce inter-carrier interference, and improve the performance of processes such as SDT, RACH-less handover, and LTM handover.

[0473] The technical solution of this application is described in detail below through specific embodiments.

[0474] Example 1: Taking uplink information (such as uplink SDT) that transmits data when the first uplink information is in an idle or inactive state, and downlink information (such as downlink SDT) that transmits data when the first downlink information is in an idle or inactive state as an example.

[0475] In Example 1, for data transmission in idle or inactive states, such as Small Data Transmission (SDT), Random Access-based SDT (RA-based SDT) and Gardner-based SDT (CG-based SDT) are supported. In this example, for multi-carrier scenarios, for RACH-based or CG-based small data transmission, the uplink or uplink carrier is flexibly selected from at least two uplink carriers and / or at least two downlink carriers for data transmission and reception. The uplink and downlink carriers can be flexibly paired without a constrained correspondence.

[0476] RA-based SDT

[0477] For RA-based SDT, SDT can be performed based on two-step random access (2-step RACH) or four-step random access (4-step RACH). During random access, the terminal determines the downlink receive carrier and / or uplink transmit carrier for different messages based on network-side device configuration or network-side device instructions.

[0478] In one possible implementation, the network-side device configures multiple Msg3 candidate carriers. For different carriers, the network-side device configures different data volume thresholds. Different Msg3 candidate carriers are associated with different preamble carriers or different preamble resources. Based on the data volume thresholds and uplink data volume configured by the network-side device, the terminal determines the Msg3 transmission carrier selected by the terminal, or determines the Msg3 transmission carrier preferred by the terminal, or determines the Msg3 transmission carrier desired by the terminal. Further, the terminal transmits the preamble associated with the Msg3 transmission carrier. Based on the detected preamble information, the network-side device can obtain the Msg3 transmission carrier desired by the terminal, or obtain the uplink data volume range of the terminal, and accordingly determine / indicate the carrier for the initial transmission and / or retransmission of Msg3.

[0479] In one possible implementation, the network-side device configures multiple PUSCH candidate carriers corresponding to MsgA, and configures different data volume thresholds for different carriers. Different PUSCH candidate carriers corresponding to MsgA can be distinguished by the MsgA-corresponding PRACH carriers associated with them, or by the MsgA-corresponding Preamble resources associated with them. The terminal determines the selected MsgA-corresponding PRACH and MsgA-corresponding PUSCH resources based on the data volume thresholds and uplink data volume configured by the network-side device.

[0480] In one possible implementation, for the small data carried in the PUSCH corresponding to Msg3 or MsgA, the network-side device can configure an independent carrier group or the same carrier group as the random access procedure for subsequent transmissions. For the same or different carrier groups, the carriers used in subsequent transmissions can be the same or different from those used in the random access procedure.

[0481] CG-based SDT

[0482] The network-side equipment configures CG resources for the terminal on multiple carrier groups or carriers, and configures carrier group or carrier selection conditions for the terminal for CG. In one possible implementation, the network-side equipment configures CG resources for the terminal on multiple carriers, with different data volume thresholds configured for different carriers, and the terminal selects the corresponding carrier based on the size of the transmitted data.

[0483] For an uplink carrier containing CG resources, its corresponding downlink carrier may or may not have an SSB (SSB) transmission. Correspondingly, the association between CG resources and SSBs configured by the network-side equipment can be based on the same carrier or different carriers. In one possible implementation, the network-side equipment configures CG resources for the terminal on multiple carriers. If the downlink carrier corresponding to the uplink carrier selected by the terminal does not contain an SSB, the terminal measures the SSBs on other downlink carriers associated with that downlink carrier and determines the CG resources based on the uplink / downlink carrier associations configured by the network-side equipment. For example, the network-side equipment determines the CG resources used for SDT (Segmented Data Transmission) on the uplink carrier based on the SSBs on the downlink carriers and the associations between the SSBs on the downlink carriers and the CGs on the uplink carriers configured by the network-side equipment.

[0484] Figure 4 illustrates a multi-carrier CG-SDT method. The network-side equipment configures CG resources for the terminal on the first uplink carrier and the second uplink carrier for small data transmission (SDT). Both the first uplink carrier and the second uplink carrier are associated with the first downlink carrier. That is, the network-side equipment configures the mapping between the SSB of the first downlink carrier and the CG resources of the first uplink carrier or the second uplink carrier. Based on the SSB measurement of the first downlink carrier (e.g., selecting the SSB with the best channel quality), the terminal selects the optimal CG resource on the first uplink carrier or the second uplink carrier to transmit uplink small data.

[0485] Optionally, for small data transmission based on CG, retransmission is supported. The retransmission carrier can be the same as or different from the initial transmission carrier. The retransmission carrier can be based on network configuration or determined by the terminal, which notifies the network of the associated initial transmission information (such as the Hybrid Automatic Repeat reQuest (HARQ) process) through corresponding indication information. In one possible implementation, small data transmission based on CG supports automatic retransmission, where the automatic retransmission carrier can be the same as or different from the initial transmission carrier or the previous retransmission carrier. The determination of the retransmission carrier can be pre-configured by the network, such as the network-side device configuring a carrier list from the first to the Nth transmission (e.g., the initial transmission and N-1 retransmissions), or the terminal can send corresponding indication information before the corresponding CG transmission timing to instruct the CG transmission carrier.

[0486] Optionally, for subsequent transmissions, the network-side device can configure a carrier group for the subsequent transmission. In one possible implementation, the network-side device configures a carrier group for subsequent transmission, and the carriers contained in this carrier group are not exactly the same as the carriers contained in the carrier group used for CG-SDT. In another possible implementation, the network-side device does not configure an additional independent carrier group, that is, the carrier group for subsequent transmission is the same as the carrier group used for CG transmission, but the transmission of subsequent data can be different from the selected CG carrier.

[0487] Example 2: Taking the uplink information in the first uplink information as RACH-less handover and the downlink information in the first downlink information as RACH-less handover as examples.

[0488] In Example 2, for RACH-less handover, both configured grant (CG)-based and dynamic grant (DG)-based RACH-less handover are supported. In this example, for multi-carrier scenarios, RACH-based or CG-based RACH-less handover can flexibly select uplink or downlink carriers from at least two uplink carriers and / or at least two downlink carriers for data transmission and reception. The uplink and downlink carriers can be flexibly paired without requiring a constrained correspondence.

[0489] CG-based RACH-less switching

[0490] The network-side device configures CG resources on multiple carriers for the terminal, which is used by the terminal to send an RRC Reconfiguration Complete message. Optionally, the network-side device configures RACH-less carrier selection conditions for the terminal based on CG. In one possible implementation, the network-side device configures CG resources on multiple carriers for the terminal, which is used by the terminal to send an RRC Reconfiguration Complete message. Different thresholds are configured for different carriers, that is, the network-side device configures thresholds according to carrier granularity (per carrier), beam granularity (per beam), or SSB granularity (per SSB). The thresholds are used to determine whether the CG resources are valid. When all carriers and all beams are below the threshold, the configured CG is considered invalid, and random access is triggered. For CGs that meet the conditions, the Media Access Control (MAC) layer indicates the carrier ultimately selected by the underlying layer and its associated SSB index.

[0491] For an uplink carrier carrying CG resources, its corresponding downlink carrier may or may not have an SSB (SSB) transmission. Correspondingly, the association between CG resources and SSBs configured by the network-side equipment can be based on the same carrier or different carriers. In one possible implementation, if the downlink carrier corresponding to the uplink carrier selected by the terminal does not contain an SSB, the terminal measures the SSBs on other downlink carriers associated with that downlink carrier and determines the CG resources based on the cross-carrier association relationships configured by the network-side equipment. For example, the network-side equipment determines the CG resources transmitted on the uplink carrier based on the SSBs on the downlink carrier and the association relationships between the SSBs on the downlink carrier and the CGs on the uplink carrier configured by the network-side equipment.

[0492] Optionally, RACH-less handover based on CG supports CG retransmission. The CG retransmission carrier can be the same as or different from the initial transmission carrier. In one possible approach, the CG retransmission carrier is different from the initial transmission carrier. The terminal considers the CG valid based on the SSB association relationship between carriers. If the SSB index of the initial transmission carrier corresponding to the SSB selected by the retransmission carrier is the same as or associated with the initial transmission carrier, the CG is considered valid. One illustration is shown in Figure 5. The initial transmission carrier of the CG is the first uplink carrier, the beam / SSB associated with the CG resource selected by the terminal is beam 1 in Figure 5, and the retransmission carrier of the CG is the second uplink carrier. The beam of the second uplink carrier is the same as the beam of the first uplink carrier, or the beam of the second uplink carrier reuses the beam of the first uplink carrier. Therefore, the retransmission of the CG is valid only if the beam / SSB associated with the CG resource selected by the terminal on the second uplink carrier is also beam 1 in Figure 5. In another illustration, the initial CG transmission carrier is the first uplink carrier, the beam / SSB associated with the CG resource selected by the terminal is beam 1 in Figure 5, and the retransmission carrier of the CG is the third uplink carrier. The beams of the third uplink carrier have a corresponding relationship with the beams of the first uplink carrier (inclusion relationship in Figure 5). For example, beam 1 of the third uplink carrier corresponds to beams 1 and 2 of the first uplink carrier, and beam 2 of the third uplink carrier corresponds to beams 3 and 4 of the first uplink carrier. Therefore, the retransmission of the CG is valid only when the beam / SSB associated with the CG resource selected by the terminal on the third uplink carrier is beam 1 in Figure 5.

[0493] DG-based RACH-less switching

[0494] In RACH-less handover based on DG, the carrier used for PDCCH listening and the carrier for receiving RRC reconfiguration messages can be the same or different. For example, the terminal receives an RRC reconfiguration message on downlink carrier a. The reconfiguration message instructs the terminal to listen to the PDCCH via uplink carrier a. The PDCCH is used to schedule the transmission of uplink information (such as RRC reconfiguration completion).

[0495] In one possible implementation, the carrier used for PDCCH listening can be the same as or different from the PUSCH transmission carrier scheduled by the terminal. For example, the terminal listens for PDCCH on downlink carrier b, which schedules the terminal to transmit PUSCH on uplink carrier b. The uplink carrier b can be indicated by RRC signaling configuration, or by DCI, or by DCI indicating one of multiple candidate carriers configured by RRC.

[0496] In one possible implementation, the beam indication included in the RRC reconfiguration message may be the same as or different from the PDCCH listening carrier. Optionally, the network-side device can configure SSB associations between different carriers, and the terminal determines the PDCCH listening beam based on these associations. For example, the beam indication included in the RRC reconfiguration is the SSB index of the first carrier, and the terminal listens for the PDCCH on the second carrier, determining the PDCCH listening beam based on the SSB mapping of the first and second carriers configured by the network-side device; or, the beam indication included in the RRC reconfiguration is the SSB index of the first carrier, the terminal listens for the PDCCH on the second carrier, the second carrier has no SSB, the network indicates that the second carrier can refer to the SSB of the first carrier, and the terminal determines the PDCCH listening beam based on the SSB on the first carrier.

[0497] The RACH-less handover described in this embodiment is applicable to Layer 3-based handover and also to LTM-based handover. For LTM-based handover without random access, similar to the above scheme, the LTM candidate configuration may include CG configuration. Optionally, the CG configuration included in the LTM candidate configuration may be CG resources configured on multiple carriers. In this scenario, CG carrier selection, CG association with SSB, and CG retransmission are the same as in the CG-based RACH-less handover in this embodiment, and will not be repeated here.

[0498] Example 3: Taking the first uplink information as the uplink information in LTM and the first downlink information as the downlink information in LTM as an example.

[0499] In Example 3, for LTM-based handover, including RACH-based LTM handover and RACH-free LTM handover, in this example, for multi-carrier scenarios, for the RACH-based LTM handover process and the RACH-free LTM handover process (including at least one of the following: LTM candidate configuration, early synchronization, measurement feedback, cell handover indication, random access), the downlink carrier or uplink carrier for data transmission and reception can be flexibly selected from multiple uplink available carriers and / or downlink available carriers. The uplink available carriers and downlink available carriers can be flexibly paired without a constrained correspondence. Correspondingly, the relevant LTM configuration information includes at least one of the following related configurations applicable to the LTM process: downlink carrier group, downlink carrier, uplink carrier group, and uplink carrier.

[0500] For RACH-free LTM handover, the terminal needs to obtain the downlink timing and uplink timing of the target cell in advance. For multi-carrier scenarios, the network-side equipment configures multiple uplink carrier groups and / or uplink carriers for uplink early synchronization. Optionally, based on carrier group and / or carrier selection conditions, the terminal sends a random access preamble to obtain uplink synchronization in advance; or, the terminal sends a preamble on the uplink carrier groups and / or uplink carriers configured by the network-side equipment to obtain uplink synchronization of each uplink carrier group and / or uplink carrier in advance.

[0501] In scenarios where there is no effective uplink timing, including when the uplink timing of the target cell is not obtained in advance, or when the uplink timing information of the target cell that has been obtained is invalid, the terminal initiates a random access procedure. In this scenario, the LTM cell handover command (such as through MAC CE) may carry the uplink carrier for sending the preamble, and optionally, the uplink carrier group and / or downlink carrier group indicating the random access procedure.

[0502] For contention-based LTM handover, during the random access procedure, as mentioned above, the LTM cell handover command (e.g., carried via MAC CE) can include the uplink carrier for transmitting the preamble. It should be noted that the random access procedure supports both contention-based and non-contention-based random access.

[0503] The wireless communication method provided in this application can be executed by a wireless communication device. This application uses an example of a wireless communication device executing the wireless communication method to illustrate the wireless communication device provided in this application.

[0504] This application provides a wireless communication device. As an example, the wireless communication device may be a communication equipment or a component within a communication equipment, such as a chip. The communication equipment may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0505] The wireless communication 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, 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.

[0506] Referring to Figure 6, when the wireless communication device is a terminal or a component in a terminal, the wireless communication device 300 includes: a processing module 301, a transmitting module 302, and a receiving module 303;

[0507] The processing module 301 or the receiving module 303 is used to acquire first information; wherein, the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0508] The processing module 301 is further configured to determine a target uplink carrier based on the first information, and the transmitting module 302 is configured to transmit first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information of a terminal transmitting data in an idle state or a deactivated state, or, the first uplink information is uplink information during a Layer 1 / Layer 2 triggered mobility LTM handover, or, the first uplink information is uplink information during a handover without random access; and / or,

[0509] The processing module 301 is further configured to determine a target downlink carrier based on the first information, and the receiving module 303 is configured to receive first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information of data received by a terminal in an idle state or a deactivated state, or, the first downlink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access.

[0510] In some embodiments, the processing module 301 is specifically used for:

[0511] Determine a target uplink carrier group from the at least one uplink carrier group, and determine the target uplink carrier from the target uplink carrier group; or,

[0512] The target uplink carrier is determined from the at least two uplink carriers;

[0513] And / or,

[0514] Determine a target downlink carrier group from the at least one downlink carrier group, and determine the target downlink carrier from the target downlink carrier group; or,

[0515] The target downlink carrier is determined from the at least two downlink carriers.

[0516] In some embodiments, a downlink carrier group is associated with one or more uplink carrier groups; and / or,

[0517] An uplink carrier group is associated with one or more downlink carrier groups.

[0518] In some embodiments, the first information includes the association between the uplink carrier group and the downlink carrier group;

[0519] or,

[0520] The association between the uplink carrier group and the downlink carrier group is determined based on at least one of the following:

[0521] Frequency band, frequency band combination, spectrum range, bandwidth portion (BWP).

[0522] In some embodiments, the downlink carriers within each downlink carrier group of the at least one downlink carrier group satisfy at least one of the following conditions:

[0523] Some or all of the downlink carriers correspond to the same synchronization signal block (SSB) index;

[0524] There is a correlation between the SSB indices corresponding to some or all downlink carriers;

[0525] The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB.

[0526] or,

[0527] The downlink carrier group in the at least one downlink carrier group satisfies at least one of the following conditions:

[0528] Some or all downlink carrier groups correspond to the same SSB index;

[0529] There is a correlation between the SSB indices corresponding to some or all downlink carrier groups;

[0530] or,

[0531] The downlink carriers of the at least two downlink carriers satisfy at least one of the following conditions:

[0532] Some or all downlink carriers correspond to the same SSB index;

[0533] There is a correlation between the SSB indices corresponding to some or all downlink carriers;

[0534] The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB.

[0535] In some embodiments, the downlink carriers within each downlink carrier group of the at least one downlink carrier group satisfy at least one of the following conditions:

[0536] A downlink carrier's SSB index is associated with one or more uplink carriers' random access opportunities (ROs).

[0537] An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices;

[0538] An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers;

[0539] A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers;

[0540] A downlink carrier's corresponding SSB index is associated with one or more uplink carrier configuration authorization CG resources;

[0541] A CG resource for an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers;

[0542] or,

[0543] The downlink carrier group in the at least one downlink carrier group satisfies at least one of the following conditions:

[0544] An SSB index corresponding to a downlink carrier group is associated with one or more ROs corresponding to uplink carrier groups.

[0545] An RO corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups.

[0546] An SSB index corresponding to a downlink carrier group is associated with one or more random access preambles corresponding to uplink carrier groups.

[0547] A random access preamble corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups;

[0548] An SSB index corresponding to a downlink carrier group is associated with CG resources of one or more uplink carrier groups;

[0549] A CG resource for an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups;

[0550] or,

[0551] The downlink carriers of the at least two downlink carriers satisfy at least one of the following conditions:

[0552] An SSB index corresponding to a downlink carrier is associated with one or more ROs corresponding to uplink carriers.

[0553] An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices;

[0554] An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers;

[0555] A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers;

[0556] An SSB index corresponding to a downlink carrier is associated with one or more CG resources of uplink carriers;

[0557] An uplink carrier's CG resource is associated with one or more downlink carriers' corresponding SSB indices.

[0558] In some embodiments, when an SSB index corresponding to a downlink carrier is associated with ROs corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier is associated with random access preambles corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier is associated with CG resources of multiple uplink carriers, the multiple uplink carriers are uplink carriers for uplink repetitive transmission.

[0559] or,

[0560] When an SSB index corresponding to a downlink carrier group is associated with ROs corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier group is associated with random access preambles corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier group is associated with CG resources of multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission.

[0561] In some embodiments, the receiving module 303 is further configured to receive second information;

[0562] The second information includes at least one of the following:

[0563] The conditions that the downlink carriers in each downlink carrier group of the at least one downlink carrier group satisfy;

[0564] The conditions that the downlink carrier groups in the at least one downlink carrier group satisfy;

[0565] The conditions that the downlink carriers of the at least two downlink carriers satisfy.

[0566] In some embodiments, repeated transmission of the first uplink information corresponds to the same uplink carrier or the same uplink carrier group, or repeated transmission of the first uplink information corresponds to different uplink carriers or different uplink carrier groups.

[0567] And / or,

[0568] The repeated transmission of the first downlink information corresponds to the same downlink carrier or the same downlink carrier group, or the repeated transmission of the first downlink information corresponds to different downlink carriers or different downlink carrier groups.

[0569] In some embodiments, the uplink transmission following the first uplink information corresponds to the same uplink carrier or the same uplink carrier group as the transmission of the first uplink information; or, the uplink transmission following the first uplink information corresponds to different uplink carriers or different uplink carrier groups as the transmission of the first uplink information.

[0570] And / or,

[0571] The downlink transmission following the first downlink information corresponds to the same downlink carrier or the same downlink carrier group as the transmission of the first downlink information, or the downlink transmission following the first downlink information corresponds to a different downlink carrier or a different downlink carrier group than the transmission of the first downlink information.

[0572] In some embodiments, the first uplink information is uplink information transmitting data in an idle state or a deactivated state, and the uplink information transmitting data in the idle state or a deactivated state is message 3Msg3 in the four-step random access, and the Msg3 in the four-step random access includes the first uplink data.

[0573] The target uplink carrier is determined based on at least one of the following:

[0574] The identifier of the wireless communication device 300;

[0575] Paging messages sent by network-side devices;

[0576] Default uplink carrier;

[0577] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0578] The data volume of the first uplink data;

[0579] The uplink carrier corresponding to the resources of the random access preamble in the four-step random access;

[0580] The uplink carrier identified by the random access preamble in the four-step random access process;

[0581] The uplink carrier available for Msg3 in the four-step random access;

[0582] The uplink carrier indicated in the RAR during four-step random access;

[0583] The uplink carrier corresponding to the PRACH transmission in the four-step random access process.

[0584] In some embodiments, the first uplink information is uplink information transmitting data in an idle state or a deactivated state, and the uplink information transmitting data in the idle state or a deactivated state is message AMsgA in two-step random access, and the MsgA in two-step random access includes second uplink data.

[0585] The target uplink carrier is determined based on at least one of the following:

[0586] The identifier of the wireless communication device 300;

[0587] Paging messages sent by network-side devices;

[0588] Default uplink carrier;

[0589] The uplink carrier associated with the downlink carrier corresponding to the SSB transmission used for synchronization;

[0590] The uplink carrier available for MsgA in the two-step random access;

[0591] DCI in PDCCH used to trigger non-contention-based two-step random access;

[0592] The amount of data in the second uplink;

[0593] Downlink signal quality of the reference carrier;

[0594] The uplink carrier available for MsgA in the two-step random access associated with the downlink carrier with the highest downlink signal quality.

[0595] In some embodiments, the first uplink information is uplink information for transmitting data in an idle state or a deactivated state, and the uplink information for transmitting data in an idle state or a deactivated state is uplink transmission on a configured authorized CG resource;

[0596] The target uplink carrier is determined based on at least one of the following:

[0597] The identifier of the wireless communication device 300;

[0598] Paging messages sent by network-side devices;

[0599] Default uplink carrier;

[0600] The uplink carrier associated with the downlink carrier corresponding to the SSB transmission used for synchronization;

[0601] The amount of data to be transmitted;

[0602] The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

[0603] In some embodiments, the first downlink information is downlink information for transmitting data in an idle state or a deactivated state, and the downlink information for transmitting data in an idle state or a deactivated state is message 4Msg4 in four-step random access, and the Msg4 in four-step random access includes the first downlink data.

[0604] The target downlink carrier is determined based on at least one of the following:

[0605] The identifier of the wireless communication device 300;

[0606] Paging messages sent by network-side devices;

[0607] The downlink carrier available for Msg4 in the four-step random access;

[0608] The downlink carrier corresponding to the RAR transmission in the four-step random access;

[0609] The downlink carrier indicated in the RAR during four-step random access;

[0610] In the four-step random access, the downlink carrier associated with the uplink carrier corresponding to the Msg3 transmission;

[0611] The downlink carrier corresponding to the SSB used for synchronization;

[0612] The data volume of the first downlink data;

[0613] Reference carrier;

[0614] Default downlink carrier;

[0615] The downlink carrier with the highest signal quality;

[0616] The downlink carrier with the highest average signal quality.

[0617] In some embodiments, the first downlink information is downlink information for transmitting data in an idle state or a deactivated state, and the downlink information for transmitting data in an idle state or a deactivated state is message B MsgB in two-step random access, and the MsgB in two-step random access includes second downlink data.

[0618] The target downlink carrier is determined based on at least one of the following:

[0619] The identifier of the wireless communication device 300;

[0620] Paging messages sent by network-side devices;

[0621] The downlink carrier corresponding to the SSB transmission used for synchronization;

[0622] The amount of data in the second downlink data;

[0623] The downlink carrier available for MsgB in the two-step random access;

[0624] The downlink carrier associated with the uplink carrier in the MsgA transmission during two-step random access;

[0625] The downlink carrier indicated in MsgA during two-step random access;

[0626] Reference carrier;

[0627] Default downlink carrier;

[0628] The downlink carrier with the highest signal quality;

[0629] The downlink carrier with the highest average signal quality.

[0630] In some embodiments, the first uplink information is uplink information during LTM handover, and the uplink information during LTM handover includes at least one of the following: information for uplink synchronization, uplink transmission on configuration authorized CG resources, physical random access channel PRACH in four-step random access, Msg3 in four-step random access, uplink messages after Msg4 in four-step random access, and MsgA in two-step random access.

[0631] The target uplink carrier is determined based on at least one of the following:

[0632] The identifier of the wireless communication device 300;

[0633] Paging messages sent by network-side devices;

[0634] Default uplink carrier;

[0635] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0636] The LTM switching command indicates;

[0637] The uplink carrier available for the uplink information during the LTM handover;

[0638] The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

[0639] In some embodiments, the first downlink information is downlink information in LTM handover, and the downlink information in LTM handover includes at least one of the following: LTM handover command, random access response (RAR) in four-step random access, Msg4 in four-step random access, and MsgB in two-step random access.

[0640] The target downlink carrier is determined based on at least one of the following:

[0641] The identifier of the wireless communication device 300;

[0642] Paging messages sent by network-side devices;

[0643] Default downlink carrier;

[0644] The downlink carrier corresponding to the SSB used for synchronization;

[0645] The LTM switching command indicates;

[0646] LTM handover command transmission corresponds to the downlink carrier;

[0647] The uplink carrier available for the downlink information during the LTM handover;

[0648] The downlink carrier with the highest downlink signal quality;

[0649] The downlink carrier with the highest average signal quality.

[0650] In some embodiments, the first uplink information is uplink information during a handover without random access, and the uplink information during a handover without random access is the Configuration Grant Physical Uplink Shared Channel (CG PUSCH).

[0651] The target uplink carrier is determined based on at least one of the following:

[0652] The identifier of the wireless communication device 300;

[0653] Paging messages sent by network-side devices;

[0654] Default uplink carrier;

[0655] The uplink carrier available for the CG PUSCH;

[0656] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0657] The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

[0658] In some embodiments, the SSB index associated with the uplink carrier corresponding to the initial transmission of the CG PUSCH is the same as the SSB index associated with the uplink carrier corresponding to the retransmission of the CG PUSCH, or the SSB index associated with the uplink carrier corresponding to the initial transmission of the CG PUSCH is associated with the SSB index associated with the uplink carrier corresponding to the retransmission of the CG PUSCH.

[0659] In some embodiments, if the SSB index associated with the uplink carrier corresponding to the initial transmission of the CG PUSCH is the same as the SSB index associated with the uplink carrier corresponding to the retransmission of the CG PUSCH, the retransmission resources on the uplink carrier corresponding to the retransmission of the CG PUSCH are valid; and / or, if the SSB index associated with the uplink carrier corresponding to the initial transmission of the CG PUSCH is associated with the SSB index associated with the uplink carrier corresponding to the retransmission of the CG PUSCH, the retransmission resources on the uplink carrier corresponding to the retransmission of the CG PUSCH are valid.

[0660] And / or,

[0661] The uplink carrier corresponding to the initial transmission of the CG PUSCH is the same as the uplink carrier corresponding to the retransmission of the CG PUSCH, or the uplink carrier corresponding to the initial transmission of the CG PUSCH is different from the uplink carrier corresponding to the retransmission of the CG PUSCH.

[0662] In some embodiments, the first uplink information is uplink information during a handover without random access, and the uplink information during a handover without random access is the Dynamically Authorized Physical Uplink Shared Channel (DG PUSCH).

[0663] The target uplink carrier is determined based on at least one of the following:

[0664] The identifier of the wireless communication device 300;

[0665] Paging messages sent by network-side devices;

[0666] Default uplink carrier;

[0667] The uplink carrier available for the DG PUSCH;

[0668] The uplink carrier indicated by the Radio Resource Control (RRC) reconfiguration message;

[0669] The uplink carrier indicated by the physical downlink control channel PDCCH used to schedule the DG PUSCH;

[0670] The uplink carrier associated with the downlink carrier corresponding to the DG PUSCH is used to schedule the DG PUSCH.

[0671] The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization;

[0672] The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

[0673] In some embodiments, the sending module 302 is further configured to send third information;

[0674] The third information is used to indicate whether the wireless communication device 300 supports data transmission based on multiple carriers or multiple carrier groups in idle or deactivated states; or, the third information is used to indicate whether the wireless communication device 300 supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during LTM handover; or, the third information is used to indicate whether the wireless communication device 300 supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during handover without random access.

[0675] Referring to Figure 7, when the wireless communication device is a network-side device or a component in a network-side device, the wireless communication device 400 includes: a transmitting module 401 and a receiving module 402;

[0676] The sending module 401 is used to send first information to the terminal; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0677] The receiving module 402 is used to receive first uplink information; wherein the first uplink information is transmitted based on a target uplink carrier, and the target uplink carrier is determined based on the first information; wherein the first uplink information is uplink information of a terminal transmitting data in an idle state or a deactivated state, or, the first uplink information is uplink information in a mobility LTM handover triggered by Layer 1 / Layer 2, or, the first uplink information is uplink information in a handover without random access;

[0678] And / or,

[0679] The sending module 401 is used to send first downlink information to the terminal; wherein the first downlink information is sent based on a target downlink carrier, and the target downlink carrier is determined based on the first information; wherein the first downlink information is downlink information for receiving data by the terminal in an idle state or a deactivated state, or the first downlink information is downlink information during LTM handover, or the first downlink information is downlink information during handover without random access.

[0680] In some embodiments, the target uplink carrier is determined from a target uplink carrier group in the at least one uplink carrier group, or the target uplink carrier is determined from the at least two uplink carriers;

[0681] And / or,

[0682] The target downlink carrier is determined from a target downlink carrier group in the at least one downlink carrier group, or the target downlink carrier is determined from the at least two downlink carriers.

[0683] In some embodiments, the first information includes the association between the uplink carrier group and the downlink carrier group;

[0684] In this context, a downlink carrier group is associated with one or more uplink carrier groups; and / or, an uplink carrier group is associated with one or more downlink carrier groups.

[0685] In some embodiments, the downlink carriers within each downlink carrier group of the at least one downlink carrier group satisfy at least one of the following conditions:

[0686] Some or all of the downlink carriers correspond to the same synchronization signal block (SSB) index;

[0687] There is a correlation between the SSB indices corresponding to some or all downlink carriers;

[0688] The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB.

[0689] or,

[0690] The downlink carrier group in the at least one downlink carrier group satisfies at least one of the following conditions:

[0691] Some or all downlink carrier groups correspond to the same SSB index;

[0692] There is a correlation between the SSB indices corresponding to some or all downlink carrier groups;

[0693] or,

[0694] The downlink carriers of the at least two downlink carriers satisfy at least one of the following conditions:

[0695] Some or all downlink carriers correspond to the same SSB index;

[0696] There is a correlation between the SSB indices corresponding to some or all downlink carriers;

[0697] The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB.

[0698] In some embodiments, the downlink carriers within each downlink carrier group of the at least one downlink carrier group satisfy at least one of the following conditions:

[0699] A downlink carrier's SSB index is associated with one or more uplink carriers' random access opportunities (ROs).

[0700] An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices;

[0701] An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers;

[0702] A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers;

[0703] A downlink carrier's corresponding SSB index is associated with one or more uplink carrier configuration authorization CG resources;

[0704] A CG resource for an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers;

[0705] or,

[0706] The downlink carrier group in the at least one downlink carrier group satisfies at least one of the following conditions:

[0707] An SSB index corresponding to a downlink carrier group is associated with one or more ROs corresponding to uplink carrier groups.

[0708] An RO corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups.

[0709] An SSB index corresponding to a downlink carrier group is associated with one or more random access preambles corresponding to uplink carrier groups.

[0710] A random access preamble corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups;

[0711] An SSB index corresponding to a downlink carrier group is associated with CG resources of one or more uplink carrier groups;

[0712] A CG resource for an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups;

[0713] or,

[0714] The downlink carriers of the at least two downlink carriers satisfy at least one of the following conditions:

[0715] An SSB index corresponding to a downlink carrier is associated with one or more ROs corresponding to uplink carriers.

[0716] An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices;

[0717] An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers;

[0718] A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers;

[0719] An SSB index corresponding to a downlink carrier is associated with one or more CG resources of uplink carriers;

[0720] An uplink carrier's CG resource is associated with one or more downlink carriers' corresponding SSB indices.

[0721] In some embodiments, when an SSB index corresponding to a downlink carrier is associated with ROs corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier is associated with random access preambles corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier is associated with CG resources of multiple uplink carriers, the multiple uplink carriers are uplink carriers for uplink repetitive transmission.

[0722] or,

[0723] When an SSB index corresponding to a downlink carrier group is associated with ROs corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier group is associated with random access preambles corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier group is associated with CG resources of multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission.

[0724] In some embodiments, the sending module 401 is further configured to send second information to the terminal;

[0725] The second information includes at least one of the following:

[0726] The conditions that the downlink carriers in each downlink carrier group of the at least one downlink carrier group satisfy;

[0727] The conditions that the downlink carrier groups in the at least one downlink carrier group satisfy;

[0728] The conditions that the downlink carriers of the at least two downlink carriers satisfy.

[0729] In some embodiments, repeated transmission of the first uplink information corresponds to the same uplink carrier or the same uplink carrier group, or repeated transmission of the first uplink information corresponds to different uplink carriers or different uplink carrier groups.

[0730] And / or,

[0731] The repeated transmission of the first downlink information corresponds to the same downlink carrier or the same downlink carrier group, or the repeated transmission of the first downlink information corresponds to different downlink carriers or different downlink carrier groups.

[0732] In some embodiments, the uplink transmission following the first uplink information corresponds to the same uplink carrier or the same uplink carrier group as the transmission of the first uplink information; or, the uplink transmission following the first uplink information corresponds to different uplink carriers or different uplink carrier groups as the transmission of the first uplink information.

[0733] And / or,

[0734] The downlink transmission following the first downlink information corresponds to the same downlink carrier or the same downlink carrier group as the transmission of the first downlink information, or the downlink transmission following the first downlink information corresponds to a different downlink carrier or a different downlink carrier group than the transmission of the first downlink information.

[0735] In some embodiments, the receiving module 402 is further configured to receive third information;

[0736] The third information is used to indicate whether the terminal supports data transmission based on multiple carriers or multiple carrier groups in idle or deactivated states, or whether the third information is used to indicate whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during LTM handover, or whether the third information is used to indicate whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during handover without random access.

[0737] Therefore, in this embodiment, the terminal determines a target uplink carrier based on the first information, and the terminal sends first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by the terminal in an idle state or a deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or, the terminal determines a target downlink carrier based on the first information, and the terminal receives first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information for data reception by the terminal in an idle state or a deactivated state, or, the first uplink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access. Specifically, for processes such as SDT, RACH-less handover, and LTM handover, the target uplink carrier can be flexibly adjusted within the uplink carrier group or at least two uplink carriers, and / or the target downlink carrier can be flexibly adjusted within the downlink carrier group or at least two downlink carriers. While ensuring uplink and downlink transmission coverage, this helps to achieve better load balancing, reduce inter-carrier interference, and improve the performance of processes such as SDT, RACH-less handover, and LTM handover.

[0738] The wireless communication 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.

[0739] As shown in Figure 8, this application embodiment also provides a communication device 500, including a processor 501 and a memory 502, wherein the memory 502 stores a program or instructions that can be run on the processor 501.

[0740] Optionally, when the communication device 500 is a terminal, the program or instructions executed by the processor 501 implement the various steps executed by the terminal in the above wireless communication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0741] Optionally, when the communication device 500 is a network-side device, the program or instructions executed by the processor 501 implement the various steps executed by the network-side device in the above wireless communication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0742] 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 FIG3. The 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 the terminal embodiment and achieve the same technical effect. The terminal may be the wireless communication device 300 shown in FIG6.

[0743] Specifically, Figure 9 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0744] The terminal 600 includes, but is not limited to, at least some of the following components: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

[0745] Those skilled in the art will understand that terminal 600 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 610 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 9 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.

[0746] It should be understood that, in this embodiment, the input unit 604 may include a graphics processor 6041 and a microphone 6042. The graphics processor 6041 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 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

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

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

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

[0750] In some embodiments, the processor 610 or the radio frequency unit 601 is configured to acquire first information; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0751] The processor 610 is further configured to determine a target uplink carrier based on the first information, and the radio frequency unit 601 is further configured to transmit first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by a terminal in an idle state or a deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or,

[0752] The processor 610 is further configured to determine a target downlink carrier based on the first information, and the radio frequency unit 601 is further configured to receive first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information of data received by a terminal in an idle state or a deactivated state, or, the first uplink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access.

[0753] Therefore, in this embodiment, the terminal determines a target uplink carrier based on the first information, and the terminal sends first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by the terminal in an idle state or a deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or, the terminal determines a target downlink carrier based on the first information, and the terminal receives first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information for data reception by the terminal in an idle state or a deactivated state, or, the first uplink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access. Specifically, for processes such as SDT, RACH-less handover, and LTM handover, the target uplink carrier can be flexibly adjusted within the uplink carrier group or at least two uplink carriers, and / or the target downlink carrier can be flexibly adjusted within the downlink carrier group or at least two downlink carriers. While ensuring uplink and downlink transmission coverage, this helps to achieve better load balancing, reduce inter-carrier interference, and improve the performance of processes such as SDT, RACH-less handover, and LTM handover.

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

[0755] This application also provides a network-side 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 of the method embodiment shown in FIG3. This network-side device embodiment corresponds to the method embodiment executed by the above-described network-side device. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0756] This application also provides a network-side device, which may be the wireless communication device 400 shown in FIG7.

[0757] Specifically, as shown in Figure 10, the network-side device 700 includes: an antenna 71, a radio frequency (RF) device 72, a baseband device 73, a processor 74, and a memory 75. The antenna 71 is connected to the RF device 72. In the uplink direction, the RF device 72 receives information through the antenna 71 and sends the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes the information to be transmitted and sends it to the RF device 72. The RF device 72 processes the received information and then transmits it through the antenna 71.

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

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

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

[0761] Specifically, the network-side device 700 in this application embodiment further includes: instructions or programs stored in memory 75 and executable on processor 74. Processor 74 calls the instructions or programs in memory 75 to execute the methods executed by each module shown in FIG7 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0762] In some embodiments, the radio frequency device 72 is configured to: send first information to a terminal; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers;

[0763] The radio frequency device 72 is further configured to receive first uplink information; wherein the first uplink information is transmitted based on a target uplink carrier, and the target uplink carrier is determined based on the first information; wherein the first uplink information is uplink information transmitting data in an idle state or a deactivated state, or, the first uplink information is uplink information during LTM handover, or, the first uplink information is uplink information during handover without random access; and / or,

[0764] The radio frequency device 72 is further configured to send first downlink information to the terminal; wherein the first downlink information is sent based on a target downlink carrier, and the target downlink carrier is determined based on the first information; wherein the first downlink information is downlink information transmitting data in an idle state or a deactivated state, or the first uplink information is downlink information during LTM handover, or the first downlink information is downlink information during handover without random access.

[0765] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described wireless communication method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

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

[0767] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described wireless communication method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0769] 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 wireless communication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0770] 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 performed by the terminal in the wireless communication method described above, and the network-side device can be used to perform the steps performed by the network-side device in the wireless communication method described above.

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

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

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

Claims

1. A wireless communication method, wherein, include: The terminal acquires first information; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers; The terminal determines a target uplink carrier based on the first information, and the terminal transmits first uplink information based on the target uplink carrier; wherein, the first uplink information is uplink information for data transmission by the terminal in an idle state or a deactivated state, or, the first uplink information is uplink information during a Layer 1 / Layer 2 triggered mobility LTM handover, or, the first uplink information is uplink information during a handover without random access; and / or, The terminal determines a target downlink carrier based on the first information, and the terminal receives first downlink information based on the target downlink carrier; wherein, the first downlink information is downlink information of data received by the terminal in an idle state or a deactivated state, or, the first downlink information is downlink information during LTM handover, or, the first downlink information is downlink information during handover without random access.

2. The method according to claim 1, wherein, The terminal determines the target uplink carrier based on the first information, including: The terminal determines a target uplink carrier group from the at least one uplink carrier group, and the terminal determines the target uplink carrier from the target uplink carrier group; or, The terminal determines the target uplink carrier from the at least two uplink carriers; And / or, The terminal determines the target downlink carrier based on the first information, including: The terminal determines a target downlink carrier group from the at least one downlink carrier group, and the terminal determines the target downlink carrier from the target downlink carrier group; or, The terminal determines the target downlink carrier from the at least two downlink carriers.

3. The method according to claim 1 or 2, wherein, A downlink carrier group is associated with one or more uplink carrier groups; and / or, An uplink carrier group is associated with one or more downlink carrier groups.

4. The method according to claim 3, wherein, The first information includes the correlation between the uplink carrier group and the downlink carrier group; or, The association between the uplink carrier group and the downlink carrier group is determined based on at least one of the following: Frequency band, frequency band combination, spectrum range, bandwidth portion (BWP).

5. The method according to any one of claims 1 to 4, wherein, The downlink carriers within each of the at least one downlink carrier group satisfy at least one of the following conditions: Some or all of the downlink carriers correspond to the same synchronization signal block (SSB) index; There is a correlation between the SSB indices corresponding to some or all downlink carriers; The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB. or, The downlink carrier group in the at least one downlink carrier group satisfies at least one of the following conditions: Some or all downlink carrier groups correspond to the same SSB index; There is a correlation between the SSB indices corresponding to some or all downlink carrier groups; or, The downlink carriers of the at least two downlink carriers satisfy at least one of the following conditions: Some or all downlink carriers correspond to the same SSB index; There is a correlation between the SSB indices corresponding to some or all downlink carriers; The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB.

6. The method according to any one of claims 1 to 5, wherein, The downlink carriers within each of the at least one downlink carrier group satisfy at least one of the following conditions: A downlink carrier's SSB index is associated with one or more uplink carriers' random access opportunities (ROs). An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices; An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers; A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers; A downlink carrier's corresponding SSB index is associated with one or more uplink carrier configuration authorization CG resources; A CG resource for an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers; or, The downlink carrier group in the at least one downlink carrier group satisfies at least one of the following conditions: An SSB index corresponding to a downlink carrier group is associated with one or more ROs corresponding to uplink carrier groups. An RO corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups. An SSB index corresponding to a downlink carrier group is associated with one or more random access preambles corresponding to uplink carrier groups. A random access preamble corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups; An SSB index corresponding to a downlink carrier group is associated with CG resources of one or more uplink carrier groups; A CG resource for an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups; or, The downlink carriers of the at least two downlink carriers satisfy at least one of the following conditions: An SSB index corresponding to a downlink carrier is associated with one or more ROs corresponding to uplink carriers. An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices; An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers; A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers; An SSB index corresponding to a downlink carrier is associated with one or more CG resources of uplink carriers; An uplink carrier's CG resource is associated with one or more downlink carriers' corresponding SSB indices.

7. The method according to claim 6, wherein, When an SSB index corresponding to a downlink carrier is associated with ROs corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier is associated with random access preambles corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier is associated with CG resources of multiple uplink carriers, the multiple uplink carriers are uplink carriers used for uplink repetitive transmission. or, When an SSB index corresponding to a downlink carrier group is associated with ROs corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier group is associated with random access preambles corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier group is associated with CG resources of multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission.

8. The method according to any one of claims 5 to 7, wherein, The method further includes: The terminal receives second information; wherein the second information includes at least one of the following: The conditions that the downlink carriers in each downlink carrier group of the at least one downlink carrier group satisfy; The conditions that the downlink carrier groups in the at least one downlink carrier group satisfy; The conditions that the downlink carriers of the at least two downlink carriers satisfy.

9. The method according to any one of claims 1 to 8, wherein, The repeated transmission of the first uplink information corresponds to the same uplink carrier or the same uplink carrier group, or the repeated transmission of the first uplink information corresponds to different uplink carriers or different uplink carrier groups. And / or, The repeated transmission of the first downlink information corresponds to the same downlink carrier or the same downlink carrier group, or the repeated transmission of the first downlink information corresponds to different downlink carriers or different downlink carrier groups.

10. The method according to claim 9, wherein, The uplink transmissions following the first uplink information correspond to the same uplink carrier or the same uplink carrier group as the transmission of the first uplink information; or, the uplink transmissions following the first uplink information correspond to different uplink carriers or different uplink carrier groups than the transmission of the first uplink information. And / or, The downlink transmission following the first downlink information corresponds to the same downlink carrier or the same downlink carrier group as the transmission of the first downlink information, or the downlink transmission following the first downlink information corresponds to a different downlink carrier or a different downlink carrier group than the transmission of the first downlink information.

11. The method according to any one of claims 1 to 10, wherein, The first uplink information is uplink information that transmits data in an idle state or a deactivated state. The uplink information that transmits data in an idle state or a deactivated state is message 3Msg3 in the four-step random access. The Msg3 in the four-step random access includes the first uplink data. The target uplink carrier is determined based on at least one of the following: The identifier of the terminal; Paging messages sent by network-side devices; Default uplink carrier; The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization; The data volume of the first uplink data; The uplink carrier corresponding to the resources of the random access preamble in the four-step random access; The uplink carrier identified by the random access preamble in the four-step random access process; The uplink carrier available for Msg3 in the four-step random access; The uplink carrier indicated in the RAR during four-step random access; The uplink carrier corresponding to the PRACH transmission in the four-step random access process.

12. The method according to any one of claims 1 to 10, wherein, The first uplink information is uplink information transmitting data in an idle state or a deactivated state. The uplink information transmitting data in an idle state or a deactivated state is message A MsgA in a two-step random access, and MsgA in the two-step random access includes the second uplink data. The target uplink carrier is determined based on at least one of the following: The identifier of the terminal; Paging messages sent by network-side devices; Default uplink carrier; The uplink carrier associated with the downlink carrier corresponding to the SSB transmission used for synchronization; The uplink carrier available for MsgA in the two-step random access; DCI in PDCCH used to trigger non-contention-based two-step random access; The amount of data in the second uplink; Downlink signal quality of the reference carrier; The uplink carrier available for MsgA in the two-step random access associated with the downlink carrier with the highest downlink signal quality.

13. The method according to any one of claims 1 to 10, wherein, The first uplink information is uplink information that transmits data in an idle state or a deactivated state, and the uplink information that transmits data in an idle state or a deactivated state is uplink transmission on the configured authorized CG resource; The target uplink carrier is determined based on at least one of the following: The identifier of the terminal; Paging messages sent by network-side devices; Default uplink carrier; The uplink carrier associated with the downlink carrier corresponding to the SSB transmission used for synchronization; The amount of data to be transmitted; The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

14. The method according to any one of claims 1 to 10, wherein, The first downlink information is downlink information transmitting data in an idle state or a deactivated state. The downlink information transmitting data in an idle state or a deactivated state is message 4Msg4 in the four-step random access, and Msg4 in the four-step random access includes the first downlink data. The target downlink carrier is determined based on at least one of the following: The identifier of the terminal; Paging messages sent by network-side devices; The downlink carrier available for Msg4 in the four-step random access; The downlink carrier corresponding to the RAR transmission in the four-step random access; The downlink carrier indicated in the RAR during four-step random access; In the four-step random access, the downlink carrier associated with the uplink carrier corresponding to the Msg3 transmission; The downlink carrier corresponding to the SSB used for synchronization; The amount of data in the first downlink data; Reference carrier; Default downlink carrier; The downlink carrier with the highest signal quality; The downlink carrier with the highest average signal quality.

15. The method according to any one of claims 1 to 10, wherein, The first downlink information is downlink information for transmitting data in an idle state or a deactivated state. The downlink information for transmitting data in an idle state or a deactivated state is message B MsgB in two-step random access, and MsgB in two-step random access includes the second downlink data. The target downlink carrier is determined based on at least one of the following: The identifier of the terminal; Paging messages sent by network-side devices; The downlink carrier corresponding to the SSB transmission used for synchronization; The amount of data in the second downlink data; The downlink carrier available for MsgB in the two-step random access; The downlink carrier associated with the uplink carrier in the MsgA transmission during two-step random access; The downlink carrier indicated in MsgA during two-step random access; Reference carrier; Default downlink carrier; The downlink carrier with the highest signal quality; The downlink carrier with the highest average signal quality.

16. The method according to any one of claims 1 to 10, wherein, The first uplink information is the uplink information in LTM handover, and the uplink information in LTM handover includes at least one of the following: information for uplink synchronization, uplink transmission on configuration authorized CG resources, physical random access channel PRACH in four-step random access, Msg3 in four-step random access, uplink messages after Msg4 in four-step random access, and MsgA in two-step random access. The target uplink carrier is determined based on at least one of the following: The identifier of the terminal; Paging messages sent by network-side devices; Default uplink carrier; The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization; The LTM switching command indicates; The uplink carrier available for the uplink information during the LTM handover; The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

17. The method according to any one of claims 1 to 10, wherein, The first downlink information is downlink information in LTM handover, which includes at least one of the following: LTM handover command, random access response (RAR) in four-step random access, Msg4 in four-step random access, and MsgB in two-step random access; The target downlink carrier is determined based on at least one of the following: The identifier of the terminal; Paging messages sent by network-side devices; Default downlink carrier; The downlink carrier corresponding to the SSB used for synchronization; The LTM switching command indicates; LTM handover command transmission corresponds to the downlink carrier; The uplink carrier available for the downlink information during the LTM handover; The downlink carrier with the highest downlink signal quality; The downlink carrier with the highest average signal quality.

18. The method according to any one of claims 1 to 10, wherein, The first uplink information is uplink information during a handover without random access, and the uplink information during a handover without random access is the Configuration Grant Physical Uplink Shared Channel (CG PUSCH). The target uplink carrier is determined based on at least one of the following: The identifier of the terminal; Paging messages sent by network-side devices; Default uplink carrier; The uplink carrier available for the CG PUSCH; The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization; The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

19. The method according to claim 18, wherein, The SSB index associated with the uplink carrier for the initial transmission of the CG PUSCH is the same as the SSB index associated with the uplink carrier for the retransmission of the CG PUSCH, or the SSB index associated with the uplink carrier for the initial transmission of the CG PUSCH is associated with the SSB index associated with the uplink carrier for the retransmission of the CG PUSCH.

20. The method according to claim 18 or 19, wherein, If the SSB index associated with the uplink carrier corresponding to the initial transmission of the CG PUSCH is the same as the SSB index associated with the uplink carrier corresponding to the retransmission of the CG PUSCH, the retransmission resources on the uplink carrier corresponding to the retransmission of the CG PUSCH are valid; and / or, if the SSB index associated with the uplink carrier corresponding to the initial transmission of the CG PUSCH is associated with the SSB index associated with the uplink carrier corresponding to the retransmission of the CG PUSCH, the retransmission resources on the uplink carrier corresponding to the retransmission of the CG PUSCH are valid. And / or, The uplink carrier corresponding to the initial transmission of the CG PUSCH is the same as the uplink carrier corresponding to the retransmission of the CG PUSCH, or the uplink carrier corresponding to the initial transmission of the CG PUSCH is different from the uplink carrier corresponding to the retransmission of the CG PUSCH.

21. The method according to any one of claims 1 to 10, wherein, The first uplink information is uplink information during a handover without random access, and the uplink information during a handover without random access is the Dynamically Authorized Physical Uplink Shared Channel (DG PUSCH). The target uplink carrier is determined based on at least one of the following: The identifier of the terminal; Paging messages sent by network-side devices; Default uplink carrier; The uplink carrier available for the DG PUSCH; The uplink carrier indicated by the Radio Resource Control (RRC) reconfiguration message; The uplink carrier indicated by the physical downlink control channel PDCCH used to schedule the DG PUSCH; The uplink carrier associated with the downlink carrier corresponding to the DG PUSCH is used to schedule the DG PUSCH. The uplink carrier associated with the downlink carrier corresponding to the SSB used for synchronization; The uplink carrier associated with the downlink carrier with the highest downlink signal quality.

22. The method according to any one of claims 1 to 21, wherein, The method further includes: The terminal sends third information; The third information is used to indicate whether the terminal supports data transmission based on multiple carriers or multiple carrier groups in idle or deactivated states, or whether the third information is used to indicate whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during LTM handover, or whether the third information is used to indicate whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during handover without random access.

23. A wireless communication method, wherein, include: The network-side device sends first information to the terminal; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers; The network-side device receives first uplink information; wherein the first uplink information is transmitted based on a target uplink carrier, and the target uplink carrier is determined based on the first information; wherein the first uplink information is uplink information for data transmission by a terminal in an idle or deactivated state, or, the first uplink information is uplink information during a Layer 1 / Layer 2 triggered mobility LTM handover, or, the first uplink information is uplink information during a handover without random access; And / or, The network-side device sends first downlink information to the terminal; wherein the first downlink information is sent based on a target downlink carrier, and the target downlink carrier is determined based on the first information; wherein the first downlink information is downlink information for data received by the terminal in an idle state or a deactivated state, or the first downlink information is downlink information during LTM handover, or the first downlink information is downlink information during handover without random access.

24. The method according to claim 23, wherein, The target uplink carrier is determined from the target uplink carrier group in the at least one uplink carrier group, or the target uplink carrier is determined from the at least two uplink carriers; And / or, The target downlink carrier is determined from a target downlink carrier group in the at least one downlink carrier group, or the target downlink carrier is determined from the at least two downlink carriers.

25. The method according to claim 23 or 24, wherein, The first information includes the correlation between the uplink carrier group and the downlink carrier group; In this context, a downlink carrier group is associated with one or more uplink carrier groups; and / or, an uplink carrier group is associated with one or more downlink carrier groups.

26. The method according to any one of claims 23 to 25, wherein, The downlink carriers within each of the at least one downlink carrier group satisfy at least one of the following conditions: Some or all of the downlink carriers correspond to the same synchronization signal block (SSB) index; There is a correlation between the SSB indices corresponding to some or all downlink carriers; The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB. or, The downlink carrier group in the at least one downlink carrier group satisfies at least one of the following conditions: Some or all downlink carrier groups correspond to the same SSB index; There is a correlation between the SSB indices corresponding to some or all downlink carrier groups; or, The downlink carriers of the at least two downlink carriers satisfy at least one of the following conditions: Some or all downlink carriers correspond to the same SSB index; There is a correlation between the SSB indices corresponding to some or all downlink carriers; The SSB index corresponding to the downlink carrier that has not transmitted SSB is multiplexed with the SSB index corresponding to the downlink carrier that has transmitted SSB.

27. The method according to any one of claims 23 to 26, wherein, The downlink carriers within each of the at least one downlink carrier group satisfy at least one of the following conditions: A downlink carrier's SSB index is associated with one or more uplink carriers' random access opportunities (ROs). An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices; An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers; A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers; A downlink carrier's corresponding SSB index is associated with one or more uplink carrier configuration authorization CG resources; A CG resource for an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers; or, The downlink carrier group in the at least one downlink carrier group satisfies at least one of the following conditions: An SSB index corresponding to a downlink carrier group is associated with one or more ROs corresponding to uplink carrier groups. An RO corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups. An SSB index corresponding to a downlink carrier group is associated with one or more random access preambles corresponding to uplink carrier groups. A random access preamble corresponding to an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups; An SSB index corresponding to a downlink carrier group is associated with CG resources of one or more uplink carrier groups; A CG resource for an uplink carrier group is associated with one or more SSB indices corresponding to downlink carrier groups; or, The downlink carriers of the at least two downlink carriers satisfy at least one of the following conditions: An SSB index corresponding to a downlink carrier is associated with one or more ROs corresponding to uplink carriers. An uplink carrier's corresponding RO is associated with one or more downlink carriers' corresponding SSB indices; An SSB index corresponding to a downlink carrier is associated with one or more random access preambles corresponding to uplink carriers; A random access preamble corresponding to an uplink carrier is associated with one or more SSB indices corresponding to downlink carriers; An SSB index corresponding to a downlink carrier is associated with one or more CG resources of uplink carriers; An uplink carrier's CG resource is associated with one or more downlink carriers' corresponding SSB indices.

28. The method according to claim 27, wherein, When an SSB index corresponding to a downlink carrier is associated with ROs corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier is associated with random access preambles corresponding to multiple uplink carriers, the multiple uplink carriers are uplink carriers used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier is associated with CG resources of multiple uplink carriers, the multiple uplink carriers are uplink carriers used for uplink repetitive transmission. or, When an SSB index corresponding to a downlink carrier group is associated with ROs corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier group is associated with random access preambles corresponding to multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission; and / or, when an SSB index corresponding to a downlink carrier group is associated with CG resources of multiple uplink carrier groups, the multiple uplink carrier groups are uplink carrier groups used for uplink repetitive transmission.

29. The method according to any one of claims 26 to 28, wherein, The method further includes: The network-side device sends the second information to the terminal; The second information includes at least one of the following: The conditions that the downlink carriers in each downlink carrier group of the at least one downlink carrier group satisfy; The conditions that the downlink carrier groups in the at least one downlink carrier group satisfy; The conditions that the downlink carriers of the at least two downlink carriers satisfy.

30. The method according to any one of claims 23 to 29, wherein, The repeated transmission of the first uplink information corresponds to the same uplink carrier or the same uplink carrier group, or the repeated transmission of the first uplink information corresponds to different uplink carriers or different uplink carrier groups. And / or, The repeated transmission of the first downlink information corresponds to the same downlink carrier or the same downlink carrier group, or the repeated transmission of the first downlink information corresponds to different downlink carriers or different downlink carrier groups.

31. The method according to claim 30, wherein, The uplink transmissions following the first uplink information correspond to the same uplink carrier or the same uplink carrier group as the transmission of the first uplink information; or, the uplink transmissions following the first uplink information correspond to different uplink carriers or different uplink carrier groups than the transmission of the first uplink information. And / or, The downlink transmission following the first downlink information corresponds to the same downlink carrier or the same downlink carrier group as the transmission of the first downlink information, or the downlink transmission following the first downlink information corresponds to a different downlink carrier or a different downlink carrier group than the transmission of the first downlink information.

32. The method according to any one of claims 23 to 31, wherein, The method further includes: The network-side device receives third information; The third information is used to indicate whether the terminal supports data transmission based on multiple carriers or multiple carrier groups in idle or deactivated states, or whether the third information is used to indicate whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during LTM handover, or whether the third information is used to indicate whether the terminal supports uplink and / or downlink transmission based on multiple carriers or multiple carrier groups during handover without random access.

33. A wireless communication device, wherein, include: A processing module or a receiving module is configured to acquire first information; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers; The processing module is further configured to: determine the target uplink carrier based on the first information; The transmitting module is configured to transmit first uplink information based on the target uplink carrier; wherein the first uplink information is uplink information for data transmission by a terminal in an idle or deactivated state, or, the first uplink information is uplink information during a Layer 1 / Layer 2 triggered mobility LTM handover, or, the first uplink information is uplink information during a handover without random access; and / or, The processing module is further configured to determine the target downlink carrier based on the first information; The receiving module is further configured to receive first downlink information based on the target downlink carrier; wherein the first downlink information is downlink information of data received by a terminal in an idle state or a deactivated state, or the first downlink information is downlink information during LTM handover, or the first downlink information is downlink information during handover without random access.

34. A wireless communication device, wherein, include: A transmitting module is configured to transmit first information to a terminal; wherein the first information includes at least one of the following: at least one uplink carrier group, at least one downlink carrier group, at least two uplink carriers, and at least two downlink carriers; A receiving module is configured to receive first uplink information; wherein the first uplink information is transmitted based on a target uplink carrier, and the target uplink carrier is determined based on the first information; wherein the first uplink information is uplink information for data transmission by a terminal in an idle state or a deactivated state, or, the first uplink information is uplink information during a Layer 1 / Layer 2 triggered mobility LTM handover, or, the first uplink information is uplink information during a handover without random access; And / or, The sending module is used to send first downlink information to the terminal; wherein the first downlink information is sent based on a target downlink carrier, and the target downlink carrier is determined based on the first information; wherein the first downlink information is downlink information for receiving data by the terminal in an idle state or a deactivated state, or the first downlink information is downlink information during LTM handover, or the first downlink information is downlink information during handover without random access.

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

36. A network-side device, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the wireless communication method as described in any one of claims 23 to 32.

37. A readable storage medium, wherein, The readable storage medium stores a program or instructions that, when executed by a processor, implement the wireless communication method as described in any one of claims 1 to 22, or implement the steps of the wireless communication method as described in any one of claims 23 to 32.

Images