Patent Description:
In the 5th Generation (<NUM>) New Radio (NR) mobile networks, before a user equipment (UE) can send data to a base station (BS), the UE is required to obtain uplink synchronization and downlink synchronization with the BS. The uplink timing synchronization can be achieved by performing a random access procedure. To meet the demand for faster and efficient communications, the random access procedure is to be enhanced.

3GPP R2-<NUM>, <CIT>, and 3GPP R2-<NUM> form part of the prior art.

The example embodiments disclosed herein are directed to solving the issues relating to one or more of the existing problems, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of the claims.

The following paragraphs describe embodiments, aspects and examples that are not specifically claimed but may be useful for understanding the invention.

" Such an example network <NUM> includes a base station <NUM> (hereinafter "BS <NUM>") and a user equipment device <NUM> (hereinafter "UE <NUM>") that can communicate with each other via a communication link <NUM> (e.g., a wireless communication channel), and a cluster of cells <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> overlaying a geographical area <NUM>.

In the present disclosure, the BS <NUM> and UE <NUM> are respectively described herein as non-limiting examples of "communication node" (or "wireless communication node") and "communication device" (or "wireless communication device") generally, which can practice the methods disclosed herein. Such communication nodes and devices may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.

<FIG> illustrates a block diagram of an example wireless communication system <NUM> for transmitting and receiving wireless communication signals, e.g., OFDM/OFDMA signals, in accordance with some embodiments of the present solution. The system <NUM> may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, system <NUM> can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment <NUM> of <FIG>, as described above.

The operations of the two transceiver modules <NUM> and <NUM> can be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna <NUM> for reception of transmissions over the wireless transmission link <NUM> at the same time that the downlink transmitter is coupled to the downlink antenna <NUM>.

In accordance with various embodiments, the BS <NUM> may be a next generation nodeB (gNodeB or gNB), an evolved node B (eNB), a serving eNB, a target eNB, a femto station, a pico station, or a Transmission Reception Point (TRP), for example.

Furthermore, the steps of a process, method, or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules <NUM> and <NUM>, respectively, or in any practical combination thereof.

<FIG> illustrates an example <NUM>-step random access procedure <NUM>, in accordance with some embodiments of the present disclosure. Referring to <FIG>, the <NUM>-step random access procedure (RACH) <NUM> is performed between a BS <NUM> (e.g., a gNB) and a UE <NUM>. BS <NUM> and UE <NUM> may be same or similar to BS <NUM> and UE <NUM> in <FIG>, respectively. In some embodiments, at Step <NUM> (<NUM>), the UE <NUM> transmits a random access channel (RACH) preamble or physical random access channel (PRACH) preamble in message <NUM> (Msg1) through an uplink random access channel (RACH) to the BS <NUM>. At Step <NUM> (<NUM>), once the preamble is received successfully by the BS <NUM>, the BS <NUM> sends a message <NUM> (Msg2) back to the UE <NUM>, in which a medium access control (MAC) random access response (RAR) can be included as a response to the preamble. At Step <NUM> (<NUM>), once the MAC RAR with a corresponding random access preamble (RAP) identifier (ID) is received, the UE <NUM> transmits a message <NUM> (Msg3) to the BS <NUM> with the grant carried in the MAC RAR. At Step <NUM> (<NUM>), once the Msg3 is received, the BS <NUM> sends a message <NUM> (Msg4) back to the UE <NUM>, in which a contention resolution ID can be included for the purpose of contention resolution. In some embodiments, to reduce latency and accelerate the initial access procedure, a <NUM>-step random access procedure can be used, as described in relation to <FIG> below.

The following is related to a claimed embodiment.

<FIG> illustrates an example <NUM>-step random access procedure <NUM>, in accordance with some embodiments of the present disclosure. In some embodiments, a <NUM>-step random access procedure (RACH) <NUM> can complete the four steps in <FIG> in two messages or two steps. In some embodiments, at least some content of the Msg1 and Msg3 in the <NUM>-step RACH are included in Msg1 of the <NUM>-step RACH, and at least some content of the Msg2 and Msg4 (RAR and contention resolution) in the <NUM>-step RACH are included in Msg2 of the <NUM>-step RACH. Referring to <FIG>, the <NUM>-step random access procedure <NUM> is performed between a BS <NUM> (e.g., a gNB) and a UE <NUM>. BS <NUM> and UE <NUM> may be same or similar to BS <NUM> and UE <NUM> in <FIG>, respectively. In some embodiments, at Step <NUM> (<NUM>), the UE <NUM> transmits Msg <NUM> that includes a preamble and a data payload to a BS <NUM> for access to the BS <NUM>. In some embodiments, the payload may be optional. In some embodiments, the preamble may be optional. At step <NUM> (<NUM>), the BS <NUM> transmits Msg2 as a response to the Msg1 to the UE <NUM>. Details of the <NUM>-step random access procedure are described herein below.

In some embodiments, when both the <NUM>-step RA configuration and the <NUM>-step RA configuration are broadcasted in system information (e.g., system information block type <NUM> (SIB1)), a RA type selection is performed, for example, between a <NUM>-step random access procedure (<NUM>-step RACH) and a <NUM>-step random access procedure (<NUM>-step RACH). For example, the RA type selection can be performed for Step <NUM> of the <NUM>-step random access procedure, in some embodiments.

In some embodiments, the following alternatives or options can be considered or implemented in RA type selection between <NUM>-step RACH and <NUM>-step RACH. These alternatives or options can be performed separately or in combination. In brief overview, a "RACH type selection factor" based solution can be considered or implemented in a first alternative (ALT <NUM>), a "RACH type selection timer" based solution can be considered or implemented in a second alternative (ALT <NUM>), and a backoff indicator based solution can be considered or implemented in a third alternative (ALT <NUM>), as described in more detail herein below.

In some embodiments, with (or upon, responsive to, after, when) the RACH type selection factor being configured (described in more detail below), a UE (e.g., UE <NUM>) can draw, obtain, or determine a random number or a randomly generated number "rand", for example, in the range of <NUM> ≤ rand < <NUM>. In other embodiments, the "rand" can be in other ranges. The "rand" can be randomly generated by the UE or another device, in some embodiments. In some embodiments, the UE can compare the "rand" with a value indicated by the RACH type selection factor. If the "rand" is lower (or lower+equal, or larger, or larger+equal) than the value indicated by the RACH type selection factor, the UE is allowed to select the <NUM>-step RACH. Otherwise, the UE selects the <NUM>-step RACH.

In some embodiments, with (or upon, responsive to, after, when) the RACH type selection factor being configured, the UE can draw, obtain, or determine a random number or a randomly generated number "rand", for example, in the range of <NUM> ≤ rand < <NUM>. In other embodiments, the "rand" can be in other ranges. The "rand" can be randomly generated by the UE or another device, in some embodiments. In some embodiments, the UE can compare the "rand" with a value indicated by the RACH type selection factor. If the "rand" is lower (or lower+equal, or larger, or larger+equal) than the value indicated by the RACH type selection factor, the UE shall select the <NUM>-step RACH. Otherwise, the UE shall select the <NUM>-step RACH.

In some embodiments, besides the factor based solution, some other criteria may also be considered in the RA type selection (e.g., RSRP threshold, and <NUM>-step RACH can only be selected in case the RSRP measured is larger than the RSRP threshold). Therefore, the factor based RA type selection can be used in the following two ways: Alt1: The factor based solution is used to determine whether the <NUM>-step RACH is allowed; and Alt2: The factor based solution is used to determine whether the <NUM>-step RACH shall be selected. In Alt1, the factor based solution can be used together with other criteria, and <NUM>-step RACH can only be selected in case the selection of <NUM>-step RACH is allowed by all the criteria. In Alt <NUM>, the factor based solution shall be used in case the <NUM>-step RACH is allowed, which can be determined by other criteria.

In some embodiments, the following alternatives or options can be considered or implemented for the configuration of the RACH type selection factor.

In alternative <NUM> of the configuration of the RACH type selection factor, the RACH type selection factor can be configured per access category. With (based on, using) the per access category configured "RACH type selection factor," the UE can determine the access category first and then use the corresponding "RACH type selection factor" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection factor, the RACH type selection factor can be configured per unified access control (UAC)-BarringInfoSet. With (based on, using) the per UAC-BarringInfoSet configured "RACH type selection factor," the UE can determine the UAC-BarringInfoSet first and then use the corresponding "RACH type selection factor" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection factor, the RACH type selection factor can be configured per access identity. With (based on, using) the per access identity configured "RACH type selection factor," the UE can determine the access identity first and then use the corresponding "RACH type selection factor" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection factor, the RACH type selection factor can be configured per public land mobile network (PLMN). With (based on, using) the per PLMN configured "RACH type selection factor," the UE can determine the PLMN first and then use the corresponding "RACH type selection factor" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection factor, the RACH type selection factor can be configured for different triggers or trigger events of the RACH procedure. In some embodiments, the following triggers or trigger events of the RACH procedure can be considered or implemented: (a) Initial access from radio resource control (RRC)_IDLE; (b) RRC connection re-establishment procedure; (c) Handover; (d) Downlink (DL) or Uplink (UL) data arrival during RRC_CONNECTED when the UL synchronization status is "non-synchronized"; (e) UL data arrival during RRC_CONNECTED when there are no physical uplink control channel (PUCCH) resources for Scheduling Request (SR) available; (f) SR failure; (g) Request by RRC upon synchronous reconfiguration; (h) Transition from RRC_INACTIVE; (i) Establishing (or to establish) time alignment at secondary cell (SCell) addition; (j) Request for other system information (which may be sometimes referred to as remaining and other system information in the NR mobile networks) or system information message (SI); (k) Beam failure recovery. In some embodiments, with (based on, using) the trigger-specific configured "RACH type selection factor," the UE can determine the trigger first and then use the corresponding "RACH type selection factor" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection factor, the RACH type selection factor can be configured for services with different Quality of Service (QoS) requirements, or for different logical channel, or for different logical channel group. For each type of service with different QoS requirement, logical channel, or logical channel group, a "RACH type selection factor" can be configured. Then, according to (based on, using) the QoS requirement, logical channel, or logical channel group from which there is data for transmission, the UE uses the corresponding "RACH type selection factor" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection factor, the RACH type selection factor can be configured per cell. With (based on, using) the per cell configured "RACH type selection factor," the UE can determine the cell first and then use the corresponding "RACH type selection factor" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection factor, the RACH type selection factor can be configured per bandwidth part (BWP). With (based on, using) the per BWP configured "RACH type selection factor," the UE can determine the BWP first and then use the corresponding "RACH type selection factor" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In some embodiments, a combination of the above alternatives for configuring the RACH type selection factor can be considered or implemented. For example, for each cell or BWP, different RACH type selection factor(s) can be configured for different access category, access identifier, UAC-BarringInfoSet, trigger, or service type, etc..

In some embodiments, with respect to the above alternatives for configuring the RACH type selection factor, in the event that the "RACH type selection factor" is missing for the corresponding access category/access identifier/UAC-BarringInfoSet/trigger/cell/BWP/QoS requirement/logical channel/logical channel group, the following additional alternatives may be considered or used: (a) additional alternative <NUM>, where the UE uses the <NUM>-step random access procedure; (b) additional alternative <NUM>, where a default value (e.g., configured by the network or BS, or fixed/specified in the specification) is used for the "RACH type selection factor"; (c) additional alternative <NUM>, where the UE uses the <NUM>-step random access procedure.

<FIG> is a flow diagram illustrating an example process <NUM> for enhanced random access procedure using the RACH type selection factor, in accordance with some embodiments of the present disclosure. In some embodiments, the process <NUM> can be performed by a wireless communication device (e.g., UE <NUM>). At operation <NUM>, the wireless communication device receives information indicating a value from a wireless communication node (e.g., BS <NUM>). In some embodiments, the information can be broadcasted in system information, or by RRC signaling. In some embodiments, the value can correspond to or associated with a RACH type selection factor. In some embodiments, the value can be configured by the wireless communication node. For example, the value can be configured using the alternatives for configuring the RACH type selection factor, as described herein above.

In some embodiments, the value indicated by the information received at operation <NUM> can be configured based on an access category. In some embodiments, the value can be configured based on a UAC-BarringInfoSet. In some embodiments, the value can be configured based on an access identity. In some embodiments, the value can be configured based on a PLMN. In some embodiments, the value can be configured based on one or more triggers or trigger events of the <NUM>-step random access procedure or the <NUM>-step random access procedure to access to the wireless communication node. In some embodiments, the value can be configured based on a QoS requirement. In some embodiments, the plurality of values can respectively be configured based on a plurality of logical channels or logical channel groups. In some embodiments, the value can be configured based on a cell that the wireless communication device is in. In some embodiments, the value can be configured based on a BWP.

Referring again to <FIG>, at operation <NUM>, the wireless communication device can compare a randomly generated value with the value received from the wireless communication node to determine whether the randomly generated value satisfies the value. In some embodiments, the wireless communication device can generate a random number as the randomly generated value. In other embodiments, the randomly generated value can be generated by another device and transmitted to the wireless communication device. In some embodiments, the randomly generated value can be in the range of greater than or equal to <NUM>, and less than <NUM> (<NUM> ≤ randomly generated value < <NUM>). In other embodiments, the randomly generated value can be in other ranges.

In some embodiments, responsive to determining that the randomly generated value satisfies the value (e.g., the randomly generated value is less than, or less than or equal to, or greater than, or greater than or equal to the value) at operation <NUM>, the process <NUM> proceeds to operation <NUM>. Otherwise, the process <NUM> proceeds to operation <NUM>.

At operation <NUM>, the wireless communication device selects the <NUM>-step random access procedure to access to the wireless communication node. At operation <NUM>, the wireless communication device selects the <NUM>-step random access procedure to access to the wireless communication node. If the <NUM>-step random access procedure is selected at operation <NUM>, the process <NUM> may proceed to operation <NUM>. If the <NUM>-step random access procedure is selected at operation <NUM>, the process <NUM> may proceed to operation <NUM>.

At operation <NUM>, the wireless communication device transmits a first message to access to the wireless communication node. The content of the first message being transmitted at operation <NUM> can be based on the selection of the <NUM>-step random access procedure. In some embodiments, the content of the first message may include a random access preamble and a payload when (responsive to) the <NUM>-step random access procedure is selected. In some embodiments, the payload may be optional. In some embodiments, the preamble may be optional.

At operation <NUM>, the wireless communication device transmits a first message to access to the wireless communication node. The content of the first message being transmitted at operation <NUM> can be based on the selection of the <NUM>-step random access procedure. In some embodiments, the content of the first message may include a random access preamble when (responsive to) the <NUM>-step random access procedure is selected.

In some embodiments, a wireless communication node (e.g., BS <NUM>) can transmit, to a wireless communication device (e.g., UE <NUM>), information indicating a value. In some embodiments, the value can correspond to or associated with a RACH type selection factor. In some embodiments, the value can be configured by the wireless communication node. For example, the value can be configured using the alternatives for configuring the RACH type selection factor, as described herein above. In some embodiments, the wireless communication node can receive, from the wireless communication device, a first message to access to the wireless communication node. In some embodiments, the first message can include a random access preamble when the <NUM>-step random access procedure is selected (e.g., by the wireless communication device). In some embodiments, the first message can include a random access preamble and a payload when the <NUM>-step random access procedure is selected (e.g., by the wireless communication device). In some embodiments, the payload may be optional. In some embodiments, the preamble may be optional. In some embodiments, the wireless communication node can transmit a second message in response to the first message.

<FIG> is a flow diagram illustrating an example process <NUM> for enhanced random access procedure using the RACH type selection factor, in accordance with some embodiments of the present disclosure. In some embodiments, the process <NUM> can be performed by a wireless communication device (e.g., UE <NUM>). At operation <NUM>, the wireless communication device receives information indicating a plurality of values from a wireless communication node (e.g., BS <NUM>). In some embodiments, the information can be broadcasted in system information, or by RRC signaling. In some embodiments, the plurality of values respectively correspond to a plurality of parameters. In some embodiments, the plurality of parameters can be a plurality of access control parameters, such as a plurality of access categories, a plurality of UAC-BarringInfoSets, or a plurality of access identities. In some embodiments, the plurality of parameters can be a plurality of non-access control parameters, such as a plurality of PLMNs, a plurality of triggers or trigger events of the random access procedure, a plurality of QoS requirements, a plurality of logical channels or logical channel groups, a plurality of cell IDs, or a plurality of BWPs. In some embodiments, the plurality of values can be configured by the wireless communication node. For example, the plurality of values can be configured using the alternatives for configuring the RACH type selection factor, as described herein above.

In some embodiments, the plurality of values received at operation <NUM> can respectively be configured based on a plurality of access categories. In some embodiments, the plurality of values can respectively be configured based on a plurality of UAC-BarringInfoSets. In some embodiments, the plurality of values can respectively be configured based on a plurality of access identities. In some embodiments, the plurality of values can respectively be configured based on a plurality of PLMNs. In some embodiments, the plurality of values can respectively be configured based on a plurality of triggers or trigger events of the <NUM>-step random access procedure or the <NUM>-step random access procedure to access to the wireless communication node. In some embodiments, the plurality of values can respectively be configured based on a plurality of QoS requirements. In some embodiments, the plurality of values can respectively be configured based on a plurality of logical channels or logical channel groups. In some embodiments, the plurality of values can respectively be configured based on a plurality of cells. In some embodiments, the plurality of values can respectively be configured based on a plurality of BWPs.

As an example, when the plurality of parameters are a plurality of access categories (i.e., when the "RACH type selection factor" is per access category), the wireless communication node can configure a factor <NUM> for access category <NUM>, a factor <NUM> for access category <NUM>, and a factor <NUM> for access category <NUM>, and so on. Continuing with this example, the wireless communication device can then determine or decide the access category, generate a randomly generated value, and compare the randomly generated value with the corresponding factor. For instance, if the access category is category <NUM>, the factor to be compared against is factor <NUM>.

Referring again to <FIG>, at operation <NUM>, the wireless communication device selects one parameter from the plurality of parameters. Continuing with the above example, when the plurality of parameters are a plurality of access categories, the wireless communication device can select one category from the plurality of access categories. At operation <NUM>, the wireless communication device can compare a randomly generated value with a value selected from the plurality of values to determine whether the randomly generated value satisfies the value. In some embodiments, the value is selected or determined from the plurality of values according to the selected parameter at operation <NUM>. In some embodiments, the wireless communication device can generate a random number as the randomly generated value. In other embodiments, the randomly generated value can be generated by another device and transmitted to the wireless communication device. In some embodiments, the randomly generated value can be in the range of greater than or equal to <NUM>, and less than <NUM> (<NUM> ≤ randomly generated value < <NUM>). In other embodiments, the randomly generated value can be in other ranges.

In some embodiments, responsive to determining that the randomly generated value satisfies the value selected from the plurality of values (e.g., the randomly generated value is less than, or less than or equal to, or greater than, or greater than or equal to the value) at operation <NUM>, the process <NUM> proceeds to operation <NUM>. Otherwise, the process <NUM> proceeds to operation <NUM>.

In some embodiments, a wireless communication node (e.g., BS <NUM>) can transmit, to a wireless communication device (e.g., UE <NUM>), information indicating a plurality of values. In some embodiments, the plurality of values can respectively correspond to a plurality of parameters. In some embodiments, the plurality of values respectively correspond to a plurality of parameters. In some embodiments, the plurality of parameters can be a plurality of access control parameters, such as a plurality of access categories, a plurality of UAC-BarringInfoSets, or a plurality of access identities. In some embodiments, the plurality of parameters can be a plurality of non-access control parameters, such as a plurality of PLMNs, a plurality of triggers or trigger events of the random access procedure, a plurality of QoS requirements, a plurality of logical channels, a plurality of logical channel groups, a plurality of cell IDs, or a plurality of BWPs. In some embodiments, the plurality of values can be configured by the wireless communication node. For example, the plurality of values can be configured using the alternatives for configuring the RACH type selection factor, as described herein above.

In some embodiments, the wireless communication node can receive, from the wireless communication device, a first message to access to the wireless communication node. In some embodiments, the first message can include a random access preamble when the <NUM>-step random access procedure is selected (e.g., by the wireless communication device). In some embodiments, the first message can include a random access preamble and a payload when the <NUM>-step random access procedure is selected (e.g., by the wireless communication device). In some embodiments, the payload may be optional. In some embodiments, the preamble may be optional. In some embodiments, the wireless communication node can transmit a second message in response to the first message.

In some embodiments, a "RACH type selection timer" based solution can be considered or implemented for RACH type selection. In some embodiments, during the running of each timer, a corresponding UE (e.g., UE <NUM>) is not allowed to initiate a <NUM>-step random access procedure regardless of whether the condition for the selection of the <NUM>-step random access procedure is met if configured. On the other hand, when the timer expires or is stopped, the UE is allow to select a <NUM>-step random access procedure or a <NUM>-step random access procedure, or perform the RACH type selection if other threshold(s) for type selection is configured.

In some embodiments, during the running of each timer, a corresponding UE (e.g., UE <NUM>) is only allowed to initiate a <NUM>-step random access procedure or is allowed to initiate a <NUM>-step RACH provided that the condition for the selection of the <NUM>-step random access procedure is met if configured. On the other hand, when the timer expires or is stopped, the UE can only perform the <NUM>-step RACH.

In some embodiments, one or multiple times can be configured, with the same or different length. In some embodiments, the length of the timer can be configured using the following alternatives or options. In a first alternative, the timer can be directly configured by a network or a BS, and can be broadcasted in system information or signaled by a Radio Resource Control (RRC) signaling. In a second alternative, a default length of timer can be configured or predefined (predetermined), and scaling factors can be used for configuring of the length of the timer. When the scaling factor is missing, the default length is used.

In some embodiments, with respect to the start of the timer, a "RACH type selection timer enable indicator" can be used to control the timer configured. In some embodiments, the "RACH type selection timer enable indicator" can be one bit if a unified timer is configured, or a bit string if multiple timers are configured. In some embodiments, a "RACH type selection timer enable indicator" having a value "<NUM>" means the timer is started, and "<NUM>" means the timer is stopped. In other embodiments, difficult values or formats of the "RACH type selection timer enable indicator" can be used. In some embodiments, the "RACH type selection timer enable indicator" can be delivered or transmitted to the UE by system information or a RRC signaling, or included in a RA response or Msg <NUM>. In some embodiments, the UE can receive the "RACH type selection timer enable indicator" which can activate the timer. In some embodiments the timer can be started upon (or after a certain duration of) the first transmission of Msg1 of <NUM>-step RACH, or upon (or after a certain duration of) the first transmission of Msg1 of <NUM>-step RACH.

In some embodiments, the configuration of the timer can be broadcasted in system information or signaled by a RRC signaling. In some embodiments, the following alternatives or options can be considered or implemented for the configuration of the RACH type selection timer.

In alternative <NUM> of the configuration of the RACH type selection timer, the timer can be configured per access category. With (based on, using) the per access category configured timer, the UE can determine the access category first and then use the corresponding RACH type selection timer to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection timer, the timer can be configured per UAC-BarringInfoSet. With (based on, using) the per UAC-BarringInfoSet configured timer, the UE can determine the UAC-BarringInfoSet first and then use the corresponding RACH type selection timer to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection timer, the timer can be configured per access identity. With (based on, using) the per access identity configured timer, the UE can determine the access identity first and then use the corresponding RACH type selection timer to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection timer, the timer can be configured per PLMN. With (based on, using) the per PLMN configured timer, the UE can determine the PLMN first and then use the corresponding RACH type selection timer to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection time, the timer can be configured for different triggers or trigger events of the RACH procedure. In some embodiments, the following triggers or trigger events of the RACH procedure can be considered or implemented: (a) Initial access from RRC_IDLE; (b) RRC connection re-establishment procedure; (c) Handover; (d) Downlink (DL) or Uplink (UL) data arrival during RRC_CONNECTED when the UL synchronization status is "non-synchronized"; (e) UL data arrival during RRC_CONNECTED when there are no PUCCH resources for Scheduling Request (SR) available; (f) SR failure; (g) Request by RRC upon synchronous reconfiguration; (h) Transition from RRC_INACTIVE; (i) Establishing (or to establish) time alignment at SCell addition; (j) Request for other system information (which may be sometimes referred to as remaining and other system information in the NR mobile networks) or system information message (SI); (k) Beam failure recovery. In some embodiments, with (based on, using) the trigger-specific configured timer, the UE can determine the trigger first and then use the corresponding timer to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

For example, if timers for different trigger events are configured, and the "RACH type selection timer enable indicator" is set to "<NUM>" and broadcasted in system information, then the "RACH type selection timer" configured for trigger events other than the beam failure recovery (BFR) can be running. During the running of each timer, the RACH triggered by the corresponding events can only follow the <NUM>-step random access procedure, except for BFR triggered RACH where the UE can select the <NUM>-step random access procedure or the <NUM>-step random access procedure according to certain threshold(s) if configured.

In alternative <NUM> of the configuration of the RACH type selection timer, the timer can be configured for services with different QoS requirements, or different logical channels or different logical channel groups. For each type of service with different QoS requirement/logical channels/logical channel groups, a timer can be configured. Then, according to (based on, using) the QoS requirement/logical channels/logical channel groups, the UE uses the corresponding "RACH type selection timer" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection timer, the timer can be configured per cell. With (based on, using) the per cell configured timer, the UE can determine the cell first and then use the corresponding "RACH type selection timer" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In alternative <NUM> of the configuration of the RACH type selection timer, the RACH type selection factor can be configured per BWP. With (based on, using) the per BWP configured timer, the UE can determine the BWP first and then use the corresponding "RACH type selection timer" to determine which random access procedure (e.g., <NUM>-step random access procedure or <NUM>-step random access procedure) is to be selected.

In some embodiments, a combination of the above alternatives for configuring the RACH type selection timer can be considered or implemented. For example, for each cell or BWP, different RACH type selection timer(s) can be configured for different access category, access identifier, UAC-BarringInfoSet, trigger, or service type, etc. In some embodiments, if the configuration of the timer is absent, the UE can select the RACH type according to other configured or predefined criterion, if configured.

<FIG> is a flow diagram illustrating an example process <NUM> for enhanced random access procedure using the RACH type selection timer, in accordance with some embodiments of the present disclosure. In some embodiments, the process <NUM> can be performed by a wireless communication device (e.g., UE <NUM>). At operation <NUM>, the wireless communication device receives information indicating a timer from a wireless communication node (e.g., BS <NUM>). In some embodiments, the information can be broadcasted in system information, or by RRC signaling. In some embodiments, the timer can be or correspond to a RACH type selection timer. In some embodiments, the timer can be configured by the wireless communication node. For example, the timer can be configured using the alternatives for configuring the RACH type selection timer, as described herein above.

In some embodiments, the timer (e.g., a duration of the timer) indicated by the information received at operation <NUM> can be configured based on an access category. In some embodiments, the timer (e.g., a duration of the timer) can be configured based on a UAC-BarringInfoSet. In some embodiments, the timer (e.g., a duration of the timer) can be configured based on an access identity. In some embodiments, the timer (e.g., a duration of the timer) can be configured based on a PLMN. In some embodiments, the timer (e.g., a duration of the timer) can be configured based on one or more triggers or trigger events of the <NUM>-step random access procedure or the <NUM>-step random access procedure to access to the wireless communication node. In some embodiments, the timer (e.g., a duration of the timer) can be configured based on a QoS requirement/logical channels/logical channel groups. In some embodiments, the timer (e.g., a duration of the timer) can be configured based on a cell that the wireless communication device is in. In some embodiments, the timer (e.g., a duration of the timer) can be configured based on a BWP.

In some embodiments, a duration of the timer can be configured by a communication network or a BS, and broadcasted in system information. In some embodiments, a duration of the timer can be configured by a communication network or a BS, and signaled by a Radio Resource Control (RRC) signaling. In some embodiments, a duration of the timer can be configured based on a scaling factor, and in the event that the scaling factor is missing, a default duration can be used.

In some embodiments, the wireless communication device can receive an enable indicator (e.g., a RACH type selection timer enable indicator) which can activate or start the timer. In some embodiments, the enable indicator can be transmitted from the wireless communication node.

Referring again to <FIG>, at operation <NUM>, the wireless communication device can determine whether the timer in active. In some embodiments, the timer is active when the timer is running, and the timer is inactive when the timer expires or is stopped. In some embodiments, responsive to determining that the timer is active at operation <NUM>, the process <NUM> proceeds to operation <NUM>, and responsive to determining that the timer is inactive at operation <NUM>, the process <NUM> proceeds to operation <NUM>.

At operation <NUM>, the wireless communication device selects a <NUM>-step random access procedure to access to the wireless communication node responsive to determining that the timer is active. At operation <NUM>, the wireless communication device selects either the <NUM>-step random access procedure or a <NUM>-step random access procedure to access to the wireless communication node responsive to determining that the timer is inactive. If the <NUM>-step random access procedure is selected at operation <NUM>, the process <NUM> may proceed to operation <NUM>. If either the <NUM>-step random access procedure or the <NUM>-step random access procedure is selected at operation <NUM>, the process <NUM> may proceed to operation <NUM>.

At operation <NUM>, the wireless communication device transmits a first message to access to the wireless communication node. The content of the first message being transmitted at operation <NUM> can be based on the selection of the <NUM>-step random access procedure or the <NUM>-step random access procedure at operation <NUM>. In some embodiments, the content of the first message may include a random access preamble when (responsive to) the <NUM>-step random access procedure is selected at operation <NUM>. In some embodiments, the content of the first message may include a random access preamble and a payload when (responsive to) the <NUM>-step random access procedure is selected at operation <NUM>. In some embodiments, the payload may be optional. In some embodiments, the preamble may be optional.

In some embodiments, a wireless communication node (e.g., BS <NUM>) can transmit, to a wireless communication device (e.g., UE <NUM>), information indicating a timer. In some embodiments, the timer can be or correspond to a RACH type selection timer. In some embodiments, the timer can be configured by the wireless communication node. For example, the value can be configured using the alternatives for configuring the RACH type selection timer, as described herein above. In some embodiments, the wireless communication node can receive, from the wireless communication device, a first message to access to the wireless communication node. In some embodiments, the first message can include a random access preamble when the <NUM>-step random access procedure is selected (e.g., by the wireless communication device). In some embodiments, the first message can include a random access preamble and a payload when the <NUM>-step random access procedure is selected (e.g., by the wireless communication device). In some embodiments, the payload may be optional. In some embodiments, the preamble may be optional. In some embodiments, the wireless communication node can transmit a second message in response to the first message.

In some embodiments, a Backoff indication can be included in a Msg2 (e.g., the Msg2 in a <NUM>-step random access procedure or a <NUM>-step random access procedure). When a UE receives a backoff indication, the UE can determine the backoff time according to the backoff indication. During the running of backoff time, the UE is not allowed to retry the correspondent random access procedure or RACH.

In some embodiments, a backoff indication can be configured according to the following alternatives: (a) in a first alternative, one backoff indication can be configured for both RACH types (e.g., the <NUM>-step random access procedure and the <NUM>-step random access procedure); (b) in a second alternative, one backoff indication is configured for either the <NUM>-step random access procedure or the <NUM>-step random access procedure; (c) in a third alternative, separate backoff indications can be configured for the <NUM>-step random access procedure and <NUM>-step random access procedure, respectively, and can be included in a Msg2. For example, during the backoff time for the <NUM>-setp random access procedure and the <NUM>-step random access procedure, the UE cannot initiate random access procedure. However, if the backoff time for the <NUM>-step random access procedure is running, and the backoff time for <NUM>-step random access procedure is not running, the UE can only initiate <NUM>-step random access procedure. Similarly, if the backoff time for the <NUM>-step random access procedure is running, and the backoff time for <NUM>-step random access procedure is not running, the UE can only initiate <NUM>-step random access procedure.

In some embodiments, a combination of above alternatives can be considered or implemented. For example, different "RACH type selection factors" can be configured for different trigger events. On top of that, separated backoff times can be configured for the <NUM>-step random access procedure and the <NUM>-Step random access procedure. An example is provided below, with the assumption that the backoff time for the <NUM>-step random access procedure is longer than the backoff time for <NUM>-step random access procedure.

At Step <NUM> of the Example, the UE determines the RACH type selection factor based on triggering events. The UE then selects the RACH type by comparing a randomly generated number against the RACH type selection factor.

At Step <NUM> of the Example, the UE selects the RACH resource and transmits a Msg1 on the selected RACH resource.

At Step <NUM> of the Example, the UE receives a Msg2 which includes separated backoff indications for <NUM>-step random access procedure and <NUM>-step random access procedure.

At Step <NUM> of the Example, after or when the backoff time for the <NUM>-step random access procedure expires or stops, while the backoff time for <NUM>-step random access procedure is still running, the UE re-attempts the <NUM>-step random access procedure. If the UE still has not gained access to the BS after the backoff time for the <NUM>-step random access procedure expires or stops, then UE re-attempts RACH by going back to step <NUM>.

<FIG> is a flow diagram illustrating an example process <NUM> for enhanced random access procedure with the backoff indication, in accordance with some embodiments of the present disclosure. In some embodiments, the process <NUM> can be performed by a wireless communication device (e.g., UE <NUM>). At operation <NUM>, the wireless communication device transmits a first message to access to a wireless communication node (BS <NUM>). In some embodiments, the content of the first message can be based on a selection of a <NUM>-step random access procedure or a <NUM>-step random access procedure. In some embodiments, the selection of the <NUM>-step random access procedure or the <NUM>-step random access procedure can be the performed using the "RACH type selection factor" or the "RACH type selection timer" processes as described herein above. In some embodiments, the content of the first message can include a random access preamble when the <NUM>-step random access procedure is selected. The content of the first message can include the random access preamble and a payload when the <NUM>-step random access procedure is selected. In some embodiments, the payload may be optional. In some embodiments, the preamble may be optional.

At operation <NUM>, the wireless communication device receives, from the wireless communication node, in response to transmitting the first message, a second message indicating a first timer. In some embodiments, the first time can be a backoff timer or indication, for example, as described herein above.

At operation <NUM>, the wireless communication device determines that first timer is inactive. In some embodiments, the wireless communication device can determines whether the first timer is active (e.g., running). If the first timer is active or running, the wireless communication device is not allowed to retry the random access procedure or RACH. In such a case, the wireless communication device may wait until the first timer expires or stops. On the other hand, if first timer is inactive (e.g., not running, stops, or expires after running for the duration of the timer), the wireless communication device can retry the random access procedure.

At operation <NUM>, responsive to determining that the first timer is inactive at operation <NUM>, the wireless communication device selects either the <NUM>-step random access procedure or the <NUM>-step random access procedure to retransmit the first message. In some embodiments, the first timer can be configured for both the <NUM>-step random access procedure and the <NUM>-step random access procedure. In such a case, the wireless communication device can either retransmit the first message at operation <NUM> using the same random access procedure used at operation <NUM>, or select one of the <NUM>-step random access procedure or the <NUM>-step random access procedure according to the "RACH type selection factor" or the "RACH type selection timer" processes as described herein above.

In some embodiments, the first timer can be configured for one of the <NUM>-step random access procedure or the <NUM>-step random access procedure. In such a case, the wireless communication device can retransmit the first message based on the random access procedure (i.e., either the <NUM>-step random access procedure or the <NUM>-step random access procedure) associated with the first timer.

In some embodiments, the first timer can include a first value and a second value. For example, the first value can be configured for the <NUM>-step random access procedure, and the second value can be configured for the <NUM>-step random access procedure. In such a case, the wireless communication device can retransmit the first message using the random access procedure associated with the value indicating an inactive timer. If both the first value and the second value indicate inactive timers, the wireless communication device can either retransmit the first message at operation <NUM> using the same random access procedure used at operation <NUM>, or select one of the <NUM>-step random access procedure or the <NUM>-step random access procedure according to the "RACH type selection factor" or the "RACH type selection timer" processes as described herein above.

In some embodiments, a wireless communication node (e.g., BS <NUM>) can receive, from a wireless communication device (e.g., UE <NUM>), a first message. In some embodiments, the content of the first message can be based on a selection of a <NUM>-step random access procedure or a <NUM>-step random access procedure. In some embodiments, the wireless communication node can transmit, to the wireless communication device in response to receiving the first message, a second message indicating a first timer. For example, the first timer can be a backoff time or indication. In some embodiments, the wireless communication node can receive the first message transmitted from the wireless communication device.

In some embodiments, at least one of the following information can be included in the payload of Msg1 in the <NUM>-step random access procedure to implicitly or explicitly indicate the time-domain resource on which the corresponding preamble is transmitted. For example, the information can include: (a) System Frame Number (SFN) index or the Least Significant Bit (LSB) of the SFN index and slot index; (b) Absolute timing which can contain at least the Coordinated Universal Time corresponding to the SFN boundary at or immediately after the ending boundary of the slot in which preamble is transmitted; (c) SFN mod N, where SFN is the index of the radio frame in which the preamble is transmitted, and N is the periodicity of consecutive RACH occasions (ROs); and (d) Random access radio network temporary identifier (RA-RNTI) value that is determined by the RO in which the preamble is transmitted.

In some embodiments, a counter based solution can be considered or implemented for the transmission control of Msg1 in the <NUM>-step random access procedure. In some embodiments, the UE may implement a counter in the MAC layer or physical layer. For each Msg1 transmission, the UE can increase the counter by <NUM>. When the counter exceeds a maximum number of allowable transmission times, the UE can report a RACH failure.

In some embodiments, the counter and the maximum number of allowable transmission times can be configured according to following alternatives.

In a first alternative, one transmission counter and one maximum number of allowable transmission times are defined or configured (e.g., Transmax is defined for both the <NUM>-step RACH and <NUM>-step RACH). For each transmission of Msg1, regardless if it is Msg1 of the <NUM>-step RACH or the <NUM>-step RACH, the counter is increased by <NUM>. For example, if counter >= (Transmax +<NUM>), the UE reports a RACH failure.

In a second alternative, one transmission counter and separate maximum number of allowable transmission times are defined or configured for the <NUM>-step RACH and the <NUM>-step RACH (e.g., transmax-2step for the <NUM>-step RACH and transmax-4step for the <NUM>-stepRACH). In the case that the transmax-2step is smaller than the transmax-4step, if transmission counter < = transmax-2step, the UE can initiate either a <NUM>-step RACH or a <NUM>-step RACH; if transmax-2step < transmission counter < = transmax-4step, the UE is only allowed to initiate the 4step RACH. Similarly, in the case that the transmax-4step < the transmax-2step, if transmission counter < = transmax-4step, the UE can initiate either a <NUM>-step RACH or a <NUM>-step RACH; if transmax-4step < transmission counter < = transmax-2step, the UE is only allowed to initiate the 2step RACH. If the counter is larger than max {transmax-4step, transmax-2step}, the UE reports a RACH failure.

In a third alternative, separate counters and separate maximum number of allowable transmission times are defined or configured. One total allowable transmax-total can be defined or configured. Separate counters and separate maximum number of allowable transmission times are maintained for the <NUM>-step RACH and the <NUM>-step RACH (e.g., counter-2stepRACH and transmax-2stepRACH are for the <NUM>-stepRACH while counter-4stepRACH and transmax-4stepRACH are for 4stepRACH). The UE is not allowed to select <NUM>-step RACH or <NUM>-step RACH if the corresponding counter exceeds the configured corresponding maximum number of allowable transmission times. The UE reports a RACH failure when (counter-2stepRACH + counter-4stepRACH) exceeds transmax-total.

In a fourth alternative, a counter for Msg1 transmission (regardless it is Msg1 for <NUM>-step RACH or Msg1 for <NUM>-step RACH) and a maximum number of allowable transmission times for <NUM>-step RACH can be configured, e.g., TransCounter, and transmax-2stepRACH. The counter can increase by <NUM> for each <NUM>-step RACH attempt. After the first attempt of the <NUM>-step RACH, the UE can only re-attempts <NUM>-step RACH if the TransCounter<= transmax-2stepRACH. If the TransCounter >= transmax-2stepRACH+<NUM>, then UE only allows to perform <NUM> step RACH. Additionally, a maximum number of total allowable transmission time can be configured, e.g., transmax. If TransCounter >= transmax+<NUM>, then UE reports a RACH failure.

In a fifth alternative, a timer for reporting RACH failure can be introduced. The timer starts upon the first transmission of Msg1. During the running of timer, the UE can re-attempt RACH if needed. The timer stops upon successful completion of the RACH procedure. Upon expiry of the timer, UE reports a RACH failure.

In some embodiments, a combination of one or more of the above alternatives can also be considered or implemented. For example, one counter and one transmax can be configured; on top of that, a timer can be additionally configured. If either threshold is satisfied, the UE reports a RACH failure.

In some embodiments, after the transmission of Msg1, the UE can monitor corresponding search space with random access radio network temporary identifier (RA-RNTI), which is computed based on the RO in which the preamble part of Msg1 transmits.

The RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted, can be computed as: <MAT> where s_id is the index of the first OFDM symbol of the PRACH occasion (<NUM> ≤ s_id < <NUM>), t_id is the index of the first slot of the PRACH occasion in a system frame (<NUM> ≤ t_id < <NUM>), f_id is the index of the PRACH occasion in the frequency domain (<NUM> ≤ f_id < <NUM>), and ul_carrier_id is the UL carrier used for Random Access Preamble transmission (<NUM> for NUL carrier, and <NUM> for SUL carrier).

In some embodiments of the present disclosure, the RNTI has a bitwidth of <NUM> bits. For the cases where the cell size is extensively large (e.g., a non-terrestrial network (NTN)) or the user density is very high (e.g., Internet of things (IoT) services), the bitwidth of RNTI can be extended to meet the connectivity requirements. Thus, some indications can be introduced to enable the usage of the long RNTI. For example, a one bit indicator (e.g., long-RNTI-enabled) can be introduced. In some embodiments, if the long-RNTI-enabled is set to '<NUM>', the long RNTI sequence can be used for scrambling; if the long-RNTI-enabled is set to '<NUM>', the normal RNTI sequence can be used for scrambling. Absent of this indicator, interpreted as the long-RNTI-enabled is set to '<NUM>', and normal RNTI sequence can be used for scrambling.

In some embodiments, the indication can be configured by following alternatives: (a) in a first alternative, the indication is included in master information block (MIB); (b) in a second alternative, the indication is included in system information block (SIB); (c) in a third alternative, the indication is configured per frequency band (e.g., for transmissions utilizing the frequency band configured with the "long-RNTI-enabled" being set to '<NUM>', the long RNTI sequence will be used for scrambling); and (d) in a fourth alternative, the indication is configured per PLMN.

In some embodiments, if the long RNTI is used, the system frame information of the RO in which preamble part of Msg1 transmits can be included in the formula of the RA-RNTI, which can be one of following: (a) LSB of SFN index; (b) SFN_index; (c) SFN_index mod N, where the SFN index equals the index of system frame number where the PRACH occasion starts, and the PRACH occasion is where the preamble part of Msg1 transmits. N is the smallest integer that is greater than or equal to the RAR window size in radio frames (e.g., if RAR window size takes up <NUM> radio frames, then N equals <NUM>).

An example is provided below:<MAT> where frame_id = SFN_index mod N; N is the smallest integer that is greater than or equal to the RAR window size in radio frames, which can be written as CIEL (RAR window size in radio frames); and SFN_index is the index of system frame number where PRACH occasion starts, and the PRACH occasion is where the preamble part of Msg1 transmits.

In some embodiments, the following alternatives can be considered or implemented with respect to the content and format of Msg2 of the <NUM>-step random access procedure.

In some embodiments, a Msg2 MAC protocol data unit (PDU) can include one or more MAC subPDUs and optionally padding. Each MAC subPDU can include one of the following: (a) a MAC subheader with Backoff Indicator only; (b) a MAC subheader and SuccessRAR; and (c) a MAC subheader and fallbackRAR.

In some embodiments, the MAC subheader for Msg2 includes the following fields: (a) E: the Extension field is a flag indicating whether the MAC subPDU that includes this MAC subheader is the last MAC subPDU in the MAC PDU. In some embodiments, the size of the E field is <NUM> bit. (b) T: the Type field is a flag indicating the presence of the Backoff Indicator within the MAC subheader, the presence of MAC RAR after the MAC subheader, and the type of the corresponding MAC RAR if present (e.g., successRAR or fallback RAR). In some embodiments, the size of the T field is <NUM> bits. (c) BI: the Backoff Indicator field identifies the overload condition in the cell. In some embodiments, the size of the BI field is <NUM> bits. (d) R: Reserved bit, set to "<NUM>", in some embodiments.

In some embodiments, the definition of the 2bits T field can be implemented as follows: (a) "<NUM>": indicating the presence of a Backoff Indicator field in the subheader (BI); (b) "<NUM>": indicating the presence of a successRAR in the MAC subPDU; (c) "<NUM>": indicating the presence of a fallbackRAR in the MAC subPDU; and (d) "<NUM>": reserved. In some embodiments, the T field can also be used to indicate the presence of a MAC subPDU for the common configuration of the resource for the transmission of ACK of MsgB reception, and the value "<NUM>" of T field can be used in such case.

It should be understood that the value used for each case listed above is an example, and the mapping between the value and the case is not limited to the examples above. They are provided for illustrative purpose only and should not be regarded as limiting.

In some embodiments, the following two kinds of MAC subheader can be supported in the MAC PDU for the Msg1 response in <NUM>-step RACH: (a) The MAC subheader with Backoff Indicator only, which includes four header fields: E/T/R/BI; and (b) The MAC subheader for successRAR and fallback RAR, which includes seven header fields: E/T/R/R/R/R/R.

In some embodiments, the successRAR is of a fixed size, and can include the following fields: (a) Contention Resolution ID: this field contains the UL common control channel (CCCH) service data unit (SDU). In some embodiments, if the UL CCCH SDU is longer than <NUM> bits, this field contains the first <NUM> bits of the UL CCCH SDU. In some embodiments, the size of the Contention Resolution ID is <NUM> bits. (b) Timing Advance Command (TAC): the same as the TAC field in MAC RAR for the <NUM>-step RACH. In some embodiments, the size of the Timing Advance Command field is <NUM> bits. (c) C-RNTI (cell radio network temporary identifier): the C-RNTI allocated for the UE within the cell. In some embodiments, the size of the C-RNTI field is <NUM> bits. (d) R: Reserved bit, set to <NUM>, in some embodiments. (e) In some embodiments, UL grant may be included in the successRAR, or some field to carry the configuration of resource for the transmission of ACK for MsgB reception.

In some embodiments, the fallbackRAR is of a fixed size, and can include the following fields: (a) RAPID: The Random Access Preamble Identifier field identifies the transmitted Random Access Preamble. In some embodiments, the size of the RAPID field is <NUM> bits. (b) Timing Advance Command (TAC): the same as the TAC field in MAC RAR for <NUM>-step RACH. In some embodiments, the size of the Timing Advance Command field is <NUM> bits. (c) UL Grant: the same as the UL Grant field in MAC RAR for <NUM>-step RACH. In some embodiments, the size of the UL Grant field is <NUM> bits. (d) Temporary C-RNTI: the Temporary C-RNTI field indicates the temporary identity that is used by the MAC entity during Random Access. In some embodiments, the size of the Temporary C-RNTI field is <NUM> bits. (e) R: Reserved bit, set to <NUM>, in some embodiments.

In some embodiments, a Msg2 MAC PDU includes one or more MAC subPDUs and optionally padding. Each MAC subPDU can include one of the following: (a) a MAC subheader with Backoff Indicator only; and (b) a MAC subheader with RAPID and MAC RAR, where the MAC RAR can be used to carry either the successRAR or fallback RAR.

In some embodiments, the MAC subheader for Msg2 can include the following fields: (a) E: the Extension field is a flag indicating whether the MAC subPDU that includes this MAC subheader is the last MAC subPDU in the MAC PDU. In some embodiments, the size of the E field is <NUM> bit. (b) T: the Type field is a flag indicating the presence of the Backoff Indicator within the MAC subheader, and the presence of MAC RAR after the MAC subheader. In some embodiments, the size of the T field is <NUM> bit. (c) BI: the Backoff Indicator field identifies the overload condition in the cell. In some embodiments, the size of the BI field is <NUM> bits. (d) RAPID: The Random Access Preamble Identifier field identifies the transmitted Random Access Preamble. In some embodiments, the size of the RAPID field is <NUM> bits. (e) R: Reserved bit, set to "<NUM>", in some embodiments.

In some embodiments, the definition of the <NUM> bit T field in MAC subheader can be implemented as follows: (a) "<NUM>": indicating the presence of a Backoff Indicator field in the subheader (BI), and "<NUM>": indicating the presence of a MAC RAR in the MAC subPDU; Or (b) "<NUM>": indicating the presence of a Backoff Indicator field in the subheader (BI), and "<NUM>": indicating the presence of a MAC RAR in the MAC subPDU.

In some embodiments, the following two kinds of MAC subheader can be supported in the MAC PDU for Msg1 response in the <NUM>-step RACH: (a) The MAC subheader with Backoff Indicator only, which includes four header fields: E/T/R/BI; and (b) The MAC subheader for successRAR and fallback RAR, which includes seven header fields: E/T/RAP ID.

In some embodiments, the MAC RAR is of a flexible size, and includes the one T field and the fields for successRAR or fields for fallback RAR. T: the Type field is a flag indicating the whether the fields for successRAR or the fields for fallbackRAR are included in the MAC RAR.

In some embodiments, the definition of the <NUM> bit T field in MAC RAR is as follow: (a) "<NUM>": indicating the MAC RAR includes the fields for successRAR, and "<NUM>": indicating the MAC RAR includes the fields for fallbackRAR; Or (b) "<NUM>": indicating the MAC RAR includes the fields for successRAR, and "<NUM>": indicating the MAC RAR includes the fields for fallbackRAR. In some embodiments, the size of T field can also be larger than <NUM> bit. If the T field is larger than <NUM> bit, besides the value used to indicate the MAC RAR including the field for successRAR or fallbackRAR, the other value can either be reserved for further use, or be used for other purpose.

In some embodiments, the fields of success RAR are included in the following information: (a) Contention Resolution ID: this field contains the UL CCCH SDU. In some embodiments, if the UL CCCH SDU is longer than <NUM> bits, this field contains the first <NUM> bits of the UL CCCH SDU. In some embodiments, the size of the Contention Resolution ID is <NUM> bits. (b) Timing Advance Command (TAC): the same as the TAC field in MAC RAR for <NUM>-step RACH. In some embodiments, the size of the Timing Advance Command field is <NUM> bits. (c) C-RNTI: the C-RNTI allocated for the UE within the cell. In some embodiments, the size of the C-RNTI field is <NUM> bits. (d) R: Reserved bit, set to <NUM>, in some embodiments. In some embodiments, UL grant may be included in the successRAR, or some field to carry the configuration of resource for the transmission of ACK for MsgB reception.

In some embodiments, the fields of fallback RAR are included in the following information: (a) Timing Advance Command (TAC): the same as the TAC field in MAC RAR for the <NUM>-step RACH. In some embodiments, the size of the Timing Advance Command field is <NUM> bits. (b) UL Grant: the same as the UL Grant field in MAC RAR for the <NUM>-step RACH. In some embodiments, the size of the UL Grant field is <NUM> bits. (c) Temporary C-RNTI: the Temporary C-RNTI field indicates the temporary identity that is used by the MAC entity during Random Access. In some embodiments, the size of the Temporary C-RNTI field is <NUM> bits. (d) R: Reserved bit, set to <NUM>, in some embodiments.

In some embodiments, for both solution <NUM> and solution <NUM> (alternative <NUM> and alternative <NUM> below), the acknowledgment (ACK) resource information can be included in Msg2 as well. With the ACK resource information included, the UE determines the resource for the transmission of the ACK for Msg2. In some embodiments, the following can be the solutions for the configuration of the ACK resource: (a) alternative <NUM>: Separate MAC subPDU for common resource and explicit UE specific resource configuration in another separate MAC subPDU; (b) alternative <NUM>: Separate MAC subPDU for common resource and implicit UE specific resource configuration in another separate MAC subPDU; and (c) alternative <NUM>: UE specific ACK resource as part of success RAR.

In some embodiments, the configuration of common resource, or part of configuration of common resource can also be included in DCI, which is used to schedule the MsgB. In some embodiments, the ACK of MsgB reception can be carried on PUCCH, PUSCH or some other physical channels designed for the transmission of feedback specifically.

In some embodiments, for alternative <NUM> and alternative <NUM>, the common MAC subPDU can be the time, and/or frequency, and/or code domain resource which can be used by multiple UEs, for which the corresponding successRAR can be found in the same Msg2. In some embodiments, the code domain resource refer to the code or sequence which will be used in the transmission of ACK of MsgB reception, including the generation of ACK signal.

In some embodiments, for alternative <NUM>, some kind of UE specific resource configuration can be explicitly included in another separate MAC subPDU. In some embodiments, the explicit configuration resource can be at least one of the following: (a) Code domain resource, which can be used by the UE in the ACK transmission, or some parameters that can be used to calculate or derive the code domain resource that is to be used by the UE; (b) Frequency domain resource, which can be used by the UE in the ACK transmission, or some parameters that can be used to calculate or derive the frequency domain resource that is to be used by the UE; (c) Time domain resource, which can be used by the UE in the ACK transmission, or some parameters that can be used to calculate or derive the time domain resource that is to be used by the UE; and (d) Index of resource configured in the common MAC subPDU for the common resource, where a resource pool can be configured as the common resource. For example, in a common resource pool, it indicates code from X to Y are reserved for the transmission of the ACK, and in the UE specific resource configuration, an index can be used to indicate that the nth code is to be used for the transmission of the ACK.

In some embodiments, for alternative <NUM>, some kind of UE specific resource configuration can be implicitly included in another separate MAC subPDU. In some embodiments, the implicit configuration resource can be at least one of the following: (a) UE derives the time domain resource based on the RAP ID (e.g., Random Access Preamble identifier corresponding to the transmitted PREAMBLE_INDEX), or the sequence of MAC subPDU in the whole MAC PDUs in the Msg2, or the sequence of MAC success RAR in the whole MAC success RARs in the Msg2, or the sequence of MAC RAR in the whole MAC RARs included in the Msg2; (b) UE derives the frequency domain resource based on the RAP ID (e.g., Random Access Preamble identifier corresponding to the transmitted PREAMBLE_INDEX), or the sequence of MAC subPDU in the whole MAC PDUs in the Msg2, or the sequence of MAC success RAR in the whole MAC success RARs in the Msg2, or the sequence of MAC RAR in the whole MAC RARs included in the Msg2; and (c) UE derives the code domain resource based on the RAP ID (e.g., Random Access Preamble identifier corresponding to the transmitted PREAMBLE_INDEX), or the sequence of MAC subPDU in the whole MAC PDUs in the Msg2, or the sequence of MAC success RAR in the whole MAC success RARs in the Msg2, or the sequence of MAC RAR in the whole MAC RARs included in the Msg2.

In some embodiments, for alternative <NUM> and alternative <NUM> above, the corporation method of common resource and the UE specific resource can be as follows: (a) Alt1: the resource of the ACK can include the resource in time/frequency/code domain. Part of the resources can be configured as common resource and the rest can be configured as UE specific resource. For example, the common resource can include the resource in frequency and time domain, and the UE specific resource can include the resource in code domain. Alternatively, the common resource can include the resource in time domain, and the UE specific resource can include the resource in code domain and frequency domain. (b) Alt2: the common resource can include a pool of resource (e.g., a list of resource or a range of resource), and the UE specific resource can include an index to indicate one of the resource in the pool. (c) Alt3: a combination of Alt1 and Alt2. For example, the common resource can include the configuration of time and frequency resource, as well as a range or a list of code domain resource. The UE can determine the code domain resource based on some kind of index derived based on the UE specific resource configuration (in either explicit way or implicit way) and the range/list given in the common resource.

In some embodiments, to include the MAC subPDU for the common ACK resource, a new MAC subPDU is to be supported which includes a MAC subheader and ACK resources. In some embodiments, the definition of the 2bits T field in the MAC subheader can be implemented as follows: (a) "<NUM>": indicating the presence of a Backoff Indicator field in the subheader (BI); (b) "<NUM>": indicating the presence of a successRAR in the MAC subPDU; (c) "<NUM>": indicating the presence of a fallbackRAR in the MAC subPDU; and (d) "<NUM>": indicating the presence of ACK resource in the MAC subPDU.

Claim 1:
A method of random access, comprising:
transmitting, by a wireless communication device (<NUM>, <NUM>), a first message including a preamble and a data payload to a network; and
receiving, by the wireless communication device (<NUM>, <NUM>) from the network, a second message in response to the first message,
wherein the second message is a MAC PDU that includes one or more MAC subPDUs, characterised in that at least one MAC subPDU of the one or more MAC subPDUs includes a first MAC subheader and SuccessRAR, and
wherein the SuccessRAR has a fixed size and comprises:
a contention resolution identifier,
a timing advance command, TAC,
a cell radio network temporary identifier, C-RNTI,
a reserved bit, and
a configuration of an acknowledgement resource for transmission of an acknowledgment of receiving the second message,
wherein the configuration of the acknowledgement resource comprises:
a code domain resource information,
a frequency domain resource information, and
a time domain resource information.