A random access method, apparatus, device, and storage medium

Abstract

This disclosure relates to a random access method, apparatus, device, and storage medium, which may include: determining configuration information, wherein the configuration information is used to determine whether to configure an initial downlink partial bandwidth (BWP) for a terminal and to determine whether the initial downlink BWP supports random access by the terminal in connected mode. By configuring the corresponding BWP for the terminal, the terminal can perform corresponding random access operations according to the configured BWP, avoiding communication failures.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a random access method, apparatus, device and storage medium. Background Technology

[0002] In related technologies, a new terminal type is proposed in 5G New Radio (NR) to cover the requirements of mid-range IoT devices. In the current 3GPP standardization, this new terminal type is called a low-capability terminal, sometimes also called a Reduced capability UE, or RedCap terminal, or simply NR-lite. The RedCap terminal is distinguished from ordinary terminals.

[0003] Considering factors such as terminal bandwidth limitations, TDD center frequency alignment, and synchronization signal and PBCH block (SSB) overhead, a separate initial bandwidth part (Initial BWP) needs to be configured for RedCap terminals. Initial BWP includes the initial downlink bandwidth part (Initial DL BWP) and / or the initial uplink bandwidth part (Initial UL BWP).

[0004] In some cases, RedCap terminals will switch to the initial uplink BWP and / or initial downlink BWP configured specifically for RedCap terminals for random access. However, for connected RedCap terminals, due to the random access channel (RACH) triggering, switching to the initial downlink BWP can cause problems for transmitting proprietary information, resulting in communication failures. Summary of the Invention

[0005] To overcome the problems existing in related technologies, this disclosure provides a random access method, apparatus, device and storage medium.

[0006] According to a first aspect of the present disclosure, a random access method is provided, applied to a network device. The method may include: determining configuration information, wherein the configuration information is used to determine an initial downlink partial bandwidth (BWP) configured for a terminal, and to determine whether the initial downlink BWP supports random access by the terminal in a connected state.

[0007] In one possible implementation, the initial downlink BWP supports random access by the terminal in connected mode.

[0008] In one possible implementation, the initial downlink BWP is configured with a synchronization signal block (SSB).

[0009] In one possible implementation, the initial downlink BWP includes a common search space for random access and at least one other common search space. The other common search space is different from the common search space used for random access.

[0010] In one possible implementation, the center frequency of the initial downlink BWP is the same as the center frequency of the initial uplink BWP configured for the terminal.

[0011] In one possible implementation, the method may further include: using the initial downlink BWP to transmit terminal-specific information.

[0012] In one possible implementation, the configuration information is also used to determine that the initial downlink BWP is not used for terminal-specific information.

[0013] In one possible implementation, the initial downlink BWP does not include an SSB.

[0014] In one possible implementation, the initial downlink BWP does not support random access by the terminal in connected mode.

[0015] In one possible implementation, the initial downlink BWP does not include an SSB.

[0016] In one possible implementation, the center frequency of the initial downlink BWP is not the same as the center frequency of the initial uplink BWP configured for the terminal.

[0017] In one possible implementation, the configuration information is also used to determine an active BWP configured for the terminal, the active BWP including random access resources for the terminal to perform random access.

[0018] In one possible implementation, activating the BWP differs from the initial downlink BWP.

[0019] According to a second aspect of the present disclosure, a random access method is provided, applied to a terminal. The method may include: determining configuration information, wherein the configuration information is used to determine an initial downlink partial bandwidth (BWP) configured for the terminal, and to determine whether the initial downlink BWP supports random access by the terminal in connected mode. Random access is then performed based on the configuration information.

[0020] In one possible implementation, the initial downlink BWP supports random access by the terminal in connected mode. Random access based on configuration information may include: using the initial downlink BWP for random access.

[0021] In one possible implementation, the initial downlink BWP is configured with a synchronization signal block (SSB).

[0022] In one possible implementation, the initial downlink BWP includes a common search space for random access and at least one other common search space, which is different from the common search space for random access.

[0023] In one possible implementation, the center frequency of the initial downlink BWP is the same as the center frequency of the initial uplink BWP configured for the terminal.

[0024] In one possible implementation, the method further includes utilizing the exclusive information of the initial downlink BWP receiving terminal.

[0025] In one possible implementation, the configuration information is also used to determine that the initial downlink BWP is not used to transmit terminal-specific information.

[0026] In one possible implementation, the initial downlink BWP does not include an SSB.

[0027] In one possible implementation, the method may further include: ceasing the use of the exclusive information of the initial downlink BWP receiving terminal.

[0028] In one possible implementation, the initial downlink BWP does not support random access by the terminal in connected mode. Random access based on configuration information may include: stopping random access using the initial downlink BWP.

[0029] In one possible implementation, the initial downlink BWP does not include an SSB.

[0030] In one possible implementation, the center frequency of the initial downlink BWP is not the same as the center frequency of the initial uplink BWP configured for the terminal.

[0031] In one possible implementation, the configuration information is also used to determine an active BWP configured for the terminal, the active BWP including random access resources for the terminal to perform random access.

[0032] In one possible implementation, activating the BWP is different from the initial downlink BWP; random access based on configuration information also includes: using the activated BWP for random access.

[0033] According to a third aspect of the present disclosure, a random access apparatus is provided, the apparatus comprising: a determining module, configured to determine configuration information, the configuration information being configured to determine an initial downlink partial bandwidth (BWP) configured for a terminal, and to determine whether the initial downlink BWP supports random access by the terminal in a connected state.

[0034] In one possible implementation, the initial downlink BWP supports random access by the terminal in connected mode.

[0035] In one possible implementation, the initial downlink BWP is configured with a synchronization signal block (SSB).

[0036] In one possible implementation, the initial downlink BWP includes a common search space for random access and at least one other common search space, which is different from the common search space for random access.

[0037] In one possible implementation, the center frequency of the initial downlink BWP is the same as the center frequency of the initial uplink BWP configured for the terminal.

[0038] In one possible implementation, the apparatus further includes a transmission module for transmitting terminal-specific information using the initial downlink BWP.

[0039] In one possible implementation, the configuration information is also used to determine that the initial downlink BWP is not used for terminal-specific information.

[0040] In one possible implementation, the initial downlink BWP does not include an SSB.

[0041] In one possible implementation, the initial downlink BWP does not support random access by the terminal in connected mode.

[0042] In one possible implementation, the initial downlink BWP does not include an SSB.

[0043] In one possible implementation, the center frequency of the initial downlink BWP is not the same as the center frequency of the initial uplink BWP configured for the terminal.

[0044] In one possible implementation, the configuration information is also used to determine an active BWP configured for the terminal, the active BWP including random access resources for the terminal to perform random access.

[0045] In one possible implementation, activating the BWP differs from the initial downlink BWP.

[0046] According to a fourth aspect of the present disclosure, a random access apparatus is provided, the apparatus comprising: a determining module, configured to determine configuration information, the configuration information being configured to determine an initial downlink partial bandwidth (BWP) configured for a terminal, and to determine whether the initial downlink BWP supports random access by the terminal in a connected state; and an access module, configured to perform random access based on the configuration information.

[0047] In one possible implementation, the initial downlink BWP supports random access by the terminal in connected mode; the access module is also used to perform random access using the initial downlink BWP.

[0048] In one possible implementation, the initial downlink BWP is configured with a synchronization signal block (SSB).

[0049] In one possible implementation, the initial downlink BWP includes a common search space for random access and at least one other common search space, which is different from the common search space for random access.

[0050] In one possible implementation, the center frequency of the initial downlink BWP is the same as the center frequency of the initial uplink BWP configured for the terminal.

[0051] In one possible implementation, the apparatus further includes a receiving module for receiving terminal-specific information using the initial downlink BWP.

[0052] In one possible implementation, the configuration information is also used to determine that the initial downlink BWP is not used to transmit the terminal's proprietary information.

[0053] In one possible implementation, the initial downlink BWP does not include an SSB.

[0054] In one possible implementation, the apparatus further includes a receiving module for stopping the use of the initial downlink BWP receiving terminal's proprietary information.

[0055] In one possible implementation, the initial downlink BWP does not support random access by the terminal in connected mode; the access module is also used to stop random access using the initial downlink BWP.

[0056] In one possible implementation, the initial downlink BWP does not include an SSB.

[0057] In one possible implementation, the center frequency of the initial downlink BWP is not the same as the center frequency of the initial uplink BWP configured for the terminal.

[0058] In one possible implementation, the configuration information is also used to determine an active BWP configured for the terminal, the active BWP including random access resources for the terminal to perform random access.

[0059] In one possible implementation, the activated BWP is different from the initial downlink BWP; the access module is also used to perform random access using the activated BWP.

[0060] According to a fifth aspect of the present disclosure, a random access device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to perform the method described in the first aspect or any embodiment of the first aspect.

[0061] According to a sixth aspect of the present disclosure, a random access device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to perform the method described in the second aspect or any embodiment of the second aspect.

[0062] According to a seventh aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, which, when executed by a processor of a network device, enables the network device to perform the method described in the first aspect or any embodiment of the first aspect.

[0063] According to an eighth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, which, when instructions in the storage medium are executed by a processor of a mobile terminal, enables the mobile terminal to perform the method described in the second aspect or any embodiment of the second aspect.

[0064] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects: configuration information for determining the initial downlink BWP configured for the terminal, and determining whether the initial downlink BWP supports random access by the terminal in connected state, so that the terminal can perform corresponding random access operations according to the configured BWP and avoid communication failure.

[0065] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0066] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0067] Figure 1 This is a schematic diagram of a wireless communication system according to an exemplary embodiment.

[0068] Figure 2 This is a flowchart illustrating a random access method according to an exemplary embodiment.

[0069] Figure 3This is a flowchart illustrating another random access method according to an exemplary embodiment.

[0070] Figure 4 This is a flowchart illustrating yet another random access method according to an exemplary embodiment.

[0071] Figure 5 This is a flowchart illustrating another random access method according to an exemplary embodiment.

[0072] Figure 6 This is a flowchart illustrating another random access method according to an exemplary embodiment.

[0073] Figure 7 This is a flowchart illustrating yet another random access method according to an exemplary embodiment.

[0074] Figure 8 This is a flowchart illustrating another random access method according to an exemplary embodiment.

[0075] Figure 9 This is a flowchart illustrating another random access method according to an exemplary embodiment.

[0076] Figure 10 This is a flowchart illustrating yet another random access method according to an exemplary embodiment.

[0077] Figure 11 This is a flowchart illustrating another random access method according to an exemplary embodiment.

[0078] Figure 12 This is a schematic diagram illustrating a random access device according to an exemplary embodiment.

[0079] Figure 13 This is a schematic diagram of another random access device according to an exemplary embodiment.

[0080] Figure 14 This is a schematic diagram of a random access device according to an exemplary embodiment.

[0081] Figure 15 This is a schematic diagram of another random access device according to an exemplary embodiment. Detailed Implementation

[0082] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure.

[0083] The random access method disclosed herein can be applied to Figure 1 In the wireless communication system shown, through... Figure 1 As can be seen, the wireless communication system 100 may include a network device 110 and a terminal 120. The network device 110 and the terminal 120 can communicate through wireless resources, such as sending and receiving relevant information.

[0084] Understandable, Figure 1 The wireless communication system shown is for illustrative purposes only. A wireless communication system may also include other network devices, such as core network equipment, wireless relay equipment, and wireless backhaul equipment. Figure 1 Not shown in the diagram. This disclosure does not limit the number of network devices and terminals included in the wireless communication system.

[0085] It is further understood that the wireless communication system of this disclosure is a network providing wireless communication functionality. The wireless communication system can employ different communication technologies, such as code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and carrier sense multiple access with collision avoidance. Based on factors such as capacity, speed, and latency, networks can be categorized as 2G networks, 3G networks, 4G networks, or future evolution networks, such as 5G networks. 5G networks can also be referred to as New Radio (NR). For ease of description, this disclosure may sometimes simply refer to the wireless communication network as a network.

[0086] Furthermore, the network device 110 involved in this disclosure can also be referred to as a wireless access network device. This wireless access network device can be: a base station, an evolved Node B (eBY), a home base station, an access point (AP) in a Wi-Fi system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), etc. It can also be a gNB in ​​an NR system, or a component or part of a base station. When it is a vehicle-to-everything (V2X) communication system, the network device can also be an in-vehicle device. It should be understood that the specific technologies and device forms used in the embodiments of this disclosure are not limited.

[0087] Furthermore, the terminal 120 involved in this disclosure can also be referred to as a terminal device, user equipment (UE), mobile station (MS), mobile terminal (MT), etc., which is a device that provides voice and / or data connectivity to a user. For example, the terminal can be a handheld device with wireless connectivity, an in-vehicle device, etc. Currently, some examples of terminals include: smartphones (Mobile Phones), pocket personal computers (PPCs), handheld computers, personal digital assistants (PDAs), laptops, tablets, wearable devices, or in-vehicle devices, etc. In addition, when it is a vehicle-to-everything (V2X) communication system, the terminal device can also be an in-vehicle device. It should be understood that the embodiments of this disclosure do not limit the specific technology or specific device form adopted by the terminal.

[0088] The terminals involved in the embodiments of this disclosure can be understood as a new type of terminal designed in 5G NR: low-capability terminals. Low-capability terminals are sometimes also called Reduced capability UEs, RedCap terminals, or simply NR-lite. The embodiments of this disclosure will be described below using a RedCap terminal as an example.

[0089] It is understood that the terminal involved in the embodiments of this disclosure can be a RedCap terminal. The network device involved in the embodiments of this disclosure can be a base station. It is further understood that the embodiments of this disclosure use a base station as the network device and a RedCap terminal as the terminal as an example for description. Of course, the network device can also be any other possible network device, and the terminal can also be any other possible terminal, which is not limited in this disclosure.

[0090] Similar to Internet of Things (IoT) devices in Long Term Evolution (LTE), 5G NR-lite typically needs to meet the following requirements:

[0091] -Low cost, low complexity

[0092] - Some degree of coverage enhancement

[0093] - Power saving

[0094] Since current NR systems are designed for high-end terminals with high speed and low latency, they cannot meet the requirements of RedCap terminals. Therefore, the current NR system needs to be modified to meet the requirements of RedCap terminals. For example, to meet requirements such as low cost and low complexity, the radio frequency (RF) bandwidth of NR-IoT can be limited, for example, to 5MHz or 10MHz, or the size of the NR-lite buffer can be limited, thereby limiting the size of each received transmission block, etc. Regarding power saving, possible optimization directions include simplifying the communication process and reducing the number of times the RedCap terminal detects the downlink control channel.

[0095] In related technologies, considering factors such as terminal bandwidth limitations, TDD centerfrequency alignment, and synchronization signal and PBCH block (SSB) overhead, a separate initial bandwidth part (Initial BWP) needs to be configured for RedCap terminals. The Initial BWP includes the Initial downlink bandwidth part (Initial DL BWP) and / or the Initial uplink bandwidth part (Initial UL BWP).

[0096] In some cases, for a RedCap terminal in a connected state, random access may be initiated due to possible timing advance (TA) synchronization failure, beam failure, uplink resource requests, etc. In some instances, one or more of the following events may be triggered: radio resource control (RRC) connection re-establishment process; downlink (DL) or UL data arrival during RRC CONNECTED when the uplink (UL) synchronization state is "unsynchronized"; UL data arrival during RRC CONNECTED when no physical uplink control channel (PUCCH) resources are available for scheduling requests (SR); scheduling request failure; RRC requests during synchronization reconfiguration (e.g., handover); establishing time calibration for the auxiliary timing advance group (TAG); requesting other system information; beam failure recovery. Of course, many other possible events may also be triggered, which are not limited in this disclosure.

[0097] In some cases, for a connected RedCap terminal, the BWP (Browser Window) for random access can be selected in the following ways. For example, the terminal can first check whether the monitored active UL BWP contains random access resources. If the active UL BWP does not contain random access resources, and an uplink initial BWP is pre-configured for the RedCap terminal, the RedCap terminal can switch to the configured uplink initial BWP for random access. Of course, to ensure consistency between uplink and downlink, when the RedCap terminal switches to the uplink initial BWP, the downlink BWP will also be switched. For example, if a downlink initial BWP is pre-configured for the RedCap terminal, the RedCap terminal can switch to the configured downlink initial BWP for reception.

[0098] Of course, under normal circumstances, the initial downlink BWP will be configured with a common search space (CSS), which includes search spaces for system information blocks (SIBs), scheduling (SS), search space SIB1, other system information (SIB1), paging search space, and random access search space (RA-SearchSpace). It can be understood that the terminal can monitor terminal-specific information within these search spaces, such as downlink control information (DCI) scrambled with the cell-radio network temporary identifier (C-RNTI).

[0099] However, different RedCap terminals have different requirements regarding SSBs. For example, some RedCap terminals require all BWPs used to have an SSB. Other RedCap terminals can communicate with network devices using BWPs without an SSB. These RedCap terminals that can communicate with network devices using BWPs without an SSB are considered to have higher capabilities. This ability to work with BWPs without an SSB can be considered optional, and not all RedCap terminals support it.

[0100] Of course, in other cases, if the initial DL BWP is used as a random access channel (RACH) but not for paging purposes, the initial DL BWP configured for a RedCap terminal may not have an SSB. Furthermore, in the case of time division duplex (TDD), the initial DL BWP and the initial UL BWP may not have the same center frequency. When a RedCap terminal switches from PACH to the initial DL BWP, terminal-specific information may still be transmitted.

[0101] However, when a RedCap terminal is in connected mode and switches to the initial UL BWP / initial DLBWP due to RACH triggering, communication failures (e.g., transmitting proprietary information) will occur for RedCap terminals that do not support BWP operation without an SSB, as the BWP is not configured with an SSB. In TDD systems, the different center frequencies of the initial DLBWP and initial UL BWP will also cause communication failures.

[0102] Therefore, this disclosure provides a random access method in which a network device configures configuration information for a terminal to determine an initial downlink BWP. This configuration information is used to determine whether the configured initial downlink BWP supports random access by the terminal in connected mode, so that the terminal can accurately determine whether to use the configured initial downlink BWP for random access based on the configuration information, thereby avoiding communication failure.

[0103] It is understood that the terminals mentioned in the embodiments of this disclosure may be RedCap terminals.

[0104] Figure 2 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 2 As shown, this random access method can be used in network devices, and the method may include the following steps:

[0105] In step S11, configuration information is determined. This configuration information is used to determine the initial downlink BWP configured for the terminal and to determine whether the initial downlink BWP supports random access by the terminal in connected mode.

[0106] In this embodiment of the disclosure, the configuration information configured by the network device for the terminal is used to determine whether the initial downlink BWP supports random access by the terminal in the connected state, thereby enabling the terminal to accurately determine whether to use the configured initial downlink BWP for random access based on the configuration information, thereby avoiding communication failure.

[0107] In the random access method provided in this disclosure, in some embodiments, the configuration information can be predefined rules. The network device can pre-store these predefined rules and directly determine the configuration information based on them. In other examples, the configuration information can also be signaling. This signaling can be determined and sent to the terminal by the network device, or it can be determined and sent to the network device by other devices. The network device can receive and determine the signaling, and thus determine the configuration information. For example, the configuration information can be sent by other network devices. This disclosure does not limit the method of obtaining the configuration information.

[0108] In some examples of the random access method provided in the embodiments of this disclosure, the network device may also send the configuration information to the terminal after determining the configuration information, so that the terminal can perform corresponding operations according to the configuration information.

[0109] In a random access method provided in this embodiment, the configuration information determined by the network device can support the terminal to perform random access in the connected state.

[0110] In some examples, configuration information may include an initial DL BWP configured for the terminal, which can support random access by the terminal in connected mode. In some examples, the initial DL BWP configured for a RedCap terminal may be represented as initial DL BWP-RedCap.

[0111] In a random access method provided in this embodiment, the initial DL BWP supports random access by the terminal in connected state. The network device can configure an SSB for this initial DL BWP.

[0112] Figure 3 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 3 As shown, this random access method can be used in network devices, and the method may include the following steps:

[0113] In step S21, an initial DL BWP is configured for the terminal. The initial DL BWP supports random access by the terminal in connected mode, and the initial DL BWP includes an SSB.

[0114] In this embodiment of the disclosure, the network device configures an SSB for the initial DL BWP, enabling RedCap terminals to perform random access on the initial DL BWP. Furthermore, it can be understood that when the network device configures an SSB for the initial DLBWP, especially for RedCap terminals that require all BWPs to have an SSB, random access can be performed on the initial DLBWP without communication failure.

[0115] In a random access method provided in this embodiment, the network device configures an SSB for the initial DL BWP when it determines that certain conditions are met.

[0116] For example, when the initial DL BWP contains a common search space for random access, and at least one other common search space, the network device can configure an SSB for the initial DL BWP.

[0117] It is understandable that other public search spaces are any possible public search spaces that are different from the public search space used for random access.

[0118] In the random access method provided in this disclosure, when the initial DL BWP includes a common search space for random access and at least one other common search space, the initial DL BWP configured by the network device includes an SSB, and the initial DL BWP supports random access by the terminal in connected state, ensuring that RedCap terminals that need to transmit terminal-specific information can complete random access on the initial DL BWP. Especially for RedCap terminals that require all BWPs to have an SSB, communication failures will not occur.

[0119] In a random access method provided in this disclosure, the network device can configure the center frequency of the initial DL BWP to be consistent with the center frequency of the initial UL BWP configured for the terminal under certain conditions. For example, in a TDD system, the network device can configure the center frequency of the initial DL BWP to be consistent with the center frequency of the initial UL BWP configured for the terminal.

[0120] Figure 4 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 4 As shown, this random access method can be used in network devices, and the method may include the following steps:

[0121] In step S31, an initial DL BWP is configured for the terminal. The initial DL BWP supports random access by the terminal in connected mode, and the center frequency of the initial DL BWP is consistent with the center frequency of the initial UL BWP.

[0122] In a random access method provided in this embodiment, the network device is configured to have the center frequency of the initial DL BWP consistent with that of the initial UL BWP, thereby avoiding communication failures of the terminal due to the inconsistency of the center frequencies of the initial DL BWP and the initial UL BWP.

[0123] In a random access method provided in this disclosure, where the initial DL BWP supports random access by the terminal in connected mode, the network device can also use the initial DL BWP to send terminal-specific information. This specific information can also be referred to as terminal-specific information. For example, the terminal-specific information can be DCI scrambled by C-RNTI. It is understood that the network device can transmit the terminal-specific information within the common search space configured in the initial DL BWP.

[0124] In one example, in the random access method provided in this embodiment of the present disclosure, the network device configures an initial DLBWP for the terminal to support random access in the connected state, and when the center frequency of the initial DLBWP is consistent with the center frequency of the initial ULBWP, the network device uses the initial DLBWP to send the terminal's exclusive information.

[0125] In a random access method provided in this disclosure, where the initial DL BWP supports random access by the terminal in connected mode, the configuration information configured by the network device can also be used to determine that the initial DL BWP is not used to send terminal-specific information. In other words, the network device can inform the RedCap terminal through the configuration information that it will not send terminal-specific information on the initial DL BWP. Therefore, the terminal does not need to monitor the initial DL BWP to determine whether it has received terminal-specific information. Thus, this disclosure avoids communication failures caused by the RedCap terminal's inability to transmit terminal-specific information.

[0126] In a random access method provided in this disclosure, the network device can be configured to determine that the initial DL BWP is not used to send terminal-specific information when the initial DL BWP does not contain an SSB. This allows the network device to avoid monitoring terminal-specific information within the common search space (CSS) when a RedCap terminal switches to the initial DL BWP for random access. For example, terminal-specific DCIs are not detected within the CSS.

[0127] In this way, the initial DL BWP configured on the network device can ensure that RedCap terminals complete the corresponding random access based on the initial DL BWP, thus avoiding communication failures. Especially for RedCap terminals that require all BWPs to have an SSB, random access can be completed on the initial DL BWP, and the terminal-specific DCI on the initial DL BWP does not need to be monitored, thereby avoiding communication failures.

[0128] In a random access method provided in this embodiment, the initial DLBWP configured by the network device for the terminal may not support random access by the terminal in the connected state.

[0129] It is understandable that when the initial DL BWP configured for the terminal by the network device does not support random access by the RedCap terminal in connected mode, it can avoid the communication failure that occurs when the RedCap terminal, which especially requires all BWPs to have SSB, completes random access on the initial DL BWP.

[0130] In a random access method provided in this embodiment, the network device configures the initial DL BWP to not support random access by the terminal in the connected state when it determines that the set conditions are met.

[0131] In a random access method provided in this embodiment, when the configured initial DL BWP does not contain an SSB, the network device can configure the initial DL BWP to not support random access by the terminal in the connected state.

[0132] Figure 5 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 5 As shown, this random access method can be used in network devices, and the method may include the following steps:

[0133] In step S41, an initial DL BWP is configured for the terminal. This initial DL BWP does not include an SSB, and the initial DL BWP does not support random access by the terminal in connected mode.

[0134] In the random access method provided in this disclosure, when the initial DL BWP configured in the network device does not contain an SSB, the initial DL BWP can be configured to not support random access by RedCap terminals in connected mode. This can avoid communication failures when RedCap terminals, which especially require all BWPs to have an SSB, complete random access on an initial DL BWP that does not contain an SSB.

[0135] In a random access method provided in this embodiment of the present disclosure, in a TDD system, when the center frequency of the initial DL BWP configured by the network device is inconsistent with the center frequency of the initial UL BWP configured, the network device configures the initial DL BWP to not support random access by the terminal in the connected state.

[0136] Figure 6 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 6 As shown, this random access method can be used in network devices, and the method may include the following steps:

[0137] In step S51, an initial DL BWP is configured for the terminal. The center frequency of the initial DL BWP is different from that of the initial ULBWP, and the initial DL BWP does not support random access by the terminal in connected mode.

[0138] In the random access method provided in this embodiment of the present disclosure, in a TDD system, the center frequency of the initial DLBWP configured by the network device is inconsistent with the center frequency of the initial UL BWP. The network device is configured such that the initial DL BWP does not support random access by the terminal in the connected state. This can avoid communication failure when the RedCap terminal performs random access when the center frequency of the initial DL BWP is inconsistent with the center frequency of the initial UL BWP.

[0139] In a random access method provided in this disclosure, the configuration information determined by the network device can also be used to determine the active BWP configured for the terminal. This active BWP includes random access resources for the terminal to perform random access. These random access resources can be physical random access channel (PRACH) resources. In other words, the active BWP monitored by the RedCap terminal contains PRACH resources. It is understood that the active BWP is a different UL BWP from the initial UL BWP.

[0140] In one example of a random access method provided in this disclosure, a network device is configured with an initial DL BWP that does not support random access by a terminal in connected state, and an active BWP. The active BWP includes random access resources for the terminal to perform random access.

[0141] In a random access method provided in this embodiment, the active BWP is different from the initial DL BWP, which does not support random access by the terminal in the connected state.

[0142] By configuring a certain initial DL BWP to not support random access by the terminal in connected mode, and an active BWP, the network device can ensure that the terminal can complete the corresponding random access using other BWPs while not performing random access on the initial UL BWP, thus avoiding communication failures.

[0143] In a random access method provided in this embodiment, the configuration information determined by the network device can be signaling or predefined rules.

[0144] It is understood that the random access method performed by a network device in the embodiments of this disclosure allows the terminal to perform corresponding random access operations based on the configured BWP, thus avoiding communication failures. In some cases, it can prevent a terminal in connected state from operating on a BWP without an SSB. In other cases, it can prevent communication failures when the center frequencies of the uplink and downlink BWPs are inconsistent.

[0145] Based on the same concept, embodiments of this disclosure also provide a random access method executed by a terminal.

[0146] Figure 7 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 7As shown, this random access method can be used in a terminal, such as a RedCap terminal, and the method may include the following steps:

[0147] In step S61, configuration information is determined. This configuration information is used to determine the initial DLBWP configured for the terminal and to determine whether the initial DLBWP supports random access by the terminal in connected mode.

[0148] In some examples, the terminal may have pre-stored configured information, which the terminal can then directly determine. In other examples, the configuration information may be sent by a network device, which the terminal can then receive and determine. This disclosure does not limit the method of obtaining the configuration information.

[0149] In step S62, random access is performed based on the configuration information.

[0150] In this embodiment of the disclosure, the terminal can complete the corresponding random access based on the initial DL BWP used to determine whether the terminal supports random access in the connected state.

[0151] In the random access method provided in this disclosure, in some embodiments, the configuration information can be predefined rules. The terminal can pre-store the predefined rules and directly determine the configuration information based on the predefined rules. Of course, in other examples, the configuration information can also be signaling. The signaling can be determined and sent to the terminal by the network device, and the terminal receives the signaling sent by the network device.

[0152] In a random access method provided in this embodiment, the initial DL BWP can support random access by the terminal in a connected state. The terminal can then utilize this initial DL BWP for random access.

[0153] In a random access method provided in this embodiment, the initial DL BWP supports random access by the terminal in the connected state, and the initial DL BWP is configured with an SSB.

[0154] In this embodiment, the RedCap terminal completes random access on the initial DL BWP with an SSB. Especially for RedCap terminals that require all BWPs to have an SSB, communication failures will not occur.

[0155] In the random access method provided in this embodiment, the initial DL BWP may include a common search space for random access and at least one other common search space. The initial DL BWP is configured with an SSB, allowing the terminal to perform random access. The other common search spaces are any possible common search spaces different from the common search space used for random access. This ensures that the RedCap terminal can transmit terminal-specific information without communication failure.

[0156] In a random access method provided in this disclosure, the center frequency of the initial DL BWP is consistent with the center frequency of the initial UL BWP configured for the terminal. For example, in a TDD system, the center frequency of the initial DL BWP is consistent with the center frequency of the initial UL BWP configured for the terminal. This avoids communication failures caused by inconsistencies between the center frequencies of the initial DL BWP and the initial UL BWP.

[0157] Figure 8 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 8 As shown, when the initial DL BWP can support random access by the terminal in connected mode, the method may include the following steps:

[0158] In step S71, the exclusive information of the initial downlink BWP receiving terminal is utilized.

[0159] In one example, in the random access method provided in this embodiment of the present disclosure, a terminal in the connected state can perform random access according to the initial DL BWP, and if the center frequency of the initial DL BWP is consistent with the center frequency of the initial UL BWP, the terminal uses the initial DL BWP to receive the terminal's exclusive information.

[0160] In some examples, a terminal can utilize the initial DL BWP to receive terminal-specific information (or terminal-specific information) sent by the network device. For example, this could be DCI scrambled by C-RNTI. It is understood that the terminal can monitor the common search space configured in this initial DL BWP to receive the terminal-specific information when it is detected.

[0161] In this way, the terminal can complete the corresponding random access based on the configuration information, thus avoiding communication failure.

[0162] In a random access method provided in this disclosure, where the initial DL BWP supports random access by the terminal in connected mode, the configuration information is also used to determine that the initial downlink BWP is not used to transmit the terminal's proprietary information. Therefore, the terminal can know that the network device will not send its proprietary information on the initial DL BWP.

[0163] In a random access method provided in this disclosure, when the initial DL BWP does not contain an SSB, it can be determined that the initial DL BWP is not used to send terminal-specific information. Therefore, when switching to the initial DL BWP for random access, the terminal can avoid monitoring terminal-specific information within the CSS. For example, terminal-specific DCIs can be ignored within the CSS.

[0164] Figure 9 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 9 As shown, when the initial DL BWP does not contain an SSB, the method may include the following steps:

[0165] In step S81, the use of the initial downlink BWP receiving terminal's proprietary information is stopped.

[0166] In one example, in the random access method provided in this embodiment of the present disclosure, when the initial DL BWP does not contain an SSB, the terminal in the connected state can perform random access based on the initial DL BWP, and the terminal can stop using the initial DL BWP to receive terminal-specific information.

[0167] In some examples, the terminal stops using the initial DL BWP to receive terminal-specific information (or terminal-specific information) sent by the network device. Understandably, the terminal can stop monitoring terminal-specific information in the public search space configured for this initial DL BWP; that is, the initial DL BWP does not contain an SSB, and when the terminal switches to this initial DL BWP, it can choose not to monitor terminal-specific DCIs within the CSS.

[0168] By using the above method, the configured initial DL BWP can ensure that RedCap terminals complete the corresponding random access based on the initial DLBWP, thus avoiding communication failures. Especially for RedCap terminals that require all BWPs to have an SSB, random access can be completed on the initial DL BWP, and the terminal-specific DCI on the initial DLBWP can be ignored, thereby preventing communication failures.

[0169] Figure 10 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 10 As shown, the method may include the following steps:

[0170] In step S91, the configured initial DL BWP does not support random access by the terminal in connected state, and the terminal stops using the initial DL BWP for random access.

[0171] In the random access method provided in this disclosure, the configured initial DL BWP does not contain an SSB, and the configured initial DL BWP does not support random access by the terminal in connected mode. This avoids communication failures when RedCap terminals, which especially require all BWPs to have an SSB, attempt random access on an initial DL BWP that does not contain an SSB.

[0172] In the random access method provided in this disclosure embodiment, in a TDD system, the center frequency point of the configured initial DLBWP is inconsistent with the center frequency point of the initial UL BWP configured for the terminal, and the configured initial DL BWP does not support random access by the terminal in connected mode. This avoids communication failures that occur when the RedCap terminal attempts random access when the center frequency point of the initial DL BWP is inconsistent with the center frequency point of the initial UL BWP.

[0173] In a random access method provided in this disclosure, configuration information can also be used to determine the active BWP configured for the terminal. This active BWP includes random access resources for the terminal to perform random access. The random access resources may be PRACH resources. In other words, the active BWP monitored by the RedCap terminal contains PRACH resources.

[0174] In a random access method provided in this disclosure, the active BWP is a different UL BWP than the initial UL BWP. In some embodiments, Figure 11 This is a flowchart illustrating a random access method according to an exemplary embodiment, such as... Figure 11 As shown, the method may include the following steps:

[0175] In step S101, random access is performed using the active BWP.

[0176] By configuring a certain initial DL BWP to not support random access in connected mode and an active BWP, the terminal can ensure that while it does not perform random access on the initial UL BWP, it can use other BWPs to complete the corresponding random access, thus avoiding communication failures.

[0177] In some embodiments, the configuration information described above may be signaling or predefined rules.

[0178] It is understood that the random access method executed by the terminal provided in this disclosure allows the terminal to perform corresponding random access operations by utilizing a configured BWP, thereby avoiding communication failures. In some cases, it can prevent the terminal in connected state from operating on a BWP without an SSB. In other cases, it can prevent communication failures when the center frequencies of the uplink and downlink BWPs are inconsistent.

[0179] It should be understood that the execution methods of terminals and network devices are similar. Therefore, for details, please refer to the corresponding descriptions in the network devices, which will not be repeated here.

[0180] It should be noted that those skilled in the art will understand that the various implementation methods / embodiments described above in this disclosure can be used in conjunction with the foregoing embodiments, or they can be used independently. Whether used alone or in conjunction with the foregoing embodiments, the implementation principle is similar. In this disclosure, some embodiments are described as implementations used together. Of course, those skilled in the art will understand that such illustrative examples are not intended to limit the embodiments of this disclosure.

[0181] Based on the same concept, embodiments of this disclosure also provide a random access device.

[0182] It is understood that the random access device provided in this disclosure includes hardware structures and / or software modules corresponding to each function in order to achieve the above-mentioned functions. In conjunction with the units and algorithm steps of the various examples disclosed in this disclosure, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of this disclosure.

[0183] Figure 12 This is a schematic diagram illustrating a random access device according to an exemplary embodiment. (Refer to...) Figure 12The device 200 may be a base station, and the device 200 may include:

[0184] The determination module 201 is used to determine configuration information, which is used to determine the initial downlink partial bandwidth (BWP) configured for the terminal and to determine whether the initial downlink BWP supports random access by the terminal in connected mode.

[0185] In one implementation, the initial downlink BWP supports random access by the terminal in connected mode.

[0186] In one implementation, the initial downlink BWP is configured with a synchronization signal block (SSB).

[0187] In one implementation, the initial downlink BWP includes a common search space for random access and at least one other common search space, which is different from the common search space for random access.

[0188] In one implementation, the center frequency of the initial downlink BWP is the same as the center frequency of the initial uplink BWP configured for the terminal.

[0189] In one embodiment, the apparatus 200 further includes a transmission module 202 for transmitting terminal-specific information using the initial downlink BWP.

[0190] In one implementation, the configuration information is also used to determine that the initial downlink BWP is not used for transmitting terminal-specific information.

[0191] In one implementation, the initial downlink BWP does not include an SSB.

[0192] In one implementation, the initial downlink BWP does not support random access by the terminal in connected mode.

[0193] In one implementation, the initial downlink BWP does not include an SSB.

[0194] In one example implementation, the center frequency of the initial downlink BWP is inconsistent with the center frequency of the initial uplink BWP configured for the terminal.

[0195] In one embodiment, the configuration information is further used to determine the active BWP configured for the terminal, wherein the active BWP includes random access resources for the terminal to perform random access.

[0196] In one implementation, the activated BWP differs from the initial downlink BWP.

[0197] In one implementation, the configuration information is signaling or predefined rules.

[0198] Regarding the apparatus 200 in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments of the relevant methods, and will not be elaborated upon here.

[0199] Figure 13 This is a schematic diagram illustrating a random access device according to an exemplary embodiment. (Refer to...) Figure 13 The device 300 may be a terminal, such as a RedCap terminal, and the device 300 may include:

[0200] The determination module 301 is used to determine configuration information. The configuration information is used to determine the initial downlink partial bandwidth (BWP) configured for the terminal and to determine whether the initial downlink BWP supports random access by the terminal in connected mode.

[0201] Access module 302 is used for random access based on configuration information.

[0202] In one implementation, the initial downlink BWP supports random access by the terminal in connected mode. The access module 302 is further configured to perform random access using the initial downlink BWP.

[0203] In one implementation, the initial downlink BWP is configured with a synchronization signal block (SSB).

[0204] In one implementation, the initial downlink BWP includes a common search space for random access and at least one other common search space, which is different from the common search space for random access.

[0205] In one implementation, the center frequency of the initial downlink BWP is the same as the center frequency of the initial uplink BWP configured for the terminal.

[0206] In one embodiment, the device 300 further includes a receiving module 303, configured to receive terminal-specific information using the initial downlink BWP.

[0207] In one implementation, the configuration information is also used to determine that the initial downlink BWP is not used to transmit terminal-specific information.

[0208] In one implementation, the initial downlink BWP does not include an SSB.

[0209] In one embodiment, the device 300 further includes a receiving module 303 for stopping the use of the exclusive information of the initial downlink BWP receiving terminal.

[0210] In one implementation, the initial downlink BWP does not support random access by the terminal in connected mode; the access module 302 is further configured to stop using the initial downlink BWP for random access.

[0211] In one implementation, the initial downlink BWP does not include an SSB.

[0212] In one implementation, the center frequency of the initial downlink BWP is different from the center frequency of the initial uplink BWP configured for the terminal.

[0213] In one embodiment, the configuration information is further used to determine the active BWP configured for the terminal, wherein the active BWP includes random access resources for the terminal to perform random access.

[0214] In one implementation, the activated BWP is different from the initial downlink BWP; random access is performed based on configuration information, and the access module 302 is also used to perform random access using the activated BWP.

[0215] In one implementation, the configuration information is signaling or predefined rules.

[0216] Regarding the apparatus 300 in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments of the relevant methods, and will not be elaborated upon here.

[0217] Figure 14 This is a schematic diagram illustrating a device 400 for random access according to an exemplary embodiment. For example, device 400 may be provided as a base station or a server. (Refer to...) Figure 14 The device 400 includes a processing component 422, which further includes one or more processors, and memory resources represented by memory 432 for storing instructions executable by the processing component 422, such as application programs. The application programs stored in memory 432 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 422 is configured to execute instructions to perform the random access method corresponding to the network device described above.

[0218] Device 400 may also include a power supply component 426 configured to perform power management of device 400, a wired or wireless network interface 450 configured to connect device 400 to a network, and an input / output (I / O) interface 458. Device 400 may operate on an operating system stored in memory 432, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0219] Figure 15 This is a block diagram illustrating a device 500 for random access according to an exemplary embodiment. For example, device 500 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, RedCap terminal, etc.

[0220] Reference Figure 15 The device 500 may include one or more of the following components: processing component 502, memory 504, power component 506, multimedia component 508, audio component 510, input / output (I / O) interface 512, sensor component 514, and communication component 516.

[0221] Processing component 502 typically controls the overall operation of device 500, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 502 may include one or more processors 520 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 502 may include one or more modules to facilitate interaction between processing component 502 and other components. For example, processing component 502 may include a multimedia module to facilitate interaction between multimedia component 508 and processing component 502.

[0222] Memory 504 is configured to store various types of data to support the operation of device 500. Examples of this data include instructions for any application or method operating on device 500, contact data, phonebook data, messages, pictures, videos, etc. Memory 504 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0223] The power supply component 506 provides power to the various components of the device 500. The power supply component 506 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device 500.

[0224] Multimedia component 508 includes a screen that provides an output interface between the device 500 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 508 includes a front-facing camera and / or a rear-facing camera. When the device 500 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0225] Audio component 510 is configured to output and / or input audio signals. For example, audio component 510 includes a microphone (MIC) configured to receive external audio signals when device 500 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 504 or transmitted via communication component 516. In some embodiments, audio component 510 also includes a speaker for outputting audio signals.

[0226] I / O interface 512 provides an interface between processing component 502 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0227] Sensor assembly 514 includes one or more sensors for providing state assessments of various aspects of device 500. For example, sensor assembly 514 may detect the on / off state of device 500, the relative positioning of components such as the display and keypad of device 500, changes in the position of device 500 or a component of device 500, the presence or absence of user contact with device 500, the orientation or acceleration / deceleration of device 500, and temperature changes of device 500. Sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 514 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0228] Communication component 516 is configured to facilitate wired or wireless communication between device 500 and other devices. Device 500 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 516 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 516 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0229] In an exemplary embodiment, device 500 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0230] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 504 including instructions, which can be executed by a processor 520 of device 500 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0231] The configuration information of the initial downlink BWP configured for the terminal is determined in this disclosure. This information is used to determine whether the initial downlink BWP supports random access by the terminal in connected mode, so that the terminal can perform corresponding random access operations according to the configured BWP and avoid communication failure.

[0232] It can be further understood that in this disclosure, "multiple" refers to two or more, and other quantifiers are similar. "And / or" describes the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. The singular forms "a," "the," and "the" are also intended to include the plural forms unless the context clearly indicates otherwise.

[0233] It is further understood that the terms "first," "second," etc., are used to describe various types of information, but this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another, and do not indicate a specific order or degree of importance. In fact, the expressions "first," "second," etc., are completely interchangeable. For example, without departing from the scope of this disclosure, first information can also be referred to as second information, and similarly, second information can also be referred to as first information.

[0234] It is further understood that although operations are described in a specific order in the accompanying drawings in the embodiments of this disclosure, this should not be construed as requiring these operations to be performed in the specific order or serial order shown, or requiring all of the shown operations to be performed to obtain the desired result. In certain environments, multitasking and parallel processing may be advantageous.

[0235] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein.

[0236] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A random access method, characterized in that, Applied to network devices, the method includes: The configuration information is determined, which is used to determine the initial downlink partial bandwidth (BWP) configuration for the terminal and to determine whether the initial downlink BWP supports random access in connected mode. Send the configuration information to the terminal; The initial downlink BWP is configured with a synchronization signal block (SSB), and the initial downlink BWP supports the terminal to perform random access in the connected state. The initial downlink BWP does not include the synchronization signal block (SSB), and the initial downlink BWP does not support the terminal performing random access in connected mode.

2. The method according to claim 1, characterized in that, The initial downlink BWP includes a common search space for random access and at least one other common search space, which is different from the common search space for random access.

3. The method according to any one of claims 1 to 2, characterized in that, The center frequency of the initial downlink BWP is the same as the center frequency of the initial uplink BWP configured for the terminal.

4. The method according to claim 1, characterized in that, The method further includes: The terminal's proprietary information is transmitted using the initial downlink BWP.

5. The method according to claim 1, characterized in that, The configuration information is also used to determine that the initial downlink BWP is not used to send the terminal's proprietary information.

6. The method according to claim 1, characterized in that, The center frequency of the initial downlink BWP is inconsistent with the center frequency of the initial uplink BWP configured for the terminal.

7. The method according to claim 1, characterized in that, The configuration information is also used to determine the activation of BWP for the terminal, wherein the activated BWP includes random access resources for the terminal to perform random access.

8. The method according to claim 7, characterized in that, The activated BWP is different from the initial downlink BWP.

9. A random access method, characterized in that, Applied to a terminal, the method includes: The configuration information is received, which is used to determine the initial downlink partial bandwidth (BWP) configuration for the terminal and to determine whether the initial downlink BWP supports random access in connected mode. The initial downlink BWP is configured with a synchronization signal block (SSB), and the initial downlink BWP supports the terminal to perform random access in the connected state. The initial downlink BWP does not include the synchronization signal block (SSB), and the initial downlink BWP does not support the terminal performing random access in connected mode.

10. The method according to claim 9, characterized in that, The initial downlink BWP includes a common search space for random access and at least one other common search space, which is different from the common search space for random access.

11. The method according to any one of claims 9 to 10, characterized in that, The center frequency of the initial downlink BWP is the same as the center frequency of the initial uplink BWP configured for the terminal.

12. The method according to claim 9, characterized in that, The method further includes: The terminal's proprietary information is received using the initial downlink BWP.

13. The method according to claim 9, characterized in that, The configuration information is also used to determine that the initial downlink BWP is not used to transmit the terminal's proprietary information.

14. The method according to claim 13, characterized in that, The method further includes: Stop using the initial downlink BWP to receive the terminal's proprietary information.

15. The method according to claim 9, characterized in that, The center frequency of the initial downlink BWP is inconsistent with the center frequency of the initial uplink BWP configured for the terminal.

16. The method according to claim 15, characterized in that, The configuration information is also used to determine the active BWP configured for the terminal, wherein the active BWP includes random access resources for the terminal to perform random access.

17. The method according to claim 16, characterized in that, The activated BWP is different from the initial downlink BWP; Random access is performed using the activated BWP.

18. A random access device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to perform the method described in any one of claims 1 to 8.

19. A random access device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to perform the method described in any one of claims 9 to 17.

20. A non-transitory computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the network device, the network device is able to perform the method according to any one of claims 1 to 8.

21. A non-transitory computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the mobile terminal, the mobile terminal is able to perform the method according to any one of claims 9 to 17.

Images