Method for enhancing random access, and electronic device and storage medium

Abstract

Provided in the embodiments of the present application are a method for enhancing random access, and an electronic device and a storage medium, which are applied to the technical field of wireless communications. The method comprises: determining at least one identity identifier; and receiving physical downlink control signaling scrambled by the identity identifier, and receiving a contention resolution packet on the basis of the physical downlink control signaling. The embodiments of the present application enable a user equipment to detect a plurality of identity identifiers, resolve a contention issue among the plurality of identity identifiers, and realize the determination of an identity identifier of the user equipment, thereby improving the efficiency of random access.

Description

A method, electronic device, and storage medium for enhancing random access. Technical Field

[0001] This application relates to the field of wireless communication technology, and more particularly to a method, electronic device, and storage medium for enhancing random access. Background Technology

[0002] Currently, preamble transmission and random access response reception in related technologies suffer from inefficiency. The User Equipment (UE) only detects a collision after receiving a downlink (DL) response message (Msg4) from the Contention Resolution Media Access Control (MAC) Control Element (MAC CE) whose contention resolution identifier (ID) does not match the UE's. In non-terrestrial networks (NTNs), restarting the entire random access procedure is extremely costly due to the very long round-trip time (RTT). Therefore, contention-based transmission of Msg3 can be used, eliminating the need for Msg1 or a random access response (RAR). Since UEs possess global navigation and positioning capabilities, they know their location before accessing an NTN cell and can determine satellite positions from ephemeris information broadcast in the System Information Block (SIB). Therefore, these NTN UEs can obtain effective timing advances based on their own location and satellite positions, making preamble transmission unnecessary. Building upon the existing 4-step random access support in NTN, Diversity Slotted Aloha (DSA) has been introduced to further enhance uplink capacity. This allows for the transmission of multiple copies / duplicates of Msg3 during the 4-step random access process. In DSA, the UE sends multiple copies / duplicates of Msg3 using different resources. If no collision occurs, the network can successfully receive any of these copies / duplicates. Since the Radio Network Temporary Identifier (RNTI) used for Msg4 transmission may be derived from the Physical Uplink Shared Channel (PUSCH) resources used for CB-Msg3 message transmission, UEs using different PUSCH resources to send multiple copies of Msg3 will use different RNTIs to transmit different copies / duplicates of Msg4 or contention-resolved messages. This requires the UE to start multiple contention-resolved timers after sending Msg3. If these timers overlap, the UE will have to monitor multiple RNTIs simultaneously. However, not all UEs have the capability to monitor multiple RNTIs simultaneously. Therefore, we continue with an enhanced random access approach to address the contention-based message detection problem. Summary of the Invention

[0003] This application provides an enhanced random access method, electronic device, and storage medium, which aims to enable the UE to detect contention resolution messages without monitoring multiple identity identifiers, thereby determining the identity identifier of the user equipment and improving random access efficiency.

[0004] This application provides an enhanced random access method, wherein the method is applied to a user equipment and includes:

[0005] Identify at least one identity identifier;

[0006] Obtain the physical downlink control signaling scrambled with the identity identifier, and obtain the contention resolution message based on the physical downlink control signaling.

[0007] This application also provides an electronic device, wherein the electronic device includes:

[0008] One or more processors;

[0009] Memory, used to store one or more programs;

[0010] When the one or more programs are executed by the one or more processors, the one or more processors implement the enhanced random access method as described in any of the embodiments of this application.

[0011] This application also provides a computer-readable storage medium storing one or more programs that are executed by one or more processors to implement the enhanced random access method as described in any of the embodiments of this application. Attached Figure Description

[0012] Figure 1 is a schematic diagram of an NTN network communication architecture provided in an embodiment of this application;

[0013] Figure 2 is an example diagram of information transmission based on resources within a time group according to an embodiment of this application;

[0014] Figure 3 is a flowchart of an enhanced random access method provided in an embodiment of this application;

[0015] Figure 4 is a flowchart of an enhanced random access method provided in an embodiment of this application;

[0016] Figure 5 is a flowchart of an enhanced random access method provided in an embodiment of this application;

[0017] Figure 6 is a detection example diagram showing that the first competition resolution window and the second competition resolution window do not overlap, provided in the embodiments of this application;

[0018] Figure 7 is an example diagram of the detection of partial overlap between the first competition resolution window and the second competition resolution window provided in the embodiments of this application;

[0019] Figure 8 is a detection example diagram showing that the first competition resolution window and the second competition resolution window completely overlap according to the embodiments of this application;

[0020] Figure 9 is a detection example diagram with only one contention resolution window provided in an embodiment of this application;

[0021] Figure 10 is an example diagram of effective PRACH timing provided in the embodiments of this application;

[0022] Figure 11 is an example diagram of another effective PRACH timing provided by an embodiment of this application;

[0023] Figure 12 is an example diagram of another effective PRACH timing provided in an embodiment of this application;

[0024] Figure 13 is an example diagram of another effective PRACH timing provided by an embodiment of this application;

[0025] Figure 14 is an example diagram of another effective PRACH timing provided by an embodiment of this application;

[0026] Figure 15 is an example diagram of another effective PRACH timing provided by an embodiment of this application;

[0027] Figure 16 is a schematic diagram of an enhanced random access device provided in an embodiment of this application;

[0028] Figure 17 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0029] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of this application.

[0030] In the following description, the use of suffixes such as “module,” “part,” or “unit” to denote elements is solely for the purpose of illustration in this application and has no particular meaning in itself. Therefore, “module,” “part,” or “unit” may be used interchangeably.

[0031] Transparent NTN is a satellite communication architecture in which the satellite acts solely as a radio frequency repeater and does not process the signal. In this mode, the satellite acts as a repeater, providing radio frequency relay forwarding functions, and data is transparently transmitted between the satellite and the ground gateway station. The structure of transparent NTN can be shown in Figure 1. The link between the UE and the satellite is the service link. The link between the base station (BS) and the satellite is a feeder link and is common to all UEs within the same cell.

[0032] To further enhance uplink capacity in the NTN network, a DSA mechanism is introduced. For DSA, M resources are combined together, such as combining the first resource and the second resource together, to form one "opportunity". N opportunities are combined together and called an opportunity group, as shown in Figure 2. UE A selects (resource 1, opportunity 1) and (resource 2, opportunity 2) to send Msg3 and receives it successfully; UE B selects (resource 3, opportunity 1) and (resource 3, opportunity 3) to send Msg3, but only Msg3 on (resource 3, opportunity 3) is successfully received; UE C selects (resource 3, opportunity 1) and (resource 1, opportunity 3) to send Msg3, but both fail to receive; UE D selects (resource 4, opportunity 1) and (resource 1, opportunity 2) to send Msg3, but only Msg3 on (resource 4, opportunity 1) is successfully received.

[0033] This application embodiment addresses a scenario in DSA where a UE transmits multiple copies / repeats of Msg3 using different resources. If no conflict occurs, the network can successfully receive any of these copies / repeats. Since the RNTI used for Msg4 transmission may be derived based on the PUSCH resources used for CB-Msg3 transmission, UEs using different PUSCH resources to transmit multiple copies of Msg3 will use different RNTIs to scramble different copies / repeats of Msg4 or contention resolution messages. Accordingly, the UE will start multiple contention resolution timers (MAC-contentionResolutionTimers) after transmitting Msg3. If there is overlap between the running times of multiple MAC-contentionResolutionTimers, the UE will have to monitor multiple RNTIs simultaneously. However, not all UEs have the ability to monitor multiple RNTIs simultaneously. Therefore, this application embodiment enhances the random access procedure triggered by contention-based Msg3. It is understood that the technical solutions provided in this application embodiment are also applicable to random access procedures without Msg1 and Msg2 in NR, LTE, LTE-A, eMTC, NB-IoT, and future mobile communications. In this sequence, Msg1 is either the Physical Random Access Channel (PRACH) or a preamble; Msg2 is one of the Physical Downlink Control Channel (PDCCH), Downlink Control Information (DCI), or a Random Access Response (RAR) scheduled by DCI signaling; and Msg3 is a message transmitted on the UL-SCH containing either a C-RNTI MAC CE or a CCCH SDU. Msg3 is also used for DTCH multiplexing in UP-EDT. Msg3 is submitted from the upper layer as part of the random access procedure and associated with the UE contention resolution identity. Msg4 is a DCI or a contention resolution message scheduled by DCI signaling. The contention resolution window can be a mac-ContentionResolutionTimer, which specifies the number of consecutive subframes the MAC entity monitors the PDCCH after Msg3 is sent.

[0034] Figure 3 is a flowchart of an enhanced random access method provided in an embodiment of this application. This embodiment is applicable to scenarios of preamble-free random access. The method can be executed by an enhanced random access device. As shown in Figure 3, the method provided in this embodiment specifically includes the following steps:

[0035] Step 110: Determine at least one identity identifier.

[0036] The identity identifier can be information used to identify information during random access. The identity identifier can include Cell-Radio Network Temporary Identifier (C-RNTI), Temporary Cell-Radio Network Temporary Identifier (TC-RNTTI), core network identity identifier, and other types of temporary wireless network identifiers.

[0037] In this embodiment, the user terminal can identify one or more identity identifiers and can transmit information with the base station through the identified identity identifiers.

[0038] Step 120: Receive physical downlink control signaling scrambled with identity identifiers, and receive contention resolution messages based on the physical downlink control signaling.

[0039] Among them, physical downlink control signaling can be used to transmit contention resolution messages, which are information used to resolve conflicts between multiple identities during random access.

[0040] Specifically, the base station can obtain the identity identifier of the user equipment based on the transmission resources of the received first message. The base station can scramble the physical downlink control signaling using the identity identifier and transmit the scrambled physical downlink control signaling to the user equipment. The base station can also schedule the transmission of contention resolution messages according to the physical downlink control signaling. The user equipment can receive the physical downlink control signaling scrambled with the identity identifier and receive the scheduled contention resolution messages according to the physical downlink control signaling. The first message may include the Msg3 message.

[0041] In this embodiment of the application, by determining the identity identifier, obtaining the physical downlink control signaling scrambled according to the identity identifier, and receiving the contention resolution message based on the physical downlink control signaling, the random access efficiency can be improved.

[0042] Figure 4 is a flowchart of an enhanced random access method provided in an embodiment of this application. This embodiment is a specific modification based on the above-described embodiment. Referring to Figure 4, the method provided in this embodiment specifically includes the following steps:

[0043] Step 210: Determine at least one identity identifier.

[0044] Step 220: Transmit the first message in at least two resources according to the determined identity identifier; wherein the first message transmitted in at least two resources is a repeated transmission of the same first message.

[0045] The first message may include a message sent by the user equipment to the base station (gNB or eNodeB) during the random access process to complete the random access process. The first message may carry the identity identifier of the user equipment. The first message may be used to resolve contention issues. The first message may include at least the Msg3 message.

[0046] In this embodiment of the application, the first message transmitted in different resources can be scrambled by multiple identified identifiers. The first message transmitted in different resources is a repeated transmission of the same first message. The scrambled first message can be transmitted to the base station in the corresponding resource.

[0047] Step 230: Receive physical downlink control signaling scrambled with identity identifiers, and receive contention resolution messages based on the physical downlink control signaling.

[0048] Based on the above application embodiments, the identity identifier is determined according to at least one of the following resources: time domain resource index for transmitting the first message, frequency domain resource index for transmitting the first message, code domain resource index for transmitting the first message, timing index for transmitting the first message, and index of resources for transmitting the first message.

[0049] In this embodiment, the identity identifier can be determined by at least one of the following: time-domain resource index, frequency-domain resource index, code-domain resource index, timing index, and resource index. The time-domain resource index may include Orthogonal Frequency Division Multiplexing (OFDM) symbol index, time slot index, subframe index, radio frame index, superframe index, etc.; the frequency-domain resource index includes frequency-domain resource index, resource block index, subcarrier index, etc.; the code-domain resource index includes orthogonal code index, non-orthogonal code index, etc.; and the timing index may include information indicating the timing in the DSA. In this embodiment, the first message transmitted on different resources has a specific identity identifier, which is determined based on the resource transmitting the first message.

[0050] In the embodiments of this application, the same first message transmitted in at least two resources may have a specific identity identifier, which may be determined by the resource transmitting the first message, such as the timing index of the first message transmission or the time slot index within the timing of the first message transmission.

[0051] In some other application embodiments, the Msg3 message carries at least the core network identity identifier of the user equipment.

[0052] In other application embodiments, the same first message transmitted on different resources has a common identity identifier, which is configured according to higher-level signaling.

[0053] In this embodiment of the application, the same first message transmitted in at least two resources may have a public identity identifier, which can be configured according to higher-level signaling.

[0054] Based on the above-described embodiments, the first message includes at least the Msg3 message. In an exemplary implementation, in DSA, the UE can transmit multiple copies / repetitions of the first message at multiple times, wherein the first message transmitted at multiple times can be a copy / repetition of the same first message, and the first messages transmitted at different times can be scrambled using different RNTIs. The RNTI can be determined by at least one of the following parameters:

[0055] Time-domain resource-related indexes, such as the first OFDM symbol index of the first resource, the first time slot index of the first resource, the first subframe index of the first resource, the first radio frame index of the first resource, and the first superframe index of the first resource;

[0056] Frequency domain resource-related indexes, such as the first frequency domain resource index of the first resource, the first resource block index of the first resource, and the first subcarrier index of the first resource;

[0057] Code field resource indexes, such as orthogonal code indexes and non-orthogonal code indexes;

[0058] Timing index and resource index.

[0059] In this embodiment of the application, when the first message includes a Msg3 message, the RNTIs corresponding to the multiple Msg3 messages sent by the user equipment can consider the following parameters:

[0060] 1. Multiple repetitions of the same Msg3 transmitted on different resources have a specific RNTI. The determination of the RNTI can consider at least one parameter among the time-domain resource-related index, frequency-domain resource-related index, code-domain resource-related index, timing index, and resource index. For example, Msg3 transmitted by UE A on (resource 1, timing 1) (e.g., A1-Msg3) corresponds to A1-RNTI; Msg3 transmitted on (resource 2, timing 2) (e.g., A2-Msg3) corresponds to A2-RNTI, where A1-RNTI is not equal to A2-RNTI, and A2-Msg3 is a repetition of A1-Msg3. The Msg3 message must contain at least the UE's core network identity identifier.

[0061] Furthermore, when the base station has the capability to receive multiple repetitions of MSG3 scrambled with different RNTIs, the base station responds to each received MSG3 (e.g., A1-Msg3, A2-Msg3) and scrambles it with the corresponding RNTI to send it to the UE (e.g., A1-Msg4, A2-Msg4). The Msg4 contains at least the UE's contention resolution ID (e.g., core network identity identifier). The UE receives the MSG4.

[0062] 2. Multiple repetitions of the same Msg3 transmitted on different resources have the same RNTI, i.e., a common RNTI, which can be configured by higher-layer signaling. For example, UE A transmits Msg3 (e.g., A1-Msg3) on (resource 1, timing 1), which corresponds to A1-RNTI; and transmits Msg3 (e.g., A2-Msg3) on (resource 2, timing 2), which corresponds to A2-RNTI. Here, A1-RNTI is equal to A2-RNTI, which is a common RNTI configured or pre-configured by higher-layer signaling. A2-Msg3 is a repetition of A1-Msg3. The Msg3 message must contain at least the UE's core network identity identifier.

[0063] Furthermore, the base station receives multiple repetitions of Msg3 scrambled using the common RNTI, and decodes the multiple core network identity identifiers carried by each received Msg3 to determine if they are consistent. For Msg3s with consistent core network identity identifiers, the base station responds only once, scrambles physical downlink control information using the common RNTI, and schedules Msg4 to be sent to the UE. Msg4 contains at least the UE's contention resolution ID (e.g., core network identity identifier) ​​and an identity identifier offset indication. The UE receives MSG4.

[0064] Figure 5 is a flowchart of an enhanced random access method provided in an embodiment of this application. This embodiment is a specific modification based on the above-described embodiments. Referring to Figure 5, the method provided in this embodiment specifically includes the following steps:

[0065] Step 310: Determine at least one identity identifier.

[0066] Step 320: Transmit the first message in at least two resources according to the determined identity identifier; wherein the first message transmitted in at least two resources is a repeated transmission of the same first message.

[0067] Step 330: Detect identity-scrambled physical downlink control signaling and the contention resolution message for physical downlink control signaling scheduling within at least one contention resolution window.

[0068] In this embodiment of the application, there can be one or more contention resolution windows. The user equipment can receive physical downlink control signaling scrambled with identity identifiers within the one or more contention resolution windows, and schedule the transmission of contention resolution messages through the received physical downlink control signaling. The user equipment can obtain contention resolution messages within the contention resolution window.

[0069] Furthermore, based on the above-described embodiments, the contention resolution message is detected within at least one contention resolution window, and the relationship between the contention resolution windows includes at least one of the following:

[0070] At least two competing resolution windows do not overlap;

[0071] At least two competing resolution windows partially overlap;

[0072] At least two competing resolution windows completely overlap.

[0073] In the embodiments of this application, the user equipment can obtain the contention resolution message within one or at least two contention resolution windows. There are at least two contention resolution windows, and the contention resolution windows may not overlap, partially overlap, or completely overlap.

[0074] In some embodiments, the timing of detecting identity-scrambled physical downlink control signaling and the contention resolution message for physical downlink control signaling scheduling within the contention resolution window includes at least one of the following:

[0075] After the first contention resolution window timer is started;

[0076] The first contention is resolved after the window timer restarts;

[0077] The first contention is resolved after the window timer is closed;

[0078] The first contention is resolved before the window timer closes;

[0079] The first contention resolution window timer expires;

[0080] The first contention resolution window timer expired;

[0081] The first contention resolves the issue after the window timer expires and restarts;

[0082] The second contention resolution window timer starts before it begins;

[0083] The second contention is resolved after the window timer is started.

[0084] In this embodiment of the application, detecting identity-scrambled physical downlink control signaling within the contention resolution window, and the contention resolution message for physical downlink control signaling scheduling, may include at least one of the following:

[0085] After the first contention resolution window timer is started, the physical downlink control signaling with identity scrambled and the contention resolution message of physical downlink control signaling scheduling are detected within the contention resolution window;

[0086] After the first contention resolution window timer restarts, the physical downlink control signaling with identity scrambled and the contention resolution message of physical downlink control signaling scheduling are detected within the contention resolution window.

[0087] After the first contention resolution window timer is closed, the identity-scrambled physical downlink control signaling and the contention resolution message of the physical downlink control signaling scheduling are detected within the contention resolution window.

[0088] Before the first contention resolution window timer closes, detect the identity-scrambled physical downlink control signaling and the contention resolution message of the physical downlink control signaling scheduling within the contention resolution window;

[0089] After the first contention resolution window timer expires, the physical downlink control signaling with identity scrambled and the contention resolution message of physical downlink control signaling scheduling are detected within the contention resolution window.

[0090] Before the first contention resolution window timer expires, detect the identity-scrambled physical downlink control signaling and the contention resolution message of the physical downlink control signaling scheduling within the contention resolution window;

[0091] After the first contention resolution window timer expires and restarts, the physical downlink control signaling with identity scrambled and the contention resolution message of the physical downlink control signaling scheduling are detected within the contention resolution window.

[0092] Before the second contention resolution window timer starts, the physical downlink control signaling with identity scrambled and the contention resolution message of physical downlink control signaling scheduling are detected within the contention resolution window.

[0093] After the second contention resolution window timer is started, the physical downlink control signaling with identity scrambled and the contention resolution message of physical downlink control signaling scheduling are detected within the contention resolution window.

[0094] Based on the above-described embodiments, the system receives identity-scrambled physical downlink control signaling and receives a contention resolution message based on the physical downlink control signaling, including at least one of the following:

[0095] In the first contention resolution window, detect the physical downlink control signaling scrambled by the first identity and the contention resolution message of the physical downlink control signaling scheduling;

[0096] The second contention resolution window detects the physical downlink control signaling scrambled by the second identity and the contention resolution message of the physical downlink control signaling scheduling;

[0097] In the window where the first contention resolution window and the second contention resolution window overlap, the physical downlink control signaling scrambled by the first identity and the second identity respectively, as well as the contention resolution message scheduled by the physical downlink control signaling, are detected.

[0098] The overlapping window can be the window corresponding to the overlapping portion of the first competition resolution window and the second competition resolution window.

[0099] In this embodiment, there can be multiple identity identifiers, including a first identity identifier and a second identity identifier. The first and second identity identifiers can scramble a first message transmitted in different resources, where the first message is a duplicate or copy of the same first message. The user equipment can receive physical downlink control signaling scrambled with the first identity identifier within a first contention resolution window, and schedule the transmission of the contention resolution message using the received physical downlink control signaling, thereby obtaining the contention resolution message within the first contention resolution window. The user equipment can also receive physical downlink control signaling scrambled with the second identity identifier within the first contention resolution window, and schedule the transmission of the contention resolution message using the received physical downlink control signaling. Furthermore, the user equipment can simultaneously detect physical downlink control signaling scrambled with the first and second identity identifiers respectively, as well as the contention resolution messages scheduled by them, within an overlapping window.

[0100] In some embodiments, the application further includes at least one of the following: using a first identity identifier as the identity identifier of the user equipment; or using a second identity identifier as the identity identifier of the user equipment.

[0101] In this embodiment of the application, a first identity identifier or a second identity identifier can be used as the identity identifier of the user equipment. The first identity identifier can be the identity identifier of the physical downlink control signaling and contention resolution message scrambled within the first contention resolution window, and the second identity identifier can be the identity identifier of the physical downlink control signaling and contention resolution message scrambled within the second contention resolution window. The first identity identifier and the second identity identifier can be determined by the user equipment based on the resources for transmitting the first message.

[0102] In some embodiments of the application, at least one of the following is also included:

[0103] The physical downlink control signaling with scrambled identity and the media access control layer protocol data unit were successfully decoded. The contention resolution window timer has been stopped.

[0104] The physical downlink control signaling with scrambled identity was detected, and decoding of the Media Interception Control Layer Protocol Data Unit failed.

[0105] No identity-scrambled physical downlink control signaling was detected.

[0106] In this embodiment, the user equipment stops the contention resolution window timer when it detects successful decoding of the identity-scrambled physical downlink control signaling and the Media Intervention Control Layer Protocol (Media Intervention Layer) data unit. The user equipment may also detect failure to decode the identity-scrambled physical downlink control signaling and the Media Intervention Layer Protocol (Media Intervention Layer) data unit; in this embodiment, the user equipment may also fail to detect identity-scrambled physical downlink control signaling.

[0107] Based on the above application embodiments, the contention resolution window timer includes at least one of the following: a first contention resolution window timer, a second contention resolution window timer, and a restarted first contention resolution window timer.

[0108] The second contention resolution window timer can be a different timer than the first contention resolution window timer. The durations of the first and second contention resolution windows can not overlap, partially overlap, or completely overlap. That is, the closing time of the first contention resolution timer is at least before the opening time of the second contention resolution timer, the closing time of the first contention resolution timer is after the opening time of the second contention resolution timer, and the opening times of the first and second contention resolution timers are perfectly aligned. The second contention resolution window timer can also be a timer that restarts the first contention resolution window timer.

[0109] Specifically, if the user equipment detects successful decoding of the identity-scrambled physical downlink control signaling and the Media Access Control Layer Protocol (MAC Layer) data unit in the first contention resolution window, it can stop the first contention resolution window timer; if the user equipment detects successful decoding of the identity-scrambled physical downlink control signaling and the MAC Layer ...

[0110] In some embodiments, at least one of the following is also included: detecting that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in the first message;

[0111] The core network identity identifier carried in the contention resolution message is found to be inconsistent with the core network identity identifier carried in the first message.

[0112] No physical downlink control signaling with scrambled identity was detected.

[0113] In this embodiment of the application, the user equipment may also compare the core network device identifier carried in the contention resolution message with the core network identity identifier carried in the first message to determine whether the core network identity identifier carried in the contention resolution message is consistent or inconsistent with the core network identity identifier carried in the first message. Alternatively, the user equipment may not detect physical downlink control signaling scrambled by the identity identifier.

[0114] In this application embodiment, the identity identifier includes at least one of the following: a specific identity identifier and a public identity identifier.

[0115] In some embodiments, at least one of the following is also included: race resolution successful; race resolution unsuccessful.

[0116] Based on the above-described embodiments, the method further includes: using the identity identifier of the contention resolution message that has been scrambled after the contention resolution is successfully resolved as the identity identifier of the user equipment.

[0117] In this embodiment of the application, when it is determined that the contention resolution is successful, the identity identifier corresponding to the contention resolution message that the contention resolution is successful can be used as the identity identifier of the user equipment. For example, the contention resolution message scheduled by the user equipment is successfully resolved by physical downlink control signaling scrambled with the first identity identifier. For example, if the physical downlink control signaling scrambled with the first identity identifier and the Media Intervention Control Layer Protocol Data Unit are successfully decoded, the contention resolution window timer is stopped. Furthermore, if the core network identity identifier carried by the contention resolution message is found to be consistent with the core network identity identifier carried by the first message, the contention resolution can be considered successful, and the first identity identifier can be used as the identity identifier of the user equipment.

[0118] In some embodiments, the user equipment further includes at least one of the following:

[0119] User equipment has the capability to receive physical downlink control signaling scrambled with at least two different identities, and to receive at least two contention resolution messages based on the physical downlink control signaling;

[0120] User equipment does not have the capability to receive physical downlink control signaling scrambled by at least two different identities, and to receive at least two contention resolution messages based on the physical downlink control signaling.

[0121] In the embodiments of this application, the user equipment may or may not have the ability to receive physical downlink control signaling scrambled by at least two different identities, and to receive at least two contention resolution messages based on the physical downlink control signaling.

[0122] In an exemplary implementation, taking the first message as an example of a Msg3 message, when the UE transmits multiple repetitions of Msg3, the base station can respond with one or more contention resolution messages. The UE can detect multiple contention resolution messages and can use the duration of the contention resolution messages scheduled by the aforementioned received physical downlink control signaling as a contention resolution window. The reception of multiple contention resolution messages can involve the UE receiving contention resolution messages within multiple contention resolution windows. The reception of the contention resolution messages can include the following scheme:

[0123] In one exemplary implementation, multiple contention resolution windows are non-overlapping:

[0124] (1) For the UE, there are multiple contention resolution windows that do not overlap. The multiple contention resolution windows correspond to multiple repetitions of Msg3 sent by the UE. The start of the second contention resolution window timer in the multiple contention resolution windows is after the start of the first contention resolution window timer, or the restart of the first contention resolution window timer is recorded as the second contention resolution window. See Figure 6. The detection examples of multiple contention resolution windows in (1) are shown in Table 1:

[0125] Table 1 Summary of UE detections at each contention resolution window

[0126] In some embodiments, the UE has the capability to receive contention resolution messages with multiple different RNTI scramblings:

[0127] 1) The UE determines the corresponding RNTI based on the transmission resources corresponding to each repetition and detects the PDCCH scrambled by the RNTI and its scheduled contention resolution message in at least one of the following methods.

[0128] a. After the first contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU is successfully decoded, the first contention resolution window timer stops, and the UE detects that the core network identity identifier carried in the contention resolution message matches the core network identity identifier carried in its sent Msg3 message. The UE then considers the first-stage contention resolution successful. After the first contention resolution window timer restarts or the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU is successfully decoded, the UE stops the second contention resolution window timer or stops the restarted first contention resolution window timer, and the UE detects that the core network identity identifier carried in the contention resolution message matches the core network identity identifier carried in its sent Msg3 message. The UE then considers the second-stage contention resolution successful. When either stage of contention resolution is successful, the UE considers random access successful, and the UE uses either the first RNTI corresponding to the first stage or the second RNTI corresponding to the second stage as its identity identifier. Or,

[0129] b. After the first contention resolution window timer is started, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message within the first contention resolution window. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU is successfully decoded, the first contention resolution window timer is stopped, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in the Msg3 message it sent, then the UE considers the first phase of contention resolution to be successful.

[0130] a) The UE cancels the detection of the PDCCH scrambled by the second RNTI and its scheduled contention resolution message within the second contention resolution window; the UE considers random access successful and uses the first RNTI of the first phase as its identity identifier. Alternatively,

[0131] b) After the first contention resolution window timer restarts or the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the second RNTI, then the UE considers the second-phase contention resolution to have failed, the UE considers random access to have succeeded, and uses the first RNTI of the first phase as its identity identifier. Or,

[0132] c. After the first contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the MAC PDU decoding fails and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, the first contention resolution window timer restarts. Alternatively, after the second contention resolution window timer starts, the UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the MAC PDU decoding succeeds and the second contention resolution window timer stops, or the restarted first contention resolution window timer stops, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the second-phase contention resolution successful; the UE considers random access successful and uses the second RNTI of the second phase as its identity identifier. Or,

[0133] d. After the first contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the first RNTI, then the first contention resolution window timer restarts or the second contention resolution window starts. The UE then continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the contention resolution to have failed. The UE considers this random access attempt to have failed and will re-initiate random access at an appropriate time.

[0134] In other application embodiments, multiple resolution windows partially overlap:

[0135] (2) For a given UE, when there are multiple contention resolution windows and the contention resolution windows overlap, the multiple contention resolution windows correspond to multiple repetitions of Msg3 sent by the UE, and the overlapping part of the contention resolution windows is recorded as the overlapping window (the second contention resolution window timer is started before the first contention resolution window timer is closed), as shown in Figure 7:

[0136] ① When the UE does not have the ability to receive multiple contention resolution messages with different RNTI scrambling at the same time, that is, it can only detect one RNTI scrambling contention resolution message within the overlapping window, (2) in multiple cases, the UE's detection summary in each contention resolution window is shown in Table 2:

[0137] Table 2 Summary of UE detections at each contention resolution window

[0138] 1) The UE determines the corresponding RNTI based on the transmission resources corresponding to each repetition and detects the PDCCH scrambled by the RNTI and its scheduling contention resolution message according to at least one of the following methods:

[0139] a. After the first contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU is successfully decoded, the first contention resolution window timer stops, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the first-stage contention resolution successful. After the first contention resolution window timer closes / stops / expires, the UE detects the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window (at this time, the second contention resolution window timer is started). If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU is successfully decoded, the second contention resolution window timer stops, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the second-stage contention resolution successful. The UE considers random access successful and uses either the first RNTI of the first stage or the second RNTI of the second stage as its identity identifier. Or,

[0140] b. After the first contention resolution window timer is started, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message within the first contention resolution window. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU is successfully decoded, the first contention resolution window timer is stopped, and the core network identity identifier carried in the detected contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the first phase of contention resolution to be successful.

[0141] a) Detection after UE cancellation; the UE considers random access successful and uses the first RNTI as its identity identifier. Or,

[0142] b) After the first contention resolution window timer closes, stops, or expires, the UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window (at which point the second contention resolution window timer is open). If the PDCCH scrambled by the second RNTI is detected, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the PDCCH scrambled by the second RNTI is not detected, then the UE uses the first RNTI of the first phase as its identity identifier and declares successful random access. Or,

[0143] c. After the first contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the first RNTI, then after the first contention resolution window timer closes or expires, the UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window (at this time, the second contention resolution window timer is started). If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU decoding is successful, the second contention resolution window timer stops, and the core network identity identifier carried in the detected contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the second-stage contention resolution successful; the UE considers random access successful and uses the second RNTI of the second stage as its identity identifier. Or,

[0144] d. After the first contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the first RNTI, then after the first contention resolution window timer closes or expires, the UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window (at this time, the second contention resolution window timer is already started). If the UE detects the PDCCH scrambled by the second RNTI, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the second RNTI, then the UE considers the contention resolution to have failed; the UE considers this random access attempt to have failed and will re-initiate random access at an appropriate time. Or,

[0145] e. After the first contention resolution window timer starts and before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU is successfully decoded, the first contention resolution window timer stops, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the first-stage contention resolution successful. After the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU is successfully decoded, the second contention resolution window timer stops, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the second-stage contention resolution successful. The UE considers random access successful if it uses either the first RNTI of the first stage or the second RNTI of the second stage as its own identity identifier. Alternatively,

[0146] f. After the first contention resolution window timer starts and before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message within the first contention resolution window. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU is successfully decoded, the first contention resolution window timer is stopped, and the core network identity identifier carried in the contention resolution message is found to be consistent with the core network identity identifier carried in the Msg3 message it sent, then the UE considers the first phase of contention resolution to be successful.

[0147] a) Detection after UE cancellation; the UE considers random access successful and uses the first RNTI of Phase 1 as its identity identifier. Or,

[0148] b) After the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or no PDCCH scrambled by the second RNTI is detected, the UE considers random access successful and uses the first RNTI of the first phase as its identity identifier. Or,

[0149] g. Before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the first RNTI, then after the second contention resolution window timer starts, the UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU decoding is successful, the second contention resolution window timer stops, and the core network identity identifier carried in the detected contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the second-stage contention resolution successful; the UE considers random access successful and uses the second RNTI of the second stage as its own identity identifier. Or,

[0150] h. Before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the first RNTI, then after the second contention resolution window timer starts, the UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the second RNTI, then the UE considers the contention resolution to have failed; the UE considers this random access to have failed and will re-initiate random access at an appropriate time.

[0151] ② When the UE has the ability to simultaneously receive multiple contention resolution messages with different RNTI scrambling, that is, it can detect multiple contention resolution messages with different RNTI scrambling within the overlapping window, the detection summary of the UE in each contention resolution window in multiple cases in (2) is shown in Table 3:

[0152] Table 3 Summary of UE detections at each contention resolution window

[0153] 1) The UE determines the corresponding RNTI based on the transmission resources corresponding to each repetition and detects the PDCCH scrambled by the RNTI and its scheduling contention resolution message according to at least one of the following methods.

[0154] a. After the first contention resolution window timer starts and before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message within the first contention resolution window. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU is successfully decoded, the first contention resolution window timer is stopped, and the core network identity identifier carried in the contention resolution message is found to be consistent with the core network identity identifier carried in the Msg3 message it sent, then the UE considers the contention resolution successful.

[0155] a) Detection after UE cancellation; the UE considers random access successful and uses the first RNTI as its identity identifier. Or,

[0156] b) After the second contention resolution window timer starts and before the first contention resolution window timer closes or expires, if the UE detects a PDCCH scrambled with the second RNTI within the overlapping window and the second contention resolution window after the first contention resolution window timer closes or expires, MAC PDU decoding fails, and / or the core network identity carried in the detected contention resolution message is inconsistent with the core network identity carried in its sent Msg3 message, or if no PDCCH scrambled with the second RNTI is detected, the UE considers random access successful and uses the first RNTI as its identity. Alternatively,

[0157] b. After the first contention resolution window timer starts and before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU decoding is successful, the first contention resolution window timer stops, and the core network identity identifier carried in the detected contention resolution message matches the core network identity identifier carried in its sent Msg3 message, then the UE considers the first phase of contention resolution successful. After the second contention resolution window timer starts and before the first contention resolution window timer closes or expires, the UE simultaneously detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages and the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the overlapping window. If either RNTI-scrambled PDCCH is detected and the MAC PDU decoding is successful, the UE stops the first contention resolution window timer. If the core network identity identifier carried in the detected contention resolution message matches the core network identity identifier carried in its sent Msg3 message, then the UE considers the first phase of contention resolution successful. If the PDU decoding is successful, the first and second contention resolution window timers are stopped. If the core network identity identifier carried in any RNTI-scrambled contention resolution message detected matches the core network identity identifier carried in its sent Msg3 message, the UE considers the second-stage contention resolution successful. Within the second contention resolution window after the first contention resolution window timer has closed or expired, the UE detects a contention resolution message scrambled by the second RNTI. If a PDCCH scrambled by the second RNTI is detected, the MAC PDU decoding is successful, the second contention resolution window timer is stopped, and the core network identity identifier carried in the detected contention resolution message matches the core network identity identifier carried in its sent Msg3 message, the UE considers the third-stage contention resolution successful. When any stage of contention resolution is successful, the UE considers random access successful, and the UE uses either the first or second RNTI of the corresponding stage as its identity identifier. Alternatively,

[0158] c. After the first contention resolution window timer starts and before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU is successfully decoded, the first contention resolution window timer is stopped, and the core network identity identifier carried in the detected contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the first phase contention resolution successful. After the second contention resolution window timer starts and before the first contention resolution window timer closes or expires, the UE simultaneously detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages and the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the overlapping window. If either RNTI-scrambled PDCCH is detected and the MAC PDU is successfully decoded, the first and second contention resolution window timers are stopped, and the core network identity identifier carried in either RNTI-scrambled contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the second phase contention resolution successful.

[0159] a) Detection after UE cancellation or cessation; when contention is resolved successfully at any stage, the UE considers random access successful, and the UE uses either the first RNTI or the second RNTI of the corresponding stage as its identity identifier. Or,

[0160] b) Within the second contention resolution window after the first contention resolution window timer has closed or expired, the UE detects the PDCCH scrambled by the second RNTI and its scheduled contention resolution message. If the UE detects the PDCCH scrambled by the second RNTI, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the second RNTI, then the UE considers the third-stage contention resolution to have failed. If any stage of contention resolution is successful, the UE considers random access successful, and the UE uses either the first RNTI or the second RNTI of the corresponding stage as its identity identifier. Or,

[0161] d. After the first contention resolution window timer starts and before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the first RNTI, then after the second contention resolution window timer starts and before the first contention resolution window timer closes or expires, the UE simultaneously detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages and the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the overlapping window. If either the RNTI-scrambled PDCCH is detected and the MAC PDU decoding fails, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the PDU decoding is successful, the first and second contention resolution window timers are stopped. If the core network identity identifier carried in any RNTI-scrambled contention resolution message matches the core network identity identifier carried in its sent Msg3 message, the UE considers the second-stage contention resolution successful. The UE continues to detect PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window after the first contention resolution window timer has closed or expired. If a PDCCH scrambled by the second RNTI is detected, the MAC PDU decoding is successful, the second contention resolution window timer is stopped, and the core network identity identifier carried in the detected contention resolution message matches the core network identity identifier carried in its sent Msg3 message, the UE considers the third-stage contention resolution successful. When any stage of contention resolution is successful, the UE considers random access successful, and the UE uses either the first or second RNTI of the corresponding stage as its identity identifier. Alternatively,

[0162] e. After the first contention resolution window timer starts and before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the first RNTI, then after the second contention resolution window timer starts and before the first contention resolution window timer closes or expires, the UE simultaneously detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages and the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the overlapping window. If either the RNTI-scrambled PDCCH is detected and the MAC PDU decoding is successful, the first and second contention resolution window timers are stopped, and if the core network identity identifier carried in either the detected RNTI-scrambled contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the second-stage contention resolution successful.

[0163] a) Detection after UE cancellation or cessation; when contention is resolved successfully at any stage, the UE considers random access successful, and the UE uses either the first RNTI or the second RNTI of the corresponding stage as its identity identifier. Or,

[0164] b) The UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window after the first contention resolution window timer closes or expires. If the second RNTI-scrambled PDCCH is detected, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or the second RNTI-scrambled PDCCH is not detected; when contention resolution is successful in any stage, the UE considers random access successful, and the UE uses either the first RNTI or the second RNTI of the corresponding stage as its identity identifier. Or,

[0165] f. After the first contention resolution window timer starts and before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE detects the PDCCH scrambled by the first RNTI, then after the second contention resolution window timer starts and before the first contention resolution window timer closes, the UE simultaneously detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages, and the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the overlapping window. If either RNTI-scrambled PDCCH is detected, MAC PDU decoding fails. If PDU decoding fails and / or if the core network identity identifier carried in multiple contention resolution messages scrambled by multiple RNTIs detected is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if no PDCCH scrambled by any RNTI is detected, then the UE continues to detect contention resolution messages scrambled by the second RNTI within the second contention resolution window after the first contention resolution window timer has closed or expired. If the core network identity identifier carried in the detected contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the UE considers the third-stage contention resolution successful; the UE considers this random access successful, and the UE uses the second RNTI of the third stage as its identity identifier. Alternatively,

[0166] g. After the first contention resolution window timer starts and before the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the MAC PDU fails to decode and / or the core network identity carried in the detected contention resolution message is inconsistent with the core network identity carried in its sent Msg3 message, or if the first RNTI scrambled PDCCH is not detected, then after the second contention resolution window timer starts and before the first contention resolution window timer closes, the UE continues to simultaneously detect the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages, and the second RNTI scrambled PDCCH and its scheduled contention resolution messages within the overlapping window. If either RNTI scrambled PDCCH is detected, the MAC PDU fails to decode and / or the core network identity carried in the detected contention resolution message is inconsistent with the core network identity carried in its sent Msg3 message, or if the first RNTI scrambled PDCCH is not detected, the UE continues to detect the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages, and the second RNTI scrambled PDCCH and its scheduled contention resolution messages, within the overlapping window. If the PDU decoding fails and / or the core network identity carried in multiple contention resolution messages scrambled by multiple RNTIs is inconsistent with the core network identity carried in the Msg3 message it sent, or if no RNTI-scrambled PDCCH is detected, the UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window after the first contention resolution window timer closes or expires. If the second RNTI-scrambled PDCCH is detected, and the MAC PDU decoding fails and / or the core network identity carried in the detected contention resolution messages is inconsistent with the core network identity carried in the Msg3 message it sent, or if the second RNTI-scrambled PDCCH is not detected, the UE considers the contention resolution to have failed; the UE considers this random access to have failed and will re-initiate random access at an appropriate time.

[0167] (3) For a certain UE, there are multiple contention resolution windows and the contention resolution windows overlap. The multiple contention resolution windows correspond to multiple repetitions of Msg3 sent by the UE. The first contention resolution window timer expires and restarts (i.e. the restarted window can be called the second contention resolution window), as shown in Figure 7.

[0168] ①The UE does not have the ability to simultaneously receive multiple contention resolution messages scrambled by different RNTIs. In multiple cases in (3), the UE's detection summary in each contention resolution window is shown in Table 4:

[0169] Table 4 Summary of UE detection in each competition window

[0170] 1) The UE determines the corresponding RNTI based on the transmission resources corresponding to each repetition and detects the PDCCH scrambled by the RNTI and its scheduling contention resolution message according to at least one of the following methods:

[0171] a. After the first contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU is successfully decoded, the first contention resolution window timer stops, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message. The UE then considers the first phase of contention resolution successful. After the first contention resolution window timer expires and restarts, the UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU is successfully decoded, the second contention resolution window timer stops, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message. The UE then considers the second phase of contention resolution successful. The UE considers random access successful and uses either the first RNTI of the first phase or the second RNTI of the second phase as its identity identifier. Or,

[0172] b. After the first contention resolution window timer is started, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message within the first contention resolution window. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU is successfully decoded, the first contention resolution window timer is stopped, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in the Msg3 message it sent, then the UE considers the first phase of contention resolution to be successful.

[0173] a) Detection after UE cancellation; the UE considers random access successful and uses the first RNTI as its identity identifier. Or,

[0174] b) After the first contention resolution window timer restarts, the UE detects the PDCCH scrambled by the second RNTI and its scheduled contention resolution message within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the second RNTI, then the UE uses the first RNTI of the first phase as its identity identifier and declares successful random access. Or,

[0175] c. After the first contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the first RNTI, the UE restarts after the first contention resolution window timer expires. The UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, MAC PDU decoding is successful, the restarted first contention resolution window timer stops, and if the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, the UE considers the second-stage contention resolution successful; the UE considers random access successful and uses the second RNTI of the second stage as its identity identifier. Or,

[0176] d. After the first contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution messages within the first contention resolution window. If the UE detects the PDCCH scrambled by the first RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the first RNTI, the UE restarts after the first contention resolution window timer expires. The UE continues to detect the PDCCH scrambled by the second RNTI and its scheduled contention resolution messages within the second contention resolution window. If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE does not detect the PDCCH scrambled by the second RNTI, the UE considers the contention resolution to have failed; the UE considers this random access to have failed and will initiate random access again at an appropriate time.

[0177] In other application embodiments, multiple resolution windows completely overlap:

[0178] (4) For a given UE, when there are multiple contention resolution windows and the contention resolution windows completely overlap, the multiple contention resolution windows correspond to multiple repetitions of Msg3 sent by the UE, and the overlapping part of the contention resolution windows is recorded as the overlapping window. The start of the second contention resolution window timer is completely aligned with the start of the first contention resolution window timer, as shown in Figure 8:

[0179] ① When the UE does not have the ability to receive multiple contention resolution messages with different RNTI scrambling at the same time, that is, it can only detect one RNTI scrambling contention resolution message within the overlapping window, (4) in multiple cases, the UE's detection summary in each contention resolution window is shown in Table 5.

[0180] Table 5 Summary of UE detections at each contention resolution window

[0181] 1) The UE determines the corresponding RNTI based on the transmission resources corresponding to each repetition and detects the PDCCH scrambled by the RNTI and its scheduling contention resolution message according to at least one of the following methods:

[0182] a. After the first contention resolution window timer starts and / or the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message within the overlapping window. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU decoding is successful, the first and / or second contention resolution window timers are stopped, and the core network identity identifier carried in the detected contention resolution message matches the core network identity identifier carried in its sent Msg3 message, then the contention resolution is successful, the UE considers random access successful, and uses the first RNTI as its identity identifier. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message does not match the core network identity identifier carried in its sent Msg3 message, or the PDCCH scrambled by the first RNTI is detected, then the contention resolution fails, the UE considers random access failed, and re-initiates random access at an appropriate time. Or,

[0183] b. After the first contention resolution window timer starts and / or the second contention resolution window timer starts, the UE detects the PDCCH scrambled by the second RNTI and its scheduled contention resolution message within the overlapping window. If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU decoding is successful, the first and / or second contention resolution window timers are stopped, and the UE detects that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the contention resolution is successful, the UE considers the random access successful, and uses the second RNTI as its identity identifier. If the UE detects the PDCCH scrambled by the second RNTI, the MAC PDU decoding fails, and / or the core network identity identifier carried in the detected contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the UE detects the PDCCH scrambled by the second RNTI, then the contention resolution fails, the UE considers the random access failed, and re-initiates random access at an appropriate time.

[0184] ② When the UE has the ability to simultaneously receive multiple contention resolution messages with different RNTI scrambling, that is, it can detect multiple contention resolution messages with different RNTI scrambling within the overlapping window, the detection summary of the UE in each contention resolution window in multiple cases in (4) is shown in Table 6:

[0185] Table 6 Summary of UE detection in each competition window

[0186] 1) The UE determines the corresponding RNTI based on the transmission resources corresponding to each repetition and detects the contention resolution message for the RNTI scrambling according to at least one of the following methods:

[0187] a. After the first contention resolution window timer starts and / or the second contention resolution window timer starts, the UE simultaneously detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message and the contention resolution message scrambled by the second RNTI within the overlapping window. If the detected PDCCH scrambled by the first RNTI is successfully decoded by the MAC PDU, the first and / or second contention resolution window timers are stopped, and the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message. Alternatively, if the detected PDCCH scrambled by the second RNTI is successfully decoded by the MAC PDU, the first and / or second contention resolution window timers are stopped, and the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the contention resolution is successful, the UE considers the random access to be successful, and uses the first RNTI or the second RNTI as its own identity identifier.

[0188] b. After the first contention resolution window timer starts and / or the second contention resolution window timer starts, the UE simultaneously detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message and the PDCCH scrambled by the second RNTI and its scheduled contention resolution message within the overlapping window. If the detected PDCCH scrambled by the first RNTI has a successful MAC PDU decoding, the first and / or second contention resolution window timers are stopped. The core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message. If the detected PDCCH scrambled by the second RNTI has a failed MAC PDU decoding and / or the core network identity identifier carried in the contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the detected PDCCH scrambled by the second RNTI has a failed MAC PDU decoding, then the contention resolution is successful, the UE still considers the random access to be successful, and uses the first RNTI as its own identity identifier.

[0189] c. After the first contention resolution window timer starts and / or the second contention resolution window timer starts, the UE simultaneously detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message and the contention resolution message scrambled by the second RNTI within the overlapping window. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU decoding fails and / or the core network identity identifier carried in the contention resolution message is inconsistent with the core network identity identifier carried in its sent Msg3 message, or if the PDCCH scrambled by the first RNTI is not detected, and the PDCCH scrambled by the second RNTI is detected, the MAC PDU decoding is successful. The first and / or second contention resolution window timers are stopped. If the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in its sent Msg3 message, then the contention resolution is successful, the UE still considers the random access to be successful, and uses the second RNTI as its own identity identifier.

[0190] d. The UE simultaneously detects the PDCCH scrambled by the first RNTI and its scheduled contention resolution message and the PDCCH scrambled by the second RNTI and its scheduled contention resolution message within the overlapping window. If multiple RNTI-scrambled PDCCHs are detected, all MAC PDUs fail to decode, and or the core network identity identifier carried in multiple contention resolution messages is inconsistent with the core network identity identifier carried in its sent Msg3 message, or no RNTI-scrambled PDCCH is detected, then the contention resolution fails, the UE considers the random access to have failed, and initiates random access again at an appropriate time.

[0191] In some application embodiments, only a single contention resolution window exists:

[0192] (5) For a given UE, when there is only one contention resolution window, the contention resolution window corresponds to multiple repetitions of Msg3 sent by the UE, as shown in Figure 9:

[0193] ① Within the first contention resolution window, the UE detects the PDCCH scrambled by the common RNTI and its scheduled contention resolution message. If the PDCCH scrambled by the first RNTI is detected, the MAC PDU is successfully decoded, the timer of the first contention resolution window is stopped, and the core network identity identifier carried in the contention resolution message is found to be consistent with the core network identity identifier carried in its sent Msg3 message, then the contention resolution is successful, and the UE considers the random access to be successful; and uses the identity identifier offset indication contained in the contention resolution message in conjunction with the common RNTI as its own identity identifier.

[0194] In some application embodiments, the UE determines a valid (or available) PRACH timing (RO) based on at least one of a reference point and an offset value, and then sends a PRACH.

[0195] In non-terrestrial networks (NTNs), satellites can cover vast areas with a limited number of synchronous beams. Beam hopping can be used to facilitate coverage over large areas by allowing each beam to serve a smaller area. In some implementations, coverage availability based on beam hopping patterns can be adapted to traffic loads in different areas. Due to beam hopping, user equipment (UEs) can send or receive signals while the serving beam is active. For PRACH timing, the UE needs to determine which PRACH timings are valid or available, and then send PRACH on those valid or available PRACH timings.

[0196] In some application embodiments, the reference point may be at least one of the following:

[0197] 1. The start time of SFN0 or SFN512;

[0198] 2. The start time of the Synchronization Signal Block (SSB) detected by the UE;

[0199] 3. The end time of the SSB detected by the UE.

[0200] In the above-mentioned application embodiments, the time can be accurate to the symbol level, slot level, millisecond level, subframe level, or frame level.

[0201] In some application embodiments, the offset value can be at the symbol level, slot level, millisecond level, subframe level, or frame level. The offset value can be cell-specific (i.e., the same value is used throughout the cell), per SSB (each SSB has an offset value), or per SSB periodicity (SSBs with the same period use the same offset value, while SSBs with different periods use independent offset values).

[0202] Specifically, the offset value can include one of the following:

[0203] 1. Base station configuration values;

[0204] 2. Predefined values;

[0205] 3. Timing advance (TA) value, such as the timing advance of pre-compensation;

[0206] 4. Koffset;

[0207] 5. Round-trip time between the satellite and the UE;

[0208] 6. Round-trip time between the UE and the base station;

[0209] 7. Round-trip time between the UE and the reference point;

[0210] 8. The duration (stay time) of the beam / position / cell / transmission configuration indicator (TCI) status corresponding to the SSB detected by the UE.

[0211] In some application embodiments, referring to Figure 10, the RO between the reference point and the reference point plus the offset value is a valid PRACH. The reference point is the SSB end time, and the offset value is the duration or dwell time during which the UE detects the beam, band, cell, transmission configuration indication (TCI) state corresponding to the SSB.

[0212] Furthermore, in some application embodiments, the location of the RO takes into account the impact of timed extraction.

[0213] In other embodiments, the RO (Reference Point) is valid for a time duration after the reference point plus an offset value. This duration can be configured or predefined, and can be symbol-level, slot-level, millisecond-level, subframe-level, or frame-level. Referring to Figure 11, the reference point is the SSB end time, and the RO position does not consider the effect of timing advance. The offset value can be at least one of the following:

[0214] 1. TA (timing advance) value;

[0215] 2. Koffset;

[0216] 3. Round-trip time between the satellite and the UE;

[0217] 4. Round-trip time between the UE and the base station;

[0218] 5. Round-trip time between the UE and the reference point.

[0219] In other embodiments, the first RO after adding an offset value to the reference point is valid. Referring to Figure 12, the RO position does not account for timing advance. This offset value includes at least one of the following:

[0220] 1. TA (timing advance) value;

[0221] 2. Koffset;

[0222] 3. Round-trip time between the satellite and the UE;

[0223] 4. Round-trip time between the UE and the base station;

[0224] 5. Round-trip time between the UE and the reference point.

[0225] In other application embodiments, the N Returns (ROs) after adding the offset value to the reference point are valid, where N is an integer, which can be configured by the base station or predefined. Referring to Figure 13, the reference point is the SSB end time, and N is 2. In some implementations, the value of N considers the duration (dwell time) of the beam, beam position, cell, and Transmission Configuration Indication (TCI) state corresponding to the SSB detected by the UE. The position of the ROs does not consider the effect of timing advance. The offset value includes at least one of the following:

[0226] 1. TA (timing advance) value;

[0227] 2. Koffset;

[0228] 3. Round-trip time between the satellite and the UE;

[0229] 4. Round-trip time between the UE and the base station;

[0230] 5. Round-trip time between the UE and the reference point.

[0231] In one exemplary implementation, the first RO after the reference point is valid. Referring to Figure 14, the reference point is the SSB end time, and the location of the RO takes into account the effect of timing advance.

[0232] In another exemplary implementation, N ROs following the reference point are valid, where N is an integer that can be configured by the base station or predefined. Referring to Figure 15, the reference point is the SSB end time, N is 3, and the location of the ROs takes into account the effect of timing advance.

[0233] Figure 16 is a schematic diagram of an enhanced random access device provided in an embodiment of this application. This device can execute the enhanced random access method provided in any embodiment of this application, and possesses the corresponding functional modules and beneficial effects for executing the method. This device can be implemented by software and / or hardware. The device provided in this embodiment specifically includes:

[0234] The identifier determination module 410 is used to determine at least one identity identifier.

[0235] The contention receiving module 420 is used to receive physical downlink control signaling scrambled with identity information and to receive contention resolution messages based on the physical downlink control signaling.

[0236] In some embodiments, the apparatus further includes a message transmission module 430, configured to transmit a first message in at least two resources based on a determined identity identifier; wherein the first message transmitted in at least two resources is a repeated transmission of the same first message.

[0237] In some embodiments, the identifier determination module 410 determines the identity identifier based on at least one of the following resources:

[0238] The time-domain resource index for transmitting the first message, the frequency-domain resource index for transmitting the first message, the code-domain resource index for transmitting the first message, the timing index for transmitting the first message, and the index of resources for transmitting the first message.

[0239] In some embodiments, the first messages transmitted on different resources in the message transmission module 430 have specific identifiers, which are determined based on the resources on which the first messages are transmitted.

[0240] Based on the above application embodiments, the first message carries at least the core network identity identifier of the user equipment.

[0241] In some application embodiments, the same first message transmitted on different resources in the message transmission module 430 has a common identity identifier, which is configured according to higher-level signaling.

[0242] In some embodiments, the contention receiving module 420 includes:

[0243] The window receiving unit is used to detect identity-scrambled physical downlink control signaling and contention resolution messages for physical downlink control signaling scheduling within at least one contention resolution window.

[0244] In some embodiments, the execution timing of the window receiving unit in the contention receiving module 420 includes at least one of the following:

[0245] After the first contention resolution window timer is started;

[0246] The first contention is resolved after the window timer restarts;

[0247] The first contention is resolved after the window timer is closed;

[0248] The first contention is resolved before the window timer closes;

[0249] The first contention resolution window timer expires;

[0250] The first contention resolution window timer expired;

[0251] The first contention resolves the issue after the window timer expires and restarts;

[0252] The second contention resolution window timer starts before it begins;

[0253] The second contention is resolved after the window timer is started.

[0254] In some embodiments, the contention receiving module 420 is specifically used for at least one of the following:

[0255] In the first contention resolution window, detect the physical downlink control signaling scrambled by the first identity and the contention resolution message of the physical downlink control signaling scheduling;

[0256] The second contention resolution window detects the physical downlink control signaling scrambled by the second identity and the contention resolution message of the physical downlink control signaling scheduling;

[0257] In the window where the first contention resolution window and the second contention resolution window overlap, the physical downlink control signaling scrambled by the first identity and the second identity respectively, as well as the contention resolution message scheduled by the physical downlink control signaling, are detected.

[0258] In some embodiments, the application further includes a decoding detection module, configured to: detect successful decoding of identity-scrambled physical downlink control signaling and Media Intervention Control Layer Protocol (MILD) data units, and stop the contention resolution window timer; detect failed decoding of identity-scrambled physical downlink control signaling and MILD data units; or detect no identity-scrambled physical downlink control signaling.

[0259] In some embodiments, the contention resolution window timer in the device includes at least one of the following:

[0260] First contention resolution window timer, second contention resolution window timer, restarted first contention resolution timer.

[0261] In some embodiments, the apparatus further includes an information comparison module, configured to: detect that the core network identity identifier carried in the contention resolution message is consistent with the core network identity identifier carried in the first message; or detect that the core network identity identifier carried in the contention resolution message is inconsistent with the core network identity identifier carried in the first message.

[0262] In some embodiments, the apparatus is also used for at least one of the following: successful contention resolution; failed contention resolution.

[0263] In some embodiments, the apparatus is also used to stop detecting the physical downlink control signaling scrambled by the identity identifier and the contention resolution message of the physical downlink control signaling scheduling within the contention resolution window after the contention resolution is successful.

[0264] In some embodiments, the apparatus is further configured to: use a first identity identifier as the identity identifier of the user equipment; or use a second identity identifier as the identity identifier of the user equipment.

[0265] In some embodiments, the user equipment further includes at least one of the following:

[0266] User equipment has the capability to receive physical downlink control signaling scrambled with at least two different identities, and to receive at least two contention resolution messages based on the physical downlink control signaling;

[0267] User equipment does not have the capability to receive physical downlink control signaling scrambled by at least two different identities, and to receive at least two contention resolution messages based on the physical downlink control signaling.

[0268] In some application embodiments, the identity identifier includes at least one of the following:

[0269] Specific identity identifiers and public identity identifiers.

[0270] Figure 17 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device includes a processor 10, a memory 11, an input device 12, and an output device 13. The number of processors 10 in the electronic device can be one or more. Figure 17 shows one processor 10 as an example. The processor 10, memory 11, input device 12, and output device 13 in the electronic device can be connected by a bus or other means. Figure 17 shows a connection via a bus as an example.

[0271] The memory 11, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the modules corresponding to the device in the embodiments of this application (identifier determination module 410 and contention receiving module 420). The processor 10 executes various functional applications and data processing of the electronic device by running the software programs, instructions, and modules stored in the memory 11, thereby implementing the enhanced random access method described above.

[0272] The memory 11 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on the use of the electronic device. Furthermore, the memory 11 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory, or other non-volatile solid-state storage device. In some instances, the memory 11 may further include memory remotely located relative to the processor 10, which can be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0273] Input device 12 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the electronic device. Output device 13 may include display devices such as a display screen.

[0274] This application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform an enhanced random access method, the method comprising:

[0275] Identify at least one identity identifier;

[0276] Receive the physical downlink control signaling scrambled with the identity identifier, and receive a contention resolution message based on the physical downlink control signaling.

[0277] Based on the above description of the implementation methods, those skilled in the art can clearly understand that this application can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0278] It is worth noting that in the embodiments of the above-mentioned device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.

[0279] Those skilled in the art will understand that all or some of the steps, apparatuses, or functional modules / units in the methods disclosed above can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0280] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. The corresponding software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, cartridges, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0281] The above description, with reference to the accompanying drawings, illustrates preferred embodiments of this application, but does not limit the scope of this application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of this application shall be within the scope of this application.

Claims

1. A method for enhancing random access, applied to a user equipment, the method comprising: Identify at least one identity identifier; Receive physical downlink control signaling scrambled with the at least one identity identifier, and receive a contention resolution message based on the physical downlink control signaling.

2. The method according to claim 1, further comprising: The first message is transmitted in at least two resources based on the determined at least one identity identifier; Wherein, the first message transmitted in the at least two resources is a repeated transmission of the same first message.

3. The method according to claim 2, wherein, The at least one identity identifier is determined based on at least one of the following resources: The time-domain resource index for transmitting the first message, the frequency-domain resource index for transmitting the first message, the code-domain resource index for transmitting the first message, the timing index for transmitting the first message, and the index of resources for transmitting the first message.

4. The method according to claim 2, wherein, The first message transmitted on different resources has a specific identity identifier, and the at least one identity identifier is determined according to the resource on which the first message is transmitted.

5. The method according to claim 2 or 4, wherein, The first message carries at least the core network identity identifier of the user equipment.

6. The method according to claim 2, wherein, The same first message transmitted on different resources has a common identity identifier, which is configured according to higher-level signaling.

7. The method according to claim 2, wherein, The step of receiving physical downlink control signaling scrambled with the at least one identity identifier, and receiving a contention resolution message based on the physical downlink control signaling, includes: The at least one identity-scrambled physical downlink control signaling and the contention resolution message scheduled by the physical downlink control signaling are detected within at least one contention resolution window.

8. The method according to claim 7, wherein, The timing of detecting the at least one identity-scrambled physical downlink control signaling and the contention resolution message scheduled by the physical downlink control signaling within at least one contention resolution window includes at least one of the following: After the first contention resolution window timer is started; The first contention is resolved after the window timer restarts; The first contention is resolved after the window timer is closed; The first contention is resolved before the window timer closes; The first contention resolution window timer expires; The first contention resolution window timer expired; The first contention resolves the issue after the window timer expires and restarts; The second contention resolution window timer starts before it begins; The second contention is resolved after the window timer is started.

9. The method according to claim 1 or 7, wherein, The step of receiving physical downlink control signaling scrambled with the at least one identity identifier, and receiving a contention resolution message based on the physical downlink control signaling, includes at least one of the following: The first contention resolution window detects physical downlink control signaling scrambled by the first identity and the contention resolution message scheduled by the physical downlink control signaling; The second contention resolution window detects the physical downlink control signaling scrambled by the second identity and the contention resolution message scheduled by the physical downlink control signaling; In the window where the first contention resolution window and the second contention resolution window overlap, the physical downlink control signaling scrambled by the first identity and the second identity respectively, and the contention resolution message scheduled by the physical downlink control signaling are detected.

10. The method according to claim 1 or 7, further comprising at least one of the following: Upon successful decoding of the physical downlink control signaling scrambled with at least one identity and the Media Intervention Control Layer Protocol data unit, the contention resolution window timer is stopped. The decoding of the physical downlink control signaling and the media access control layer protocol data unit scrambled by the at least one identity was detected to have failed. No physical downlink control signaling scrambled with the at least one identity was detected.

11. The method according to claim 10, wherein, The race resolution window timer includes at least one of the following: First contention resolution window timer, second contention resolution window timer, restarted first contention resolution timer.

12. The method of claim 7, further comprising at least one of the following: The core network identity identifier carried in the contention resolution message is detected to be consistent with the core network identity identifier carried in the first message. The core network identity identifier carried in the contention resolution message is found to be inconsistent with the core network identity identifier carried in the first message.

13. The method of claim 12, further comprising at least one of the following: The competition was successfully resolved; The competition failed to resolve the issue.

14. The method according to claim 13, further comprising: If contention resolution is successful, the detection of at least one identity-scrambled physical downlink control signaling and the contention resolution message scheduled by the physical downlink control signaling within at least one contention resolution window is stopped.

15. The method of claim 9, further comprising at least one of the following: The first identity identifier shall be used as the identity identifier of the user equipment; The second identity identifier is used as the identity identifier of the user equipment.

16. The method according to claim 1 or 7, wherein, The user equipment also includes at least one of the following: The user equipment is capable of receiving at least two physical downlink control signaling messages scrambled with different identity identifiers, and receiving at least two contention resolution messages based on the physical downlink control signaling messages; The user equipment does not have the capability to receive physical downlink control signaling scrambled with at least two different identity identifiers, and to receive at least two contention resolution messages based on the physical downlink control signaling.

17. The method according to claim 1, 7, or 15, wherein, The at least one identity identifier includes at least one of the following: Specific identity identifiers and public identity identifiers.

18. The method according to any one of claims 2, 3, 4, 6 or 12, wherein, The first message includes at least the Msg3 message.

19. An electronic device comprising: At least one processor; The memory is configured to store at least one program. When the at least one program is executed by the at least one processor, the at least one processor implements the enhanced random access method as described in any one of claims 1-18.

20. A computer-readable storage medium storing at least one program, which is executed by at least one processor to implement the enhanced random access method as described in any one of claims 1-18.

Images