Wireless communication method, apparatus and device
By having the terminal switch or activate the target frequency domain resources during random access, or by having the network-side device send configuration information, the use of frequency domain resources is optimized, which solves the problem of insufficient performance during random access, improves scheduling and switching performance, and saves power for the terminal.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- VIVO MOBILE COMM CO LTD
- Filing Date
- 2024-12-03
- Publication Date
- 2026-06-05
AI Technical Summary
Existing technologies lack sufficient frequency domain resource scheduling and handover performance during random access, failing to meet the high requirements of communication technologies.
When a terminal initiates random access, it performs a switch or activation operation on the target frequency domain resource based on the configuration of the activated frequency domain resource, or the network-side device sends configuration information to indicate the activation or deactivation timer of the frequency domain resource to optimize the use of frequency domain resources.
It improves the frequency domain resource scheduling and switching performance during random access, ensures uplink and downlink transmission performance, and achieves power saving effect for the terminal.
Smart Images

Figure CN122160912A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of communication technology, specifically relating to a wireless communication method, apparatus, and device. Background Technology
[0002] In related technologies, a cell (or carrier) supports the activation of a Band Width Part (BWP). When a BWP needs to be handed over, there needs to be an active BWP that meets the requirements to maintain operation. However, with the evolution of communication technologies, higher demands are placed on the performance of frequency domain resource scheduling and handover during random access. How to improve the performance of frequency domain resource scheduling and handover during random access is a problem that needs to be solved. Summary of the Invention
[0003] This application provides a wireless communication method, apparatus, and device that can solve the problems of insufficient performance in frequency domain resource scheduling and switching during current random access.
[0004] Firstly, a wireless communication method is provided, comprising:
[0005] When a terminal initiates random access, it performs a first operation, a second operation, or a third operation depending on whether random access resources are configured on the first activated uplink frequency domain resource.
[0006] The first operation includes one of the following:
[0007] Switch to the target uplink frequency domain resource and activate the target uplink frequency domain resource;
[0008] The second operation includes one of the following:
[0009] Switch to the first target downlink frequency domain resource and activate the first target downlink frequency domain resource;
[0010] The third operation includes one of the following:
[0011] Switch to the second target downlink frequency domain resource and activate the second target downlink frequency domain resource.
[0012] Secondly, a wireless communication method is provided, including:
[0013] The network-side device sends the first configuration information to the terminal;
[0014] The first configuration information includes at least one of the following:
[0015] Information on the deactivation timers for N downlink frequency domain resources;
[0016] The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources.
[0017] The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate more uplink frequency domain resources;
[0018] The third indication information is used to indicate the characteristic set of M uplink frequency domain resources;
[0019] The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources;
[0020] The fifth indication information is used to indicate at least one of the following supported by each of the M uplink frequency domain resources: channel bandwidth or channel bandwidth list, bandwidth portion BWP bandwidth or BWP bandwidth list, terminal type or terminal type list, terminal capability or terminal capability list, terminal power consumption level or terminal power consumption level list, service or service list.
[0021] The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0022] The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0023] The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0024] Where M and N are both positive integers.
[0025] Thirdly, a wireless communication method is provided, including:
[0026] The terminal performs the fourth operation when initiating random access; or,
[0027] The terminal performs the fifth operation when initiating random access;
[0028] The fourth operation includes one of the following: stopping the deactivation timer of some or all of the activated downlink frequency domain resources, or not stopping the deactivation timer of some or all of the activated downlink frequency domain resources.
[0029] The fifth operation includes performing a random access procedure using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell, wherein random access resources are configured on the first uplink frequency domain resources.
[0030] Fourthly, a wireless communication device is provided, comprising:
[0031] The processing module is used to perform a first operation, a second operation, or a third operation when initiating random access, depending on whether random access resources are configured on the activated first uplink frequency domain resource.
[0032] The first operation includes one of the following:
[0033] Switch to the target uplink frequency domain resource and activate the target uplink frequency domain resource;
[0034] The second operation includes one of the following:
[0035] Switch to the first target downlink frequency domain resource and activate the first target downlink frequency domain resource;
[0036] The third operation includes one of the following:
[0037] Switch to the second target downlink frequency domain resource and activate the second target downlink frequency domain resource.
[0038] Fifthly, a wireless communication device is provided, comprising:
[0039] The sending module is used to send the first configuration information to the terminal;
[0040] The first configuration information includes at least one of the following:
[0041] Information on the deactivation timers for N downlink frequency domain resources;
[0042] The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources.
[0043] The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate more uplink frequency domain resources;
[0044] The third indication information is used to indicate the characteristic set of M uplink frequency domain resources;
[0045] The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources;
[0046] The fifth indication information is used to indicate at least one of the following supported by each of the M uplink frequency domain resources: channel bandwidth or channel bandwidth list, bandwidth portion BWP bandwidth or BWP bandwidth list, terminal type or terminal type list, terminal capability or terminal capability list, terminal power consumption level or terminal power consumption level list, service or service list.
[0047] The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0048] The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0049] The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0050] Where M and N are both positive integers.
[0051] Sixthly, a wireless communication device is provided, comprising:
[0052] The processing module is used to perform a fourth operation when initiating random access; or,
[0053] The processing module is used to perform the fifth operation when a random access is initiated;
[0054] The fourth operation includes one of the following: stopping the deactivation timer of some or all of the activated downlink frequency domain resources, or not stopping the deactivation timer of some or all of the activated downlink frequency domain resources.
[0055] The fifth operation includes performing a random access procedure using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell, wherein random access resources are configured on the first uplink frequency domain resources.
[0056] In a seventh aspect, 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, or to implement the steps of the method described in the third aspect.
[0057] Eighthly, 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 or third aspect.
[0058] Ninthly, a terminal is provided, including a processor and a communication interface;
[0059] The processor is used to perform a first operation, a second operation, or a third operation when initiating random access, depending on whether random access resources are configured on the activated first uplink frequency domain resource.
[0060] The first operation includes one of the following:
[0061] Switch to the target uplink frequency domain resource and activate the target uplink frequency domain resource;
[0062] The second operation includes one of the following:
[0063] Switch to the first target downlink frequency domain resource and activate the first target downlink frequency domain resource;
[0064] The third operation includes one of the following:
[0065] Switch to the second target downlink frequency domain resource and activate the second target downlink frequency domain resource.
[0066] In a tenth aspect, a terminal is provided, including a processor and a communication interface;
[0067] Wherein, the processor is configured to perform a fourth operation when initiating random access; or, the processor is configured to perform a fifth operation when initiating random access;
[0068] The fourth operation includes one of the following: stopping the deactivation timer of some or all of the activated downlink frequency domain resources, or not stopping the deactivation timer of some or all of the activated downlink frequency domain resources.
[0069] The fifth operation includes performing a random access procedure using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell, wherein random access resources are configured on the first uplink frequency domain resources.
[0070] Eleventhly, 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.
[0071] In a twelfth aspect, a network-side device is provided, including a processor and a communication interface;
[0072] The communication interface is used to send first configuration information to the terminal;
[0073] The first configuration information includes at least one of the following:
[0074] Information on the deactivation timers for N downlink frequency domain resources;
[0075] The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources.
[0076] The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate more uplink frequency domain resources;
[0077] The third indication information is used to indicate the characteristic set of M uplink frequency domain resources;
[0078] The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources;
[0079] The fifth indication information is used to indicate at least one of the following supported by each of the M uplink frequency domain resources: channel bandwidth or channel bandwidth list, bandwidth portion BWP bandwidth or BWP bandwidth list, terminal type or terminal type list, terminal capability or terminal capability list, terminal power consumption level or terminal power consumption level list, service or service list.
[0080] The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0081] The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0082] The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0083] Where M and N are both positive integers.
[0084] In a thirteenth 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 the steps of the method described in the second aspect, or the steps of the method described in the third aspect.
[0085] In a fourteenth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device;
[0086] The terminal may be used to perform the steps of the method as described in the first or third aspect, and the network-side device may be used to perform the steps of the method as described in the second aspect.
[0087] In a fifteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.
[0088] In a sixteenth 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 the steps of the wireless communication method as described in the second aspect, or the steps of the wireless communication method as described in the third aspect.
[0089] In the embodiments of the first aspect, when initiating random access, the terminal performs a first operation, a second operation, or a third operation depending on whether a random access resource is configured on the activated first uplink frequency domain resource; wherein the first operation includes one of the following: switching to a target uplink frequency domain resource and activating the target uplink frequency domain resource; wherein the second operation includes one of the following: switching to a first target downlink frequency domain resource and activating the first target downlink frequency domain resource; wherein the third operation includes one of the following: switching to a second target downlink frequency domain resource and activating the second target downlink frequency domain resource. Specifically, the terminal can activate the target uplink frequency domain resource when initiating random access, thereby enabling the terminal to maintain multiple activated uplink frequency domain resources, ensuring uplink transmission performance during random access, and also improving the scheduling and switching performance of uplink frequency domain resources during random access; or, the terminal can switch to the target uplink frequency domain resource when initiating random access, thereby avoiding the terminal unnecessarily maintaining multiple activated uplink frequency domain resources, achieving terminal power saving effect, and also improving the scheduling and switching performance of uplink frequency domain resources during random access. Alternatively, the terminal can activate either the first target downlink frequency domain resource or the second target downlink frequency domain resource when initiating random access, thereby enabling the terminal to maintain multiple active downlink frequency domain resources, ensuring downlink transmission performance during random access, and also improving the performance of downlink frequency domain resource scheduling and switching during random access; or, the terminal can switch to the first target downlink frequency domain resource or the second target downlink frequency domain resource when initiating random access, thereby avoiding the terminal needing to maintain multiple active downlink frequency domain resources unnecessarily, achieving power saving effect for the terminal, and also improving the performance of downlink frequency domain resource scheduling and switching during random access.
[0090] In the second aspect of the embodiment, the network-side device sends first configuration information to the terminal; wherein the first configuration information includes at least one of the following: information on deactivation timers for N downlink frequency domain resources; first indication information for indicating whether multiple activation of uplink frequency domain resources is enabled for M uplink frequency domain resources; second indication information for indicating whether multiple activation of uplink frequency domain resources is enabled for the N downlink frequency domain resources; third indication information for indicating the feature set of the M uplink frequency domain resources; fourth indication information for indicating the feature set of the N downlink frequency domain resources; and fifth indication information for indicating the feature set of the M uplink frequency domain resources. The frequency domain resources each support at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capabilities, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services; the sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capabilities, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services. Therefore, the terminal can activate or switch uplink frequency domain resources during random access based on the first configuration information, and / or the terminal can activate or switch downlink frequency domain resources during random access based on the first configuration information, improving uplink and downlink transmission performance during random access, and also improving the scheduling and switching performance of uplink and downlink frequency domain resources during random access.
[0091] In the third aspect of the embodiment, the terminal performs a fourth operation when initiating random access; or, the terminal performs a fifth operation when initiating random access; the fourth operation includes one of the following: stopping the deactivation timer of some or all of the activated downlink frequency domain resources, or not stopping the deactivation timer of some or all of the activated downlink frequency domain resources; the fifth operation includes performing a random access procedure using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell, wherein random access resources are configured on the first uplink frequency domain resources. Specifically, when initiating random access, the terminal stops the deactivation timer of some or all of the activated downlink frequency domain resources, or does not stop the deactivation timer of some or all of the activated downlink frequency domain resources, thereby making reasonable use of downlink frequency domain resources and improving the performance of downlink frequency domain resource scheduling, handover, etc. during random access. Alternatively, when initiating random access, the terminal uses the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell to perform a random access procedure, thereby improving random access performance and the performance of uplink and downlink frequency domain resource scheduling, handover, etc. during random access. Attached Figure Description
[0092] Figure 1 This is a schematic diagram of a communication system architecture provided in an embodiment of this application.
[0093] Figure 2 This is one of the schematic flowcharts of a wireless communication method provided according to an embodiment of this application.
[0094] Figure 3 This is a second illustrative flowchart of a wireless communication method provided according to an embodiment of this application.
[0095] Figure 4 This is the third illustrative flowchart of a wireless communication method provided according to an embodiment of this application.
[0096] Figure 5 This is one of the schematic flowcharts of BWP operation during random access provided in the embodiments of this application.
[0097] Figure 6 This is the second illustrative flowchart of BWP operation during random access provided in the embodiments of this application.
[0098] Figure 7 This is one of the schematic block diagrams of a wireless communication device provided according to an embodiment of this application.
[0099] Figure 8 This is a second schematic block diagram of a wireless communication device provided according to an embodiment of this application.
[0100] Figure 9 This is a schematic block diagram of a wireless communication device provided according to an embodiment of this application.
[0101] Figure 10 This is a schematic block diagram of a communication device provided according to an embodiment of this application.
[0102] Figure 11 This is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application.
[0103] Figure 12 This is a schematic block diagram of a network-side device provided according to an embodiment of this application. Detailed Implementation
[0104] 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.
[0105] 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.
[0106] 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.
[0107] 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.
[0108] Figure 1 This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. Specifically, the wireless communication system includes a terminal 11 and a network-side device 12.
[0109] 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), shipboard equipment, pedestrian user equipment (PUE), smart home device (home device with wireless communication function, such as refrigerator, television, washing machine or furniture, etc.), game console, personal computer (PC), ATM or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in the embodiments of this application.
[0110] Among them, network-side equipment 12 may include access network equipment.
[0111] 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 (NRNode 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 specific technical terms. 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.
[0112] To better understand the technical solution of this application, the following describes the scheduling-based BWP handover.
[0113] A currently connected terminal (UE) can be configured with one or more BWPs in a serving cell. BWP handover is used to simultaneously activate an inactive BWP and deactivate an active BWP. BWP handover methods include: control using the Physical Downlink Control Channel (PDCCH), control using a BWP deactivation timer (bwp-inactivityTimer), control using Radio Resource Control (RRC) signaling, or control by the Media Access Control (MAC) entity itself when performing random access procedures or detecting consecutive Listen Before Talk (LBT) failures on a Special Cell (SpCell).
[0114] For BWP handover controlled by bwp-InactivityTimer, one bwp-InactivityTimer is configured for each serving cell, and one active BWP is associated with one bwp-InactivityTimer.
[0115] If the currently active BWP is not the default BWP (as indicated by defaultDownlinkBWP-Id), or if the currently active BWP is not the initial BWP (as indicated by defaultDownlinkBWP-Id when defaultDownlinkBWP-Id is not configured), and if it is not a dormant BWP (as associated with dormantBWP-Id) when dormantBWP-Id is configured, and there is a schedule, including the following:
[0116] The PDCCH indicating downlink allocation or uplink authorization is received on the BWP with scrambled Cell Radio Network Temporary Identity (C-RNTI) or Configured Scheduling Radio Network Temporary Identity (CS-RNTI);
[0117] Alternatively, it may receive an indication to allocate a downlink PDCCH scrambled with either the Group Radio Network Temporary Identity (G-RNTI) configured for multicast or the Group Configured Scheduling Radio Network Temporary Identity (G-CS-RNTI);
[0118] Or it received a PDCCH indicating downlink allocation or uplink authorization for an activated BWP with C-RNTI or CS-RNTI scrambling;
[0119] Alternatively, a Media Access Control Protocol Data Unit (MAC PDU) was transmitted on the configured grant and no LBT failure indication was received from the underlying layer;
[0120] Alternatively, a unicast-related MAC PDU or a multicast service (MBS)-related MAC PDU may be received on the downlink allocation.
[0121] If there is no running random access procedure in the current serving cell, or if the running random access procedure successfully completes after receiving the C-RNTI scrambled PDCCH, then the BWP-related bwp-InactivityTimer will be started or restarted.
[0122] For non-redcap UEs, the initial BWP is the BWP configured with the initial downlink BWP. For redcap UEs, the initial BWP is either the initial downlink BWP-RedCap (if configured) or the initial downlink BWP (if initial downlink BWP-RedCap is not configured).
[0123] When the bwp-InactivityTimer associated with the active BWP expires, if a default BWP is configured, the UE will perform a BWP handover and switch to the default BWP; otherwise, the UE will switch to the initial BWP.
[0124] When the UE receives a PDCCH for BWP handover, and the active BWP indicated by the PDCCH is not the default BWP (the BWP indicated by defaultDownlinkBWP-Id) or not the initial BWP (when defaultDownlinkBWP-Id is not configured), and is not the dormitory BWP when dormitoryBWP-Id is configured, then the UE starts or restarts the bwp-InactivityTimer associated with that BWP.
[0125] When a UE performs a Random Access Channel (RACH) procedure in a serving cell, after selecting a carrier, the UE stops the bwp-inactivityTimer of the active BWP associated with that serving cell for that carrier. If the cell is a secondary cell (SCell), the UE also stops the bwp-inactivityTimer of the active BWP of the SCell.
[0126] When the network side releases the configuration of bwp-InactivityTimer in the Radio Resource Control (RRC) signaling, the UE must stop the bwp-InactivityTimer of the active BWP in the serving cell.
[0127] To better understand the technical solution of this application, the following describes BWP handover based on random access.
[0128] A currently connected UE can be configured with one or more Backdoor Window (BWP) within a serving cell, but only one BWP can be active. When a UE initiates random access, it needs to check whether the currently active uplink BWP has RACH resources configured. If not, the UE needs to switch to the initial uplink BWP.
[0129] When a connected UE initiates random access, the bwp-InactivityTimer related to the active BWP of the current serving cell needs to be stopped. If the current serving cell is an SCell, the bwp-InactivityTimer related to the active BWP of the SpCell also needs to be stopped.
[0130] 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.
[0131] Figure 2 This is a schematic flowchart of a wireless communication method 200 according to an embodiment of this application, such as... Figure 2 As shown, the wireless communication method 200 may include at least some of the following:
[0132] S210, when the terminal initiates random access, it performs a first operation, a second operation, or a third operation depending on whether random access resources are configured on the activated first uplink frequency domain resource.
[0133] The first operation includes one of the following:
[0134] Switch to the target uplink frequency domain resource and activate the target uplink frequency domain resource;
[0135] The second operation includes one of the following:
[0136] Switch to the first target downlink frequency domain resource and activate the first target downlink frequency domain resource;
[0137] The third operation includes one of the following:
[0138] Switch to the second target downlink frequency domain resource and activate the second target downlink frequency domain resource.
[0139] It should be understood that Figure 2 The steps or operations of the wireless communication method 200 are illustrated, but these steps or operations are merely examples, and other operations may be performed in this application. Figure 2 Variations of various operations within it.
[0140] In this embodiment, the terminal can be in an RRC connected state. Of course, the terminal can also be in other RRC states, and this application is not limited to this.
[0141] The frequency domain resources described in the embodiments of this application can be equivalent to or replaced with BWP or other similar descriptions such as small bandwidth or micro bandwidth. For example, uplink frequency domain resources can be equivalent to or replaced with uplink BWP, and downlink frequency domain resources can be equivalent to or replaced with downlink BWP. This application does not limit this.
[0142] The switching to the target uplink frequency domain resource described in this application embodiment can be understood as activating the target uplink frequency domain resource while deactivating the previously activated uplink frequency domain resource. The activation of the target uplink frequency domain resource described in this application embodiment can be understood as activating the target uplink frequency domain resource while keeping one or more uplink frequency domain resources active.
[0143] The switching to the first target downlink frequency domain resource described in this application embodiment can be understood as activating the first target downlink frequency domain resource while deactivating the previously activated downlink frequency domain resource. The activation of the first target downlink frequency domain resource described in this application embodiment can be understood as activating the first target downlink frequency domain resource while keeping one or more downlink frequency domain resources active.
[0144] The channel bandwidth list described in this application embodiment can also be replaced with a channel bandwidth combination or a channel bandwidth set. The BWP bandwidth list described in this application embodiment can also be replaced with a BWP bandwidth combination or a BWP bandwidth set. The terminal type list described in this application embodiment can also be replaced with a terminal type combination or a terminal type set. The terminal capability list described in this application embodiment can also be replaced with a terminal capability combination or a terminal capability set. The terminal energy consumption level list described in this application embodiment can also be replaced with a terminal energy consumption level combination or a terminal energy consumption level set. The service list described in this application embodiment can also be replaced with a service combination or a service set. This application embodiment is not limited in this respect.
[0145] The deactivation timer described in this application embodiment can also be called an inactive timer, and this application does not limit it to that.
[0146] The enabling described in the embodiments of this application can also be understood as support or activation, and the disabling described in the embodiments of this application can also be understood as non-support or non-activation. This application does not limit this.
[0147] The "enabling multi-active uplink frequency domain resources" described in this application embodiment can be understood as enabling the characteristic of multi-active uplink frequency domain resources, or enabling the function of multi-active uplink frequency domain resources. Taking the uplink frequency domain resource as an example of an uplink BWP, "enabling multi-active uplink BWP" can be understood as enabling the characteristic of multi-active uplink BWP, or enabling the function of multi-active uplink BWP.
[0148] The "disable multi-activation of uplink frequency domain resources" mentioned in the embodiments of this application can be understood as disabling the characteristic of disabling multi-activation of uplink frequency domain resources, or disabling the function of disabling multi-activation of uplink frequency domain resources.
[0149] The "enabling multi-active downlink frequency domain resources" described in this application embodiment can be understood as enabling the characteristic of multi-active downlink frequency domain resources, or enabling the function of multi-active downlink frequency domain resources. Taking the downlink frequency domain resource as a downlink BWP as an example, "enabling multi-active downlink BWP" can be understood as enabling the characteristic of multi-active downlink BWP, or enabling the function of multi-active downlink BWP.
[0150] The "disable multiple activation of downlink frequency domain resources" mentioned in the embodiments of this application can be understood as disabling the characteristic of disabling multiple activation of downlink frequency domain resources, or disabling the function of disabling multiple activation of downlink frequency domain resources.
[0151] The multi-active uplink frequency domain resources and multi-active downlink frequency domain resources described in the embodiments of this application can also be unified as multi-active frequency domain resources, and the embodiments of this application do not limit this.
[0152] The switching to the second target downlink frequency domain resource described in this application embodiment can be understood as activating the second target downlink frequency domain resource while deactivating the previously activated downlink frequency domain resource. The activation of the second target downlink frequency domain resource described in this application embodiment can be understood as activating the second target downlink frequency domain resource while keeping one or more downlink frequency domain resources active.
[0153] In the embodiments of this application, the terminal can activate the target uplink frequency domain resource when initiating random access, thereby enabling the terminal to maintain multiple active uplink frequency domain resources, ensuring uplink transmission performance during random access, and also improving the scheduling and switching performance of uplink frequency domain resources during random access; or, the terminal can switch to the target uplink frequency domain resource when initiating random access, thereby avoiding the terminal from needing to maintain multiple active uplink frequency domain resources unnecessarily, achieving terminal power saving effect, and also improving the scheduling and switching performance of uplink frequency domain resources during random access.
[0154] Alternatively, in this embodiment, the terminal can activate either the first target downlink frequency domain resource or the second target downlink frequency domain resource when initiating random access, thereby enabling the terminal to maintain multiple activated downlink frequency domain resources, ensuring downlink transmission performance during random access, and also improving the scheduling and switching performance of downlink frequency domain resources during random access; or, the terminal can switch to the first target downlink frequency domain resource or the second target downlink frequency domain resource when initiating random access, thereby avoiding the terminal from unnecessarily maintaining multiple activated downlink frequency domain resources, achieving power saving effect for the terminal, and also improving the scheduling and switching performance of downlink frequency domain resources during random access.
[0155] In some embodiments, the random access resources described in this application may include, but are not limited to, at least one of the following:
[0156] Random access opportunity (RO);
[0157] Physical Random Access Channel (PRACH) occasion.
[0158] In some embodiments, the above-described S210 may specifically include:
[0159] If no random access resource is configured on the first uplink frequency domain resource, the terminal performs the first operation when initiating random access, or the terminal performs the second operation when initiating random access;
[0160] If random access resources are configured on the first uplink frequency domain resources, the terminal performs the third operation when initiating random access.
[0161] In some embodiments, the terminal performs the first operation when initiating random access, including:
[0162] If the first condition is met, the terminal switches to the target uplink frequency domain resource when initiating random access;
[0163] And / or,
[0164] If the second condition is met, the terminal activates the target uplink frequency domain resource when initiating random access;
[0165] The first condition includes, but is not limited to, at least one of the following:
[0166] The terminal does not support multiple activations of uplink frequency domain resources; the first uplink frequency domain resource does not enable multiple activations of uplink frequency domain resources; the target uplink frequency domain resource does not enable multiple activations of uplink frequency domain resources; multiple activations of uplink frequency domain resources are not enabled between the first uplink frequency domain resource and the target uplink frequency domain resource; the first uplink frequency domain resource and the target uplink frequency domain resource overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the target uplink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the target uplink frequency domain resource; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the target uplink frequency domain resource; the terminal The supported channel bandwidth is greater than or equal to the smallest channel bandwidth in the target uplink frequency domain resource's supported channel bandwidth list; the terminal's supported channel bandwidth is greater than or equal to the smallest BWP bandwidth in the target uplink frequency domain resource's supported BWP bandwidth list; the target uplink frequency domain resource's supported terminal type list includes at least the terminal type of the terminal; the target uplink frequency domain resource's supported terminal capability list includes at least the terminal capabilities of the terminal; the target uplink frequency domain resource's supported terminal energy consumption level list includes at least the terminal energy consumption level of the terminal; the target uplink frequency domain resource's supported service list includes at least the service corresponding to the random access initiated by the terminal; the target uplink frequency domain resource is configured with random access resources (such as resources corresponding to Msg1 or MsgA);
[0167] The second condition includes, but is not limited to, at least one of the following:
[0168] The terminal supports multiple active uplink frequency domain resources; the first uplink frequency domain resource enables multiple active uplink frequency domain resources; the target uplink frequency domain resource enables multiple active uplink frequency domain resources; multiple active uplink frequency domain resources are enabled between the first uplink frequency domain resource and the target uplink frequency domain resource; the first uplink frequency domain resource and the target uplink frequency domain resource do not overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the target uplink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the target uplink frequency domain resource; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the target uplink frequency domain resource; the terminal supports The channel bandwidth of the terminal is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the target uplink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the target uplink frequency domain resource; the list of terminal types supported by the target uplink frequency domain resource includes at least the terminal type of the terminal; the list of terminal capabilities supported by the target uplink frequency domain resource includes at least the terminal capabilities of the terminal; the list of terminal energy consumption levels supported by the target uplink frequency domain resource includes at least the terminal energy consumption level of the terminal; the list of services supported by the target uplink frequency domain resource includes at least the services corresponding to the random access initiated by the terminal; and random access resources (such as resources corresponding to Msg1 or MsgA) are configured on the target uplink frequency domain resource.
[0169] In this embodiment, if the first condition is met, the terminal switches to the target uplink frequency domain resource when initiating random access; and / or, if the second condition is met, the terminal activates the target uplink frequency domain resource when initiating random access. Thus, the terminal can reasonably perform relevant operations (such as switching, activation, etc.) on the uplink frequency domain resource based on the first and second conditions when initiating random access, and can also improve the performance of uplink frequency domain resource scheduling and switching during random access.
[0170] Optionally, the terminal type can be an Internet of Things (IoT) terminal, an Ambient Internet of Things (A-IoT) terminal, a Reduced Capability (RedCap) terminal, a Non-Terrestrial Network (NTN) terminal, a Very Small Aperture Terminal (VSAT) terminal, an A-IoT+RedCap terminal, an A-IoT+NTN terminal, an IoT+NTN terminal, etc.
[0171] It should be noted that an A-IoT+RedCap terminal indicates that the terminal can support both A-IoT and RedCap features simultaneously, such as a RedCap terminal equipped with an A-IoT module. A-IoT+NTN terminals, IoT+NTN terminals, etc. are similar, and will not be elaborated further here.
[0172] Optionally, the list of terminal types may include, but is not limited to, at least one of the following: IoT terminal, A-IoT terminal, RedCap terminal, NTN terminal, VSAT terminal.
[0173] Optionally, the terminal's capabilities can include whether the terminal supports multiple active uplink frequency domain resources, the number of receive antennas or transmit antennas supported by the terminal, and the channel bandwidth or BWP bandwidth supported by the terminal.
[0174] Optionally, the terminal's terminal capability list may include, but is not limited to, at least one of the following: whether the terminal supports multiple active uplink frequency domain resources, the number of receive antennas or transmit antennas supported by the terminal, and the channel bandwidth or BWP bandwidth supported by the terminal.
[0175] It should be noted that the terminal's terminal energy consumption level can also be understood or replaced as the terminal's terminal energy consumption status.
[0176] For example, the terminal energy consumption level indicates the level of energy consumption of the terminal when performing a service. If the terminal is performing an Extended Reality (XR) service, it is a high power consumption service.
[0177] For example, the terminal's power consumption status indicates the terminal's current remaining battery energy, such as when the terminal's remaining power is low.
[0178] Optionally, the terminal can support services such as Ultra-Reliable and Low-Latency Communication (URLLC), Enhanced Mobile Broadband (eMBB), emergency services, XR services, and Device to Device (D2D) services.
[0179] Optionally, the list of services supported by the terminal may include, but is not limited to, at least one of the following: URLLC service, eMBB service, emergency service, XR service, and D2D service.
[0180] In some embodiments, the first condition is agreed upon by a protocol, or the first condition is configured by a network-side device.
[0181] In some embodiments, the second condition is agreed upon by a protocol, or the second condition is configured by a network-side device.
[0182] In some embodiments, where the first operation includes activating the target uplink frequency domain resource, the wireless communication method 200 further includes:
[0183] After completing random access, the terminal activates the target uplink frequency domain resource.
[0184] In this embodiment, the target uplink frequency domain resource can be an uplink frequency domain resource that is temporarily activated during the random access process, and the terminal deactivates the target uplink frequency domain resource after completing the random access.
[0185] It should be noted that for multi-active uplink frequency domain resources, it is not necessarily only the initial uplink frequency domain resource that is configured with RO, thereby optimizing uplink transmission during random access. Taking uplink frequency domain resources as an example of uplink BWP, for multi-active UL BWP, it is not necessarily only the initial UL BWP that is configured with RO.
[0186] In some embodiments, the terminal preferentially switches to a non-initial target uplink frequency domain resource that is configured with random access resources. In other words, the target uplink frequency domain resource is a non-initial uplink frequency domain resource configured with random access resources.
[0187] In this embodiment, the terminal selects other non-initial uplink frequency domain resources configured with RO (such as the target uplink frequency domain resource), which helps to balance the random access load (RACH load) among different uplink frequency domain resources, so that the terminal does not have to return to the initial uplink frequency domain resource to initiate random access (RACH).
[0188] In some embodiments, the terminal performs the second operation when initiating random access, including:
[0189] If the third condition is met, the terminal switches to the first target downlink frequency domain resource when initiating random access; and / or,
[0190] If the fourth condition is met, the terminal activates the first target downlink frequency domain resource when initiating random access;
[0191] The third condition includes, but is not limited to, at least one of the following:
[0192] The terminal does not support multiple activations of downlink frequency domain resources; the currently activated downlink frequency domain resource does not enable multiple activations of downlink frequency domain resources; the first target downlink frequency domain resource does not enable multiple activations of downlink frequency domain resources; multiple activations of downlink frequency domain resources are not enabled between the first target downlink frequency domain resource and the currently activated downlink frequency domain resource; the first target downlink frequency domain resource and the currently activated downlink frequency domain resource overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the first target downlink frequency domain resource; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the first target downlink frequency domain resource; the terminal supports... The supported channel bandwidth is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource; the terminal type list supported by the first target downlink frequency domain resource includes at least the terminal type of the terminal; the terminal capability list supported by the first target downlink frequency domain resource includes at least the terminal capability of the terminal; the terminal energy consumption level list supported by the first target downlink frequency domain resource includes at least the terminal energy consumption level of the terminal; the service list supported by the first target downlink frequency domain resource includes at least the service corresponding to the random access initiated by the terminal; random access response resources (such as resources corresponding to Msg2 or MsgB) are configured on the first target downlink frequency domain resource.
[0193] The fourth condition includes, but is not limited to, at least one of the following:
[0194] The terminal supports multiple active downlink frequency domain resources; the currently active downlink frequency domain resource enables multiple active downlink frequency domain resources; the first target downlink frequency domain resource enables multiple active downlink frequency domain resources; multiple active downlink frequency domain resources are enabled between the first target downlink frequency domain resource and the currently active downlink frequency domain resource; the first target downlink frequency domain resource and the currently active downlink frequency domain resource do not overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the first target downlink frequency domain resource; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the first target downlink frequency domain resource; the terminal supports The channel bandwidth of the terminal is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource; the terminal type list supported by the first target downlink frequency domain resource includes at least the terminal type of the terminal; the terminal capability list supported by the first target downlink frequency domain resource includes at least the terminal capability of the terminal; the terminal energy consumption level list supported by the first target downlink frequency domain resource includes at least the terminal energy consumption level of the terminal; the service list supported by the first target downlink frequency domain resource includes at least the service corresponding to the random access initiated by the terminal; random access response resources (such as resources corresponding to Msg2 or MsgB) are configured on the first target downlink frequency domain resource.
[0195] In this embodiment, if the third condition is met, the terminal switches to the first target downlink frequency domain resource when initiating random access; and / or, if the fourth condition is met, the terminal activates the first target downlink frequency domain resource when initiating random access. Thus, the terminal can reasonably perform relevant operations (such as switching, activation, etc.) on the downlink frequency domain resource based on the third and fourth conditions when initiating random access, and can also improve the performance of downlink frequency domain resource scheduling and switching during random access.
[0196] In some embodiments, the third condition is agreed upon by a protocol, or the third condition is configured by a network-side device.
[0197] In some embodiments, the fourth condition is agreed upon by a protocol, or the fourth condition is configured by a network-side device.
[0198] In some embodiments, the serving cell to which the first target downlink frequency domain resource belongs includes a special cell (SpCell).
[0199] In some embodiments, where the second operation includes activating the first target downlink frequency domain resource, the wireless communication method 200 further includes:
[0200] After completing random access, the terminal activates the first target downlink frequency domain resource.
[0201] In this embodiment, the first target downlink frequency domain resource can be a downlink frequency domain resource that is temporarily activated during the random access process. The terminal deactivates the first target downlink frequency domain resource after completing the random access.
[0202] It should be noted that for multiple activated downlink frequency domain resources, it is not necessarily only the initial downlink frequency domain resources that are configured with random access response resources, thereby optimizing downlink transmission during the random access process.
[0203] In some embodiments, the terminal preferentially switches to a non-initial downlink frequency domain resource (such as a first target downlink frequency domain resource) that is configured with random access response resources. In other words, the first target downlink frequency domain resource is a non-initial downlink frequency domain resource that is configured with random access response resources.
[0204] In this embodiment, the terminal selects other non-initial downlink frequency domain resources (such as the first target downlink frequency domain resource) that are configured with random access response resources. This helps to balance the random access load (RACHload) among different downlink frequency domain resources, so that the terminal does not have to return to the initial downlink frequency domain resource to perform random access response.
[0205] In some embodiments, the terminal performs the third operation when initiating random access, including:
[0206] If the fifth condition is met, the terminal switches to the second target downlink frequency domain resource when initiating random access; and / or,
[0207] If the sixth condition is met, the terminal activates the second target downlink frequency domain resource when initiating random access;
[0208] The fifth condition includes, but is not limited to, at least one of the following:
[0209] The terminal does not support multiple activations of downlink frequency domain resources; the currently activated downlink frequency domain resource does not enable multiple activations of downlink frequency domain resources; the second target downlink frequency domain resource does not enable multiple activations of downlink frequency domain resources; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource do not enable multiple activations of downlink frequency domain resources; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; the deactivation timer for at least one activated downlink frequency domain resource is not running;
[0210] The sixth condition includes, but is not limited to, at least one of the following:
[0211] The terminal supports multiple activation of downlink frequency domain resources; the currently activated downlink frequency domain resource enables multiple activation of downlink frequency domain resources; the second target downlink frequency domain resource enables multiple activation of downlink frequency domain resources; multiple activation of downlink frequency domain resources is enabled between the currently activated downlink frequency domain resource and the second target downlink frequency domain resource; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource do not overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; the deactivation timer for at least one activated downlink frequency domain resource is running.
[0212] In this embodiment, if the fifth condition is met, the terminal switches to the second target downlink frequency domain resource when initiating random access; and / or, if the sixth condition is met, the terminal activates the second target downlink frequency domain resource when initiating random access. Thus, the terminal can reasonably perform relevant operations (such as switching, activation, etc.) on the downlink frequency domain resource based on the fifth and sixth conditions when initiating random access, and can also improve the performance of downlink frequency domain resource scheduling and switching during random access.
[0213] In some embodiments, the fifth condition is agreed upon by a protocol, or the fifth condition is configured by a network-side device.
[0214] In some embodiments, the sixth condition is agreed upon by a protocol, or the sixth condition is configured by a network-side device.
[0215] In some embodiments, the identifier of the second target downlink frequency domain resource is the same as the identifier of the first uplink frequency domain resource. Taking a BWP as an example, the second target downlink frequency domain resource can be a BWP.
[0216] In some embodiments, the second target downlink frequency domain resource includes a third target downlink frequency domain resource, the identifier of which is the same as the identifier of the first uplink frequency domain resource. Optionally, the second target downlink frequency domain resource may include at least two downlink frequency domain resources, wherein the third target downlink frequency domain resource may be one of the at least two downlink frequency domain resources. Taking a BWP as an example, the second target downlink frequency domain resource may be an aggregation of multiple discrete BWPs.
[0217] In some embodiments, the wireless communication method 200 further includes:
[0218] The terminal deactivates K downlink frequency domain resources;
[0219] In this context, the deactivation timers for the K downlink frequency domain resources are not running, where K is a positive integer.
[0220] In this embodiment, the terminal deactivates K downlink frequency domain resources, wherein the deactivation timers for the K downlink frequency domain resources are not running, thereby reducing the terminal power consumption caused by activating downlink frequency domain resources.
[0221] It should be noted that the deactivation timer for the activated downlink frequency domain resource is running, indicating that the activated downlink frequency domain resource may be continuously receiving scheduling based on other services. Therefore, deactivation may not be performed on it.
[0222] For example, taking the following frequency domain resource as a BWP, perform deactivation operations on K active DL BWPs where the deactivation timer (bwp-inactivityTimer) is not running.
[0223] In some embodiments, the wireless communication method 200 further includes:
[0224] The terminal receives first configuration information from the network-side device;
[0225] The first configuration information includes, but is not limited to, at least one of the following:
[0226] Information on the deactivation timers for N downlink frequency domain resources;
[0227] The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources.
[0228] The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate multiple downlink frequency domain resources;
[0229] The third indication information is used to indicate the characteristic set of M uplink frequency domain resources;
[0230] The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources;
[0231] The fifth indication information is used to indicate that each of the M uplink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0232] The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0233] Wherein, the M uplink frequency domain resources include the target uplink frequency domain resources, and the N downlink frequency domain resources include, but are not limited to, at least one of the following: the first target downlink frequency domain resources, the second target downlink frequency domain resources, and the third target downlink frequency domain resources;
[0234] The characteristic set of each uplink frequency domain resource in the M uplink frequency domain resources includes, but is not limited to, at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0235] The characteristic set of each downlink frequency domain resource in the N downlink frequency domain resources includes, but is not limited to, at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0236] Where M and N are both positive integers.
[0237] In this embodiment, the terminal can activate or switch uplink frequency domain resources during random access based on the first configuration information, and / or the terminal can activate or switch downlink frequency domain resources during random access based on the first configuration information, thereby improving the uplink and downlink transmission performance during random access, and also improving the scheduling and switching performance of uplink and downlink frequency domain resources during random access.
[0238] Optionally, the first configuration information can be carried by at least one of the following:
[0239] RRC signaling, Downlink Control Information (DCI), and Media Access Control Element (MAC CE) signaling.
[0240] The above text combined Figure 2 The terminal-side embodiments of this application are described in detail below, in conjunction with... Figure 3 The network-side embodiments of this application are described in detail below. It should be understood that the network-side embodiments correspond to the terminal-side embodiments, and similar descriptions can be found in the terminal-side embodiments.
[0241] Figure 3 This is a schematic flowchart of a wireless communication method 300 according to an embodiment of this application, such as... Figure 3 As shown, the wireless communication method 300 may include at least some of the following:
[0242] S310, the network-side device sends the first configuration information to the terminal;
[0243] The first configuration information includes at least one of the following:
[0244] Information on the deactivation timers for N downlink frequency domain resources;
[0245] The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources.
[0246] The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate multiple downlink frequency domain resources;
[0247] The third indication information is used to indicate the characteristic set of M uplink frequency domain resources;
[0248] The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources;
[0249] The fifth indication information is used to indicate that each of the M uplink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0250] The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0251] The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0252] The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0253] Where M and N are both positive integers.
[0254] It should be understood that Figure 3 The steps or operations of the wireless communication method 300 are illustrated, but these steps or operations are merely examples, and other operations may be performed in this application. Figure 3 Variations of various operations within it.
[0255] The frequency domain resources described in the embodiments of this application can be equivalent to or replaced with BWP or other similar descriptions such as small bandwidth or micro bandwidth. For example, uplink frequency domain resources can be equivalent to or replaced with uplink BWP, and downlink frequency domain resources can be equivalent to or replaced with downlink BWP. This application does not limit this.
[0256] In this embodiment, the terminal can activate or switch uplink frequency domain resources during random access based on the first configuration information, and / or the terminal can activate or switch downlink frequency domain resources during random access based on the first configuration information, thereby improving the uplink and downlink transmission performance during random access, and also improving the scheduling and switching performance of uplink and downlink frequency domain resources during random access.
[0257] The channel bandwidth list described in this application embodiment can also be replaced with a channel bandwidth combination or a channel bandwidth set. The BWP bandwidth list described in this application embodiment can also be replaced with a BWP bandwidth combination or a BWP bandwidth set. The terminal type list described in this application embodiment can also be replaced with a terminal type combination or a terminal type set. The terminal capability list described in this application embodiment can also be replaced with a terminal capability combination or a terminal capability set. The terminal energy consumption level list described in this application embodiment can also be replaced with a terminal energy consumption level combination or a terminal energy consumption level set. The service list described in this application embodiment can also be replaced with a service combination or a service set. This application embodiment is not limited in this respect.
[0258] Optionally, the second target downlink frequency domain resource may include at least two downlink frequency domain resources, wherein the third target downlink frequency domain resource may be one of the at least two downlink frequency domain resources. Taking a BWP as an example, the second target downlink frequency domain resource may be an aggregation of multiple discrete BWPs.
[0259] Optionally, the first configuration information can be carried by at least one of the following:
[0260] RRC signaling, DCI, MAC CE signaling.
[0261] Optionally, the terminal type can be IoT terminal, A-IoT terminal, RedCap terminal, NTN terminal, VSAT terminal, A-IoT+RedCap terminal, A-IoT+NTN terminal, IoT+NTN terminal, etc.
[0262] It should be noted that an A-IoT+RedCap terminal indicates that the terminal can support both A-IoT and RedCap features simultaneously, such as a RedCap terminal equipped with an A-IoT module. A-IoT+NTN terminals, IoT+NTN terminals, etc. are similar, and will not be elaborated further here.
[0263] Optionally, the list of terminal types may include, but is not limited to, at least one of the following: IoT terminal, A-IoT terminal, RedCap terminal, NTN terminal, VSAT terminal.
[0264] Optionally, the terminal's capabilities can include whether the terminal supports multiple active uplink frequency domain resources, the number of receive antennas or transmit antennas supported by the terminal, and the channel bandwidth or BWP bandwidth supported by the terminal.
[0265] Optionally, the terminal's terminal capability list may include, but is not limited to, at least one of the following: whether the terminal supports multiple active uplink frequency domain resources, the number of receive antennas or transmit antennas supported by the terminal, and the channel bandwidth or BWP bandwidth supported by the terminal.
[0266] It should be noted that the terminal's terminal energy consumption level can also be understood or replaced as the terminal's terminal energy consumption status.
[0267] For example, the terminal energy consumption level indicates the level of energy consumption of the terminal when performing a service. If the terminal is performing extended reality (XR) service, it is a high power consumption service.
[0268] For example, the terminal's power consumption status indicates the terminal's current remaining battery energy, such as when the terminal's remaining power is low.
[0269] Optionally, the terminal can support services such as URLLC, eMBB, emergency, XR, and D2D.
[0270] Optionally, the list of services supported by the terminal may include, but is not limited to, at least one of the following: URLLC service, eMBB service, emergency service, XR service, and D2D service.
[0271] Figure 4 This is a schematic flowchart of a wireless communication method 400 according to an embodiment of this application, such as... Figure 4 As shown, the wireless communication method 400 may include at least some of the following:
[0272] S410, the terminal performs the fourth operation when initiating random access; or, the terminal performs the fifth operation when initiating random access.
[0273] The fourth operation includes one of the following: stopping the deactivation timer of some or all downlink frequency domain resources that are active, or not stopping the deactivation timer of some or all downlink frequency domain resources that are active.
[0274] The fifth operation includes performing a random access procedure using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell, wherein random access resources are configured on the first uplink frequency domain resources.
[0275] It should be understood that Figure 4 The steps or operations of the wireless communication method 400 are illustrated, but these steps or operations are merely examples, and other operations may be performed in this application. Figure 4 Variations of various operations within it.
[0276] In this embodiment, the terminal can be in an RRC connected state. Of course, the terminal can also be in other RRC states, and this application is not limited to this.
[0277] It should be noted that when a terminal initiates random access, in order not to affect the reception of the Random Access Response (RAR) or subsequent scheduling, the running deactivation timer needs to be stopped. When the network side is configured with multiple active downlink frequency domain resources, or the terminal supports multiple active downlink frequency domain resources, some active downlink frequency domain resources need to remain active, while other active downlink frequency domain resources do not necessarily need to remain active (e.g., downlink frequency domain resources that the network side does not send RARs to), then it is necessary to stop some or all of the running deactivation timers.
[0278] In this embodiment, when initiating random access, the terminal may either deactivate the deactivation timers for some or all of the activated downlink frequency domain resources, or not deactivate them. This allows for the efficient use of downlink frequency domain resources and improves the performance of downlink frequency domain resource scheduling and handover during random access. Alternatively, when initiating random access, the terminal may use the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell to perform the random access procedure. This improves random access performance and also enhances the performance of uplink and downlink frequency domain resource scheduling and handover during random access.
[0279] The deactivation timer described in this application embodiment can also be called an inactive timer, and this application does not limit it to that.
[0280] The frequency domain resources described in the embodiments of this application can be equivalent to or replaced with BWP or other similar descriptions such as small bandwidth or micro bandwidth. For example, uplink frequency domain resources can be equivalent to or replaced with uplink BWP, and downlink frequency domain resources can be equivalent to or replaced with downlink BWP. This application does not limit this.
[0281] In some embodiments, the first cell and the second cell may be the same or different, and this application embodiment does not limit this.
[0282] In some embodiments, during S410 described above, the terminal performs a fourth operation when initiating random access, including:
[0283] The terminal executes the fourth operation based on the running status of the deactivation timer for partially or fully activated downlink frequency domain resources of the serving cell; or,
[0284] If the serving cell is a secondary cell, the terminal performs the fourth operation based on the running status of the deactivation timer of the partially or fully activated downlink frequency domain resources of the SpCell.
[0285] In some embodiments, the terminal performs the fourth operation based on the running status of the deactivation timer for some or all of the activated downlink frequency domain resources of the serving cell, including at least one of the following:
[0286] If all active downlink frequency domain resources of the serving cell are running deactivation timers, the terminal stops all active downlink frequency domain resources of the serving cell from running deactivation timers.
[0287] If the deactivation timers for all active downlink frequency domain resources of the serving cell are running, the terminal stops the deactivation timers for the active target downlink frequency domain resources of the serving cell.
[0288] If the deactivation timer for at least one active downlink frequency domain resource of the serving cell is running, the terminal stops the deactivation timers for all active downlink frequency domain resources of the serving cell.
[0289] If the deactivation timer for at least one active downlink frequency domain resource of the serving cell is not running, the terminal does not stop the deactivation timers for all active downlink frequency domain resources of the serving cell.
[0290] If the deactivation timer for at least one active downlink frequency domain resource of the serving cell is running, the terminal stops the deactivation timer for the active target downlink frequency domain resource of the serving cell.
[0291] If the deactivation timer for at least one active downlink frequency domain resource of the serving cell does not run, the terminal does not stop the deactivation timer for the active target downlink frequency domain resource of the serving cell.
[0292] If the serving cell has only one active downlink frequency domain resource, and the deactivation timer of the active downlink frequency domain resource is running, the terminal stops the deactivation timer of the active downlink frequency domain resource.
[0293] In this embodiment, the terminal can determine whether to stop the deactivation timer of the activated downlink frequency domain resources based on the running status of the deactivation timer of the activated downlink frequency domain resources in the serving cell, thereby enabling more flexible control over the deactivation timer of the activated downlink frequency domain resources in the serving cell.
[0294] In some embodiments, the terminal performs the fourth operation based on the running status of the deactivation timer for some or all of the activated downlink frequency domain resources of SpCell, including at least one of the following:
[0295] If all active downlink frequency domain resources of the SpCell are running deactivation timers, the terminal stops all active downlink frequency domain resources of the SpCell from running.
[0296] If all the deactivation timers for the active downlink frequency domain resources of the SpCell are running, the terminal stops the deactivation timer for the active target downlink frequency domain resource of the SpCell.
[0297] If the deactivation timer of at least one active downlink frequency domain resource of the SpCell is running, the terminal stops the deactivation timers of all active downlink frequency domain resources of the SpCell.
[0298] If the deactivation timer of at least one active downlink frequency domain resource of the SpCell does not run, the terminal does not stop the deactivation timers of all active downlink frequency domain resources of the SpCell.
[0299] If the deactivation timer of at least one active downlink frequency domain resource of the SpCell is running, the terminal stops the deactivation timer of the active target downlink frequency domain resource of the SpCell;
[0300] If the deactivation timer of at least one active downlink frequency domain resource of the SpCell does not run, the terminal does not stop the deactivation timer of the active target downlink frequency domain resource of the SpCell;
[0301] If the SpCell has only one active downlink frequency domain resource, and the deactivation timer of the active downlink frequency domain resource is running, the terminal stops the deactivation timer of the active downlink frequency domain resource.
[0302] In this embodiment, the terminal can determine whether to stop the deactivation timer of the active downlink frequency domain resource based on the running status of the deactivation timer of the active downlink frequency domain resource in the SpCell, thereby enabling more flexible control over the deactivation timer of the active downlink frequency domain resource in the SpCell.
[0303] In some embodiments, the target downlink frequency domain resource satisfies at least one of the following:
[0304] The target downlink frequency domain resource is indicated by the network side; the identifier of the target downlink frequency domain resource is the same as the identifier of the activated uplink frequency domain resource; the identifier of the target downlink frequency domain resource is the same as the identifier of the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource is a downlink frequency domain resource associated with the activated uplink frequency domain resource; the target downlink frequency domain resource is a downlink frequency domain resource associated with the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource includes downlink frequency domain resources with the same identifier as the activated uplink frequency domain resource; the target downlink frequency domain resource includes downlink frequency domain resources with the same identifier as the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource includes downlink frequency domain resources associated with the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource includes downlink frequency domain resources associated with the activated uplink frequency domain resource configured with random access resources.
[0305] In some embodiments, the first cell is SpCell and the second cell is the serving cell. In S410 above, when the terminal initiates random access, it performs a fifth operation, including at least one of the following:
[0306] If the serving cell is a secondary cell, the SpCell includes at least two active downlink frequency domain resources, and the at least two active downlink frequency domain resources include the first downlink frequency domain resource. The terminal uses the first downlink frequency domain resource and the first uplink frequency domain resource to perform a random access procedure.
[0307] If the serving cell is a secondary cell, and the SpCell only includes the activated first downlink frequency domain resources, the terminal uses the first downlink frequency domain resources and the first uplink frequency domain resources to perform a random access procedure;
[0308] If the serving cell is a secondary cell, and the SpCell includes an inactive first downlink frequency domain resource, the terminal activates the first downlink frequency domain resource, and the terminal uses the first downlink frequency domain resource and the first uplink frequency domain resource to perform a random access procedure.
[0309] In this embodiment, the first cell is SpCell and the second cell is the serving cell. When the terminal initiates random access, it uses the first downlink frequency domain resources activated by SpCell and the first uplink frequency domain resources activated by the serving cell to perform the random access process, thereby improving the performance of random access and the performance of uplink and downlink frequency domain resource scheduling and handover during random access.
[0310] In some embodiments, the association between the first downlink frequency domain resource and the first uplink frequency domain resource is indicated by the network side. Therefore, the terminal can obtain the association between the first downlink frequency domain resource and the first uplink frequency domain resource based on the network side indication.
[0311] In some embodiments, the association between the first downlink frequency domain resource and the first uplink frequency domain resource is indicated by the network side when activating at least one of the following functions: multi-activation of uplink frequency domain resources function, multi-activation of downlink frequency domain resources function.
[0312] The multi-active uplink frequency domain resources and multi-active downlink frequency domain resources described in the embodiments of this application can also be unified as multi-active frequency domain resources, and the embodiments of this application do not limit this.
[0313] The technical solution of this application is described in detail below through specific embodiments.
[0314] Example 1, taking frequency domain resources as BWP as an example. Specifically, Example 1 uses the following scheme as an example: When the terminal initiates random access, if the first activated uplink BWP does not have PRACH occasion resources configured, the terminal performs uplink BWP handover or activation, or the terminal performs downlink BWP handover or activation.
[0315] The main idea of Example 1 is as follows: 1. Define a set of features related to BWP so that the network side does not need to allocate a separate BWP for each potential new UE type and UE capability in the future; 2. When the network side configures a multi-active BWP (or configures a multi-active UL BWP and / or a multi-active DL BWP), or the terminal supports a multi-active BWP (or supports a multi-active UL BWP and / or a multi-active DL BWP), the terminal will change some BWP switching operations into BWP activation operations. For the currently active downlink BWP, whether to perform a deactivation operation depends on whether the deactivation timer (bwp-inactivityTimer) is running.
[0316] Optionally, such as Figure 5 As shown, Embodiment 1 may include some or all of the steps in S1-1 to S1-3.
[0317] S1-1. The terminal receives first configuration information from the network-side device, including at least one of the following:
[0318] Information on the deactivation timers (bwp-inactivityTimer) of N downlink BWPs;
[0319] The first indication information is used to indicate whether the M uplink BWPs are enabled to activate multiple uplink BWPs;
[0320] The second indication information is used to indicate whether N downlink BWPs are enabled to activate multiple downlink BWPs;
[0321] The third indication information is used to indicate the feature set of M uplink BWPs;
[0322] The fourth indication information is used to indicate the feature set of N downlink BWPs;
[0323] The fifth indication information is used to indicate that each of the M uplink BWPs supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0324] The sixth indication information is used to indicate that each of the N downlink BWPs supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0325] The feature set of each uplink BWP in the M uplink BWPs includes, but is not limited to, at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0326] The feature set of each downlink BWP in the N downlink BWPs includes, but is not limited to, at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0327] Where M and N are both positive integers.
[0328] Optionally, the first configuration information can be carried by at least one of the following:
[0329] RRC signaling, DCI, MAC CE signaling.
[0330] Optionally, the terminal type can be IoT terminal, A-IoT terminal, RedCap terminal, NTN terminal, VSAT terminal, A-IoT+RedCap terminal, A-IoT+NTN terminal, IoT+NTN terminal, etc.
[0331] It should be noted that an A-IoT+RedCap terminal indicates that the terminal can support both A-IoT and RedCap features simultaneously, such as a RedCap terminal equipped with an A-IoT module. A-IoT+NTN terminals, IoT+NTN terminals, etc. are similar, and will not be elaborated further here.
[0332] Optionally, the list of terminal types may include, but is not limited to, at least one of the following: IoT terminal, A-IoT terminal, RedCap terminal, NTN terminal, VSAT terminal.
[0333] Optionally, the terminal's capabilities can include whether the terminal supports multiple active uplink frequency domain resources, the number of receive antennas or transmit antennas supported by the terminal, and the channel bandwidth or BWP bandwidth supported by the terminal.
[0334] Optionally, the terminal's terminal capability list may include, but is not limited to, at least one of the following: whether the terminal supports multiple active uplink frequency domain resources, the number of receive antennas or transmit antennas supported by the terminal, and the channel bandwidth or BWP bandwidth supported by the terminal.
[0335] It should be noted that the terminal's terminal energy consumption level can also be understood or replaced as the terminal's terminal energy consumption status.
[0336] For example, the terminal energy consumption level indicates the level of energy consumption of the terminal when performing a service. If the terminal is performing extended reality (XR) service, it is a high power consumption service.
[0337] For example, the terminal's power consumption status indicates the terminal's current remaining battery energy, such as when the terminal's remaining power is low.
[0338] Optionally, the terminal can support services such as URLLC, eMBB, emergency, XR, and D2D.
[0339] Optionally, the list of services supported by the terminal may include, but is not limited to, at least one of the following: URLLC service, eMBB service, emergency service, XR service, and D2D service.
[0340] S1-2. The terminal initiates a random access procedure. Optionally, the terminal performs carrier selection in S1-2.
[0341] S1-3. When the terminal initiates random access, it performs the first operation, the second operation, or the third operation depending on whether random access resources (such as PRACH occasions) are configured on the activated first uplink BWP.
[0342] The first operation includes one of the following:
[0343] Switch to the target uplink BWP and activate the target uplink BWP;
[0344] The second operation includes one of the following:
[0345] Switch to the first target downlink BWP and activate the first target downlink BWP;
[0346] The third operation includes one of the following:
[0347] Switch to the second target downlink BWP and activate the second target downlink BWP.
[0348] Optionally, if no random access resources (such as PRACH occasions) are configured on the first uplink BWP, the terminal performs the first operation when initiating random access, or the terminal performs the second operation when initiating random access; if random access resources (such as PRACH occasions) are configured on the first uplink BWP, the terminal performs the third operation when initiating random access.
[0349] Optionally, the terminal performs a first operation when initiating random access, including:
[0350] If the first condition is met, the terminal switches to the target uplink BWP when initiating random access;
[0351] And / or,
[0352] If the second condition is met, the terminal activates the target uplink BWP when initiating random access;
[0353] The first condition includes, but is not limited to, at least one of the following:
[0354] The terminal does not support multiple active uplink BWPs; the first uplink BWP does not enable multiple active uplink BWPs; the target uplink BWP does not enable multiple active uplink BWPs; multiple active uplink BWPs are not enabled between the first uplink BWP and the target uplink BWP; the first uplink BWP and the target uplink BWP overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the target uplink BWP; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the target uplink BWP; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the target uplink BWP; the terminal supports channels... The target uplink BWP supports the following: a bandwidth greater than or equal to the smallest channel bandwidth in the target uplink BWP's supported channel bandwidth list; a terminal-supported channel bandwidth greater than or equal to the smallest BWP bandwidth in the target uplink BWP's supported BWP bandwidth list; a target uplink BWP's supported terminal type list including at least the terminal's terminal type; a target uplink BWP's supported terminal capability list including at least the terminal's terminal capabilities; a target uplink BWP's supported terminal energy consumption level list including at least the terminal's terminal energy consumption level; a target uplink BWP's supported service list including at least the service corresponding to the random access initiated by the terminal; and random access resources configured on the target uplink BWP (such as resources corresponding to Msg1 or MsgA).
[0355] The second condition includes, but is not limited to, at least one of the following:
[0356] The terminal supports multiple active uplink BWPs; the first uplink BWP enables multiple active uplink BWPs; the target uplink BWP enables multiple active uplink BWPs; multiple active uplink BWPs are enabled between the first uplink BWP and the target uplink BWP; the first uplink BWP and the target uplink BWP do not overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth supported by the target uplink BWP or the BWP bandwidth; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the list of channel bandwidths supported by the target uplink BWP; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the list of BWP bandwidths supported by the target uplink BWP; the channel bandwidth supported by the terminal... The target uplink BWP must support a channel bandwidth greater than or equal to the smallest channel bandwidth in its supported channel bandwidth list; the terminal must support a channel bandwidth greater than or equal to the smallest BWP bandwidth in its supported BWP bandwidth list; the target uplink BWP must support a terminal type list that includes at least the terminal type; the target uplink BWP must support a terminal capability list that includes at least the terminal capability; the target uplink BWP must support a terminal energy consumption level list that includes at least the terminal energy consumption level; the target uplink BWP must support a service list that includes at least the service corresponding to the random access initiated by the terminal; and the target uplink BWP must be configured with random access resources (such as resources corresponding to Msg1 or MsgA).
[0357] In some implementations, if the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the target uplink BWP, the terminal switches to the target uplink BWP or activates the target uplink BWP.
[0358] In some implementations, if the target uplink BWP supports a list of BWP bandwidths or a combination of BWP bandwidths, and the channel bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth or any BWP bandwidth or the minimum BWP bandwidth in the list of BWP bandwidths or the combination of BWP bandwidths supported by the target uplink BWP, then the terminal switches to the target uplink BWP, or the terminal activates the target uplink BWP.
[0359] In some implementations, if the terminal type of the terminal is the first terminal type, and the terminal types supported by the target uplink BWP include the first terminal type, then the terminal switches to the target uplink BWP, or the terminal activates the target uplink BWP.
[0360] In some implementations, if the terminal types supported by the target uplink BWP are a list of terminal types or a combination of terminal types, and the terminal type of the terminal is included in the list of terminal types or the combination of terminal types supported by the target uplink BWP, or the terminal type of the terminal satisfies the combination of all or some elements in the list of terminal types or the combination of terminal types supported by the target uplink BWP, then the terminal switches to the target uplink BWP, or the terminal activates the target uplink BWP.
[0361] In some implementations, if the terminal's terminal capabilities are included in the terminal capabilities supported by the target uplink BWP, then the terminal switches to the target uplink BWP, or the terminal activates the target uplink BWP.
[0362] In some implementations, if the terminal's power consumption level or power consumption status is included in the power consumption level or power consumption status supported by the target uplink BWP, then the terminal switches to the target uplink BWP or activates the target uplink BWP.
[0363] In some implementations, if the terminal initiates random access for the first service, and the services supported by the target uplink BWP include the first service, then the terminal switches to the target uplink BWP, or the terminal activates the target uplink BWP.
[0364] In some implementations, if the target uplink BWP is configured with random access resources (such as PRACH occasions), the terminal switches to the target uplink BWP or the terminal activates the target uplink BWP.
[0365] For multi-active BWPs, it's not necessarily only the initial BWP that has RO configured.
[0366] In this embodiment, the UE selects other non-initial BWPs configured with RO, which helps to balance the RACH load among different BWPs, so that the UE does not have to return to the initial BWP to initiate RACH.
[0367] Optionally, the terminal may prioritize switching to a non-initial BWP that is configured with random access resources.
[0368] Optionally, deactivation is performed on K active DL BWPs where bwp-inactivityTimer is not running.
[0369] Optionally, once the random access procedure is complete, the terminal performs a deactivation operation on the target uplink BWP.
[0370] Optionally, the terminal performs a second operation when initiating random access, including:
[0371] If the third condition is met, the terminal switches to the first target downlink BWP when initiating random access; and / or, if the fourth condition is met, the terminal activates the first target downlink BWP when initiating random access.
[0372] The third condition includes, but is not limited to, at least one of the following:
[0373] The terminal does not support multiple activated downlink BWPs; the currently activated downlink BWP does not enable multiple activated downlink BWPs; the first target downlink BWP does not enable multiple activated downlink BWPs; multiple activated downlink BWPs are not enabled between the first target downlink BWP and the currently activated downlink BWP; the first target downlink BWP and the currently activated downlink BWP overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink BWP; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the list of channel bandwidths supported by the first target downlink BWP; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the list of BWP bandwidths supported by the first target downlink BWP; the terminal supports... The channel bandwidth is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink BWP; the channel bandwidth supported by the terminal is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink BWP; the list of terminal types supported by the first target downlink BWP includes at least the terminal type; the list of terminal capabilities supported by the first target downlink BWP includes at least the terminal capabilities; the list of terminal energy consumption levels supported by the first target downlink BWP includes at least the terminal energy consumption level; the list of services supported by the first target downlink BWP includes at least the services corresponding to the random access initiated by the terminal; and the first target downlink BWP is configured with random access response resources (such as resources corresponding to Msg2 or MsgB).
[0374] The fourth condition includes, but is not limited to, at least one of the following:
[0375] The terminal supports multiple active downlink BWPs; the currently active downlink BWP enables multiple active downlink BWPs; the first target downlink BWP enables multiple active downlink BWPs; multiple active downlink BWPs are enabled between the first target downlink BWP and the currently active downlink BWP; the first target downlink BWP and the currently active downlink BWP do not overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink BWP; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the list of channel bandwidths supported by the first target downlink BWP; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the list of BWP bandwidths supported by the first target downlink BWP; the terminal supports multiple active downlink BWPs. The channel bandwidth is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink BWP; the channel bandwidth supported by the terminal is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink BWP; the list of terminal types supported by the first target downlink BWP includes at least the terminal type; the list of terminal capabilities supported by the first target downlink BWP includes at least the terminal capabilities; the list of terminal energy consumption levels supported by the first target downlink BWP includes at least the terminal energy consumption level; the list of services supported by the first target downlink BWP includes at least the services corresponding to the random access initiated by the terminal; and the first target downlink BWP is configured with random access response resources (such as resources corresponding to Msg2 or MsgB).
[0376] Optionally, the terminal performs a third operation when initiating random access, including:
[0377] If the fifth condition is met, the terminal switches to the second target downlink BWP when initiating random access; and / or, if the sixth condition is met, the terminal activates the second target downlink BWP when initiating random access.
[0378] The fifth condition includes, but is not limited to, at least one of the following:
[0379] The terminal does not support multiple activation of downlink BWPs; the currently activated downlink BWP does not enable multiple activation of downlink BWPs; the second target downlink BWP does not enable multiple activation of downlink BWPs; multiple activation of downlink BWPs is not enabled between the currently activated downlink BWP and the second target downlink BWP; the currently activated downlink BWP and the second target downlink BWP overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one activated downlink BWP does not contain a downlink BWP with the same identifier as the first uplink BWP; at least one activated downlink BWP does not contain a downlink BWP with the same identifier as the first uplink BWP; the deactivation timer of at least one activated downlink BWP is not running;
[0380] The sixth condition includes, but is not limited to, at least one of the following:
[0381] The terminal supports multiple active downlink BWPs; the currently active downlink BWP enables multiple active downlink BWPs; the second target downlink BWP enables multiple active downlink BWPs; multiple active downlink BWPs are enabled between the currently active downlink BWP and the second target downlink BWP; the currently active downlink BWP and the second target downlink BWP do not overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one active downlink BWP does not contain a downlink BWP with the same identifier as the first uplink BWP; at least one active downlink BWP does not contain a downlink BWP with the same identifier as the first uplink BWP; the deactivation timer for at least one active downlink BWP is running.
[0382] In some implementations, if the serving cell is SpCell and none of the at least one active downlink BWP has the same BWP identifier (bwp-ID) as the first uplink BWP, the terminal activates a second target downlink BWP when initiating random access, wherein the bwp-ID of the second target downlink BWP is the same as the bwp-ID of the first uplink BWP. For example, if the bwp-ID of the currently active downlink BWP is 2 and the bwp-ID of the first uplink BWP is 3, then the terminal activates the downlink BWP with bwp-ID = 3 (i.e., the second target downlink BWP is the downlink BWP with bwp-ID = 3). Optionally, the bwp-inactivityTimer of the at least one active downlink BWP is running. Optionally, the first configuration information indicates that the second target downlink BWP supports multi-active downlink BWP, or the first configuration information indicates that the second target downlink BWP supports multi-active BWP. Optionally, the terminal supports multi-active downlink BWP (DL BWP), or the terminal supports multiple active BWPs (BWPs). Optionally, deactivation operations are performed on the K active downlink BWPs where the bwp-inactivityTimer is not running. Optionally, after the random access procedure is completed, the terminal performs a deactivation operation on the second target downlink BWP.
[0383] In some implementations, if the serving cell is SpCell and none of the at least one active downlink BWP has the same BWP identifier (bwp-ID) as the first uplink BWP, the terminal switches to the second target downlink BWP, where the bwp-ID of the second target downlink BWP is the same as the bwp-ID of the first uplink BWP. Optionally, the bwp-inactivityTimer of the at least one active downlink BWP is not running. Optionally, the first configuration information indicates that the second target downlink BWP does not support multi-active downlink BWPs, or the first configuration information indicates that the second target downlink BWP does not support multi-active BWPs. Optionally, the terminal does not support multi-active downlink BWPs, or the terminal does not support multi-active BWPs. Optionally, a deactivation operation is performed on the K active downlink BWPs whose bwp-inactivityTimer is not running.
[0384] In some implementations, if none of the at least one active downlink BWPs has the same bwp-ID as the first uplink BWP, the terminal activates a second target downlink BWP when initiating random access, wherein the bwp-ID of the second target downlink BWP is the same as the bwp-ID of the first uplink BWP. For example, if the bwp-ID of the currently active downlink BWP is 2 and the bwp-ID of the first uplink BWP is 3, then the terminal activates the downlink BWP with bwp-ID = 3 (i.e., the second target downlink BWP is the downlink BWP with bwp-ID = 3). Optionally, the bwp-inactivityTimer of the at least one active downlink BWP is running. Optionally, the first configuration information indicates that the second target downlink BWP does not support multi-active downlink BWPs, or the first configuration information indicates that the second target downlink BWP does not support multi-active BWPs. Optionally, the terminal does not support multi-active downlink BWPs (DL BWPs), or the terminal does not support multi-active BWPs. Optionally, deactivation operations are performed on the K active downlink BWPs whose bwp-inactivityTimer is not running. Optionally, after the random access procedure is completed, the terminal performs deactivation operations on the second target downlink BWP.
[0385] In some implementations, if none of the at least one active downlink BWPs has the same BWP identifier (bwp-ID) as the first uplink BWP, the terminal switches to a second target downlink BWP, wherein the bwp-ID of the second target downlink BWP is the same as the bwp-ID of the first uplink BWP. Optionally, the bwp-inactivityTimer of the at least one active downlink BWP is not running. Optionally, the first configuration information indicates that the second target downlink BWP does not support multi-active downlink BWPs, or the first configuration information indicates that the second target downlink BWP does not support multi-active BWPs. Optionally, the terminal does not support multi-active downlink BWPs, or the terminal does not support multi-active BWPs. Optionally, a deactivation operation is performed on the K active downlink BWPs whose bwp-inactivityTimer is not running.
[0386] Example 2, taking frequency domain resources as BWP as an example. Specifically, Example 2 uses the following scheme as an example: when the terminal initiates random access, the bwp-inactivityTimer is used to process the running active downlink BWP (active DL BWP).
[0387] The main idea of this embodiment is that when a terminal initiates random access, in order not to affect RAR reception or subsequent scheduling, it needs to stop the running bwp-inactivityTimer. When the network side is configured with multi-active BWP (or configured with multi-active UL BWP and / or multi-active DL BWP), or the terminal supports multi-active BWP (or supports multi-active UL BWP and / or multi-active DL BWP), some active downlink BWPs need to remain active, while other active downlink BWPs do not necessarily need to remain active (e.g., DLBWPs that do not transmit RAR on the network side), then it is not necessary to stop the running bwp-inactivityTimer of the serving cell.
[0388] Optionally, such as Figure 6 As shown, Embodiment 2 may include some or all of the steps in S2-1 to S2-3.
[0389] S2-1. The terminal receives second configuration information from the network-side device, including at least one of the following:
[0390] BWP deactivates the timer bwp-inactivityTimer;
[0391] Downlink BWP associated with an uplink BWP configured with random access resources.
[0392] For example, when a terminal initiates random access using the active UL BWP on the SpCell, the network-side device can instruct the terminal to use the DL BWP associated with the active UL BWP during the random access process. For instance, if a UE initiates RACH using the active UL BWP with bwp-ID=2 on the SpCell, and the network indicates that the UL BWP with bwp-ID=2 is associated with the DL BWP with bwp-ID=3, then the UE's random access on the SpCell will use both the active UL BWP with bwp-ID=2 and the active DL BWP with bwp-ID=3.
[0393] For example, when a terminal initiates random access on the active UL BWP of an SCell, the network-side device can instruct the terminal to use the SpCell DL BWP associated with the active UL BWP during the random access process. For instance, if a UE initiates RACH on the active UL BWP with bwp-ID=1 in an SCell, and the NW indicates that the SCell UL BWP with bwp-ID=1 is associated with the SpCell DL BWP with bwp-ID=4, then the UE's random access on the SCell will use both the active UL BWP with bwp-ID=1 and the active DL BWP with bwp-ID=4.
[0394] Optionally, when activating the multi-active BWP or multi-active DL BWP function, the network-side device may indicate the DL BWP associated with the UL BWP configured with random access resources.
[0395] This can be understood as follows: if the network-side device only activates a single-active downlink BWP, the UE will use this active DL BWP for random access. The network-side device does not need to separately indicate which active DL BWP the UE should use for downlink information when activating a multi-active DL BWP.
[0396] S2-2. The terminal initiates a random access procedure. Optionally, the terminal performs carrier selection in S2-2. Optionally, the terminal initiates a random access procedure in the serving cell.
[0397] S2-3. The terminal performs the fourth operation when initiating random access; or the terminal performs the fifth operation when initiating random access;
[0398] The fourth operation includes one of the following: stopping the deactivation timer of some or all of the downlink BWPs that are active, or not stopping the deactivation timer of some or all of the downlink BWPs that are active.
[0399] The fifth operation includes performing a random access procedure using an activated first downlink BWP of the SpCell and an activated first uplink BWP of the serving cell, wherein random access resources are configured on the first uplink BWP.
[0400] Optionally, the terminal performs a fourth operation when initiating random access, including:
[0401] The terminal executes the fourth operation based on the deactivation timer status of the partially or fully activated downlink BWP of the serving cell; or,
[0402] If the serving cell is a secondary cell, the terminal performs the fourth operation based on the deactivation timer of the partially or fully activated downlink BWP of the SpCell.
[0403] Optionally, the terminal performs the fourth operation based on the deactivation timer status of the partially or fully activated downlink BWP of the serving cell, including at least one of the following:
[0404] If the deactivation timers for all active downlink BWPs in the serving cell are running, the terminal stops the deactivation timers for all active downlink BWPs in the serving cell.
[0405] If the deactivation timers of all active downlink BWPs in the serving cell are running, the terminal stops the deactivation timer of the target downlink BWP of the serving cell.
[0406] If the deactivation timer of at least one active downlink BWP of the serving cell is running, the terminal stops the deactivation timers of all active downlink BWPs of the serving cell.
[0407] If the deactivation timer of at least one active downlink BWP of the serving cell does not run, the terminal does not stop the deactivation timers of all active downlink BWPs of the serving cell.
[0408] If the deactivation timer of at least one active downlink BWP of the serving cell is running, the terminal stops the deactivation timer of the target downlink BWP of the serving cell.
[0409] If the deactivation timer of at least one active downlink BWP of the serving cell does not run, the terminal does not stop the deactivation timer of the target downlink BWP of the serving cell.
[0410] If the serving cell has only one active downlink BWP, and the deactivation timer of the active downlink BWP is running, the terminal stops the deactivation timer of the active downlink BWP.
[0411] Optionally, the terminal performs the fourth operation based on the running status of the deactivation timer for the partially or fully activated downlink BWP in SpCell, including at least one of the following:
[0412] If all active downlink BWPs in the SpCell are running deactivation timers, the terminal stops all active downlink BWPs in the SpCell.
[0413] If all active downlink BWPs of the SpCell are running deactivation timers, the terminal stops the deactivation timer of the target downlink BWP of the SpCell.
[0414] If the deactivation timer of at least one active downlink BWP of the SpCell is running, the terminal stops the deactivation timers of all active downlink BWPs of the SpCell.
[0415] If the deactivation timer of at least one active downlink BWP of the SpCell does not run, the terminal does not stop the deactivation timers of all active downlink BWPs of the SpCell.
[0416] If the deactivation timer of at least one active downlink BWP of the SpCell is running, the terminal stops the deactivation timer of the active target downlink BWP of the SpCell.
[0417] If the deactivation timer of at least one active downlink BWP of the SpCell does not run, the terminal does not stop the deactivation timer of the active target downlink BWP of the SpCell.
[0418] If the SpCell has only one active downlink BWP, and the deactivation timer of the active downlink BWP is running, the terminal stops the deactivation timer of the active downlink BWP.
[0419] Optionally, the target downlink BWP satisfies at least one of the following:
[0420] The target downlink BWP is indicated by the network side; the identifier of the target downlink BWP is the same as the identifier of the activated uplink BWP; the identifier of the target downlink BWP is the same as the identifier of the activated uplink BWP configured with random access resources (such as PRACH occasions); the target downlink BWP is a downlink BWP associated with an activated uplink BWP; the target downlink BWP is a downlink BWP associated with an activated uplink BWP configured with random access resources; the target downlink BWP includes downlink BWPs with the same identifier as the activated uplink BWP; the target downlink BWP includes downlink BWPs with the same identifier as the activated uplink BWP configured with random access resources; the target downlink BWP includes downlink BWPs associated with an activated uplink BWP; the target downlink BWP includes downlink BWPs associated with an activated uplink BWP configured with random access resources.
[0421] Optionally, the association between the target downlink BWP and the activated uplink BWP can be configured by the network side, or the association between the target downlink BWP and the activated uplink BWP can be agreed upon by the protocol.
[0422] Optionally, the first cell is SpCell, the second cell is the serving cell, and the terminal performs a fifth operation when initiating random access, including at least one of the following:
[0423] If the serving cell is a secondary cell, the SpCell includes at least two active downlink BWPs, and the at least two active downlink BWPs include the first downlink BWP. The terminal uses the first downlink BWP and the first uplink BWP to perform a random access procedure.
[0424] If the serving cell is a secondary cell and the SpCell only includes the activated first downlink BWP, the terminal uses the first downlink BWP and the first uplink BWP to perform a random access procedure;
[0425] If the serving cell is a secondary cell and the SpCell includes an inactive first downlink BWP, the terminal activates the first downlink BWP, and the terminal uses the first downlink BWP and the first uplink BWP to perform a random access procedure.
[0426] Optionally, the association between the first downlink BWP and the first uplink BWP is indicated by the network side. Therefore, the terminal can obtain the association between the first downlink BWP and the first uplink BWP based on the network side indication.
[0427] Optionally, the association between the first downlink BWP and the first uplink BWP is indicated by the network side when activating at least one of the following functions: multiple uplink BWP activation function, multiple downlink BWP activation function.
[0428] 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.
[0429] 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.
[0430] 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.
[0431] In some embodiments, see Figure 7 When the wireless communication device is a terminal or a component within a terminal, the wireless communication device 500 includes:
[0432] Processing module 501 is used to perform a first operation, a second operation, or a third operation when initiating random access, depending on whether random access resources are configured on the activated first uplink frequency domain resource.
[0433] The first operation includes one of the following:
[0434] Switch to the target uplink frequency domain resource and activate the target uplink frequency domain resource;
[0435] The second operation includes one of the following:
[0436] Switch to the first target downlink frequency domain resource and activate the first target downlink frequency domain resource;
[0437] The third operation includes one of the following:
[0438] Switch to the second target downlink frequency domain resource and activate the second target downlink frequency domain resource.
[0439] In some embodiments, the processing module 501 is specifically used for:
[0440] If no random access resource is configured on the first uplink frequency domain resource, the first operation is performed when initiating random access, or the second operation is performed when initiating random access;
[0441] If random access resources are configured on the first uplink frequency domain resource, the third operation is performed when initiating random access.
[0442] In some embodiments, the processing module 501 is specifically used for:
[0443] If the first condition is met, the system switches to the target uplink frequency domain resources when initiating random access;
[0444] And / or,
[0445] If the second condition is met, the target uplink frequency domain resource is activated when initiating random access;
[0446] The first condition includes at least one of the following:
[0447] The wireless communication device 500 does not support multiple active uplink frequency domain resources; the first uplink frequency domain resource does not enable multiple active uplink frequency domain resources; the target uplink frequency domain resource does not enable multiple active uplink frequency domain resources; multiple active uplink frequency domain resources are not enabled between the first uplink frequency domain resource and the target uplink frequency domain resource; the first uplink frequency domain resource and the target uplink frequency domain resource overlap in the time domain or frequency domain; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to the channel bandwidth or bandwidth portion BWP bandwidth supported by the target uplink frequency domain resource; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the target uplink frequency domain resource; the BWP bandwidth supported by the wireless communication device 500 is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the target uplink frequency domain resource. The target uplink frequency domain resource supports the following: a wide channel bandwidth; a channel bandwidth supported by the wireless communication device 500 that is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the target uplink frequency domain resource; a BWP bandwidth supported by the wireless communication device 500 that is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the target uplink frequency domain resource; a terminal type list supported by the target uplink frequency domain resource that includes at least the terminal type of the wireless communication device 500; a terminal capability list supported by the target uplink frequency domain resource that includes at least the terminal capability of the wireless communication device 500; a terminal energy consumption level list supported by the target uplink frequency domain resource that includes at least the terminal energy consumption level of the wireless communication device 500; a service list supported by the target uplink frequency domain resource that includes at least the service corresponding to the random access initiated by the wireless communication device 500; and random access resources are configured on the target uplink frequency domain resource.
[0448] The second condition includes at least one of the following:
[0449] The wireless communication device 500 supports multiple active uplink frequency domain resources; the first uplink frequency domain resource enables multiple active uplink frequency domain resources; the target uplink frequency domain resource enables multiple active uplink frequency domain resources; multiple active uplink frequency domain resources are enabled between the first uplink frequency domain resource and the target uplink frequency domain resource; the first uplink frequency domain resource and the target uplink frequency domain resource do not overlap in the time domain or frequency domain; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to the channel bandwidth or BWP bandwidth supported by the target uplink frequency domain resource; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the target uplink frequency domain resource; the BWP bandwidth supported by the wireless communication device 500 is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the target uplink frequency domain resource; the... The channel bandwidth supported by the wireless communication device 500 is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the target uplink frequency domain resource; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the target uplink frequency domain resource; the terminal type list supported by the target uplink frequency domain resource includes at least the terminal type of the wireless communication device 500; the terminal capability list supported by the target uplink frequency domain resource includes at least the terminal capability of the wireless communication device 500; the terminal power consumption level list supported by the target uplink frequency domain resource includes at least the terminal power consumption level of the wireless communication device 500; the service list supported by the target uplink frequency domain resource includes at least the service corresponding to the random access initiated by the wireless communication device 500; and random access resources are configured on the target uplink frequency domain resource.
[0450] In some embodiments, where the first operation includes activating the target uplink frequency domain resource, the processing module 501 is further configured to deactivate the target uplink frequency domain resource after completing random access.
[0451] In some embodiments, the processing module 501 is specifically used for:
[0452] If the third condition is met, the system switches to the first target downlink frequency domain resource when initiating random access;
[0453] And / or,
[0454] If the fourth condition is met, the first target downlink frequency domain resource is activated when initiating random access;
[0455] The third condition includes at least one of the following:
[0456] The wireless communication device 500 does not support multiple active downlink frequency domain resources; the currently active downlink frequency domain resource does not enable multiple active downlink frequency domain resources; the first target downlink frequency domain resource does not enable multiple active downlink frequency domain resources; multiple active downlink frequency domain resources are not enabled between the first target downlink frequency domain resource and the currently active downlink frequency domain resource; the first target downlink frequency domain resource and the currently active downlink frequency domain resource overlap in the time domain or frequency domain; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink frequency domain resource; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the first target downlink frequency domain resource; the BWP bandwidth supported by the wireless communication device 500 is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the first target downlink frequency domain resource; The wireless communication device 500 supports a channel bandwidth greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the wireless communication device 500 supports a channel bandwidth greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource; the terminal type list supported by the first target downlink frequency domain resource includes at least the terminal type of the wireless communication device 500; the terminal capability list supported by the first target downlink frequency domain resource includes at least the terminal capability of the wireless communication device 500; the terminal power consumption level list supported by the first target downlink frequency domain resource includes at least the terminal power consumption level of the wireless communication device 500; the service list supported by the first target downlink frequency domain resource includes at least the service corresponding to the random access initiated by the wireless communication device 500; and random access response resources are configured on the first target downlink frequency domain resource.
[0457] The fourth condition includes at least one of the following:
[0458] The wireless communication device 500 supports multiple active downlink frequency domain resources; the currently active downlink frequency domain resource enables multiple active downlink frequency domain resources; the first target downlink frequency domain resource enables multiple active downlink frequency domain resources; multiple active downlink frequency domain resources are enabled between the first target downlink frequency domain resource and the currently active downlink frequency domain resource; the first target downlink frequency domain resource and the currently active downlink frequency domain resource do not overlap in the time domain or frequency domain; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink frequency domain resource; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to at least one channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the BWP bandwidth supported by the wireless communication device 500 is greater than or equal to at least one BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource; The channel bandwidth supported by the wireless communication device 500 is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the channel bandwidth supported by the wireless communication device 500 is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource; the terminal type list supported by the first target downlink frequency domain resource includes at least the terminal type of the wireless communication device 500; the terminal capability list supported by the first target downlink frequency domain resource includes at least the terminal capability of the wireless communication device 500; the terminal energy consumption level list supported by the first target downlink frequency domain resource includes at least the terminal energy consumption level of the wireless communication device 500; the service list supported by the first target downlink frequency domain resource includes at least the service corresponding to the random access initiated by the wireless communication device 500; and random access response resources are configured on the first target downlink frequency domain resource.
[0459] In some embodiments, the serving cell to which the first target downlink frequency domain resource belongs includes a special cell (SpCell).
[0460] In some embodiments, where the second operation includes activating the first target downlink frequency domain resource, the processing module 501 is further configured to deactivate the first target downlink frequency domain resource after completing random access.
[0461] In some embodiments, the processing module 501 is specifically used for:
[0462] If the fifth condition is met, the user switches to the second target downlink frequency domain resource when initiating random access.
[0463] And / or,
[0464] If the sixth condition is met, the second target downlink frequency domain resource is activated when initiating random access;
[0465] The fifth condition includes at least one of the following:
[0466] The wireless communication device 500 does not support multiple activation of downlink frequency domain resources; the currently activated downlink frequency domain resource does not enable multiple activation of downlink frequency domain resources; the second target downlink frequency domain resource does not enable multiple activation of downlink frequency domain resources; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource do not enable multiple activation of downlink frequency domain resources; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; the deactivation timer for at least one activated downlink frequency domain resource is not running;
[0467] The sixth condition includes at least one of the following:
[0468] The wireless communication device 500 supports multiple active downlink frequency domain resources; the currently active downlink frequency domain resource enables multiple active downlink frequency domain resources; the second target downlink frequency domain resource enables multiple active downlink frequency domain resources; multiple active downlink frequency domain resources are enabled between the currently active downlink frequency domain resource and the second target downlink frequency domain resource; the currently active downlink frequency domain resource and the second target downlink frequency domain resource do not overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one active downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; at least one active downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; the deactivation timer for at least one active downlink frequency domain resource is running.
[0469] In some embodiments, the identifier of the second target downlink frequency domain resource is the same as the identifier of the first uplink frequency domain resource; or,
[0470] The second target downlink frequency domain resource includes a third target downlink frequency domain resource, and the identifier of the third target downlink frequency domain resource is the same as the identifier of the first uplink frequency domain resource.
[0471] In some embodiments, the processing module 501 is further configured to deactivate K downlink frequency domain resources;
[0472] In this context, the deactivation timers for the K downlink frequency domain resources are not running, where K is a positive integer.
[0473] In some embodiments, the wireless communication device 500 further includes:
[0474] The receiving module 502 is used to receive first configuration information from the network-side device;
[0475] The first configuration information includes at least one of the following:
[0476] Information on the deactivation timers for N downlink frequency domain resources;
[0477] The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources.
[0478] The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate multiple downlink frequency domain resources;
[0479] The third indication information is used to indicate the characteristic set of M uplink frequency domain resources;
[0480] The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources;
[0481] The fifth indication information is used to indicate that each of the M uplink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0482] The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0483] Wherein, the M uplink frequency domain resources include the target uplink frequency domain resources, and the N downlink frequency domain resources include at least one of the following: the first target downlink frequency domain resources, the second target downlink frequency domain resources, and the third target downlink frequency domain resources;
[0484] The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0485] The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0486] Where M and N are both positive integers.
[0487] Therefore, in this embodiment, when initiating random access, the terminal performs a first operation, a second operation, or a third operation depending on whether a random access resource is configured on the activated first uplink frequency domain resource. The first operation includes one of the following: switching to a target uplink frequency domain resource and activating the target uplink frequency domain resource. The second operation includes one of the following: switching to a first target downlink frequency domain resource and activating the first target downlink frequency domain resource. The third operation includes one of the following: switching to a second target downlink frequency domain resource and activating the second target downlink frequency domain resource. Specifically, the terminal can activate the target uplink frequency domain resource when initiating random access, thereby enabling the terminal to maintain multiple activated uplink frequency domain resources, ensuring uplink transmission performance during random access, and improving the scheduling and switching performance of uplink frequency domain resources during random access. Alternatively, the terminal can switch to the target uplink frequency domain resource when initiating random access, thereby avoiding unnecessary maintenance of multiple activated uplink frequency domain resources, achieving power saving for the terminal, and also improving the scheduling and switching performance of uplink frequency domain resources during random access. Alternatively, the terminal can activate either the first target downlink frequency domain resource or the second target downlink frequency domain resource when initiating random access, thereby enabling the terminal to maintain multiple active downlink frequency domain resources, ensuring downlink transmission performance during random access, and also improving the performance of downlink frequency domain resource scheduling and switching during random access; or, the terminal can switch to the first target downlink frequency domain resource or the second target downlink frequency domain resource when initiating random access, thereby avoiding the terminal needing to maintain multiple active downlink frequency domain resources unnecessarily, achieving power saving effect for the terminal, and also improving the performance of downlink frequency domain resource scheduling and switching during random access.
[0488] In some embodiments, see Figure 8 When the wireless communication device is a network-side device or a component within a network-side device, the wireless communication device 600 includes:
[0489] The sending module 601 is used to send the first configuration information to the terminal;
[0490] The first configuration information includes at least one of the following:
[0491] Information on the deactivation timers for N downlink frequency domain resources;
[0492] The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources.
[0493] The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate multiple downlink frequency domain resources;
[0494] The third indication information is used to indicate the characteristic set of M uplink frequency domain resources;
[0495] The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources;
[0496] The fifth indication information is used to indicate at least one of the following supported by each of the M uplink frequency domain resources: channel bandwidth or channel bandwidth list, bandwidth portion BWP bandwidth or BWP bandwidth list, terminal type or terminal type list, terminal capability or terminal capability list, terminal power consumption level or terminal power consumption level list, service or service list.
[0497] The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0498] The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0499] The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0500] Where M and N are both positive integers.
[0501] Therefore, in this embodiment, the network-side device sends first configuration information to the terminal; wherein, the first configuration information includes at least one of the following: information on the deactivation timers of N downlink frequency domain resources; first indication information for indicating whether multiple activation of uplink frequency domain resources is enabled for M uplink frequency domain resources; second indication information for indicating whether multiple activation of uplink frequency domain resources is enabled for N downlink frequency domain resources; third indication information for indicating the feature set of M uplink frequency domain resources; fourth indication information for indicating the feature set of N downlink frequency domain resources; and fifth indication information for indicating the feature set of M uplink frequency domain resources. The frequency domain resources each support at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capabilities, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services; the sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capabilities, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services. Therefore, the terminal can activate or switch uplink frequency domain resources during random access based on the first configuration information, and / or the terminal can activate or switch downlink frequency domain resources during random access based on the first configuration information, improving uplink and downlink transmission performance during random access, and also improving the scheduling and switching performance of uplink and downlink frequency domain resources during random access.
[0502] In some embodiments, see Figure 9 When the wireless communication device is a terminal or a component within a terminal, the wireless communication device 700 includes:
[0503] Processing module 701 is used to perform a fourth operation when initiating random access; or,
[0504] Processing module 701 is used to perform the fifth operation when initiating random access;
[0505] The fourth operation includes one of the following: stopping the deactivation timer of some or all downlink frequency domain resources that are active, or not stopping the deactivation timer of some or all downlink frequency domain resources that are active.
[0506] The fifth operation includes performing a random access procedure using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell, wherein random access resources are configured on the first uplink frequency domain resources.
[0507] In some embodiments, the processing module 701 is specifically used for:
[0508] The fourth operation is performed based on the deactivation timer status of the partially or fully activated downlink frequency domain resources of the serving cell; or,
[0509] If the serving cell is a secondary cell, the fourth operation is performed based on the deactivation timer status of the downlink frequency domain resources that are partially or fully activated in the special cell SpCell.
[0510] In some embodiments, the processing module 701 is specifically configured to perform at least one of the following:
[0511] If all active downlink frequency domain resources of the serving cell are running deactivation timers, stop all active downlink frequency domain resources of the serving cell.
[0512] If the deactivation timers for all active downlink frequency domain resources of the serving cell are running, stop the deactivation timers for the active target downlink frequency domain resources of the serving cell.
[0513] If the deactivation timer for at least one active downlink frequency domain resource of the serving cell is running, stop the deactivation timers for all active downlink frequency domain resources of the serving cell.
[0514] If the deactivation timer for at least one active downlink frequency domain resource of the serving cell does not run, the deactivation timers for all active downlink frequency domain resources of the serving cell shall not be stopped.
[0515] If the deactivation timer for at least one active downlink frequency domain resource of the serving cell is running, stop the deactivation timer for the active target downlink frequency domain resource of the serving cell.
[0516] If the deactivation timer for at least one active downlink frequency domain resource of the serving cell does not run, the deactivation timer for the active target downlink frequency domain resource of the serving cell is not stopped.
[0517] If the serving cell has only one active downlink frequency domain resource, and the deactivation timer of the active downlink frequency domain resource is running, stop the deactivation timer of the active downlink frequency domain resource.
[0518] In some embodiments, the processing module 701 is specifically configured to perform at least one of the following:
[0519] If all active downlink frequency domain resources of the SpCell are running deactivation timers, stop all active downlink frequency domain resources of the SpCell.
[0520] If the deactivation timers for all active downlink frequency domain resources of the SpCell are running, stop the deactivation timer for the active target downlink frequency domain resource of the SpCell.
[0521] If the deactivation timer of at least one active downlink frequency domain resource of the SpCell is running, stop the deactivation timers of all active downlink frequency domain resources of the SpCell.
[0522] If the deactivation timer of at least one active downlink frequency domain resource of the SpCell does not run, the deactivation timers of all active downlink frequency domain resources of the SpCell shall not be stopped.
[0523] If the deactivation timer of at least one active downlink frequency domain resource of the SpCell is running, stop the deactivation timer of the active target downlink frequency domain resource of the SpCell;
[0524] If the deactivation timer of at least one active downlink frequency domain resource of the SpCell does not run, the deactivation timer of the active target downlink frequency domain resource of the SpCell is not stopped.
[0525] If the SpCell has only one active downlink frequency domain resource, and the deactivation timer of the active downlink frequency domain resource is running, stop the deactivation timer of the active downlink frequency domain resource.
[0526] In some embodiments, the target downlink frequency domain resource satisfies at least one of the following: the target downlink frequency domain resource is indicated by the network side; the identifier of the target downlink frequency domain resource is the same as the identifier of the activated uplink frequency domain resource; the identifier of the target downlink frequency domain resource is the same as the identifier of the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource is a downlink frequency domain resource associated with the activated uplink frequency domain resource; the target downlink frequency domain resource is a downlink frequency domain resource associated with the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource includes a downlink frequency domain resource with the same identifier as the identifier of the activated uplink frequency domain resource; the target downlink frequency domain resource includes a downlink frequency domain resource with the same identifier as the identifier of the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource includes a downlink frequency domain resource associated with the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource includes a downlink frequency domain resource associated with the activated uplink frequency domain resource configured with random access resources.
[0527] In some embodiments, the first cell is an SpCell, and the second cell is a serving cell;
[0528] The processing module 701 is specifically used to perform at least one of the following:
[0529] If the serving cell is a secondary cell, the SpCell includes at least two active downlink frequency domain resources, and the at least two active downlink frequency domain resources include the first downlink frequency domain resource. The random access procedure is performed using the first downlink frequency domain resource and the first uplink frequency domain resource.
[0530] If the serving cell is a secondary cell, and the SpCell only includes the activated first downlink frequency domain resources, the random access procedure is performed using the first downlink frequency domain resources and the first uplink frequency domain resources;
[0531] If the serving cell is a secondary cell, and the SpCell includes an inactive first downlink frequency domain resource, the first downlink frequency domain resource is activated, and a random access procedure is performed using the first downlink frequency domain resource and the first uplink frequency domain resource.
[0532] In some embodiments, the association between the first downlink frequency domain resource and the first uplink frequency domain resource is indicated by the network side.
[0533] In some embodiments, the association between the first downlink frequency domain resource and the first uplink frequency domain resource is indicated by the network side when activating at least one of the following functions: multi-activation of uplink frequency domain resources function, multi-activation of downlink frequency domain resources function.
[0534] Therefore, in this embodiment, the terminal performs a fourth operation when initiating random access; or, the terminal performs a fifth operation when initiating random access. The fourth operation includes one of the following: stopping the deactivation timers of some or all activated downlink frequency domain resources, or not stopping the deactivation timers of some or all activated downlink frequency domain resources. The fifth operation includes using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell to perform a random access procedure, wherein random access resources are configured on the first uplink frequency domain resources. Specifically, when initiating random access, the terminal stops the deactivation timers of some or all activated downlink frequency domain resources, or does not stop the deactivation timers of some or all activated downlink frequency domain resources, thereby making reasonable use of downlink frequency domain resources and improving the performance of downlink frequency domain resource scheduling and handover during random access. Alternatively, when initiating random access, the terminal uses the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell to perform a random access procedure, thereby improving random access performance and the performance of uplink and downlink frequency domain resource scheduling and handover during random access.
[0535] The wireless communication device provided in this application embodiment can achieve... Figure 2 , Figure 3 or Figure 4The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.
[0536] like Figure 10 As shown, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802, wherein the memory 802 stores programs or instructions that can run on the processor 801.
[0537] For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 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.
[0538] For example, when the communication device 800 is a network-side device, the program or instructions executed by the processor 801 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.
[0539] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 2 or Figure 4 The steps in the method embodiment shown are illustrated. The terminal embodiment corresponds to the above-described terminal-side method embodiment; all implementation processes and methods of the above method embodiments can be applied to the terminal embodiment and achieve the same technical effect. The terminal can be... Figure 7 The wireless communication device 500 shown, or the terminal, can be... Figure 9 The wireless communication device 700 shown.
[0540] Specifically, Figure 11 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.
[0541] The terminal 900 includes, but is not limited to, at least some of the following components: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.
[0542] Those skilled in the art will understand that the terminal 900 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 910 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 11The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.
[0543] It should be understood that, in this embodiment, the input unit 904 may include a graphics processor 9041 and a microphone 9042. The graphics processor 9041 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 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.
[0544] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 901 can transmit it to the processor 910 for processing; in addition, the radio frequency unit 901 can send uplink data to the network-side device. Typically, the radio frequency unit 901 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.
[0545] The memory 909 can be used to store software programs or instructions, as well as various data. The memory 909 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 909 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 909 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.
[0546] Processor 910 may include one or more processing units; optionally, processor 910 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 910.
[0547] In some embodiments, the processor 910 is configured to perform a first operation, a second operation, or a third operation when initiating random access, depending on whether a random access resource is configured on the activated first uplink frequency domain resource.
[0548] The first operation includes one of the following:
[0549] Switch to the target uplink frequency domain resource and activate the target uplink frequency domain resource;
[0550] The second operation includes one of the following:
[0551] Switch to the first target downlink frequency domain resource and activate the first target downlink frequency domain resource;
[0552] The third operation includes one of the following:
[0553] Switch to the second target downlink frequency domain resource and activate the second target downlink frequency domain resource.
[0554] Therefore, in this embodiment, when initiating random access, the terminal performs a first operation, a second operation, or a third operation depending on whether a random access resource is configured on the activated first uplink frequency domain resource. The first operation includes one of the following: switching to a target uplink frequency domain resource and activating the target uplink frequency domain resource. The second operation includes one of the following: switching to a first target downlink frequency domain resource and activating the first target downlink frequency domain resource. The third operation includes one of the following: switching to a second target downlink frequency domain resource and activating the second target downlink frequency domain resource. Specifically, the terminal can activate the target uplink frequency domain resource when initiating random access, thereby enabling the terminal to maintain multiple activated uplink frequency domain resources, ensuring uplink transmission performance during random access, and improving the scheduling and switching performance of uplink frequency domain resources during random access. Alternatively, the terminal can switch to the target uplink frequency domain resource when initiating random access, thereby avoiding unnecessary maintenance of multiple activated uplink frequency domain resources, achieving power saving for the terminal, and also improving the scheduling and switching performance of uplink frequency domain resources during random access. Alternatively, the terminal can activate either the first target downlink frequency domain resource or the second target downlink frequency domain resource when initiating random access, thereby enabling the terminal to maintain multiple active downlink frequency domain resources, ensuring downlink transmission performance during random access, and also improving the performance of downlink frequency domain resource scheduling and switching during random access; or, the terminal can switch to the first target downlink frequency domain resource or the second target downlink frequency domain resource when initiating random access, thereby avoiding the terminal needing to maintain multiple active downlink frequency domain resources unnecessarily, achieving power saving effect for the terminal, and also improving the performance of downlink frequency domain resource scheduling and switching during random access.
[0555] In other embodiments, the processor 910 is configured to perform a fourth operation when initiating random access; or, the processor 910 is configured to perform a fifth operation when initiating random access.
[0556] The fourth operation includes one of the following: stopping the deactivation timer of some or all downlink frequency domain resources that are active, or not stopping the deactivation timer of some or all downlink frequency domain resources that are active.
[0557] The fifth operation includes performing a random access procedure using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell, wherein random access resources are configured on the first uplink frequency domain resources.
[0558] Therefore, in this embodiment, the terminal performs a fourth operation when initiating random access; or, the terminal performs a fifth operation when initiating random access. The fourth operation includes one of the following: stopping the deactivation timers of some or all activated downlink frequency domain resources, or not stopping the deactivation timers of some or all activated downlink frequency domain resources. The fifth operation includes using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell to perform a random access procedure, wherein random access resources are configured on the first uplink frequency domain resources. Specifically, when initiating random access, the terminal stops the deactivation timers of some or all activated downlink frequency domain resources, or does not stop the deactivation timers of some or all activated downlink frequency domain resources, thereby making reasonable use of downlink frequency domain resources and improving the performance of downlink frequency domain resource scheduling and handover during random access. Alternatively, when initiating random access, the terminal uses the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell to perform a random access procedure, thereby improving random access performance and the performance of uplink and downlink frequency domain resource scheduling and handover during random access.
[0559] 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.
[0560] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 3 The steps of the method embodiment shown are illustrated. This network-side device embodiment corresponds to the method embodiment executed by the network-side device described above. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.
[0561] This application embodiment also provides a network-side device, which may be... Figure 8 The wireless communication device 600 shown.
[0562] Specifically, such as Figure 12As shown, the network-side device 1000 includes: an antenna 101, a radio frequency (RF) device 102, a baseband device 103, a processor 104, and a memory 105. The antenna 101 is connected to the RF device 102. In the uplink direction, the RF device 102 receives information through the antenna 101 and transmits the received information to the baseband device 103 for processing. In the downlink direction, the baseband device 103 processes the information to be transmitted and sends it to the RF device 102. The RF device 102 processes the received information and transmits it through the antenna 101.
[0563] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 103, which includes a baseband processor.
[0564] The baseband device 103 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 12 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 105 via a bus interface to call the program in the memory 105 and execute the operation of the network-side device shown in the above method embodiment.
[0565] The network-side device may also include a network interface 106, such as a Common Public Radio Interface (CPRI).
[0566] Specifically, the network-side device 1000 in this application embodiment further includes: instructions or programs stored in memory 105 and executable on processor 104, wherein processor 104 calls the instructions or programs in memory 105 to execute. Figure 8 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.
[0567] In some embodiments, the radio frequency device 102 is used to send first configuration information to the terminal;
[0568] The first configuration information includes at least one of the following:
[0569] Information on the deactivation timers for N downlink frequency domain resources;
[0570] The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources.
[0571] The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate multiple downlink frequency domain resources;
[0572] The third indication information is used to indicate the characteristic set of M uplink frequency domain resources;
[0573] The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources;
[0574] The fifth indication information is used to indicate at least one of the following supported by each of the M uplink frequency domain resources: channel bandwidth or channel bandwidth list, bandwidth portion BWP bandwidth or BWP bandwidth list, terminal type or terminal type list, terminal capability or terminal capability list, terminal power consumption level or terminal power consumption level list, service or service list.
[0575] The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services.
[0576] The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0577] The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services.
[0578] Where M and N are both positive integers.
[0579] Therefore, in this embodiment, the network-side device sends first configuration information to the terminal; wherein, the first configuration information includes at least one of the following: information on the deactivation timers of N downlink frequency domain resources; first indication information for indicating whether multiple activation of uplink frequency domain resources is enabled for M uplink frequency domain resources; second indication information for indicating whether multiple activation of uplink frequency domain resources is enabled for N downlink frequency domain resources; third indication information for indicating the feature set of M uplink frequency domain resources; fourth indication information for indicating the feature set of N downlink frequency domain resources; and fifth indication information for indicating the feature set of M uplink frequency domain resources. The frequency domain resources each support at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capabilities, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services; the sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capabilities, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services. Therefore, the terminal can activate or switch uplink frequency domain resources during random access based on the first configuration information, and / or the terminal can activate or switch downlink frequency domain resources during random access based on the first configuration information, improving uplink and downlink transmission performance during random access, and also improving the scheduling and switching performance of uplink and downlink frequency domain resources during random access.
[0580] 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.
[0581] 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.
[0582] 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.
[0583] 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.
[0584] 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.
[0585] 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.
[0586] 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.
[0587] 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.
[0588] 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, characterized in that, include: When a terminal initiates random access, it performs a first operation, a second operation, or a third operation depending on whether random access resources are configured on the first activated uplink frequency domain resource. The first operation includes one of the following: Switch to the target uplink frequency domain resource and activate the target uplink frequency domain resource; The second operation includes one of the following: Switch to the first target downlink frequency domain resource and activate the first target downlink frequency domain resource; The third operation includes one of the following: Switch to the second target downlink frequency domain resource and activate the second target downlink frequency domain resource.
2. The method according to claim 1, characterized in that, When initiating random access, the terminal performs a first operation, a second operation, or a third operation depending on whether random access resources are configured on the activated first uplink frequency domain resource, including: If no random access resource is configured on the first uplink frequency domain resource, the terminal performs the first operation when initiating random access, or the terminal performs the second operation when initiating random access; If random access resources are configured on the first uplink frequency domain resources, the terminal performs the third operation when initiating random access.
3. The method according to claim 2, characterized in that, When the terminal initiates random access, it performs the first operation, including: If the first condition is met, the terminal switches to the target uplink frequency domain resource when initiating random access; And / or, If the second condition is met, the terminal activates the target uplink frequency domain resource when initiating random access; The first condition includes at least one of the following: The terminal does not support multiple active uplink frequency domain resources; the first uplink frequency domain resource does not enable multiple active uplink frequency domain resources; the target uplink frequency domain resource does not enable multiple active uplink frequency domain resources; multiple active uplink frequency domain resources are not enabled between the first uplink frequency domain resource and the target uplink frequency domain resource; the first uplink frequency domain resource and the target uplink frequency domain resource overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or bandwidth portion BWP bandwidth supported by the target uplink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the target uplink frequency domain resource; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the target uplink frequency domain resource. The following conditions must be met: The terminal supports one less BWP bandwidth; the channel bandwidth supported by the terminal is greater than or equal to the smallest channel bandwidth in the target uplink frequency domain resource's supported channel bandwidth list; the channel bandwidth supported by the terminal is greater than or equal to the smallest BWP bandwidth in the target uplink frequency domain resource's supported BWP bandwidth list; the target uplink frequency domain resource's supported terminal type list includes at least the terminal type of the terminal; the target uplink frequency domain resource's supported terminal capability list includes at least the terminal capability of the terminal; the target uplink frequency domain resource's supported terminal energy consumption level list includes at least the terminal energy consumption level of the terminal; the target uplink frequency domain resource's supported service list includes at least the service corresponding to the random access initiated by the terminal; random access resources are configured on the target uplink frequency domain resource. The second condition includes at least one of the following: The terminal supports multiple active uplink frequency domain resources; the first uplink frequency domain resource enables multiple active uplink frequency domain resources; the target uplink frequency domain resource enables multiple active uplink frequency domain resources; multiple active uplink frequency domain resources are enabled between the first uplink frequency domain resource and the target uplink frequency domain resource; the first uplink frequency domain resource and the target uplink frequency domain resource do not overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the target uplink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the target uplink frequency domain resource; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the target uplink frequency domain resource. WP bandwidth; the channel bandwidth supported by the terminal is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the target uplink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the target uplink frequency domain resource; the terminal type list supported by the target uplink frequency domain resource includes at least the terminal type of the terminal; the terminal capability list supported by the target uplink frequency domain resource includes at least the terminal capability of the terminal; the terminal energy consumption level list supported by the target uplink frequency domain resource includes at least the terminal energy consumption level of the terminal; the service list supported by the target uplink frequency domain resource includes at least the service corresponding to the random access initiated by the terminal; random access resources are configured on the target uplink frequency domain resource.
4. The method according to claim 3, characterized in that, If the first operation includes activating the target uplink frequency domain resource, the method further includes: After completing random access, the terminal activates the target uplink frequency domain resource.
5. The method according to claim 2, characterized in that, When the terminal initiates random access, it performs the second operation, including: If the third condition is met, the terminal switches to the first target downlink frequency domain resource when initiating random access; and / or, If the fourth condition is met, the terminal activates the first target downlink frequency domain resource when initiating random access; The third condition includes at least one of the following: The terminal does not support multiple activations of downlink frequency domain resources; the currently activated downlink frequency domain resource does not enable multiple activations of downlink frequency domain resources; the first target downlink frequency domain resource does not enable multiple activations of downlink frequency domain resources; multiple activations of downlink frequency domain resources are not enabled between the first target downlink frequency domain resource and the currently activated downlink frequency domain resource; the first target downlink frequency domain resource and the currently activated downlink frequency domain resource overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource. BWP bandwidth; the channel bandwidth supported by the terminal is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource; the terminal type list supported by the first target downlink frequency domain resource includes at least the terminal type of the terminal; the terminal capability list supported by the first target downlink frequency domain resource includes at least the terminal capability of the terminal; the terminal energy consumption level list supported by the first target downlink frequency domain resource includes at least the terminal energy consumption level of the terminal; the service list supported by the first target downlink frequency domain resource includes at least the service corresponding to the random access initiated by the terminal; random access response resources are configured on the first target downlink frequency domain resource; The fourth condition includes at least one of the following: The terminal supports multiple active downlink frequency domain resources; the currently active downlink frequency domain resource enables multiple active downlink frequency domain resources; the first target downlink frequency domain resource enables multiple active downlink frequency domain resources; multiple active downlink frequency domain resources are enabled between the first target downlink frequency domain resource and the currently active downlink frequency domain resource; the first target downlink frequency domain resource and the currently active downlink frequency domain resource do not overlap in the time domain or frequency domain; the channel bandwidth supported by the terminal is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the first target downlink frequency domain resource; the BWP bandwidth supported by the terminal is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the first target downlink frequency domain resource. WP bandwidth; the channel bandwidth supported by the terminal is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the channel bandwidth supported by the terminal is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource; the terminal type list supported by the first target downlink frequency domain resource includes at least the terminal type of the terminal; the terminal capability list supported by the first target downlink frequency domain resource includes at least the terminal capability of the terminal; the terminal energy consumption level list supported by the first target downlink frequency domain resource includes at least the terminal energy consumption level of the terminal; the service list supported by the first target downlink frequency domain resource includes at least the service corresponding to the random access initiated by the terminal; random access response resources are configured on the first target downlink frequency domain resource.
6. The method according to claim 5, characterized in that, The serving cell to which the first target downlink frequency domain resource belongs includes the special cell SpCell.
7. The method according to claim 5 or 6, characterized in that, When the second operation includes activating the first target downlink frequency domain resource, the method further includes: After completing random access, the terminal activates the first target downlink frequency domain resource.
8. The method according to claim 2, characterized in that, When the terminal initiates random access, it performs the third operation, including: If the fifth condition is met, the terminal switches to the second target downlink frequency domain resource when initiating random access; and / or, If the sixth condition is met, the terminal activates the second target downlink frequency domain resource when initiating random access; The fifth condition includes at least one of the following: The terminal does not support multiple activations of downlink frequency domain resources; the currently activated downlink frequency domain resource does not enable multiple activations of downlink frequency domain resources; the second target downlink frequency domain resource does not enable multiple activations of downlink frequency domain resources; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource do not enable multiple activations of downlink frequency domain resources; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; the deactivation timer for at least one activated downlink frequency domain resource is not running; The sixth condition includes at least one of the following: The terminal supports multiple activation of downlink frequency domain resources; the currently activated downlink frequency domain resource enables multiple activation of downlink frequency domain resources; the second target downlink frequency domain resource enables multiple activation of downlink frequency domain resources; multiple activation of downlink frequency domain resources is enabled between the currently activated downlink frequency domain resource and the second target downlink frequency domain resource; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource do not overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; the deactivation timer for at least one activated downlink frequency domain resource is running.
9. The method according to claim 8, characterized in that, The identifier of the second target downlink frequency domain resource is the same as the identifier of the first uplink frequency domain resource; or, The second target downlink frequency domain resource includes a third target downlink frequency domain resource, and the identifier of the third target downlink frequency domain resource is the same as the identifier of the first uplink frequency domain resource.
10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: The terminal deactivates K downlink frequency domain resources; In this context, the deactivation timers for the K downlink frequency domain resources are not running, where K is a positive integer.
11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: The terminal receives first configuration information from the network-side device; The first configuration information includes at least one of the following: Information on the deactivation timers for N downlink frequency domain resources; The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources. The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate multiple downlink frequency domain resources; The third indication information is used to indicate the characteristic set of M uplink frequency domain resources; The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources; The fifth indication information is used to indicate that each of the M uplink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services. The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services. Wherein, the M uplink frequency domain resources include the target uplink frequency domain resources, and the N downlink frequency domain resources include at least one of the following: the first target downlink frequency domain resources, the second target downlink frequency domain resources, and the third target downlink frequency domain resources; The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services. The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services. Where M and N are both positive integers.
12. A wireless communication method, characterized in that, include: The network-side device sends the first configuration information to the terminal; The first configuration information includes at least one of the following: Information on the deactivation timers for N downlink frequency domain resources; The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources. The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate multiple downlink frequency domain resources; The third indication information is used to indicate the characteristic set of M uplink frequency domain resources; The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources; The fifth indication information is used to indicate at least one of the following supported by each of the M uplink frequency domain resources: channel bandwidth or channel bandwidth list, bandwidth portion BWP bandwidth or BWP bandwidth list, terminal type or terminal type list, terminal capability or terminal capability list, terminal power consumption level or terminal power consumption level list, service or service list. The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services. The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services. The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services. Where M and N are both positive integers.
13. A wireless communication method, characterized in that, include: The terminal performs the fourth operation when initiating random access; or, The terminal performs the fifth operation when initiating random access; The fourth operation includes one of the following: stopping the deactivation timer of some or all downlink frequency domain resources that are active, or not stopping the deactivation timer of some or all downlink frequency domain resources that are active. The fifth operation includes performing a random access procedure using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell, wherein random access resources are configured on the first uplink frequency domain resources.
14. The method according to claim 13, characterized in that, When the terminal initiates random access, it performs a fourth operation, including: The terminal executes the fourth operation based on the running status of the deactivation timer for partially or fully activated downlink frequency domain resources of the serving cell; or, If the serving cell is a secondary cell, the terminal performs the fourth operation based on the deactivation timer status of the downlink frequency domain resources that are partially or fully activated in the special cell SpCell.
15. The method according to claim 14, characterized in that, The terminal performs the fourth operation based on the running status of the deactivation timer for some or all of the activated downlink frequency domain resources of the serving cell, including at least one of the following: If all active downlink frequency domain resources of the serving cell are running deactivation timers, the terminal stops all active downlink frequency domain resources of the serving cell from running deactivation timers. If the deactivation timers for all active downlink frequency domain resources of the serving cell are running, the terminal stops the deactivation timers for the active target downlink frequency domain resources of the serving cell. If the deactivation timer for at least one active downlink frequency domain resource of the serving cell is running, the terminal stops the deactivation timers for all active downlink frequency domain resources of the serving cell. If the deactivation timer for at least one active downlink frequency domain resource of the serving cell does not run, the terminal does not stop the deactivation timers for all active downlink frequency domain resources of the serving cell. If the deactivation timer of at least one active downlink frequency domain resource of the serving cell is running, the terminal stops the deactivation timer of the active target downlink frequency domain resource of the serving cell; If the deactivation timer for at least one active downlink frequency domain resource of the serving cell is not running, the terminal does not stop the deactivation timer for the active target downlink frequency domain resource of the serving cell. If the serving cell has only one active downlink frequency domain resource, and the deactivation timer of the active downlink frequency domain resource is running, the terminal stops the deactivation timer of the active downlink frequency domain resource.
16. The method according to claim 14, characterized in that, The terminal performs the fourth operation based on the running status of the deactivation timer for some or all of the activated downlink frequency domain resources of SpCell, including at least one of the following: If all active downlink frequency domain resources of the SpCell are running deactivation timers, the terminal stops all active downlink frequency domain resources of the SpCell from running. If all the deactivation timers for the active downlink frequency domain resources of the SpCell are running, the terminal stops the deactivation timer for the active target downlink frequency domain resource of the SpCell. If the deactivation timer of at least one active downlink frequency domain resource of the SpCell is running, the terminal stops the deactivation timers of all active downlink frequency domain resources of the SpCell. If the deactivation timer of at least one active downlink frequency domain resource of the SpCell does not run, the terminal does not stop the deactivation timers of all active downlink frequency domain resources of the SpCell. If the deactivation timer of at least one active downlink frequency domain resource of the SpCell is running, the terminal stops the deactivation timer of the active target downlink frequency domain resource of the SpCell; If the deactivation timer of at least one active downlink frequency domain resource of the SpCell does not run, the terminal does not stop the deactivation timer of the active target downlink frequency domain resource of the SpCell; If the SpCell has only one active downlink frequency domain resource, and the deactivation timer of the active downlink frequency domain resource is running, the terminal stops the deactivation timer of the active downlink frequency domain resource.
17. The method according to claim 15 or 16, characterized in that, The target downlink frequency domain resources satisfy at least one of the following: The target downlink frequency domain resource is indicated by the network side; the identifier of the target downlink frequency domain resource is the same as the identifier of the activated uplink frequency domain resource; the identifier of the target downlink frequency domain resource is the same as the identifier of the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource is a downlink frequency domain resource associated with the activated uplink frequency domain resource; The target downlink frequency domain resource is a downlink frequency domain resource associated with an activated uplink frequency domain resource configured with random access resources; The target downlink frequency domain resources include downlink frequency domain resources whose identifiers are the same as those of the activated uplink frequency domain resources; The target downlink frequency domain resource includes downlink frequency domain resources whose identifier is the same as that of the active uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource includes downlink frequency domain resources associated with the active uplink frequency domain resource; the target downlink frequency domain resource includes downlink frequency domain resources associated with the active uplink frequency domain resource configured with random access resources.
18. The method according to claim 13, characterized in that, The first cell is SpCell, and the second cell is the serving cell; When initiating random access, the terminal performs a fifth operation, including at least one of the following: If the serving cell is a secondary cell, the SpCell includes at least two active downlink frequency domain resources, and the at least two active downlink frequency domain resources include the first downlink frequency domain resource. The terminal uses the first downlink frequency domain resource and the first uplink frequency domain resource to perform a random access procedure. If the serving cell is a secondary cell, and the SpCell only includes the activated first downlink frequency domain resources, the terminal uses the first downlink frequency domain resources and the first uplink frequency domain resources to perform a random access procedure; If the serving cell is a secondary cell and the SpCell includes an inactive first downlink frequency domain resource, the terminal activates the first downlink frequency domain resource, and the terminal uses the first downlink frequency domain resource and the first uplink frequency domain resource to perform a random access procedure.
19. The method according to claim 13 or 18, characterized in that, The association between the first downlink frequency domain resource and the first uplink frequency domain resource is indicated by the network side.
20. The method according to claim 19, characterized in that, The association between the first downlink frequency domain resource and the first uplink frequency domain resource is indicated by the network side when activating at least one of the following functions: multiple activation of uplink frequency domain resource function, multiple activation of downlink frequency domain resource function.
21. A wireless communication device, characterized in that, include: The processing module is used to perform a first operation, a second operation, or a third operation when initiating random access, depending on whether random access resources are configured on the activated first uplink frequency domain resource. The first operation includes one of the following: Switch to the target uplink frequency domain resource and activate the target uplink frequency domain resource; The second operation includes one of the following: Switch to the first target downlink frequency domain resource and activate the first target downlink frequency domain resource; The third operation includes one of the following: Switch to the second target downlink frequency domain resource and activate the second target downlink frequency domain resource.
22. The apparatus according to claim 21, characterized in that, The processing module is specifically used for: If no random access resource is configured on the first uplink frequency domain resource, the first operation is performed when initiating random access, or the second operation is performed when initiating random access; If random access resources are configured on the first uplink frequency domain resource, the third operation is performed when initiating random access.
23. The apparatus according to claim 22, characterized in that, The processing module is specifically used for: If the first condition is met, the system switches to the target uplink frequency domain resources when initiating random access; And / or, If the second condition is met, the target uplink frequency domain resource is activated when initiating random access; The first condition includes at least one of the following: The wireless communication device does not support multiple active uplink frequency domain resources; the first uplink frequency domain resource does not enable multiple active uplink frequency domain resources; the target uplink frequency domain resource does not enable multiple active uplink frequency domain resources; multiple active uplink frequency domain resources are not enabled between the first uplink frequency domain resource and the target uplink frequency domain resource; the first uplink frequency domain resource and the target uplink frequency domain resource overlap in the time domain or frequency domain; the channel bandwidth supported by the wireless communication device is greater than or equal to the channel bandwidth or bandwidth portion BWP bandwidth supported by the target uplink frequency domain resource; the channel bandwidth supported by the wireless communication device is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the target uplink frequency domain resource; the BWP bandwidth supported by the wireless communication device is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the target uplink frequency domain resource. WP bandwidth; the channel bandwidth supported by the wireless communication device is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the target uplink frequency domain resource; the channel bandwidth supported by the wireless communication device is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the target uplink frequency domain resource; the terminal type list supported by the target uplink frequency domain resource includes at least the terminal type of the wireless communication device; the terminal capability list supported by the target uplink frequency domain resource includes at least the terminal capability of the wireless communication device; the terminal power consumption level list supported by the target uplink frequency domain resource includes at least the terminal power consumption level of the wireless communication device; the service list supported by the target uplink frequency domain resource includes at least the service corresponding to the random access initiated by the wireless communication device; random access resources are configured on the target uplink frequency domain resource; The second condition includes at least one of the following: The wireless communication device supports multiple active uplink frequency domain resources; the first uplink frequency domain resource enables multiple active uplink frequency domain resources; the target uplink frequency domain resource enables multiple active uplink frequency domain resources; multiple active uplink frequency domain resources are enabled between the first uplink frequency domain resource and the target uplink frequency domain resource; the first uplink frequency domain resource and the target uplink frequency domain resource do not overlap in the time domain or frequency domain; the channel bandwidth supported by the wireless communication device is greater than or equal to the channel bandwidth or BWP bandwidth supported by the target uplink frequency domain resource; the channel bandwidth supported by the wireless communication device is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the target uplink frequency domain resource; the BWP bandwidth supported by the wireless communication device is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the target uplink frequency domain resource. The wireless communication device supports a channel bandwidth greater than or equal to the smallest channel bandwidth in the target uplink frequency domain resource's supported channel bandwidth list; the wireless communication device supports a channel bandwidth greater than or equal to the smallest BWP bandwidth in the target uplink frequency domain resource's supported BWP bandwidth list; the target uplink frequency domain resource's supported terminal type list includes at least the terminal type of the wireless communication device; the target uplink frequency domain resource's supported terminal capability list includes at least the terminal capability of the wireless communication device; the target uplink frequency domain resource's supported terminal energy consumption level list includes at least the terminal energy consumption level of the wireless communication device; the target uplink frequency domain resource's supported service list includes at least the service corresponding to the random access initiated by the wireless communication device; and random access resources are configured on the target uplink frequency domain resource.
24. The apparatus according to claim 22, characterized in that, The processing module is specifically used for: If the third condition is met, the system switches to the first target downlink frequency domain resource when initiating random access; And / or, If the fourth condition is met, the first target downlink frequency domain resource is activated when initiating random access; The third condition includes at least one of the following: The wireless communication device does not support multiple active downlink frequency domain resources; the currently active downlink frequency domain resource does not enable multiple active downlink frequency domain resources; the first target downlink frequency domain resource does not enable multiple active downlink frequency domain resources; multiple active downlink frequency domain resources are not enabled between the first target downlink frequency domain resource and the currently active downlink frequency domain resource; the first target downlink frequency domain resource and the currently active downlink frequency domain resource overlap in the time domain or frequency domain; the channel bandwidth supported by the wireless communication device is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink frequency domain resource; the channel bandwidth supported by the wireless communication device is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the first target downlink frequency domain resource; the BWP bandwidth supported by the wireless communication device is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the first target downlink frequency domain resource. The following conditions must be met: the channel bandwidth supported by the wireless communication device is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the channel bandwidth supported by the wireless communication device is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource; the terminal type list supported by the first target downlink frequency domain resource includes at least the terminal type of the wireless communication device; the terminal capability list supported by the first target downlink frequency domain resource includes at least the terminal capability of the wireless communication device; the terminal energy consumption level list supported by the first target downlink frequency domain resource includes at least the terminal energy consumption level of the wireless communication device; the service list supported by the first target downlink frequency domain resource includes at least the service corresponding to the random access initiated by the wireless communication device; and random access response resources are configured on the first target downlink frequency domain resource. The fourth condition includes at least one of the following: The wireless communication device supports multiple active downlink frequency domain resources; the currently active downlink frequency domain resource enables multiple active downlink frequency domain resources; the first target downlink frequency domain resource enables multiple active downlink frequency domain resources; multiple active downlink frequency domain resources are enabled between the first target downlink frequency domain resource and the currently active downlink frequency domain resource; the first target downlink frequency domain resource and the currently active downlink frequency domain resource do not overlap in the time domain or frequency domain; the channel bandwidth supported by the wireless communication device is greater than or equal to the channel bandwidth or BWP bandwidth supported by the first target downlink frequency domain resource; the channel bandwidth supported by the wireless communication device is greater than or equal to at least one channel bandwidth in the channel bandwidth list supported by the first target downlink frequency domain resource; the BWP bandwidth supported by the wireless communication device is greater than or equal to at least one BWP bandwidth in the BWP bandwidth list supported by the first target downlink frequency domain resource. The channel bandwidth supported by the wireless communication device is greater than or equal to the smallest channel bandwidth in the list of channel bandwidths supported by the first target downlink frequency domain resource; the channel bandwidth supported by the wireless communication device is greater than or equal to the smallest BWP bandwidth in the list of BWP bandwidths supported by the first target downlink frequency domain resource; the terminal type list supported by the first target downlink frequency domain resource includes at least the terminal type of the wireless communication device; the terminal capability list supported by the first target downlink frequency domain resource includes at least the terminal capability of the wireless communication device; the terminal energy consumption level list supported by the first target downlink frequency domain resource includes at least the terminal energy consumption level of the wireless communication device; the service list supported by the first target downlink frequency domain resource includes at least the service corresponding to the random access initiated by the wireless communication device; and random access response resources are configured on the first target downlink frequency domain resource.
25. The apparatus according to claim 22, characterized in that, The processing module is specifically used for: If the fifth condition is met, the system switches to the second target downlink frequency domain resource when initiating random access; And / or, If the sixth condition is met, the second target downlink frequency domain resource is activated when initiating random access; The fifth condition includes at least one of the following: The wireless communication device does not support multiple activation of downlink frequency domain resources; the currently activated downlink frequency domain resource does not enable multiple activation of downlink frequency domain resources; the second target downlink frequency domain resource does not enable multiple activation of downlink frequency domain resources; multiple activation of downlink frequency domain resources is not enabled between the currently activated downlink frequency domain resource and the second target downlink frequency domain resource; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; the deactivation timer for at least one activated downlink frequency domain resource is not running; The sixth condition includes at least one of the following: The wireless communication device supports multiple activation of downlink frequency domain resources; the currently activated downlink frequency domain resource enables multiple activation of downlink frequency domain resources; the second target downlink frequency domain resource enables multiple activation of downlink frequency domain resources; multiple activation of downlink frequency domain resources is enabled between the currently activated downlink frequency domain resource and the second target downlink frequency domain resource; the currently activated downlink frequency domain resource and the second target downlink frequency domain resource do not overlap in the time domain or frequency domain; the serving cell is SpCell, and at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; at least one activated downlink frequency domain resource does not contain a downlink frequency domain resource with the same identifier as the first uplink frequency domain resource; the deactivation timer for at least one activated downlink frequency domain resource is running.
26. The apparatus according to any one of claims 21 to 25, characterized in that, The wireless communication device further includes: The receiving module is used to receive first configuration information from the network-side device; The first configuration information includes at least one of the following: Information on the deactivation timers for N downlink frequency domain resources; The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources. The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate multiple downlink frequency domain resources; The third indication information is used to indicate the characteristic set of M uplink frequency domain resources; The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources; The fifth indication information is used to indicate that each of the M uplink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services. The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services. Wherein, the M uplink frequency domain resources include the target uplink frequency domain resources, and the N downlink frequency domain resources include at least one of the following: the first target downlink frequency domain resources, the second target downlink frequency domain resources, and the third target downlink frequency domain resources; The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services. The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services. Where M and N are both positive integers.
27. A wireless communication device, characterized in that, include: The sending module is used to send the first configuration information to the terminal. The first configuration information includes at least one of the following: Information on the deactivation timers for N downlink frequency domain resources; The first indication information is used to indicate whether the M uplink frequency domain resources are enabled to activate multiple uplink frequency domain resources. The second indication information is used to indicate whether N downlink frequency domain resources are enabled to activate multiple downlink frequency domain resources; The third indication information is used to indicate the characteristic set of M uplink frequency domain resources; The fourth indication information is used to indicate the characteristic set of N downlink frequency domain resources; The fifth indication information is used to indicate at least one of the following supported by each of the M uplink frequency domain resources: channel bandwidth or channel bandwidth list, bandwidth portion BWP bandwidth or BWP bandwidth list, terminal type or terminal type list, terminal capability or terminal capability list, terminal power consumption level or terminal power consumption level list, service or service list. The sixth indication information is used to indicate that each of the N downlink frequency domain resources supports at least one of the following: channel bandwidth or a list of channel bandwidths, BWP bandwidth or a list of BWP bandwidths, terminal type or a list of terminal types, terminal capability or a list of terminal capability, terminal power consumption level or a list of terminal power consumption levels, and services or a list of services. The feature set of each uplink frequency domain resource in the M uplink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services. The feature set of each downlink frequency domain resource in the N downlink frequency domain resources includes at least one of the following: supported channel bandwidth or a list of channel bandwidths, supported BWP bandwidth or a list of BWP bandwidths, supported terminal types or a list of terminal types, supported terminal capabilities or a list of terminal capabilities, supported terminal energy consumption levels or a list of terminal energy consumption levels, and supported services or a list of services. Where M and N are both positive integers.
28. A wireless communication device, characterized in that, include: The processing module is used to perform the fourth operation when random access is initiated; or, The processing module is used to perform the fifth operation when a random access is initiated; The fourth operation includes one of the following: stopping the deactivation timer of some or all downlink frequency domain resources that are active, or not stopping the deactivation timer of some or all downlink frequency domain resources that are active. The fifth operation includes performing a random access procedure using the activated first downlink frequency domain resources of the first cell and the activated first uplink frequency domain resources of the second cell, wherein random access resources are configured on the first uplink frequency domain resources.
29. The apparatus according to claim 28, characterized in that, The processing module is specifically used for: The fourth operation is performed based on the deactivation timer status of the partially or fully activated downlink frequency domain resources of the serving cell; or, If the serving cell is a secondary cell, the fourth operation is performed based on the deactivation timer status of the downlink frequency domain resources that are partially or fully activated in the special cell SpCell.
30. The apparatus according to claim 29, characterized in that, The processing module is specifically used to perform at least one of the following: If all active downlink frequency domain resources of the serving cell are running deactivation timers, stop all active downlink frequency domain resources of the serving cell. If the deactivation timers for all active downlink frequency domain resources of the serving cell are running, stop the deactivation timers for the active target downlink frequency domain resources of the serving cell. If the deactivation timer for at least one active downlink frequency domain resource of the serving cell is running, stop the deactivation timers for all active downlink frequency domain resources of the serving cell. If the deactivation timer for at least one active downlink frequency domain resource of the serving cell does not run, the deactivation timers for all active downlink frequency domain resources of the serving cell shall not be stopped. If the deactivation timer for at least one active downlink frequency domain resource of the serving cell is running, stop the deactivation timer for the active target downlink frequency domain resource of the serving cell. If the deactivation timer for at least one active downlink frequency domain resource of the serving cell does not run, the deactivation timer for the active target downlink frequency domain resource of the serving cell is not stopped. If the serving cell has only one active downlink frequency domain resource, and the deactivation timer of the active downlink frequency domain resource is running, stop the deactivation timer of the active downlink frequency domain resource.
31. The apparatus according to claim 29, characterized in that, The processing module is specifically used to perform at least one of the following: If all active downlink frequency domain resources of the SpCell are running deactivation timers, stop all active downlink frequency domain resources of the SpCell. If the deactivation timers for all active downlink frequency domain resources of the SpCell are running, stop the deactivation timer for the active target downlink frequency domain resource of the SpCell. If the deactivation timer of at least one active downlink frequency domain resource of the SpCell is running, stop the deactivation timers of all active downlink frequency domain resources of the SpCell. If the deactivation timer of at least one active downlink frequency domain resource of the SpCell does not run, the deactivation timers of all active downlink frequency domain resources of the SpCell shall not be stopped. If the deactivation timer of at least one active downlink frequency domain resource of the SpCell is running, stop the deactivation timer of the active target downlink frequency domain resource of the SpCell; If the deactivation timer of at least one active downlink frequency domain resource of the SpCell does not run, the deactivation timer of the active target downlink frequency domain resource of the SpCell is not stopped. If the SpCell has only one active downlink frequency domain resource, and the deactivation timer of the active downlink frequency domain resource is running, stop the deactivation timer of the active downlink frequency domain resource.
32. The apparatus according to claim 30 or 31, characterized in that, The target downlink frequency domain resources satisfy at least one of the following: The target downlink frequency domain resource is indicated by the network side; the identifier of the target downlink frequency domain resource is the same as the identifier of the activated uplink frequency domain resource; the identifier of the target downlink frequency domain resource is the same as the identifier of the activated uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource is a downlink frequency domain resource associated with the activated uplink frequency domain resource; The target downlink frequency domain resource is a downlink frequency domain resource associated with an activated uplink frequency domain resource configured with random access resources; The target downlink frequency domain resources include downlink frequency domain resources whose identifiers are the same as those of the activated uplink frequency domain resources; The target downlink frequency domain resource includes downlink frequency domain resources whose identifier is the same as that of the active uplink frequency domain resource configured with random access resources; the target downlink frequency domain resource includes downlink frequency domain resources associated with the active uplink frequency domain resource; the target downlink frequency domain resource includes downlink frequency domain resources associated with the active uplink frequency domain resource configured with random access resources.
33. The apparatus according to claim 28, characterized in that, The first cell is SpCell, and the second cell is the serving cell; The processing module is specifically used to perform at least one of the following: If the serving cell is a secondary cell, the SpCell includes at least two active downlink frequency domain resources, and the at least two active downlink frequency domain resources include the first downlink frequency domain resource. The random access procedure is performed using the first downlink frequency domain resource and the first uplink frequency domain resource. If the serving cell is a secondary cell, and the SpCell only includes the activated first downlink frequency domain resources, the random access procedure is performed using the first downlink frequency domain resources and the first uplink frequency domain resources; If the serving cell is a secondary cell, and the SpCell includes an inactive first downlink frequency domain resource, the first downlink frequency domain resource is activated, and a random access procedure is performed using the first downlink frequency domain resource and the first uplink frequency domain resource.
34. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the wireless communication method as claimed in any one of claims 1 to 11, or to implement the steps of the wireless communication method as claimed in any one of claims 13 to 20.
35. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the wireless communication method as described in claim 12.
36. A readable storage medium, characterized in that, 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 11, or implement the steps of the wireless communication method as described in claim 12, or implement the steps of the wireless communication method as described in any one of claims 13 to 20.