Downlink carrier switching method and apparatus

By maintaining information reception on the first downlink carrier during carrier switching, the problem of low random access success rate during carrier switching is solved, achieving more efficient carrier switching and information reception.

WO2026233101A1PCT designated stage Publication Date: 2026-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/091907
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-04-21
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

During carrier switching, the success rate of a terminal performing contention-based random access is low, especially when switching between the n12 and n29 frequency bands, where the terminal cannot simultaneously receive and send information, resulting in access failure.

Method used

During carrier switching, the terminal remains on the first downlink carrier to receive downlink information until the identification information is sent or the contention resolution information is received, ensuring that carrier switching is performed at the appropriate time and improving the access success rate.

Benefits of technology

By maintaining information reception on the first downlink carrier, the terminal is ensured to receive the necessary downlink information, which improves the success rate of contention-based random access and enhances the orderliness and accuracy of carrier handover.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026091907_12112026_PF_FP_ABST
    Figure CN2026091907_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the field of communications. Provided are a downlink carrier switching method and apparatus. The downlink carrier switching method comprises: during contention-based random access, before a first time (the time at which the sending of identification information of a terminal is completed, the time at which contention resolution information is received, the time at which a random access response window corresponding to downlink information ends, or the time at which a random access contention resolution timer expires), a terminal maintaining at a first downlink carrier to receive downlink information during the contention-based random access. Therefore, it is ensured that the terminal can receive the downlink information for random access instead of failing to receive the downlink information for random access due to the switching to a second downlink carrier on the basis of switching configuration information, thereby improving the success rate of the contention-based random access.
Need to check novelty before this filing date? Find Prior Art

Description

Downlink carrier switching method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 202510600346.3, filed on May 9, 2025, entitled “Downlink Carrier Switching Method and Apparatus”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and in particular to a method and apparatus for switching downlink carriers. Background Technology

[0003] With the widespread adoption of 5G, carrier aggregation (CA) technology has become a core solution for improving user transmission bandwidth and network capacity. CA technology significantly improves user experience by aggregating multiple component carriers (CCs) to integrate frequency domain resources from the same or different frequency bands for terminal use.

[0004] However, in low-frequency bands (such as those below 1 GHz), while their wide coverage supports basic communication services, the surge in data traffic leads to a shortage of frequency domain resources. Taking the n12 band as an example, its frequency division duplex (FDD) band (downlink 729-746 MHz, uplink 669-716 MHz) may already be severely congested, while the adjacent supplementary downlink (SDL) n29 band (downlink 717-728 MHz, no uplink resources) may not be fully utilized, resulting in resource waste. Although integrating the n12 and n29 bands through CA technology can theoretically alleviate congestion, this technology places high demands on the hardware capabilities of the terminal, especially relying on multi-radio frequency reception (Rx) units to achieve concurrent transmission across multiple frequency bands.

[0005] Currently, some terminals are able to switch between downlink carriers such as n12 and n29 to receive data. These terminals are called handover terminals. However, when handover terminals perform contention-based random access during carrier switching, the success rate is low. Summary of the Invention

[0006] This application provides a downlink carrier switching method and apparatus to improve the success rate of contention-based random access by a terminal during carrier switching.

[0007] To achieve the above objectives, this application adopts the following technical solution:

[0008] Firstly, a downlink carrier switching method is provided. This method is applied to a terminal, and the executing entity of the method can be the terminal, a component or device applied to the terminal (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal's functions. The downlink carrier switching method includes: receiving switching configuration information, which instructs the terminal to switch between a first downlink carrier and a second downlink carrier, wherein the first and second downlink carriers are downlink carriers in a carrier aggregation scenario; during contention-based random access, maintaining downlink information reception on the first downlink carrier until a first time; starting from or after the first time, performing carrier switching based on the switching configuration information, wherein the first time is the time when the terminal's identification information is completed, or the first time is the time when contention resolution information is received, where the terminal's identification information is used for contention resolution, or the first time is the time when the random access response window corresponding to the downlink information ends, or the time when the random access contention resolution timer expires.

[0009] In the first aspect, during contention-based random access, before the first time (the time when the terminal completes sending the identification information, the time when the contention resolution information is received, the time when the random access response window corresponding to the downlink information ends, or the time when the random access contention resolution timer expires), the terminal maintains receiving downlink information on the first downlink carrier during the contention-based random access process. This ensures that the terminal can receive the downlink information used for random access and will not fail to receive the downlink information used for random access due to switching to the second downlink carrier based on the handover configuration information, thereby improving the success rate of contention-based random access.

[0010] In one possible design, contention-based random access includes contention-based two-step random access or contention-based four-step random access.

[0011] This design supports contention-based two-step random access or contention-based four-step random access, enriching the application scenarios for carrier switching based on handover configuration information.

[0012] In one possible design, after the first time point, handover is performed based on handover configuration information, including: carrier handover starting at a second time point based on the handover configuration information, wherein the second time point is separated from the first time point by a third time point, which is a time predefined by the protocol or a time configured by the network device. Optionally, the unit of the third time point is a time slot.

[0013] In this design, by specifying a third time (e.g., in time slots) between the second and first time intervals, the terminal is ensured to perform carrier switching at appropriate times, thereby improving the orderliness and accuracy of carrier switching.

[0014] In a second aspect, a communication device is provided for implementing the method described in the first aspect. For example, the communication device may be a terminal as described in the first aspect, or a component or device applied to a terminal (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal's functions.

[0015] The communication device includes modules, units, or means corresponding to the implementation method. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0016] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations. The transceiver module, also called a transceiver unit, is used to implement the sending and / or receiving functions in any of the above aspects and any possible implementations. The transceiver module may consist of transceiver circuitry, a transceiver, a transceiver unit, or a communication interface.

[0017] In some possible designs, the transceiver module includes a sending module and / or a receiving module, which are used to implement the sending or receiving functions in any of the above aspects and any possible implementations.

[0018] Thirdly, a communication device is provided, comprising: a processor and a communication interface; the communication interface is used to communicate with a module outside the communication device; the processor is used to execute computer programs or instructions to cause the communication device to perform the method described in the first aspect. For example, the communication device may be a terminal as described in the first aspect, or a component or device applied to a terminal (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or part of the terminal functions.

[0019] Fourthly, a communication device is provided, comprising: at least one processor; the processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the method described in the first aspect. The memory may be coupled to the processor, or the memory may exist independently of the processor; for example, the memory and the processor may be two separate modules. The memory may be located outside or within the communication device.

[0020] The communication device is used to implement the method described in the first aspect. For example, the communication device can be the terminal in the first aspect, or it can be a component or device applied to the terminal (e.g., a processor, chip, or chip system), or it can be a logic module or software that can implement all or part of the terminal's functions. When the device is a chip system, it can be composed of chips or can include chips and other discrete devices.

[0021] Fifthly, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in the first aspect.

[0022] In a sixth aspect, a computer program product containing instructions is provided that, when run on a communication device, enables the communication device to perform the method described in the first aspect.

[0023] In a seventh aspect, a communication device is provided, configured to cause the communication device to perform the method described in the first aspect.

[0024] It is understandable that when the communication device provided by any of the second to fourth aspects is a chip, the sending action / function of the communication device can be understood as outputting information, and the receiving action / function of the communication device can be understood as inputting information.

[0025] Eighthly, a communication system is provided, which includes the terminal described in the preceding aspects.

[0026] The technical effects of any of the design methods in aspects two through eight can be found in the technical effects of different design methods in aspect one, and will not be repeated here. Attached Figure Description

[0027] Figure 1 is a schematic diagram of the carrier aggregation communication architecture provided in an embodiment of this application;

[0028] Figure 2 is a schematic diagram of the communication frequency bands provided in an embodiment of this application;

[0029] Figure 3 is a schematic diagram of a downlink carrier switching scenario provided in an embodiment of this application;

[0030] Figures 4 and 5 are schematic diagrams of the communication process provided in the embodiments of this application;

[0031] Figures 6 and 7 are schematic diagrams of the communication system architecture provided in the embodiments of this application;

[0032] Figure 8 is a flowchart illustrating the downlink carrier switching method provided in an embodiment of this application;

[0033] Figures 9-11 are schematic diagrams of carrier switching scenarios provided in the embodiments of this application;

[0034] Figures 12 and 13 are schematic diagrams of the structure of the communication device provided in the embodiments of this application. Detailed Implementation

[0035] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0036] Before introducing the embodiments of this application, some terms involved in the embodiments of this application will be explained.

[0037] 1. Carrier aggregation technology:

[0038] Carrier aggregation (CA) technology in New Radio (NR) is used to increase the transmission bandwidth of individual users. Specifically, CA technology improves the overall network resource utilization and enhances the user experience by integrating frequency domain resources of the same or different frequency bands for terminal use. CA technology supports greater transmission bandwidth and higher data transmission rates by aggregating two or more carriers (CCs), as shown in Figure 1. In carrier aggregation, the primary cell (PCell) (e.g., cell 1) is the primary serving cell designated by the terminal when performing initial connection establishment, radio resource control (RRC) connection reconstruction, or handover, and is responsible for RRC signaling interaction with the terminal. The carrier element corresponding to the PCell is called the primary component carrier (PCC). The downlink primary component carrier (DL PCC) refers to the downlink transmission frequency band of the PCell; the uplink primary component carrier (UL PCC) refers to the uplink transmission frequency band of the PCell.

[0039] A secondary cell (SCell) (e.g., cell 2) is added to the terminal via the RRC reconfiguration process to provide additional radio resources. The carrier element corresponding to the SCell is called a secondary component carrier (SCC). The downlink secondary component carrier (DL SCC) is the downlink transmission frequency band of the SCell; the uplink secondary component carrier (UL SCC) is the uplink transmission frequency band of the SCell.

[0040] A serving cell may contain one downlink carrier, one downlink carrier and one uplink carrier, or one downlink carrier and two uplink carriers. Therefore, a serving cell can correspond one-to-one with one downlink carrier. In other words, the concepts of carrier (unless otherwise specified, all carriers refer to downlink carriers) and cell are interchangeable in this application.

[0041] 2. Low-frequency band dynamic carrier aggregation:

[0042] Thanks to the propagation characteristics of low-frequency electromagnetic waves, operators can provide wide-coverage services. However, surges in data traffic can cause congestion in low-frequency bands, impacting user experience. Aggregating multiple low-frequency carriers using CA (Carrier Aggregator) technology can alleviate this problem.

[0043] For example, taking the background technology introduction of the n12 and n29 frequency bands as an example, as shown in Figure 2, the n12 frequency band is currently severely congested, while the n29 frequency band is not fully utilized. At this time, the two frequency bands can be combined through CA technology.

[0044] When combining the n12 and n29 frequency bands via CA technology, the configuration of PCell and PCC can include: the UE's PCell corresponds to the n12 frequency band, the DL PCC is 729MHz-746MHz, and the UL PCC is 669MHz-716MHz. The configuration of SCell and SCC can include: the UE's SCell corresponds to the n29 frequency band, and the DL SCC is 717MHz-728MHz.

[0045] 3. Downlink carrier handover mechanism of the terminal:

[0046] For some low-performance terminal devices (such as feature phones for the elderly and budget smartphones), equipped with a single RF Rx unit, they cannot simultaneously receive data in primary and secondary cells like conventional carrier aggregation technology. This forces these terminals to switch between different frequency bands to receive data, for example, alternating between the n29 band (secondary cell SCell) and the n12 band (primary cell PCell). From a network perspective, multiple users can achieve load balancing by switching frequency bands to receive data. Furthermore, because there is only a 1MHz isolation bandwidth between the n12 uplink band and the n29 downlink band, limited by the terminal's duplexer hardware performance, when a terminal switches to the n29 band to receive downlink data, it cannot simultaneously transmit uplink information on the n12 band.

[0047] Therefore, an effective multi-band utilization scheme is as follows: the terminal's Rx unit first operates in the n12 band, and then switches to the n29 band to receive downlink data according to the base station's dynamic instructions or a preset switching cycle (at which time the n12 band is suspended). After a period of time, the Rx unit switches back to the n12 band, and so on.

[0048] For example, the two downlink carriers that the terminal switches between can be carrier 1 corresponding to the n12 frequency band and carrier 2 corresponding to the n29 frequency band. As shown in Figure 3, D represents the downlink time slot and U represents the uplink time slot. According to the periodic switching configuration information, during the first time period (T1-T2), the terminal communicates through carrier 1. At this time, the first time unit is the first time period, and the first downlink carrier is carrier 1. After the first time period ends, a carrier switch (also known as Rx switch) is performed at T2. After the switch, during the second time period (T2-T3), the terminal communicates through carrier 2. At this time, the first time unit is the second time period, and the first downlink carrier is carrier 2. After the second time period ends, a carrier switch is performed at T3. After the switch, during the third time period (T3-T4), the terminal switches back to carrier 1 for communication. At this time, the first time unit is the third time period, and the first downlink carrier is carrier 1.

[0049] It is understood that the above description of carrier switching under the n12 and n29 frequency bands is for illustrative purposes only. The embodiments of this application are also applicable to other frequency band combinations, such as combinations of another FDD frequency band and SDL frequency band, combinations of FDD frequency bands, or combinations of FDD frequency bands and TDD frequency bands, etc., without limitation.

[0050] 4. Terminal Rx handover mechanism based on semi-static configuration switching mode:

[0051] In mobile communication networks, terminals can achieve efficient Rx handover based on semi-statically configured switching patterns. After a terminal accesses the network, it typically sets the FDD band as the primary cell (PCell) and the SDL band as the secondary cell (SCell). At this time, the base station will send a specific handover pattern to the terminal through Radio Resource Control (RRC) configuration messages, specifying the periodic Rx handover rules.

[0052] Taking a typical scenario as an example, the terminal will perform a switching every 40ms: first, it will work continuously on the FDD band for 30ms to complete the data reception and transmission tasks; then, within the next 10ms, it will switch Rx to the SDL band to focus on data reception on that band; after 10ms, it will quickly switch back to the FDD band to resume the transmission and reception operations on that band.

[0053] This switching mechanism has distinct operating characteristics: when the terminal is on an FDD carrier, bidirectional data transmission occurs in the FDD band, while the SDL carrier remains idle and cannot receive data; conversely, when the terminal switches to an SDL carrier, it receives data in the SDL band, and the FDD carrier's transmission and reception functions are temporarily suspended. Through this semi-static configuration and periodic switching, the terminal can flexibly allocate resources and achieve efficient collaborative operation between different frequency bands.

[0054] 5. Contention-based random access (CBRA)

[0055] 5G defines a physical random access channel (PRACH), enabling user equipment (UE) to initiate random access (RA) on specific PRACH time-frequency resources. The signal transmitted by a UE when initiating access is called a random access preamble. The random access preamble informs the base station that there is a random access request.

[0056] Random access has the following two different mechanisms:

[0057] Contention-based random access: In this random access process, the preamble is randomly selected by the user equipment from a range of common configurations. These preambles are random. In this case, different user equipment may choose conflicting preambles, and the base station needs to resolve access issues through contention. The result is random and cannot be guaranteed to be 100% successful.

[0058] Contention-free random access (CFRA): In this random access process, preambles are assigned to user equipment by the base station and are dedicated. In this case, user equipment will not experience preamble conflicts. However, when dedicated preambles are insufficient, the base station will instruct the user equipment to initiate contention-based random access.

[0059] For connected user equipment (UE), the random access mechanism and the initiator of random access can differ depending on the triggering scenario. For example, if a UE has uplink data to transmit to the base station but finds itself out of uplink synchronization, it will initiate contention-based random access, selecting a random access preamble to send to the base station. Conversely, if the base station has downlink data to transmit to the UE but finds itself out of uplink synchronization, the base station will trigger the UE to initiate random access via a physical downlink control channel order (PDCCH) (the base station sends downlink control information format 1_0, DCI format 1_0, to the UE to perform random access). This random access can be non-contention-based, meaning a random access preamble is specified in the downlink control information format 1_0, or contention-based, meaning a random access preamble is not specified in the downlink control information format 1_0.

[0060] Contention-based random access can be divided into two types: 4-step and 2-step.

[0061] As shown in Figure 4, the 4-step access process may include:

[0062] 1. The user equipment sends a random access preamble, i.e., Msg1. The user equipment can obtain the physical random access channel (PRACH) configuration from the system information block 1 (SIB1) message or the radio resource control (RRC) configuration message, randomly select a random access preamble according to the configuration, and send it on the time-frequency domain resource indicated by the configuration (denoted as the random access occasion (RACH Occasion)).

[0063] 2. The base station sends a random access response (Msg2). After sending the random access preamble, the user equipment (UE) starts a random access response window (ra-ResponseWindow). Within this window, it continuously monitors downlink control information (DCI). The base station sends downlink control information scrambled with a random access radio network temporary identifier (RA-RNTI) to indicate the physical downlink shared channel (PDSCH) resources used to carry Msg2. After receiving the downlink control information, the UE further receives Msg2. From Msg2, it can obtain information such as timing advance (TA), uplink grant (UL Grant), random access preamble identifier (RAPID), and temporary cell radio network temporary identifier (TC-RNTI). If the random access preamble identifier in Msg2 corresponds to Msg1, the UE considers the random access response successful.

[0064] a) In particular, in certain scenarios (e.g., when a user equipment requests a system message via contention-based random access (CBRA), the media access control sub-protocol data unit (MAC subPDU) carried in the random access response only contains the random access preamble identifier. In this case, the user equipment considers the system message request to be successful, ends the random access process, and does not need to continue to the contention resolution stage described below.

[0065] 3. The user equipment (UE) sends uplink scheduled transmission information (Msg3) for contention resolution. The time-frequency domain resources of Msg3 are indicated by the uplink grant in Msg2. Msg3 carries the UE's unique identifier (UE ID), which is used for further contention resolution to distinguish the UE from the base station.

[0066] 4. The base station sends a contention resolution message, Msg4, to the user equipment. After the user equipment sends Msg3, it starts a contention resolution timer. Before the contention resolution timer expires, the user equipment monitors the physical downlink control channel (PDCCH) in the common search space of the Type 1 physical downlink control channel. If the user equipment successfully resolves downlink control information using the temporary cell radio network identifier, it stops the contention resolution timer, and the random access procedure is considered to have been successfully completed. Otherwise, the random access procedure restarts from step one.

[0067] As shown in Figure 5, the 2-step access process may include:

[0068] 1. The User Equipment (UE) sends MsgA. The first message the UE sends to the base station (gNB) is MsgA. Unlike the traditional 4-step CBRA, MsgA contains both the random access preamble and the data carried on the Physical Uplink Shared Channel (PUSCH payload). The UE sends this MsgA on appropriate time-frequency domain resources according to its configuration. The purpose is to simultaneously complete the transmission of the random access preamble and attempt to transmit part of the uplink data, thereby accelerating the access process.

[0069] 2. The base station sends back MsgB. After receiving MsgA, the base station will process it and send back message MsgB to the UE.

[0070] Among them, MsgB has two cases:

[0071] Successful outcome: If the random access procedure is successful, MsgB is a Contention Resolution message. The base station uses this message to inform the UE that the random access procedure has been successfully completed. After receiving this message, the UE can consider the random access procedure to be over and can then proceed with normal data communication and other operations according to network instructions.

[0072] Failure scenario: If the random access procedure fails, MsgB is a fallback indication. In this case, it means that 2-step CBRA has failed, and the UE needs to fall back to the third step of 4-step RACH (Random Access Channel) based on the time-frequency domain resource configuration information provided in the fallback indication. That is, it needs to use these configuration information to send Msg3 to the base station and retry the contention resolution procedure to complete the random access.

[0073] In detail, when the 2-step CBRA random access procedure fails, the base station sends MsgB (backoff instruction) to the UE. The UE needs to backoff to the third step of the 4-step RACH procedure based on the time-frequency domain resource configuration information therein to retry contention resolution. The UE first parses the configuration information to clarify key parameters such as the time-domain start time, duration, and time-frequency position of the Msg3 message. Then, it prepares Msg3 accordingly, organizing and encapsulating its own identity and access request parameters to carry a unique identifier, UE ID, that can be distinguished by the base station. Once Msg3 is ready and the specified time has elapsed, the UE sends Msg3 on the corresponding physical resource, returning to the contention resolution phase. The base station processes and judges based on the UE ID and other information in Msg3. After sending Msg3, the UE starts a contention resolution timer. Before the timeout, it monitors the PDCCH in the Type-1 PDCCH common search space. If the DCI can be successfully parsed using TC-RNTI, it indicates that the base station has processed Msg3, and the UE can stop the timer to determine that the access is successful. Otherwise, the contention resolution has failed, and it may need to repeat the initial steps until success.

[0074] The following provides an exemplary description of a communication system to which the embodiments of this application can be applied.

[0075] The downlink carrier switching method provided in this application can be applied to various communication systems, such as Long Term Evolution (LTE) systems, 5G mobile communication systems, Wireless Fidelity (WiFi) systems, future communication systems, or systems integrating multiple communication systems. This application does not limit the application to these systems. 5G can also be referred to as NR.

[0076] The downlink carrier switching method provided in this application can be applied to various communication scenarios, such as one or more of the following communication scenarios: enhanced mobile broadband, ultra-reliable low-latency communication, machine-type communication, massive machine-type communication, device-to-device, vehicle-to-everything (V2X), vehicle-to-vehicle (V2V), and Internet of Things (IoT).

[0077] To facilitate understanding of the embodiments of this application, the application scenario used in this application will be described using the communication system architecture shown in Figure 6 as an example. Figure 6 is a schematic diagram of a possible, non-limiting system. As shown in Figure 6, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 6, collectively referred to as 110) and at least one terminal (120a-120j in Figure 6, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 6). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network device in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0078] RAN 100 can be used for cellular systems related to the 3rd generation partnership project (3GPP), such as the communication systems described above. RAN 100 can also be used for communication systems such as cloud radio access networks (CRAN).

[0079] RAN node 110, sometimes also referred to as access network equipment, network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 6 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 6 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0080] In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node can be a macro base station (as shown in Figure 6, 110a), a micro base station or indoor station (as shown in Figure 6, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node can also be configured with program instructions for performing corresponding communication functions, as well as corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node's functions.

[0081] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0082] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0083] In this embodiment, the form of the RAN node is not limited. The device used to implement the function of the RAN node can be the RAN node itself; or it can be a device that supports the RAN node in implementing this function, such as a chip system. The device can be installed in the RAN node or used in conjunction with the RAN node.

[0084] A terminal can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, transportation vehicles with wireless communication capabilities, communication modules, etc. The embodiments of this application do not limit the device form of the terminal. A terminal typically contains a communication module, circuit, or chip that performs the corresponding communication function. The terminal can also be configured with program instructions for performing the corresponding communication function.

[0085] The embodiments of this application do not limit the device form of the terminal. The device used to implement the functions of the terminal can be the terminal itself; it can also be a device that supports the terminal in implementing the functions, such as a chip system. The device can be installed in the terminal or used in conjunction with the terminal. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices. All or part of the functions of the terminal in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0086] In another example, Figure 7 illustrates a different possible application framework in a communication system. As shown in Figure 7, the communication system includes a RAN intelligent controller (RIC). For example, RICs include near-real-time RICs (near-RT RICs) and non-real-time RICs (non-RT RICs). Non-real-time RICs primarily process non-real-time information, such as data that is not sensitive to latency, with latency in the order of seconds. Real-time RICs primarily process near-real-time information, such as data that is relatively sensitive to latency, with latency in the order of tens of milliseconds.

[0087] Near real-time RICs and non-real-time RICs can be used for model training and inference, as well as other possible data processing. Near real-time and non-real-time RICs can also be configured as separate network elements. Furthermore, near real-time and non-real-time RICs can be integrated into other devices; for example, near real-time RICs can be located in RAN nodes (e.g., CU, DU), while non-real-time RICs can be located in OAM, cloud servers, core network devices, or other network devices.

[0088] As described in the background section, when a handover terminal performs contention-based random access during carrier handover, the success rate is low.

[0089] In detail, during the four-step contention-based random access (CBRA) procedure, terminals configured with a specific handover mode will switch between FDD and SDL carriers as set. If the base station sends the DCI and Msg2 scheduling message on the FDD carrier when the terminal switches to the SDL carrier, the terminal will be unable to receive this information. Since Msg2 carries critical information such as resource authorization and timing advance required for Msg3 transmission, if it is missed, the terminal will be unable to obtain the uplink transmission configuration, resulting in the inability to transmit Msg3 normally, interrupting the random access procedure, and affecting the connection and data transmission between the terminal and the base station.

[0090] The 2-step CBRA process suffers from a similar problem. When the terminal switches its receiving function from FDD to SDL carrier in handover mode, if the base station sends the DCI and MsgB scheduling MsgB on the FDD carrier, the terminal will also be unable to receive the aforementioned information sent by the base station. MsgB contains the contention resolution result and key configurations for subsequent transmission. If the terminal does not receive it, it cannot confirm the access result, nor can it obtain transmission resources and timing information, thus failing to correctly execute subsequent operations, or even repeatedly initiating access, causing the 2-step CBRA process to fail and severely interfering with the connection efficiency and data transmission between the terminal and the base station.

[0091] To address the aforementioned technical problems, this application provides a method for switching downlink carriers. The method provided in this application will be described below with reference to the accompanying drawings.

[0092] In conjunction with the above-described communication system, this application provides a downlink carrier switching method. In this downlink carrier switching method, during contention-based random access, before a first time (the time when the terminal completes sending the identification information, the time when the contention resolution information is received, the time when the random access response window corresponding to the downlink information ends, or the time when the random access contention resolution timer expires), the terminal maintains receiving downlink information on the first downlink carrier during the contention-based random access process. This ensures that the terminal can receive the downlink information used for random access and will not fail to receive the downlink information used for random access due to switching to the second downlink carrier based on the switching configuration information, thereby improving the success rate of contention-based random access.

[0093] It should be noted that in the embodiments of this application, "sending information" can be understood as the transmission of information between devices or between logical modules within a device. For example, "network device sending information" can refer to a network device sending information to other devices (e.g., a terminal), or it can refer to logical module 1 within the network device sending information to logical module 2. Similarly, "network device receiving information" can be understood as a network device receiving information sent by other devices (e.g., a terminal), or logical module 1 within the network device receiving information from logical module 2.

[0094] "Sending information to a terminal" or related illustrations indicate that the destination of the information is a terminal, including direct or indirect sending; "receiving information from a terminal" or related illustrations indicate that the source of the information is a terminal, including direct or indirect receiving. Information may undergo format conversion and other processing during transmission, but the destination terminal can still understand the valid information from the source terminal. Similar expressions in this application can be interpreted in a similar way, and will not be elaborated further here.

[0095] In this embodiment, the names of messages, parameters, or information between network elements are examples and may differ in actual applications. Each network element may execute some or all of the steps, and the order and operation of the steps may be adjusted, and are not limited to all operations in the embodiments.

[0096] This application uses terminal devices and network devices as examples of interaction subjects, but the execution subjects are not limited to these. The methods of terminal devices can be implemented by their modules (such as chips, processors), logical nodes, or software; similarly, the methods of network devices can be implemented by their modules, logical nodes, or software, without any specific limitation.

[0097] Figure 8 shows a flowchart of the downlink carrier switching method provided in an embodiment of this application. As shown in Figure 8, the method may include the following steps:

[0098] S110, the network device sends handover configuration information to the terminal, and the terminal receives the handover configuration information from the network device accordingly.

[0099] The handover configuration information is used to instruct the terminal to switch between the first downlink carrier and the second downlink carrier, which are downlink carriers in a carrier aggregation scenario. Network devices can flexibly configure the handover configuration information based on implementation needs to indicate various possible downlink receive switching patterns (DL Rx switching patterns), or simply switching patterns. For example, the handover configuration information can instruct the terminal to switch downlink carriers based on the switching pattern shown in Figure 3.

[0100] The first downlink carrier is an FDD carrier, and the second downlink carrier is an SDL carrier.

[0101] S120, during contention-based random access, the terminal continues to receive downlink information on the first downlink carrier until the first moment.

[0102] The contention-based random access process can be initiated by the network device through a PDCCH Order instructing the terminal, or triggered by the terminal itself. After sending the RA preamble to the network device on the FDD carrier, the terminal remains on the FDD carrier until the first time interval, without performing downlink carrier handover based on the handover configuration information. Another possible interpretation is that the handover configuration information is not activated before the first time interval.

[0103] In one possible interpretation, S120 could also be described as: before the first time, during the contention-based random access process, the terminal maintains its reception of downlink information on the first downlink carrier.

[0104] Optionally, the first time can be the time when the terminal completes sending the identification information, or the first time can also be the time when the contention resolution information is received, whereby the terminal's identification information is used for contention resolution.

[0105] In a four-step access scenario, the first time is the time when the terminal completes sending its identification information. Since the Msg3 message sent by the terminal includes the terminal's identification information, the first time in this scenario can be the time when the terminal completes sending the Msg3 message. In other words, the first time is the time related to Msg3, that is, the time slot in which the physical uplink shared channel carrying the Msg3 message is located after the terminal finishes sending it.

[0106] For example, the terminal's identification information can be a cell radio network temporary identifier (C-RNTI). The information contained in Msg3 can be a C-RNTI for a media access control control element (MAC CE) used to transmit dedicated traffic channel (DTCH) / dedicated control channel (DCCH) logical channels. When the network device receives Msg3, it can confirm the terminal's identity based on the C-RNTI within it, and then return Msg4 (physical downlink control channel (PDCCH) scrambled with the C-RNTI).

[0107] In a two-step access scenario, the first time is the time when the contention resolution information is received. The MsgB sent by the network device to the terminal includes contention resolution information. Therefore, in this scenario, the first time can be the time when the terminal receives the MsgB. In other words, the first time is the time related to the MsgB, that is, the time slot in which the terminal finishes receiving the physical downlink shared channel carrying the MsgB message.

[0108] S130, the terminal performs carrier switching based on the handover configuration information, either from the first moment or after the first moment.

[0109] In the 4-step access scenario, the first time is the time when the terminal completes sending Msg3, and the time when the terminal completes receiving Msg4 is later than the time when the terminal completes sending Msg3. Optionally, as shown in Figure 9, the terminal can start carrier switching based on the handover configuration information at the time of completing sending Msg3, or, as shown in Figure 10, the terminal can start carrier switching based on the handover configuration information at the time of completing receiving Msg4. In other words, the time when carrier switching based on the handover configuration information begins is the time related to Msg4, that is, the time slot in which the physical downlink shared channel carrying the Msg4 message is located after the terminal finishes receiving it.

[0110] In a two-step access scenario, the first time is the time when the terminal receives the MsgB, which includes contention resolution information. The receipt of the MsgB marks the end of the CBRA process, and the terminal can continue to perform carrier switching based on the handover configuration information. As shown in Figure 11, the terminal can perform carrier switching based on the handover configuration information either at the time of receiving the MsgB or after receiving the MsgB.

[0111] In one embodiment, MsgB does not contain a contention resolution message, but instead carries a fallback indication. In this case, the terminal needs to fall back from 2-step random access to 4-step random access mode. Specifically, the terminal needs to re-enter 4-step access and begin preparing to send the Msg3 message. This fallback process can be referred to the description of the process shown in Figure 5. In this case, the terminal remains on the first downlink carrier, performing the above fallback process until the time for sending Msg3 is completed or later, at which point it begins carrier switching based on the handover configuration information.

[0112] In one embodiment, the first time is the time when the random access response window corresponding to the downlink information ends, or the time when the random access contention resolution timer expires.

[0113] In this application, considering that the terminal may be unable to send its identification information or receive contention resolution information, the embodiments of this application also design the aforementioned two possible first-time scenarios. Specifically, in a contention-based random access procedure, there are the following two types of abnormal situations:

[0114] Scenario 1: The terminal did not receive Msg2 / MsgB after sending the RA preamble.

[0115] After the terminal sends the random access preamble to the network device, it continuously monitors the Msg2 or MsgB returned by the network device within the random access response window. If the terminal still fails to detect the Msg2 / MsgB returned by the network device by the end of the random access response window, for example, due to poor channel conditions causing the network device to fail to receive the RA preamble sent by the terminal, the terminal increments the first counter, which is initially set to 0, by 1. Then, the terminal retransmits the RA preamble and restarts the above monitoring process. This process repeats until the value of the first counter reaches the first threshold, at which point the CBRA process is determined to have failed. It should be noted that the duration of the random access response window can be indicated by the ra-ResponseWindow information cell configured in the RRC.

[0116] In scenario one, the first time is the end time of the random access response window corresponding to the downlink information. The downlink information can be from Msg2 or MsgB.

[0117] In the 4-step random access process, if the terminal does not receive Msg2 after sending the RA preamble, it will proceed as follows: First, the terminal maintains a preamble transmission counter (preambleTransmissionCounter) with an initial value of 0. This counter increments by 1 after each retransmission of Msg1. When the maximum allowed number of preamble retransmissions (preambleTransMax) is exceeded, random access is deemed a failure, and an RRC layer report is triggered. Next, the terminal randomly selects a backoff time between 0 and backoff milliseconds based on the backoff parameters configured by the base station in SIB2. During Msg1 retransmission, the transmit power increases by a power ramping step (powerRampingStep) (default 2dB) until it reaches the terminal's maximum transmit power limited by the p-Max parameter. Simultaneously, the terminal reselects PRACH resources and chooses the preamble type. After the backoff ends, the terminal repeatedly sends Msg1 and initiates a random access response window until the counter exceeds its limit or Msg2 is received.

[0118] In a 2-step random access procedure, if the terminal does not receive MsgB, it will execute the corresponding fallback mechanism. Upon the first failure, the terminal starts a counter for the maximum number of MsgA transmissions (msgA-TransMax) and retransmits MsgA containing the preamble and Msg3 payload. If msgA-TransMax reaches its limit and the network is configured for a 4-step fallback, the network device will send a fallback instruction to the terminal. The terminal will then switch to the 4-step procedure, discard the original MsgA resource, reselect the Msg1 preamble, and may switch to a contention-based random access procedure. It will then send Msg1 and check Msg2, using the random access response window and the maximum number of preamble transmissions (preambleTransMax) parameter. If MsgB is received but contention resolution fails (e.g., a contention ID mismatch), the terminal will directly retransmit MsgA without performing a fallback operation.

[0119] Scenario 2: The terminal sends Msg3 but does not receive Msg4.

[0120] In the four-step contention-based random access (CBRA) procedure, after the terminal sends message 3 (Msg3) to the network device, it continuously monitors for message 4 (Msg4) from the network device within a contention resolution timer. If the terminal fails to receive Msg4 from the network device by the end of the contention resolution timer (e.g., due to poor channel conditions), it increments a second counter (initially 0) by 1. The terminal then retransmits Msg3 and restarts the monitoring process. This process loops until the second counter reaches a second threshold, at which point the CBRA procedure is considered a failure. The duration of the contention resolution timer is indicated by the ra-ContentionResolutionTimer cell configured in the RRC.

[0121] In scenario two, the first time is when the random access contention resolution timer expires.

[0122] In this case, when instructing step S130 (starting from or after the first time, performing carrier switching based on the handover configuration information), the following explanations are provided for cases one and two above:

[0123] In scenario one, the first time is the end time of the random access response window corresponding to the downlink information. Before the end time of the random access response window, carrier switching is not performed based on the handover configuration information. Instead, carrier switching is performed based on the handover configuration information at or after the end time of the random access response window to ensure that the downlink information in scenario one can be received by the terminal.

[0124] In scenario two, the first time is the time when the random access contention resolution timer expires. Before the contention resolution timer expires, carrier switching is not performed based on the handover configuration information. Instead, carrier switching is performed based on the handover configuration information at or after the contention resolution timer expires, ensuring that the downlink information in scenario two can be received by the terminal.

[0125] In this embodiment of the application, during the contention-based random access process, before the first time, the terminal maintains the reception of downlink information on the first downlink carrier, ensuring that the terminal can receive the downlink information for random access, and will not fail to receive the downlink information for random access due to switching to the second downlink carrier based on the handover configuration information, thereby improving the success rate of contention-based random access.

[0126] In one embodiment, when S130 performs a handover based on handover configuration information after a first time, S130 may include: starting carrier handover based on handover configuration information at a second time.

[0127] The second time is separated from the first time by a third time, which is a time predefined by the protocol or a time configured by the network device.

[0128] In more detail, the terminal begins handover based on handover configuration information at a second time after the third time interval of the first time interval. For example, the third time interval may include n time slots; in other words, the unit of the third time interval is a time slot. For instance, n = 1, which is the next time slot after the time slot of the first time interval. Further, the value of n can be predefined by the protocol or configured by the network device for the terminal via RRC signaling.

[0129] In this embodiment, by specifying a third time (e.g., in time slots) between the second time and the first time interval, the terminal is ensured to perform carrier switching at an appropriate time, thereby improving the orderliness and accuracy of carrier switching.

[0130] The foregoing mainly describes the solution provided by the embodiments of this application from the perspective of the execution logic of each step. It is understood that each node, such as a network device, includes corresponding hardware structures and / or software modules to execute each function in order to achieve the above-mentioned functions. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein, the method of the embodiments of this application can be implemented in hardware, software, or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0131] This application embodiment can divide the network device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0132] In specific implementations, the network elements shown in this application, such as terminals, can adopt the composition structure shown in Figure 12 or include the components shown in Figure 12. Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. When the communication device has the functions of the terminal described in the embodiment of this application, the communication device can be a terminal or a chip or system-on-a-chip in the terminal.

[0133] For example, Figure 12 illustrates a possible structural schematic of a communication device. It is understood that the communication device 700 includes means of the necessary form, such as modules, units, elements, circuits, or interfaces, to be appropriately configured together to perform this solution. The communication device 700 can be a terminal or network device described in the above method embodiments, or it can be a component (e.g., a chip) in these devices used to implement the methods described in the above method embodiments. The communication device 700 includes one or more processors 701. The processor 701 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[0134] Optionally, in one design, the processor 701 may include a program 703 (sometimes also referred to as code or instructions) that can be executed on the processor 701 to cause the communication device 700 to perform the methods described in the above embodiments. In yet another possible design, the communication device 700 includes circuitry (not shown in FIG12) for implementing the signal processing functions in the above embodiments.

[0135] Optionally, the communication device 700 may include one or more memories 702 storing a program 704 (sometimes referred to as code or instructions), which can be run on the processor 701 to cause the communication device 700 to perform the methods described in the above method embodiments.

[0136] Optionally, the processor 701 and / or memory 702 may include AI modules 707 and 708, which are used to implement AI-related functions. The AI ​​modules can be implemented through software, hardware, or a combination of both. For example, the AI ​​module may include a RIC module. For example, the AI ​​module may be a near real-time RIC or a non-real-time RIC.

[0137] Optionally, the processor 701 and / or memory 702 may also store data. The processor and memory may be configured separately or integrated together.

[0138] Optionally, the communication device 700 may further include a transceiver 705 and / or an antenna 706. The processor 701, sometimes referred to as a processing unit, controls the communication device. The transceiver 705, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to realize the transmission and reception functions of the communication device through the antenna 706.

[0139] Figure 13 illustrates a possible exemplary block diagram of the communication device involved in the embodiments of this application. As shown in Figure 13, the communication device 900 may include modules or units for implementing the methods described above. In one possible design, the communication device 900 includes a processing unit 902 and a communication unit 903. Optionally, the communication device 900 may further include a storage unit 901 for storing device program code and / or data.

[0140] The communication device 900 can be a terminal-side device in the above embodiments, such as a terminal or a communication module in a terminal, or a circuit or chip in a terminal that is responsible for communication functions.

[0141] For example, in one embodiment, the communication unit 903 is used to receive handover configuration information, which instructs the terminal to switch between a first downlink carrier and a second downlink carrier, wherein the first downlink carrier and the second downlink carrier are downlink carriers in a carrier aggregation scenario; the processing unit 902 is used to keep the terminal receiving downlink information on the first downlink carrier during contention-based random access until a first time; the processing unit 902 is used to perform carrier switching based on the handover configuration information starting from or after the first time, wherein the first time is the time when the terminal's identification information is completed, or the first time is the time when contention resolution information is received, wherein the terminal's identification information is used for contention resolution, or the first time is the time when the random access response window corresponding to the downlink information ends, or the time when the random access contention resolution timer expires.

[0142] In this embodiment of the application, during the contention-based random access process, before the first time (the time when the terminal completes sending the identification information, the time when the contention resolution information is received, the time when the random access response window corresponding to the downlink information ends, or the time when the random access contention resolution timer expires), the terminal maintains receiving downlink information on the first downlink carrier during the contention-based random access process. This ensures that the terminal can receive the downlink information used for random access and will not fail to receive the downlink information used for random access due to switching to the second downlink carrier based on the handover configuration information, thereby improving the success rate of contention-based random access.

[0143] In one possible design, when the communication device 900 is a terminal or a communication module within a terminal, the function of the processing unit 902 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The function of the communication unit 903 can be implemented by transceiver circuitry.

[0144] In one possible design, when the communication device 900 is a circuit or chip in a terminal responsible for communication functions, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 902 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 903 can be implemented by an interface circuit or data transceiver circuit on the aforementioned chip.

[0145] In one possible design, when the communication device 900 is a terminal or a processing module within a terminal, the functionality of the processing unit 902 can be implemented by one or more processors. Specifically, the processor may include a GPU, or a system-on-a-chip (SoC) or SIP chip containing a GPU. Alternatively, the processor may include an AI processor, or a SoC or SIP chip containing an AI processor. Or, the processor may include an ASIC, or a SoC or SIP chip containing an ASIC. The functionality of the communication unit 903 can be implemented by transceiver circuitry.

[0146] In one possible design, when the communication device 900 is a circuit or chip in a terminal responsible for processing functions, such as a GPU or a system-on-a-chip (SoC) or SIP chip containing a GPU, an AI processor or a SoC or SIP chip containing an AI processor, or an ASIC or a SoC or SIP chip containing an ASIC, the function of the processing unit 902 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 903 can be implemented by interface circuitry or data transceiver circuitry on the aforementioned chip.

[0147] It is understandable that the division of units in the above-mentioned device is merely a logical functional division. One function can correspond to one functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into one physical entity, or they can be distributed across different physical entities. Furthermore, the above-mentioned functional units can be implemented in hardware, software, or a combination of both.

[0148] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0149] In one example, storage unit 901 may include random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory and / or registers, etc.

[0150] This application embodiment also provides a communication system, which may include a terminal, and optionally, may further include a network device. The terminal may have the corresponding functions of the aforementioned communication device 900.

[0151] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be a terminal device of any of the foregoing embodiments, such as an internal storage unit including a data sending end and / or a data receiving end, such as a hard disk or memory of the terminal device. The computer-readable storage medium can also be an external storage device of the terminal device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal device. Further, the computer-readable storage medium can include both the internal storage unit and the external storage device of the terminal device. The computer-readable storage medium is used to store the computer program and other programs and data required by the terminal device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0152] This application also provides computer instructions. All or part of the processes in the above method embodiments can be executed by computer instructions to instruct related hardware (such as computers, processors, network devices, and terminals). The program can be stored in the aforementioned computer-readable storage medium.

[0153] This application also provides a computer program product that, when run on a computer, causes the above-described method embodiments to be executed.

[0154] This application also provides a chip system. The chip system may be composed of chips or may include chips and other discrete devices, without limitation. The chip system includes a processor and a transceiver. All or part of the processes in the above method embodiments can be completed by this chip system, such as the chip system being used to implement the functions performed by the network device or terminal device in the above method embodiments.

[0155] In one possible design, the chip system further includes a memory for storing program instructions and / or data. When the chip system is running, the processor executes the program instructions stored in the memory to enable the chip system to perform the functions performed by the network device or terminal device in the above method embodiments.

[0156] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0157] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store instructions and / or data.

[0158] It should be noted that the terms "first" and "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0159] Unless otherwise specified, the term "transmission" in the embodiments of this application refers to bidirectional transmission, encompassing the actions of sending and / or receiving. Specifically, "transmission" in the embodiments of this application includes sending data, receiving data, or both sending and receiving data. In other words, data transmission here includes uplink and / or downlink data transmission. Data may include channels and / or signals; uplink data transmission refers to uplink channel and / or uplink signal transmission, and downlink data transmission refers to downlink channel and / or downlink signal transmission. The terms "network" and "system" in the embodiments of this application refer to the same concept; a communication system is a communication network.

[0160] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0161] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0162] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0163] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device, such as a microcontroller, chip, or processor, to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0164] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0165] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0166] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0167] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0168] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

[0169] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for switching downlink carriers, characterized in that, The method includes: Receive handover configuration information, wherein the handover configuration information is used to instruct the terminal to handover between a first downlink carrier and a second downlink carrier, wherein the first downlink carrier and the second downlink carrier are downlink carriers in a carrier aggregation scenario; During contention-based random access, continue receiving downlink information on the first downlink carrier until the first moment; Starting from or after the first time, carrier switching is performed based on the switching configuration information. The first time is the time when the terminal's identification information is sent, or the first time is the time when contention resolution information is received, where the terminal's identification information is used for contention resolution, or the first time is the time when the random access response window corresponding to the downlink information ends, or the time when the random access contention resolution timer expires.

2. The method according to claim 1, characterized in that, The contention-based random access includes contention-based two-step random access or contention-based four-step random access.

3. The method according to claim 1 or 2, characterized in that, The switching based on the switching configuration information after the first time includes: Carrier switching begins at a second time based on the switching configuration information, wherein the second time is separated from the first time by a third time, which is a time predefined by the protocol or a time configured by the network device.

4. The method according to claim 3, characterized in that, The unit of the third time is a time slot.

5. A communication device, characterized in that, Includes a module that performs the method as described in any one of claims 1-4.

6. A communication device, characterized in that, The communication device includes a processor for supporting the communication device in performing the method as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed, cause the method described in any one of claims 1-4 to be performed.

8. A computer program product, characterized in that, When it is run on a computer, it causes the method described in any one of claims 1-4 to be performed.