Patent Description:
When a user equipment (UE) initially attaches to a network or participates in a handover between cells, a random access procedure is performed by the UE and the entity (such as an evolved NodeB (eNB), low power node (LPN), and so on) to which it is attaching in order to setup a connection with the entity. <NPL> a random access procedure for use by a UE to operate coverage enhancements. The UE selects a preamble within a PRACH preamble group and transmits the preamble in configured PRACH resources. If the UE does not receive RAR within a response window, it will retry preamble transmission until the maximum tries for that coverage level. <CIT> discloses a method for transmitting a preamble over a Random Access CHannel (RACH) in a wireless communication system. The method includes generating a preamble having a length longer than a basic transmission unit, and dividing the preamble into preambles having a length less than the basic transmission unit; and sequentially transmitting the divided preambles over the RACH using different antennas. <CIT> discloses a random access procedure for use by a UE wireless communication terminal in communicating with a base station (or Node-B or eNB) of a radio access network, and in particular a E-UTRA network. A random access preamble is sent by the UE via RACH separate and prior to a random access message burst, which is sent on SCH but not until the UE receives one or more messages indicating an acknowledgment of the preamble and providing an allocation on SCH for use in transmitting the message burst, and also providing a preamble identifier, which the radio access network can then use to request retransmission of the message burst if necessary.

In accordance with an example embodiment, a method for transmitting a random access preamble according to claim <NUM> is provided. The method includes generating, by a UE, the random access preamble, and when a number of physical random access channel (PRACH) repetitions per attempt is larger than a threshold, segmenting, by the UE, the random access preamble into a plurality of blocks, and separately transmitting, by the UE, each of the plurality of blocks.

Separately transmitting each of the plurality of blocks includes interleaving at least some of the plurality of blocks with an uplink data channel.

In accordance with an example embodiment, a non-transitory computer-readable medium storing programming for execution by at least one processor is provided. The programming including instructions to implement the method according to any one of claims <NUM> to <NUM>.

Practice of the foregoing embodiments enables the adaptation of the backoff window used in contention resolution to meet the extended preamble durations of narrow band communications systems. Fixed backoff windows cannot effectively deal with channel contention without sacrificing overall efficiency.

The making and using of the presently example embodiments are discussed in detail below. It should be appreciated, however, that the present disclosure provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the embodiments, and do not limit the scope of the disclosure.

<FIG> illustrates a high-level diagram of an Internet of Things (IoT) communications system <NUM>. IoT communications system <NUM> includes a network <NUM> that is connected to a wide variety of IoT devices, including electrical devices, physical objects, and other items, that are consumer, industrial, automotive, environment, agricultural, military, medical, and retail in nature. Network <NUM> allows the IoT devices to be connected, as well as controlled. Network <NUM> may be any existing communications infrastructure, such as the Internet, a private or public data network, and so on.

<FIG> illustrates an example IoT communications system <NUM> implemented using a heterogeneous network (HetNet). The HetNet includes a planned network infrastructure, such as a 3GPP LTE compliant communications network, or any other standards or non-standards compliant communications network wherein communications take place through entities that are deployed in a structured fashion. As shown in <FIG>, the planned network infrastructure includes a plurality of evolved NodeBs (eNBs), including eNB <NUM> with coverage area <NUM>, eNB <NUM> with coverage area <NUM>, and eNB <NUM> with coverage area <NUM>. The HetNet also includes an unplanned network infrastructure. The unplanned network infrastructure may include low powered nodes (LPNs) that are deployed by an operator of the HetNet or by users of the HetNet to help improve coverage and/or overall communications system performance. The unplanned network infrastructure shown in <FIG> includes a plurality of LPNs, including LPN <NUM> with coverage area <NUM> and LPN <NUM> with coverage area <NUM>. As their name implies, the LPNs usually transmit at a lower power level than the eNBs of the planned network infrastructure. eNBs and LPNs may be referred to as cells or transmission points.

The HetNet serves IoT devices, such as IoT device <NUM>, IoT device <NUM>, and IoT device <NUM>, that are either mobile or immobile. The capabilities of the IoT devices may vary widely. As an example, if the IoT device is a smart device, such as a smart telephone, the IoT device may be capable of simultaneously communicating with multiple services, display multimedia, create multimedia, participate in an interactive session, serve data, and so on. As another example, if the IoT device is a sensor, such as a security sensor or a weather temperature, the IoT device may be limited to periodically report its sensory reading to a data aggregator. Regardless of the capabilities of the IoT devices, the IoT devices need to be able to establish a connection with the communications infrastructure (e.g., the HetNet in <FIG>).

eNBs are also commonly referred to as NodeBs, base stations, communications controllers, access points, and so on, depending on the type of the planned network infrastructure. IoT devices are also commonly referred to as user equipments (UEs), mobile stations, mobiles, terminals, users, subscribers, stations, devices, smart devices, and so on, depending on the type of the IoT devices.

While it is understood that HetNets may employ multiple eNBs capable of communicating with a number of IoT devices, only three eNBs, two LPNs, and three IoT devices are illustrated for simplicity.

As discussed previously, a random access procedure is performed by a UE when it initially attaches to a communications system or when it participates in a handover between cells. The UE participates in the random access procedure with an entity (e.g., an eNB, a LPN, and so on) of the communications system or cell. In a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) compliant communications system, a random access procedure typically entails the UE selecting and transmitting one out of a plurality of random access preambles to the eNB (an example of an entity of the communications system as described above) and the eNB assigns network resources to the UE to allow the UE to make a connection request. If the random access procedure fails, the UE must wait a certain amount of time before the UE can try again. The amount of time that the UE waits is referred to as a backoff (BO).

<FIG> illustrates an example random access procedure <NUM>. Random access procedure <NUM> involves processing performed by and transmissions made by an eNB <NUM> and a UE <NUM>. Part of random access procedure <NUM> includes UE <NUM> selecting a random access preamble and transmitting the random access preamble to eNB <NUM>. However, in situations when more than one UE is participating in a random access procedure, there is a non-zero probability that another UE will select the same random access preamble. When multiple UEs transmit the same random access preamble, a preamble collision occurs (event <NUM>). eNB <NUM> determines a backoff (BO) parameter (block <NUM>) and transmits a random access response (RAR) with the backoff parameter to UE <NUM> (event <NUM>). UE <NUM> performs a backoff in accordance with the BO parameter provided by eNB <NUM> (block <NUM>). Once the backoff completes, UE <NUM> transmits the random access preamble (event <NUM>).

The RACH backoff mechanism used in 3GPP LTE is introduced in 3GPP LTE Release-<NUM> and is based on media access control (MAC) backoff indication (BI). Limited changes to the backoff mechanism, such as a reduction in MAC BI size from <NUM> bits to another value and corresponding changes to backoff range can be considered if needed and time permits. The UE randomly and uniformly chooses the backoff time from interval [o, backoff parameter value]. The interval [<NUM>, backoff parameter value] is also referred to as the backoff window. The backoff parameter value is signaled in the form of an index into a table of backoff parameter values. Table <NUM> shows Table <NUM>-<NUM>, backoff parameter values from 3GPP TS <NUM> and Table <NUM> shows 3GPP LTE Physical Random Access Channel (PRACH) preamble durations.

In a narrow-band IoT (NB-IoT) ad hoc meeting and a RAN1#<NUM> meeting, the following items were agreed upon:.

- An NB-PRACH scheme based on single-tone transmissions with <NUM> subcarrier spacing is to be used in NB-IoT;
- Each transmission consists of <NUM> groups with each group comprising <NUM> cyclic prefix (CP) and <NUM> symbols in a symbol group; and
- <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> NB-PRACH repetitions are provided, with an eNB being able to configure up to <NUM> NB-PRACH repetitions from the <NUM> provided repetitions. Table <NUM> shows possible preamble durations based on the <NUM> provided repetitions.

However, these backoff parameter values and backoff time are not matched with NB-IoT preamble durations anymore. It can be seen that with repetitions, NB-IoT PRACH preamble duration is even longer than some of the backoff parameter in Table <NUM>, hence some small values make no sense compared with longer preamble duration. For example, the backoff parameter value with <NUM> is no use for preambles with more than one repetition.

<FIG> illustrates a time-frequency diagram <NUM> of a NB-PRACH transmission with <NUM> repetitions. As discussed previously, each NB-PRACH transmission consists of <NUM> groups with each group comprising <NUM> CP and a symbol group with <NUM> symbols. As an illustrative example, a first NB-PRACH transmission <NUM> includes <NUM> groups <NUM>-<NUM>. As shown in <FIG>, a second NB-PRACH transmission <NUM> also includes <NUM> groups (<NUM>-<NUM>) with each group comprising <NUM> CP and a symbol group with <NUM> symbols. Additionally, pseudorandom frequency hopping is implemented between NB-PRACH transmissions, which is shown in <FIG> as frequency difference <NUM> between first NB-PRACH transmission <NUM> and second NB-PRACH transmission <NUM>. However, the frequency resource usage within each NB-PRACH transmission remains consistent between repetitions.

It is noted that compared to the 3GPP LTE PRACH preamble, the NB-PRACH preamble duration can be much longer, especially in situations when a large number of repetitions are transmitted for the purpose of coverage enhancement. Furthermore, there is also a much wider variation in NB-PRACH length. In some circumstances, e.g., with larger repetition values, the NB-PRACH preamble duration is even longer than some of the backoff parameter values currently used in 3GPP LTE. Hence, some of the smaller backoff parameter values do not make practical sense when compared with larger NB-PRACH preamble durations. As an illustrative example, a backoff parameter value of <NUM> is not useful for NB-PRACH preambles with more than <NUM> repetition. The randomly selected backoff time does not match current NB-PRACH preamble durations. As another illustrative example, according to the 3GPP LTE backoff parameter values, if a cell load is not heavy and a backoff parameter value is selected as <NUM>, but a random access preamble has a duration of <NUM> (without gap time (GT)), the random access preamble will cause interference. As used herein a gap time means a time duration when no signals are transmitted. In a situation when inserted between a Physical Uplink Shared Channel (PUSCH) and a PRACH in the time domain, a gap time is the same as a guard time.

<FIG> illustrates a time-frequency diagram <NUM> illustrating a collision arising from an insufficiently small backoff parameter value. Collisions among RA preamble transmissions may happen due to the mismatched backoff time and preamble durations. For discussion purposes, the situation illustrated in <FIG> involves NB-PRACH preamble durations of <NUM> and a backoff parameter value of <NUM>. At event <NUM>, a first UE (UE1) and a second UE (UE2) transmit NB-PRACH preambles (preamble <NUM> for UE1 and preamble <NUM> for UE2) at the same network resource, resulting in a preamble collision. Both UEs randomly select backoff times of <NUM> (for UE1) and <NUM> (for UE2), respectively. Therefore, after a backoff of <NUM>, UE1 retransmits its NB-PRACH preamble (preamble <NUM>) (event <NUM>) and after a backoff of <NUM>, UE2 retransmits its NB-PRACH preamble (preamble <NUM>) (event <NUM>). However, because the NB-PRACH preambles are <NUM> long, UE1 is unable to complete the transmission of its NB-PRACH preamble <NUM> before UE2 transmits its NB-PRACH preamble <NUM> and another preamble collision takes place.

Using the current backoff mechanism, the collision probability for long preamble durations and short preamble durations differ greatly due to the wide range of preamble lengths. As an illustrative example, under the same cell load conditions and if the backoff parameter value is set to <NUM>, UEs using short preamble durations (e.g., <NUM>) will have many more opportunities for access with low collision probability, but UEs using long preamble durations (e.g., <NUM>) will have less opportunities for access with high collision probability. Additionally, due to the narrow band nature of NB-IoT, long preamble durations may block and cause extra delay in NB PUSCH (NB-PUSCH) transmission. The allocation of network resources may need to be changed to reduce the blocking issue.

<FIG> illustrates a diagram <NUM> of network resources highlighting different collision probabilities. Due to wide range of preamble length, given same resource unit, the collision probabilities for long preamble duration and short preamble duration differ significantly. Diagram <NUM> displays three kinds of random access preamble durations, where each has been allocated resources of the same size. With the legacy mechanism, for the same cell load, if the backoff window is fixed as a large one like <NUM>, for UEs with short preamble duration like <NUM> preamble duration, they have more opportunities to access hence they may have low collision probability; while for UEs with long preamble duration like <NUM> preamble duration, they have less opportunities and high collision probability. It is noted that collision and interference may still happen after backing off, since NB-PRACH preamble duration becomes much longer than some of the backoff parameter value defined for LTE, especially with large number of repetitions; the NB-PRACH preamble lengths vary widely and the collision probabilities may be different for different preamble lengths in some cases.

According to an example embodiment, the backoff parameter values are defined as multiples of random access preamble durations (random access preamble units) to align the backoff time with preamble duration. Instead of defining the backoff parameter values in time values, which results in widely varying access opportunities and collision probability with different random access preamble durations, the defining of the backoff parameter values as multiple of random access preamble units allows the access opportunities and collision probability to remain substantially constant with different random access preamble durations. Example embodiments include:.

Detailed discussion of these example embodiments are provided below.

According to an example embodiment, an eNB determines the backoff parameter values according to the load on corresponding random access channels. A technical standard or an operator of the communications system may define possible backoff parameter values, such as a table of possible backoff parameter values. However, an eNB selects the actual backoff parameter value(s) to signal to the UEs based on the load on the random access channels.

According to an example embodiment, network resource allocation is performed semi-statically to allocate the network resources for NB-PRACH based on random access load. Different numbers of network resources may be allocated for different NB-PRACH channels, with each random access channel being related to one NB-PRACH preamble format (e.g., duration, repetition, and so on). In order to reduce latency to the NB-PUSCH, long random access preambles may be split into multiple parts.

According to example embodiment <NUM>, the backoff parameter values are specified as multiples of random access preamble units and the same backoff parameter values are used for different random access parameter durations. The backoff window of a UE is defined as the product of the backoff parameter value and the random access preamble unit, where the random access preamble unit is equal to the random access preamble duration for the UE. Therefore, the random access window differs for different UEs with different random access preamble durations. The use of the same backoff parameter values for different random access preamble durations is very simple with unified parameters. However, in situations with heavy loads, the latency for long random access preamble durations may be very large. The backoff parameter values may be defined by a technical standard or by an operator of the communications system. Table <NUM> shows an example backoff parameter value table. Table <NUM> shows example backoff parameter values in ms and multiples of preamble durations.

The backoff window may be used in a manner same to the backoff window in 3GPP LTE compliant communications systems, the UE randomly selects a time from within the backoff window and the UE waits until the time expires before retransmitting its NB-PRACH preamble.

The backoff window may be used in a manner similar to the backoff window in 3GPP LTE compliant communications systems, the UE randomly selects a number from within the backoff window and the UE waits the number times the random access preamble unit before retransmitting its NB-PRACH preamble. <FIG> illustrates an example backoff window <NUM> that is <NUM> times the random access preamble unit in duration. Table <NUM> shows example backoff times for two UEs with different random access preamble units.

According to example embodiment <NUM>, backoff parameter values are specified as multiples of random access preamble units and different sets of backoff parameter values are used for different random access preamble repetitions. The use of different sets of backoff preamble values for different random access preamble repetitions enable the adjustment of different backoff window sizes for different random access preamble durations. As an example, long random access preamble durations are assigned a set of backoff parameter values with small values, while short random access preamble durations are assigned a set of backoff parameter values with large values. <FIG> illustrates a table <NUM> of example backoff parameter values with different sets of backoff parameter values assigned to different random access preamble durations. As shown in <FIG>, a first backoff parameter set <NUM> comprising smaller backoff parameter values are assigned to high random access preamble repetitions, a second backoff parameter set <NUM> comprising medium backoff parameter values are assigned to medium random access preamble repetitions, and a third backoff parameter set <NUM> comprising a wide range of backoff parameter values are assigned to low random access preamble repetitions.

According to example embodiment <NUM>, backoff parameter values are specified as multiples of random access preamble units and a combination of backoff window size and frequency hopping based on the number of random access preamble repetitions is used. As an illustrative example, a non-zero backoff window size and frequency hopping are used in situations with small numbers of random access preamble repetitions. As another illustrative example, backoff windows are not used but frequency hopping is used in situations with large numbers of random access preamble repetitions.

<FIG> illustrates a time-frequency graph <NUM> highlighting first example NB-PRACH operation in accordance with example embodiment <NUM>. As shown in <FIG>, the backoff window is a multiple of the random access preamble duration and the frequency hopping occurs within the same frequency NB-PRACH band or PRB. In NB-IoT, a PRB may contain multiple NB-PRACH bands. <FIG> illustrates a time-frequency graph <NUM> highlighting second example NB-PRACH operation in accordance with example embodiment <NUM>. As shown in <FIG>, the backoff window is a multiple of the random access preamble duration and the frequency hopping occurs in a different frequency NB-PRACH band or PRB. The examples shown in <FIG> and <FIG> may be preferably used in situations with small numbers of random access preamble repetitions.

<FIG> illustrates a time-frequency graph <NUM> highlighting third example NB-PRACH operation in accordance with example embodiment <NUM>. As shown in <FIG>, the backoff window is of duration zero (i.e., there is no backoff) and the frequency hopping occurs within the same frequency NB-PRACH band or PRB. <FIG> illustrates a time-frequency graph <NUM> highlighting fourth example NB-PRACH operation in accordance with example embodiment <NUM>. As shown in <FIG>, the backoff window is of duration zero and the frequency hopping occurs in a different frequency NB-PRACH band or PRB. The examples shown in <FIG> and <FIG> may be preferably used in situations with large numbers of random access preamble repetitions.

According to example <NUM>, backoff parameter values are specified as multiples of random access preamble units and a multi-step backoff is performed. As an illustrative example, in a situation wherein NB-PRACH resources are periodically allocated with each period including a number of time-frequency resources allocated for random access preamble transmission, a two-step backoff includes: in a first step, backoff is performed in steps of a predefined period (the period and steps of the period are determined by the eNB or UE ); and in a second step, a random offset within the period is selected (the random offset is determined by the UE). Frequency hopping can also be utilized.

<FIG> illustrates a first time-frequency graph <NUM> highlighting a multi-step backoff in accordance with example embodiment <NUM>. As shown in <FIG>, some time-frequency resources are allocated for random access preamble transmission, while others are allocated for PUSCH transmission, gap time, and so on. Different UEs are assigned in different NB-PRACH periods. As an example, UE1 is assigned an NB-PRACH backoff with one period meaning that UE1 can retransmit a NB-PRACH preamble on a UE selected time-frequency resource in the next period, while UE2 is assigned an NB-PRACH backoff with two periods meaning that UE2 can retransmit an NB-PRACH preamble on a UE selected time-frequency resource in the second period following the first transmission. As shown in <FIG>, when the random access preamble is shorter, there are more transmission opportunities, therefore the UEs can randomly select an access opportunity for random access preamble transmission, while for longer random access preambles, there are fewer opportunities. <FIG> illustrates a second time-frequency graph <NUM> highlighting a multi-step backoff in accordance with example embodiment <NUM>. As shown in <FIG>, no resources are allocated for PUSCH transmission, while others are allocated for random access preamble transmission, gap time, and so on.

In another non-claimed embodiment, it is beneficial to align NB-PRACH with <NUM> milli-second subframe boundary of LTE. In one alternative, different gap time can be inserted in the end of NB-PRACH. Table <NUM> lists example gap times that may be inserted at the end of a NB-PRACH preamble. The gap times listed in Table <NUM> are for illustrative purposes. The actual gap time could be different and depends on the intended cell coverage and/or the preamble duration. For example, the gap time for NB-PRACH with <NUM> repetitions may be <NUM> for <NUM> CP and <NUM> for <NUM> CP, respectively. The gap time may be used for alignment purposes, such as a <NUM> subframe boundary, for example.

In another alternative non-claimed embodiment, multiple NB-PRACH resources can be multiplexed in TDM. Each resource is dedicated to one type of NB-PRACH with the same preamble duration. Multiple allocated NB-PRACH durations are aggregated in time and followed by a gap time to align the whole PRACH resource to <NUM> subframe boundary.

In another alternative non-claimed embodiment, multiple NB-PRACH resources can be multiplexed in TDM. Each resource is dedicated to one type of NB-PRACH with the same preamble duration. Multiple allocated NB-PRACH durations are aggregated in time to align the whole PRACH resource to <NUM> subframe boundary. In this case, there is no gap time after PRACH. For example, <NUM> preambles with duration <NUM> can align with <NUM> subframe boundary.

According to a non-claimed embodiment, an eNB allocates the time-frequency resources for NB-PRACH based on the random access load. The eNB may make use of the system information block (SIB) to signal the allocations. As an illustrative example, the eNB may allocate different numbers of time-frequency resources for different random access channels, with each random access channel being related to a random access preamble format. The random access channels (i.e., the allocated time-frequency resources) may be time division multiplexed (TDM) and/or frequency division multiplexed (FDM) within one NB-PRACH band or PRB. Alternatively, the random access channels may be allocated in different NB-PRACH bands or PRBs. The load may be distributed on a random access channel basis rather than cell basis. When the load is high, more time-frequency resources may be allocated.

<FIG> illustrate example allocations of time-frequency resources to random access channels. <FIG> illustrates an example allocation <NUM> of time-frequency resources to random access channels in a FDM manner. <FIG> illustrates an example allocation <NUM> of time-frequency resources to random access channels in a TDM manner.

According to a non-claimed embodiment, the time-frequency resources allocated for random access channels are multiplexed with time-frequency resources allocated for NB-PUSCH. The multiplexing of the NB-PUSCH and the random access channels may help to reduce the latency of the NB-PUSCH caused by long NB-PRACH preambles.

According to a non-claimed embodiment, multiple bands or PRBs are used in multiplexing the NB-PRACH and the NB-PUSCH. <FIG> illustrates a diagram <NUM> of two bands or PRBs used for multiplexing channels of the same coverage level. In a situation where the NB-PUSCH and the NB-PRACH are of the same coverage level (i.e., they have the same preamble duration), the channels are multiplexed into the same band or PRB, using TDM, for example. <FIG> illustrates a diagram <NUM> of two bands or PRBs when at least one of the bands or PRBs has unused resources. In a situation where there are unused resources in one or more bands or PRBs, the NB-PUSCH can be allocated the unused resources. <FIG> illustrates a diagram <NUM> of two bands or PRBs highlighting priority based allocation. In a situation with mixed multiplexing, the allocation of the resources may be made in accordance with the priority of the preambles. As an example, long preambles have higher priority than short preambles. <FIG> illustrates a diagram <NUM> of two bands or PRBs with separate band or PRB allocation. The NB-PUSCH and the NB-PRACH may be allocated to separate bands or PRBs. If more than <NUM> bands or PRBs are available, each of the NB-PUSCH or the NB-PRACH may be allocated more than <NUM> band or PRB.

According to a claimed embodiment, long random access preambles (preambles with long durations) are split into multiple parts. Each part may be separately scheduled and transmitted. Reducing the duration of the random access preambles reduces the latency on the NB-PUSCH since the network resources are not allocated for extended amounts of time. Each of the shorter parts may utilize the backoff parameter values assigned to a whole random access preamble of the same duration as the shorter part. <FIG> illustrates a time-frequency diagram <NUM> highlighting the splitting of a long random access preamble into shorter parts. As shown in diagram <NUM>, a long random access preamble is split into <NUM> parts and is transmitted in resource <NUM> and resource <NUM>. It is noted that in order to align the boundaries (e.g., <NUM> slot or <NUM> subframe boundary), gap time may be inserted after a random access preamble.

<FIG> illustrates a flow diagram of example operations <NUM> occurring in a UE participating in a random access procedure. Operations <NUM> may be indicative of operations occurring in a UE as the UE participates in a random access procedure.

Operations <NUM> begin with the UE determining that the random access procedure has failed (block <NUM>). The random access procedure has failed if the eNB does not send a random access response to a random access preamble sent by the UE, for example. Alternatively, the random access procedure has failed if the UE receives a random access response from the eNB, but the random access response is not for the UE but another UE that sent the same random access preamble. The UE selects a backoff time from a backoff window ranging from [<NUM>, random access parameter value * random access preamble unit] (block <NUM>). The random access parameter value is signaled by the eNB. As an illustrative example, the eNB signals an indicator of which random access parameter value to use out of a table of random access parameter values specified by a technical standard or an operator of the communications system. The UE waits until the backoff time expires (block <NUM>). When the backoff time expires, the UE retransmits the random access preamble (block <NUM>). In some example embodiments, the random access preamble is segmented into a plurality of blocks and the UE transmits each of the plurality of blocks. In some example embodiments, the UE interleaves a PUSCH with at least some of the blocks.

In a first non-claimed aspect, the present application provides a system and method for performing a random access procedure. The method includes randomly selecting, by a UE, a backoff time from within a backoff window ranging from <NUM> to a specified multiple of a random access preamble unit, waiting, by the UE, until a time initialized with the backoff time expires, and retransmitting, by the UE, a random access preamble.

According to a first embodiment of the method according to the first aspect, the specified multiple is one of a plurality of specified multiples, and different specified multiples are selected for random access preambles with different durations. According to a second embodiment of the method according to any preceding embodiment of the first aspect or the first aspect as such, there is a plurality of sets of specified multiples, and the specified multiple is selected from one of the plurality of sets of specified multiples in accordance with a duration of the random access preamble. According to a third embodiment of the method according to any preceding embodiment of the first aspect or the first aspect as such, the random access preamble is initially transmitted on one of a first carrier or a first band, and the random access preamble is retransmitted on one of a second carrier or a second band.

According to a fourth embodiment of the method according to any preceding embodiment of the first aspect or the first aspect as such, randomly selecting the backoff time includes selecting an initial backoff time within a step of a predefined period, and selecting the backoff time within the initial backoff time. According to a fifth embodiment of the method according to any preceding embodiment of the first aspect or the first aspect as such, the method also includes segmenting the random access preamble into a plurality of blocks, where retransmitting the random access preamble includes separately transmitting each of the plurality of blocks. According to a sixth embodiment of the method according to any preceding embodiment of the first aspect or the first aspect as such, separately transmitting each of the plurality of blocks includes interleaving at least some of the plurality of blocks with an uplink data channel. According to a seventh embodiment of the method according to any preceding embodiment of the first aspect or the first aspect as such, the random access preamble is transmitted in a network resource, and the network resource also includes a gap inserted after the network resource so that a duration of the network resource and a gap time associated with the gap is equal to an integer multiple of a subframe duration.

In a second claimed aspect, the present application provides a system and method for transmitting a random access procedure. The method includes generating, by a UE, the random access preamble, and when a number of physical random access channel (PRACH) repetitions per attempt is larger than a threshold, segmenting, by the UE, the random access preamble into a plurality of blocks, and separately transmitting, by the UE, each of the plurality of blocks.

According to a first embodiment of the method according to the second aspect, separately transmitting each of the plurality of blocks includes interleaving at least some of the plurality of blocks with an uplink data channel.

<FIG> illustrates a flow diagram of example operations <NUM> occurring in an eNB participating in a random access procedure. Operations <NUM> may be indicative of operations occurring in an eNB as the eNB participates in a random access procedure.

Operations <NUM> begin with the eNB determining a backoff parameter value (block <NUM>). The backoff parameter value is specified as a multiple of a random access preamble unit (e.g., a random access preamble duration) of the UE. As an illustrative example, the same set of backoff parameter values is used for all random access preamble units. As another illustrative example, different sets of backoff parameter values are used for different random access preamble durations. As yet another illustrative example, in addition to backoff parameter values based on random access parameter units, frequency hopping is also used. As yet another illustrative example, a multi-step backoff is used, where a period for backoff is specified and an offset within the period is either specified or is selectable by the UE. The eNB signals the backoff parameter value or an indicator thereof to the UE (block <NUM>). The eNB receives a random access preamble in accordance with the backoff parameter value (block <NUM>).

In a third non-claimed aspect, the present application provides a system and method for performing a random access procedure. The method includes determining, by an eNB, a backoff parameter value in accordance with a random access preamble unit associated with a UE participating in the random access procedure, signaling, by the eNB, an indicator of the backoff parameter value, and receiving, by the eNB, a random access preamble in accordance with the backoff parameter value.

According to a first embodiment of the method according to the third aspect, the backoff parameter value specifies a multiple of the random access preamble unit. According to a second embodiment of the method according to any preceding embodiment of the third aspect or the third aspect as such, there is a plurality of sets of specified multiples, and the specified multiple is selected from one of the plurality of sets of specified multiples in accordance with a duration of the random access preamble. According to a third embodiment of the method according to any preceding embodiment of the third aspect or the third aspect as such, the method also includes selecting a step of a predefined period, and signaling an indicator of the step of the predefined period.

According to a fourth embodiment of the method according to any preceding embodiment of the third aspect or the third aspect as such, the random access preamble is segmented into a plurality of blocks, and receiving the random access preamble includes separately receiving each of the plurality of blocks. According to a fifth embodiment of the method according to any preceding embodiment of the third aspect or the third aspect as such, the method also includes receiving an uplink data channel interleaved with at least some of the plurality of blocks.

In order to deal with the possible collision problem caused by mismatched backoff parameter values, it is to define the backoff time as multiple times of basic time units, where the unit may equal to a preamble duration. From the RAN1 aspect, a problem is that the preamble duration (without considering GT) is not aligned with the subframe boundary of <NUM> subframe for <NUM> subcarrier spacing and <NUM> subframe for <NUM> subcarrier spacing, which may increase the scheduling complexity. According to an example embodiment, one solution is to insert gap time. Following are two examples:.

According to another non-claimed embodiment, one solution is to bundle a plurality of random access preamble transmissions without a gap time and use a resource pattern to schedule the random access preamble transmissions. In this solution, it is assumed that there is a dedicated band for random access transmissions, and eNB won't schedule NB-PUSCH in this band. Hence there is no need for GT. Multiple random access preamble transmission resources corresponding to different preamble durations are multiplexed by TDM. <FIG> illustrates a first diagram <NUM> of network resources highlighting a continuous allocation of network resources. <FIG> illustrates a second diagram <NUM> of network resources highlighting a mixed allocation of network resources.

Proposal <NUM>: Consider above solutions to align the PRACH channel with NB-IoT subframe boundaries. To deal with the possible unbalanced collision probability for different PRACH preamble formats, semi-statically resource allocation for PRACH may be adopted. Firstly, a random access channel load indicator can be defined instead of current cell load. This is to say, the load is per random access channel basis. Each random access channel is related to one preamble format. When load is heavy, more resources may be allocated. Consequently, eNB can allocate different number of resources for different random access channels based on random access channel load, in which the resource allocation information may be carried via SIB.

Proposal <NUM>: Consider semi-static resource allocation based on random access channel load to balance the collision probabilities in different random access channels for different preamble formats.

<FIG> illustrates a block diagram of a non-claimed embodiment processing system <NUM> for performing methods described herein, which may be installed in a host device. As shown, the processing system <NUM> includes a processor <NUM>, a memory <NUM>, and interfaces <NUM>-<NUM>, which may (or may not) be arranged as shown in <FIG>. The processor <NUM> may be any component or collection of components adapted to perform computations and/or other processing related tasks, and the memory <NUM> may be any component or collection of components adapted to store programming and/or instructions for execution by the processor <NUM>. In an embodiment, the memory <NUM> includes a non-transitory computer readable medium. The interfaces <NUM>, <NUM>, <NUM> may be any component or collection of components that allow the processing system <NUM> to communicate with other devices/components and/or a user. For example, one or more of the interfaces <NUM>, <NUM>, <NUM> may be adapted to communicate data, control, or management messages from the processor <NUM> to applications installed on the host device and/or a remote device. As another example, one or more of the interfaces <NUM>, <NUM>, <NUM> may be adapted to allow a user or user device (e.g., personal computer (PC), etc.) to interact/communicate with the processing system <NUM>. The processing system <NUM> may include additional components not depicted in <FIG>, such as long term storage (e.g., non-volatile memory, etc.).

In some embodiments, the processing system <NUM> is included in a network device that is accessing, or part otherwise of, a telecommunications network. In one example, the processing system <NUM> is in a network-side device in a wireless or wireline telecommunications network, such as a base station, a relay station, a scheduler, a controller, a gateway, a router, an applications server, or any other device in the telecommunications network. In other embodiments, the processing system <NUM> is in a user-side device accessing a wireless or wireline telecommunications network, such as a mobile station, a user equipment (UE), a personal computer (PC), a tablet, a wearable communications device (e.g., a smartwatch, etc.), or any other device adapted to access a telecommunications network.

In some embodiments, one or more of the interfaces <NUM>, <NUM>, <NUM> connects the processing system <NUM> to a transceiver adapted to transmit and receive signaling over the telecommunications network. <FIG> illustrates a block diagram of a transceiver <NUM> adapted to transmit and receive signaling over a telecommunications network. The transceiver <NUM> may be installed in a host device. As shown, the transceiver <NUM> comprises a network-side interface <NUM>, a coupler <NUM>, a transmitter <NUM>, a receiver <NUM>, a signal processor <NUM>, and a device-side interface <NUM>. The network-side interface <NUM> may include any component or collection of components adapted to transmit or receive signaling over a wireless or wireline telecommunications network. The coupler <NUM> may include any component or collection of components adapted to facilitate bi-directional communication over the network-side interface <NUM>. The transmitter <NUM> may include any component or collection of components (e.g., up-converter, power amplifier, etc.) adapted to convert a baseband signal into a modulated carrier signal suitable for transmission over the network-side interface <NUM>. The receiver <NUM> may include any component or collection of components (e.g., down-converter, low noise amplifier, etc.) adapted to convert a carrier signal received over the network-side interface <NUM> into a baseband signal. The signal processor <NUM> may include any component or collection of components adapted to convert a baseband signal into a data signal suitable for communication over the device-side interface(s) <NUM>, or vice-versa. The device-side interface(s) <NUM> may include any component or collection of components adapted to communicate data-signals between the signal processor <NUM> and components within the host device (e.g., the processing system <NUM>, local area network (LAN) ports, etc.).

The transceiver <NUM> may transmit and receive signaling over any type of communications medium. In some embodiments, the transceiver <NUM> transmits and receives signaling over a wireless medium. For example, the transceiver <NUM> may be a wireless transceiver adapted to communicate in accordance with a wireless telecommunications protocol, such as a cellular protocol (e.g., long-term evolution (LTE), etc.), a wireless local area network (WLAN) protocol (e.g., Wi-Fi, etc.), or any other type of wireless protocol (e.g., Bluetooth, near field communication (NFC), etc.). In such embodiments, the network-side interface <NUM> comprises one or more antenna/radiating elements. For example, the network-side interface <NUM> may include a single antenna, multiple separate antennas, or a multi-antenna array configured for multi-layer communication, e.g., single input multiple output (SIMO), multiple input single output (MISO), multiple input multiple output (MIMO), etc. In other embodiments, the transceiver <NUM> transmits and receives signaling over a wireline medium, e.g., twisted-pair cable, coaxial cable, optical fiber, etc. Specific processing systems and/or transceivers may utilize all of the components shown, or only a subset of the components, and levels of integration may vary from device to device.

It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a selecting unit/module, a waiting unit/module, a determining unit/module, and/or a signaling unit/module. The respective units/modules may be hardware, software, or a combination thereof. For instance, one or more of the units/modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

Claim 1:
A method for transmitting a random access preamble, the method comprising:
generating, by a user equipment, UE, the random access preamble; and characterized in that:
when a number of physical random access channel, PRACH, repetitions per attempt is larger than a threshold,
splitting, by the UE, the random access preamble into a plurality of parts in discontinuous time resources, and
separately transmitting, by the UE, each of the plurality of parts;
wherein the random access preamble comprises the PRACH repetitions, each PRACH repetition of the PRACH repetitions comprises <NUM> symbol groups (<NUM>, <NUM>, <NUM>, <NUM>).