Patent Description:
The two-step random access procedure is a new implementation of the random access procedure introduced in Rel-<NUM> (Release <NUM>). The two-step random access procedure and the four-step random access procedure are quite different in terms of resource configuration and access process.

The existing methods and contents of random access reporting are designed based on four-step random access, and thus the existing process of reporting random access cannot reflect the two-step random access procedure. Therefore, the parameter configuration of the two-step random access procedure cannot be adaptively optimized according to the related parameters for the two-step random access procedure, and there is a technical problem that the optimization for parameter configuration of the two-step random access procedure is poor.

3GPP draft R2-<NUM> introduces further useful information in Logged measurements, RACH report.

Embodiments of the present disclosure provide methods and devices for reporting parameters for a two-step random access procedure for solving the above technical problem.

The technical solutions provided by the example embodiments of the present disclosure may have the following beneficial effects:.

The first message sent by the network device is received. The first message is used to indicate the terminal device to report a random access parameter list to the network device, and the random access parameter list includes a two-step random access parameter list or includes the two-step random access parameter list and a four-step random access parameter list. According to the first message, the random access parameter list is reported to the network device. Therefore, the terminal device reports the random access parameter list to the network device, so as to ensure that the network device can obtain the parameter list for the two-step random access.

It is to be understood that the foregoing general description and the following detailed description are exemplary only and are not intended impose limitations on the present disclosure.

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate example embodiments consistent with the present disclosure and together with the description serve to explain the principles of the present disclosure.

Example embodiments will be described below in detail and examples of the embodiments are illustrated in the accompanying drawings. Where the following description refers to the drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations in the following exemplary detailed descriptions are not intended to represent all implementations consistent with the implementations of the present disclosure. Rather, they are merely examples of methods and apparatus consistent with some aspects of the present disclosure as defined in the appended claims.

In the system architecture, an example communication system may be a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (LTE) system, a LTE Frequency Division Duplex (FDD) system, a LTE Time Division Duplex (TDD) system, an Advanced long term evolution (LTE-A) system, a New Radio (NR) system, an evolution system of NR system, a LTE-based access to unlicensed spectrum (LTE-U) system, a New Radio based access to unlicensed spectrum (NR-U), a Universal Mobile Telecommunication System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication systems, a Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next-generation communication systems or other communication systems.

The example communication system specifically includes a network device and a terminal. When the terminal accesses a mobile communication network provided by the network device, the terminal and the network device can communicate and be connected with each other through a wireless link, and the communication connection mode may be a single connection mode or a dual connection mode or a multi-connection mode. When the communication connection mode is the single connection mode, the network device may be an LTE base station or an NR base station (also known as a gNB base station). When the communication mode is the dual connection mode, it can be implemented by the carrier aggregation (CA) technology, or implemented by multiple network devices. The terminals involved in the example embodiments of the present disclosure may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of User Equipment (UE), Mobile Station (MS), terminal device and so on. For the convenience of description, the devices mentioned above are collectively referred to as terminal devices.

Additionally, the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B can mean three situations: A alone, B alone, and A and B together. In addition, the character "/" herein generally indicates that the related objects before or after "/" are in an "or" relationship.

It should be understood that, in the example implementations of the present disclosure, "B corresponding to A" means that B is associated with A, and B may be determined according to A. However, it should also be understood that determining B based on A does not mean determining B based only on A, but also determining B based on A and/or other information.

<FIG> is a system architecture of a communication system to which the following example embodiments of the present disclosure may be applied. The system architecture includes: a base station A and a terminal device B.

NR (new radio) Rel-<NUM> Self-Organizing Network (SON) can optimize network parameter configuration according to information reported by the terminal device B. The base station A obtains the terminal device information through the information reporting procedure of the terminal device B.

The base station A sends a UEInformationRequest (terminal device information request) message to the terminal device B in a connected state whose security information is successfully activated. The UEInformationRequest message contains the information type that the base station A needs the terminal device B to report. When the value corresponding to each parameter field is "true", it means that the base station A needs the terminal device B to report the information corresponding to the parameter field. For example, connEstFailReportReq (connection failure report request) indicates whether the terminal device B needs to report the connection failure related information; logMeasReportReq (logged measurement report request) indicates whether the terminal device B needs to report logged measurement related information; mobilityHistoryReportReq (mobility history report request) indicates whether the terminal device B needs to report mobility history information; ra-ReportReq (random access report request) indicates whether the terminal device B needs to report information related to the random access procedure; rlf-ReportReq (request for radio link failure report) indicates whether the terminal device B needs to report information about radio link failure.

The terminal device B feeds back the recorded information to the base station A via a UEInformationResponse (terminal device information response) message in response to the UEInformationRequest initiated by the base station A.

The terminal device B may record each random access attempt information in perRAInfoList (each random access information list) in temporal order for each random access attempt. The recorded information includes: the selected SSB (Synchronization Signal Block)/CSI-RS (Channel Status Indicator Reference Signal) index, downlink beam quality corresponding to the selected SSB/CSI-RS, and contention detection. The downlink beam quality indicates through a Boolean value whether the measurement result corresponding to the selected SSB/CSI-RS is higher than a threshold configured by the network side. The contention detection indicates through a Boolean value whether other user's CRID (Contention Resolution Identity) is detected in received Msg4 (the fourth message).

The two-step random access (<NUM>-step Random Access Channel) procedure is a new feature introduced by NR (new radio) Rel-<NUM>, which aims to reduce delay and signaling overhead in the four-step random access (<NUM>-step Random Access Channel) procedure.

In the two-step random access procedure, MsgA (message A) contains the preamble transmitted on PRACH (Physical Random Access Channel) and the load information (Msg3, the third message) transmitted on the PUSCH (Physical Uplink Shared Channel). After the MsgA is transmitted, the terminal device B monitors the response from the base station A in a configured window. If the terminal device B receives an indication of successful contention resolution sent by the base station A, the terminal device B ends the random access procedure; if a fallback indication is received in MsgB (message B), terminal device B performs Msg3 transmission and monitors the contention resolution result. If the contention resolution fails after Msg3 transmission, the terminal device B continues to try transmission of MsgA. In addition, the base station A can configure the maximum number 'N' of two-step random access attempts for the terminal device B. When terminal device B has tried 'N' two-step random access and still fails to access, the terminal device B can switch to the four-step random access procedure to continue access attempt.

After MsgA is sent, there may be the following situations for the reception on the terminal device B side:.

How to obtain relevant parameters for the two-step random access procedure will be described in the following example embodiments of the present disclosure, so as to ensure that the parameter configuration of the two-step random access procedure can be adaptively optimized according to the relevant parameters for the two-step random access procedure.

<FIG> is a flowchart of a method for reporting a random access procedure according to an example embodiment <NUM> of the present disclosure. The method includes the following steps:
In step <NUM>, a terminal device receives a first message sent by a network device.

The first message is used to indicate the terminal device to report a random access parameter list to the network device, and the random access parameter list includes a two-step random access parameter list or includes the two-step random access parameter list and a four-step random access parameter list.

In step <NUM>, the terminal device reports the random access parameter list to the network device according to the first message.

The random access parameter list includes a random access procedure parameter for at least one successfully completed random access procedure, and the random access procedure parameter includes:
a random access resource parameter, and a collision detection and fallback indication parameter. A random access type switching parameter is optionally included.

Regarding the signaling structure of the first message, a request parameter and a response parameter may be introduced separately for different random access types. Specifically, the following options which are not according to the claimed invention are included:.

<FIG> is an interaction diagram of a method for reporting a random access procedure according to an example embodiment <NUM> of the present disclosure. Optionally, the first message includes: a first request parameter and/or a second request parameter.

In step <NUM>, the network device indicates, via the first request parameter, the terminal device to report the four-step random access parameter list.

In step <NUM>, the network device indicates, via the second request parameter, the terminal device to report the two-step random access parameter list. Correspondingly, the terminal device sends the first response parameter and the second response parameter.

Step <NUM> may include the following steps:.

The first message may be a UEInformationRequest message, and the first message may include the first request parameter and the second request parameter. The first request parameter may be ra-ReportReq. When the first request parameter is configured as true, it means that the network device indicates the terminal device to report the four-step random access procedure. At this time, if there is a four-step random access parameter list that can be reported at the terminal device side, the terminal device reports the four-step random access parameter list to the network device via a first response parameter in UEInformationResponse which is set correspondingly to the first request parameter; otherwise, the terminal device does not respond. When the second request parameter is configured to be true, it means that the network device indicates the terminal device to report the two-step random access procedure. At this time, if there is a two-step random access parameter list that can be reported at the terminal device side, the terminal device reports the reportable two-step random access parameter list to the network device via a second response parameter in UEInformationResponse which is set correspondingly to the second request parameter; otherwise, the terminal device does not respond.

<FIG> is an interaction diagram of a method for reporting a random access procedure according to an example embodiment <NUM> of the present disclosure. Optionally, the first message includes a request parameter, and the request parameter includes a first sub-request parameter and a second sub-request parameter.

In step <NUM>, the network device indicates, via the first sub-request parameter, the terminal device to report the four-step random access parameter list.

In step <NUM>, the network device indicates, via the second sub-request parameter, the terminal device to report the two-step random access parameter list. Correspondingly, the terminal device sends a response parameter, and the response parameter includes a first sub-response parameter and a second sub-response parameter.

The request parameter includes the first sub-request parameter and the second sub-request parameter. A response parameter is set corresponding to the request parameter and the response parameter is used for the terminal device to report the four-step random access procedure and the two-step random access procedure. The response parameter includes the first sub-response parameter and the second sub-response parameter. When the first sub-request parameter is set to be true, if there is a reportable four-step random access parameter list at the terminal device side, the four-step random access parameter list is reported to the network device via the first sub-response parameter of the response parameter in UEInformationResponse; otherwise, the terminal device does not respond. When the second sub-request parameter is set to be true, if there is a reportable two-step random access parameter list at the terminal device side, the two-step random access parameter list is reported to the network device via the second sub-response parameter of the response parameters in the UEInformationResponse; otherwise, the terminal device does not respond.

The above Method <NUM> and Method <NUM> are only used as examples to illustrate how to optimize the signaling structure, and the implementation may be sending the random access parameter lists separately for different random access types. However, the above examples are not intended to limit the specific implementations of the present disclosure. In example implementations, the network device may initiate a report request to the terminal device in a targeted manner according to optimization requirements.

Regarding the signaling structure of the first message, it may also be possible to request the terminal device to report all the random access parameter lists that can be reported without distinguishing the types. Specifically, the following optional methods which are not according to the claimed invention may be included:.

<FIG> is an interaction diagram of a method for reporting a random access procedure according to an example embodiment <NUM> of the present disclosure. Optionally, the first message includes a request parameter.

In step <NUM>, the network device indicates via the request parameter the terminal device to report the random access parameter list, and the random access parameter list includes a two-step random access parameter list and/or a four-step random access parameter list.

Step <NUM> may include the following steps:
In step <NUM>, the terminal device reports via a response parameter the random access parameter list according to the request parameter.

The first message may include the request parameter, and the response parameter is set corresponding to the request parameter. The response parameter is used for the terminal device to report the four-step random access procedure and the two-step random access procedure. When the request parameter is set to be true, if there is a four-step random access parameter list and a two-step random access parameter list that can be reported at the terminal device side, the reportable random access parameter lists are reported to the network device via the response parameter in UEInformationResponse which is set corresponding to the request parameter; otherwise, the terminal device does not respond.

In step <NUM>, the network device indicates, via the request parameter, the terminal device to report the random access parameter list. The random access parameter list includes a two-step random access parameter list and/or a four-step random access parameter list. Correspondingly, the terminal device sends a response parameter, and the response parameter includes a first sub-response parameter and a second sub-response parameter.

The first sub-response parameter and the second sub-response parameter of the response parameter are used for the terminal device to report the four-step random access parameter list and the two-step random access parameter list, respectively. When the request parameter is set to be true, if there is a reportable four-step random access parameter list at the terminal device side, the four-step random access parameter list is reported to the network device via the first sub-response parameter of the response parameter in the UEInformationResponse; otherwise, the terminal device does not respond. If there is a two-step random access parameter list that can be reported at the terminal device side, the two-step random access parameter list is reported to the network device via the second sub-response parameter of the response parameter in UEInformationResponse; otherwise, the terminal device does not respond.

In step <NUM>, the network device indicates, via the request parameter, the terminal device to report the random access parameter list. The random access parameter list includes a two-step random access parameter list and/or a four-step random access parameter list. Correspondingly, the terminal device sends a first response parameter and a second response parameter.

When the request parameter configuration is true, if there is a reportable four-step random access parameter list at the terminal device side, the four-step random access parameter list is reported to the network device via the first response parameter in the UEInformationResponse; otherwise, the terminal device does not respond. If there is a reportable two-step random access parameter list at the terminal device side, the reportable two-step random access parameter list is reported to the network device via the second response parameter in the UEInformationResponse; otherwise, the terminal device does not respond.

In the above-mentioned example implementations of requesting the terminal device to report all the random access parameter lists that can be reported without distinguishing the types, after receiving the request from the network device side, the terminal device reports all the random access parameter lists, so the network device does not need to obtain in advance the type of random access parameter list at the terminal device side.

When the first message requests the terminal device to report all the random access parameter lists that can be reported without distinguishing types, as shown in the above embodiments, the terminal device reports the two-step random access parameter list and the four-step random access parameter list respectively, or report the two-step random access parameter list and the four-step random access parameter list together, depending on the storage method of the two-step random access parameter list and the four-step random access parameter list. For example, when the two-step random access parameter list and the four-step random access parameter list are stored in different list entries, they are respectively reported by different response parameters. If the two-step random access parameter list and the four-step random access parameter list are stored in the same list entry, they are reported together with a response parameter. The storage methods of the two-step random access parameter list and the four-step random access parameter list will be described in detail in the following contents.

Optionally, the random access resource parameters include:.

According to the claimed invention, the random access resource parameters include: a frequency domain starting point of a physical uplink shared channel resource; and.

Optionally, the random access resource parameters include a guard period for a physical uplink shared channel resource unit in a frequency domain.

The two-step random access includes a PRACH resource for preamble transmission and a PUSCH resource for payload transmission. In order to optimize the resource configuration of the two-step random access on each BWP (Bandwidth Part), the network device needs the corresponding physical resource configuration during the access procedure of the terminal device, so as to make corresponding adjustments according to the access performance. Therefore, the terminal device needs to report the random access resource parameter used in two-step random access procedure each time.

<FIG> is a schematic diagram of random access resource parameters. As shown in <FIG>, the random access resource parameters may include the following parameters:.

According to the claimed invention, the random access resource parameters include:.

The msgA-RO-FrequencyStart, msgA-RO-FDM and msgA-SubcarrierSpacing are used to reflect the frequency domain information of PRACH resources. The three can be used to jointly determine the starting position, number and occupied bandwidth of PRACH on BWP. The frequencyStartMsgA-PUSCH, nrofMsgA-PO-FDM, nrofPRBs-PerMsgA, and guardPeriodMsgA-PUSCH are used to reflect the frequency domain information of PUSCH resources, and the four can be used to jointly determine the starting position, number and occupied bandwidth of PUSCH resources on the BWP.

Optionally, the contention detection and fallback indication parameter include:.

For each two-step random access attempt, after MsgA is sent, there may be following situations for the reception at the terminal device side:.

The contention detection indication and the fallback indication are configured. The contention detection indication is used to indicate whether the terminal device can detect that the contention resolution fails after the MsgA and/or Msg3 are sent. The fallback indication is used to indicate whether the terminal device has received the fallbackRAR sent by the network device.

For situations <NUM> and <NUM> above: the contention detection indication is set to "false (no)' and the fallback indication is set to 'false';.

Optionally, the contention detection indication includes:.

It is possible that only the contention detection indication is configured. The contention detection indication may include the first detection indication and the second detection indication. The first detection indication is used to indicate whether a contention resolution failure is detected in the MsgB in the two-step random access procedure. The second contention detection indication is used to indicate whether a contention resolution failure is detected in Msg4 when a fallback occurs, and the second contention detection indication can be used to implicitly indicate that a fallback procedure has occurred to the terminal device.

For the above situations <NUM> and <NUM>: the first contention detection indication is set to 'false';.

In the two-step random access procedure, when the network device only detects the MsgA preamble but fails to detect/decode the MsgA payload, the terminal device will receive the fallbackRAR and transmit Msg3 according to the indication in the fallbackRAR. The reasons why the payload is not successfully detected/decoded may be as follows:.

The terminal device feeds back the fallback situation in the two-step random access procedure to the network device, and the network device determines the reason for the terminal device fallback in combination with the resource configuration, the number of attempts and so on, and then optimizes the PRACH and PUSCH resource configuration and adjusts power control parameters in combination with PUSCH resource information.

In an example implementation, the network device can optimize the number of PUSCH resource configurations through nrofMsgA-PO-FDM and a fallback indication. For example, in a certain PUSCH configuration, nrofMsgA-PO-FDM is set to <NUM>, and a total of N users initiate random access in this configuration and the access succeeds finally. According to the random access parameters reported by N terminal devices, the network device finds that <NUM>% of the terminal devices have undergone a fallback procedure before the access is successful, and the number of PUSCH resources multiplexed in the frequency domain is small. Based on this, the network device can determine that the reason why the terminal device has a high fallback probability may be due to less PUSCH resource configuration which results in multiple preambles associated with one PUSCH resource unit. When multiple terminal devices send MsgA payloads on the same time-frequency resource, there will be interference between each other, affecting the successful detection/decoding of PUSCH by the network device, and triggering the fallback procedure. Therefore, the network device can adjust the nrofMsgA-PO-FDM, such as increasing it to <NUM>, to reduce the probability of fallback of the terminal device.

In an example implementation, the network device may further optimize the grouping threshold through frequencyStartMsgA-PUSCH and nrofPRBs-PerMsgA and the fallback indication. For example, the network device configures different preamble groups for the terminal device. Preamble groupA corresponds to PUSCH configuration #<NUM>, the frequency starting point is frequencyStartMsgA-PUSCH#<NUM>, and nrofPRBs-PerMsgA is <NUM>; preamble groupB corresponds to PUSCH configuration #<NUM>, the frequency starting point is frequencyStartMsgA-PUSCH#<NUM>, and nrofPRBs-PerMsgA is <NUM>. The data volume threshold ra-MsgASizeGroupA used to select the preamble group A is <NUM> bits.

A total of N terminal devices select groupA or groupB and the corresponding PUSCH resources to initiate two-step random access according to the relationship between the size of the MsgA paylaod to be transmitted and the data volume threshold, and the access is finally successful. According to the random access parameters reported by N terminal devices, the network device finds that <NUM>% of the terminal devices that initiate random access on the PUSCH resources corresponding to groupA are notified by the network to fall back, while only <NUM>% of terminal devices that initiate random access on the PUSCH resources corresponding to groupB are notified by the network to fall back. Based on this, the network device determines that the number of terminal devices belonging to group A is too large, and then adjusts the data volume threshold ra-MsgASizeGroupA used for preamble group A selection to be smaller, for example, to <NUM> bits to balance the user data under the two preamble groups and reduce the occurrence probability of fallback.

In an example implementation, the network device may further optimize the frequency domain interval of PUSCH resources through guardPeriodMsgA-PUSCH and the fallback indication. For example, in a certain PUSCH configuration, guardPeriodMsgA-PUSCH is <NUM>, and a total of N users initiate random access in this configuration and the access succeeds finally. According to the random access parameters reported by N terminal devices, the network device found that <NUM>% of the terminal devices had a fallback procedure before the access was successful, and guardPeriodMsgA-PUSCH was set to <NUM>. Based on this, the network device can determine that the reason why the terminal devices have a high fallback probability may be due to the interference between adjacent PUSCH resources in the frequency domain which affects the successful detection/decoding of the PUSCH by the network and triggers the fallback procedure. Therefore, the network device can reduce the occurrence probability of fallback of the terminal devices by setting guardPeriodMsgA-PUSCH.

Optionally, in an example embodiment of the present disclosure, when random access type switching occurs in the random access procedure of the terminal device, the random access parameter list stored by the terminal device and whether there is a random access type switching parameter may include the following situations:.

<FIG> is a schematic diagram of a random access parameter list. As shown in <FIG>, optionally, when there exists random access type switching, and different random access procedure parameters are respectively stored in the list entries of different random access parameter lists, for example, the two-step random access procedure parameters are stored as the first list entry in the two-step random access parameter list and the four-step random access procedure parameters are stored as the second list entry in the four-step random access parameter list, the random access switching type parameters include:.

The random access type switching parameter includes: the switching indication for the two-step random access parameter list and the switching indication for the four-step random access parameter list.

The switching indication can be set as the indexes of the first list entry and the second list entry. The first list entry of the two-step random access parameter list stores the two-step random access procedure parameters. When access type switching occurs in the two-step random access, the four-step random access procedure parameters after switching are stored in the second list entry of the four-step random access parameter list, and the switching indication of the two-step random access parameter list in the first list entry is set to the index of the second list entry; the switching indication of the four-step random access parameter list in the second list entry is set as the index of the first list entry. Therefore, the list entries before and after the switching are associated, which can assist the network to understand the complete random access procedure. The two-step random access procedure parameters may include resource information, type information, beam information, contention resolution information of two-step random access, and four-step random access procedure parameters may include resource information, type information, beam information, contention resolution information of four-step random access.

In an example implementation, the two-step random access procedure parameters and the four-step random access procedure parameters are stored separately, and thus the uniformity of the types in each list can be maintained.

<FIG> is a schematic diagram of a random access parameter list. As shown in <FIG>, optionally, when there exists random access type switching, different random access procedure parameters are stored as the same list entry in the same list entry of the two-step random access parameter list or the four-step random access parameter. For example, both the two-step random access procedure parameters and the four-step random access procedure parameters are stored in the random access parameter list as the third list entry.

When there exists random access type switching, both the successfully completed two-step random access procedure parameters and four-step random access procedure parameters are stored in the random access parameter list as the third list entry, including the two-step random access parameter list or the four-step random access parameter list. The two-step random access procedure parameters and four-step random access procedure parameters are stored in temporal order, that is, the third list entry includes both the two-step random access procedure parameters and the four-step random access procedure parameters.

In this example embodiment, the two-step random access procedure parameters and the four-step random access procedure parameters are stored as a single access procedure in the random access parameter list as a whole, and type information needs to be introduced to distinguish two different access types in the same list entry.

Optionally, the first list entry and/or the third list entry includes: reference signal received power for downlink path loss reference.

The reference signal received power for downlink path loss reference is used to indicate a threshold for optimizing random access type selection.

The reasons for the terminal to switch the access type may be as follows:.

The terminal device records and reports the type switching that occurs during the two-step random access procedure and the specific access information under the corresponding type, which can assist the network device to infer the cause of access problem in the two-step random access in the terminal device, and then optimize the resource configuration, the threshold for selecting the access type and the power control parameter for the two-step random access.

In an example implementation, the network optimizes the access type selection threshold by using RSRP (Reference Signal Receiving Power) for downlink pathloss reference and a switching indication. For example: assuming that the threshold for random access type selection is -60dBm, if the RSRP used by the terminal device for the downlink pathloss reference is greater than -60dBm, two-step random access is selected, and otherwise, four-step random access is selected. According to the random access parameter lists reported by the terminal devices, the network device finds that half of the users who have selected two-step random access have switched the random access type, and the RSRP for downlink pathloss reference reported by the users who have switched access type is relatively low. Based on this, the network device determines that the users with poor channel status select two-step random access because the access type selection threshold is set low, and then the network device can increase the threshold for random access type selection, for example, to -40dBm, so as to ensure that users with better channel status choose two-step random access to reduce the occurrence probability of switching.

In the embodiment <NUM>, the first message sent by the network device is received. The first message is used to indicate the terminal device to report the random access parameter list to the network device. The random access parameter list includes a two-step random access parameter list and/or a four-step random access parameter list. The random access parameter list is reported to the network device according to the first message. Therefore, the terminal device can report the random access parameter list to the network device, ensuring that the network device can obtain the two-step random access parameter list, and further, according to the relevant parameters for the two-step random access procedure, the parameter configuration for the two-step random access procedure can be adaptively optimized, thereby solving the technical problem that the optimization for parameter configuration of the two-step random access procedure is poor.

<FIG> is a block diagram of a device for reporting a random access procedure according to an example embodiment <NUM> of the present disclosure. As shown in <FIG>, the device is a terminal device. The device may include but not limited to: a receiving module <NUM> and a sending module <NUM>.

The receiving module <NUM> is configured to receive a first message sent by a network device, wherein the first message is used to indicate the terminal device to report a random access parameter list to the network device, and the random access parameter list includes a two-step random access parameter list or includes the two-step random access parameter list and a four-step random access parameter list.

The sending module <NUM> is configured to report the random access parameter list to the network device according to the first message.

According to the claimed invention, the random access parameter list includes a random access procedure parameter for at least one successfully completed random access procedure, and the random access procedure parameter includes:
a random access resource parameter, and a collision detection and fallback indication parameter. A random access type switching parameter is optionally included.

According to some not claimed embodiments, the first message includes: a first request parameter and/or a second request parameter;.

According to some not claimed embodiments, the first message includes a request parameter, and the request parameter is used to indicate the terminal device to report the two-step random access parameter list and/or the four-step random access parameter list.

According to some embodiments, the sending module <NUM> is further configured to:
according to the request parameter, report the random access parameter list via a response parameter.

According to some not claimed embodiments, the sending module <NUM> is further configured to:.

According to some not claimed embodiments, the request parameter includes a first sub-request parameter and a second sub-request parameter, the first sub-request parameter is used to indicate the terminal device to report the four-step random access parameter list, and the second sub-request parameter is used to indicate the terminal device to report the two-step random access parameter list;
wherein the sending module <NUM> is further configured to:.

According to some embodiments, the random access resource parameter includes:.

According to the claimed invention, the random access parameters include:.

Optionally, the random access parameters include a guard period for a physical uplink shared channel resource unit in a frequency domain.

According to some embodiments, the contention detection and fallback indication parameter include:.

According to some embodiments, the contention detection indication includes:.

According to some embodiments, when random access type switching exists, a two-step random access procedure parameter is stored as a first list entry in the two-step random access parameter list, and a four -step random access procedure parameter is stored as a second list entry in the four-step random access parameter list, the random access type switching parameter includes:.

According to some embodiments, when random access type switching exists, both a two-step random access procedure parameter and a four-step random access procedure parameter are stored in the random access parameter list as a third list entry.

According to some embodiments, the first list entry and/or the third list entry includes: a reference signal received power for a downlink pathloss reference.

For the implementations of the functions and roles of each module in the device embodiments and other parts that are not described or defined in detail, please refer to the description in example embodiment <NUM> above for details, and repeated descriptions will be omitted here.

<FIG> is a block diagram of a device for reporting a random access procedure according to an example embodiment <NUM> of the present disclosure. As shown in <FIG>, the device may be a network device. The device may include but not limited to a sending module <NUM> and a receiving module <NUM>.

The sending module <NUM> is configured to send a first message to a terminal device, wherein the first message is used to indicate the terminal device to report a random access parameter list to the network device, and the random access parameter list includes a two-step random access parameter list or includes the two-step random access parameter list and a four-step random access parameter list.

The receiving module <NUM> is configured to receive the random access parameter list which is reported by the terminal device according to the first message.

According to some embodiments, the receiving module <NUM> is further configured to:
receive the random access parameter list which is reported by the terminal device via a response parameter according to the request parameter.

According to some not claimed embodiments, the receiving module <NUM> is further configured to:.

According to some not claimed embodiments, the request parameter includes a first sub-request parameter and a second sub-request parameter, the first sub-request parameter is used to indicate the terminal device to report the four-step random access parameter list, and the second sub-request parameter is used to indicate the terminal device to report the two-step random access parameter list;
wherein the receiving module <NUM> is further configured to:.

For the implementations of the functions and roles of each module in the device embodiments and other parts that are not described or defined in detail, please refer to the description in example embodiment <NUM> and embodiment <NUM> above for details, and repeated descriptions will be omitted here.

<FIG> is a schematic diagram of the hardware structure of a device for reporting a random access procedure according to an example embodiment <NUM> of the present disclosure. As shown in <FIG>, the device includes: a processor <NUM> and a memory <NUM>, and the above components of the device are connected to each other through a bus system for communication.

The memory <NUM> stores a program that can be run on the processor <NUM>. When the processor <NUM> executes the program, it implements some or all of the steps of the method for reporting the random access procedure in the embodiment <NUM> of the above method.

The processor <NUM> may be an independent component, or may be a collective term for multiple processing components. For example, it may be a CPU, an ASIC, or one or more integrated circuits configured to implement the above method embodiments, such as at least one microprocessor DSP, or at least one programmable gate FPGA, etc..

The steps of the methods or algorithms described in the example embodiments of the present application may be implemented in a hardware, or may be implemented in a manner of a processor executing software instructions. Software instructions can be composed of corresponding software modules, and software modules can be stored in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), registers, hard disks, removable hard disks, read-only optical disks (CD-ROMs), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium. According to some embodiments, the storage medium can also be an integral part of the processor. The processor and storage medium may reside in an ASIC. Additionally, the ASIC may reside in access network device, a target network device or a core network device. According to some embodiments, the processor and the storage medium may also exist in the access network device, the target network device or the core network device as discrete components.

Those skilled in the art should realize that, in one or more of the above examples, the functions described in the example embodiments of the present disclosure may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, the functions can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the example embodiments of the present disclosure are produced. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in the computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website, computer, server, or data center to another website, computer, server, or data center in a wired manner (e.g., coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or in a wireless manner (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available medium. The available medium may be magnetic medium (e.g., floppy disks, hard disks, magnetic tapes), optical medium (e.g., Digital Video Disc (DVD)), or semiconductor medium (e.g., Solid State Disk (SSD)), and so on.

The purposes, technical solutions and beneficial effects of the example embodiments of the present disclosure are described above in detail using the example implementations. It should be understood that the above descriptions are only example implementations of the present disclosure, and are not intended to limit the protection scope of the embodiments of the present disclosure.

Claim 1:
A method for reporting a random access procedure, applied in a terminal device, wherein the method comprises:
receiving (<NUM>) a first message sent by a network device, wherein the first message is used to indicate the terminal device to report a random access parameter list to the network device, and the random access parameter list comprises a two-step random access parameter list, or comprises the two-step random access parameter list and a four-step random access parameter list; and
reporting (<NUM>) the random access parameter list to the network device according to the first message;
wherein the random access parameter list comprises a random access procedure parameter for at least one successfully completed random access procedure, and
characterized in that the random access procedure parameter comprises:
random access resource parameters and a collision detection and fallback indication parameter;
wherein the random access resource parameters comprise:
a frequency domain starting point of a physical uplink shared channel resource for two-step random access; and
the number of multiplexed physical uplink shared channel resources for two-step random access in a frequency domain; and
the number of physical resource blocks occupied by each physical uplink shared channel resource unit for two-step random access in a frequency domain.