Bandwidth part selection for random access procedure

Abstract

Example embodiments of the present disclosure relate to bandwidth part selection for random access procedure. According to embodiments of the present disclosure, a terminal device receives configuration information from a network device. The configuration information indicates a set of BWPs and configurations of the set of BWPs. When a random access procedure is triggered for a certain feature combination, the terminal device determines whether a condition for switching to a target BWP is met. If the condition is met, the terminal device switches to the target BWP. In this way, resource efficiency is improved.

Description

Technical Field

[0001] The embodiments of this disclosure generally relate to the telecommunications field, and in particular to methods, apparatus, devices, and computer-readable storage media for selecting a bandwidth portion (BWP) for a random access procedure. Background Technology

[0002] With the development of communication systems, more and more technologies have been proposed. The Physical Random Access Channel (PRACH) is a shared channel used by terminal devices to access mobile networks for cell establishment and burst data transmission. To access the PRACH, a terminal device can initiate a random access procedure. Furthermore, the terminal device can be configured with one or more Bandwidth Parts (BWPs). A Bandwidth Part (BWP) is a set of contiguous Physical Resource Blocks (PRBs) on a given carrier. These BWPs are selected from a contiguous subset of common resource blocks of a given numberology. Summary of the Invention

[0003] In summary, the example implementation of this disclosure provides a solution for determining the BWP in a random access procedure.

[0004] In a first aspect, a first device is provided. The first device includes at least one processor; and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured together with the at least one processor to cause the first device to: receive configuration information from a second device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) configurations for the set of BWPs; determine at the first device to trigger a random access procedure based on at least one feature; determine, based on the set of RACH configurations, whether conditions for handover to a target BWP are met, wherein the target BWP is configured with RACH resources for at least one feature; and, based on the determination that the conditions are met, perform random access with the second device on the target BWP.

[0005] In a second aspect, a second device is provided. The second device includes: at least one processor; and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured together with the at least one processor to cause the second device to: transmit configuration information to a first device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) for the set of BWPs; and perform random access with the first device on a target BWP, wherein the random access procedure is triggered based on at least one feature, and the target BWP is configured with RACH resources for the at least one feature.

[0006] In a third aspect, a method is provided. The method includes: receiving configuration information at a first device and from a second device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) configurations for the set of BWPs; determining at the first device to trigger a random access procedure based on at least one feature; determining, based on the set of RACH configurations, whether conditions for handover to a target BWP are met, wherein the target BWP is configured with RACH resources for at least one feature; and performing random access with the second device on the target BWP based on the determination that the conditions are met.

[0007] In a fourth aspect, a method is provided. The method includes: transmitting configuration information at a second device to a first device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) for the set of BWPs; and performing random access with the first device on a target BWP, wherein the random access procedure is triggered based on at least one feature, and the target BWP is configured with RACH resources for the at least one feature.

[0008] In a fifth aspect, an apparatus is provided. The apparatus includes: means for receiving configuration information at a first device and from a second device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) configurations for the set of BWPs; means for determining at the first device to trigger a random access procedure based on at least one feature; means for determining, based on the set of RACH configurations, whether conditions for switching to a target BWP are met, wherein the target BWP is configured with RACH resources for at least one feature; and means for performing random access with the second device on the target BWP based on the determination that the conditions are met.

[0009] In a sixth aspect, an apparatus is provided. The apparatus includes: means for transmitting configuration information at a second device and to a first device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) configured for the set of BWPs; and means for performing random access with the first device on a target BWP, wherein the random access procedure is triggered based on at least one feature, and the target BWP is configured with RACH resources for the at least one feature.

[0010] In a seventh aspect, a computer-readable medium is provided. The computer-readable medium includes program instructions for causing a device to perform at least the method according to any one of the third and fourth aspects above.

[0011] It should be understood that the Summary of the Invention section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0012] Some example implementations will now be described with reference to the accompanying drawings, in which:

[0013] Figure 1 An example communication environment in which an example implementation of the present disclosure may be carried out is shown;

[0014] Figure 2 The signaling flow for selecting appropriate resources for a random access procedure is illustrated according to some example embodiments of this disclosure;

[0015] Figure 3 A schematic diagram of a BWP according to some example embodiments of the present disclosure is shown;

[0016] Figure 4 A flowchart is shown illustrating a method implemented at a first device according to some example embodiments of the present disclosure;

[0017] Figure 5 A flowchart is shown illustrating a method implemented at a first device according to some example embodiments of the present disclosure;

[0018] Figure 6 A simplified block diagram of an apparatus suitable for implementing an example embodiment of this disclosure is shown; and

[0019] Figure 7 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0020] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0021] The principles of this disclosure will now be described with reference to some example embodiments. It will be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and not to imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0022] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0023] The embodiments described in this disclosure, such as “an embodiment,” “an embodiment,” “an example embodiment,” etc., may include specific features, structures, or characteristics, but each embodiment may not necessarily include that specific feature, structure, or characteristic. Furthermore, such wording does not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in conjunction with an embodiment, it should be understood that, whether explicitly described or not, implementing such a feature, structure, or characteristic in conjunction with other embodiments is within the knowledge of those skilled in the art.

[0024] It should be understood that while the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited to these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed items.

[0025] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “described” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that, when used herein, the terms “comprising” and / or “having” specify the presence of the declared features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0026] As used in this application, the term "circuit system" may refer to one or more or all of the following:

[0027] (a) Hardware-only implementations (such as implementations using only analog and / or digital circuit systems), and

[0028] (b) A combination of hardware circuitry and software, such as (if applicable):

[0029] (i) A combination of analog and / or digital hardware circuitry with software / firmware, and

[0030] (ii) Any part of a hardware processor (including a digital signal processor), software, and memory that works together to enable a device such as a mobile phone or server to perform various functions, and

[0031] (c) Hardware circuitry and / or processors, such as microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.

[0032] This definition of circuit system applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term circuit system also covers implementations of hardware circuitry or processors (or processors) and their accompanying software and / or firmware. For example, and where applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits in mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0033] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, future fifth-generation (5G) communication protocols, and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that embody the nature of this disclosure. This disclosure should not be construed as limiting its scope to the systems mentioned above.

[0034] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and techniques used, a network device may refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header (RRH), a relay, an Integration and Access Backhaul (IAB) node, a low-power node (such as a home base station, pico), a non-terrestrial network (NTN), or an ungrounded network device (such as a satellite network device, a low Earth orbit (LEO) satellite, a geostationary Earth orbit (GEO) satellite, an aircraft network device, etc.). In some example implementations, a gNB may be divided into a Centralized Unit (CU) and a Decentralized Unit (DU). The CU carries higher layers of the protocol stack, including Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP), while the DU carries lower layers, such as the physical layer, the Media Access Control (MAC) layer, and the Radio Link Control (RLC) layer.

[0035] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises premises (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0036] As mentioned above, a terminal device can initiate a random access procedure (RACH) to access the PRACH. The random access procedure (RACH) can be contention-based (CBRA) or contention-free (CFRA). A technique called "RACH partitioning" has been proposed. RACH partitioning strategies can be optimized to improve network access performance. For example, based on different service types, the RACH partitioning strategy can partition the random access channel (RACH) resources and allocate RACH resources to each service type. The term "RACH resource" as used herein can refer to the time / frequency resources used for RACH (i.e., the so-called RACH timing - RO) or the RACH preamble, and RACH partitioning can be implemented by partitioning PRACH resources (i.e., mapping different RACH timings to different features) or by partitioning the preambles associated with the RACH timing (i.e., mapping different preambles of the RO to different features). Furthermore, the terminal device can be configured with one or more BWPs. The terminal device can be configured with up to four BWPs for downlink and uplink, but at a given time, only one BWP is active for downlink and one BWP is active for uplink.

[0037] Because configuring many different RACH partitions is a burden for network devices, these partitions may only be configured on certain BWPs, where most end devices can utilize the RACH partitions, for example, in the initial BWP. Therefore, whenever an end device operates on a dedicated BWP that may not have RACH partitions with a set of features available for triggering its RA procedure, it will use a common RACH (if configured on the BWP), which may not provide optimal performance for the end device.

[0038] To address at least some of the aforementioned and other potential problems, a new solution is needed for selecting an appropriate BWP for the random access procedure. According to an embodiment of this disclosure, the terminal device receives configuration information from a network device. The configuration information indicates a set of BWPs and their RACH configurations. When a random access procedure is triggered for a certain combination of characteristics, the terminal device determines whether conditions for switching to a target BWP are met. If the conditions are met, the terminal device switches to the target BWP. In this way, resource efficiency is improved.

[0039] Figure 1 A schematic diagram of a communication environment 100 in which embodiments of the present disclosure may be implemented is shown. The communication environment 100, as part of a communication network, includes devices 110-1, 110-2, ..., 110-N, which may be collectively referred to as "first device 110". The communication environment 100 also includes a second device 120 capable of communicating with the first device 110.

[0040] The communication environment 100 may include any suitable number of devices and cells. In the communication environment 100, the first device 110 and the second device 120 can transmit data and control information to each other. When the first device 110 is a terminal device and the second device 120 is a network device, the link from the second device 120 to the first device 110 is called a downlink (DL), and the link from the first device 110 to the second device 120 is called an uplink (UL). The second device 120 and the first device 110 are interchangeable.

[0041] It should be understood that Figure 1 The number of first devices and cells shown, as well as their connections, is provided for illustrative purposes only and does not imply any limitation. Environment 100 may include any suitable number of devices and networks suitable for implementing embodiments of this disclosure.

[0042] Communication in communication environment 100 can be implemented according to any suitable communication protocol, including but not limited to first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G) cellular communication protocols, wireless local area network communication protocols (such as IEEE 802.11), and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple-input multiple-output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0043] Example embodiments of this disclosure will now be described in detail with reference to the accompanying drawings. Figure 2 This illustrates a signaling flow 200 for selecting resources for a random access procedure according to an example embodiment of this disclosure. For illustrative purposes, reference will be made to... Figure 1 The signaling flow 200 is described. The signaling flow 200 may involve the first device 110-1 and the second device 120.

[0044] The second device 120 transmits configuration information 2010 to the first device 110-1. The configuration information indicates a set of BWPs and a set of RACH configurations for that set of BWPs. In some example embodiments, the configuration information may be transmitted via RRC signaling. Alternatively, the configuration information may be transmitted via Media Access Control (MAC) signaling. In other embodiments, the configuration information may be transmitted via Physical Layer (PHY) signaling.

[0045] In some example implementations, configuration information may include an index of BWPs and a corresponding RACH configuration for each BWP. Each BWP, digitally defined, may have three distinct parameters: subcarrier spacing, symbol duration, and cyclic prefix length. The RACH configuration may include one or more of the following: BWP bandwidth size, frequency location, and control resource set (CORESET). Each DL BWP may include at least one CORESET with a UE-specific search space (USS), while at least one DL BWP configured on the primary carrier includes a CORESET with a common search space (CSS). For the uplink, the terminal device may not transmit PUSCH or PUCCH outside the active bandwidth portion. During initial access, an initial active BWP exists for the terminal device until the terminal device explicitly configures a BWP during or after RRC connection establishment. The term "initial BWP" as used herein may refer to the BWP used to perform the initial access procedure. The term "active BWP" as used herein may refer to a UE-specific / dedicated BWP that cannot be used to perform the access procedure. The active BWP is the BWP used by the terminal device for data transfer when an RRC connection is established. As used in this document, the term "default BWP" refers to the UE-specific BWP configured during RRC reconfiguration. If no default BWP is configured, the initial BWP can be referred to as the default BWP. For example, as... Figure 3 As shown, the configuration information may include the RACH configuration of BWP310, BWP320, BWP330, and BWP340. For example only, BWP310 can be the initial BWP, BWP320 can be the active BWP, and BWP340 can be the default BWP. It should be noted that... Figure 3 This is merely an example, not a limitation.

[0046] In other implementations, the configuration information may include a set of features that can trigger a random access procedure. As used herein, the term "feature" may refer to the reason for triggering a random access procedure. In this case, the configuration information may also indicate that one or more BWPs in the group are configured with RACH resources for one or more features. Alternatively, the configuration information may also indicate that one or more BWPs in the group are not configured with RACH resources for one or more features. It should be noted that Table 1 is merely an example, and other combinations of features and priorities are possible.

[0047] Table 1

[0048]

[0049] The first device 110-1 determines a random access procedure triggered in 2020 based on at least one feature. For example, the at least one feature may include one or more of the following: RedCap, SDT, CovEnh, or slice. It should be noted that multiple features may include other features.

[0050] The first device 110-1 determines whether 2030 meets the conditions for switching to the target BWP. In some example embodiments, this condition may be included in configuration information received from the second device 120. Alternatively, the condition may be predefined at the first device 110-1. If the condition is met, the first device 110-1 switches 2040 to the target BWP. In this way, when random access is triggered in RRC connection mode, the first device 110-1 can consider not only the RACH configuration of the active BWP but also the RACH configuration of the group of BWPs, thereby improving resource efficiency and distributing RACH payloads. It should be noted that embodiments of this disclosure are also applicable to "RRC idle" and "RRC inactive" states.

[0051] In some example implementations, the first device 110-1 may first determine whether the active BWP is configured with RACH resources for at least one feature. If the active BWP is not configured with RACH resources for at least one feature, the first device 110-1 may switch to the initial BWP. In this case, the first device 110-1 may also determine whether the initial BWP is configured with RACH resources for at least one feature. For example, refer to... Figure 3 If BWP320 is not configured with RACH resources for at least one feature, the first device 110-1 may switch to BWP310. If the initial BWP is configured with RACH resources for at least one feature, the initial BWP may be considered the target BWP. If the initial BWP is not configured with RACH resources for at least one feature, the first device 110-1 may determine whether other BWPs in the group (e.g., BWP330 and BWP340) are configured with RACH resources for that at least one feature. If other BWPs are configured with RACH resources for that at least one feature, the initial BWP may be considered the target BWP. In this way, the impact on the current mechanism is minimal and easy to implement. In some examples, when a random access procedure is triggered based on multiple features, the first device 110-1 may determine the priority of the multiple features and identify the feature with the highest priority as the at least one feature.

[0052] Alternatively, the first device 110-1 may first determine whether any BWP in the group of BWPs is configured with RACH resources for the at least one feature. In this case, if a BWP is configured with RACH resources for the at least one feature, such a BWP can be considered a target BWP. In other embodiments, if no BWP in the group of BWPs is configured with RACH resources for the at least one feature, the first device 110-1 may perform random access on the active BWP. Alternatively, if no BWP in the group of BWPs is configured with RACH resources for the at least one feature, the first device 110-1 may switch to the initial BWP. In this case, the first device 110-1 may perform random access on the initial BWP. In this way, a suitable BWP can be selected quickly.

[0053] In some example implementations, if random access for coverage enhancement is triggered, the first device 110-1 can determine whether the active BWP is configured with RACH resources for coverage enhancement based on the set of RACH configurations. In this case, if the active BWP is not configured with RACH resources for coverage enhancement, and the conditions in the configuration information indicate a first reference signal received power (RSRP) threshold for coverage enhancement, the first device 110-1 can compare the RSRP value on the active BWP with the first RSRP threshold. Based on this comparison, the first device 110-1 can determine whether the RSRP value on the active BWP is lower than the first RSRP threshold. If the RSRP value is lower than the first RSRP threshold, the first device 110-1 can switch to the target BWP configured with RACH resources for coverage enhancement. For example, if the RSRP value of BWP320 is lower than the first RSRP threshold, and the configuration information indicates that BWP330 is configured with RACH resources for coverage enhancement, the first device 110-1 can switch to BWP330. In this way, the BWP for random access can be appropriately selected.

[0054] In other embodiments, if random access for capability reduction is triggered, the first device 110-1 can determine whether the active BWP is configured with RACH resources for capability reduction based on the set of RACH configurations. In this case, if the active BWP is not configured with RACH resources for capability reduction, and the conditions in the configuration information indicate a second RSRP threshold for capability reduction, the first device 110-1 can compare the RSRP value on the active BWP with the second RSRP threshold. The first device 110-1 can determine, based on this comparison, whether the RSRP value on the active BWP is lower than the second RSRP threshold. If the RSRP value is lower than the second RSRP threshold, the first device 110-1 can switch to the target BWP configured with RACH resources for capability reduction. For example, if the RSRP value of BWP320 is lower than the second RSRP threshold, and the configuration information indicates that BWP340 is configured with RACH resources for capability reduction, the first device 110-1 can switch to BWP340. The second RSRP threshold may be different for 1RX terminal devices (receivers / receiver chains / receiver branches) and 2RX terminal devices. In one example, the second RSRP threshold can also be applied by an idle / inactive RedCap terminal device to determine whether access is via a RedCap-specific initial BWP or a cell-initial BWP (if the RedCap UE also supports cell-initial BWPs). In this way, the BWP for random access can be appropriately selected.

[0055] Alternatively, if random access for capability reduction is triggered, the first device 110-1 can determine whether the active BWP is configured with RACH resources for capability reduction based on the set of RACH configurations. If the active BWP is not configured with RACH resources for capability reduction, the first device 110-1 can switch to a target BWP configured with RACH resources for capability reduction. In one example implementation, if the first device 110-1 only supports 1RX (receiver / receiver chain), the first device 110-1 can always switch to a BWP that supports a specific RACH partition for capability reduction (as long as such a BWP is available). In this way, the BWP for random access can be appropriately selected.

[0056] In some example implementations, if random access to a slice / slice group is triggered, the first device 110-1 can determine whether the active BWP is configured with RACH resources for the slice / slice group based on the RACH configuration of that group. If the active BWP is not configured with RACH resources for the slice / slice group, the first device 110-1 can switch to a target BWP that is configured with RACH resources for the slice. For example, if BWP320 is not configured with RACH resources for the slice / slice group, and the configuration information indicates that BWP330 is configured with RACH resources for the slice / slice group, the first device 110-1 can switch to BWP330. In this way, the BWP for random access can be appropriately selected, and the RACH payload can be distributed.

[0057] In the example implementation, if a RACH resource is configured for the active BWP, the second device 120 can explicitly configure the first device 110-1 to perform random access on the active BWP. In other words, random access BWP handover can be disabled. For example, the second device 120 can transmit downlink control information or RRC configuration including a disabling indication for BWP handover to the first device 110-1.

[0058] Return to reference Figure 2 The first device 110-1 and the second device 120 perform a 2050 random access on the target BWP. In some embodiments, after triggering random access, the first device 110-1 may perform random access on an active BWP configured with shared RACH resources. If the number of random access failures exceeds a threshold, the first device 110-1 may determine that conditions for switching to the target BWP are met. In this case, the first device 110-1 may switch to the target BWP configured with RACH resources for at least one feature. The second device 120 may configure the threshold via any appropriate signaling. Alternatively, the threshold may be predefined at the first device 110-1.

[0059] According to the above implementation scheme, feature-specific RACH partitions can also be applied in "connected" mode, for example, when the network device anticipates that the 1RX RedCap UE will not survive on the common RACH (e.g., due to RAR coverage issues). Furthermore, it enables BWP handover based on feature-specific RA partitions, thereby improving resource efficiency because it eliminates the need for the NW to replicate the RA partitions to benefit a dedicated BWP. Additionally, RACH payload distribution can be achieved by distributing feature-specific RACH partitions to different BWPs.

[0060] Figure 4 A flowchart of an example method 400 implemented at a first device 110-1 according to some example embodiments of the present disclosure is shown.

[0061] At block 410, the first device 110-1 receives configuration information from the second device 120. The configuration information indicates a set of BWPs and a set of RACH configurations for that set of BWPs. In some example embodiments, the configuration information may be transmitted via RRC signaling. Alternatively, the configuration information may be transmitted via MAC signaling. In other embodiments, the configuration information may be transmitted via PHY signaling.

[0062] In some example implementations, configuration information may include an index of BWPs and a corresponding RACH configuration for each BWP. Each BWP, digitally defined, may have three distinct parameters: subcarrier spacing, symbol duration, and cyclic prefix length. The RACH configuration may include one or more of the following: BWP bandwidth size, frequency location, and control resource set (CORESET). Each DL BWP may include at least one CORESET with a UE-specific search space (USS), while at least one DL BWP configured on the primary carrier includes a CORESET with a common search space (CSS). For the uplink, the terminal device may not transmit PUSCH or PUCCH outside the active bandwidth portion. During initial access, an initial active BWP exists for the terminal device until the terminal device explicitly configures a BWP during or after RRC connection establishment.

[0063] In other implementations, the configuration information may include a set of features that can trigger a random access procedure. As used herein, the term "feature" may refer to a reason that can trigger a random access procedure. In this case, the configuration information may also indicate that one or more BWPs in the group are configured with RACH resources for one or more features. Alternatively, the configuration information may also indicate that one or more BWPs in the group are not configured with RACH resources for one or more features.

[0064] At box 420, the first device 110-1 determines that a random access procedure is triggered based on at least one feature. For example, the at least one feature may include one or more of the following: RedCap, SDT, CovEnh, or slice. It should be noted that multiple features may include other features.

[0065] At block 430, the first device 110-1 determines whether the conditions for switching to the target BWP are met. In some example embodiments, this condition may be included in configuration information received from the second device 120. Alternatively, the condition may be predefined at the first device 110-1.

[0066] At box 440, if the conditions are met, the first device 110-1 and the second device 120 perform random access on the target BWP. In this way, when random access is triggered in RRC connection mode, the first device 110-1 can consider not only the RACH configuration of the active BWP, but also the RACH configuration of the group of BWPs, thereby improving resource efficiency and distributing RACH payloads.

[0067] In some example implementations, the first device 110-1 may first determine whether the active BWP is configured with RACH resources for at least one feature. If the active BWP is not configured with RACH resources for at least one feature, the first device 110-1 may switch to the initial BWP. In this case, the first device 110-1 may also determine whether the initial BWP is configured with RACH resources for at least one feature. If the initial BWP is configured with RACH resources for at least one feature, the initial BWP may be considered the target BWP. If the initial BWP is not configured with RACH resources for at least one feature, the first device 110-1 may determine whether other BWPs in the group are configured with RACH resources for the at least one feature. If other BWPs are configured with RACH resources for the at least one feature, the initial BWP may be considered the target BWP. In this way, the impact on the current mechanism is minimal and it is easy to implement. In some examples, when a random access procedure is triggered based on multiple features, the first device 110-1 may determine the priority of the multiple features and identify the feature with the highest priority as the at least one feature.

[0068] Alternatively, the first device 110-1 may first determine whether any BWP in the group of BWPs is configured with RACH resources for the at least one feature. In this case, if a BWP is configured with RACH resources for the at least one feature, such a BWP can be considered a target BWP. In other embodiments, if no BWP in the group of BWPs is configured with RACH resources for the at least one feature, the first device 110-1 may perform random access on the active BWP. Alternatively, if no BWP in the group of BWPs is configured with RACH resources for the at least one feature, the first device 110-1 may switch to the initial BWP. In this case, the first device 110-1 may perform random access on the initial BWP. In this way, a suitable BWP can be selected quickly.

[0069] In some example implementations, if random access for coverage enhancement is triggered, the first device 110-1 can determine whether the active BWP is configured with RACH resources for coverage enhancement based on the set of RACH configurations. In this case, if the active BWP is not configured with RACH resources for coverage enhancement, and the conditions in the configuration information indicate a first reference signal received power (RSRP) threshold for coverage enhancement, the first device 110-1 can compare the RSRP value on the active BWP with the first RSRP threshold. Based on this comparison, the first device 110-1 can determine whether the RSRP value on the active BWP is lower than the first RSRP threshold. If the RSRP value is lower than the first RSRP threshold, the first device 110-1 can switch to a target BWP configured with RACH resources for coverage enhancement. In this way, the BWP for random access can be appropriately selected.

[0070] In other implementations, if random access for capability reduction is triggered, the first device 110-1 can determine whether the active BWP is configured with RACH resources for capability reduction based on the set of RACH configurations. In this case, if the active BWP is not configured with RACH resources for capability reduction, and the conditions in the configuration information indicate a second RSRP threshold for capability reduction, the first device 110-1 can compare the RSRP value on the active BWP with the second RSRP threshold. The first device 110-1 can determine, based on this comparison, whether the RSRP value on the active BWP is lower than the second RSRP threshold. If the RSRP value is lower than the second RSRP threshold, the first device 110-1 can switch to the target BWP configured with RACH resources for capability reduction. The second RSRP threshold may be different for 1RX and 2RX terminal devices. In one example, the second RSRP threshold may also be applied by an idle / inactive RedCap terminal device to determine whether access is via a RedCap-specific initial BWP or a cell-initial BWP (if the RedCap UE also supports cell-initial BWPs). In this way, the BWP for random access can be appropriately selected.

[0071] Alternatively, if random access for capability reduction is triggered, the first device 110-1 can determine whether the active BWP is configured with RACH resources for capability reduction based on the set of RACH configurations. If the active BWP is not configured with RACH resources for capability reduction, the first device 110-1 can switch to a target BWP configured with RACH resources for capability reduction. In one example implementation, if the first device 110-1 only supports 1RX (receiver / receiver chain), the first device 110-1 can always switch to a BWP that supports a specific RACH partition for capability reduction (as long as such a BWP is available). In this way, the BWP for random access can be appropriately selected.

[0072] In some example implementations, if random access to a slice / slice group is triggered, the first device 110-1 can determine whether the active BWP is configured with RACH resources for the slice / slice group based on the RACH configuration of that group. If the active BWP is not configured with RACH resources for the slice / slice group, the first device 110-1 can switch to a target BWP configured with RACH resources for the slice. In this way, the BWP for random access can be appropriately selected, and the RACH payload can be distributed.

[0073] In the example implementation, if a RACH resource is configured for the active BWP, the second device 120 can explicitly configure the first device 110-1 to perform random access on the active BWP. In other words, random access BWP handover can be disabled. For example, the second device 120 can transmit downlink control information or RRC configuration including a disabling indication for BWP handover to the first device 110-1.

[0074] In some implementations, after triggering random access, the first device 110-1 may perform random access on an active BWP configured with common RACH resources. If the number of random access failures exceeds a threshold, the first device 110-1 may determine that conditions for switching to a target BWP are met. In this case, the first device 110-1 may switch to the target BWP configured with RACH resources for at least one feature. The second device 120 may configure the threshold via any appropriate signaling. Alternatively, the threshold may be predefined at the first device 110-1.

[0075] Figure 5 A flowchart of an example method 500 implemented at a second device 120 according to some example embodiments of the present disclosure is shown.

[0076] At block 510, the second device 120 transmits configuration information to the first device 110-1. The configuration information indicates a set of BWPs and a set of RACH configurations for that set of BWPs. In some example embodiments, the configuration information may be transmitted via RRC signaling. Alternatively, the configuration information may be transmitted via MAC signaling. In other embodiments, the configuration information may be transmitted via PHY signaling.

[0077] In some example implementations, configuration information may include an index of BWPs and a corresponding RACH configuration for each BWP. Each BWP, digitally defined, may have three distinct parameters: subcarrier spacing, symbol duration, and cyclic prefix length. The RACH configuration may include one or more of the following: BWP bandwidth size, frequency location, and control resource set (CORESET). Each DL BWP may include at least one CORESET with a UE-specific search space (USS), while at least one DL BWP configured on the primary carrier includes a CORESET with a common search space (CSS). For the uplink, the terminal device may not transmit PUSCH or PUCCH outside the active bandwidth portion. During initial access, an initial active BWP exists for the terminal device until the terminal device explicitly configures a BWP during or after RRC connection establishment.

[0078] In other implementations, the configuration information may include a set of features that can trigger a random access procedure. As used herein, the term "feature" may refer to a reason that can trigger a random access procedure. In this case, the configuration information may also indicate that one or more BWPs in the group are configured with RACH resources for one or more features. Alternatively, the configuration information may also indicate that one or more BWPs in the group are not configured with RACH resources for one or more features.

[0079] At box 520, the second device 120 performs random access with the first device 110-1 on a target BWP configured with RACH resources for at least one feature.

[0080] In some example embodiments, a first device (e.g., first apparatus 110) capable of performing any of the methods 400 may include means for performing the corresponding operations of method 400. This means may be implemented in any suitable form. For example, the means may be implemented as a circuit system or a software module. The first device may be implemented as first apparatus 110 or included within the first apparatus. In some example embodiments, the means may include at least one processor and at least one memory, the at least one memory including computer program code. The at least one memory and the computer program code are configured to cause the execution of the means together with the at least one processor.

[0081] In some embodiments, the first device includes: means for receiving configuration information at a first device and from a second device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) configurations for the set of BWPs; means for determining at the first device to trigger a random access procedure based on at least one feature; means for determining, based on the set of RACH configurations, whether conditions for switching to a target BWP are met, wherein the target BWP is configured with RACH resources for at least one feature; and means for performing random access with the second device on the target BWP based on the determination that the conditions are met.

[0082] In some implementations, the RACH configuration group also includes conditions for switching to the target BWP.

[0083] In some implementations, the at least one feature includes one of the following: reduced capability, small data transmission, enhanced coverage, or slicing.

[0084] In some embodiments, the condition indicates a first reference signal received power (RSRP) threshold for coverage enhancement, and the first device further includes: means for determining whether the active BWP of the first device is configured with RACH resources for coverage enhancement based on the set of RACH configurations; means for determining the value of RSRP on the active BWP based on the determination that the active BWP is not configured with RACH resources for coverage enhancement; and means for determining whether a condition for switching to a target BWP is met, including: means for comparing the value of RSRP of the active BWP with a first RSRP threshold; means for determining that the condition for switching to the target BWP is met based on the determination that the value of RSRP is lower than the first RSRP threshold; and means for switching from the active BWP to the target BWP configured with RACH resources for coverage enhancement.

[0085] In some implementations, the condition indicates a second RSRP threshold associated with capability reduction, and the first device further includes: means for determining the value of RSRP on the active BWP; and means for determining whether a condition for switching to a target BWP is met, including: means for comparing the value of RSRP on the active BWP with the second RSRP threshold; means for determining that the condition for switching to the target BWP is met based on determining that the value of RSRP is lower than the second RSRP threshold; and means for switching from the active BWP to the target BWP configured with RACH resources for capability reduction.

[0086] In some implementations, the means for determining whether the conditions for switching to the target BWP are met includes: means for determining whether the active BWP is configured with RACH resources for capability reduction; and means for switching from the active BWP to the target BWP configured with RACH resources for capability reduction based on the determination that the active BWP is not configured with RACH resources for capability reduction.

[0087] In some implementations, the means for determining whether the conditions for switching to a target BWP are met includes: means for determining whether the active BWP is configured with RACH resources for slicing; and means for switching from the active BWP to a target BWP configured with RACH resources for slicing based on the determination that the active BWP is not configured with RACH resources for slicing.

[0088] In some embodiments, the first device includes: means for determining whether an active BWP of the first device is configured with a RACH configuration based on the set of RACH configurations; means for switching to an initial BWP based on the determination that the active BWP is not configured with a RACH configuration; and means for determining whether conditions for switching to a target BWP are met, including: means for determining whether conditions for switching to a target BWP are met based on the determination that the initial BWP does not support at least one feature.

[0089] In some implementations, the means for determining whether the conditions for switching to the target BWP are met includes: means for performing random access on the active BWP configured with common RACH resources; and means for determining that the conditions for switching to the target BWP are met based on determining that the number of random access failures on the active BWP exceeds a threshold.

[0090] In some implementations, the means for receiving configuration information includes means for receiving configuration information via one of the following: Radio Resource Control (RRC) signaling, Media Access Control (MAC) signaling, or Physical (PHY) signaling.

[0091] In some implementations, the first device is a terminal device, and the second device is a network device.

[0092] In some example embodiments, a second device (e.g., second apparatus 120) capable of performing any of the methods 500 may include means for performing the corresponding operations of method 500. This means may be implemented in any suitable form. For example, the means may be implemented as a circuit system or a software module. The first device may be implemented as the second apparatus 120 or included within the second apparatus. In some example embodiments, the means may include at least one processor and at least one memory, the at least one memory including computer program code. The at least one memory and the computer program code are configured to cause the execution of the means together with the at least one processor.

[0093] In some embodiments, the second device includes: means for transmitting configuration information at the second device and to the first device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) for the set of BWPs; and means for performing random access with the first device on a target BWP, wherein the random access procedure is triggered based on at least one feature, and the target BWP is configured with RACH resources for the at least one feature.

[0094] In some implementations, the RACH configuration group also includes conditions for switching to the target BWP.

[0095] In some implementations, the at least one feature includes one of the following: reduced capability, small data transmission, enhanced coverage, or slicing.

[0096] In some implementations, this condition indicates a first reference signal received power (RSRP) threshold for coverage enhancement.

[0097] In some implementations, this condition indicates a second RSRP threshold associated with the reduction in capability.

[0098] In some implementations, the means for transmitting configuration information includes means for transmitting configuration information via one of the following: Radio Resource Control (RRC) signaling, Media Access Control (MAC) signaling, or Physical (PHY) signaling.

[0099] In some implementations, the first device is a terminal device, and the second device is a network device.

[0100] Figure 6 This is a simplified block diagram of apparatus 600 suitable for implementing exemplary embodiments of the present disclosure. Apparatus 600 may be provided to implement communication devices, such as... Figure 1The first device 110 is shown in the figure. As shown, the device 600 includes one or more processors 610, one or more memories 620 connected to the processors 610, and one or more communication modules 640 connected to the processors 610.

[0101] Communication module 640 is used for bidirectional communication. Communication module 640 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 640 may include at least one antenna.

[0102] Processor 610 can be of any type suitable for a local area network and may include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture (to give non-limiting examples). Device 600 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock that synchronizes the main processor.

[0103] Memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that will not be maintained during a power outage.

[0104] Computer program 630 includes computer-executable instructions that are executed by an associated processor 610. Program 630 may be stored in memory (e.g., ROM 624). Processor 610 may perform any suitable actions and processes by loading program 630 into RAM 622.

[0105] Some example implementations of this disclosure can be achieved by means of program 630, enabling device 600 to perform as described in the reference. Figures 2 to 5 Any process discussed in this disclosure. Example embodiments of this disclosure may also be implemented in hardware or through a combination of software and hardware.

[0106] In some example embodiments, program 630 may be tangibly contained in a computer-readable medium (such as in memory 620) that may be included in device 600 or in other storage devices accessible by device 600. Device 600 may load program 630 from the computer-readable medium into RAM 622 for execution. The computer-readable medium may include any type of tangible non-volatile storage device, such as ROM, EPROM, flash memory, hard disk, CD, DVD and other magnetic and / or optical storage devices. Figure 7 An example of a computer-readable medium 700 in the form of an optical storage disk is shown. A program 630 is stored on the computer-readable medium.

[0107] Generally, various embodiments of this disclosure can be implemented using hardware or special-purpose circuitry, software, logic, or any combination thereof. Some aspects can be implemented using hardware, while others can be implemented using firmware or software executable by a controller, microprocessor, or other computing device. Although aspects of embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or represented using some other diagrammatic representation, it will be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented as non-limiting examples using hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0108] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as computer-executable instructions included in a program module, which execute in a device on a target physical processor or virtual processor to perform the above-referenced... Figures 2 to 5 Any of the methods described herein. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. In various implementations, the functionality of program modules may be combined or separated as desired among program modules. The machine-executable instructions for a program module may execute on a local device or a distributed device. In a distributed device, a program module may reside on both local and remote storage media.

[0109] Program code for performing the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0110] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable an apparatus, device, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0111] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0112] Furthermore, although operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in a sequential order, or requiring all shown operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0113] Although this disclosure has been described using language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.

Claims

1. A first device, comprising: At least one processor; as well as At least one memory, said at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to: The second device receives configuration information indicating: a set of bandwidth portion (BWP) and a set of random access channels (RACH) configurations for the set of BWPs; At the first device, it is determined that the random access procedure is triggered based on at least one feature; The conditions for switching to a target BWP are determined based on the set of RACH configurations, wherein the target BWP is configured with RACH resources for the at least one feature, wherein the at least one feature includes a capability-reduced RedCap, and the conditions for switching are met whenever a BWP supporting a specific RACH partition with reduced capability is available. as well as Based on the determination that the conditions are met, the random access is performed with the second device on the target BWP.

2. The first apparatus of claim 1, wherein the at least one memory and the computer program code are configured, together with at least one processor, to further cause the first apparatus to: Determine whether any BWP in the set is configured with the RACH resource for the at least one feature. Based on the determination that no BWP in the set of BWPs is configured with the RACH resource for the at least one feature, switch to the initial BWP, and Random access is performed on the initial BWP.

3. The first apparatus of claim 1, wherein the set of RACH configurations further includes the condition for switching to the target BWP.

4. The first device as claimed in claim 1, wherein the at least one feature further comprises one or more of the following: Small data transmission, Enhanced coverage, or slice.

5. The first apparatus of claim 4, wherein the condition indicates a first reference signal received power (RSRP) threshold for coverage enhancement, and The at least one memory and the computer program code are configured, together with the at least one processor, to also cause the first device to: Based on the set of RACH configurations, determine whether the active BWP of the first device is configured with RACH resources for coverage enhancement; Based on the determination that the active BWP is not configured with the RACH resource for coverage enhancement, the value of RSRP on the active BWP is determined; and The at least one memory and the computer program code are configured, together with the at least one processor, to cause the first device to determine whether the conditions for switching to the target BWP are met in such a way as follows: The value of the RSRP of the active BWP is compared with the first RSRP threshold; Based on the determination that the RSRP value is lower than the first RSRP threshold, it is determined that the condition for switching to the target BWP is met; as well as Switch from the active BWP to the target BWP configured with the RACH resource for coverage enhancement.

6. The first device as claimed in any one of claims 1 or 4, wherein the condition indicates a second RSRP threshold associated with a reduction in capability, and The at least one memory and the computer program code are configured, together with the at least one processor, to also cause the first device to: Determine the value of RSRP on the active BWP; and The at least one memory and the computer program code are configured, together with the at least one processor, to cause the first device to determine whether the conditions for switching to the target BWP are met in such a way as follows: The value of the RSRP of the active BWP is compared with the second RSRP threshold; Based on the determination that the value of the RSRP is lower than the second RSRP threshold, it is determined that the condition for switching to the target BWP is met; as well as Switch from the active BWP to the target BWP configured with the RACH resources for capability reduction.

7. The first apparatus of claim 1, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the first apparatus to determine whether the condition for switching to the target BWP is met in such a way as: Determine if the active BWP is configured with RACH resources for slicing; and If it is determined that the active BWP is not configured with the RACH resource for the slice, the system switches from the active BWP to the target BWP that is configured with the RACH resource for the slice.

8. The first apparatus of claim 1, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to further cause the first apparatus to: Based on the set of RACH configurations, determine whether the active BWP of the first device is configured with a RACH configuration; Based on the determination that the active BWP is not configured with the RACH configuration, switch to the initial BWP; and The at least one memory and the computer program code are configured, together with the at least one processor, to cause the first device to determine whether the conditions for switching to the target BWP are met in such a way as follows: Based on the determination that the initial BWP does not support at least one feature, it is determined whether the condition for switching to the target BWP is met.

9. The first apparatus of claim 1, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the first apparatus to determine whether the condition for switching to the target BWP is met in such a way as: Perform random access on active BWPs configured with shared RACH resources; and Based on the determination that the number of random access failures on the active BWP exceeds a threshold, the condition for switching to the target BWP is determined to be met.

10. The first apparatus of claim 1, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the first apparatus to receive the configuration information in such a manner as follows: The configuration information is received via one of the following: Radio Resource Control (RRC) signaling, Media access control MAC signaling, or Physical PHY signaling.

11. The first device as claimed in claim 1, wherein the first device is a terminal device and the second device is a network device.

12. The first device as claimed in claim 1, wherein the first device supports only one receiver or receiver chain 1RX.

13. A second device, comprising: At least one processor; as well as At least one memory, said at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the second device: Transmit configuration information to the first device, the configuration information indicating: a set of bandwidth portion (BWP) and a set of random access channels (RACH) configurations for the set of BWPs; and Random access is performed on the target BWP with the first device, wherein the random access procedure is triggered based on at least one feature, and the target BWP is configured with RACH resources for the at least one feature, wherein the at least one feature includes a capability reduction RedCap.

14. The second apparatus of claim 13, wherein the set of RACH configurations further includes a condition for switching to the target BWP.

15. The second device of claim 13, wherein the at least one feature further comprises one or more of the following: Small data transmission, Enhanced coverage, or slice.

16. The second apparatus of claim 14, wherein the condition indicates a first reference signal received power (RSRP) threshold for coverage enhancement.

17. The second device as claimed in any one of claims 14 or 16, wherein the condition indicates a second RSRP threshold associated with a reduction in capability.

18. The second apparatus of claim 13, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to also cause the first apparatus to transmit the configuration information in such a manner as follows: The configuration information is transmitted via one of the following: Radio Resource Control (RRC) signaling, Media access control MAC signaling, or Physical PHY signaling.

19. The second device as claimed in claim 13, wherein the first device is a terminal device and the second device is a network device.

20. A method of communication, comprising: At the first device and from the second device, configuration information is received, the configuration information indicating: a set of bandwidth portion BWPs and a set of random access channels (RACH) configurations for the set of BWPs; At the first device, it is determined that the random access procedure is triggered based on at least one feature; The conditions for switching to a target BWP are determined based on the set of RACH configurations, wherein the target BWP is configured with RACH resources for the at least one feature, wherein the at least one feature includes a capability-reduced RedCap, and the conditions for switching are met whenever a BWP supporting a specific RACH partition with reduced capability is available. as well as Based on the determination that the conditions are met, the random access is performed with the second device on the target BWP.

21. The method of claim 20, wherein the method further comprises: Determine whether any BWP in the set is configured with the RACH resource for the at least one feature. Based on the determination that no BWP in the set of BWPs is configured with the RACH resource for the at least one feature, switch to the initial BWP, and Random access is performed on the initial BWP.

22. The method of claim 20, wherein the set of RACH configurations further includes the condition for switching to the target BWP.

23. The method of claim 20, wherein the at least one feature further comprises one or more of the following: Small data transmission, Enhanced coverage, or slice.

24. The method of claim 20, wherein the condition indicates a first reference signal received power (RSRP) threshold for coverage enhancement, and wherein the method further comprises: Based on the set of RACH configurations, determine whether the active BWP of the first device is configured with RACH resources for coverage enhancement; Based on the determination that the active BWP is not configured with the RACH resource for coverage enhancement, the value of RSRP on the active BWP is determined; and The conditions for determining whether the switch to the target BWP is met include: The value of the RSRP of the active BWP is compared with the first RSRP threshold; Based on the determination that the RSRP value is lower than the first RSRP threshold, it is determined that the condition for switching to the target BWP is met; and Switch from the active BWP to the target BWP configured with the RACH resource for coverage enhancement.

25. The method of claim 20, wherein the condition indicates a second RSRP threshold associated with a reduction in capability, wherein the method further comprises: Determine the value of RSRP on the active BWP; and The conditions for determining whether the switch to the target BWP is met include: The value of the RSRP of the active BWP is compared with the second RSRP threshold; Based on the determination that the value of the RSRP is lower than the second RSRP threshold, it is determined that the condition for switching to the target BWP is met; and Switch from the active BWP to the target BWP configured with the RACH resources for capability reduction.

26. The method of claim 20, wherein determining whether the condition for switching to the target BWP is met comprises: Determine if the active BWP is configured with RACH resources for slicing; as well as If it is determined that the active BWP is not configured with the RACH resource for the slice, the system switches from the active BWP to the target BWP that is configured with the RACH resource for the slice.

27. The method of claim 20, further comprising: Based on the set of RACH configurations, determine whether the active BWP of the first device is configured with a RACH configuration; If it is determined that the active BWP is not configured with the RACH configuration, switch to the initial BWP; and The conditions for determining whether the switch to the target BWP is met include: Based on the determination that the initial BWP does not support at least one feature, it is determined whether the condition for switching to the target BWP is met.

28. The method of claim 20, wherein determining whether the condition for switching to the target BWP is met comprises: Perform random access on active BWPs configured with shared RACH resources; as well as Based on the determination that the number of random access failures on the active BWP exceeds a threshold, the condition for switching to the target BWP is determined to be met.

29. The method of claim 20, wherein receiving the configuration information includes: The configuration information is received via one of the following: Radio Resource Control (RRC) signaling, Media access control MAC signaling, or Physical PHY signaling.

30. The method of claim 20, wherein the first device is a terminal device and the second device is a network device.

31. A method of communication, comprising: At the second device, configuration information is transmitted to the first device, the configuration information indicating: a set of bandwidth portion (BWP) and a set of random access channels (RACH) configurations for the set of BWPs; as well as Random access is performed on the target BWP with the first device, wherein the random access procedure is triggered based on at least one feature, and the target BWP is configured with RACH resources for the at least one feature, wherein the at least one feature includes a capability reduction RedCap.

32. The method of claim 31, wherein the set of RACH configurations further includes a condition for switching to the target BWP.

33. The method of claim 31, wherein the at least one feature further comprises one or more of the following: Small data transmission, Enhanced coverage, or slice.

34. The method of claim 32, wherein the condition indicates a first reference signal received power (RSRP) threshold for coverage enhancement.

35. The method of claim 32, wherein the condition indicates a second RSRP threshold associated with a reduction in capability.

36. The method of claim 31, wherein transmitting the configuration information comprises: The configuration information is transmitted via one of the following: Radio Resource Control (RRC) signaling, Media access control MAC signaling, or Physical PHY signaling.

37. The method of claim 31, wherein the first device is a terminal device and the second device is a network device.

38. A device for communication, comprising: A means for receiving configuration information from a second device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) configurations for the set of BWPs; A means for determining whether a random access procedure is triggered based on at least one feature; A means for determining whether conditions for switching to a target BWP are met based on the set of RACH configurations, wherein the target BWP is configured with RACH resources for the at least one feature, wherein the at least one feature includes a capability-reduced RedCap, and the conditions for switching are met whenever a BWP supporting a specific RACH partition with reduced capability is available. as well as A means for performing the random access with the second device on the target BWP based on determining that the conditions are met.

39. A device for communication, comprising: A means for transmitting configuration information from a second device to a first device, the configuration information indicating: a set of bandwidth portions (BWPs) and a set of random access channels (RACHs) configured for the set of BWPs; as well as A means for performing random access with the first device on a target BWP, wherein the random access procedure is triggered based on at least one feature, and the target BWP is configured with RACH resources for the at least one feature, wherein the at least one feature includes a capability reduction RedCap.

40. A computer-readable medium comprising program instructions for causing a device to perform the method as claimed in any one of claims 20 to 30 or the method as claimed in any one of claims 31 to 37.

Images